|
|
Product Numbers: PA-2CE1/PRI-75(=), PA-2CE1/PRI-120(=)
This configuration note describes the installation and configuration of the channelized E1 Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) port adapters (PA-2CE1/PRI-75 and PA-2CE1/PRI-120). The port adapters are used in the Catalyst VIP2-15 and VIP2-40 modules attached to the Route Switch Module (RSM) and used in the Catalyst 5000 series switches. The port adapters can also be used in the following:
Use this configuration note with the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your VIP2-15 and VIP2-40.
For complete descriptions of interface subcommands and the configuration options available for interfaces that support the 2CE1 port adapter functionality, refer to the publications listed in the "If You Need More Information" section.
This configuration note is organized into the following sections:
The Cisco IOS software that runs your router contains extensive features and functionality. For additional information on configuring the Catalyst VIP2 port adapter interfaces, refer to the following documentation:
Specific hardware and software prerequisites to ensure proper operation of the 2CE1 port adapters follow:
Follow the safety guidelines in this section when working with any equipment that connects to electrical power or telephone wiring.
Follow these basic guidelines when working with any electrical equipment:
ESD damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. Port adapters and the Catalyst VIP2 comprise printed circuit boards that are fixed in metal carriers. Electromagnetic interference (EMI) shielding and connectors are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use a preventive antistatic strap during handling.
Follow these guidelines for preventing ESD damage:
 | Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms. |
