|
|
This chapter provides information on the High-Speed Serial Interface Processor (HIP). (See Figure 9-1.)
The HIP provides a single HSSI, EIA/TIA-612/613 network interface for Cisco 7000 series and Cisco 7500 series routers, and ships as Product Number CX-HIP(=). The HIP provides a single, full-duplex HSSI for transmitting and receiving data at rates of up to 52 megabits per second (Mbps).
HSSI, which was recently standardized as EIA/TIA-612/613, provides access to services at T3 (45 Mbps), E3 (34 Mbps), and Synchronous Optical Network (SONET) STS-1 (51.82 Mbps) rates. The actual rate of the interface depends on the external data service unit (DSU) and the type of service to which it is connected.
The HIP supports both 16- and 32-bit cyclic redundancy checks (CRCs). The default is 16-bit CRCs. To enable 32-bit CRCs, you must use a configuration command, depending on the hardware version of your HIP. (For a description of the CRC function, refer to the section "Configuring Cyclic Redundancy Checks" on page 9-14.)
The default HIP microcode resides on a read-only memory (ROM) device in socket U133. (See Figure 9-1.)
The HSSI port is a female, 50-pin, SCSI-II-type connector. You must use an HSSI cable to connect the HIP to an external DSU. Refer to the section "HIP Connectors, Cables, and Pinouts" for descriptions of HSSI cables.
This section provides information about hardware requirements for the HIP.
The HIP uses a 16-bit cyclic redundancy check (CRC) by default, but also supports a 32-bit CRC, depending on the hardware version of your HIP.
To determine if your HIP will support a 32-bit CRC, use the show diagbus command; if the resulting display indicates Part Number 81-0050-01, Hardware Version 1.0, you cannot use the CRC-32 feature. If the display indicates Part Number 81-0050-02, Hardware Version 1.1, you can use the CRC-32 feature.
Two types of cables are available for use with the HIP: the HSSI cable, which is used to connect your router to an external DSU (and an HSSI network), and a null modem cable, which allows you to connect two HSSI-equipped routers back to back.
The HSSI cable (CAB-HSI1=) connects the HIP with the external DSU. The HSSI cable is 10 feet (3.048 meters) long. The maximum HSSI cable length allowed is 50 feet (15.24 meters).
Figure 9-2 shows the 50-pin connector used at each end of the HSSI cable.
 | Caution Although the HIP connector and the HSSI cable are similar to SCSI-II format, they are not identical. The HSSI cable specification is more stringent than that for the SCSI-II. If you try to use a SCSI-II cable instead of an HSSI cable, proper operation cannot be guaranteed. |
