|
|
To continue your PA-A3 OC-12 installation, you must configure the ATM interface. This chapter contains the following sections:
You modify the configuration of your router through the software command interpreter called the EXEC (also called enable mode). You must enter the privileged level of the EXEC command interpreter with the enable command before you can use the configure command to configure a new interface or change the existing configuration of an interface. The system prompts you for a password if one has been set.
The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>). At the console terminal, use the following procedure to enter the privileged level:
Router> enable
Password:
Step 2 Enter the password (the password is case sensitive). For security purposes, the password is not displayed.
When you enter the correct password, the system displays the privileged-level system prompt (#):
Router#
To configure the new interface, proceed to the "Configuring the Interface" section.
After you verify that the new PA-A3 OC-12 is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interface. Have the following information available:
If you installed a new PA-A3 OC-12 or if you want to change the configuration of an existing interface, you must enter configuration mode to configure the new interface. If you replaced a PA-A3 OC-12 that was previously configured, the system recognizes the new interface and brings it up in its existing configuration.
For a summary of the configuration options available and instructions for configuring the interface on a PA-A3 OC-12, refer to the appropriate configuration publications listed in the "Related Documentation" section.
You execute configuration commands from the privileged level of the EXEC command interpreter, which usually requires password access. Contact your system administrator, if necessary, to obtain password access. (See the "Using the EXEC Command Interpreter" section for an explanation of the privileged level of the EXEC.)
This section contains the following subsections:
Before you remove an interface that you will not replace, or replace port adapters, use the shutdown command to shut down (disable) the interface to prevent anomalies when you reinstall the new or reconfigured port adapter. When you shut down an interface, it is designated administratively down in the show command displays.
Follow these steps to shut down an interface:
Step 2 At the privileged-level prompt, enter configuration mode and specify that the console terminal is the source of the configuration subcommands, as follows:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 3 Shut down the interface by entering the interface atm subcommand (followed by the interface address of the interface), and then enter the shutdown command. Table 4-1 shows the command syntax.
When you have finished, press Ctrl-Z---hold down the Control key while you press Z---or enter end or exit to exit configuration mode and return to the EXEC command interpreter.
| Platform | Command | Example |
|---|---|---|
VIP4 in Cisco 7500 series routers | interface, followed by the type (atm) and slot/port adapter/port (interface-processor-slot-number | The example is for interface 0 on a port adapter in port adapter slot 0 of a VIP4 installed Router(config-if)# interface atm 1/0/0 Router(config-if)# shutdown Ctrl-Z Router# |
Step 4 Write the new configuration to NVRAM as follows:
Router# copy running-config startup-config [OK] Router#
The system displays an OK message when the configuration has been stored in NVRAM.
Step 5 Verify that the new interface is now in the correct state (shut down) using the
show interfaces command (followed by the interface type and interface address of the interface) to display the specific interface. Table 4-2 provides an example.
| Platform | Command | Example |
|---|---|---|
VIP4 in Cisco 7500 series routers | show interfaces atm, followed by slot/port adapter/port (interface-processor-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 0 of a VIP4 in interface processor slot 1. Router# show interfaces atm 1/0/0 atm 1/0/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Step 6 Reenable the interface by doing the following:
a. Repeat Step 3 to reenable an interface. Substitute the no shutdown command for the shutdown command.
b. Repeat Step 4 to write the new configuration to memory. Use the copy running-config startup-config command.
c. Repeat Step 5 to verify that the interface is are in the correct state. Use the show interfaces command followed by the interface type and interface address of the interface.
For complete descriptions of software configuration commands, refer to the publications listed in the "Related Documentation" section.
Following are instructions for a basic configuration: enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. For complete descriptions of configuration subcommands and the configuration options available for ATM interfaces, refer to the appropriate software documentation.
In the following procedure, press the Return key after each step unless otherwise noted. At any time you can exit the privileged level and return to the user level by entering disable at the prompt as follows:
Router# disable Router>
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 2 Specify the first interface to configure by entering the interface atm subcommand, followed by the interface address of the interface you plan to configure. Table 4-3 provides an example.
| Platform | Command | Example |
|---|---|---|
VIP4 in Cisco 7500 series routers | interface atm, followed by slot/port adapter/port (interface-processor-slot-number/ | The example is for the interface of a PA-A3 OC-12 on a VIP4 in interface processor slot 1. Router(config)# interface atm 1/0/0 Router(config-if)# |
Step 3 Assign an IP address and subnet mask to the interface (if IP routing is enabled on the system) by using the ip address subcommand, as in the following example:
Router(config-if)# ip address 10.0.0.0 10.255.255.255
Step 4 Add any additional configuration subcommands required to enable routing protocols and set the interface characteristics.
Step 5 Reenable the interface using the no shutdown command. (See the "Shutting Down an Interface" section.)
Step 6 After including all of the configuration subcommands to complete your configuration, press Ctrl-Z---hold down the Control key while you press Z---or enter end or exit to exit configuration mode and return to the EXEC command interpreter prompt.
Step 7 Write the new configuration to NVRAM as follows:
Router# copy running-config startup-config [OK] Router#
 |
Note If you are going to disconnect or reconfigure the ATM interface cable, use the shutdown command prior to this action. After reattaching the ATM interface cable, use the no shutdown command to bring up the ATM interface. |
This completes the procedure for creating a basic configuration.
To configure the PA-A3 OC-12 for OC12c/STM4c, use the atm sonet stm-4 command in interface configuration mode, as shown in the example below:
Router(config)# interface atm 1/0/0 Router(config-if)# atm sonet stm-4
A virtual circuit (VC) is a point-to-point connection between remote hosts and routers. A VC is established for each ATM end node with which the router communicates. The characteristics of the VC are established when the VC is created and include the following:
When you assign class of service to a VC for QoS management, the following default priority levels apply:
1. OAM and signaling (highest level)
2. nrt-VBR
3. UBR, ILMI (lowest level)
Each VC supports the following router functions:
By default, fast switching is enabled on the PA-A3 OC-12 interface. Switching features can be turned off with interface configuration commands. Optimum/flow/CEF switching must be explicitly enabled for the interface.
To use a permanent virtual circuit (PVC), you must configure the PVC in both the router and the ATM switch. PVCs remain active until the circuit is removed from either configuration.
When a PVC is configured, all of the configuration options are passed on to the PA-A3 OC-12. You can write these PVCs into nonvolatile RAM (NVRAM); they are used when the system image is reloaded.
Some ATM switches might have point-to-multipoint PVCs that do the equivalent of broadcasting. If a point-to-multipoint PVC exists, it can be used as the sole broadcast PVC for all multicast requests.
To configure a PVC, perform the tasks in the following sections. The first task is required; the other tasks are optional.
To create a PVC on the ATM interface and enter interface-ATM-VC configuration mode, use the pvc [name] vpi/vci [ilmi | qsaal | smds] command beginning in interface configuration mode.
|
Note After configuring the parameters for an ATM PVC, you must exit the interface-ATM-VC configuration mode in order to create the PVC and enable the settings. |
Once you specify a name for a PVC, you can reenter the interface-ATM-VC configuration mode by simply entering pvc name. Refer to the "ATM Commands" chapter of the Cisco IOS Wide-Area Networking Command Reference publication for more information on creating a PVC.
The ATM interface supports a static mapping scheme that identifies the network address of remote hosts or routers. This section describes how to map a PVC to an address.
To map a protocol address to a PVC, use the protocol protocol protocol-address [[no] broadcast]
command in interface-ATM-VC configuration mode.
|
Note If you enable or disable broadcasting directly on a PVC using the protocol command, this configuration will take precedence over any direct configuration using the broadcast command. |
To configure the ATM adaptation layer (AAL) and encapsulation type, use the encapsulation aal5encap
command beginning in interface-ATM-VC configuration mode.
For a list of AAL types and encapsulations supported for the aal-encap argument, refer to the encapsulation aal5 command in the "ATM Commands" chapter of the Cisco IOS Wide-Area Networking Command Reference publication. The global default is AAL5 with SNAP encapsulation.
The supported traffic parameters are part of the following service categories: unspecified bit rate (UBR), UBR+, variable bit rate non real-time (VBR-NRT), and real-time variable bit rate (VBR). Only one of these categories can be specified per PVC connection, so if a new one is entered, it will replace the existing one.
To configure PVC traffic parameters, use one of the following commands beginning in interface-ATM-VC configuration mode:
| Command | Purpose |
|---|---|
ubr output-pcr | Configure the unspecified bit rate (UBR). |
Configure the UBR and a minimum guaranteed rate. | |
vbr-nrt output-pcr output-scr output-mbs | Configure the variable bit rate-non real time (VBR-NRT) QoS. |
vbr-rt peak-rate average-rate burst | Configure the real-time variable bit rate (VBR). |
The -pcr and -mcr arguments are the peak cell rate and minimum cell rate, respectively. The -scr and -mbs arguments are the sustainable cell rate and maximum burst size, respectively.
You can optionally configure the PVC to generate end-to-end F5 OAM loopback cells to verify connectivity on the virtual circuit. The remote end must respond by echoing back such cells. If OAM response cells are missed (indicating the lack of connectivity), the PVC state goes down. If all the PVCs on a subinterface go down, the subinterface goes down.
To configure transmission of end-to-end F5 OAM cells on a PVC, use the following commands in interface-ATM-VC configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | oam-pvc [manage] frequency | Configure transmission of end-to-end F5 OAM loopback cells on a PVC, specify how often loopback cells should be sent, and optionally enable OAM management of the connection. |
Step 2 | oam retry up-count down-count retry-frequency | (Optional.) Specify OAM management parameters for verifying connectivity of a PVC connection. This command is only supported if OAM management is enabled. |
Use the up-count argument to specify the number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to change a PVC connection state to up. Use the down-count argument to specify the number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to tear down a PVC. Use the retry-frequency argument to specify the frequency (in seconds) with which end-to-end F5 OAM loopback cells should be transmitted when a change in up/down state is being verified. For example, if a PVC is up and a loopback cell response is not received after the frequency (in seconds) specified using the oam-pvc command, then loopback cells are sent at the retry-frequency to verify whether or not the PVC is down.
You can configure your router to automatically discover PVCs that are configured on an attached adjacent switch. The discovered PVCs and their traffic parameters are configured on an ATM main interface or subinterface that you specify. Your router receives the PVC parameter information using Interim Local Management Interface (ILMI).
To configure PVC discovery on an ATM interface, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
interface atm slot/port-adapter/0 | Specify the ATM interface using the appropriate format of the interface atm command. | |
Step 2 | pvc [name] 0/16 ilmi | Configure an ILMI PVC on the main interface. |
Step 3 | exit | Return to interface configuration mode. |
atm ilmi-pvc-discovery [subinterface] | Configure PVC discovery on the main interface and optionally specify that discovered PVCs will be assigned to a subinterface. | |
Step 5 | exit | Return to global configuration mode. |
interface atm slot/port-adapter/0[.subinterface-number {multipoint | point-to-point}] | Specify the ATM main interface or subinterface that discovered PVCs will be assigned to. | |
ip address ip-address mask | (Optional.) Specify the protocol address for the subinterface. |
Use the subinterface keyword in Step 4 if you want the discovered PVCs to reside on an ATM subinterface that you specify in Step 6. The discovered PVCs are assigned to the subinterface number that matches the VPI number of the discovered PVC. For example, if subinterface 2/0.1 is specified using the interface atm command in Step 6, then all discovered PVCs with a VPI value of 1 will be assigned to this subinterface. Repeat Step 6 and Step 7 if you want discovered PVCs to be assigned to more than one subinterface. If no subinterfaces are configured, discovered PVCs will be assigned to the main interface specified in Step 1.
Inverse Address Resolution Protocol (ARP) is enabled by default when you create a PVC using the pvc command. Once configured, a protocol mapping between an ATM PVC and a network address is learned dynamically as a result of the exchange of ATM Inverse ARP packets.
Inverse ARP is supported on PVCs running IP or IPX with no static map is configured. If a static map is configured, Inverse ARP will be disabled.
To enable Inverse ARP on an ATM PVC, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | interface atm slot/port-adapter/0[.subinterface-number {multipoint | point-to-point}] | Specify the ATM interface using the appropriate format of the interface atm command. |
Step 2 | pvc [name] vpi/vci | Specify an ATM PVC by name (optional) and VPI/VCI numbers. |
Step 3 | encapsulation aal5snap | Configure AAL5 LLC-SNAP encapsulation if it is not already configured. |
Step 4 | (Optional.) Adjust the Inverse ARP time period. |
When PVC discovery is enabled on an active PVC and the router terminates that PVC, the PVC will generate an ATM Inverse ARP request. This allows the PVC to resolve its own network addresses without configuring a static map.
Address mappings learned through Inverse ARP are aged out. However, mappings are refreshed periodically. This period is configurable using the inarp command, which has a default of 15 minutes.
You can also enable Inverse ARP using the protocol command. This is necessary only if you disabled Inverse ARP using the no protocol command. For more information about this command, refer to the "ATM Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference publication.
Figure 4-1 shows a fully meshed network. Fully meshed means that each network node has either a physical circuit or a virtual circuit connecting it to every other network node. The configurations for Routers A, B, and C follow. In this example, the routers are configured to use PVCs. The two map-list statements configured in Router A identify the ATM addresses of Routers B and C. The two map-list statements in Router B identify the ATM addresses of Routers A and C. The two map-list statements in Router C identify the ATM addresses of Routers A and B.
Router A
interface ATM4/0/0 ip address 172.21.168.1 255.255.255.0 no ip directed-broadcast pvc 0/32 protocol ip 172.21.168.2 broadcast encapsulation aal5snap pvc 0/33 protocol ip 172.21.168.3 broadcast encapsulation aal5snap
Router B
interface ATM2/0/0 ip address 172.21.168.2 255.255.255.0 no ip directed-broadcast pvc 0/32 protocol ip 172.21.168.1 broadcast encapsulation aal5snap pvc 0/34 protocol ip 172.21.168.3 broadcast encapsulation aal5snap
Router C
interface ATM1/0/0 ip address 172.21.168.3 255.255.255.0 no ip directed-broadcast pvc 0/33 protocol ip 172.21.168.1 broadcast encapsulation aal5snap pvc 0/34 protocol ip 172.21.168.2 broadcast encapsulation aal5snap
ATM switched virtual circuit (SVC) service operates much like X.25 SVC service, although ATM allows much higher throughput. Virtual circuits are created and released dynamically, providing user bandwidth on demand. This service requires a signaling protocol between the router and the switch.
The ATM signaling software provides a method of dynamically establishing, maintaining, and clearing ATM connections at the User-Network Interface (UNI). The ATM signaling software conforms to ATM Forum UNI 3.0 or ATM Forum UNI 3.1 depending on what version is selected by ILMI or configuration.
In UNI mode, the user is the router and the network is an ATM switch. This is an important distinction. The Cisco router does not perform ATM-level call routing. Instead, the ATM switch does the ATM call routing, and the router routes packets through the resulting circuit. The router is viewed as the user and the LAN interconnection device at the end of the circuit, and the ATM switch is viewed as the network.
Figure 4-2 illustrates the router position in a basic ATM environment. The router is used primarily to interconnect LANs through an ATM network. Workstation C connected directly to the destination ATM switch illustrates that you can connect not only routers to ATM switches, but also any computer with an ATM interface that conforms to the ATM Forum UNI specification.
You must complete the tasks in the following sections to use SVCs:
For further information on configuring the PA-A3 OC-12 for SVCs, see the Wide-Area Networking Configuration Guide publication.
In an SVC environment, you must configure a PVC for communication with the ILMI so the router can receive SNMP traps and new network prefixes. The recommended vpi and vci values for the ILMI PVC are 0 and 16, respectively. To create an ILMI PVC on an ATM main interface, use the pvc [name] 0/16 ilmi command in interface configuration mode.
|
Note This ILMI PVC can be set up only on an ATM main interface, not on ATM subinterfaces. |
Once you have configured an ILMI PVC, you can optionally enable the ILMI keepalive function by using the atm ilmi-keepalive [seconds] command in interface configuration mode.
No other configuration steps are required.
ILMI address registration for receipt of SNMP traps and new network prefixes is enabled by default. The ILMI keepalive function is disabled by default; when enabled, the default interval between keepalives is 3 seconds.
Unlike X.25 service, which uses in-band signaling (connection establishment done on the same circuit as data transfer), ATM uses out-of-band signaling. One dedicated PVC exists between the router and the ATM switch, over which all SVC call establishment and call termination requests flow. After the call is established, data transfer occurs over the SVC, from router to router. The signaling that accomplishes the call setup and teardown is called Layer 3 signaling or the Q.2931 protocol.
For out-of-band signaling, a signaling PVC must be configured before any SVCs can be set up. In Figure 4-3, a signaling PVC from the source router to the ATM switch is used to set up two SVCs. This is a fully meshed network; Workstations A, B, and C can all communicate with one other.
To configure the signaling PVC for all SVC connections, use the pvc [name] vpi/vci qsaal command in interface configuration mode.
|
Note This signaling PVC can be set up only on a major interface, not on the subinterfaces. |
The VPI and VCI values must be configured consistently with the local switch. The standard value of VPI is 0; the standard value of VCI is 5.
Every ATM interface involved with signaling must be configured with a network service access point (NSAP) address. The NSAP address is the ATM address of the interface and must be unique across the network.
To configure an NSAP address, complete the tasks described in one of the following sections:
If the switch is capable of delivering the NSAP address prefix to the router by using ILMI, and the router is configured with a PVC for communication with the switch through ILMI, you can configure the endstation ID (ESI) and selector fields using the atm esi-address command. The atm esi-address command allows you to configure the ATM address by entering the ESI (12 hexadecimal characters) and the selector byte (2 hexadecimal characters). The NSAP prefix (26 hexadecimal characters) is provided by the ATM switch.
To configure the router to get the NSAP prefix from the switch and use locally entered values for the remaining fields of the address, use the following commands beginning in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | pvc [name] 0/16 ilmi | Configure an ILMI PVC on an ATM main interface for communicating with the switch by using ILMI. |
Step 2 | exit | Return to interface configuration mode. |
Step 3 | Enter the ESI and selector fields of the NSAP address. |
The recommended vpi and vci values for the ILMI PVC are 0 and 16, respectively.
You can also specify a keepalive interval for the ILMI PVC. See the "Configuring Communication with the ILMI" section earlier in this chapter for more information.
When you configure the ATM NSAP address manually, you must enter the entire address in hexadecimal format because each digit entered represents a hexadecimal digit. To represent the complete NSAP address, you must enter 40 hexadecimal digits in the following format:
XX.XXXX.XX.XXXXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XX
|
Note All ATM NSAP addresses can be entered in the dotted hexadecimal format shown, which conforms to the UNI specification. The dotted method provides some validation that the address is a legal value. If you know your address format is correct, the dots may be omitted. |
Because the interface has no default NSAP address, you must configure the NSAP address for SVCs. To set the ATM interface's source NSAP address, use the atm nsap-address nsap-address command in interface configuration mode.
The atm nsap-address and atm esi-address commands are mutually exclusive. Configuring the router with the atm nsap-address command negates the atm esi-address setting, and vice versa. For information about using the atm esi-address command, see the preceding section, "Configuring the ESI and Selector Fields."
To create an SVC, use the following commands beginning in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Create an SVC and specify the destination NSAP address. | |
Step 2 | (Optional.) Configure the ATM adaptation layer (AAL) and encapsulation type. | |
Step 3 | Map a protocol address to an SVC. |
Once you specify a name for an SVC, you can reenter interface-ATM-VC configuration mode by simply entering the svc name command; you can remove an SVC configuration by entering the no svc name command.
For a list of AAL types and encapsulations supported for the aal-encap argument, refer to the encapsulation aal5 command in the "ATM Commands" chapter of the Cisco IOS Wide-Area Networking Command Reference publication. The default is AAL5 with SNAP encapsulation.
The following example is also a configuration for the fully meshed network shown in Figure 4-1, but one in which SVCs are used. PVC 1 is the signaling PVC.
Router A
interface ATM4/0/0 ip address 172.21.168.1 255.255.255.0 no ip directed-broadcast atm nsap-address 47.00908100000000105BFC1501.200000000001.00 pvc 0/5 qsaal svc nsap 47.00908100000000105BFC1501.200000000002.00 protocol ip 172.21.168.2 broadcast encapsulation aal5snap svc nsap 47.00908100000000105BFC1501.200000000003.00 protocol ip 172.21.168.3 broadcast encapsulation aal5snap
Router B
interface ATM2/0/0 ip address 172.21.168.2 255.255.255.0 no ip directed-broadcast atm nsap-address 47.00908100000000105BFC1501.200000000002.00 pvc 0/5 qsaal svc nsap 47.00908100000000105BFC1501.200000000001.00 protocol ip 172.21.168.1 broadcast encapsulation aal5snap svc nsap 47.00908100000000105BFC1501.200000000003.00 protocol ip 172.21.168.3 broadcast encapsulation aal5snap
Router C
interface ATM1/0/0 ip address 172.21.168.3 255.255.255.0 no ip directed-broadcast atm nsap-address 47.00908100000000105BFC1501.200000000003.00 pvc 0/5 qsaal svc nsap 47.00908100000000105BFC1501.200000000001.00 protocol ip 172.21.168.1 broadcast ncapsulation aal5snap svc nsap 47.00908100000000105BFC1501.200000000002.00 protocol ip 172.21.168.2 broadcast encapsulation aal5snap
Cisco implements both the ATM Address Resolution Protocol (ARP) server and ATM ARP client functions described in RFC 1577. RFC 1577 models an ATM network as a logical IP subnetwork on a LAN.
The tasks required to configure classical IP and ARP over ATM depend on whether there are SVCs or PVCs in the environment. For further information, refer to the Wide-Area Networking Configuration Guide.
You can customize the PA-A3 OC-12. The features you can customize have default values that probably suit your environment and need not be changed. However, you might need to enter configuration commands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. Perform the tasks in the following sections if you need to customize the PA-A3 OC-12:
Each ATM interface has a default maximum packet size or maximum transmission unit (MTU) size. On the PA-A3 OC-12, this number defaults to 4470 bytes, the range being 64 through 9188 bytes. To set the maximum MTU size, use the following command in interface configuration mode:
mtu bytes
This command is documented in the Configuration Fundamentals Command Reference publication.
To configure an ATM interface for local loopback (useful for checking that the PA-A3 OC-12 is working by looping the transmit data back to the receive data), use the following command:
loopback diagnostic
The no form of the command turns off local loopback.
To configure an ATM interface for external loopback (useful for checking that the PA-A3 OC-12 is working by looping the receive data back to the transmit data), use the following command:
loopback line
To configure an ATM interface for external loopback at the cell level, use the following command:
loopback cell
To configure an ATM interface for external loopback at the payload level, use the following command:
loopback payload
The no form of each command turns off external loopback.
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces, and use the ping and loopback commands to check connectivity. This section includes the following subsections:
Table 4-4 demonstrates how you can use the show commands to verify that the new interface is configured and operating correctly and that the PA-A3 OC-12 appears in it correctly. Sample displays of the output of selected show commands appear in the sections that follow. For complete command descriptions and examples, refer to the publications listed in the "Related Documentation" section.
|
Note The ouputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only. |
| Command | Function | Example |
|---|---|---|
show version or | Displays system hardware configuration, the number of each interface type installed, Cisco IOS software version, names and sources of configuration files, and boot images | Router# show version |
show controllers | Displays all the current interface processors and their interfaces | Router# show controllers |
show diag slot | Displays types of port adapters installed in your system and information about a specific port adapter slot, interface processor slot, or chassis slot | Router# show diag 2 |
show interfaces type interface-processor- | Displays status information about a specific type of interface (for example, ATM) on a VIP4 in a Cisco 7500 series router | Router# show interfaces atm 3/0/0 |
show protocols | Displays protocols configured for the entire system and for specific interfaces | Router# show protocols |
show running-config | Displays the running configuration file | Router# show running-config |
show startup-config | Displays the configuration stored in NVRAM | Router# show startup-config |
You can display the current state of the ATM network and connected virtual circuits. To show current virtual circuits and traffic information, perform the following tasks in EXEC mode. For information about EXEC mode, see the "Using the EXEC Command Interpreter" section.
| Command | Purpose |
|---|---|
show atm interface atm slot/0 | Display ATM-specific information about an ATM interface. |
show atm map | Display the configured list of ATM static maps to remote hosts on an ATM network. |
show atm traffic | Display information about global traffic to and from all ATM networks connected to the router. Display a list of counters of all ATM traffic on this router. |
show atm-vc [vcd] | Display ATM virtual circuit information about all PVCs and SVCs (or a specific virtual circuit). |
show sscop | Display SSCOP details for the ATM interface. |
show atm arp-server | Display ATM ARP server table. |
show atm ilmi | Display ATM ILMI information. |
If an interface is shut down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the interface is properly connected and terminated. If you still have problems bringing up the interface, contact a service representative for assistance. This section includes the following subsections:
Proceed to the "Using the ping Command to Verify Network Connectivity" section when you have finished using the show commands.
Display the configuration of the system hardware, the number of each interface type installed, the Cisco IOS software version, the names and sources of configuration files, and the boot images, using the show version (or show hardware) command.
|
Note The ouputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only. |
Following is an example of the show version command from a Cisco 7500 series router with the PA-A3 OC-12:
Router# show version Cisco Internetwork Operating System Software IOS (tm) RSP Software (RSP-PV-M), Version 12.0(19991214:220504) [den 160] Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Wed 12-Jan-00 15:42 by biff Image text-base:0x60010900, data-base:0x60C40000 ROM:System Bootstrap, Version 11.1(8)CA1, (fc1) Router uptime is 10 minutes System returned to ROM by reload at 15:05:17 UTC Sun Aug 15 1999 System image file is "slot0:rsp-pv-mz.cfg1-noABR-322_a1_0112" cisco RSP4 (R5000) processor with 65536K/2072K bytes of memory. R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache Last reset from power-on G.703/E1 software, Version 1.0. G.703/JT2 software, Version 1.0. X.25 software, Version 3.0.0. Chassis Interface. 1 EIP controller (6 Ethernet). 4 VIP2 R5K controllers (1 ATM)(3 POS). 1 VIP4 RM7000 controller (1 ATM). 6 Ethernet/IEEE 802.3 interface(s) 2 ATM network interface(s) 3 Packet over SONET network interface(s) 123K bytes of non-volatile configuration memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash PCMCIA card at slot 1 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). No slave installed in slot 7. Configuration register is 0x0
Display the types of port adapters installed in your system (and specific information about each) using the show diag slot command, where slot is the interface processor slot in a Cisco 7500 series router with a VIP4.
|
Note The ouputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only. |
Following is an example of the show diag slot command that shows a PA-A3 OC-12 in port adapter
slot 0 on a VIP4 in interface processor slot 4:
Router# show diag 4 Slot 4: Physical slot 4, ~physical slot 0xB, logical slot 4, CBus 0 Microcode Status 0x4 Master Enable, LED, WCS Loaded Board is analyzed Pending I/O Status:None EEPROM format version 1 VIP4 RM7000 controller, HW rev 2.01, board revision UNKNOWN Serial number:12610483 Part number:73-3143-02 Test history:0x00 RMA number:00-00-00 Flags:cisco 7000 board; 7500 compatible EEPROM contents (hex): 0x20:01 22 02 01 00 C0 6B B3 49 0C 47 02 00 00 00 00 0x30:02 4B 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 Slot database information: Flags:0x4 Insertion time:0x3028 (00:12:05 ago) Controller Memory Size:64 MBytes DRAM, 65536 KBytes SRAM PA Bay 0 Information: OC-12 ATM SMI Port Adaptor, 1 ports EEPROM format version 1 HW rev 2.00, Board revision 86 Serial number:12325404 Part number:73-3310-02 --Boot log begin-- Cisco Internetwork Operating System Software IOS (tm) VIP Software (SVIP-DW-M), Version 12.0(19991214:220504) [den 162] Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Wed 12-Jan-00 15:45 by biff Image text-base:0x600108E0, data-base:0x602A0000 --Boot log end--
For complete descriptions of interface subcommands and the configuration options available for VIP4 interfaces, refer to the publications listed in the "Related Documentation" section.
|
Note The ouputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only. |
Following is an example of the show interfaces command used with the VIP4. In this example, the single ATM interface is on a port adapter in port adapter slot 0 of a VIP4 in interface processor slot 4.
Router# show interfaces atm 4/0/0 ATM4/0/0 is up, line protocol is up Hardware is cyBus OC12 ATM PA, address is 0060.47bd.bf80 (bia 0060.47bd.bf80) Internet address is 10.0.0.2/8 MTU 4470 bytes, sub MTU 4470, BW 599040 Kbit, DLY 80 usec, rely 255/255, load 1/255 Encapsulation ATM, loopback not set Keepalive not supported Encapsulation(s):AAL5 4096 maximum active VCs, 1024 VCs per VP, 3 current VCCs VC idle disconnect time:300 seconds Last input never, output 00:06:33, output hang never Last clearing of "show interface" counters never Queueing strategy:fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 30 second input rate 0 bits/sec, 0 packets/sec 30 second output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 15 packets output, 7488 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out
Using the ping command, you can verify that an interface port is functioning properly. This section provides a brief description of this command. Refer to the publications listed in the "Related Documentation" section for detailed command descriptions and examples.
The ping command sends echo request packets out to a remote device at an IP address that you specify. After sending an echo request, the system waits a specified time for the remote device to reply. Each echo reply is displayed as an exclamation point (!) on the console terminal; each request that is not returned before the specified timeout is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate a bad connection.
Following is an example of a successful ping command to a remote server with the address 10.0.0.10:
Router# ping 10.0.0.10 <Return> Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 10.0.0.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms Router#
If the connection fails, verify that you have the correct IP address for the destination and that the device is active (powered on), and repeat the ping command.
Posted: Wed Jun 21 14:15:44 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.