The 2CE1 port adapters, shown in Figure 1 and Figure 2, provide up to two channelized E1 (unbalanced 75-ohm or balanced 120-ohm) or ISDN PRI interfaces for connecting the Catalyst VIP2 to channel service units (CSUs). Each 2CE1 interface can transmit and receive data bidirectionally at the E1 rate of 2.048 megabits per second (Mbps).
Each 2CE1 interface connects to external networks through a single port that has a 15-pin, D-shell receptacle. You must use G.703 serial interface cables to connect unbalanced 75-ohm or balanced 120-ohm 2CE1 interfaces to a CSU. By setting jumpers on the 2CE1 printed circuit board, 2CE1 interfaces are configurable for balanced and unbalanced connections. Refer to the "Configuring 2CE1 Port Adapter Jumpers" section for balanced and unbalanced 2CE1 jumper settings.
When running channelized E1, each 2CE1 interface provides up to 31 E1 channel groups, which are numbered from 0 to 30. Each channel group provides up to 31 64-kilobit per second (kbps) time slots (DS0 channels), which are numbered 1 to 31. Multiple DS0 channels can be mapped to a single channel group. Each channel group is presented to the system as a serial interface that can be configured individually. Usable bandwidth for each channel group is calculated as n x 64 kbps, where n is a number of DS0 channels (1 to 31).
When running ISDN PRI, each 2CE1 interface provides 30 bearer (B) channels that can transmit and receive data at the rate of 64 kbps, full duplex, and one data (D) channel that can transmit and receive data at the rate of 16 kbps, full duplex. The B channels are used for transmitting user data. The D channel is used for call setup control and network connection teardown, and provides the communication from the router to the ISDN switch. The B and D channels are presented to the system as serial interfaces that support High-Level Data Link Control (HDLC) and Point-to-Point Protocol (PPP) encapsulation. The 2CE1 port adapter supports dial-on-demand routing (DDR) when running ISDN PRI.
Figure 3 shows a Catalyst VIP2 with one installed port adapter and one port adapter blank. Port adapters have handles that allow for easy installation and removal. The left port adapter is in port adapter slot 0, and the port adapter blank is in port adapter slot 1.
The 2CE1 port adapters have an enabled LED, standard on all port adapters, and three status LEDs for each port. (See Figure 4.)
After system initialization, the enabled LED goes on to indicate that the port adapter has been enabled for operation.
The following conditions must be met before a 2CE1 port adapter is enabled:
If any of these conditions is not met, or if the initialization fails for other reasons, the enabled LED does not go on. Table 1 lists port LED status indications.
| Port LED | Status |
LB (loopback) | This green LED comes on when the port is in loopback mode (line or local). The LED remains off during normal operation of the port adapter. |
LA (local alarm) | This green LED comes on when the incoming signal from a remote source has one of the following alarms: loss of frame (LOF), loss of signal (LOS), or all-in-one signal (AIS). The LED remains off during normal operation of the port adapter. |
RA (remote alarm) | This green LED comes on when the remote source's incoming signal contains a remote alarm (a yellow alarm). The LED remains off during normal operation of the port adapter. |
Three G.703 serial interface cables are available for use with the 2CE1 port adapters: two cables for balanced 120-ohm 2CE1 interface connections and one cable for an unbalanced 75-ohm 2CE1 interface connection.
All three cables have a 15-pin, D-shell (DB-15) connector at the Catalyst VIP2 end and either twinax, RJ-45, or BNC connectors at the network end. Figure 5, Figure 6, and Figure 7 show the 2CE1 interface cables.
The product numbers for the 2CE1 interface cables follow:
Table 2 lists connector pinouts for the 2CE1 interface cables.
| 2CE1 End | Network End | |||||
|---|---|---|---|---|---|---|
| DB-15 | Twinax | RJ-45 | BNC | |||
| Pin1 | Signal2 | Pin | Signal | Pin | Signal | Signal |
9 | Tx Tip | Tx-1 | Tx Tip | 1 | Tx Tip | Tx Tip |
2 | Tx Ring | Tx-2 | Tx Ring | 2 | Tx Ring | Tx Shield |
10 | Tx Shield | Shield | Tx Shield | 3 | Tx Shield | - |
8 | Rx Tip | Rx-1 | Rx Tip | 4 | Rx Tip | Rx Tip |
15 | Rx Ring | Rx-2 | Rx Ring | 5 | Rx Ring | Rx Shield |
7 | Rx Shield | Shield | Rx Shield | 6 | Rx Shield | - |
| 1Any pins not described in this table are not connected. 2Tx = transmit. Rx = receive. |
The following sections describe how to install the 2CE1 port adapters.
| Caution To prevent system problems, do not remove port adapters from the Catalyst VIP2 or attempt to install other port adapters in the Catalyst VIP2 while the system is operating. To install or replace port adapters, first remove the RSM/VIP2 combination from the switch. |
Each port adapter circuit board is mounted to a metal carrier and is sensitive to ESD damage. The following procedures should be performed by a Cisco-certified service provider only. Although the Catalyst VIP2 supports online insertion and removal (OIR), individual port adapters do not. To replace port adapters, you must first remove the RSM/VIP2 combination from the chassis, and then install or replace port adapters as required. If a blank port adapter is installed in the Catalyst VIP2 in which you want to install a new port adapter, you must first remove the Catalyst VIP2 from the chassis, and then remove the blank port adapter.
When only one port adapter is installed in a Catalyst VIP2, a blank port adapter must fill the empty slot to allow the Catalyst VIP2 and switch chassis to conform to electromagnetic interference (EMI) emissions requirements, and to permit proper airflow through the chassis. If you plan to install a new port adapter, you must first remove the blank port adapter.
Follow this procedure to remove and replace any type of port adapter in the Catalyst VIP2:
Step 1 Attach an ESD-preventive wrist strap between you and an unfinished chassis surface or to the ESD connector on the switch.
Step 2 For a new port adapter installation or a port adapter replacement, first disconnect all interface cables from the ports on the front of the port adapter.
Step 3 To remove the RSM/VIP2 combination from the chassis, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
Step 4 Place the removed RSM/VIP2 combination on an antistatic mat.
Step 5 Locate the screw at the rear of the port adapter (or blank port adapter) to be replaced. (See Figure 8.) This screw secures the port adapter (or blank port adapter) to its slot.
Step 6 Remove the screw that secures the port adapter (or blank port adapter).
Step 7 With the screw removed, grasp the handle on the front of the port adapter (or blank port adapter) and carefully pull it out of its slot, away from the edge connector at the rear of the slot. (See Figure 9.)
Step 8 If you removed a port adapter, place it in an antistatic container for safe storage or shipment back to the factory. If you removed a blank port adapter, no special handling is required; store the blank port adapter for potential future use.
Step 9 Remove the new port adapter from its antistatic container and position it at the opening of the slot. (See Figure 10.)
| Caution To prevent jamming the carrier between the upper and lower edges of the port adapter slot, and to ensure that the edge connector at the rear of the port adapter mates with the connector at the rear of the port adapter slot, make certain that the leading edges of the carrier are between the upper and lower slot edges, as shown in Figure 10. |
Step 10 Before you insert the new port adapter in its slot, verify that the port adapter carrier is between the upper and lower slot edges, as shown in Figure 11. Do not jam the carrier between the slot edges.
| Caution To ensure a positive ground attachment between the port adapter carrier and the Catalyst VIP2 port adapter slot, and to ensure that the connectors at the rear of the port adapter slot mate properly with the port adapter, make certain the carrier is between the upper and lower slot edges, as shown in Figure 11. |
Step 11 Carefully slide the new port adapter into the port adapter slot until the connector on the port adapter completely mates with the connector on the motherboard.
Step 12 Install the screw in the rear of the port adapter slot (see Figure 8 for its location). Do not overtighten this screw.
Step 13 To replace the RSM/VIP2 combination in the chassis, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
Step 14 Reconnect the interface cables to the port adapter ports.
This completes the procedure for installing a new port adapter or replacing a port adapter in a Catalyst VIP2.
On a single 2CE1 port adapter, you can use up to two G.703 serial connections.
Connect a 2CE1 interface cable, as follows:
Step 1 Attach the cable directly to the receptacle on the 2CE1 port adapter and tighten the strain-relief screws. (See Figure 12.)
Step 2 Attach the network end of the cable to your PRI CSU and tighten the strain-relief screws.
This completes the procedure for attaching a 2CE1 interface cable.
Depending on the circumstances, you might need to change the configuration of both 2CE1 port adapter interfaces for balanced 120-ohm connections or unbalanced 75-ohm connections.
Configuring 2CE1 port adapter interfaces for balanced 120-ohm or unbalanced 75-ohm connections requires setting ten jumpers on the 2CE1 printed circuit board and attaching the appropriate interface cable (balanced or unbalanced) to both 2CE1 ports. Refer to the "2CE1 Port Adapter Cables and Pinouts" section on page 8 for 2CE1 interface cable types. The following steps explain how to set 2CE1 jumpers for balanced 120-ohm or unbalanced 75-ohm connections:
Step 1 Attach an ESD-preventive wrist strap between you and an unfinished chassis surface or to the ESD connector on the switch.
Step 2 Remove the RSM/VIP2 combination from the chassis. To do so, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
Step 3 Remove the installed 2CE1 port adapter from the Catalyst VIP2. Refer to the "Installing or Replacing a Port Adapter in a Catalyst VIP2" section for port adapter removal procedures.
Step 4 With the 2CE1 port adapter on an antistatic mat, use a number 1 Phillips screwdriver to remove the three screws that secure the plastic jumper cover to the 2CE1 printed circuit board. (See Figure 13.) Save the screws.
Step 5 Set the ten jumpers on the 2CE1 printed circuit board for balanced 120-ohm or unbalanced 75-ohm interface connections.
Jumper locations J2, J3, J5, J8, J9, J11, J12, and J14 have three pins, and jumper locations J4 and J10 have two pins. Each jumper location is configured by placing an insulated jumper over two pins (leaving the third pin of a three-pin jumper location exposed). In balanced 120-ohm configurations, the insulated jumper covers both pins of jumper locations J4 and J10. In unbalanced 75-ohm configurations, the insulated jumper is not present on jumper locations J4 and J10. Table 3 lists the 2CE1 jumper locations and their jumper settings. Figure 14 and Figure 15 show balanced 120-ohm and unbalanced 75-ohm 2CE1 jumper configurations, respectively.
| Balanced 120-Ohm Configuration | Unbalanced 75-Ohm Configuration | ||
|---|---|---|---|
| Jumper Location | Jumper Setting | Jumper Location | Jumper Setting |
J2 | Right two pins | J2 | Left two pins |
J3 | Right two pins | J3 | Left two pins |
J5 | Right two pins | J5 | Left two pins |
J8 | Right two pins | J8 | Left two pins |
J9 | Right two pins | J9 | Left two pins |
J11 | Right two pins | J11 | Left two pins |
J12 | Right two pins | J12 | Left two pins |
J14 | Right two pins | J14 | Left two pins |
J4 | Present | J4 | Not present |
J10 | Present | J10 | Not present |
Step 6 Replace the plastic jumper cover over the 2CE1 jumpers and secure it to the port adapter's printed circuit board using a number 1 Phillips screwdriver and the screws that you saved in Step 4.
Step 7 Reinstall the 2CE1 port adapter into the Catalyst VIP2. Refer to the "Installing or Replacing a Port Adapter in a Catalyst VIP2" section for port adapter replacement procedures.
Step 8 Replace the RSM/VIP2 combination in the chassis. To do so, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
This completes the procedure for configuring 2CE1 port adapter jumpers.
Use the show controller cbus command to identify the E1 cable type (balanced or unbalanced) attached to the 2CE1. An example of the show controller cbus command that shows an E1 interface port (1/0) with an unbalanced cable attached follows:
Router# show controller cbus
slot9: VIP2, hw 2.0, sw 22.20, ccb 5800FFB0, cmdq 480000C8, vps 8192
software loaded from system
IOS (tm) VIP Software (SVIP-DW-M), Version 11.2(0.201), BETA TEST SOFTWARE
ROM Monitor version 17.0
E1 1/0, applique is Channelized E1 - unbalanced
gfreeq 48000138, lfreeq 48000180 (1536 bytes), throttled 0
rxlo 4, rxhi 99, rxcurr 0, maxrxcurr 0
[display text omitted]
You modify the configuration of your router through the EXEC software command interpreter. 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 to 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:
Step 1 At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a privileged-level password:
Router> enable
Password:
Step 2 Enter the password (the password is case-sensitive). For security purposes, the password is not displayed.
Step 3 When you enter the correct password, the system displays the privileged-level system prompt (#):
Router#
If you installed a new 2CE1-equipped Catalyst VIP2 or if you want to change the configuration of an existing interface, you must use the privileged-level configure command. If you replaced a 2CE1 port adapter that was previously configured, the system recognizes the new 2CE1 port adapter interfaces and brings each of them up in their existing configuration.
After you verify that the new 2CE1 port adapter is installed correctly (the enabled LED goes on), use the configure command to configure the new interfaces. You will need the following information:
| Keywords by Area | Switch Type |
|---|---|
Australia
|
Australian TS013 switches |
Europe
|
German 1TR6 ISDN switches |
Japan
|
Japanese NTT ISDN switches |
North America
|
AT&T basic rate switches |
New Zealand
|
New Zealand NET3 switches |
For complete descriptions of interface subcommands and the configuration options available for the Catalyst VIP2-related interfaces, refer to the publications listed in the "If You Need More Information" section on page 2.
In the RSM, physical port addresses specify the actual physical location of each interface port on the Catalyst VIP2. This physical location is identified by interface type/port adapter slot/interface port number.
On the Catalyst VIP2, the first port adapter slot number is always 0; the second port adapter slot number is always 1. The individual interface port numbers always begin with 0. The number of additional ports depends on the number of ports on a port adapter.
For example, on the 2CE1-equipped Catalyst VIP2, the addresses for the interface ports are 0/0 through 0/1 (port adapter slot 0 and interface ports 0 through 1). If the port adapter was in port adapter slot 1, these same interface ports would be numbered 1/0 through 1/1.
You can identify interface ports by physically checking the port adapter interface port location on the Catalyst VIP2 or by using the show interface command to display information about a specific interface or all interfaces in the router.
Before you replace an interface cable, replace port adapters, or remove an interface that you will not replace, use the shutdown command to shut down (disable) the interfaces. Doing so prevents anomalies from occurring when you reinstall the new or reconfigured Catalyst VIP2. You can shut down all interfaces of a controller by specifying the controller before issuing the shutdown command. You can shut down individual interfaces of a controller by specifying the channel group or PRI group assigned to each controller (channel groups and PRI groups are treated as serial interfaces by the system). 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 1 Enter the privileged level of the EXEC command interpreter. (Refer to the "Using the EXEC Command Interpreter" section for instructions.)
Step 2 At the privileged-level prompt, enter Configuration mode and specify that the console terminal will be 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 Specify the port address of the controller that you want shut down by entering the subcommand controller, followed by the type (e1) and port adapter number/interface port number. The following example is for a 2CE1 in port adapter slot 1:
Router(config)# controller e1 1/0
Step 4 Enter the shutdown command, as follows:
Router(config-cont)# shutdown
Step 5 To shut down existing individual controller interfaces, enter the port:channel-group or PRI-group address of each interface followed by the shutdown command. When you have entered all the interfaces to be shut down, press CNTL/Z (hold down the Control key while you press Z) to exit Configuration mode and return to the EXEC command interpreter prompt, as follows:
Router(config)# int serial 1/0:0 Router(config-int)# shutdown CNTL/Z Router#
Step 6 Write the new configuration to memory, as follows:
Router# copy running-config startup-config [OK] Router#
The system displays an OK message when the configuration has been stored.
Step 7 To verify that new interfaces are now in the correct state (shutdown), use the show interface serial port adapter slot/interface port number/channel-group or pri-group command to display the specific interface, or use the show controller command, followed by the type (e1) and port adapter slot/interface port number, to display the status of all interfaces of the controller.
Router# show int serial 1/0:0 Serial1/0:0 is down, line protocol is down Hardware is cxBus E1 [display text omitted]
Step 8 To reenable the interfaces, repeat the previous steps, but use the no shutdown command in Step 4; then write the new configuration to memory, as follows:
Router(config)# int serial 1/0:0 Router(config-int)# no shutdown CNTL/Z Router# Router# copy running-config startup-config [OK] Router# show int serial 1/0:0 Serial1/0:0 is up, line protocol is up Hardware is cxBus E1 [display text omitted]
For complete descriptions of software configuration commands, refer to the publications listed in the "If You Need More Information" section on page 2.
Instructions follow for a basic channelized E1 configuration: enabling a controller 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, refer to the publications listed in the "If You Need More Information" section on page 2.
The channel groups must be mapped before the 2CE1 controller can be configured. The following controller commands are used to map the channel group (the default variable is listed first):
In the following procedure, press the Return key after each configuration step.
Step 1 At the privileged-level prompt, enter Configuration mode and specify that the console terminal will be the source of the configuration subcommands, as follows:
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Step 2 At the prompt, specify the controller to configure by entering the subcommand cont, followed by e1 and port adapter number/interface port number. The example that follows is for the 2CE1 in port adapter slot 1, interface port 1.
Router(config)# cont e1 1/1
Step 3 At the prompt, specify the framing type:
Router(config-controller)# framing crc4
Step 4 At the prompt, specify the line code format:
Router(config-controller)# linecode hdb3 Router(config-controller)# %CONTROLLER-3-UPDOWN: Controller e1 1/1, changed state to up Router(config-controller)#
Step 5 At the prompt, use the channel-group modification command to specify the channel group and time slots to be mapped. The following example shows channel group 0 and time slots 1, 3 through 5, and 7 selected for mapping.
Router(config-controller)# channel-group 0 timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on InterfacSerial1/1:0,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1:0, changed state to up Router(config-controller)#
Step 6 At the prompt, specify the interface type and port adapter number/interface port number:channel-group to modify:
Router(config-controller)# int serial 1/1:0
Step 7 If IP routing is enabled on the system, assign an IP address and subnet mask to the interface with the ip address configuration subcommand, as in the following example:
Router(config-int)# ip address 1.1.15.1 255.255.255.0 Router(config-int)#
Step 8 Add any additional configuration subcommands required to enable routing protocols and adjust the interface characteristics.
Step 9 Use the no shutdown commands to reenable the interfaces. Refer to the "Shutting Down an Interface" section for no shutdown command examples.
Step 10 To complete the configuration, enter CNTL/Z (hold down the Control key while you press Z) to exit Configuration mode.
Step 11 Write the new configuration to memory, as follows:
Router# write memory
The system displays an OK message when the configuration is stored.
Step 12 Exit the privileged level and return to the user level by entering disable at the prompt, as follows:
Router# disable Router>
This completes the procedure for creating a basic channelized E1 configuration. Proceed to the "Checking the Configuration" section to check the interface configuration using show commands. For additional information about configuring channelized E1 interfaces, refer to the publications Wide-Area Networking Configuration Guide and Wide-Area Networking Command Reference.
Following are instructions for a basic channelized E1 ISDN PRI configuration: enabling a controller 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, refer to the publications listed in the "If You Need More Information" section on page 2.
The PRI group must be mapped before the 2CE1 controller can be configured (there is only one PRI group for each controller). The following controller commands are used to map the PRI group:
In the following procedure, press the Return key after each configuration step.
Step 1 At the privileged-level prompt, enter Configuration mode and specify that the console terminal will be the source of the configuration subcommands, as follows:
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 2 Identify the ISDN switch type. In the following example, the switch primary-net5 (a switch for the European Community) is identified as the switch type:
Router(config)# isdn switch-type primary-net5
Step 3 At the prompt, specify the controller to configure by entering the subcommand cont, followed by e1 and port adapter number/interface port number. The following example is for the 2CE1 in port adapter slot 1, interface port 1.
Router(config)# cont e1 1/1
Step 4 At the prompt, specify the framing type:
Router(config-controller)# framing crc4
Step 5 At the prompt, specify the line code format:
Router(config-controller)# linecode hdb3 Router(config-controller)# %CONTROLLER-3-UPDOWN: Controller e1 1/1, changed state to up Router(config-controller)#
Step 6 At the prompt, use the pri-group modification command to specify the time slots to map. The following example shows PRI-group time slots 1, 3 through 5, and 7 (the B channels) selected and mapped to time slot 16 (the D channel), which is recognized by the system as time slot 15.
Router(config-controller)# pri-group timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on InterfacSerial1/1:15,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on InterfacSerial1/1:15,
changed state to up
Router(config-controller)#
Step 7 At the prompt, specify the interface type and port adapter number/interface port number:pri-group to modify (for channelized E1 ISDN PRI, the PRI group is configured by using time slot 16, which is recognized by the system as time slot 15).
Router(config-controller)# int serial 1/1:15
Step 8 If IP routing is enabled on the system, assign an IP address and subnet mask to the interface with the ip address configuration subcommand, as in the following example:
Router(config-int)# ip address 1.1.15.1 255.255.255.0 Router(config-int)#
Step 9 Add any additional configuration subcommands required to enable routing protocols and adjust the interface characteristics.
Step 10 Use the no shutdown commands to reenable the interfaces. Refer to the "Shutting Down an Interface" section for no shutdown command examples.
Step 11 To complete the configuration, enter CNTL/Z (hold down the Control key while you press Z) to exit Configuration mode.
Step 12 Write the new configuration to memory, as follows:
Router# write memory
The system displays an OK message when the configuration is stored.
Step 13 Exit the privileged level and return to the user level by entering disable at the prompt, as follows:
Router# disable Router>
This completes the procedure for creating a basic channelized E1 ISDN PRI configuration. Proceed to the "Checking the Configuration" section to check the interface configuration using show commands. For dialer interface configuration and additional channelized E1 ISDN PRI interface configuration information, refer to the publications Wide-Area Networking Configuration Guide and Wide-Area Networking Command Reference.
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces and the ping and loopback commands to check connectivity.
The following steps use show commands to verify that the new interfaces are configured and operating correctly:
Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new serial interfaces.
Step 2 Display the VIP2 and its interfaces with the show controllers cbus command.
Step 3 Specify one of the new E1 interfaces with the show interfaces interface type/port adapter slot/interface port number:channel-group or pri-group command and 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 show protocols command. If necessary, return to Configuration mode to add or remove protocol routing on the system or specific interfaces.
Step 5 Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM by using the show startup-config 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 bringing up the interface, contact a customer service representative for assistance.
To display information about a specific interface, use the show interfaces command with the interface type, port adapter slot, interface port number, and channel group or PRI group address in the format show interfaces (interface type /port adapter slot/interface port number:channel-group or pri-group).
The following example of the show interfaces serial port adapter slot/interface port number:channel-group command shows all the information specific to the first 2CE1 interface port (interface port 0) in port adapter slot 1, channel group 2:
Router# sh int serial 1/0:2
Serial1/0:2 is up, line protocol is up
Hardware is cxBus E1
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
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 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions alarm present
Timeslot(s) Used:1-31, Transmitter delay is 0 flags, transmit queue length 0
The following example of the show interfaces serial port adapter slot/interface port number:pri-group command shows all the information specific to the same interface port (interface port 0 in port adapter slot1) when the port is configured for ISDN PRI:
Router# sh int serial 1/0:15
Serial1/0:15 is up, line protocol is up (spoofing)
Hardware is cxBus E1
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
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 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions alarm present
Timeslot(s) Used:1-31, Transmitter delay is 0 flags, transmit queue length 0
Router# show version Cisco Internetwork Operating System Software IOS (tm) C5RSM Software (C5RSM-JSV-M), Version 11.2(9)P Copyright (c) 1986-1997 by cisco Systems, Inc. Compiled Tue 24-Jun-97 17:09 by shj Image text-base: 0x600108E0, data-base: 0x6095E000 ROM: System Bootstrap, Version 11.2(15707) BOOTFLASH: C5RSM Software (C5RSM-JSV-M), Version 11.2 yosemite_3 uptime is 17 hours, 17 minutes System restarted by reload System image file is "dirt/yosemite/c5rsm-jsv-mz.7P", booted via tftp from 223.255.254.254 cisco RSP2 (R4700) processor with 32768K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on G.703/E1 software, Version 1.0. SuperLAT software copyright 1990 by Meridian Technology Corp). Bridging software. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software. 1 C5IP controller (15 Vlan). 2 MIP controllers (4 E1). 1 VIP2 controller (2 E1)(4 Token Ring). 6 Channelized E1/PRI ports. 123K 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 0x100 Router#
To determine which type of port adapter is installed on the Catalyst VIP2 in your system, use the show diag command. The following example is for a 2CE1 port adapter in port adapter slot 1 with the ISDN switch type primary-net5:
Router# show isdn status
The current ISDN Switchtype = primary-net5
ISDN Serial1/0:15 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
ISDN Serial1/1:15 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Total Allocated ISDN CCBs = 0
(Display text omitted.)
To determine which type of port adapter is installed in the Catalyst VIP2 in your system, use the show diag command. Specific port adapter information is displayed, as shown in the following example of a 2CE1 port adapter:
Router# show diag
Slot 0:
Physical slot 0, ~physical slot 0xF, logical slot 0, CBus 1
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: Console I/O, Debug I/O
EEPROM format version 1
C5IP controler, HW rev 1.0, board revision A0
Serial number: 00000001 Part number: 00-0000-01
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 1C 01 00 00 00 00 01 00 00 00 01 00 00 00 00
0x30: 50 00 00 00 00 00 00 00 00 00 00 78 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0xFAC (17:24:40 ago)
Slot 7:
EEPROM format version 1
Route/Switch Processor 2, HW rev 1.0, board revision A0
Serial number: 00000001 Part number: 00-0000-01
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 1C 01 00 00 00 00 01 00 00 00 01 00 00 00 00
0x30: 50 00 00 00 00 00 00 00 00 00 00 78 00 00 00 00
.
.
.
.PA Bay 0 Information:
Token Ring PA, 4 ports
EEPROM format version 1
HW rev 1.0, Board revision B0
Serial number: 02825610 Part number: 73-1390-04
PA Bay 1 Information:
Multi-channel (E1) port adapter, 2 ports
EEPROM format version 255
HW rev FF.FF, Board revision UNKNOWN
Serial number: 4294967295 Part number: 255-65535-255
Use the show controllers cbus command to display the internal status of the interface processors and Catalyst VIP2, including hardware versions and the currently running microcode versions. The show controllers cbus command also lists each interface (port), including logical interface numbers, interface types, physical port addresses and hardware (station address) of each interface, and cable types attached to each interface.
The following example shows a 2CE1 port adapter installed in port adapter slot 1:
Router# show controller cbus
(additional displayed text omitted from this example)
slot9: VIP2, hw 2.0, sw 22.20, ccb 5800FFB0, cmdq 480000C8, vps 8192
software loaded from system
IOS (tm) VIP Software (SVIP-DW-M), Experimental Version 11.2(19970625:000938
) [shj-V112_7_P 102]
ROM Monitor version 17.0
E1 1/0, applique is Channelized E1 - unbalanced
gfreeq 48000138, lfreeq 48000180 (1536 bytes), throttled 0
rxlo 4, rxhi 99, rxcurr 0, maxrxcurr 0
[display text omitted]
Use the show controller e1 command to display the status of each installed E1 interface. The following example shows the status of a 2CE1 port adapter installed in port adapter slot 1 interface port 0:
Router# show cont e1
E1 1/0 is up.
Applique type is Channelized E1 - unbalanced
No far end block errors detected
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (700 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
10 Line Code Violations, 1 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins
1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
Total Data (last 1 15 minute intervals):
10 Line Code Violations, 1 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
E1 1/1 is up.
Applique type is Channelized E1 - unbalanced
No far end block errors detected
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (700 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
10 Line Code Violations, 1 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins
1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
Total Data (last 1 15 minute intervals):
10 Line Code Violations, 1 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
The ping and loopback commands allow you to verify that an interface port is functioning properly and to check the path between a specific port and connected devices at various locations on the network after the system has booted successfully and is operational. Refer to the publications listed in the "If You Need More Information" section on page 2 for detailed command descriptions and examples.
The ping command sends echo request packets to a remote device at an IP address that you specify. After sending an echo request, the command 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 that the connection failed.
An example of a successful ping command to a remote server with the address 1.1.1.10 follows:
Router# ping 1.1.1.10 <Return> Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 1.1.1.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.
The loopback test allows you to detect and isolate equipment malfunctions by testing the connection between the 2CE1 port adapter interface and a remote device such as a modem or a CSU. The loopback subcommand places an interface in loopback mode, which enables test packets that are generated from the ping command to loop through a remote device or interface cable. If the packets complete the loop, the connection is good. If not, you can isolate a fault to the remote device or interface cable in the path of the loopback test.
When no interface cable is attached to a 2CE1 port adapter interface, issuing the loopback controller command tests the path between the Catalyst VIP2 and the interface port only (without leaving the Catalyst VIP2 and port adapter).
For complete descriptions of interface subcommands and the configuration options available for Catalyst VIP2-related interfaces, refer to the publications listed in the "If You Need More Information" section on page 2.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Posted: Mon Jul 26 09:40:42 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.