|
|
Table Of Contents
Listing Cisco IOS Commands and Syntax
Before You Begin
This chapter provides basic information about the Cisco ONS 15540 ESPx. This chapter includes the following topics:
•
About Cisco IOS Command Modes
•
About the CLI
You can configure the Cisco ONS 15540 ESPx from the CLI (command-line interface) that runs on the system console or terminal, or by using remote access.
To use the CLI, your terminal must be connected to the Cisco ONS 15540 ESPx through the console port or one of the TTY lines. By default, the terminal is configured to a basic configuration, which should work for most terminal sessions.
About Cisco IOS Command Modes
The Cisco IOS user interface is divided into many different modes. The commands available to you depend on which mode you are currently in. To get a list of the commands available in a given mode, type a question mark (?) at the system prompt.
When you start a session on the system, you begin in user mode, also called EXEC mode. Only a limited subset of the commands are available in EXEC mode. To have access to all commands, you must enter privileged EXEC mode. Normally, you must type in a password to access privileged EXEC mode. From privileged mode, you can type in any EXEC command or access global configuration mode. Most of the EXEC commands are one-time commands, such as show commands, which show the current configuration status, and clear commands, which clear counters or interfaces. The EXEC commands are not saved across system reboots or across processor switchovers.
You can monitor and control the standby processor with commands entered on the active processor. A subset of EXEC and privileged EXEC commands are available through the standby processor console.
Note
The configuration modes allow you to make changes to the running configuration. If you later save the configuration, these commands are stored across system reboots. You must start at global configuration mode. From global configuration mode, you can enter interface configuration mode, subinterface configuration mode, and a variety submodes.
ROM (read-only memory) monitor mode is a separate mode used when the system cannot boot properly. For example, your system or access server might enter ROM monitor mode if it does not find a valid system image when it is booting, or if its configuration file is corrupted at startup.
Table 2-1 lists and describes the most commonly used modes, how to enter the modes, and the resulting system prompts. The system prompt helps you identify which mode you are in and, therefore, which commands are available to you.
Table 2-1 Frequently Used IOS Command Modes
User EXEC
To connect to remote devices, change terminal settings on a temporary basis, perform basic tests, and display system information.
Log in.
Switch>Privileged EXEC (Enable)
To set operating parameters. The privileged command set includes the commands in user EXEC mode, as well as the configure command. Use this command to access the other command modes.
From the user EXEC mode, enter the enable command and the enable password.
Switch#Global configuration
To configure features that affect the system as a whole.
From the privileged EXEC mode, enter the configure terminal command.
Switch(config)#Interface configuration
To enable features for a particular interface. Interface commands enable or modify the operation of a port.
From global configuration mode, enter the interface type location command.
For example, enter
interface fastethernet 0Switch(config-if)#Line configuration
To configure the console port or VTY line from the directly connected console or the virtual terminal used with Telnet.
From global configuration mode, enter the line console 0 command to configure the console port, or the line vty line-number command to configure a VTY line.
Switch(config-line)#Redundancy configuration
To configure system redundancy.
From global configuration mode, enter the redundancy command.
Switch(config-red)#APS1 configuration
To configure APS redundancy features.
From redundancy configuration mode, enter the associate group command.
Switch(config-aps)#Threshold list configuration
To configure alarm threshold list attributes and thresholds.
From the global configuration mode, enter the threshold-list command.
Switch(config-t-list)#Threshold configuration
To configure alarm threshold attributes.
From threshold list configuration mode, enter the threshold command.
Switch(config-threshold)#
1 Automatic Protection Switching
The Cisco IOS command interpreter, called the EXEC, interprets and executes the commands you enter. You can abbreviate commands and keywords by entering just enough characters to make the command unique from other commands. For example, you can abbreviate the show command to sh and the configure terminal command to config t.
When you type exit, the CLI backs out one command mode level. In general, typing exit returns you to global configuration mode. To exit configuration mode completely and return to privileged EXEC mode, press Ctrl-Z or end.
Listing Cisco IOS Commands and Syntax
In any command mode, you can get a list of available commands by entering a question mark (?).
Switch> ?To obtain a list of commands that begin with a particular character sequence, type in those characters followed immediately by the question mark (?). Do not include a space. This form of help is called word help, because it lists the words for you.
Switch# c?calendar cd clear clock configureconnect copyTo list keywords or arguments, enter a question mark in place of a keyword or argument. Include a space before the question mark. This form of help is called command syntax help, because it reminds you which keywords or arguments are applicable based on the command, keywords, and arguments you have already entered.
Switch# configure ?memory Configure from NV memorynetwork Configure from a TFTP network hostoverwrite-network Overwrite NV memory from TFTP network hostterminal Configure from the terminal<cr>To redisplay a command you previously entered, press the Up-arrow key. You can continue to press the Up-arrow key to see more previously issued commands.
Tips
You can press Ctrl-Z or end in any mode to immediately return to privileged EXEC (enable) mode, instead of entering exit, which returns you to the previous mode.
Interface Naming Conventions
The Cisco ONS 15540 ESPx has three types of motherboards, the line card motherboard, the 10-GE motherboard, and the mux/demux motherboard. Each line card motherboard can have up to four transponder modules. Each transponder module has two interfaces: an external client side interface and an internal trunk side interface. The client side interface connects to client equipment. The trunk side interface connects to a mux/demux module in a mux/demux motherboard. The interfaces of each mux/demux module connect to a pair of fibers, one for the receive direction and one for the transmit direction. The Cisco ONS 15540 ESPx CLI supports the following interface types:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Figure 2-1 shows the interface relationships on the Cisco ONS 15540 ESPx for splitter protected line card motherboards with transparent transponder modules and mux/demux motherboards with mux/demux modules and the OSC.
Figure 2-1 Cisco ONS 15540 ESPx Interface Model with Splitter Protection
Figure 2-2 shows the interface relationship on the Cisco ONS 15540 ESPx for unprotected line card motherboards with transparent transponder modules and mux/demux motherboards with mux/demux modules and the OSC.
Figure 2-2 Cisco ONS 15540 ESPx Interface Model with Line Card Protection
Tengigethernetphy Interfaces
The tengigethernetphy interfaces are the client side interfaces of the 10-GE transponder modules. This uncolored interface carries 10-GE physical layer signals. It does not terminate layer 2 or layer 3 protocol operations.
The naming convention for the tengigethernetphy interfaces on the 10-GE transponder module is as follows:
tengigethernetphy slot/subcard/port
Transparent Interfaces
The transparent interfaces are the client side interfaces on the transponder modules. The interface does not terminate the protocol, hence the term transparent. Also, transparent applies to transparency with regard to networking protocols. The transparent interface connects to the wave interface on the ITU side of the transponder module (see Figure 2-1).
The naming convention for the client side interfaces on the transponder module is as follows:
transparent slot/subcard/port
Because the client side of a transponder module has only one port, the port number is always 0. For example, the client side interface identifier for a transponder module in subcard position 2 in slot 4 is transparent 4/2/0.
Wave Interfaces
The wave interface is the specific wavelength generated by a transponder module. The wave interface electrically connects to the client side transparent interface and optically connects to two wavepatch interfaces on a splitter protected line card motherboard (see Figure 2-1), or to one wavepatch interface on an unprotected line card motherboard (see Figure 2-2).
The naming convention for wave interfaces is as follows:
wave slot/subcard
Waveethernetphy Interfaces
The waveethernetphy interface is a colored interface that carries 2.5-Gbps or 10-Gbps Ethernet physical layer signals. This interface resides on the same card as the corresponding uncolored interface. It does not terminate Layer 2 or Layer 3 protocol operations.
The naming convention for the waveethernetphy interfaces on the 10-GE transponder module is as follows:
waveethernetphy slot/subcard
Wavepatch Interfaces
The wavepatch interface is the interface on the line card motherboard between the transponder modules and the mux/demux modules. The wave interfaces on the ITU side of the transponder modules connect to the wavepatch interfaces, which send the signal to the front panel of the line card motherboard. From the front panel connector, the wavepatch interface cross connects to the filter interface connector on a mux/demux module or a mux/demux motherboard, either directly or through the cross connect panel.
A splitter protected line card motherboard has two wavepatch interfaces for each subcard position and two MTP connectors for the wavepatch interfaces on its front panel. (See Figure 2-1.)
An unprotected line card motherboard has only one wavepatch interface per subcard position and only one MTP connector for the wavepatch interfaces on its front panel. (See Figure 2-2.)
The wavepatch interface operational state reflects the operational state of the corresponding wave interface. If the wave interfaces are operationally down, the corresponding wavepatch interfaces are operationally down. Conversely, if the wave interfaces are operationally up, then the wavepatch interfaces are up. However, the administrative states of the wave and wavepatch interfaces are independently tracked.
The naming convention for wavepatch interfaces is as follows:
wavepatch slot/subcard/port
On a splitter protected motherboard with two MTP connectors, the upper MTP connector on the front panel supports wavepatch slot/subcard/0 interfaces and the lower MTP connector supports the wavepatch slot/subcard/1 interfaces. On an unprotected motherboard, the MTP connector supports wavepatch slot/subcard/0 interfaces.
Filter Interfaces
Each filter interface corresponds to an individual wavelength filter on the front panel of a mux/demux module. The filter interface cross connects a wavepatch interface on a line card motherboard to a wdm interface on the same mux/demux module (see Figure 2-1). This cross connection can be a direct connection between the line card motherboard and the mux/demux module or the mux/demux motherboard, or it can be a connection through the cross connect panel.
The naming convention for filter interfaces is as follows:
filter slot/subcard/port
The port numbers are 0 through 3 for 4-channel mux/demux modules, 0 through 7 for 8-channel mux/demux modules, and 0 through 31 for 32-channel mux/demux modules.
Wdm Interfaces
The wdm interface is the interface on the mux/demux module that receives the DWDM signal containing wavelengths to be dropped, or transmits the DWDM signal with added wavelengths. It represent the pairs of fibers (Tx and Rx) coming out of a mux/demux module. The wdm interface connects either to a wdm interface on another network node or, in the case of an add/drop mux/demux module, to a thru interface on another add/drop mux/demux module in the same slot (see Figure 2-1). The wdm interface can also connect to a thru interface on another shelf in a multiple shelf node.
The naming convention for wdm interfaces is as follows:
wdm slot/subcard
Thru Interfaces
The thru interface is the interface on the add/drop mux/demux module that sends the DWDM signal to, or receives it from, another add/drop mux/demux module without altering it. It represents the pairs of fibers (Tx and Rx) coming out of an add/drop mux/demux module. The thru interface connects the wdm or thru interface on another mux/demux module, either on the same slot or the other slot. The thru interface can also connect to a wdm interface on another shelf in a multiple shelf node.
The naming convention for thru interfaces is as follows:
thru slot/subcard
Wdmrelay Interfaces
The wdmrelay interface on a PSM (protection switch module) is a passive interface that represents a pair of fibers and connects the PSM to the wdm interface on a mux/demux module.
The naming convention for wdmrelay interfaces is as follows:
wdmrelay slot/subcard/port
Wdmsplit Interfaces
The wdmsplit interface on a PSM represents a pair of fibers and connects the trunk fiber. The PSM has two wdmsplit interfaces, one for the west direction and one for the east.
The naming convention for wdmsplit interfaces is as follows:
wdmsplit slot/subcard/port
The west interface is wdmsplit slot/subcard/0 and the east interface is wdmsplit slot/subcard/1.
OSC Interfaces
The optional OSC provides management communications among the Cisco ONS 15540 ESPx systems in a network. The OSC is separate from the 32 data channels. The shelf can have two OSCs, one per mux/demux slot. Each OSC has two interfaces: one connection on the mux/demux motherboard and one on the mux/demux module that sends and receives the OSC wavelength on the network trunk (see Figure 2-1). Each interface represents the pairs of fibers (Tx and Rx).
The naming convention for the OSC interface on a mux/demux motherboard is as follows:
wave slot
The naming convention for the OSC interface on a mux/demux module is as follows:
oscfilter slot/subcard
The subcard position number for an oscfilter interface on a terminal mux/demux module is either 0 or 2 because the module occupies two subcard positions in the mux/demux motherboard.
Note
Ethernetdcc Interfaces
The ethernetdcc interfaces on a 10-GE transponder module provide the communication path for the in-band message channel OAM messages between nodes in the network.
The naming convention for ethernetdcc interfaces is as follows:
ethernetdcc slot/subcard/port
The 10-GE transponder module has two ethernetdcc interfaces, one on the trunk side and one on the client side. The trunk side ethernetdcc interface is always visible in show command output when a 10-GE module is present on the system. The client side ethernetdcc interface is only visible in show command output when the in-band message channel is enabled on the interface.
NME Interfaces
Each processor card has a Fast Ethernet interface, called an NME (network management Ethernet), for network management purposes. The NME interface on the active processor card is named fastethernet 0 and the NME interface on the standby processor card is named fastethernet-sby 0.
Each NME interface has a unique MAC address. Also, you must configure each NME interface with a unique IP address. After a processor switchover, when standby processor card takes over as active, the IP and MAC addresses of the standby processor card are reinitialized to those of the active processor card.
Note
Auxiliary Port Interfaces
Each processor card has an auxiliary port interface. You can use this interface for modem connections. This interface is named aux 0.
Note
Configuration Overview
To configure your Cisco ONS 15540 ESPx systems and network, perform the following steps:
Step 1
For detailed information about the hardware components, refer to the
Cisco ONS 15540 ESPx Hardware Installation Guide. For detailed information on system planning and design, refer to the Cisco ONS 15540 ESPx Planning Guide.Step 2
For detailed information on hardware configuration rules, refer to the
Cisco ONS 15540 ESPx Planning Guide.Step 3
For detailed information on configuring the NME port, see Chapter 3, "Initial Configuration."
Step 4
For detailed information on cross connecting modules, refer to the
Cisco ONS 15540 ESPx Planning Guide. For information on configuring patch connections with the CLI, see the "Configuring Patch Connections" section on page 4-20.Step 5
For detailed information on cabling between mux/demux modules, refer to the
Cisco ONS 15540 ESPx Planning Guide. For information on configuring patch connections with the CLI, see the "Configuring Patch Connections" section on page 4-20.Step 6
For more information about the show patch and show connect commands, see the "Displaying Patch Connections" section on page 4-23 and the "About Cross Connections" section on page 4-24.
Step 7
For detailed information on interface configuration, see Chapter 4, "Configuring 2.5-Gbps Transponder Module Interfaces and Patch Connections."
Step 8
For detailed information on configuring APS, see Chapter 7, "Configuring APS."
Step 9
For detailed information on processor card redundancy, see the "About Processor Card Redundancy" section on page 3-11.
Step 10
For detailed information on configuring IP connectivity on the OFC, see the "Configuring IP on the OSC" section on page 11-8.
Step 11
For detailed information on network monitoring, see Chapter 11, "Monitoring Your Network Topology".
Posted: Thu Jun 3 14:32:56 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
