|
|
To continue your PA-H port adapter installation, you must configure the HSSI interface. The instructions that follow apply to all supported platforms. Minor differences between the platforms---with Cisco IOS software commands---are noted.
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 interfaces, proceed to the "Configuring the Interfaces" section.
After you verify that the new PA-H 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-H or if you want to change the configuration of an existing interface, you must enter configuration mode to configure the new interfaces. If you replaced a PA-H that was previously configured, the system recognizes the new interfaces and brings each of them up in their existing configuration.
For a summary of the configuration options available and instructions for configuring interfaces on a PA-H, 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, replace a HSSI cable, or replace port adapters, use the shutdown command to shut down (disable) the interfaces 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 interfaces by entering the interface serial 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 |
|---|---|---|
Catalyst RSM/VIP2 in Catalyst 5000 family switches | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0 Router(config-if)# shutdown Ctrl-Z Router# |
Cisco 7120 series routers | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 3. Router(config-if)# interface serial 3/0 Router(config-if)# shutdown Ctrl-Z Router# |
Cisco 7140 series routers | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 4. Router(config-if)# interface serial 4/0 Router(config-if)# shutdown Ctrl-Z Router# |
Cisco 7200 series routers | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 6. Router(config-if)# interface serial 6/0 Router(config-if)# shutdown Ctrl-Z Router# |
Cisco uBR7223 router | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0 Router(config-if)# shutdown Ctrl-Z Router# |
Cisco uBR7246 router | interface, followed by the type (serial) and slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 2. Router(config-if)# interface serial 2/0 Router(config-if)# shutdown Ctrl-Z Router# |
VIP2 in Cisco 7000 series or | interface, followed by the type (serial) and slot/port adapter/port (interface-processor-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 1 of a VIP2 installed Router(config-if)# interface serial 1/1/0 Router(config-if)# shutdown Ctrl-Z Router# |
 |
Note If you need to shut down additional interfaces, enter the interface serial command (followed by the interface address of the interface) for each of the interfaces on your port adapter. Use the no shutdown command to enable the interface. |
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 new interfaces are 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 examples.
| Platform | Command | Example |
|---|---|---|
Catalyst RSM/VIP2 in Catalyst 5000 family switches | show interfaces serial, followed by slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 1. Router# show interfaces serial 1/0 Serial 1/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Cisco 7120 series routers | show interfaces serial, followed by slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 3. Router# show interfaces serial 3/0 Serial 3/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Cisco 7140 series routers | show interfaces serial, followed by slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 4. Router# show interfaces serial 4/0 Serial 4/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Cisco 7200 series routers | show interfaces serial, followed by slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 6. Router# show interfaces serial 6/0 Serial 6/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Cisco uBR7223 router | show interfaces serial, followed by slot/port (port-adapter-slot- number/ | The example is for interface 0 on a port adapter in port adapter slot 1. Router# show interfaces serial 1/0 Serial 1/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Cisco uBR7246 router | show interfaces serial, followed by slot/port (port-adapter-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 2. Router# show interfaces serial 2/0 Serial 2/0 is administratively down, line protocol is down [Additional display text omitted from this example]
|
VIP2 in Cisco 7000 series or Cisco 7500 series routers | show interfaces serial, followed by slot/port adapter/port (interface-processor-slot-number/ | The example is for interface 0 on a port adapter in port adapter slot 1 of a VIP2 in interface processor slot 1. Router# show interfaces serial 1/1/0 Serial 1/1/0 is administratively down, line protocol is down [Additional display text omitted from this example] |
Step 6 Reenable interfaces 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 interfaces 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, specifying IP routing, and setting up external timing on a DCE interface. 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 <serial> 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 interface to configure by entering the interface hssi subcommand, followed by the interface address of the interface you plan to configure. Table 4-3 gives examples for all supported platforms.
| Platform | Command | Example |
|---|---|---|
Catalyst RSM/VIP2 in Catalyst 5000 family switches | interface hssi, followed by slot/port (port-adapter-slot-number/ | The example is for the interface on a PA-H in port adapter slot 1. Router(config)# interface hssi 1/0 Router(config-if)# |
Cisco 7120 series router | interface hssi, followed by 3/port (port-adapter-slot-number/ | The example is for the interface on a PA-H in port adapter slot 3. Router(config)# interface hssi 3/0 Router(config-if)# |
Cisco 7140 series router | interface hssi, followed by 4/port (port-adapter-slot-number/ | The example is for the interface on a PA-H in port adapter slot 4. Router(config)# interface hssi 4/0 Router(config-if)# |
Cisco 7200 series routers | interface hssi, followed by slot/port (port-adapter-slot-number/ | The example is for the interface on a PA-H in port adapter slot 6. Router(config)# interface hssi 6/0 Router(config-if)# |
Cisco uBR7223 router | interface hssi, followed by slot/port (port-adapter-slot- number/ | The example is for the interface on a PA-H in port adapter slot 1. Router(config)# interface hssi 1/0 Router(config-if)# |
Cisco uBR7246 and Cisco uBR7246 VXR routers | interface hssi, followed by slot/port (port-adapter-slot-number/ | The example is for the interface on a PA-H in port adapter slot 2. Router(config)# interface hssi 2/0 Router(config-if)# |
VIP2 or VIP4 in Cisco 7000 series or Cisco 7500 series routers | interface hssi, followed by slot/port-adapter/port (interface-processor-slot-number/ | The example is for the interface on a PA-H in port adapter slot 1 of a VIP2 or VIP4 in interface processor slot 1. Router(config)# interface hssi 1/1/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. <The Note and Step 5 may not apply to your port adapter.>
|
Note If you are configuring a DTE interface, proceed to Step 6. If you are configuring a DCE interface, you need to configure the external clock signal, which is described in Step 5. The example in Step 5 applies to all systems in which the PA-H is supported. |
Step 5 Set the clock rate using the clock rate command. (See the next section, "Configuring Timing [Clock] Signals.")
Router(config-if)# clock rate 64000
Step 6 Reenable the interfaces using the no shutdown command. (See the "Shutting Down an Interface" section.)
Step 7 Configure all additional port adapter interfaces as required.
Step 8 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 9 Write the new configuration to NVRAM as follows:
Router# copy running-config startup-config [OK] Router#
This completes the procedure for creating a basic configuration.
All EIA/TIA-232 interfaces support both DTE and DCE mode, depending on the mode of the compact serial cable attached to the port. To use a port as a DTE interface, you need only connect a DTE compact serial cable to the port. When the system detects the DTE mode cable, it automatically uses the external timing signal. To use a port in DCE mode, you must connect a DCE compact serial cable and set the clock speed with the clock rate configuration command. You must also set the clock rate to perform a loopback test. This section describes how to set the clock rate on a DCE port and, if necessary, how to invert the clock to correct a phase shift between the data and clock signals. Table 4-4 summarizes some of the commands used to configure the clock rate. See the specific sections that follow for further details.
| Purpose | Command | Example | Additional Information |
|---|---|---|---|
Set standard clock rate. | clock rate | The example is for a serial interface with a standard clock rate of 72 kbps. Router(config)# interface serial 3/0 Router(config-if)# clock rate 7200 | |
Set nonstandard clock rate. | clock rate | The example is for a serial interface with a nonstandard clock rate of 1234567 kbps. Router(config)# interface serial 3/0 Router(config-if)# clock rate 1234567 | |
Remove a clock rate that has been set. | no clock rate | The example is for a serial interface and removes a standard clock rate of 72 kbps. Router(config)# interface serial 3/0 Router(config-if)# clock rate 7200 Router(config-if)# no clock rate | |
Invert the transmit clock signal. | invert-txc | The example inverts the transmit clock signal for a serial interface. Router(config)# interface serial 3/0 Router(config-if)# invert-txc | |
Change the clock signal back to its original phase. | no invert-txc | The example sets the transmit clock signal for a serial interface back to its original phase. Router(config)# interface serial 3/0 Router(config-if)# no invert-txc | |
Invert the data signal. | invert data | The example inverts the data stream for both transmit and receive for a serial interface: Router(config)# interface serial 3/0 Router(config-if)# invert data |
The default operation on a PA-H DCE interface is for the DCE device to generate its own clock signal (TxC) and send it to the remote DTE. The remote DTE device returns the clock signal to the DCE (the PA-H). Set the clock rate of an interface using the clock rate subcommand, which specifies the clock rate as a bits-per-second value. This subcommand functions in the same way on all supported platforms.
Before you can assign a clock rate, you must use the interface serial command (followed by the interface address of the interface) to select the interface to which you want to assign the clock rate value.
In the following example, the clock rate is specified as 72 kbps:
Router(config-if)# clock rate 72000
The preceding command example applies to all systems in which the PA-H is supported. Use the no clock rate command to remove the clock rate.
Following are the standard clock rates:
1200, 2400, 4800, 9600, 19200 38400 , 56000 , 64000 ,
72000 , 125000 148000 , 250000, 500000, 800000, 1000000,
1300000, 2000000, 4000000, 8000000
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 prompt. Then write the new configuration to NVRAM using the copy running-config startup-config command.
|
Note Cisco IOS Release 11.2(7a)P or a later release of 11.2 P, or Release 11.1(10)CA or a later release of 11.1 CA loaded on your Cisco 7200 router or on your Cisco 7000 series or Cisco 7500 series router with a VIP2-40(=) supports nonstandard clock rates (any value from 1200 to 8000000) on PA-H interfaces. Cisco IOS Release 12.0(3)T or a later release of 12.0 T, or Release 12.0(1)XE or a later release of 12.0 XE supports nonstandard clock rates on PA-H interfaces installed in Cisco 7204VXR and Cisco 7206VXR routers. Cisco IOS Release 11.3(7)NA or a later release of 11.3 NA, or Release 12.0(3)T or a later release of 12.0 T loaded on your Cisco uBR7246 router supports nonstandard clock rates (any value from 1200 to 8000000) on PA-H interfaces. Nonstandard clock rates are rounded (if necessary) to the nearest clock rate that the hardware can support. |
Set a nonstandard clock rate for an interface using the clock rate subcommand. Before you can assign a nonstandard clock rate, you must use the interface serial command (followed by the interface address of the interface) to select the interface to which you want to assign the nonstandard clock rate value.
In the following example, a nonstandard clock rate of 1234567 bps is specified:
Router(config-if)# clock rate 1234567
The preceding command example applies to all systems in which the PA-H is supported.
Use the no clock rate command to remove the clock rate.
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 prompt. Then write the new configuration to NVRAM using the copy running-config startup-config command.
The following example shows how to use the show running-config command to determine the exact clock rate to which the nonstandard clock rate was rounded:
Router# show running-config Building configuration... ... ! interface Serial1/0 (interface Serial3/1/0 on a VIP2) no ip address clockrate 1151526 ! ...
In the preceding example, only the relevant output from the show running-config command is shown; other information is omitted.
Systems that use long cables or cables that are not transmitting the TxC (clock) signal might experience high error rates when operating at higher transmission speeds. If a PA-H DCE port is reporting a high number of error packets, a phase shift might be the problem: inverting the clock might correct this phase shift.
When the EIA/TIA-232 interface is a DTE, the invert-txc command inverts the TxC signal the DTE receives from the remote DCE. When the EIA/TIA-232 interface is a DCE, the invert-txc command inverts the clock signal to the remote DTE port. Use the no invert-txc command to change the clock signal back to its original phase.
If you use an EIA/TIA-232 interface on the PA-H port adapter to drive a dedicated T1 line that does not have B8ZS encoding---a method to avoid 15 zeros---you must invert the data stream
(both TXD and RXD) either in the connecting CSU/DSU or on the interface. To invert the data stream coming out of the PA-H, use the invert data command. By inverting the HDLC data stream, the HDLC zero insertion algorithm becomes a ones insertion algorithm that satisfies the T1 requirements.
|
Note Invert data only on the PA-H interface or on the CSU/DSU; inverting both cancels out both data inversions. |
Table 4-5 summarizes NRZI format commands. For more information, see the remainder of this section.
| Purpose | Command | Example | Further Information |
|---|---|---|---|
Enable NRZI encoding. | nrzi-encoding [mark]1 | The example is for a serial interface with NRZI mark encoding specified: Router(config)# interface serial 3/0 Router(config-if)# nrzi-encoding mark The example is for a serial interface with NRZI space encoding specified: Router(config)# interface serial 3/0 Router(config-if)# nrzi-encoding | |
Disable NRZI encoding. | no nrzi-encoding | The example disables NRZI encoding on a serial interface: Router(config)# interface serial 3/0 Router(config-if)# no nrzi-encoding |
All EIA/TIA-232 interfaces on the PA-H support nonreturn-to-zero (NRZ) and nonreturn-to-zero inverted (NRZI) formats. Both formats use two different voltage levels for transmission. NRZ signals maintain constant voltage levels with no signal transitions---no return to a zero voltage level---during a bit interval and are decoded using absolute values: 0 and 1. NRZI uses the same constant signal levels but interprets the absence of data---a space---at the beginning of a bit interval as a signal transition and the presence of data---a mark---as no signal transition. NRZI uses relational encoding to interpret signals rather than determining absolute values.
NRZ format---the factory default on all interfaces---is more common. NRZI format is commonly used with EIA/TIA-232 connections in IBM environments.
Enable NRZI encoding on any interface using the nrzi-encoding [mark] command, where no argument after the command is interpreted as a signal transition, and mark is interpreted as no signal transition. This command functions in the same way on all supported platforms. Before you can enable NRZI encoding, you must use the interface serial command (followed by the interface address of the interface) to select the interface on which you want to enable NRZI encoding.
In the example that follows, NRZI encoding with a signal transition---no argument---is specified:
Router(config-if)# nrzi-encoding
In the example that follows, NRZI encoding with no signal transition---with argument---is specified:
Router(config-if)# nrzi-encoding mark
The preceding command examples apply to all systems in which the PA-H is supported.
Use the no nrzi-encoding command to disable NRZI encoding.
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 prompt. Then write the new configuration to NVRAM using the copy running-config startup-config command.
For complete command descriptions and instructions, refer to the Configuration Fundamentals Configuration Guide publication. For more information, see the "Obtaining Documentation" section and the .
This section provides an example of how you can configure cyclic redundancy checks (CRCs) on the PA-H.
The PA-H uses a 16-bit CRC by default; it also supports a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The sender of a data frame divides the bits in the frame message by a predetermined number to calculate a remainder or frame check sequence (FCS). Before it sends the frame, the sender appends the FCS value to the message so that the frame contents are exactly divisible by the predetermined number. The receiver divides the frame contents by the same predetermined number that the sender used to calculate the FCS. If the result is not 0, the receiver assumes that a transmission error occurred.
To enable 32-bit CRC on an interface, enter configuration mode and specify the slot and port address of the interface using the interface hssi subcommand, and then enter the crc32 command. Enter Ctrl-Z to exit from configuration mode.
|
Note The syntax for the interface hssi subcommand is given in Table 4-3 for all supported platforms. |
In the example that follows, the interface on a PA-H on a VIP2 or VIP4 installed in interface processor slot 1 of a Cisco 7000 series or Cisco 7500 series router is configured for 32-bit CRC:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Router(config)# interface hssi 1/0/0 Router(config-if)# crc32 Ctrl-z
To disable CRC-32 and return to the default CRC-16 setting, specify the slot and port address and use the no crc32 command.
|
Note When enabling a 32-bit CRC on an interface, ensure that the remote device is also configured for a 32-bit CRC. Both the sender and the receiver must use the same CRC setting. |
To check the interface configuration using show commands, proceed to the section "Configuring Half-Duplex and Binary Synchronous Communications in Cisco 7200 Series Routers." (For additional configuration options and instructions for configuring the PA-H, refer to the appropriate configuration publications listed in the "Related Documentation" section.)
This section explains how to configure EIA/TIA-232 interfaces for half-duplex and Bisync operation in Cisco 7200 routers.
|
Note Cisco IOS Release 11.2(7a)P or a later release of 11.2 P supports half-duplex and Bisync operation on the PA-H in Cisco 7200 routers. Cisco IOS Release 11.1(19)CC1 or a later release of 11.1 CC, or Release 11.3(4)AA or a later release of 11.3 AA supports half-duplex and Bisync operation on the PA-H installed in Cisco 7202 routers. Cisco IOS Release 12.0(3)T or a later release of 12.0 T, or Release 12.0(2)XE or a later release of 12.0 XE supports half-duplex and Bisync operation on the PA-H in Cisco 7204VXR and Cisco 7206VXR routers. The Catalyst RSM/VIP2, Cisco 7100 series routers, Cisco uBR7246 routers, and the VIP2 do not support half-duplex and Bisync operation on the PA-H. |
Use the half-duplex command to configure EIA/TIA-232 interfaces for half-duplex mode; full-duplex mode is the default for low-speed serial interfaces. Serial DCE interfaces in half-duplex mode can be configured for controlled-carrier mode or constant-carrier mode; constant-carrier mode is the default. Controlled-carrier mode sets the EIA/TIA-232 interface to deactivate Data Carrier Detect (DCD) until a transmission is sent to the interface. After a transmission is received, DCD is activated and the interface waits a user-configured amount of time and then transmits the data. After the transmission, the interface waits a user-configured amount of time and then deactivates DCD. Constant-carrier mode activates DCD at all times.
Use the half-duplex controlled-carrier command to configure an EIA/TIA-232 interface for controlled-carrier mode. Use the no half-duplex controlled-carrier command to return the interface to constant-carrier mode.
Follow these steps to configure controlled-carrier mode on an EIA/TIA-232 interface:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 2 Specify the interface to configure for controlled-carrier mode using the interface serial subcommand (followed by the interface address of the interface) and then enter the
half-duplex controlled-carrier subcommand.
The following example is for the first interface of the port adapter in port adapter slot 1:
Router(config)# interface serial 1/0 Router(config-if)# half-duplex controlled-carrier
Step 3 Specify the length of the timer delay the interface uses when it is configured for controlled-carrier mode by using the following command:
half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}
where value is the length of the timer delay in milliseconds.
The following example specifies a Data Carrier Detect (DCD) drop delay of 100 milliseconds on the first interface of a port adapter in port adapter slot 1:
Router(config)# interface serial 1/0 Router(config-if)# half-duplex timer dcd-drop-delay 100 ms
Table 4-6 lists the default delay settings and the value argument for each timer you can use with the half-duplex timer command.
| Timer | Command Syntax | Default Settings1 |
|---|---|---|
CTS delay2 | half-duplex timer cts-delay | 0 |
CTS drop timeout | half-duplex timer cts-drop-timeout | 250 |
DCD drop delay3 | half-duplex timer dcd-drop-delay | 100 |
DCD transmission start delay | half-duplex timer dcd-txstart-delay | 100 |
RTS drop delay4 | half-duplex timer rts-drop-delay | 3 |
RTS timeout | half-duplex timer rts-timeout | 3 |
Transmit delay | half-duplex transmit-delay | 0 |
| 1In milliseconds (ms). 2Clear To Send (CTS). 3Data Carrier Detect (DCD). 4Request To Send (RTS). |
Step 4 Complete the configuration by pressing Ctrl-Z---hold down the Control key while you press Z---or entering end or exit to exit configuration mode and return to the EXEC command interpreter prompt.
Step 5 Write the new configuration to NVRAM as follows:
Router# copy running-config startup-config [OK] Router#
This completes the procedure for configuring controlled-carrier mode on an EIA/TIA-232 interface. For additional information on configuring half-duplex operation on low-speed serial interfaces, refer to the chapter "Configuring Interfaces" of the Configuration Fundamentals Configuration Guide publication. For more information, see the "Obtaining Documentation" section and the .
|
Note To configure EIA/TIA-232 interfaces for Binary Synchronous (Bisync) operation in Cisco 7200 routers, refer to the "Block Serial Tunneling (BSTUN)" section of the "Configuring Serial Tunnel (STUN) and Block Serial Tunnel (BSTUN)" chapter of the Bridging and IBM Networking Configuration Guide. |
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces, and use the ping command to check connectivity.
This section includes the following subsections:
Table 4-7 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the PA-H appears in them 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 outputs 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 hssi 0 or 1/ | Displays status information about the interface on a PA-H in a Catalyst RSM/VIP2 | Router# show interfaces hssi 1/0 | ||
show interfaces hssi 3/interface-port-number | Displays status information about the interface on a PA-H in a Cisco 7120 series router | Router# show interfaces serial 3/1 | ||
show interfaces hssi 4/interface-port-number | Displays status information about the interface on a PA-H in a Cisco 7140 series router | Router# show interfaces serial 4/1 | ||
show interfaces hssi port-adapter-slot-number/ | Displays status information about the interface on a PA-H in a Cisco 7200 series router | Router# show interfaces hssi 1/0 | ||
show interfaces hssi 1/interface-port-number | Displays status information about the interface on a PA-H in a Cisco uBR7223 router | Router# show interfaces serial 1/1 | ||
show interfaces hssi 1 or 2/ | Displays status information about the interface on a PA-H in a Cisco uBR7246 or Cisco uBR7246 VXR router | Router# show interfaces serial 2/0 | ||
show interfaces hssi interface-processor- | Displays status information about the interface on a PA-H on a VIP2 or VIP4 in a Cisco 7000 series or Cisco 7500 series router | Router# show interfaces serial 3/1/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 |
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:
Choose the subsection appropriate for your system. Proceed to the "Using the ping Command" 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 outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only. |
 |
Caution If you are using the PA-H in the Catalyst 5000, 5500, 5505, or 5509 switch, you must install the port adapter on the Catalyst RSM/VIP2-15 or -40 Revision 2 (Part Number 73-3468-XX, where XX is the version number). Do not use the PA-H in the Catalyst 5000, 5505, or 5509 switch if you are installing it on a Catalyst RSM/VIP2-15 or -40 that is not Revision 2. If you fail to comply with this restriction, your system will shut down because of an overload of the power supply. |
|
Caution You can only have two PA-H port adapters per chassis when they are installed on a Catalyst RSM/VIP2-15 or -40 module Revision 2 and used in the Catalyst 5500 switch. |
Following is an example of the show version command from a Catalyst 5000 family switch:
Switch# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (C5RSM-JV-MZ), Released Version 11.2(15)A Copyright (c) 1986-1995 by cisco Systems, Inc. Compiled Mon 10-May-99 06:02 by biff Image text-base: 0x600088A0, data-base: 0x605A4000 ROM: System Bootstrap, Version 5.3(5) ROM: GS Bootstrap Software (RSP-BOOT-M), Version 11.2(15), RELEASED SOFTWARE Switch uptime is 4 hours, 22 minutes System restarted by reload System image file is "slot0:c5rsm-jv-mz", booted via slot0 cisco RSP7000 (R4600) processor with 16384K bytes of memory. R4600 processor, Implementation 32, Revision 2.0 Last reset from power-on G.703/E1 software, Version 1.0. Bridging software. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. Chassis Interface. (additional display text omitted from this example) 1 VIP2 controllers (1 HSSI). 1 HSSI network interface. (additional display text omitted from this example) 125K bytes of non-volatile configuration memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2
Following is an example of the show version command from a Cisco 7100 series router:
Router# show version Cisco Internetwork Operating System Software IOS (tm) EGR Software (C7100-JS-M), Version 12.0(5)XE, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC:Home:SW:IOS:Specials for info Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Thu 19-Aug-99 23:16 by rnapier Image text-base:0x60008900, data-base:0x612DA000 ROM:System Bootstrap, Version 12.0(19990324:032255) [100], DEVELOPMENT SOFTWARE BOOTFLASH:EGR Software (C7100-JS-M), Version 12.0(5)XE, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) 7100_reg_UUT uptime is 19 minutes System returned to ROM by power-on System image file is "slot0:c7100-js-mz.120-5.XE" cisco 7140-2FE (EGR) processor with 61440K/69632K bytes of memory. R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache Last reset from power-on Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. 2 FastEthernet/IEEE 802.3 interface(s) 1 HSSI network interface(s) 125K bytes of non-volatile configuration memory. 16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x0
Following is an example of the show version command from a Cisco 7200 series router:
Router# show version Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-J-M), Version 11.3(2)AA Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 10-May-99 06:02 by biff Image text-base: 0x60010890, data-base: 0x605F0000 ROM: System Bootstrap, Version 11.3(2), RELEASED SOFTWARE ROM: 7200 Software (C7200-J-M), Version 11.3(2)AA, RELEASED SOFTWARE Router uptime is 23 hours System restarted by reload System image file is "biff/c7200-j-mz", booted via tftp from 10.10.10.254 cisco 7200 (R4700) processor with 22528K/10240K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 (Level 2 Cache) Last reset from power-on Bridging software. SuperLAT software (copyright 1990 by Meridian Technology Corp). X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software (copyright 1994 by TGV Inc). (additional display text omitted from this example) 1 HSSI network interfaces. (additional display text omitted from this example) 125K bytes of non-volatile configuration memory. 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x0
Following is an example of the show version command from a Cisco 7500 series router with a VIP4:
Router# show version Cisco Internetwork Operating System Software IOS (tm) RSP Software (RSP-JV-M), Released Version 12.0(8) Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Mon 10-May-99 06:02 by biff Image text-base:0x60010900, data-base:0x60FE2000 ROM:System Bootstrap, Version 12.0(8), RELEASE SOFTWARE (fc1) BOOTFLASH:RSP Software (RSP-BOOT-M), Released Version 12.0(8) Router uptime is 18 hours, 18 minutes System returned to ROM by reload at 17:21:25 PDT Wed Oct 13 1999 System restarted at 17:25:09 PDT Wed Oct 13 1999 System image file is "rsp-jv-mz" cisco RSP2 (R4600) processor with 65536K/1072K bytes of memory. R4600 CPU at 100Mhz, Implementation 32, Rev 2.0 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. SuperLAT software (copyright 1990 by Meridian Technology Corp). Bridging software. TN3270 Emulation software. Chassis Interface. (additional display text omitted from this example) 1 VIP4 RM7000 controller (2 HSSI). 1 HSSI network interface(s) (additional display text omitted from this example) 123K bytes of non-volatile configuration memory. 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 port adapter slot in a Cisco 7200 series and Cisco uBR7200 series router and the interface processor slot in a Cisco 7000 series or Cisco 7500 series router with a VIP2 or VIP4. (The slot argument is not required with Catalyst 5000 family switches and the Catalyst RSM/VIP.)
|
Note The outputs 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 command from a Catalyst 5000 family switch:
Switch# show diag
Slot 0:
HSSI-B port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time 2d13h ago
Hardware revision 1.17 Board revision A0
Serial number 4518292 Part number 73-1801-05
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x20:01 74 01 11 00 44 F1 94 49 07 09 05 00 00 00 00
0x30:50 00 00 00 97 04 21 00 FF FF FF FF FF FF FF FF
Slot database information:
Flags: 0x4 Insertion time: 0x14E8 (3d00h ago)
VIP Controller Memory Size: Unknown
PA Bay 0 Information:
HSSI-B PA, 1 ports
EEPROM format version 1
HW rev 1.17, Board revision A0
Serial number: 12345678 Part number: 73-2559-01
Following is an example of the show diag slot command from a Cisco 7100 series router:
Router# show diag 4
Mx HSSI-B Port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time 00:38:20 ago
EEPROM contents at hardware discovery:
Hardware revision 1.17 Board revision A0
Serial number 12379034 Part number 73-2559-05
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x20:01 74 01 11 00 BC E3 9A 49 09 FF 05 00 00 00 00
0x30:50 00 00 00 99 02 20 00 FF FF FF FF FF FF FF FF
Following is an example of the show diag slot command from a Cisco 7200 series router:
Router# show diag 2
Slot 2:
HSSI-B port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time 2d13h ago
Hardware revision 1.17 Board revision A0
Serial number 12345678 Part number 73-2559-01
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 74 01 01 00 44 F1 94 49 07 09 05 00 00 00 00
0x30: 50 00 00 00 97 04 21 00 FF FF FF FF FF FF FF FF
|
Note Port adapters used with the 7200 VXR and Cisco uBR7246 VXR routers require the correct base hardware revision in order to function. The following error message will occur on bootup if the incorrect hardware revision is used: PA-3-REVNOTSUPPORTED:PA in slot 1 (Mx HSSI-B) requires base h/w revision of (1.17) for this chassisUse the show diag command to display the hardware revision. |
Following is an example of the show diag slot command from a Cisco 7500 series router with a VIP4:
Router# show diag 8
Slot 8:
Physical slot 8, ~physical slot 0x7, logical slot 8, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status:None
EEPROM format version 2
VIP4 RM7000 controller, HW rev 2.01, board revision A0
Serial number:12345678 Part number:211-18700-71
Test history:0x02 RMA number:00-00-00
Flags: unknown flags 0x7F; 7500 compatible
EEPROM contents (hex):
0x20:02 22 02 01 00 AF 7B C9 D3 49 0C 47 02 00 00 00
0x30:02 3A 0C FF FF FF FF FF FF FF FF FF FF FF FF FF
Slot database information:
Flags:0x4 Insertion time:0x3EC4FE0 (00:02:08 ago)
Controller Memory Size:64 MBytes DRAM, 65536 KBytes SRAM
PA Bay 0 Information:
HSSI-B PA, 1 port
EEPROM format version 1
HW rev 1.17, Board revision A0
Serial number:12345678 Part number:73-2559-01
For complete descriptions of interface subcommands and the configuration options available for Catalyst RSM/VIP2, Cisco 7100 series, Cisco 7200 series, Cisco uBR7246, and VIP2 and VIP4 interfaces, refer to the publications listed in the "Related Documentation" section.
|
Note The outputs 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 hssi command for a PA-H on a Catalyst RSM/VIP2 in a Catalyst 5000 family switch:
Switch# show interfaces hssi 0/0
Hssi0/0 is up, line protocol is up
Hardware is HSSI-B
Internet address is 10.1.1.10
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 2d22h, output 00:00:19, output hang never
Last clearing of "show interface" counters 2d20h
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4084 packets output, 1298712 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Following is an example of the show interfaces hssi command for a PA-H in a Cisco 7200 series router:
Router# show interfaces hssi 2/0
Hssi2/0 is up, line protocol is up
Hardware is HSSI-B
Internet address is 10.1.1.10
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 252/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input never, output never, 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
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 parity
1 input errors, 1 CRC, 0 frame, 1 overrun, 0 ignored, 0 abort
1 packets output, 24 bytes, 0 underruns
0 output errors, 0 applique, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions TM=down CA=up LC=down
|
Note For the Cisco 7206 and Cisco 7206VXR router shelves, the show interfaces command requires a shelf number in the format show interfaces type shelf-number/port-adapter-slot-number/interface-port. |
Following is an example of the show interfaces hssi command for a PA-H in a Cisco 7000 series or Cisco 7500 series router:
Router# show interfaces hssi 1/0/0
Hssi1/0/0 is up, line protocol is up
Hardware is HSSI-B
Internet address is 10.1.1.10
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 2d22h, output 00:00:19, output hang never
Last clearing of "show interface" counters 2d20h
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4084 packets output, 1298712 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
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 IP 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.
This completes the PA-H interface configuration.
Posted: Fri Apr 28 08:49:59 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.