|
|
The ONS 15190 is configured and controlled using a specialized command line interface (CLI) language. This chapter describes typical configuration scenarios and provides examples for the most common tasks. A complete description of all CLI commands used to control the ONS 15190 is provided in the chapter "Command Line Interface Reference".
Configuring the ONS 15190 is presented in the following sections:
Note that the basic configuration entity in the ONS 15190 is a node. A node describes a connection or set of connections to the system and may be of the following types: SRP, APS, PoS, sniff, or fiber. Although a node generally describes a connection to an external device, a node can be logically defined even before the device is actually connected to the ONS 15190. A detailed description of the various types of nodes is presented in the chapter "Command Line Interface Reference".
When the ONS 15190 is physically connected to the desired devices (for example, routers), the various nodes (which correspond to external devices) must be defined, and then the unit can be configured to form connections between these nodes. This configuration can include the definition of SRP rings or PoS/APS connections between nodes. It can also include the definition of sniff nodes that are used to monitor other nodes in the system. This configuration can be performed via telnet or an RS-232C connection to the unit.
Logging On to the ONS 15190 is presented in the following sections:
Before the ONS 15190 can be accessed via the network, the networking parameters must be configured via direct RS-232C serial connection. Log in to the system as administrator. Initially, the login information will be as follows:
To ensure system security, change the password the first time you use the system using the password command.
Use the net command to set the IP address, subnet mask, and default gateway of the unit. The first string is the IP address; the second string is the subnet mask; the third is the default gateway.
admin>net set ip 169.192.10.105 255.255.255.0 169.192.10.1
At this point the system can be accessed over a network at the given IP address.
When a telnet connection is established with the ONS 15190, the initial screen prompts you for your username and password. Enter either user or admin as the username and then the appropriate password to log in to the system. Initially, the password for the user login is user.
The ONS 15190 Configuration is described in the following sections:
The simplest way to configure the system for SRP use is with the command autoconnect. After the various nodes are physically connected to the ONS 15190, enter autoconnect at the system prompt. The system will determine all physical connections, configure them into a one or two rings (one for OC-12c/STM-4 and one for OC-48/STM-16) and then display them in table format for your approval.
admin> autoconnect
Sniff configuration:
Sniffer Port Sniffed node Port
-------------------- ----- -------------------- ----------
No sniffer nodes.
POS connections:
Node IP Address Ports Type Other
-------------------- --------------- -------------- ---- ----------
12000_left-2 11.1.1.2 L5.1 OC12
12000_Right-2 11.1.1.1 L7.1 OC12
Ring configuration (nodes in order of outer ring):
Ring Name Nodes IP Address A-Port B-Port Type Other
---------- ------------- ------------- ------ ------ ---- ---------
ring1 12000_left 10.1.1.2 L1.2 L1.1 OC12
12000_Right 10.1.1.1 L4.1 L2.1 OC12
7200_center 10.1.1.5 L4.2 L8.1 OC12
7200_left 10.1.1.4 L5.2 L6.1 OC12
Apply configuration? y
Configuration applied.
When the configuration is detected, you are prompted to apply the configuration. Enter y to apply the configuration or n to discard. If warning messages are displayed when executing the autoconnect command, refer to the section "Troubleshooting Configuration Problems" later in this chapter .
 |