Table 9-1 lists the HSSI connector pinouts.
Signal Name | Pin No. + Side (Router End) | Direction1 | Pin No. - Side (DSU End) |
|---|---|---|---|
| SG (Signal Ground) | 1 | -- | 26 |
| RT (Receive Timing) | 2 | <-- | 27 |
| CA (DCE Available) | 3 | <-- | 28 |
| RD (Receive Data reserved) | 4 | <-- | 29 |
| LC (Loopback circuit C) | 5 | <-- | 30 |
| ST (Send Timing) | 6 | <-- | 31 |
| SG (Signal Ground) | 7 | -- | 32 |
| TA (DTE Available) | 8 | --> | 33 |
| TT (Terminal Timing) | 9 | --> | 34 |
| LA (Loopback circuit A) | 10 | --> | 35 |
| SD (Send Data) | 11 | --> | 36 |
| LB (Loopback circuit B) | 12 | --> | 37 |
| SG (Signal Ground) | 13 | -- | 38 |
| 5 (Ancillary to DCE) | 14-18 | --> | 39-43 |
| SG (Signal Ground) | 19 | -- | 44 |
| 5 (Ancillary from DCE) | 20-24 | <-- | 45-49 |
| SG (Signal Ground) | 25 | -- | 50 |
A null modem cable (CAB-HNUL=) can connect two routers directly, back to back. (See Figure 9-3.)
The null modem cable is 10 feet (3.048 meters) long. The maximum null modem cable length allowed is 50 feet (15.24 meters).
To connect two routers back to back with the null modem cable, the two routers must be in the same location and can be two Cisco 7000 series or Cisco 7500 series routers, one of each (or other HSSI-equipped Cisco routers). A null modem connection allows you to verify the operation of the HSSI or to link the routers directly in order to build a larger node.
The null modem cable uses the same 50-pin connectors as the HSSI cable, but uses the pinouts listed in Table 9-2. For connection and configuration instructions, refer to the following section "Attaching Network Interface Cables to the HIP."
| Signal Name | From Pins | Direction | To Pins | Signal Name |
|---|---|---|---|---|
| RT (Receive Timing) | 2, 27 | --> | 9, 34 | TT (Terminal Timing) |
| CA (DCE available) | 3, 28 | --> | 8, 33 | TA (DTE Available) |
| RD (Receive Data) | 4, 29 | --> | 11, 36 | SD (Send Data) |
| LC (Loopback C) | 5, 30 | --> | 10, 35 | LA (Loopback A) |
| ST (Send Timing) | 6, 31 | --> | 6, 31 | ST (Send Timing) |
| TA (DTE available) | 8, 33 | --> | 3, 28 | CA (DCE Available) |
| TT (Terminal Timing) | 9, 34 | --> | 2, 27 | RT (Receive Timing) |
| LA (Loopback A) | 10, 35 | --> | 5, 30 | LC (Loopback C) |
| SD (Send Data) | 11, 36 | --> | 4, 29 | RD (Receive Data) |
| GND (Ground) | 1, 26, 7, 32, 13, 38, 19, 44, 25, 50 | 1, 26, 7, 32, 13, 38, 19, 44, 25, 50 | GND (Ground) | |
| Loopback (not connected) | 12, 37 | |||
| 12, 37 | Loopback (not connected) | |||
| Not used | 14-18, 20-24, 39-43, 45-49 | 14-18, 20-24, 39-43, 45-49 | Not used |
The HIP port functions as a DTE when it is connected to a DSU for a standard HSSI connection; it can also be connected to a collocated router with a null-modem cable. To connect the router to an HSSI network, use a Cisco HSSI cable between the HIP port and the DSU.
HSSI cable ends are identical; connect them as shown in Figure 9-4.
To verify the operation of the HSSI port or to build a larger node, use a null-modem cable between two HSSI ports and connect two routers back to back, as shown in Figure 9-5.
The two routers must be in the same location, and can be two Cisco 7500 series or one Cisco 7500 series and one Cisco 7000 series router (or any combination of two HSSI-equipped Cisco routers). When you configure the ports, you must enable the internal transmit clock on each HSSI with the hssi internal-clock command. When you disconnect the cable, use the no hssi internal-clock command.
For additional descriptions and examples of these commands, refer to the appropriate configuration publications, which are listed in the section "If You Need More Information" in the chapter "Using Interface Processors."
The HIP has four status LEDs on its faceplate, which indicate conditions on the HSSI port. (Refer to Figure 9-6.)
When the system has reinitialized all interfaces, the enabled LED on the HIP should go on. The console screen will also display a message as the system discovers each interface during its reinitialization.
The following conditions must be met before the HIP is enabled:
If any one of these conditions is not met, or if the initialization fails, the enabled LED does not go on.
The four port status LEDs on the HIP indicate the following:
Verify that the HIP is connected correctly as follows:
Step 1 While the system reinitializes each interface, observe the console display messages and verify that the system discovers the HIP. The system should recognize the HIP interface but leave it configured as down.
Step 2 When the reinitialization is complete, verify that the enabled LED on the HIP is on and remains on. If the LED does stay on, proceed to Step 5. If the enabled LED does not stay on, proceed to the next step.
Step 3 If the enabled LED on the HIP fails to go on, suspect that the HIP board connector is not fully seated in the backplane. Loosen the captive installation screws, then firmly push the top ejector down while pushing the bottom ejector up until both are parallel to the HIP faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the HIP should go on. If the enabled LED goes on, proceed to Step 5. If the enabled LED does not go on, proceed to the next step.
Step 4 If the enabled LED still fails to go on, remove the HIP and try installing it in another available interface processor slot.
Step 5 Use the show interfaces or show controllers cbus command to verify the status of the HIP interface. (If the HIP interface is not configured, you must configure it using the procedures in the section "Configuring the HIP.")
If an error message displays on the console terminal, refer to the appropriate reference publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.
If you want to change the configuration of an existing interface, you must enter configuration mode to configure the interface. If you replaced a HIP that was previously configured, the system will recognize the new HIP interface and bring it up in its existing configuration.
After you verify that the new HIP is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. Be prepared with the information you will need, such as the following:
For additional descriptions and examples of serial interface configuration, refer to the appropriate configuration publications, which are listed in the section "If You Need More Information" in the chapter "Using Interface Processors."
Configuring the HIP first requires privileged-level access to the EXEC command interpreter. (Refer to the section "Using the EXEC Command Interpreter" in the chapter "Using Interface Processors.") Also, privileged-level access usually requires a password. (Contact your system administrator, if necessary, to obtain privileged-level access.)
Cisco 7000 series and Cisco 7500 series routers identify an interface address by its interface processor slot number and port number in the format slot/port. Because each HIP contains a single HSSI, the port number is always 0. For example, the slot/port address of the HSSI on a HIP installed in interface processor slot 0 is 0/0; if installed in interface processor slot 1, the slot/port address changes to 1/0.
This section provides instructions for a basic interface configuration: enabling an interface and specifying IP routing. Depending on the requirements for your system configuration and the protocols you plan to route on the interface, you might also need to enter other configuration subcommands.
Use the following procedure to perform a basic configuration:
Step 1 At the privileged-mode prompt, enter configuration mode and specify that the console terminal will be the source of configuration subcommands as follows:
configure terminal
Step 2 Specify the new HSSI to configure by entering the subcommand interface, followed by the type (hssi) and slot/port (interface processor slot number/0). The example that follows is for a HIP in interface processor slot 0:
interface hssi 0/0
Step 3 If IP routing is enabled on the system, you can assign an IP address and subnet mask to the interface with the ip address configuration subcommand as follows:
ip address 1.1.1.1 255.255.255.0
Step 4 Change the shutdown state to up and enable the HSSI as follows:
no shutdown
Step 5 Add any additional configuration subcommands that are required to enable routing protocols and adjust the interface characteristics.
Step 6 When you have entered all the necessary configuration subcommands, press Ctrl-Z (hold down the Control key while you press Z) to exit configuration mode.
Step 7 Store the new configuration in NVRAM with the copy running-config startup-config command as follows:
copy running-config startup-config
The system displays an OK message when the configuration has been stored.
Step 8 Exit the privileged level and return to the user level by entering disable at the prompt as follows:
disable
Proceed to the following section to configure your HIP for cyclic redundancy checks (CRCs).
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 HIP uses a 16-bit CRC by default, but also supports a 32-bit CRC, depending on the hardware version of your HIP.
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 and sends a request to the sender to resend the frame.
The designators 16 and 32 indicate the number of check digits per frame that are used to calculate the FCS. CRC-16, which transmits streams of 8-bit characters, generates a 16-bit FCS. CRC-32, which transmits streams of 16-bit characters, generates a 32-bit FCS. CRC-32 transmits longer streams at faster rates and, therefore, provides better ongoing error correction with fewer retransmissions. To prevent errors, both the sender and the receiver must use the same CRC setting.
To enable 32-bit CRC on an interface use the crc32 command. 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. Press Ctrl-Z to exit from configuration mode.
In the example that follows, a HIP in interface processor slot 0 is configured for 32-bit CRC:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)# Router(config)#interface hssi 0/0Router(config-int)#crc32Ctrl-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.
The null modem cable can connect two routers directly back to back. The two routers must be in the same location, and can be two Cisco 7000 series routers, two Cisco 7500 series routers, or one of each. (The HSSIs on older AGS+ routers can also be used.) This setup allows you to verify the operation of the HSSI port or to directly link the routers in order to build a larger node. The null modem cable uses the same 50-pin connectors as the HSSI cable, but uses the pinouts listed in Table 9-2.
To connect two routers, attach a null modem cable between an HSSI port on each router. Enable the internal transmit clock in both routers by entering the command hssi internal-clock.
When specifying an interface, the syntax of the configure command differs between Cisco 7000 series and Cisco 7500 series and AGS+ interfaces. All router platforms use the same hssi internal-clock command to enable the internal transmit clock on the HSSI.
An AGS+ interface is defined by interface type and logical interface (unit) number (address), and Cisco 7000 series and Cisco 7500 series interfaces by interface type and physical slot/port location. (The output of the show interfaces command displays the logical unit number in both router types and the physical slot/port location in the Cisco 7000 series and Cisco 7500 series.)
The following examples show the configure command syntax for the Cisco 7000 series, Cisco 7500 series, and then for the older AGS+ model:
Cisco7000/7500Series#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)# (Enter configuration commands...) Cisco7000/7500Series(config)#interface hssi 0/0Cisco7000/7500Series(config-int)#hssi internal-clockCisco7000/7500Series(config-int)#^zAGS+#configure terminalEnter configuration commands, one per line. End with CNTL/Z. AGS+(config)# (Enter configuration commands...) AGS+(config)#interface hssi 0AGS+(config-int)#hssi internal-clockAGS+(config-int)#^z
Be sure to configure the HSSI port on both routers for an internal transmit clock. When the internal clock is enabled, the ST LED goes on. When the internal clock is enabled in both routers, the ST and RT LEDs on both of the connected HSSI ports go on. (The LEDs on the Cisco 7000 series and Cisco 7500 series HIP, and the AGS+ CSC-[C2]HSCI HSSI are identical.)
Disconnect the null modem cable and disable the internal transmit clock with the command no hssi internal-clock. Use this command to turn off the transmit clock for each port on both routers.
For additional descriptions and examples of serial interface configurations, refer to the appropriate configuration publications listed in the section "If You Need More Information" in the chapter "Using Interface Processors."
The following summary describes how to use the show commands to verify that the new interface is configured correctly:
Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new interface.
Step 2 Display all the current interface processors and their interfaces with the show controllers cbus command. Verify that the new HIP appears in the correct slot.
Step 3 Specify the new interfaces with the show interfaces hssi slot/port command and verify that the first line of the display specifies the interface with the correct slot number. Also verify that the interface and line protocol are in the correct state: up or down.
Step 4 Display the protocols configured for the entire system and specific interfaces with the command show protocols. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.
Step 5 Display the entire system configuration file with the show configuration command. Verify that the configuration is accurate for the system and each interface.
If the interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the network interface is properly connected and terminated. If you still have problems, contact a service representative for assistance.
This completes the HIP configuration procedure.
|
|