|
|
Supplement to DOC-1010ATMCR11.2= (Document Number 78-4830-02)
The following is an update to the LightStream 1010 ATM Switch Command Reference. The information in this update reflects information added after printing the command reference manual. Replace or add the section in the manual with the sections in this update. The changes in this update are arranged in alphabetical order.
Replace the following commands in the manual with the commands in this update:
Add the following commands to the manual:
To convert E.164 AESAs with the E.164 AFI to the left-justified encoding format, use the aesa embedded-number left-justified ATM router configuration command. To disable this feature, use the no form of this command.
aesa embedded-number left-justifiedThis command has no keywords or arguments.
Disabled
ATM router configuration
Configure all switches within the PNNI routing domain with the aesa embedded-number left-justified ATM router configuration command.
Disable the lowest-level node (node 1) before entering the aesa embedded-number left-justified ATM router configuration command.
The following example shows how to configure embedded left-justified E.164 AESAs.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-pnni-node)# node 1 disable Switch(config-pnni-node)# exit Switch(config-atm-router)# aesa embedded-number left-justified Switch(config-atm-router)# node 1 enable
debug atm pnni
show atm pnni aesa embedded-number
To enable or disable ILMI connectivity procedures and to change the ILMI keepalive poll interval, use the atm ilmi-keepalive interface configuration command. To disable ILMI connectivity procedures, use the no form of this command.
atm ilmi-keepalive [seconds [retry number]]
seconds | Period in seconds, from 1 to 65,535 at which the IME is polled. The default is 5 seconds. |
number | Number of retries from 2 to 5. The default is 5 retries. |
Disabled
Interface configuration
This command does not apply to the ASP 2/0/0 interface.
This command enables ILMI connectivity procedures, as described in Section 8.3.1 of the ATM Forum ILMI 4.0 Specification.
The following example enables ILMI keepalives on ATM interface 1/0/0 with a poll interval set for 4 seconds and the number of retries to 3.
Switch(config)# interface atm 1/0/0 Switch(config-if)# atm ilmi-keepalive 4 retry 3 Switch(config-if)#
atm ilmi-enable
show atm ilmi-status
To allow the mode field in AAL5 information elements (IEs) to be added when using UNI 3.0, use the atm signalling ie aal5 mode interface configuration command.
To disable this feature, use the no form of this command.
atm signalling ie aal5 mode {stream | message}
stream | Streaming mode. |
message | Message mode. |
Message mode is passed in UNI 3.0 AAL5 information elements.
Interface configuration
The atm signalling ie aal5 mode interface configuration command allows you to fill in the mode field in AAL5 IEs when using UNI 3.0.
The AAL5 IE has a mode field in UNI version 3.0. This mode field was removed in UNI version 3.1. When a setup request arrives from a UNI 3.1 side connection, the AAL5 IE does not have the mode information. Some vendor switches and end systems reject the connection because the mode information is missing. To allow interoperability, this atm signalling ie aal5 mode interface configuration command allows, by default, a message mode field to be added statically on UNI 3.0 side connections even if one was not received from the other side, for example, from a UNI 3.1 connection.
The following example configures, in interface configuration mode, ATM interface 1/0/0 signalling IEs in AAL5 to include a mode field configured as message.
Switch(config)# config terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface atm 1/0/0 Switch(config-if)# atm signalling ie aal5 mode message Switch (config-if)# ^Z Switch#
show running-config
To specify the value of virtual path connection identifier (VPCI) that is to be carried in the signalling messages within a VP tunnel, use the atm signalling vpci subinterface configuration command.
To use the default configuration, use the no form of this command.
atm signalling vpci vpci_number
vpci_number | VPCI number 0 to 255. |
Use the value of VPI on which the subinterface is established.
Subinterface configuration
The atm signalling vpci subinterface command allows you to configure the VPCI to be different from VPI when configuring PVP tunnels.
The connection identifier information element (IE) is used in signalling messages to identify the corresponding user information flow. The connection identifier IE contains the VPCI and VCI.
For example, if you want to configure a PVP tunnel connection from a LightStream 1010 ATM switch on VPI 2, VCI X, to a router with a virtual path switch in between, the signalling message would contain connection ID, VPI 2, VCI X. Since the PVP tunnel at the router end is on VPI 3, VCI X, the connection will be refused. By configuring VPCI to 3, you can configure the signalling message explicitly to contain connection ID VPI 3, VCI X, instead of containing VPI 2, VCI X.
This command could also be used to support virtual UNI connections.
The following example configures a PVP tunnel on ATM interface 0/0/0, PVP 99, and then configures the connection ID VCPI as 0 in subinterface configuration mode.
Switch(config)# config terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface atm 1/0/0 Switch(config-if)# atm pvp 99 Switch(config-if)# exit Switch(config)# interface atm 1/0/0.99Switch(config-subif)# atm signalling vpci 0 Switch(config-subif)# end Switch#
show running-config
To clear the dynamic LE ARP table or a single LE ARP entry of the LANE client configured on the specified subinterface or emulated LAN, use the clear lane le-arp privileged EXEC command.
clear lane le-arp [interface atm card/subcard/port [.subinterface-num] | name elan-name]
card/subcard/port | ATM interface for the LANE client whose LE ARP table or entry is to be cleared. |
.subinterface-num | Subinterface for the LANE client whose LE ARP table or entry is to be cleared. |
elan-name | Name of the emulated LAN for the LANE client whose LE ARP table or entry is to be cleared. Maximum length is 32 characters. |
mac-addr | MAC address of the entry to be cleared from the LE ARP table. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
Privileged EXEC
This command only removes dynamic LE ARP table entries. It does not remove static LE ARP table entries.
If you do not specify an interface or an emulated LAN, this command clears all the LANE ARP tables of any LANE client in the switch.
If you specify a major interface (not a subinterface), this command clears all the LANE ARP tables of every LANE client on all the subinterfaces of that interface.
Use of this command also removes the fast-cache entries built from the LANE ARP entries.
The following example clears all the LANE ARP tables for all clients on the switch.
Switch# clear lane le-arp
The following example clears all the LANE ARP tables for all LANE clients on all the subinterfaces of interface 2/0/0.
Switch# clear lane le-arp interface 2/0/0
The following example clears the entry corresponding to MAC address 0800.AA00.0101 from the LE ARP table for the LANE client on the emulated LAN red.
Switch# clear lane le-arp name red 0800.aa00.0101
The following example clears all dynamic entries from the LE ARP table for the LANE client on the emulated LAN red.
Switch# clear lane le-arp name red
The following example clears the dynamic entry from the LE ARP table for the LANE client with next-hop router descriptor segment number 1, bridge number 1, on the emulated LAN red.
Switch# clear lane le-arp name red route-desc segment 1 bridge 1
To force a LANE server on a specified subinterface or emulated LAN to drop the Control Direct and Control Distribute VCCs to a given LANE client and force the client to rejoin subject to the new bindings (after they have been changed), use the clear lane server privileged EXEC command.
clear lane server {interface card/subcard/port[.subinterface-num] | name elan-name}
card/subcard/port | Card, subcard, and port number of the ATM interface. |
subinterface-num | Subinterface on which the LANE server is configured. |
elan-name | Name of the emulated LAN on which the LANE server is configured. Maximum length is 32 characters. |
client-atm-addr | ATM address of the LANE client. |
lecid | LANE client ID. The LANE client ID is a value between 1 and 4096. |
mac-addr | MAC address of the LANE client. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
Privileged EXEC
After changing the bindings on the configuration server, enter this command on the LANE server. The LANE server will drop the Control Direct and Control Distribute VCCs to the LANE client. The client then asks the LANE configuration server for the location of the LANE server of the emulated LAN it is requesting to join.
If no LANE client is specified, all LANE clients attached to the LANE server are dropped.
The following example forces all the LANE clients on the emulated LAN named red to be dropped. The next time they try to join, they are forced to join a different emulated LAN.
Switch# clear lane server red
lane database
show lane server
To clear the RIF cache, use the clear rif-cache privileged EXEC command.
clear rif-cacheThis command has no keywords or arguments.
Privileged EXEC
Some entries in the RIF cache are dynamically added, and others are static.
rif
rif timeout
show rif
To enable PNNI debugging output, use the following debug atm pnni privileged EXEC commands. To disable PNNI debugging output, use the no form of these commands.
debug atm pnni adj-eventsadj-events | Turns on adjacency-related event debugging. The feature can be turned on for a specific PNNI interface. |
|---|---|
adj-packet | Turns on database summary and request packet debugging. The feature can be turned on for a specific PNNI interface. |
aggregation | Turns on link aggregation debugging. |
all | Turns on all PNNI debugging. The feature can be turned on for a specific PNNI interface. |
api | Turns on application interface debugging. |
election | Turns on PGL PNNI election debugging. |
embedded-number | Turns on debugging of E.164 AESAs with the E.164 AFI in the left-justified encoding format. |
flood-packet | Turns on PTSP and ACK packet debugging. |
hello-packet | Turns on Hello packet debugging. The feature can be turned on for a specific PNNI interface. |
rm | Turns on resource management debugging. Debugging output can be limited to a single node using the local-node node-index option.
|
route-all | Turns on all route debugging. |
route-errors | Turns on PNNI route errors debugging. |
snmp | Turns on debugging of SNMP events (get and set) related to the PNNI MIBs. |
svcc-rcc | Turns on debugging for SVCC RCC setup, SVCC Hello processing, and horizontal link extension processing. |
topology | Turns on internal topology maintenance debugging. |
Privileged EXEC
To activate a LANE client on the specified subinterface, use the lane client interface configuration command. To remove a previously activated LANE client on the subinterface, use the no form of this command.
lane client {ethernet | tokenring} [elan-name]
ethernet | Identifies the type of emulated LAN attached to this subinterface as Ethernet. |
tokenring | Identifies the type of emulated LAN attached to this subinterface as Token Ring. |
elan-name | Name of the emulated LAN. This argument is optional because the client obtains its emulated LAN name from the configuration server. Maximum length is 32 characters. |
No LANE clients are enabled on the interface.
Interface configuration
This command only applies to the CPU interface.
If a lane client command has already been entered on the subinterface for a different emulated LAN, the client initiates termination procedures for that emulated LAN and joins the new emulated LAN.
If you do not provide an elan-name value, the client contacts the server to find which emulated LAN to join. If you do provide an emulated LAN name, the client consults the configuration server to ensure that no conflicting bindings exist.
The following example shows enabling a Token Ring LANE client on a subinterface.
Switch(config)# interface atm 2/0/0.1 Switch(config-subif)# lane client tokenring
lane client-atm-address
To add a static entry to the LE ARP table of the LANE client configured on the specified subinterface, use the lane le-arp interface configuration command. To remove a static entry from the LE ARP table of the LANE client on the specified subinterface, use the no form of this command.
lane le-arp {mac-address | route-desc segment seg-num bridge bridge-num} atm-address
mac-address | MAC address to bind to the specified ATM address. |
atm-address | ATM address. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
No static address bindings are provided.
Interface configuration
This command only applies to the CPU interface.
This command only adds or removes a static entry binding a MAC address or next-hop route descriptor (for Token Ring) to an ATM address. It does not add or remove dynamic entries. Removing the static entry for a specified ATM address from an LE ARP table does not release the data direct VCC established to that ATM address. However, clearing a static entry clears any fast-cache entries that were created from the MAC address-to-ATM address binding.
Static LE ARP entries are not aged and are not removed automatically.
To remove dynamic entries from the LE ARP table of the LANE client on the specified subinterface, use the clear lane le-arp command.
The following example shows adding a static entry to the LE ARP table on the ASP interface ATM 2/0/0.
Switch(config)#interface atm 2/0/0Switch(config-if)#lane le-arp 0800.aa00.0101 47.000014155551212f.00.00.0800.200C.1001.01
The following example shows adding a static entry to the LE ARP table binding segment number 1, bridge number 1 to the ATM address.
Switch(config)#interface atm 2/0/0Switch(config-if)#lane le-arp route-desc segment 1 bridge 1 39.020304050607080910111213.00000CA05B41.01
clear lane le-arp
To enable a LANE server and a broadcast-and-unknown server on the specified subinterface, use the lane server-bus interface configuration command. To disable a LANE server and broadcast-and-unknown server on the specified subinterface, use the no form of this command.
lane server-bus {ethernet | tokenring} elan-name
ethernet | Identifies the type of emulated LAN attached to this subinterface as Ethernet. |
tokenring | Identifies the type of emulated LAN attached to this subinterface as Token Ring. |
elan-name | Name of the emulated LAN. Maximum length is 32 characters. |
No LAN type and emulated LAN name are provided.
Interface configuration
The LANE server and the broadcast-and-unknown server are located on the same switch.
If a lane server-bus command was entered on the subinterface for a different emulated LAN, the server initiates termination procedures with all clients and comes up as the server for the new emulated LAN.
Use of the no form of this command removes a previously configured LANE server and broadcast-and-unknown server on the subinterface.
The following example enables a LANE server and broadcast-and unknown server for a Token Ring ELAN.
Switch(config)# interface atm 2/0/0.1 Switch(config-subif)# lane server-bus tokenring
lane server-atm-address
To enable collection and use of RIF information on a subinterface, use the multiring interface configuration command. To disable the use of RIF information, use the no form of this command.
multiring ip [all-routes | spanning]
ip | Protocol type for which to enable multiring. |
all-routes | Uses all-routes explorers. |
spanning | Uses spanning-tree explorers. |
Disabled
Interface configuration
In source-route bridged or Token Ring switched networks only packets with RIF are forwarded by intermediate source-route bridges. To ensure that IP datagrams are transmitted across a Token Ring switch or source-route bridge to and from a LightStream 1010 ATM switch, use the multiring command.
When multiring is enabled, the Token Ring LEC strips the RIF information and caches it in its RIF table for incoming IP/ARP packets. It adds a RIF for subsequent IP/ARP response packets to be sent back across the network. Use the show rif command to display the RIF table entries. To configure static RIF entries, use the rif command.
The following example shows how to configure a subinterface with an IP address and Token Ring LANE LEC, and then enable multiring.
Switch(config)# interface atm 2/0/0.1 Switch(config-subif)# ip address 1.1.1.2 255.255.255.0 Switch(config-subif)# lane client tokenring cisco Switch(config-subif)# multiring ip
rif
show rif
To specify or replace the ring number of the emulated LAN in the configuration server's configuration database, use the name local-seg-id database configuration command. To remove the ring number from the database, use the no form of this command.
name elan-name local-seg-id seg-num
elan-name | Name of the emulated LAN. The maximum length of the name is 32 characters. |
seg-num | Segment number to be assigned to the emulated LAN. The number ranges from 1 to 4095. |
No emulated LAN name or segment number is provided.
Database configuration
This command is used for Token Ring LANE.
Refer to the lane database command for instructions on how to enter database configuration mode.
The same LANE ring number cannot be assigned to more than one emulated LAN.
The no form of this command deletes the relationships.
The following example specifies a ring number of 1024 for the emulated LAN red.
Switch(lane-config-database)# name red local-seg-id 1024
To enter static source-route information into the routing information field (RIF) cache, use the rif global configuration command. To remove an entry from the cache, use the no form of this command.
rif mac-addr [rif-string]
mac-addr | MAC address of the RIF entry. |
rif-string | Series of 4-digit hexadecimal numbers separated by a period (.). This RIF string is inserted into the packets sent to the specified MAC address. |
No static source-route information is entered.
Global configuration
If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, you may need to add static information to the RIF cache.
Using the command rif mac-address without any other arguments puts an entry into the RIF cache indicating that packets for this MAC address will not have RIF information.
Do not configure a static RIF with any of the all rings type codes. Doing so causes traffic for the configured host to appear on more than one ring and leads to unnecessary congestion.
The following example shows inserting a RIF cache entry with MAC address 1000.5A12.3456 and RIF 0630.0081.0090.
Switch(config)# rif 1000.5A12.3456 0630.0081.0090
multiring
show rif
To specify that RIFs always be stored in the forward direction, use the rif always-forward global configuration command. To disable forward-direction storing of RIFs, use the no form of this command.
rif always-forwardThis command has no keyword or arguments.
RIFs are not stored in the forward direction.
Global configuration
rif
show rif
To specify the number of minutes an inactive entry is kept in the RIF cache, use the rif timeout global configuration command. To restore the default time, use the no form of this command.
rif timeout minutes
minutes | Number of minutes an inactive RIF entry is kept in the cache. The valid range is 1 to 120. |
15 minutes
Global configuration
A RIF entry is refreshed only if a RIF field of an incoming frame is identical to the RIF information of the RIF entry in the cache.
Until a RIF entry is removed from the cache, no new information is accepted for that RIF entry.
The following example shows changing the timeout to 5 minutes.
Switch(config)# rif timeout 5
clear rif-cache
rif
show rif
To permit invalidated and aged-out entries to be removed from the RIF cache, use the rif validate-age global configuration command. To disable this feature, use the no form of this command.
rif validate-ageThis command has no keywords or options.
Aged entries are removed.
Global configuration
rif
rif timeout
show rif
To enable RIF validation for entries learned on an interface, use the rif validate-enable global configuration command. To disable the specification, use the no form of this command.
rif validate-enableThis command has no keywords or arguments.
RIF validation is enabled.
Global configuration
A RIF validation algorithm is used for the following cases:
A directed IEEE TEST command is sent to the destination MAC address. If a response is received in the time specified by rif validate-time, the entry is refreshed and is considered valid. Otherwise, the entry is removed from the cache. To prevent sending too many TEST commands, any entry that has been refreshed in less than 70 seconds is considered valid.
Validation is triggered when any of the follows occurs:
rif timeout
To send IEEE XID explorer packets instead of TEST commands to learn RIF information, use the rif xid-explorer global configuration command. To disable this specification, use the no form of this command.
rif xid-explorerThis command has no keywords or arguments.
TEST commands are sent.
Global configuration
rif
show rif
To show the E.164 AESAs with the E.164 AFI to the left-justified encoding format, use the show atm pnni aesa embedded-number privileged EXEC command.
show atm pnni aesa embedded-number
show atm pnni aesa embedded-number prefix
prefix | E.164 AFI portion of the E.164 AESA. |
Privileged EXEC
This command displays E.164 AESAs with the E.164 AFI to the left-justified encoding format.
The following is sample output from the show atm pnni aesa embedded-number command, without the prefix specified.
Switch# show atm pnni aesa embedded-number AESA embedded-number is left-justified.
The following is sample output from the show atm pnni aesa embedded-number command, with the prefix specified.
Switch# show atm pnni aesa embedded-number 45001234
AESA embedded-number is left-justified.
Translating 45.0012.34/32 to
45.1234/24
aesa embedded-number left-justified
debug atm pnni
To show the aggregated PNNI links on the switch, use the show atm pnni aggregation link privileged EXEC command.
show atm pnni aggregation link [local-node node-index] [aggregation-detail | border-detail]local-node | Specifies the PNNI local node, where the higher level induced links are generated. |
node-index | Index number of the PNNI local node, in the range of 1 to 8. |
aggregation-detail | Displays the aggregation table with aggregated metrics for the higher level induced links. |
border-detail | Displays the aggregation table with all border uplink metrics. |
Privileged EXEC
This command displays the aggregation table(s) for PNNI links.
The following is sample output from the show atm pnni aggregation link command.
Switch# show atm pnni aggregation link
PNNI link aggregation for local-node 2 (level=44, name=rhino18.2.44)
Configured aggregation modes (per service class):
CBR VBR-RT VBR-NRT ABR UBR
~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~
best-link best-link best-link best-link best-link
Aggregated outside links from child peer group:
Upnode Number: 10 Upnode Name: rhino27.2.44
AggToken InducPort BorderPort Border Node(No./Name)
~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
0 02202000 ATM0/1/2 1 rhino18
Upnode Number: 11 Upnode Name: Switch.3.32
AggToken InducPort BorderPort Border Node(No./Name)
~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
0 02CF2000 ATM0/0/2 1 rhino18
5 02CF2005 ATM0/0/2.4 9 ls1010-1
8197 02CF22A1 ATM0/0/1 9 ls1010-1
PNNI link aggregation for local-node 3 (level=32, name=rhino18.3.32)
Configured aggregation modes (per service class):
CBR VBR-RT VBR-NRT ABR UBR
~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~
best-link best-link best-link best-link best-link
Aggregated outside links from child peer group:
Upnode Number: 11 Upnode Name: Switch.3.32
AggToken InducPort BorderPort Border Node(No./Name)
~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
0 03CF2000 2CF2000 2 rhino18.2.44
5 03CF2005 2CF2005 2 rhino18.2.44
8197 03CF22A1 2CF22A1 2 rhino18.2.44
To display the current contents of the RIF cache, use the show rif privileged EXEC command.
show rifThis command has no arguments or keywords.
Privileged EXEC
The following is sample output from the show rif command:
Switch# show rif Codes: * interface, - static, + remote Hardware Addr How Idle (min) Routing Information Field 5A00.0000.2333 atm2/0/0 3 08B0.0101.2201.0FF0 5B01.0000.4444 - - - 0000.1403.4800 atm2/0/0 0 - 0000.2805.4C00 atm2/0/0 * - 0000.2807.4C00 atm2/0/0 * - 0000.28A8.4800 atm2/0/0 0 - 0077.2201.0001 atm2/0/0 10 0830.0052.2201.0FF0
In the display, entries marked with an asterisk (*) are the interface addresses of the router. Entries marked with a dash (-) are static entries. Entries with a number indicate cached entries. If the RIF timeout is set a value other than the default of 15 minutes, the timeout is displayed at the top of the display.
| Field | Description |
|---|---|
Hardware Addr | MAC address for this entry. |
How | Describes how the RIF has been learned. Possible values are atm2/0/0 or "-". |
Idle (min) | Indicates how long (in minutes) since the last response was received directly from this node. |
Routing Information Field | RIF number. |
multiring
rif
Use the sonet tx-ais on-rx-defect command to enable a SONET interface to send an alarm indication signal (AIS) if it detects the receive port has failed. To disable, use the no form of this command.
sonet tx-ais on-rx-defect
None |
|
Disabled
Interface Configuration
The sonet tx-ais on-rx-defect command should not be enabled on both ATM switch interfaces connected to the same physical line. Even if no alarm exist, both interfaces will see the AISs and never come up.
The following example enables AIS on an ATM interface.
Switch(config)# interface atm 3/0/0 Switch(config-if)# sonet tx-ais on-rx-defect
show controllers
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
|
|