|
|
A High-speed Serial Interface (HSSI) network processor module (NPM) is a high-speed and high-bandwidth serial interface device that is inserted into one of the three chassis slots on the modular Cisco 4500 or Cisco 4700 routers.
The single-port HSSI NPM supports speeds up to 52-Mbps full duplex. This dramatically raises serial performance from the 8 Mbps provided by the aggregate of 4 ports on the NP-4T NPM serial module. This represents a more than six fold increase in performance per module over previous serial connections.
There are many network applications for the HSSI network processor module. For example, network administrators can significantly increase system port density and deliver high quality of service for bandwidth-intensive applications such as video and multimedia services. Medium-sized Internet service providers and telcos can also use this module to connect to an Internet backbone provider via a T3 or E3 line. The HSSI network processor module can also be used for campus to campus high-speed serial connections. See Figure 4.
This module is supported on these platforms:
You must have at least one HSSI NPM installed in a Cisco 4500 or Cisco 4700 router before it can be configured. A maximum of two HSSI modules can be installed in one router. However, if you are running two network processor modules, the maximum suggested speed of each module is 12 Mbps.
Each HSSI NPM provides one HSSI network interface. See the "Configuration Example" section later in this chapter for an example of a configured HSSI interface.
Perform the tasks in the following sections to configure an HSSI interface. The first task is required; the remaining tasks are optional.
To specify an HSSI and enter interface configuration mode, perform one of the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Begin interface configuration. | interface hssi number |
The HSSI supports the serial encapsulation methods, except for X.25-based encapsulations. The default method is HDLC. You can define the encapsulation method by performing the following task in interface configuration mode:
| Task | Command |
|---|---|
| Configure HSSI encapsulation. | encapsulation {atm-dxi | hdlc | frame-relay | ppp | sdlc-primary | sdlc-secondary | smds | stun} |
Two HSSI interfaces can be connected back-to-back with a null-modem cable. This is used for internal testing purposes. However, you must provide internal clocking to each HSSI interface in this case. Usually clocking comes from the CSU/DSU out on the network. To specify internal clocking, perform the following task on each HSSI interface in interface configuration mode:
| Task | Command |
|---|---|
| Convert the HSSI interface into a 45-MHz clock master. | hssi internal-clock |
The example included in this section shows a Cisco 4700-M router equipped with two HSSI network processor modules (used for WAN connectivity) and one 2-Ethernet port module (used for LAN connectivity).
The following example output is created with the show config user EXEC command after the router is configured and the configuration file is saved to NVRAM. The content of the router's configuration depends on the demands of your network (for example, required protocols and available router interfaces). See the Cisco 4000 Series Installation Guide for step-by-step instructions on how to configure the router after you boot it up for the first time.
version 11.2 ! hostname c4X00 ! username brad password 7 13171F1D0A080139 username jim password 7 104D000A0618 !
Ethernet interfaces and their subinterfaces are configured for LAN access.
interface Ethernet0 ip address 10.1.1.1 255.255.255.0 media-type 10BaseT ! interface Ethernet1 ip address 10.1.2.1 255.255.255.0 media-type 10BaseT !
Interfaces HSSI 0 and HSSI 1 are the high-speed serial interfaces. Each HSSI module in this example is also configured for internal back-to-back testing by the hssi internal-clock command, which is an optional configuration. If you are not performing back-to-back internal testing between two HSSI interfaces, do not configure this command.
interface hssi 0 ip address 10.1.3.1 255.255.255.0 frame-relay interface-dlci 16 encapsulation frame-relay hssi internal-clock ! interface hssi 1 encapsulation hdlc ip address 10.1.5.1 255.255.255.0 hssi internal-clock
This section documents commands that have been created or modified to support the HSSI NPM. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references.
Use the show controllers hssi privileged EXEC command to display information that is specific to the interface hardware.
show controllers hssi number| number | Specifies the interface number. There is only one HSSI interface on each HSSI network processor module for the Cisco 4000 series routers. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
If you have the debug serial interface command turned on while running the show controllers hssi command, register data will be displayed about the controller chip.
Sample output of the show controllers hssi command on a Cisco 4000 series router follows:
Router# show controllers hssi 0
MXT slot 2, unit 0, subunit 0
f/w version 1-26, rev ID 0x2800001, version 2
idb = 0x606D09C0, ds = 0x606D23F8, ssb=0x606D262C
Clock mux=0x35, ucmd_ctrl=0x8, port_status=0x25
Serial config=0x0, line config=0x1B0002 maxdgram=4474
TM=down CA=up LC=down
line state: up
HSSI DTE cable, received clockrate 44732632
base0 registers=0x3C210000, base1 registers=0x3C212000
mxt_ds=0x6063C158, rx ring entries=32, tx ring entries=32
rxring=0x40059C3C, rxr shadow=0x606D24DC, rx_head=12 rx_tail=0
txring=0x40059D64, txr shadow=0x606D2584, tx_head=12, tx_tail=12, tx_count=0
throttled=0, enabled=0, disabled=0
rx_no_eop_err=0, rx_no_stp_err=0
rx_no_eop_stp_err=0, rx_no_buf_err=0
tx_underrun_err=1
tx_fullring=0, tx_started=111
Table 6 describes significant fields shown in the display.
| Field | Description |
|---|---|
| MXT slot number, unit number, subunit number | Identifies the type of controller chip used by the HSSI interface (MXT stands for Muselix), the chassis slot in which he chip is located, unit number, and subunit number. Since the HSSI network processor module has only one interface, there are no subunits. |
| f/w version number, rev ID value, version number | Indicates the firmware version number, revision identification value, and version number of the controller chip. |
| idb = value, ds = value, ssb = value | Specifies the Interface Description Block (IDB) hexadecimal value that corresponds to the HSSI interface, platform-specific instance (ds), and the serial controller block (ssb). |
| Clock mux = value, ucmd_ctrl = value, port_status = value Serial config = value line config = value maxdgram = value | Lists additional chip registers, which are displayed as hexadecimal values. Registers settings are displayed for the clock mux, micro command control, port status, serial configuration, line configuration, and the MTU of the HSSI interface. |
| TM = {up|down} CA = {up|down} LC = {up|down} | Status signals for the HSSI line, which include up and down indicators for test mode (TM), carrier available (CA), and loopback control (LC). |
| line state: {up|down} | Current physical-line state of the HSSI line. It is either up or down. |
| HSSI DTE cable, received clockrate value | Describes what type of cable is used to bridge the HSSI line with the HSSI interface and what clockrate the interface is receiving. |
| Register or counter type = value | Displays chip-specific registers, information about the receive and transmit ring, error statistics, and miscellaneous counters. |
Use the show interfaces hssi privileged EXEC command to display information about the HSSI interface.
show interfaces hssi unit [accounting]| unit | Must match a port number on the selected interface. |
| accounting | (Optional) Displays the number of packets of each protocol type that have been sent through the interface. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show interfaces hssi command on a Cisco 4000 series routers when HSSI is enabled:
Router# show interfaces hssi 0
Hssi0 is up, line protocol is up
Hardware is MXT
Internet address is 99.1.1.8/24
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 254/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 00:00:41, output 00:00:03, output hang never
Last clearing of "show interface" counters 00:00:18
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
100 packets input, 10400 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
100 packets output, 10400 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions TM=down CA=up LC=down
Table 7 describes significant fields shown in the display.
| Field | Description |
|---|---|
| HSSI 0 is {up | down} ...is administratively down | Indicates whether the interface hardware is currently active (whether carrier detect is present) and if it has been taken down by an administrator. "Disabled" indicates the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default. |
| line protocol is {up | down | administratively down} | Indicates whether the software processes that handle the line protocol considers the line usable (that is, whether keepalives are successful). |
| Hardware | Specifies the hardware type. |
| Internet address | Lists the Internet address followed by subnet mask. |
| MTU | Maximum Transmission Unit of the interface. |
| BW | Bandwidth of the interface in kilobits per second. |
| DLY | Delay of the interface in microseconds. |
| rely | Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes. |
| load | Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
| Encapsulation | Encapsulation method assigned to interface. |
| loopback | Indicates whether loopback is set and type of loopback test. |
| keepalive | Indicates whether keepalives are set or not. |
| Last input | Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed. |
| Last output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. |
| output hang | Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed. |
| Last clearing | Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed. |
| Output queue, drops Input queue, drops | Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue. |
| Five minute input rate, Five minute output rate | Average number of bits and packets transmitted per second in the last 5 minutes. |
| packets input | Total number of error-free packets received by the system. |
| bytes input | Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system. |
| no buffers | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events. |
| broadcasts | Total number of broadcast or multicast packets received by the interface. |
| runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. |
| giants | Number of packets that are discarded because they exceed the medium's maximum packet size. |
| parity | Report of the parity errors on the HSSI. |
| input errors | Sum of all errors that prevented the receipt of datagrams on the interface being examined. This may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories. |
| CRC | Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC errors are also reported when a far-end abort occurs, and when the idle flag pattern is corrupted. This makes it possible to get CRC errors even when there is no data traffic. |
| frame | Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems. |
| overrun | Number of times the serial receiver hardware was unable to receive data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
| ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased. |
| abort | Number of packets whose receipt was aborted. |
| packets output | Total number of messages transmitted by the system. |
| bytes output | Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
| underruns | Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. |
| congestion drop | Number of messages discarded because the output queue on an interface grew too long. This can happen on a slow, congested serial link. |
| output errors | Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error. Other datagrams may have errors that do not fall into any of the specifically tabulated categories. |
| applique | Indicates an unrecoverable error has occurred on the HSA applique. The system then invokes an interface reset. |
| interface resets | Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down. |
| restarts | Number of times the controller was restarted because of errors. |
| carrier transitions | Number of times the carrier detect signal of the interface has changed state. Indicates modem or line problems if the carrier detect line is changing state often. |
| Protocol | Protocol that is operating on the interface. |
| Pkts In | Number of packets received for that protocol. |
| Chars In | Number of characters received for that protocol. |
| Pkts Out | Number of packets transmitted for that protocol. |
| Chars Out | Number of characters transmitted for that protocol. |
| TM = {up|down} CA = {up|down} LC = {up|down} | Status signals for the HSSI line, which include up and down indicators for test mode (TM), carrier available (CA), and loopback control (LC). |
To test the HSSI interface by pinging itself, use the test interface hssi EXEC command.
test interface hssi number| number | Interface card number on a Cisco 4000 series router. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
This command is commonly used by manufacturing representatives to test the functionality of the HSSI interface before it is sold to customers. The ping command is more commonly used by customers to test a HSSI interface that is installed in the network.
The test interface command tests all the available interfaces in the router. Whereas the test interface hssi command tests only one specified HSSI interface in the router.
The following example tests a HSSI interface on a Cisco 4500-M router. The interface sends approximately100 packets to itself and then the Cisco IOS software displays the success rate of the transmission.
Router# test interface hssi 0
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Passed
1 interfaces: 1 passed, 0 failed, 0 skipped, 0 untestable
Table 8 describes the example output for this command.
| Field | Description |
|---|---|
| interfaces | Number of interfaces that were tested. |
| passed | Number of interfaces that passed the test. |
| failed | Number of interfaces that failed the test. |
| skipped | Number of interfaces that were skipped during the test. |
| untestable | Number of interfaces that were untestable during the test. |
ping
For additional software configuration information for the Cisco 4000 series routers, refer to the following documents:
|
|