|
|
To continue your PA-MC-2E1 or PA-MC-8E1 port adapter installation, you must configure the serial 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-MC-2E1 or PA-MC-8E1 is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. Have the following information available:
| Keywords by Area | Switch Type |
|---|---|
| Australia
basic-ts013 |
Australian TS013 switches |
| Europe
basic-1tr6 |
German 1TR6 ISDN switches |
| Japan
ntt |
Japanese NTT ISDN switches |
| North America
basic-5ess |
Lucent basic rate switches |
| New Zealand
basic-nznet3 |
New Zealand NET3 switches |
If you installed a new PA-MC-2E1 or PA-MC-8E1 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-MC-2E1 or PA-MC-8E1 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-MC-2E1 or PA-MC-8E1, 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 compact serial 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-2 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 and interface 1 on a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0 Router(config-if)# shutdown Router(config-if)# interface serial 1/1 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 and interface 1 on a port adapter in port adapter slot 6. Router(config-if)# interface serial 6/0 Router(config-if)# shutdown Router(config-if)# interface serial 6/1 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 and interface 1 on a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0 Router(config-if)# shutdown Router(config-if)# interface serial 1/1 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 and interface 1 on a port adapter in port adapter slot 2. Router(config-if)# interface serial 2/0 Router(config-if)# shutdown Router(config-if)# interface serial 2/1 Router(config-if)# shutdown Ctrl-Z Router# |
VIP2 or VIP4 in Cisco 7000 series or Cisco 7500 series routers | interface, followed by the type (serial) and slot/port adapter/port (interface-processor-slot-number/ | The example is for interface 1 and interface 0 on a port adapter in port adapter slot 1 of a VIP2 installed Router(config-if)# interface serial 1/1/1 Router(config-if)# shutdown 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-3 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 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/interface-port-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 or VIP4 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 first interface to configure by entering the interface serial subcommand, followed by the interface address of the interface you plan to configure. Table 4-4 provides examples.
| Platform | Command | Example |
|---|---|---|
Catalyst RSM/VIP2 in Catalyst 5000 family switches | interface serial, followed by slot/port (port-adapter-slot-number/ | The example is for the first interface of a port adapter in port adapter slot 0. Router(config)# interface serial 0/0 Router(config-if)# |
Cisco 7200 series routers | interface serial, followed by slot/port (port-adapter-slot-number/ | The example is for the first interface of a Router(config)# interface serial 6/0 Router(config-if)# |
Cisco uBR7223 router | interface serial, followed by slot/port (port-adapter-slot-number/ | The example is for the first interface of a Router(config)# interface serial 1/0 Router(config-if)# |
Cisco BR7246 router | interface serial, followed by slot/port (port-adapter-slot-number/ | The example is for the first interface of a Router(config)# interface serial 2/0 Router(config-if)# |
VIP2 or VIP4 in Cisco 7000 series or Cisco 500 series routers | interface serial, followed by slot/port adapter/port (interface-processor-slot-number/ | The example is for the first interface of a Router(config)# interface serial 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 In interface configuration mode, set the encapsulation used by the interface by entering the encapsulation {frame-relay | hdlc | ppp | smds | x25} configuration subcommand, as in the following example:
router(config-if)# encapsulation ppp
Step 5 In interface configuration mode, set the description by entering the description line (up to 80 characters describing this controller) configuration subcommand, as in the following example:
router(config-if)# description PPP channel 5
Step 6 At the privileged-level prompt, enter configuration mode and choose a E1 controller:
Router(config)# controller E1 1/0/0 (VIP2) Router(config)# controller E1 /0/0 (Catalyst RSM/VIP2) Router(config)# controller E1 1/0 (Cisco 7200 series router) Router(config)# controller E1 1/0 (Cisco uBR7200 series router)
|
Note For E1 controller examples, see the Controller Configuration Examples. |
Step 7 Change to controller configuration mode and use the framing [CRC4 | no-CRC4] configuration subcommand to set the framing format, as in the following example:
router(config-controller)# framing crc4
Use the no form of this command to restore the default, CRC4.
Step 8 In controller configuration mode, use the clock source [internal | line] configuration subcommand to set the clock source, as in the following example:
router(config-controller)# clock source internal
Use the no form of this command to restore the default, line.
Step 9 In controller configuration mode, use the channel-group number timeslots value configuration subcommand to set the channel group, as in the following example:
router(config-controller)# channel-group 0 timeslots 1-31
|
Note The channel-group number can be from 0 to 30, and the time slot value can be from 1 to 31. |
Step 10 To use an E1 port as unframed, in controller configuration mode, use the channel-group number unframed configuration subcommand to set the channel group, as in the following example:
router(config-controller)# channel-group 0 unframed
Step 11 In controller configuration mode, use the pri-group timeslots value configuration subcommand to set the pri group, as in the following example:
router(config-controller)# pri-group timeslots 1-31
Step 12 In controller configuration mode, use the description line (up to 80 characters describing this controller) configuration subcommand to set the description, as in the following example:
router(config-controller)# description Arizona 3 Router; location: building 2
Step 13 In controller configuration mode, use the shutdown configuration subcommand to shut down the controller, as in the following example:
router(config-controller)# shutdown
|
Note When the multichannel E1/PRI port adapter is being used with AMI encoding, it must be configured as 64k or invert data mode. |
To exit controller configuration mode and return to global configuration mode, enter the exit command.
Step 14 Reenable the interfaces using the no shutdown command. (See the "Shutting Down an Interface" section.)
Step 15 Configure all additional port adapter interfaces as required. See the "Configuring Multichannel E1 Interfaces" section, "Configuring Multichannel E1 ISDN PRI Interfaces" section and related "Specifying E1 Framing" section and "Defining National Reserve Bit" section for instructions and information.
Step 16 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 17 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.
The following example shows a typical controller configuration for the multichannel E1/PRI port adapter on a Catalyst RSM/VIP2:
router>enablerouter#configure terminalrouter(config)#controller E1 0/0router(config-controller)#framing crc4router(config-controller)#linecode hdb3router(config-controller)#clocksource internalrouter(config-controller)#channel-group 0 timeslots 1-31router(config-controller)#description ppp channel 5router(config-controller)#shutdownrouter(config-controller)#^Z
The following example shows a typical controller configuration for the multichannel E1/PRI port adapter on a Cisco 7200 series or Cisco uBR7200 series router:
router>enablerouter#configure terminalrouter(config)#controller E1 1/0router(config-controller)#framing crc4router(config-controller)#linecode hdb3router(config-controller)#clocksource internalrouter(config-controller)#channel-group 0 timeslots 1-31router(config-controller)#description ppp channel 5router(config-controller)#shutdownrouter(config-controller)#^Z
The following example shows a typical controller configuration for the multichannel E1/PRI port adapter on a Cisco 7500 series router:
router>enablerouter#configure terminalrouter(config)#controller E1 1/0/0router(config-controller)#framing crc4router(config-controller)#linecode hdb3router(config-controller)#clocksource internalrouter(config-controller)#channel-group 0 timeslots 1-31router(config-controller)#description ppp channel 5router(config-controller)#shutdownrouter(config-controller)#^Z
To check the interface configuration using show commands, see the "Using show Commands to Verify the New Interface Status" section.
The following example shows a typical interface configuration for the multichannel E1/PRI port adapter on a Catalyst RSM/VIP2:
router> enable router# configure terminal router(config)# interface serial router(config)# interface serial 1/0:0 router(config-if)# encapsulation ppp router(config-if)# description ppp channel 5 router(config-if)# no shutdown router(config-if)# ^Z
The following example shows a typical interface configuration for the multichannel E1/PRI port adapter on a Cisco 7200 series or Cisco uBR7200 series router:
router> enable router# configure terminal router(config)# interface serial router(config)# interface serial 4/1:0 router(config-if)# encapsulation ppp router(config-if)# description ppp channel 5 router(config-if)# no shutdown router(config-if)# ^Z
The following example shows a typical interface configuration for the multichannel E1/PRI port adapter on a Cisco 7500 series router:
router> enable router# configure terminal router(config)# interface serial router(config)# interface serial 4/1/0:0 router(config-if)# encapsulation ppp router(config-if)# description ppp channel 5 router(config-if)# no shutdown router(config-if)# ^Z
The customizable features of the E1/PRI port adapter have default values that will probably suit your environment and not need to be changed. However, you might need to enter configuration commands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. Perform the tasks in the following sections if you need to customize the E1/PRI port adapter:
Following are instructions for a basic multichannel 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 "Related Documentation" section.
The channel groups must be mapped before the multichannel E1/PRI controller can be configured. The following are controller commands used to map the channel group (the default variable is listed first):
|
Note Cisco 7000 and Cisco 7500 series routers identify channel groups as serial interfaces by chassis slot number, port adapter (0 or 1), port number (0 or 1), and channel-group number (0 to 30). For example, the address of the multichannel E1/PRI port adapter installed in chassis slot 4, port adapter slot 1, port 1, and channel group 5, is serial 4/1/1:5. |
|
Note The Catalyst RSM/VIP2 identifies channel groups as serial interfaces by port adapter (0 or 1), port number (0 or 1), and channel-group number (0 to 30). For example, the address of the multichannel E1/PRI port adapter installed in port adapter slot 1, port 1, and channel group 5, is serial 1/1:5. The Catalyst RSM/VIP2 supports only the PA-MC-8E1/120 multichannel E1/PRI port adapter. |
|
Note Cisco 7200 series and Cisco uBR7200 series routers identify the PRI group as a serial interface by port adapter slot number, port number (0 or 1), and time slot 30. For example, the address of the multichannel E1/PRI port adapter installed in port adapter slot 1, port 1, and time slot 31, is recognized by the system as serial 1/1:30. |
In the following procedure, press the Return key after each configuration step:
Router# configure terminal
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 controller, followed by E1, and chassis-slot-number/port-adapter-number/port-number (for VIP2 or VIP4), port-adapter-number/port-number (for Catalyst RSM/VIP2), or port-adapter-slot-number/port-number (for Cisco 7200 series and Cisco uBR7200 series routers).
The example that follows is for the multichannel E1/PRI port adapter on a Cisco 7500 series router in chassis slot 3, port adapter slot 1, port 1:
Router(config)# controller E1 3/1/1
The example that follows is for the multichannel E1/PRI port adapter on a Catalyst RSM/VIP2 in port adapter slot 1, port 1:
Router(config)# controller E1 1/1
The example that follows is for the multichannel E1/PRI port adapter on a Cisco 7200 series or Cisco uBR7200 series router in port adapter slot 1, port 1:
Router(config)# controller E1 1/1
Step 3 At the prompt, specify the clock source for the controller. The clock source command determines which end of the circuit provides the clocking signal.
Router(config-controller)# clock source line
|
Note You can set the clock source to use internal clocking for testing purposes. One end of a T1 circuit must provide the clock source. |
Step 4 At the prompt, specify the framing type:
Router(config-controller)# framing crc4
Step 5 At the prompt, specify the linecode format:
Router(config-controller)# linecode hdb3 Router(config-controller)#
Step 6 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.
For the VIP2 or VIP4 on a Cisco 7200 or Cisco 7500 series router:
Router(config-controller)# channel-group 0 timeslots 1,3-5,7 Router(config-controller)# %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/1:0, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/1:0,
changed state to up
Router(config-controller)#
For the Catalyst RSM/VIP2:
Router(config-controller)# channel-group 0 timeslots 1,3-5,7 Router(config-controller)# %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1:0, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1:0,
changed state to up
Router(config-controller)#
For the Cisco 7200 series and Cisco uBR7200 series routers:
Router(config-controller)# channel-group 0 timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1:0,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1:0,
changed state to up
Router(config-controller)#
Step 7 At the prompt, specify the interface serial type, and chassis-slot-number/port-adapter-number/port number:channel-group (VIP2 or VIP4) or port-adapter-slot-number/port-number (Cisco 7200 series and Cisco uBR7200 series router) to modify:
Router(config-controller)# interface serial 3/1/1:0 (VIP2) Router(config-controller)# interface serial 1/1:0 (Catalyst RSM/VIP2) Router(config-controller)# interface serial 3/1:0 (Cisco 7200 series router) Router(config-controller)# interface serial 3/1:0 (Cisco uBR7200 series router)
Step 8 At the prompt, 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 other configuration subcommands required to enable routing protocols and adjust the interface characteristics.
Step 10 Use the no shutdown commands to reenable the interfaces. See the "Customizing the Multichannel E1/PRI Port Adapter" section, for no shutdown command examples.
Step 11 After including all of the configuration subcommands, to complete the configuration, enter Ctrl-Z-- hold down the Control key while you press Z-- to exit configuration mode.
Step 12 Write the new configuration to memory:
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:
Router# disable Router>
This completes the procedure for creating a basic channelized E1 configuration. See 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 multichannel 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 "Related Documentation" section.
Table 4-5 and following information and examples provide information about ISDN PRI port configuration restrictions.
| Router Platform | Port Adapter | Number of PRI Groups Allowed Per Port Adapter | Maximum Number of Timeslots Allowable Per Port Adapter | PRI-Groups Allowable Per Router |
|---|---|---|---|---|
7200 | PA-MC-8E1 | See information and examples below. | 128 | 48 |
7200 VXR | PA-MC-8E1 | See information and examples below. | 128 | 48 |
7500 | PA-MC-8E1 | See information and examples below. | 128 | Both port adapters: 20 with Cisco IOS 11.2 release and Cicso IOS 11.1CA release |
Rules for determining the allowable number of PRI groups per port adapter:
|
Note When a port adapter is running channelized E1, there are no port restrictions. |
The PRI group must be mapped before the multichannel E1/PRI controller can be configured (there is only one PRI group for each controller). The following are controller commands used to map the PRI group:
|
Note If you do not specify the time slots, the controller is configured for 30 B channels (time slots 1 to 15 and 16 to 31) and one D channel (time slot 16). |
|
Note Cisco 7000 and Cisco 7500 series routers identify the PRI group as a serial interface by chassis slot number, port adapter slot (0 or 1), port number (0 or 1), and time slot 30. For example, the address of the multichannel E1/PRI port adapter installed in chassis slot 4, port adapter slot 1, port 1, and time slot 31, is recognized by the system as serial 4/1/1:31. |
|
Note The Catalyst RSM/VIP2 identifies the PRI group as a serial interface by port adapter slot (0 or 1), port number (0 or 1), and time slot 30. For example, the address of the multichannel E1/PRI port adapter installed in port adapter slot 1, port 1, and time slot 31, is recognized by the system as serial 1/1:31. The Catalyst RSM/VIP2 supports only the PA-MC-8E1/120 multichannel E1/PRI port adapter. |
|
Note Cisco 7200 series and Cisco uBR7200 series routers identify the PRI group as a serial interface by port adapter slot number, port number (0 or 1), and time slot 30. For example, the address of the multichannel E1/PRI port adapter installed in port adapter slot 1, port 1, and time slot 31, is recognized by the system as serial 1/1:30. |
In the following procedure for a basic multichannel E1 ISDN PRI configuration, press Return after each configuration step:
Router# configure terminal
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-5ess (a switch for the United States) is identified as the switch type:
Router(config)# isdn switch-type primary-5ess
|
Note The ISDN switch type that you identify is for all ISDN ports installed in the router. |
Step 3 At the prompt, specify the controller to configure by entering the subcommand controller, followed by E1, and chassis-slot-number/port-adapter-number/port-number (VIP2 or VIP4), port-adapter-number/port-number (Catalyst RSM/VIP2), or port-adapter-slo-number/port-number (Cisco 7200 series and Cisco uBR7200 series router).
The example that follows is for the multichannel E1/PRI port adapter on a VIP2-equipped Cisco 7500 series router in chassis slot 3, port adapter slot 1, port 1:
Router(config)# controller E1 3/1/1
The example that follows is for the multichannel E1/PRI port adapter on a Catalyst RSM/VIP2, port adapter slot 1, port 1:
Router(config)# controller E1 1/1
The example that follows is for the multichannel E1/PRI port adapter in a Cisco 7200 series or Cisco uBR7200 series router in port adapter slot 1, port 1:
Router(config)# controller E1 1/1
Step 4 At the prompt, specify the clock source for the controller. The clock source command determines which end of the circuit provides the clocking signal.
Router(config-controller)# clock source line
|
Note You can set the clock source to use internal clocking for testing purposes. One end of a T1 circuit must provide the clock source. |
Step 5 At the prompt, specify the framing type:
Router(config-controller)# framing crc4
Step 6 At the prompt, specify the linecode format:
For the VIP2 or VIP4 on a Cisco 7200 or Cisco 7500 series router:
Router(config-controller)# linecode hdb3 Router(config-controller)# %CONTROLLER-3-UPDOWN: Controller E1 3/1/1, changed state to up Router(config-controller)#
For the Catalyst RSM/VIP2:
Router(config-controller)# linecode hdb3 Router(config-controller)# %CONTROLLER-3-UPDOWN: Controller E1 1/1, changed state to up Router(config-controller)#
For the Cisco 7200 series and Cisco uBR7200 series routers:
Router(config-controller)# linecode hdb3 Router(config-controller)# %CONTROLLER-3-UPDOWN: Controller E1 3/1, changed state to up Router(config-controller)#
Step 7 At the prompt, use the pri-group modification command to specify the time slots to map. The following examples show PRI-group time slots 1, 3 through 5, and 7 (the B channels) selected and mapped to time slot 31 (the D channel), which is recognized by the system as time slot 30.
For the VIP2 or VIP4 on a Cisco 7200 or Cisco 7500 series router:
Router(config-controller)# pri-group timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/1:30,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/1:30,
changed state to up
Router(config-controller)#
For the Catalyst RSM/VIP2:
Router(config-controller)# pri-group timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1:30,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1:30,
changed state to up
Router(config-controller)#
For the Cisco 7200 series and Cisco uBR7200 series routers:
Router(config-controller)# pri-group timeslots 1,3-5,7
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1:30,
changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1:30,
changed state to up
Router(config-controller)#
|
Note In the above examples, the line-protocol status for time slot 31 (listed in the output as time slot 30) represents the entire PRI group. |
Step 8 At the prompt, specify the interface serial type and appropriate address. For multichannel E1 ISDN PRI, the PRI group is configured using time slot 31, which is recognized by the system as time slot 30.
Router(config-controller)# interface serial 3/1/1:30 (VIP2) Router(config-controller)# interface serial 1/1:30 (Catalyst RSM/VIP2) Router(config-controller)# interface serial 3/1:30 (Cisco 7200 series router) Router(config-controller)# interface serial 3/1:30 (Cisco uBR7200 series router)
Step 9 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 10 Add any other configuration subcommands required to enable routing protocols and adjust the interface characteristics.
Step 11 Use the no shutdown command to reenable the interfaces.
Step 12 After including all of the configuration subcommands, to complete the configuration, enter Ctrl-Z--hold down the Control key while you press Z--to exit configuration mode.
Step 13 Write the new configuration to memory:
Router# write memory
The system displays an OK message when the configuration is stored.
Step 14 Exit the privileged level and return to the user level by entering disable at the prompt:
Router# disable Router>
This completes the procedure for creating a basic multichannel E1 ISDN PRI configuration. See the "Checking the Configuration" section to check the interface configuration using show commands. For dialer interface configuration and additional multichannel E1 ISDN PRI interface configuration, refer to the publications Wide-Area Networking Configuration Guide and Wide-Area Networking Command Reference.
In controller configuration mode, specify E1 framing by entering the framing {crc4 | no-crc4} configuration subcommand, as in the following example:
router(config-controller)# framing crc4
Use the no form of this command to return to the default, CRC4 framing.
In interface configuration mode, define national reserve bit in G.703 frame by entering the national reserve [0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1] configuration subcommand, as in the following example:
router(config-if)# national reserve 0 1 1 0 1 1
Use the no form of this command to return to the default, which is all 0s.
To check the interface configuration using show commands see "Checking the Configuration" section.
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces. See "Using show Commands to Verify the New Interface Status" section. Use the ping and loopback commands to check connectivity. See "Using the ping Command to Verify Network Connectivity" section and "Using loopback Commands" section .
Table 4-6 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the PA-MC-2E1 and PA-MC-8E1 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 type 0 or 1/ | Displays status information about a specific type of interface (for example, serial) on a Catalyst RSM/VIP2 | Router# show interfaces serial 1/0 | ||
show interfaces type 3/interface-port- | Displays status information about a specific type of interface (for example, serial) in a Cisco 7120 series router | Router# show interfaces serial 3/1 | ||
show interfaces type 4/interface-port- | Displays status information about a specific type of interface (for example, serial) in a Cisco 7140 series router | Router# show interfaces serial 4/1 | ||
show interfaces type port-adapter-slot-number/ | Displays status information about a specific type of interface (for example, serial) in a Cisco 7200 series router | Router# show interfaces serial 1/0 | ||
show interfaces type 1/interface-port- | Displays status information about a specific type of interface (for example, serial) in a Cisco uBR7223 router | Router# show interfaces serial 1/1 | ||
show interfaces type 1 or 2/ | Displays status information about a specific type of interface (for example, serial) in a Cisco uBR7246 router | Router# show interfaces serial 2/0 | ||
show interfaces type interface-processor- | Displays status information about a specific type of interface (for example, serial) 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 to Verify Network Connectivity" section when you have finished using the show commands.
Display the configuration of the system hardware, the number of each interface type installed, the Cisco IOS software version, the names and sources of configuration files, and the boot images, using the
show version (or show hardware) command.
|
Note The 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 version command from a Catalyst 5000 family switch with the PA-MC-2E1 or PA-MC-8E1:
Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-PV-M), Version 12.0(3)T Synced to mainline version: 11.1(13.5)CA Copyright (c) 1999 by cisco Systems, Inc. Compiled Mon 24-Nov-97 23:59 Image text-base: 0x60010900, data-base: 0x60708000 ROM: System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM SOFTWARE ROM: GS Software (RSP-BOOT-M), Version 11.1(8)CA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) potent7505-1 uptime is 5 hours, 30 minutes System restarted by reload System image file is "potent/rsp-pv-mz.DTP7", booted via tftp from 171.69.209.28 cisco RSP1 (R4700) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on G.703/E1 software, Version 1.0. G.703/JT2 software, Version 1.0. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. Chassis Interface. 2 VIP2 controllers (8 Ethernet)(8 E1). 8 Ethernet/IEEE 802.3 interfaces. 3 Serial network interfaces. 8 multichannel E1/PRI ports. 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 with the PA-MC-2E1 or PA-MC-8E1:
Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (7200-PV-M), Version 11.1(20)CC Synced to mainline version: 11.1(13.5)CA Copyright (c) 1986-1997 by cisco Systems, Inc. Compiled Mon 24-Nov-97 23:59 Image text-base: 0x60010900, data-base: 0x60708000 ROM: System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM SOFTWARE ROM: GS Software (C7200-BOOT-M), Version 11.1(8)CA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) router uptime is 5 hours, 30 minutes System restarted by reload System image file is "c7200-mz.DTP7", booted via tftp from 171.69.209.28 cisco 7206 (NPE150) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on G.703/E1 software, Version 1.0. G.703/JT2 software, Version 1.0. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. Chassis Interface. 8 Ethernet/IEEE 802.3 interfaces. 3 Serial network interfaces. 8 Channelized E1/PRI ports. 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 7500 series router with the PA-MC-2E1 or PA-MC-8E1:
Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-PV-M), Version 11.1(20)CC Synced to mainline version: 11.1(13.5)CA Copyright (c) 1986-1997 by cisco Systems, Inc. Compiled Mon 24-Nov-97 23:59 Image text-base: 0x60010900, data-base: 0x60708000 ROM: System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM SOFTWARE ROM: GS Software (RSP-BOOT-M), Version 11.1(8)CA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) potent7505-1 uptime is 5 hours, 30 minutes System restarted by reload System image file is "potent/rsp-pv-mz.DTP7", booted via tftp from 171.69.209.28 cisco RSP1 (R4700) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on G.703/E1 software, Version 1.0. G.703/JT2 software, Version 1.0. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. Chassis Interface. 2 VIP2 controllers (8 Ethernet)(8 E1). 8 Ethernet/IEEE 802.3 interfaces. 3 Serial network interfaces. 8 multichannel E1/PRI ports. 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
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 7100 series, 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.
|
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. |
|
Note The slot argument is not required for Catalyst 5000 family switches. |
Following is an example of the show diag command that shows a PA-MC-2E1 or PA-MC-8E1 on a
Catalyst RSM/VIP2:
Router# show diag
Slot 0:
Physical slot 0, ~physical slot 0xD, logical slot 0, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP2 controller, HW rev 2.4, board revision D0
Serial number: 04371939 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7500
EEPROM contents (hex):
0x20: 01 15 02 04 00 42 B5 E1 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x14A4 (00:23:00 ago)
Following is an example of the show diag slot command that shows a PA-MC-2E1 or PA-MC-8E1 in port adapter slot 1 of a Cisco 7200 series router:
Router# show diag 1
Slot 1:
Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
Serial number: 04540965 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 15 02 04 00 45 4A 25 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x147C (05:33:22 ago)
Controller Memory Size: 32 MBytes DRAM, 2048 KBytes SRAM
PA Bay 0 Information:
Ethernet PA, 4 ports
EEPROM format version 1
HW rev 1.C, Board revision A0
Serial number: 04953593 Part number: 73-1556-07
PA Bay 1 Information:
Multi-channel (E1) PA, 8 ports
EEPROM format version 0
HW rev FF.FF, Board revision UNKNOWN
Serial number: 4294967295 Part number: 255-65535-255
|
Note Port adapters used with Cisco 7200 VXR routers require the correct base hardware revision in order to function. The following error message occurs on bootup if the incorrect hardware revision is used: > PA-3-REVNOTSUPPORTED:PA in slot 1 (Ethernet) requires base h/w revision of (1.14) for this chassisUse the show diag command to display the hardware revision. |
Following is an example of the show diag slot command that shows a PA-MC-2E1 or PA-MC-8E1 in port adapter slot 0 on a VIP2 in interface processor slot 1:
Router# show diag 2
Slot 2:
Physical slot 2, ~physical slot 0xD, logical slot 2, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP2 controller, HW rev 2.4, board revision D0
Serial number: 04371939 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7500
EEPROM contents (hex):
0x20: 01 15 02 04 00 42 B5 E1 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x14A4 (00:23:00 ago)
Controller Memory Size: 32 MBytes DRAM, 2048 KBytes SRAM
PA Bay 0 Information:
E1/PRI PA, 1 port
EEPROM format version 1
HW rev 1.00, Board revision AO
Serial number: 3549502 Part number: 73-2620-02
For complete descriptions of interface subcommands and the configuration options available for Catalyst RSM/VIP2 series, Cisco 7200 series, Cisco uBR7200 series, and VIP2 or VIP4 series 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. |
The following example example of the show interfaces serial command shows all of the information specific to the first multichannel E1/PRI port (port 0) on a Catalyst RSM/VIP2, port adapter slot 1, channel group 2:
Router# show interface serial 1/0:2
Serial1/0:2 is down, line protocol is down
Hardware is Multichannel E1
Internet address is 1.1.1.10/30
MTU 1500 bytes, BW 1344 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 04:18:08, output 04:18:08, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
523 packets input, 39030 bytes, 0 no buffer
Received 513 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
523 packets output, 40076 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions alarm present
Timeslot(s) Used: 1-31, Transmitter delay is 0 flags, transmit queue length 24
|
Note Interfaces are administratively shut down until you enable them. |
The following example of the show interfaces serial command shows all of the information specific to the same port on a Catalyst RSM/VIP2 (port 0 in port adapter slot 1) when the port is configured for ISDN PRI:
Router# show interface serial 1/0:30
Serial1/0:30 is up, line protocol is up(spoofing)
Hardware is Multichannel E1
MTU 1500 bytes, BW 64Kbit, 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:31, Transmitter delay is 0 flags, transmit queue length 0
|
Note In the above examples, the term "spoofing" indicates that the interface is configured for ISDN PRI. The term"spoofing" is indicated only on time slot 31 (the D channel), which is recognized by the system as time slot 30. |
Following is an example of the show interfaces serial port-adapter-slot-number/port-number:channel-group command for Cisco 7200 series and Cisco uBR7200 series routers. It shows all of the information specific to the first multichannel E1/PRI port (port 0) in port adapter slot 2, channel group 1:
Router# show interfaces serial 2/0:1
Serial2/0:1 is up, line protocol is up (looped)
Hardware is Multichannel E1
Internet address is 1.6.0.1/30
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 00:00:07, output 00:00:07, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
87 packets input, 6521 bytes, 0 no buffer
Received 87 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
87 packets output, 6521 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions
no alarm present
Timeslot(s) Used:1-31, subrate: 64Kb/s, transmit delay is 0 flags
|
Note Interfaces are administratively shut down until you enable them. |
Use the show controllers E1 port-adapter-slot-number/port-number command to display the status of each installed E1 interface. The following example of the show controllers E1 command shows the status of a multichannel E1/PRI port adapter installed in port adapter slot 1, port 0:
Router# show controllers E1 1/0
E1 1/0 is up.
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (710 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:
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
[display text omitted]
To display all the ISDN interfaces installed in the router and the ISDN switch type for the interfaces, use the show isdn status command. The following example is for a multichannel E1/PRI port adapter in port adapter slot 5, with the ISDN switch type primary-4ess:
Router# show isdn status
The current ISDN Switchtype = primary-4ess
ISDN Serial5/6:30 interface
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
TEI = 0, State = TEI_ASSIGNED
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
ISDN Serial5/7:30 interface
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
TEI = 0, State = TEI_ASSIGNED
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 1 CCBs = 0
Router# show interfaces serial 3/1/0:2
Serial3/1/0:2 is down, line protocol is down
Hardware is Multichannel E1
Internet address is 1.1.1.10/30
MTU 1500 bytes, BW 1344 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 04:18:08, output 04:18:08, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
523 packets input, 39030 bytes, 0 no buffer
Received 513 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
523 packets output, 40076 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions alarm present
Timeslot(s) Used: 1-31, Transmitter delay is 0 flags, transmit queue length 24
The following example of the show interfaces serial command shows all of the information specific to the same port on a VIP2- or VIP4-equipped Cisco 7500 series router (port 0 in chassis slot 3, port adapter slot 1) when the port is configured for ISDN PRI:
Router# show interfaces serial 3/1/0:30
Serial3/1/0:30 is up, line protocol is up(spoofing)
Hardware is Multichannel E1
MTU 1500 bytes, BW 64Kbit, 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:31, Transmitter delay is 0 flags, transmit queue length 0
(Additional displayed text omitted from this example.)
|
Note In the above examples, the term "spoofing" indicates that the interface is configured for ISDN PRI. The term" spoofing" is indicated only on time slot 31 (the D channel), which is recognized by the system as time slot 30. |
Proceed to "Using the ping Command to Verify Network Connectivity," to check network connectivity of the PA-MC-2E1 or PA-MC-8E1 and switch or router.
Following are suggested guidelines for troubleshooting the multichannel E1/PRI port adapter using the ping and loopback commands, cyclic redundancy checks, LED indications, a bit error rate test (BERT), and FDL performance reports, and for displaying remote performance reports. This section includes the following subsections:
Using the ping command, you can verify that an interface port is functioning properly. This section provides a brief description of this command. Refer to the publications listed in the "Related Documentation" section for detailed command descriptions and examples.
The ping command sends echo request packets out to a remote device at an IP address that you specify. After sending an echo request, the system waits a specified time for the remote device to reply. Each echo reply is displayed as an exclamation point (!) on the console terminal; each request that is not returned before the specified timeout is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate a bad connection.
Following is an example of a successful ping command to a remote server with the address 10.0.0.10:
Router# ping 10.0.0.10 <Return> Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 10.0.0.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms Router#
If the connection fails, verify that you have the correct IP address for the destination and that the device is active (powered on), and repeat the ping command.
Proceed to "Using loopback Commands ," to finish checking network connectivity.
The E1/PRI port adapter 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 sending 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 and sends a request to the sender to resend the frame.
|
Note To enable 32-bit CRC on an interface, follow steps 1 and 2 of the preceding procedure (enter configuration mode and specify the slot and port address of the E1/PRI port adapter), and then enter the command crc 32. Enter Ctrl-Z to exit from configuration mode. |
In the example that follows, a single E1/PRI interface, on a VIP2 or VIP4 in interface processor slot 1, is configured for 32-bit CRC:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# router(config)# interface serial 1/0/0:0 router(config-if)# crc 32 Ctrl-z
In the example that follows, a single E1/PRI interface, on a Catalyst RSM/VIP2, is configured for 32-bit CRC:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# router(config)# interface serial 0/0:0 router(config-if)# crc 32 Ctrl-z
In the example that follows, a single E1/PRI interface, on a Cisco 7206 router in slot 1, is configured for 32-bit CRC:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# router(config)# interface serial 1/0:0 router(config-if)# crc 32 Ctrl-z
To disable CRC-32 and return to the default CRC-16 setting, specify the slot and port address and use the no crc 32 command. For complete command descriptions and instructions, refer to the related software documentation.
|
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 cause the outgoing HDLC data stream to be inverted, use the invert data (enter configuration mode) as in the following example on a Cisco 7206 router:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# router(config)# interface serial 1/0:0 router(config-if)# invert data Ctrl-z
To check the interface configuration using show commands, refer to the "Checking the Configuration" section.
Should you have difficulty with the multichannel E1/PRI port adapter configuration or installation, you can troubleshoot the multichannel E1/PRI port adapter using the loopback command. Specify loopback for a E1 controller using the loopback command. There are two main loopback modes: diagnostic and local (line and payload). Specify the loopback format using the loopback [diagnostic | local] command.
|
Note To shut down the E1 controller, use the shutdown command at the controller prompt. |
Examples of specific loopback modes for the E1 controller follow:
loopback[diagnostic]
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/2/0 Router(config-controller)# loopback diagnostic
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/0 Router(config-controller)# loopback diagnostic
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/0 Router(config-controller)# loopback diagnostic
loopback[local{payload|line}]
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/2/0 Router(config-controller)# loopback local payload
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/0 Router(config-controller)# loopback local payload
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# controller E1 2/0 Router(config-controller)# loopback local payload
The multichannel E1/PRI port adapter has one status LED per port. Table 4-7 lists various system states and functions that are reflected by the front-panel status LEDs on the multichannel E1/PRI port adapter during the CPU boot process and microcode download.
| LED Color | State | Description |
|---|---|---|
Yellow | On | Ramtest has started. |
Green | On (flashes once) | Ramtest has completed. |
Yellow | On | Waiting for download. |
Green | On, then goes off | Download has started. |
Green | On (flashes once, then goes off) | Download has completed. |
|
Note After the multichannel E1/PRI port adapter microcode is booted, the microcode takes control of the LEDs. |
During the system bootup process and microcode download, if an error occurs, the port status LEDs flash yellow a number of times, pause, and then repeat the flash. Count the number of flashes to determine the error. Table 4-7 lists the LED error indications that might appear.
| Number of Yellow Flashes | Description |
|---|---|
1 | Memory tests failed. |
2 | PLX mailbox test failed. |
3 | Incomplete data on download. |
4 | Checksum error on download. |
5 | Invalid command (flashing does not repeat, but processing continues). |
6 | Unexpected return from downloaded operational code. |
7 | Processor exception has occurred. |
In all of the preceding error modes, the CPU continually loops and the system does not proceed to the microcode download.
Once the system successfully completes the CPU boot process and microcode download, the front-panel port status LEDs on the multichannel E1/PRI port adapter show the various system states and functions. (See Table 4-8.)
| LED Color | State | Description |
|---|---|---|
Green | On | Port adapter is receiving good signal. |
Yellow | On | Port adapter is in loopback mode. |
None | Off | Not receiving good signal. Not in loopback mode. |
To check bit errors using a bit error rate tester (BERT), use the following command:
[no] E1 bert pattern {2^11 | 2^15 | 2^20 O.153 | 2^20 QRSS | 2^23 | 0s | 1s | alt-0-1} interval minutes
Here 2^15 is an exponential number that represents a pseudorandom repeating pattern that is 32767 bits long, 2^20 is a pseudorandom repeating pattern that is 1048575 bits long, 2^23 is a pseudorandom repeating pattern that is 8388607 bits long, 0s is a pattern of all zeroes (00000000...), 1s is a pattern of all 1s (111111...), and minutes are 1-14400, which designate the time the BERT will run.
To stop the BERT, use the optional no form of the command. Following is an example of this command, where the pseudorandom pattern 2^20 is sent and repeats on the E1 port for 60 minutes:
Router# E1 bert pattern 2^20 interval 60
The BERT command is not saved in NVRAM. The test patterns from the multichannel E1/PRI port adapter are framed test patterns; therefore, they are inserted into the payload of a framed E1 signal.
To display the BERT results, use the following EXEC commands: show controller E1 number or show controller E1 number brief. Following are examples of displaying BERT results output from a VIP2- or VIP-4 equipped Cisco 7500 series router, a Cisco 7200 series router, or a Cisco uBR7200 series router:
1. Display BERT output results during a test:
Router# show controller E1 5/1/0
E1 5/1/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : sync
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 2
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 95565
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 95565
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (117 seconds elapsed):
1 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 43 Unavail Secs
Router#
Router# show controller E1 1/0
E1 1/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : sync
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 2
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 95565
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 95565
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (117 seconds elapsed):
1 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 43 Unavail Secs
Router#
Router# show controller E1 3/0
E1 3/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : sync
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 2
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 39816
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 39816
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 01010
Data in current interval (693 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
Router#
|
Note When the E1 is under BERT (in the running state), its line state is down and the "Total Bit Errors" value is not valid if the "Status" field is "Not Sync." |
2. When the test is done, display BERT results output.
Router# show controller E1 5/1/0 b
E1 5/1/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : done
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 0
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 230946
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 230946
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (189 seconds elapsed):
1 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 43 Unavail Secs
Router#
Router# show controller E1 1/0 b
E1 1/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : done
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 0
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 230946
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 230946
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (189 seconds elapsed):
1 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 43 Unavail Secs
Router#
Router# show controller E1 3/0 b
E1 3/0 is up. (Diagnostic Loopback)
DSX1 BERT pattern : zeros
DSX1 BERT sync : done
DSX1 BERT sync count : 1
DSX1 BERT interval : 2
DSX1 BERT time remain : 0
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 230930
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 230930
Applique type is Channelized E1 - balanced
Receiver has no alarms.
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 01010
Data in current interval (6 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
Router#
|
Note The "Status" field is irrelevant when the BERT is done. If the "Sync Detected" counter is 0, the Bit Errors fields have no meaning. |
3. When the test is stopped prematurely, display BERT results output:
Router# show controller E1 2/4/0 b
E1 2/4/0 is up.
8E1 H/W Version : 4, 8E1 ROM Version : 0.116, 8E1 F/W Version : 20.2.0
Mx H/W version : 2, Mx ucode ver : 1.25
Applique type is Channelized E1
No alarms detected.
FEAC code received : No code is being received
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
E1 1 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-31
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
BERT test result (done)
Test Pattern : All 0's, Status : Not Sync, Sync Detected : 1
Interval : 4 minute(s), Time Remain : 2 minute(s) (unable to complete)
Bit Errors(Sync BERT Started) : 0 bits
Bit Errors(Sync last Sync) : 0 bits , Bits Received : 368 Mbits
Router# show controller E1 1/0 b
E1 1/0 is up.
8E1 H/W Version : 4, 8E1 ROM Version : 0.116, 8E1 F/W Version : 20.2.0
Mx H/W version : 2, Mx ucode ver : 1.25
Applique type is Channelized E1
No alarms detected.
FEAC code received : No code is being received
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
E1 1 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-31
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
BERT test result (done)
Test Pattern : All 0's, Status : Not Sync, Sync Detected : 1
Interval : 4 minute(s), Time Remain : 2 minute(s) (unable to complete)
Bit Errors(Sync BERT Started) : 0 bits
Bit Errors(Sync last Sync) : 0 bits , Bits Received : 368 Mbits
Router# show controller E1 4/0 b
E1 4/0 is up.
8E1 H/W Version : 4, 8E1 ROM Version : 0.116, 8E1 F/W Version : 20.2.0
Mx H/W version : 2, Mx ucode ver : 1.25
Applique type is Channelized E1
No alarms detected.
FEAC code received : No code is being received
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
E1 1 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-31
No alarms detected.
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
BERT test result (done)
Test Pattern : All 0's, Status : Not Sync, Sync Detected : 1
Interval : 4 minute(s), Time Remain : 2 minute(s) (unable to complete)
Bit Errors(Sync BERT Started) : 0 bits
Bit Errors(Sync last Sync) : 0 bits , Bits Received : 368 Mbits
|
Note In the preceding three examples, the "Sync Detected" counter indicates the number of times the pattern sync is detected (from No Sync to Sync), the "Bit Errors (Sync BERT Started)" counter indicates the number of bit errors during BERT, and the "Bit Errors (Sync last Sync)" counter shows the number of bit errors since the last pattern sync was detected. |
Posted: Wed Aug 2 07:38:09 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.