Note The autoconnect command ignores non-SRP nodes. |
In most instances, the autoconnect feature successfully identifies all connected nodes and configures the ring correctly. Sometimes, however, manual adjustments might need to be made. If all nodes are correctly identified, and you need to reconfigure the ring(s), see the section "Creating an SRP Ring". If you need to add nodes to the ring after the ring is configured, you must first configure the individual nodes.
To configure a connected SRP node, you must first create a definition for the node within the ONS 15190. To do this, use the command rconf node new. Specify the name and type of the node you are creating and the specific port in the unit to which it is attached. The syntax for this command is shown in the following example:
admin>rconf node new srp ny L1.1 L1.2 Node ny added.
Srp is the node type; ny is the node name; L1.1 is the A port of the node; L1.2 is the B port of the node. This node definition is made for each node connected to the unit unless the autoconnect command is used.
admin> rconf node new srp phili L2.1 L1.2 Node phili added. admin> rconf node new srp boston L3.1 L4.2 Node boston added. admin> rconf node new srp hartford L5.1 L6.2 Node hartford added. admin> rconf node new srp baltimore L6.1 L7.2 Node baltimore added.
Other possible node types are APS, fiber, PoS, and sniff. If no node type is specified, SRP is the default. If the line cards to which the node is to be connected are not present when the node is defined, you must specify the port speed manually. For more information on the specific syntax for each node type, refer to the chapter "Command Line Interface Reference" .
After the individual nodes are defined, you can configure the logical ring. To do this, use the command rconf ring. To define a new ring, use the new option as illustrated in this example:
admin> rconf ring new control1 Ring control1 added.
The ring control1 is created. Now the specific nodes must be added to this new ring. The following example illustrates the addition of the defined 5 nodes to this ring:
admin> rconf ring control1 nodes boston ny hartford phili baltimore Ring control1 node list set.
The order of the nodes is according to the order of the outer ring.
To add a node (named node) to an existing ring (named ring), use the command rconf ring ring add node. To remove a node (named node) from a ring (named ring), use the command rconf ring ring remove node.
The ONS 15190 can be used to connect various Packet over SONET (PoS) nodes, thereby utilizing a protect link to provide greater redundancy. Create PoS nodes using the command rconf node new and connect them together using the command rconf pos connect.
In the following example, two PoS nodes, pos1 and pos2, are defined and connected to each other.
admin> rconf node new pos pos1 l1.1 oc12 OC12 POS node pos1 created. admin> rconf node new pos pos2 l3.2 oc12 OC12 POS node pos2 created. admin> rconf pos connect pos1 pos2 Nodes connected.
In order to take advantage of the available APS features, the ONS 15190 must be correctly connected to devices that support APS. You should configure any such devices (for example, GSR, ADM) appropriately, so that one connection is defined as the working link (W) and the other as the protection link (P). Also determine to which port each of these connections is physically connected in the ONS 15190.
ONS 15190 APS functionality is compliant with Bellcore GR-253 and ITU-T G.783, with the exception that unidirectional connections are not supported.
To configure a particular node to be defined for linear APS, use the command rconf node new as illustrated in the following example:
admin> rconf node new aps aaa l2.1 l4.1 oc12OC12 APS node aaa created.
In this example, the W link of node aaa is connected to L2.1, and the P link is connected to L4.1. By default, the node is set to be bidirectional, SONET, and nonrevertive, as can be displayed by executing the command rconf node show as follows:
admin> rconf node aaa show Node aaa: Type: APS W-Port: L2.1 P-Port: L4.1 APS Mode: Bidirectional Switching: Non-revertive Type: OC12 Mode: SONET Clock Source: Internal SD Threshold: 1e-6 SF Threshold: 1e-3 AIS Setting: Auto
Bidirectional nodes always use the same link (P or W). When a node is nonrevertive, control remains wherever it is as long as the link is functional. For revertive nodes, control always returns to the working link as soon as it is functional again.
|
Note Only bidirectional APS nodes are supported. |
To display the current status of the APS node named aaa, use the command l-aps aaa show status. This will indicate whether the working or protect link is active and whether there is a problem on either of the links.
admin> l-aps aaa show status APS_NODE:aaa sonet bidir nonRevertive active: W HIGHEST-REQUEST: NoRequest(Local) ch:0 KBYTES: RxK1:0 TxK1:0 RxK2:5 TxK2:5 REQUESTS(local): ALARMS:
In this example, the W link is currently active and the APS status is normal.
If there is a problem on the active link and control is switched to the protect link, a status message appears, as in the following example:
admin> l-aps aaa show status APS_NODE:aaa sonet bidir nonRevertive active: P HIGHEST-REQUEST: SignalFail(Local) ch:1 KBYTES: RxK1:21 TxK1:c1 RxK2:15 TxK2:15 REQUESTS(local): SignalFail(ch:1) ALARMS:
Here, due to a signal failure on the working link, the protect link took over and is now active. The node is defined as nonrevertive, so even when the working link is back up, the protect link will remain active as long as there are no problems.
You can connect an external analyzer to the ONS 15190 to analyze any node connected to the unit. Physically connect the analyzer to an open port and define it as a sniff node using the command: rconf node new sniff sniff-node port, where sniff-node is the name of the sniff node and port is the name of the port to be sniffed.
To analyze traffic on a node, execute the command rconf sniff connect sniff-node node port, where node is the node being analyzed and port indicates which data stream to monitor. Valid values of port follow:
The rx/tx indications are from the viewpoint of the node. For example, if b-rx is indicated for an SRP node, the stream going from the ONS 15190 to the B-side of the node will be monitored.
|
Note Only one node at any one time can be defined as a sniff node. |
The following node parameters can be set using the command rconf node set:
admin> rconf apply Configuration applied
|
Note If the active controller is reset before the configuration is applied, all configuration changes will be lost. |
Before executing the command rconf apply, it is possible to discard all current connection configuration changes by executing the command rconf discard.
To cascade two ONS 15190 units together, do the following:
Step 2 Execute the command autoconnect on the first ONS 15190 unit.
Step 3 Enter y when prompted to apply the configuration.
Step 4 Execute the command autoconnect on the second ONS 15190 unit.
Step 5 Enter y when prompted to apply the configuration.
The two units are now configured into the same ring. All nodes connected to either of the two units are now contained within this ring.
|
Note Set the trace-mode to normal when cascading multiple ONS 15190 units together. |
A message of the day (MOTD) is displayed prior to logging in to the system. To create a new MOTD, perform the following:
Step 2 Execute the command motd enable to enable the display of the MOTD before someone attempts to log in to the system.
The size of the MOTD file is limited to 1 KB.
In order to change your password, execute the command password. If you are logged in as admin, you can change either the admin or user password: password {admin | user}. You will be prompted for a new password for the respective username (user or admin). If you are logged in as user, you can only change the user password. If you type password without specifying admin or user, you will be prompted to change the password for the username through which you are presently logged in.
Some four-port OC-12c/STM-4 line cards are equipped with a laser power monitor. This feature allows you to verify the level of the laser as it enters the line card and the level of the laser as it is transmitted out. The input power is read from the hardware and has a resolution of 1.0 dBm. The output power is as read in the BOL (beginning of life) and has a resolution of 1.0 dBm.
To display these power measurements, execute the command port {all | port} show laser. Following is an example of the output from this command:
admin> port all show laser Port Type Output Power Input Power ---- ----- ------------ ----------------- L3.2 OC12 Laser ON Monitor not supported for port L4.1 OC12 -13.2 No Rx signal (Link Down) L4.2 OC12 -11.0 -24.0 L4.3 OC12 -12.4 higher than -18.0 L4.4 OC12 -12.0 lower than -32.0
If the port does not support the power laser monitor feature, this message for the port is displayed: Monitor not supported for port is given for the port.
The trace-mode option allows you to set the path trace message of the ONS 15190 to be transparent for nodes of a specific type. For example, if node A is connected to node B via the ONS 15190, in transparent mode, the path trace message transmitted by B will be that received by A and not that of the ONS 15190. In normal mode, the ONS 15190 transmits its own path trace message to each connected node. By default, SRP and raw nodes are set to normal trace-mode and pos (APS), and sniff nodes are set to transparent trace-mode.
To enable or disable transparent path trace, use this command:
system set trace-mode {pos | raw | sniff | srp } {normal | transparent}
|
Note If fiber loops are present on the system, the path trace mode must be set to normal for SRP nodes in order for features such as autotracker, autoconnect, and autodetect to function correctly. |
The autotracker option automatically tracks a node even if it is moved from one port to another. The autotracker is by default disabled. When enabled and nodes are removed from the system, traps are sent to the control panel to indicate the changes. To enable the autotracker option, use the following command:
rconf node node set autotrack {on | off}
If you are upgrading from a release of the software below release 2.0, follow the upgrade procedure in the section "Upgrade to Release 2.x from Release 1.x". If you are upgrading from release 2.0 or higher, follow the upgrade procedure in the section "Upgrade from Release 2.x".
|
Note Downtime due to the software upgrade will be approximately 1 minute due to an update in the firmware. |
|
Note Due to changes in the database made in newer releases, it is not possible, following an upgrade, to revert to earlier versions of the system configuration. For this reason, you are advised to save the current configuration on your system before upgrading. Then if you experience a problem with the new version, you will be able to revert to the previous software revision and to reload the old configuration. To save the configuration, execute the command tftp put ip-address filename conf, where ip-address is the IP address of the TFTP server where you are saving the configuration file, and filename is the filename of the configuration file. |
|
Note Upgrades to version 2.5 will discard all sniff connections; convert all unidirectional APS nodes to bidirectional nodes; and discard all low level (raw) configurations. |
To update the software on your ONS 15190 to release 2.x from release 1.x, do the following:
Step 2 Download the new software image file into the ONS 15190. You need the TFTP server IP address where the file is located, as well as the name of the file. For example:
admin> tftp get 192.168.10.27 ver25 image Retrieving 192.168.10.27:ver1028... 2.18MB Done. Release : 2.5 Created by: Cisco Systems Created on: Tue Feb 01 01:21:56 2000 Are you sure? y Storing image ...100%. Validating image Done. Updating image information (might take a while) Done. Synchronizing image... waiting for standby controller to save image information.... ........image synchronized OK done
In this example, the TFTP server IP address is 192.168.10.27, and the remote file name of the software update is ver2.0. When prompted for the version to be downloaded, enter y to continue with the download. When the download is complete, the file is stored within the Flash memory of both controller cards of the ONS 15190, but is not the currently running version of the software.
Step 3 To run the newer version of the software, you must perform a system reset. This reset may be done via the management software (as in the following example) or physically.
admin> sys reset Controller will be reset. Are you sure? y bye User Name: Password: admin>
When the system is reset, communication will be lost to the controller. If you are connected via RS-232, notification of the lost communication is displayed on the screen; if you are connected via telnet, the connection will just stop functioning. You will need to log into the system again.
When the system reboots, the now active controller (which was previously the standby controller) will still be running the old software version. However, the standby controller will be running the new software version. If you perform the command system show info, you will see that the old software version is currently running. For example:
admin> system show info System uptime: 0:08:02.363 Name: ONS 15190 Description: Lab at Cisco Systems Location: Contact: Running image: Release: 1.0.23 Created on: Wed Jan 19 21:14:46 2000 Created by: Cisco Systems Length: 2282376 Signature: 0xEF2BE4F6 Software version: Build 23 Software built on: Jan 19 2000, 21:13:45 Bootstrap version: 3.0 Stored image: Release: 2.5 Created on: Tue Feb 01 01:21:56 2000 Created by: Cisco Systems Length: 2290824 Signature: 0x4E034E21
Note that the stored release is version 2.5, but the current running software release is only version 1.0.23.
Step 4 In order to complete the procedure so that the new version will be running on the active controller card, you must perform a system reset once again. This reset will transfer control back to the original active controller which is already running the new version. The standby controller will now be reset to the new version as well. Once again, communication to the controller will be lost as shown in the following example:
admin> sys reset Controller will be reset. Are you sure? y bye Active controller has been changed please re login User Name: Password: admin>
Step 5 When you log back in to the system, verify that the new version is running with the command sys show info. In this example, the running release is the version that was downloaded: version 2.5.
admin> system show info System uptime: 1:39:52.399 System time: THU MAY 18 17:30:58 2000 Name: Description: Location: Contact: Running image: Release: 2.5 Created on: Wed May 03 20:09:48 2000 Created by: Cisco Systems Length: 3053739 Signature: 0x1E9BA6E0 Software version: 2.5.11 Software created on: May 3 2000, 20:09:01 Bootstrap version: 3.0
The software download procedure is now successfully completed.
To update your ONS 15190 with a new version of software after version 2.x has already be installed, do the following:
admin> tftp get 192.168.10.185 ver25 image Retrieving 192.168.10.185:ver2.0... 2.91MB Done. Release : 2.5 Created by: Cisco Systems Created on: Mon May 01 20:55:40 2000 Are you sure? y Storing image ...100%. Updating image information (might take a while) Done. synchronizing Image OK
In this example, the TFTP server IP address is 192.168.10.185, and the remote filename of the software update is ver25. When prompted with the version to be saved, enter y to continue with the process. After the file is downloaded, it is stored within the Flash memory of both controller cards of the ONS 15190. A reset is performed automatically to the standby controller card (for example, C2) such that the new software version will be up and running on the standby controller, but not on the active controller (for example, C1).
Step 2 You will be prompted to reset the active controller (C1) in order to begin running the new software version. Enter y to continue. Control will be transferred to the previous standby controller (C2) that is already running the new software, and C1 will be reset with the new software as well.
Changes will take affect only after controller reset Do you want to reset now? y resetting...
When the system is reset, communication will be lost to the controller. If you are connected via RS-232C, notification of the lost communication is displayed on the screen; if you are connected via telnet, the connection will just stop functioning. You will need to log into the system again.
The system will now be running the new software version. If you perform the command system show info, you will see that the new software version is currently running.
admin> system show info System uptime: 0:26:32.053 System time: 0:26:32.055 Name: Description: Location: Contact: Running image: Release: 2.5 Created on: Mon May 01 20:55:40 2000 Created by: Cisco Systems Length: 3053611 Signature: 0xC55D7EFE Software version: 2.5.11 Software created on: May 1 2000, 20:48:11 Bootstrap version: 3.0
The software download procedure is now successfully completed.
If you must revert to a previous version of the software, do the following:
admin> tftp get 192.168.10.27 ver20 image
In this example, the TFTP server IP address is 192.168.10.27, and the remote filename of the software update is ver20. When prompted with the version to be downloaded, enter y to continue with the download. You must follow the instructions for installing the particular software version that you are downloading.
Step 2 When the image is downloaded and running on your system, you must either download a previously saved version of the configuration file, or execute the command system set factory default. The factory default will provide a blank configuration for which you to begin defining your own configuration definitions.
To download a previously saved version of the configuration file, execute the command tftp get ip fname conf, where ip is the IP address where you have saved the configuration file, and fname is the name of the file.
Displaying system information is described in the following sections:
To display the running configuration on the box, use the command rconf show applied.
admin> rconf show applied Applied connection configuration: Sniff configuration: Sniffer Port Sniffed node Port -------------------- ----- -------------------- ---------- No sniffer nodes. POS connections: Node IP Address Ports Type Other -------------- ------------ ----------- ---- ---------------- 12000_left-2 11.1.1.2 L5.1 OC12 12000_Right-2 11.1.1.1 L7.1 OC12 Ring configuration (nodes in order of outer ring): Ring Name Nodes IP Address A-Port B-Port Type Other ---------- -------------- --------------- ------ ------ ---- ring1 12000_left 10.1.1.2 L1.2 L1.1 OC12 12000_Right 10.1.1.1 L4.1 L2.1 OC12 7200_center 10.1.1.5 L4.2 L8.1 OC12 7200_left 10.1.1.4 L5.2 L6.1 OC12
If you are in the process of defining a new configuration and want to view it even though it has not been applied yet, use the command rconf show current. If you have made no changes to the running configuration, the current and applied configurations will be identical.
To verify that traffic is flowing properly through the ONS 15190, use the command port all show pos total {bytes | frames | errors}.
admin> port all show pos total frames POS accumulated frames statistics: Port RX Frames TX Frames ---------- ------------------------ ---------------------------- L1.1 791,141,661 922,778,031 L1.2 793,961,106 795,007,415 L2.1 2,850,705,194 5,004,929,139 L2.2 794,423,993 795,574,350 L3.1 791,460,612 790,881,477 L3.2 795,417,207 793,966,035 L4.1 2,850,705,193 5,004,929,139 L4.2 2,088,166,454 547,246,894 L6.1 5,004,929,150 2,850,705,205 L6.2 547,246,904 2,088,166,483 L7.1 790,861,006 1,556,551,265 L7.2 5,004,867,415 2,850,065,459 L8.1 791,523,330 791,129,489 L8.2 795,574,406 794,424,048
The number of bytes or frames being transmitted and received by the various ports is displayed.
To display information concerning individual ports, use the command port. To use the this command, specify the name of the port (for example, L1.1, L8.4) or all ports, and the desired option. The following example shows the status of all ports:
admin> port all show status Port State Type Link Side AIS Conf Cur AIS Other ---------- ------ -------- ---- ---- -------- ------- ----- L1.1 Oper OC12 Up A Never L1.2 Oper OC12 Up A Never L3.1 Oper OC12 Up B Never L3.2 Oper OC12 Up B Never L4.1 Oper OC12 Down Never L4.2 Oper OC12 Up A Never L5.1 Oper OC12 Up B Never L5.2 Oper OC12 Up A Never L7.1 Oper OC12 Up B Never L7.2 Oper OC12 Up A Never L8.1 Oper OC12 Down Never L8.2 Oper OC12 Up B Never
|
Note The port all show commands only display ports that are physically present in the system. |
All configuration information is retained by the node and not the particular port. To change any node settings, use the command rconf node set. If the node is moved to a different port, the settings move with the node.
Use the card command to display or alter information about a specific line or switch card. The following example illustrates the status of card L1:
admin> card l1 show status Line Card 1: Subtype: Single Mode IR SC OC12c/STM4 SRP line card w/2 ports # of ports: 2 State: Operational Catalog number: OC12/STM4-SM-IR-SRP Serial number: 1020-012 Board version: A4 Temperature Status: Normal Temperature 1: 32.5 degC Temperature 2: 28.0 degC
To reset the card, use the command card x reset, where x is the identifier of the card you want to reset (C1, C2, L1 to L8 or S1 to S5).
Descriptions of typical problems and what to do when they are encountered are presented in the following sections:
Warning: Sides A of both node1 and node2 are attached to the same line card (L1).
Explanation A two-port line card (for example, L1) carries two A (Transmit Outer/Receive Inner) or two B (Receive Outer/Transmit Inner) connections, and one of the following commands was executed: rconf show apply, autoconnect, rconf node autodetect.
Action Node1 and node2 are the names of the nodes. It is recommended that you physically change the connections so that a line card has only one A and one B connection in order to allow better system resilience. However, even if you do not change the connections, the ring will still be functional.
|
Note This error message is only relevant to two-port line cards. |
Side A of node node-name was detected on multiple ports L1.1, L2.2, ignoring.
Explanation The side of an SRP node is defined as being on two different ports.
Action The multiple ports are listed in the error message. Determine the correct connection and correct the definition. You can also receive this message if the path trace messages are displayed incorrectly. Verify that you are in normal mode by executing the command system set trace-mode srp normal.
Node node-name was detected on multiple ports L1.1, L2.1, ignoring.
Explanation The side of a PoS node is defined as being on two different ports.
Action The multiple ports are listed. You should determine the correct connection and correct the definition. You may receive this message if the path trace messages are not being displayed correctly. Verify that you are in normal mode by executing the command system set trace-mode pos normal.
Node NODE is connected only to port L1.1.
Explanation SRP nodes must be connected to two ONS 15190 ports. In this case, only one port is detected.
Action Connect both interfaces of the node to the ONS 15190. If the node is actually a combination of several nodes, it must be defined manually. Also verify that the speed of all ports corresponds correctly with the speed of the node: either OC-12c/STM-4 or OC-48c/STM-16.
Discarding the following nodes due to identical IP address xxx.xxx.xx.xxx. SRP/POS node node connected to port L1.1 L2.2
Explanation A single IP address was detected for multiple nodes.
Action A separate message is displayed for each node detected with the stated IP address. Reconfigure the nodes to have different IP addresses.
Node node-name was not detected, discarding.
Discarding pos connection of node node1 to node node2. Discarding sniff connection of sniffer node node1 to sniffed node node2.
Explanation One of the commands autoconnect or rconf node autodetect was executed, and a previously detected node was not now detected. If the node is a pos or sniff node, the error message also indicates that it will be discarded.
Action Node, node1, and node2 are the node names. If this node is still connected, verify that the connections are secure.
Discarding user node node1 due to conflict with detected node node2.
Explanation There is a conflict between a user-defined node and an automatically detected node.
Action Verify the node definitions and connections.
Detected duplicated node name node1, resolving second node name to node2.
Explanation Multiple nodes are detected with the same name.
Action In this case, one of the nodes node2 is automatically renamed to node2.
ERROR: More than one sniff connection exists.
Explanation Two or more sniff connections were defined using the command rconf sniff connect.
Action Disconnect multiple sniff connections. Only one sniff connection can be defined at any one time.
To specify a session timeout value for the telnet session, use the command system set session timeout value, where a value of 0 corresponds to never.
If you forget your password, perform the following procedure to return the password value to its default:
Step 2 Log in from the Console RS-232C port (as either user or admin).
Step 3 Use the string !PeNtA$(* as your password.
At this point, both admin and user passwords will be reset to their default values. For login information, see the section "Configuring the Network Parameters" in this chapter.
Posted: Mon Sep 25 05:55:19 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.