Table Of Contents
Interface Configuration Task List
Understand Interface Configuration
Configure Low-Speed Serial Interfaces on Cisco 2500 Routers
Overview of Half-Duplex DTE and DCE State Machines
Half-Duplex DTE State Machines
Half-Duplex DCE State Machines
Change between Controlled-Carrier and Constant-Carrier Modes
Place a Low-Speed Serial Interface in Controlled-Carrier Mode
Place a Low-Speed Serial Interface in Constant-Carrier Mode
Change between Synchronous and Asynchronous Modes
Return a Low-Speed Serial Interface to Synchronous Mode
Configure an Asynchronous Serial Interface
Specify an Asynchronous Serial Interface
Configure Asynchronous Serial Encapsulation
Configure Dedicated or Interactive Mode
Configure Group and Member Asynchronous Interfaces
Create the Group Interface and the Member Interfaces
Define Member Asynchronous Interface Characteristics
Configure Service Modules on Cisco 2524 and Cisco 2525 Routers
Configure Fractional T1/T1 CSU/DSU Service Modules
Enable Data Inversion before Transmission
Specify the Frame Type of a FT1/T1 Line
Specify the CSU Line Build Out
Enable Loopcodes that Initiate Remote Loopbacks
Perform Loopback Remote (Interface)
Configure 2-Wire and 4-Wire 56/64-kbps CSU/DSU Service Modules
Change between DDS and Switched Dial-up Modes
Enable Acceptance of a Remote Loopback Request
Configure AS5200 T1 Controllers
Allocate Channels to Accept Voice Calls
Set the Facilities Data-Link Standard
Define the Framing Characteristics
Configure the Channelized E1 Channel Groups
Define the Framing Characteristics
Configure the Channelized T1 Channel Groups
Troubleshooting Channelized E1 and Channelized T1
Troubleshooting Channelized T1/E1 Channel Groups
Configure an Ethernet Interface
Configure Ethernet Encapsulation
Configure the Ethernet Network Interface Module on the Cisco 4000
Configure a Fiber Distributed Data Interface (FDDI)
Using Connection Management (CMT) Information
Enable FDDI Bridging Encapsulation
Set the Transmission Valid Timer
Control the Transmission Timer
Enable Duplicate Address Checking
Control the FDDI SMT Message Queue Size
Preallocate Buffers for Bursty FDDI Traffic
Configure a High-Speed Serial Interface (HSSI)
Disable or Enable Automatic Receiver Polarity Reversal
Disable or Enable the Link Test Function
Enable SNMP Illegal Address Trap (for Cisco 2505, Cisco 2507, and Cisco 2516)
Configure an ISDN Basic BRI, MBRI, or PRI Interface
Configure a LAN Extender Interface
LAN Extender Interface Configuration Task List
Configure and Create a LAN Extender Interface
Filter by MAC Address and Vendor Code
Control the Sending of Commands to the LAN Extender
Shut Down and Restart the LAN Extender's Ethernet Interface
Download a Software Image to the LAN Extender
Configure a Loopback Interface
Configure a Synchronous Serial Interface
Specify a Synchronous Serial Interface
Specify Synchronous Serial Encapsulation
Enable CHAP or PAP Authentication
Enable Link Quality Monitoring (LQM)
Disable or Reenable Peer Neighbor Routes
Configure Compression of PPP Data
Configure Compression of LAPB Data
Configure Compression of HDLC Data
Use the NRZI Line-Coding Format
Invert the Transmit Clock Signal
Ignore DCD and Monitor DSR as Line Up/Down Indicator
Configure the Clock Rate on DCE Appliques
Specify the Serial Network Interface Module Timing
Specify G.703 Interface Options
Configure a Token Ring Interface
Specify a Token Ring Interface
Configure PCbus Token Ring Interface Management
Configure the Tunnel Destination
Configure End-to-End Checksumming
Configure a Tunnel Identification Key
Configure a Tunnel Interface to Drop Out-of-Order Datagrams
Configure Asynchronous Host Mobility
Configure IP Address Pooling on Point-to-Point Links
Choose the IP Address Assignment Method
Define the Global Default Mechanism
Define DHCP as the Global Default Mechanism
Define Local Address Pooling as the Global Default Mechanism
Configure Per-Interface IP Address Assignment
Configure Features Available on Any Interface
Add a Description for an Interface
Control Interface Hold-Queue Limits
Adjust Maximum Packet Size or MTU Size
Understand Online Insertion and Removal (OIR)
Understand Fast, Autonomous, and SSE Switching Support
Monitor and Maintain the Interface
Monitor the T1 or E1 Controller
Monitor the LAN Extender Interface
Reset the Hub or Clear the Hub Counters
Shut Down and Restart the Interface
Display Diagnostic Information (Cisco 7000 family only)
Run Interface Loopback Diagnostics
Enable Loopback Testing on the HSSI
Enable Loopback on MCI and SCI Serial Cards
Enable Loopback on MCI and MEC Ethernet Cards
Configure the Ethernet Loopback Server
Enable Loopback on the CSC-FCI FDDI Card
Enable Loopback on Token Ring Cards
Troubleshooting Channelized E1 and Channelized T1
Troubleshooting Channelized T1 and E1 Channel Groups
Monitor and Maintain Service Modules on Cisco 2524 and Cisco 2525 Routers
Interface Configuration Examples
Enabling Interface Configuration Examples
Dedicated Asynchronous Interface Example
Restricting Access on the Asynchronous Interface Example
Asynchronous Routing and Dynamic Addressing Example
Configure Specific IP Addresses for an Asynchronous Interface Example
Configure DHCP Pooling Examples
Configure Local Pooling Example
Group and Member Asynchronous Interfaces Examples
Channelized E1 Controller Example
Channelized T1 Controller and Interface Examples
Enabling Ethernet Encapsulation Example
Enabling a LAN Extender Interface Example
LAN Extender Interface Access List Examples
Filtering by MAC Address Example
Filtering by Ethernet Type Code Example
PPP on a Serial Interface Examples
CHAP with an Encrypted Password Examples
Routing Two AppleTalk Networks across an IP-Only Backbone Example
Routing a Private IP Network and a Novell Net across a Public Service Provider Example
Interface Descriptions Examples
Dial Backup Service When the Primary Line Goes Down Examples
Dial Backup Service When the Primary Line Reaches Threshold Examples
Dial Backup Service When the Primary Line Exceeds Threshold Examples
Source Address for an Ethernet Hub Port Configuration Examples
Enable SNMP Illegal Address Trap for Hub Port Example
Configuring Interfaces
Use the information in this chapter to understand the types of interfaces supported on Cisco routers and access servers. Two types of interfaces are supported: physical and virtual interfaces. The types of physical interfaces on a device depend on its appliques or interface processors. The virtual interfaces that Cisco routers and access servers support include subinterfaces and IP tunnels.
Cisco routers and access servers support the following types of interfaces:
•
Asynchronous serial
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
In addition, the Cisco IOS software support subinterfaces. See the Wide-Area Networking Configuration Guide and the protocol chapters in the Cisco IOS software configuration guides for specific information on how to configure a subinterface for a particular protocol.
Note
For hardware technical descriptions and information about installing interfaces, refer to the hardware installation and maintenance publication for your product. For command descriptions and usage information, refer to the "Interface Commands" chapter of the Configuration Fundamentals Command Reference.
Interface Configuration Task List
You can perform the tasks in the following sections to configure and maintain the interfaces:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
See the end of this chapter for "Interface Configuration Examples."
Understand Interface Configuration
Begin interface configuration in global configuration mode. To configure an interface, follow these steps:
Step 1
Step 2
Router# show interfacesSerial 0 is administratively down, line protocol is downHardware is MCI SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)Use the show hardware EXEC command to see a list of the system software and hardware.
To begin configuring serial interface 0, you add the following line to the configuration file:
interface serial 0
Note
Step 3
Step 4
Note
The following sections show how to configure each interface type. Follow the interface command with the routing or bridging interface configuration commands for your particular protocol or application, as described in this chapter and subsequent chapters.
See the section "Enabling Interface Configuration Examples" at the end of this chapter.
Configure Low-Speed Serial Interfaces on Cisco 2500 Routers
This section describes how to configure low-speed serial interfaces on Cisco 2520 through Cisco 2523 routers. It describes these tasks in the following sections:
•
•
•
Overview of Half-Duplex DTE and DCE State Machines
The following section describes the communication between half-duplex DTE transmit and receive state machines and half-duplex DCE transmit and receive state machines.
Half-Duplex DTE State Machines
As shown in , the half-duplex DTE transmit state machine for low-speed interfaces remains in the ready state when it is quiescent. When a frame is available for transmission, the state machine transitions to the transmit delay state and waits for a time period, which is defined by the half-duplex timer transmit-delay command. The default is 0 ms. Transmission delays are used for debugging half-duplex links and assisting lower-speed receivers that cannot process back-to-back frames.
Figure 13 Half-Duplex DTE Transmit State Machine
After idling for a defined number of milliseconds, the state machine asserts request to send (RTS) and transitions to the wait clear to send (CTS) state for the data communications equipment (DCE) to assert CTS. A timeout timer with a value set by the half-duplex timer rts-timeout command starts. This default is 3 ms. If the timeout timer expires before CTS is asserted, the state machine returns to the ready state and de-asserts RTS. If CTS is asserted prior to the timer's expiration, the state machine transitions to the transmit state and sends the frames.
Once there are no more frames to transmit, the state machine transitions to the wait transmit finish state. The machine waits for the transmit first-in first-out (FIFO) in the serial controller to empty, starts a delay timer with a value defined by the half-duplex timer rts-drop-delay interface command, and transitions to the wait RTS drop delay state.
When the timer in the wait RTS drop delay state expires, the state machine de-asserts RTS and transitions to the wait CTS drop state. A timeout timer with a value set by the half-duplex timer cts-drop-timeout interface command starts, and the state machine waits for the CTS to de-assert. The default is 250 ms. Once the CTS signal is de-asserted or the timeout timer expires, the state machine transitions back to the ready state. If the timer expires before CTS is de-asserted, an error counter is incremented, which can be displayed by issuing the show controllers command for the serial interface in question.
As shown in , a half-duplex DTE receive state machine for low-speed interfaces idles and receives frames in the ready state. A giant frame is any frame whose size exceeds the maximum transmission unit (MTU). If the beginning of a giant frame is received, the state machine transitions to the in giant state and discards frame fragments until it receives the end of the giant frame. At this point, the state machine transitions back to the ready state and waits for the next frame to arrive.
Figure 14 Half-Duplex DTE Receive State Machine
An error counter is incremented upon receipt of the giant frames. To view the error counter, enter the show interface command for the serial interface in question.
Half-Duplex DCE State Machines
As shown in , for a low-speed serial interface in DCE mode, the half-duplex DCE transmit state machine idles in the ready state when it is quiescent. When a frame is available for transmission on the serial interface, such as when the output queues are no longer empty, the state machine starts a timer (based on the value of the transmit-delay command, in milliseconds) and transitions to the transmit delay state. Similar to the DTE transmit state machine, the transmit delay state gives you the option of setting a delay between the transmission of frames; for example, this feature lets you compensate for a slow receiver that loses data when multiple frames are received in quick succession. The default transmit-delay value is 0 ms; use the half-duplex timer transmit-delay interface configuration command to specify a delay value not equal to 0.
Figure 15 Half-Duplex DCE Transmit State Machine
After the transmit delay state, the next state depends on whether the interface is in constant-carrier mode (the default) or controlled-carrier mode.
If the interface is in constant-carrier mode, it transitions through the following states:
1
2
3
If the interface is in controlled-carrier mode, the interface performs a handshake using the data carrier detect (DCD) signal. In this mode, DCD is de-asserted when the interface is idle and has nothing to transmit. The transmit state machine transitions through the states as follows:
1
2
3
4
5
As shown in , the half-duplex DCE receive state machine idles in the ready state when it is quiescent. It transitions out of this state when the DTE asserts RTS. In response, the DCE starts a timer with the value cts-delay. This timer delays the assertion of CTS because some DTE interfaces expect this delay. (The default value of this timer is 0 ms; use the half-duplex timer cts-delay interface configuration command to specify a delay value.)
Figure 16 Half-Duplex DCE Receive State Machine
When the timer expires, the DCE state machine asserts CTS and transitions to the receive state. It stays in the receive state until there is a frame to receive. If the beginning of a giant frame is received, it transitions to the in giant state and keeps discarding all the fragments of the giant frame and transitions back to the receive state.
Transitions back to the ready state occur when RTS is de-asserted by the DTE. The response of the DCE to the de-assertion of RTS is to de-assert CTS and go back to the ready state.
Change between Controlled-Carrier and Constant-Carrier Modes
The half-duplex controlled-carrier command enables you to change between controlled-carrier and constant-carrier modes for low-speed serial DCE interfaces in half-duplex mode. Configure a serial interface for half-duplex mode by using the media-type half-duplex command. Full-duplex mode is the default for serial interfaces. This interface configuration is available on Cisco 2520 through Cisco 2523 routers.
Controlled-carrier operation means that the DCE interface will have DCD de-asserted in the quiescent state. When the interface has something to transmit, it will assert DCD, wait a user-configured amount of time, then start the transmission. When it has finished transmitting, it will again wait a user-configured amount of time, then de-assert DCD.
Place a Low-Speed Serial Interface in Controlled-Carrier Mode
To place a low-speed serial interface in controlled-carrier mode, perform the following task in interface configuration mode:
Place a low-speed serial interface in controlled-carrier mode.
half-duplex controlled-carrier
Place a Low-Speed Serial Interface in Constant-Carrier Mode
To return a low-speed serial interface to constant-carrier mode from controlled-carrier mode, perform the following task in interface configuration mode:
Place a low-speed serial interface in constant-carrier mode.
no half-duplex controlled-carrier
Change between Controlled-Carrier and Constant-Carrier Modes Example
The following example shows how to change to controlled-carrier mode from the default of constant-carrier operation:
Router(config)# interface serial 2Router(config-if)# half-duplex controlled-carrierThe following example shows how to change to constant-carrier mode from controlled-carrier mode:
Router(config)# interface serial 2Router(config-if)# no half-duplex controlled-carrierTune Half-Duplex Timers
To tune half-duplex timers, perform the following task in interface configuration mode:
The timer tuning commands permit you to adjust the timing of the half-duplex state machines to suit the particular needs of their half-duplex installation.
Note that the half-duplex timer command and its options deprecates the following two timer tuning commands that are available only on high-speed serial interfaces:
•
•
Tune Half-Duplex Timers Example
The following examples show how to set the cts-delay timer to 1234 ms and the transmit-delay timer to 50 ms:
Router(config)# interface serial 2Router(config-if)# half-duplex timer cts-delay 1234Router(config-if)# half-duplex timer transmit-delay 50Change between Synchronous and Asynchronous Modes
To specify the mode of a low-speed serial interface as either synchronous or asynchronous, perform the following task in interface configuration mode:
Specify the mode of a low-speed interface as either synchronous or asynchronous.
physical-layer {sync | async}
This command applies only to low-speed serial interfaces available on Cisco 2520 through Cisco 2523 routers.
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
•
•
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces. The default is synchronous mode.
Note that when you enter this command, it does not appear in the output of show running config and show startup config command, because the command is a physical-layer command.
Return a Low-Speed Serial Interface to Synchronous Mode
To return to the default mode (synchronous) of a low-speed serial interface on a Cisco 2520 through Cisco 2523 router, perform the following task in interface configuration mode:
Specify the Mode of a Low-Speed Serial Interface Example
The following example shows how to change a low-speed serial interface from synchronous to asynchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncThe following examples show how to change a low-speed serial interface from asynchronous mode back to its default synchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer syncor
Router(config)# interface serial 2Router(config-if)# no physical-layerThe following example shows some typical asynchronous interface configuration commands:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncRouter(config-if)# ip address 1.0.0.2 255.0.0.0Router(config-if)# async default ip address 1.0.0.1Router(config-if)# async mode dedicatedRouter(config-if)# async default routingThe following example shows some typical synchronous serial interface configuration commands available when the interface is in synchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer syncRouter(config-if)# ip address 1.0.0.2 255.0.0.0Router(config-if)# no keepaliveRouter(config-if)# ignore-dcdRouter(config-if)# nrzi-encodingRouter(config-if)# no shutdownConfigure an Asynchronous Serial Interface
To configure an asynchronous serial interface on a routing device, you must set up the interface to send SLIP or PPP packets. PPP and SLIP define methods of sending Internet packets over a standard RS-232 asynchronous serial line. PPP also defines methods for sending IPX and ARA packets during PPP sessions.
Asynchronous Serial Task List
To configure an asynchronous interface so you can connect to an asynchronous device on the network, complete the tasks in the following sections:
•
•
•
•
•
Note
Specify an Asynchronous Serial Interface
On an access server, you can configure any of the available asynchronous interfaces (1 through 8 on the Cisco 2509 and 2510, 1 through 16 on the Cisco 2511 and 2512, or 1 through 48 on the AS5100). The auxiliary (labeled AUX on the back of the product) port can also be configured as an asynchronous serial interface, although performance on the AUX port is much slower than on standard asynchronous interfaces and does not support some features. illustrates why asynchronous interfaces permit substantially better performance than AUX ports configured as asynchronous interfaces.
Table 5 Differences between Auxiliary (AUX) Port and Asynchronous Port
Maximum speed
115200 kbps
38400 kbps
Supported Platforms
Cisco 2509, 10, 11, 12, AS5100, Cisco 1001
All Cisco routers
Supports DMA buffering?1
Yes
No
PPP framing on chip2
Yes
No
IP fast switching?3
Yes
No
1 Direct Memory Access (DMA) buffering moves data packets directly to and from system memory without interrupting the main central processing unit (CPU). This process removes overhead from the CPU and increases overall system performance.
2 PPP framing on a hardware chip removes overhead from the router's CPU, which enables the router to sustain 115.2 kbps throughput on all asynchronous ports simultaneously.
3 After the destination of the first IP packet is added to the fast switching cache, it is fast switched to and from other interfaces with minimal involvement from the main processor.
On routers without built-in asynchronous interfaces, only the AUX port can be configured as an asynchronous serial interface. To configure the AUX port as an asynchronous interface, you must also configure it as an auxiliary line with the line aux 1 command as described in the chapter "Configuring Terminal Lines and Modem Support" in the Access Services Configuration Guide. Access servers do not have this restriction.
Use the line command with the appropriate line configuration commands for modem control, such as speed. Perform the following task in global configuration mode to specify a port as an asynchronous interface:
Only IP packets can be sent across lines configured for SLIP. PPP supports transmission of IP, IPX, and ARA packets on an asynchronous serial interface.
Configure Asynchronous Serial Encapsulation
There are two asynchronous serial encapsulation methods:
•
•
For information about configuring SLIP and PPP, refer to the chapter "Configuring SLIP and PPP" in the Access Services Configuration Guide.
Configure Dedicated or Interactive Mode
You can configure the asynchronous interface to be in dedicated network or interactive mode.
In dedicated mode, there is no user prompt or EXEC level, so no end-user commands are required to place the line into interface mode. When the interface is configured for dedicated mode, the user cannot change the encapsulation method, address, or other parameters.
To configure an asynchronous interface to be in dedicated network mode, perform the following task in interface configuration mode:
For an example of placing an asynchronous interface into dedicated network mode, see the section "Dedicated Asynchronous Interface Example" at the end of this chapter.
Alternatively, you can configure an asynchronous line for interactive mode. In interactive mode, the line can be used to make any type of connection, depending on the EXEC command entered by the user. For example, depending on its configuration, the line could be used for Telnet connections, or SLIP or PPP encapsulation. Perform the following task in interface configuration mode to configure an asynchronous line for interactive mode:
Enable Asynchronous Routing
To enable dynamic routing protocols on asynchronous interfaces, perform the following task in interface configuration mode:
Configure Group and Member Asynchronous Interfaces
You can create an asynchronous interface to be used as a group interface, which can be associated with other, member asynchronous interfaces.
This association allows you to configure the group interface and all of its member interfaces with a single command entered at the asynchronous group interface command line. You can have more than one group interface on a device; however, a member interface can be associated with only one group.
See the "Group and Member Asynchronous Interfaces Examples" section at the end of this chapter for an example of group and member interfaces.
illustrates the group-member interface concept.
Figure 17 Group-Member Association on Asynchronous Interfaces
Create the Group Interface and the Member Interfaces
To create an asynchronous group interface and associate member interfaces to this group interface, perform the following commands starting in global configuration mode:
Refer to the "Group and Member Asynchronous Interfaces Examples" section in this chapter for an example configuration.
Define Member Asynchronous Interface Characteristics
Member interfaces can have certain interface configurations that differ from their group. The following are valid interface configuration commands:
•
•
To configure a member with two or more interface configurations that are different from its group, enter the following command in interface configuration mode, when interface-command is one of the command arguments listed in the preceding list:
Configure a member to have specific differences from its group.
member interface-number interface-command
Enable Keepalives
Asynchronous interfaces do not send and do not expect keepalives from the remote end of a point-to-point connection. If your network requires the asynchronous connection to stay up, enable keepalives on anynchronous interfaces, using the keepalive command and setting a specific interval.
To enable keepalives, complete the following task in interface configuration mode:
Configure Service Modules on Cisco 2524 and Cisco 2525 Routers
This section describes how to configure service modules on Cisco 2524 and Cisco 2525 routers. It describes these tasks in the following sections:
•
•
Configure Fractional T1/T1 CSU/DSU Service Modules
This section describes how to configure fractional T1 and T1 (FT1/T1) service modules installed on Cisco 2524 and Cisco 2525 routers. This section describes the following tasks:
•
•
•
•
•
Specify the Clock Source
To specify the clock source for the FT1/T1 CSU/DSU module, perform the following task in interface configuration mode:
Specify the clock source, for the CSU/DSU internal clock or the line clock.
service-module t1 clock source {internal | line}
Enable Data Inversion before Transmission
Data inversion is used to guarantee the 1s density requirement on an AMI line when using bit-oriented protocols such as High-Level Data Link Control (HDLC), Point-to-Point Protocol (PPP), X.25, and Frame Relay.
To guarantee the 1s density requirement on an AMI line using the FT1/T1 CSU/DSU module, perform the following task in interface configuration mode:
Invert bit codes by changing all 1 bits to 0 bits and all 0 bits to 1 bits.
service-module t1 data-coding inverted
If the timeslot speed is set to 56 kbps, this command is rejected because line density is guaranteed when transmitting at 56 kbps. Use this command with the 64 kbps line speed. If you transmit inverted bit codes, both CSU/DSUs must have this command configured for successful communication.
To enable normal data transmission on a FT1/T1 network, perform the following task in interface configuration mode:
Enable normal data transmission on a T1 network.
service-module t1 data-coding normal
or
no service-module t1 data-coding inverted
Specify the Frame Type of a FT1/T1 Line
To specify the frame type for a line using the FT1/T1 CSU/DSU module, perform the following task in interface configuration mode:
Specify the FT1/T1 frame type. Choose either D4 super frame (sf) or extended super frame (esf).
service-module t1 framing {sf | esf}
In most cases, the service provider determines which framing type, either esf or sf, is required for your circuit.
Specify a T1 Frame Type Example
The following example enables super frame as the FT1/T1 frame type:
Router(config-if)# service-module t1 framing sfSpecify the CSU Line Build Out
To decrease the outgoing signal strength to an optimum value for the telecommunication carrier network, perform the following task on the FT1/T1 CSU/DSU module in interface configuration mode:
Decrease the outgoing signal strength in decibels.
service-module t1 lbo {-15 db | -7.5 db}
To transmit packets without decreasing outgoing signal strength, perform the following task in interface configuration mode:
Transmits packets without decreasing outgoing signal strength.
service-module t1 lbo none
The ideal signal strength should be between -15 dB and -22 dB, which is calculated by adding the phone company loss + cable length loss + line build out.
You may use this command in back-to-back configurations, but it is not needed on most actual T1 lines.
Specify the CSU Line Build Out Example
The following example shows a line build out setting of -7.5 dB:
Router1(config-if)#service-module t1 lbo -7.5dbSpecify FT1/T1 Line-Code Type
To configure the line code for the FT1/T1 CSU/DSU module, perform the following task in interface configuration mode:
Specify the line-code type. Choose alternate mark inversion (AMI) or binary 8 zero substitution (B8ZS).
service-module t1 linecode {ami | b8zs}
Configuring B8ZS is a method of ensuring the 1s density requirement on a T1 line by substituting intentional bi polar violations in bit positions four and seven for a sequence of eight zero bits. When the CSU/DSU is configured for AMI, you must guarantee the 1s density requirement in your router configuration using the service-module t1 data-coding inverted command or the service-module t1 timeslots speed 56 command.
In most cases, your T1 service provider determines which line-code type, either ami or b8zs, is required for your T1 circuit.
Specify T1 Line-Code Type Example
The following example specifies AMI as the line-code type:
Router(config-if)# service-module t1 linecode amiEnable Remote Alarms
To generate remote alarms (yellow alarms) at the local CSU/DSU or detect remote alarms sent from the remote CSU/DSU, perform the following task in interface configuration mode:
Remote alarms are transmitted by the CSU/DSU when it detects an alarm condition, such as a red alarm (loss of signal) or blue alarm (unframed 1's). The receiving CSU/DSU then knows there is an error condition on the line.
With D4 super frame configured, a remote alarm condition is transmitted by setting the bit 2 of each time slot to zero. For received user data that has the bit 2 of each time slot set to zero, the CSU/DSU will interpret the data as a remote alarm and interrupt data transmission, which explains why remote alarms are disabled by default. With extended super frame configured, the remote alarm condition is signaled out of band in the facility data link.
You can see if the FT1/T1 CSU/DSU is receiving a remote alarm (yellow alarm) by issuing the show service-module command.
To disable remote alarms, perform the following task in interface configuration mode:
Enable Loopcodes that Initiate Remote Loopbacks
To specify if the fractional T1/T1 CSU/DSU module goes into loopback when it receives a loopback code on the line, perform the following task in interface configuration mode:
Note
You can simultaneously configure the full and payload loopback points. However, only one loopback payload code can be configured at a time. For example, if you configure the service-module t1 remote-loopback payload alternate command, a payload v.54 request, which is the industry standard and default, cannot be transmitted or accepted. Full and payload loopbacks with standard-loopup codes are enabled by default.
The no form of this command disables loopback requests. For example, the no service-module t1 remote-loopback full command ignores all full-bandwidth loopback transmissions and requests. Configuring the no form of the command may not prevent telco line providers from looping your router in esf mode, because fractional T1/T1 telcos use facilities data-link messages to initiate loopbacks.
If you enable the service-module t1 remote-loopback command, the loopback remote commands on the FT1/T1 CSU/DSU module will not be successful.
Enable Loopcodes Example
The following example displays two routers connected back-to-back through an FT1/T1 line:
Router(config-if)# no service-module t1 remote-loopback fullRouter(config-if)# service-module t1 remote-loopback payload alternateboa1(config-if)# loopback remote full%SERVICE_MODULE-5-LOOPUPFAILED: Unit 0 - Loopup of remote unit failedboa1(config-if)# service-module t1 remote-loopback payload v54boa1(config-if)# loopback remote payload%SERVICE_MODULE-5-LOOPUPFAILED: Unit 0 - Loopup of remote unit failedboa1(config-if)# service-module t1 remote-loopback payload alternateboa1(config-if)# loopback remote payload%SERVICE_MODULE-5-LOOPUPREMOTE: Unit 0 - Remote unit placed in loopbackSpecify Timeslots
To define timeslots for FT1/T1 module, perform the following task in interface configuration mode:
This command specifies which timeslots are used in fractional T1 operation and determines the amount of bandwidth available to the router in each timeslot.
The range specifies the DS0 timeslots that constitute the FT1/T1 channel. The range is from 1 to 24, where the first timeslot is numbered 1 and the last timeslot is numbered 24. Specify this field by using a series of subranges separated by commas. The timeslot range must match the timeslots assigned to the channel group. In most cases, the service provider defines the timeslots that comprise a channel group. Use the no form of this command to select all FT1/T1 timeslots transmitting at 64 kbps, which is the default.
To use the entire T1 line, enable the service-module T1 timeslots all command.
Specify Timeslots Example
The following example displays a series of timeslot ranges and a speed of 64 kbps:
Router(config-if)#service-module t1 timeslots 1-10,15-20,22 speed 64Perform Loopback
You can loop packets back to the network from the integrated CSU/DSU, loop packets to DTE, and loop packets through a local CSU/DSU to a remote CSU/DSU.
Enable Loopback Line
To loop data received from the line at the local CSU/DSU back to the line, perform the following task in interface configuration mode:
Packets are looped from an incoming network transmission back into the network at a CSU or DSU loopback point.
When the loopback line command is configured on the 2-wire 56-kbps CSU/DSU module or the 4-wire 56/64-kbps CSU/DSU modules installed on a Cisco 2524 or Cisco 2525 router, the network data loops back at the CSU and the router data loops back at the DSU. If the CSU/DSU is configured for switched mode, you must have an established connection to perform a payload-line loopback. When the loopback line payload command is configured, the CSU/DSU module loops the data through the DSU portion of the module. Data is not looped back to the serial interface.
If you enable the loopback line command on the fractional T1/T1 module, the CSU/DSU performs a full-bandwidth loopback through the CSU portion of the module and data transmission through the serial interface is interrupted for the duration of the loopback. No reframing or corrections of bi polar violation errors or cyclic redundancy check (CRC) errors are performed. When you configure the line loopback payload command on the FT1/T1 module, the CSU/DSU performs a loopback through the DSU portion of the module. The line loopback payload command reframes the data link, regenerates the signal, and corrects bi polar violations and extended super frame CRC errors.
When performing a T1-line loopback with extended super framing, communication over the facilities data link is interrupted but performance statistics are still updated. To show interfaces currently in loopback operation, use the show service-module EXEC command.
Enable Loopback Line Example
The following example shows how to configure a payload loopback:
Router1(config-if)#loopback line payloadLoopback in progressRouter1(config-if)#no loopback lineThe following example shows the output when you loop a packet in switched mode without an active connection:
Router1(config-if)#service-module 56k network-type switchedRouter1(config-if)#loopback line payloadNeed active connection for this type of loopback% Service module configuration command failed: WRONG FORMAT.Enable Loopback DTE
To loop packets back to DTE from within the local CSU/DSU, perform the following task:
Packets are looped from within the CSU/DSU back to the serial interface of the router. Send a test ping to see if the packets successfully looped back. To cancel the loopback test, use the no loopback dte command.
When using the 4-wire 56/64-kbps CSU/DSU module, an out-of-service signal is transmitted to the remote CSU/DSU.
Example
The following example loops a packet from a module to the serial interface:
Router1(config-if)#loopback dteLoopback in progressRouter1#ping 12.0.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 12.0.0.1, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 8/12/28 msPerform Loopback Remote (Interface)
To loop packets at the remote CSU/DSU, perform the following task:
This command applies only when the remote CSU/DSU device is configured for this function. It is used for testing the data communication channels along with or without remote CSU/DSU circuitry. The loopback is usually performed at the line port, rather than the DTE port, of the remote CSU/DSU.
FT1/T1 CSU/DSU Module
On the integrated FT1/T1 CSU/DSU module installed on a Cisco 2524 and Cisco 2525 router, the loopback remote full command sends the loopup code to the remote CSU/DSU. The remote CSU/DSU performs a full-bandwidth loopback through the CSU portion of the module. The loopback remote payload command sends the loopup code on the configured timeslots, while maintaining the D4-extended super framing. The remote CSU/DSU performs the equivalent of a loopback line payload request. The remote CSU/DSU loops back only those timeslots that are configured at the remote end. This loopback reframes the data link, regenerates the signal, and corrects bi polar violations and extended super frame CRC errors. The loopback remote smart-jack command sends a loopup code to the remote smart jack. You cannot put the local smart jack into loopback.
Failure to loopup or initiate a remote loopback request could be caused by enabling the no service-module t1 remote-loopback command or having an alternate remote-loopback code configured on the remote end. When the loopback is terminated, the result of the pattern test is displayed.
Note
2- and 4-Wire 56/64-kbps CSU/DSU Modules
On the 2- and 4-wire 56/64-kbps CSU/DSU modules installed on a Cisco 2524 or Cisco 2525 router, an active connection is required before a loopup can be initiated while in switched mode. When transmitting V.54 loopbacks, the remote device is commanded into loopback using V.54 messages. Failure to loopup or initiate a remote loopback request could be caused by enabling the no service-module 56k remote-loopback command.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Configure 2-Wire and 4-Wire 56/64-kbps CSU/DSU Service Modules
This section describes how to configure 2- and 4-wire 56/64 kbps service modules. The following tasks are described:
•
•
Set the Clock Source
To configure the clock source for a 4-wire 56/64-kbps CSU/DSU module, perform the following task:
In most applications, the CSU/DSU should be configured with the clock source line command. For back-to-back configurations, configure one CSU/DSU with the clock source internal command and the other with the clock source line command.
Use the no form of this command to enable the line clock, which is the default.
Setting the Clock Source Example
The following example shows a router using internal clocking while transmitting frames at 38.4 kbps.
Router1(config-if)#service-module 56k clock source internalRouter1(config-if)#service-module 56k clock rate 38.4Set the Network Line Speed
To configure the network line speed for a 4-wire 56/64-kbps CSU/DSU module, perform the following task in interface configuration mode:
Configure the line with the following speeds: 2.4, 4.8, 9.6, 19.2, 38.4, 56, and 64 kbps. The 64-kbps line speed cannot be used with back-to-back DDS lines. The sub rate line speeds are determined by the service provider.
Only the 56-kbps line speed is available in switched mode, which is enabled using the service-module 56k network-type interface configuration command on the 4-wire CSU/DSU. The 2-wire CSU/DSU default is set to switched mode.
The auto linespeed enables the CSU/DSU to decipher current line speed from the sealing current running on the network. Back-to-back DDS lines do not have sealing current, therefore use auto only when transmitting over telco DDS lines and the clocking source is taken from the line.
Use the no form of this command to enable a network line speed of 56 kbps, which is the default.
Set the Network Line Speed Example
The following example displays two routers connected in back-to-back DDS mode. However, the configuration fails because the auto rate is used.
Router1(config-if)#service-module 56k clock source internalRouter1(config-if)#service-module 56k clock rate 38.4Router2(config-if)#service-module 56k clock rate auto% WARNING - auto rate will not work in back-to-back DDS.a1#ping 10.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:.....Success rate is 0 percent (0/5)Router2(config-if)#service-module 56k clock rate 38.4Router1#ping 10.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 52/54/56 msWhen transferring from DDS mode to switched mode, you must set the correct clock rate, as shown in the following example:
Router2(config-if)#service-module 56k network-type ddsRouter2(config-if)#service-module 56k clock rate 38.4Router2(config-if)#service-module 56k network-type switched% Have to use 56k or auto clock rate for switched mode% Service module configuration command failed: WRONG FORMAT.Router2(config-if)#service-module 56k clock rate auto% WARNING - auto rate will not work in back-to-back DDS.Router2(config-if)#service-module 56k network-type switchedEnable Scrambled Data Coding
To prevent application data from replicating loopback codes when operating at 64-kbps on a 4-wire CSU/DSU, perform the following task in interface configuration mode:
Enable the scrambled configuration only in 64-kbps digital data service (DDS) mode. If the network type is set to switched, the configuration is refused.
If you transmit scrambled bit codes, both CSU/DSUs must have this command configured for successful communication.
To enable normal data transmission for the 4-wire 56/64-kbps module, perform the following task, which is the default, in interface configuration mode:
Specify normal data transmission.
service-module 56k data-coding normal
or
no service-module 56k data-coding
Enable Scrambled Data Coding Example
The following example scrambles bit codes in 64 kbps DDS mode:
Router(config-if)# service-module 56k clock rate 56Router(config-if)# service-module 56k data-coding scrambledCan configure scrambler only in 64k speed DDS mode% Service module configuration command failed: WRONG FORMAT.Router(config-if)# service-module 56k clock rate 64Router(config-if)# service-module 56k data-coding scrambledChange between DDS and Switched Dial-up Modes
To transmit packets in switched dial-up mode or DDS mode using the 4-wire 56/64-kbps CSU/DSU module, perform the following task in interface configuration mode:
Transmit packets in switched dial-up mode or DDS mode.
service-module 56k network-type dds
or
service-module 56k network-type switched
Use the no form of these commands to transmit from a dedicated leased line in DDS mode. DDS is enabled by default for the 4-wire CSU/DSU. Switched is enabled by default for the 2-wire CSU/DSU.
In switched mode, you need additional dialer configuration commands to configure dial-out numbers. Before you enable the service-module 56k network-type switched command, both CSU/DSUs must use a clock source coming from the line and the clock rate configured to auto or 56k kbps. If the clock rate is not set correctly, this command will not be accepted.
The 2 and 4-wire 56/64-kbps CSU/DSU modules use V.25 bis dial commands to interface with the router. Therefore, the interface must be configured using the dialer in-band command. DTR dial is not supported.
Note
Enable Switched Dial-up Mode Example
The following example displays transmission in switched dial-up mode:
Router(config-if)# service-module 56k clock rate 19.2Router(config-if)# service-module 56k network-type switched% Have to use 56k or auto clock rate for switched mode% Service module configuration command failed: WRONG FORMAT.Router(config-if)# service-module 56k clock rate autoRouter(config-if)# service-module 56k network-type switchedRouter(config-if)# dialer in-bandRouter(config-if)# dialer string 2576666Router(config-if)# dialer-group 1Enable Acceptance of a Remote Loopback Request
To enable the acceptance of a remote loopback request on a 2- or 4-wire 56/64-kbps CSU/DSU module, perform the following task in interface configuration mode:
The no service-module 56k remote-loopback command prevents the local CSU/DSU from being placed into loopback by remote devices on the line. Unlike the T1 module, the 2- or 4-wire 56/64-kbps CSU/DSU module can still initiate remote loopbacks with the no form of this command configured.
Remote Loopback Request Example
The following example enables you to transmit and receive remote loopbacks using the service-module 56k remote-loopback command:
Router(config-if)#service-module 56k remote-loopbackRouter(config-if)#Select a Service Provider
To select a service provider to use with a 2- or 4-wire 56/64-kbps dial-up line, perform the following task in interface configuration mode:
Select a service provider for a 2 or 4 wire switched 56/64-kbps dial-up line.
service-module 56k switched-carrier {att | other | sprint}
The att keyword specifies AT&T or another digital network service provider as the line carrier, which is the default for the 4-wire 56/64-kbps CSU/DSU module. The sprint keyword specifies Sprint or another service provider whose network carries mixed voice and data as the line carrier, which is the default for the 2-wire switched 56-kbps CSU/DSU module.
In a Sprint network, echo-canceler tones are sent during call setup to prevent echo cancelers from damaging digital data. The transmission of these cancelers may increase call setup times by 8 seconds on the 4-wire module. Having echo cancellation enabled does not affect data traffic.
This configuration command is ignored if the network type is DDS.
Use the no form of this command to enable the default service provider. AT&T is enabled by default on the 4-wire 56/64-kbps module. Sprint is enabled by default on the 2-wire switched 56-kbps module.
Select a Service Provider Example
The following example selects AT&T as the service provider:
Router(config-if)# service-module 56k network-type switchedRouter(config-if)# service-module 56k switched-carrier attConfigure an ATM Interface
See the "Configuring ATM" chapter in the Wide-Area Networking Configuration Guide for information on how to configure an Asynchronous Transfer Mode (ATM) interface.
See also the section "Invoke ATM over a Serial Line" in the section "Configure a Synchronous Serial Interface" in this chapter.
Configure AS5200 T1 Controllers
Configure the Cisco AS5200 T1 controllers with the commands documented in the following sections:
•
•
•
Define the Clock Source
To select the clock source, perform the following task in interface configuration mode:
Use the clocking source from the external line.
clock source line {primary | secondary}
Use the internal clocking source from the Cisco AS5200.
clock source internal
Enter the clock source line primary command for the T1 line that has the most reliable clocking. Enter the clock source line secondary command for the T1 line that has the next best clocking. If the primary line clocking is interrupted, the clocking is backed up to the secondary line. You must configure one of these commands on each controller. If the T1 controller is configured with the clock source line primary command, you must configure the T0 controller with the clock source line secondary command.
Use the clock source internal command only if you are conducting back-to-back tests in a router lab environment. You will rarely need to use this command.
Allocate Channels to Accept Voice Calls
To enable the AS5200 modems to accept and send incoming and outgoing analog calls through a channelized T1 if you are not running ISDN PRI, you must configure the following controller configuration command:
Enable incoming and outgoing channelized T1 voice calls to dial in to and dial out of the AS5200.
cas-group channel-number [timeslots range]1
1 The default value for this command configures 24 timeslots with the channel associated signal E&M
(Ear and Mouth), which is the default signal type. Switched 56 digital calls are not supported under this new feature.
You can allocate the 24 available channels for a channelized T1 in the following four ways for a Cisco AS5200:
1
2
3
4
Adjust the Pulse Equalization
To increase the pulse of a signal at the receiver and decrease the pulse from the transmitter using pulse equalization and line build-out, perform the following task in interface configuration mode:
For a long cable, the keywords gain36 and gain26 are used to increase receiver energy (dbgain-value). The keywords 0db, -7.5db, -15db, and -22.5db are used to decrease the transmission pulse (dbloss-value). The no cablelength command increases the receiver signal pulse by 36 dB and decreases the transmitter pulse by 0 dB for a long cable.
Set the Facilities Data-Link Standard
To set the facilities data-link standard for the CSU on the AS5200's T1 controllers, perform one of the following tasks in controller interface configuration mode:
Select AT&T technical reference 54016 for extended superframe facilities data-link exchange.
fdl att
Select ANSI T1.403 for extended superframe facilities data-link exchange.
fdl ansi
You must configure one of these commands on both T1 interfaces if you want to support the CSU function on each T1 line. However, you must use the same facilities data link exchange standard as your service provider. You can have a different standard configured on each T1 interface.
Configure Channelized E1
Support for channelized E1 is provided on the following platforms:
•
•
Each E1 adapter can support a maximum of 30 channel groups. The Cisco 7000 MIP can support one or two adapters, providing a maximum of 60 channel groups per MIP. The Cisco 4000 can support one adapter, providing a maximum of 30 channel groups. Each channel group is presented to the system as a serial interface that can be configured individually. In effect, up to 30 E1 circuits are multiplexed to each hardware adapter.
Use the show controllers e1 EXEC command to display current E1 status. This command provides a report for each physical interface configured to support channelized E1.
Channelized E1 supports the following WAN protocols:
•
•
•
•
•
•
•
When a channelized E1 adapter is used for ISDN PRI, it can support DDR; when it is not used for ISDN PRI, it does not support DDR. Refer to the "Configuring ISDN" chapter in the Wide-Area Networking Configuration Guide for more information.
Channelized E1 Task List
Using channelized E1 controller and serial interface configuration commands, you can perform the tasks in the following sections to configure channelized E1:
•
•
See the end of this chapter for "Interface Configuration Examples."
Configure the E1 Controller
To configure the E1 physical characteristics, you first define the location of the controller in the router. A Cisco 7000 router can have up to four MIP and eight CX-MIP-CE1 interfaces. A Cisco 7010 router can have up to three MIP and six CX-MIP-CE1 interfaces. The Cisco 4000 series routers can support up to three network processor module (NPM) cards, each with one interface when running it as a channelized interface card. However, when the card is used to run ISDN PRI, only one NPM can be used in the Cisco 4000 and two NPMs can be used in the Cisco 4500.
Note
Perform the following task in global configuration mode to define the E1 controller and to enter controller configuration mode:
Define the Line Code
Perform the following task in controller configuration mode to define the line code as either alternate mark inversion (AMI) or HDB3:
Contact your local telephone service provider to determine the line-code requirements of the physical E1 line. The E1 controller values must match the service provided by the telephone company.
Define the Framing Characteristics
Perform the following task in controller configuration mode to define the framing characteristics as either CRC4 or no-CRC4, or as the version of E1 framing used in Australia only:
Define the framing characteristics as either CRC4 or no-CRC4.
framing {crc4 | no-crc4} [australia]
Contact your local telephone service provider to determine the framing requirements of the physical E1 line. The E1 controller values must match the service provided by the telephone company.
Define the E1 Channel Groups
You can define up to 30 channel groups for each E1 adapter. You must define the time slots that belong with each channel group. Channel groups are numbered 0 to 30, and time slots are numbered 1 to 31. Perform the following task in controller configuration mode to define the channel groups and time slots:
Define the channel group number and, if needed, circuit speed.
channel-group number timeslots range [speed {48 | 56 | 64}]
Working with your local service provider, you can create channel-groups with from one to 31 timeslots. These timeslots can be in any order, contiguous or noncontiguous. Channel-group speeds can be 48 kbps, 56 kbps, or 64 kbps; the default is 64 kbps if the speed is not specified. The speed you choose must match the speed specified by your service provider.
Defining a channel group creates a serial interface; defining multiple channel groups creates an equal number of serial interfaces that you can configure independently. The channel group numbers for each E1 controller can be arbitrarily assigned.
Configure the Channelized E1 Channel Groups
After you define the E1 channel groups, you can configure each channel group as a serial interface. In other words, you can think of each channel group as a virtual serial interface. Subinterface configuration on the created interface is also supported. To enter interface configuration mode and configure the serial interface that corresponds to a channel group, perform the following task either in global configuration mode or controller configuration mode:
Define the serial interface for an E1 channel group.
interface serial slot/port:channel-group (Cisco 7000 series)
interface serial number:channel-group (Cisco 4000 series)
E1 channel groups support local loopback. You can enable local loopback for specified individual channel groups with the loopback local command. Local loopback loops the entire specified channel group both toward the line and toward the router.
E1 channel groups do not respond to any remote loopback codes. That is, you cannot remotely loop an E1 channel group.
Configure Channelized T1
Support for channelized T1 (also referred to as fractional T1) is provided on the following platforms:
•
•
Each T1 adapter can support a maximum of 24 DS0 channel groups. Each channel group is presented to the system as a serial interface that can be configured individually. The Cisco 7000 MIP can support one or two CxCT1 adapters, providing a maximum of 48 channel groups per MIP. The Cisco 4000 supports a one adapter, providing a maximum of 24 channel groups. In effect, up to 24 DS0 circuits are multiplexed to a single hardware adapter.
Use the show controllers t1 EXEC command to display current T1 status. This command provides a report for each physical interface configured to support channelized T1.
Channelized T1 supports the following WAN protocols:
•
•
•
•
•
•
•
When a channelized T1 adapter is used for ISDN PRI, it can support DDR; when it is not used for ISDN PRI, it does not support DDR. Refer to the "Configuring ISDN" chapter in the Wide-Area Networking Configuration Guide for more information.
The Cisco channelized T1 controllers require the use of a CSU when connected to a public network. This device should take a T1 signal from the public network and provide a T1 signal to the channelized T1 controller.
Channelized T1 Task List
Using channelized T1 controller and serial interface configuration commands, you can perform the tasks in the following sections to configure channelized T1:
•
•
See the end of this chapter for "Interface Configuration Examples."
Configure the T1 Controller
To configure the T1 physical characteristics, you first define the physical location of the MIP and CxCT1 in the Cisco 7000 series router. A Cisco 7000 router can have up to four MIP and eight CxCT1 interfaces. A Cisco 7010 router can have up to three MIP and six CxCT1 interfaces. The Cisco 4000 series routers can support up to three network processor module (NPM) cards, each with one interface when running it as a channelized interface card. However, when the card is used to run ISDN PRI, only one NPM can be used in the Cisco 4000 and two NPMs can be used in the Cisco 4500.
Note
Perform the following task in global configuration mode to define the T1 controller and to enter controller configuration mode:
Define the Line Code
Perform the following task in controller configuration mode to define the line code as either alternate mark inversion (AMI) or bipolar 8 zero substitution (B8ZS):
Contact your local telephone service provider to determine the line-code requirements of the physical T1 line. The T1 controller values must match the service provided by the telephone company.
Define the Framing Characteristics
Perform the following task in controller configuration mode to define the framing characteristics as either super frame (SF) or extended super frame (ESF):
Define the framing characteristics as either SF or ESF; SF is the default.
framing {sf | esf}
Contact your local telephone service provider to determine the framing requirements of the physical T1 line. The T1 controller values must match the service provided by the telephone company.
Define the Clock Source
Under normal usage, skip this step. You must define the clock source only when connecting two devices back-to-back for testing purposes. The clock source normally comes from the T1 line rather than from the router interface, but when you connect two routers back-to-back for testing purposes, one device supplies an internal clock source. To define the clock source, perform the following task in controller configuration mode:
Define the clock source if you are connecting two cards back-to-back for testing purposes; the default source is the line.
clock source {line | internal}
Define the T1 Channel Groups
You can define up to 24 channel groups for each T1 adapter.You must define the timeslots that belong with each channel group. Channel groups are numbered 0 to 23, and timeslots are numbered 1 to 24. Perform the following task in controller configuration mode to define the channel groups and timeslots:
Define the channel group number and, if needed, circuit speed.
channel-group number timeslots range [speed {48 | 56 | 64}]
Working with your local service provider, you can create channel-groups with from one to 24 timeslots. These timeslots can be in any order, contiguous or noncontiguous. In the United States, channel-group speeds can be either 56 kbps or 64 kbps; the default is 56 kbps. If 64 kbps is used, it is recommended to be used with framing type of ESF and a linecode of B8ZS. The speed you select must match the speed provided by the telephone company.
Defining a channel group creates a serial interface; defining multiple channel groups creates an equal number of serial interfaces that you can configure independently. The channel group numbers for each T1 controller can be arbitrarily assigned.
Configure the Channelized T1 Channel Groups
After you define the T1 channel groups, you can configure each channel group as a serial interface. In other words, you can think of each channel group as a virtual serial interface. Subinterface configuration is also supported on the created serial interface. Perform the following task either in global configuration mode or controller configuration mode to enter interface configuration mode and configure the serial interface that corresponds to a channel group:
Define the serial interface for a T1 channel group.
interface serial slot/port:channel-group (Cisco 7000 series)
interface serial number:channel-group (Cisco 4000 series)
Troubleshooting Channelized E1 and Channelized T1
When troubleshooting channelized T1 or E1, you must first decide if the problem is with a particular channel group, or with the T1 or E1 line.
If the problem is with a single channel group, you have an potential interface problem.
If the problem is with the T1 or E1 line, or with all channel groups, you have a potential controller problem.
Troubleshooting Channelized T1/E1 Controllers
When you troubleshoot E1 or T1 controllers, first check that the configuration is correct. The framing type and line code should match to what the service provider has specified. Then check channel group and PRI-group configurations, especially to verify that the timeslots and speeds are what the service provider has specified.
At this point, the show controller t1 or show controller e1 commands should be used to check for T1 or E1 errors. Use the command several times to determine if error counters are increasing, or if the line status is continually changing. If this is occurring, you need to work with the service provider.
Note
Channelized T1 Controller Loopbacks
For the T1 controller, two loopbacks are available for testing.
•
•
Local Loopback: The local loopback loops the controller both toward the router, and toward the line. Since the loopback is done internally to the router, the controller should transition to the UP state within approximately 10 seconds, and no further T1 errors should be detected.
All channel groups will be looped back; if the encapsulation on that channel group supports loopbacks (for example, HDLC and PPP), you can test that channel group by pinging the interface address. For example, if you have assigned an IP address to the serial interface defined for a channel group, you can ping that IP address.
To place the controller into local loopback, perform the following task in controller configuration mode.
Loop the T1 controller toward the router and toward the line.
loopback local (controller)
To test a channel group, perform the following task in EXEC mode:
Check errors if any. by performing the following task in EXEC mode:
If any errors occur, or the controller fails to change to the UP state, please contact the Cisco TAC.
Since the controller local loopback is bidirectional, the service provider can test the line integrity using a T1 BERT test set.
Remote Loopback: The second T1 controller loopback is a remote loopback. This loopback can be used only if the entire T1 goes to a remote CSU. This is not the case with 99.9% of channelized T1. When the loopback remote controller command is executed, an inband CSU loop-up code will be sent over the entire T1, which will attempt to loop up the remote CSU. To place the controller in remote loopback, perform the following task in controller configuration mode:
Note
Channelized E1 Controller Loopback
For the E1 controller, only the local loopback is available. Local loopback operates the same as the local loopback on the T1 controller, forming a bidirectional loopback, both toward the router, and toward the line.To place the E1 controller in local loopback, perform the following task in controller configuration mode:
Place the E1 controller in local loopback toward the router and toward the line.
loopback (controller)
All channel groups will be looped back; if the encapsulation on that channel group supports loopbacks (for example, HDLC and PPP), you can test that channel group by pinging the interface address. For example, if you have assigned an IP address to the serial interface defined for a channel group, you can ping that IP address.
To place the controller into local loopback, perform the following task in controller configuration mode.
Loop the T1 controller toward the router and toward the line.
loopback local (controller)
To test a channel group, perform the following task in EXEC mode:
Check errors if any. by performing the following task in EXEC mode:
If any errors occur, it is most likely a hardware problem; please contact the Cisco TAC. At the same time, the service provider can test the line by using a T1 BERT test set.
Troubleshooting Channelized T1/E1 Channel Groups
Each channelized T1 or channelized E1 channel group is treated as a separate serial interface. To troubleshoot channel groups, first verify configurations and check everything that is normally checked for serial interfaces. You can verify that the timeslots and speed are correct for the channel group by checking for CRC errors and aborts on the incoming line.
Channelized T1/E1 Channel Group Loopbacks
Note
Two loopbacks are available for channel groups:
•
•
Interface Local Loopback: Interface local loopback is a bi-directional loopback, which will loopback toward the router and toward the line. The entire set of timeslots for the channel group are looped back. The service provider can use a BERT test set to test the link from the central office to your local router, or the remote router can test using pings to their local interface (which will go from the remote site, looped back at your local site, and return to the interface on the remote site).
To place the serial interface (channel group) into local loopback, perform the following task in interface configuration mode:
Interface Remote Loopback: Remote loopback is the ability to put the remote DDS CSU/DSU in loopback. It will work only with channel groups that have a single DS0 (1 timeslot), and with equipment that works with a latched CSU loopback as specified in AT&T specification TR-TSY-000476, "OTGR Network Maintenance Access and Testing." To place the serial interface (channel group) in remote loopback, perform the following task in interface configuration mode:
Place the serial interface (channel group) in remote loopback.
loopback remote (interface)
Using the loopback remote interface command sends a latched CSU loopback command to the remote CSU/DSU. The router must detect the response code, at which time the remote loopback is verified.
Configure a Dialer Interface
See the chapter "Configuring DDR" in the Wide-Area Networking Configuration Guide for information about how to configure a dialer interface.
Configure an Ethernet Interface
Support for the Ethernet interface is supplied on one of the following Ethernet network interface cards or systems:
•
•
•
•
•
•
Use the show interfaces, show controllers mci, and show controllers cbus EXEC commands to display the Ethernet port numbers. These commands provide a report for each interface supported by the router or access server.
Ethernet Interface Task List
Perform the tasks in the following sections to configure features on an Ethernet interface. The first task is required; the remaining tasks are optional.
•
•
•
•
Specify an Ethernet Interface
To specify an Ethernet interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration.
interface ethernet number
Begin interface configuration for the Cisco 7000 series.
interface ethernet slot/port
Configure Ethernet Encapsulation
Currently, there are three common Ethernet encapsulation methods:
•
•
•
The encapsulation method you use depends upon the type of Ethernet media connected to the router or access server and the routing or bridging application you configure. Establish Ethernet encapsulation by performing one of the following tasks in interface configuration mode:
Select ARPA Ethernet encapsulation.
encapsulation arpa
Select SAP Ethernet encapsulation.
encapsulation sap
Select SNAP Ethernet encapsulation.
encapsulation snap
For an example of selecting Ethernet encapsulation, see the section "Enabling Ethernet Encapsulation Example" at the end of this chapter. See also the chapters describing specific protocols or applications.
Configure the Ethernet Network Interface Module on the Cisco 4000
You can specify the type of Ethernet network interface module (NIM) configuration on the Cisco 4000. To do so, perform one of the following tasks in interface configuration mode:
Select a 15-pin Ethernet connector.
media-type aui
Select an RJ45 Ethernet connector.
media-type 10baset
Extend the 10BaseT Capability
On a Cisco 4000 or Cisco 4500, you can extend the twisted-pair 10BaseT capability beyond the standard 100 meters by reducing the squelch (signal cutoff time). This feature applies only to the LANCE controller 10BaseT interfaces. LANCE is the AMD controller chip for the Cisco 4000 and Cisco 4500 Ethernet interface.
To reduce squelch, perform the first task that follows in interface configuration mode. You can later restore the squelch by performing the second task.
Configure a Fiber Distributed Data Interface (FDDI)
The Fiber Distributed Data Interface (FDDI) is an ANSI-defined standard for timed 100-Mbps token passing over fiber-optic cable. FDDI is not supported on access servers.
An FDDI network consists of two counter token-passing fiber-optic rings. On most networks, the primary ring is used for data communication and the secondary ring is used as a hot standby. The FDDI standard sets a total fiber length of 200 kilometers. (The maximum circumference of the FDDI network is only half the specified kilometers because of the wrapping or looping back of the signal that occurs during fault isolation.)
The FDDI standard allows a maximum of 500 stations with a maximum distance between active stations of two kilometers when interconnecting them with multimode fiber or ten kilometers when interconnected via single mode fiber, both of which are supported by our FDDI interface controllers. The FDDI frame can contain a minimum of 17 bytes and a maximum of 4500 bytes. Our implementation of FDDI supports Station Management (SMT) Version 7.3 of the X3T9.5 FDDI specification, offering a single MAC dual-attach interface that supports the fault-recovery methods of the dual attachment stations (DASs). The mid-range platforms also support single attachment stations (SASs).
Support for FDDI is supplied on one of our FDDI interface cards, as follows:
•
•
•
•
We also provide support for some of the FDDI MIB variables as described in RFC 1285, "FDDI Management Information Base," published in January 1992 by Jeffrey D. Case of the University of Tennessee and SNMP Research, Inc. One such variable that we support is snmpFddiSMTCFState.
FDDI interface configuration is not required for dual homing. The FDDI interface recognizes that it is attached to two M ports on the concentrators and automatically supports dual homing.
Using Connection Management (CMT) Information
Connection Management (CMT) is an FDDI process that handles the transition of the ring through its various states (off, on, active, connect, and so on) as defined by the X3T9.5 specification. The FIP provides CMT functions in microcode.
A partial sample output of the show interfaces fddi command follows, along with an explanation of how to interpret the CMT information in the output.
Phy-A state is active, neighbor is B, cmt signal bits 08/20C, status ALSPhy-B state is active, neighbor is A, cmt signal bits 20C/08, status ILSCFM is thru A, token rotation 5000 usec, ring operational 0:01:42Upstream neighbor 0800.2008.C52E, downstream neighbor 0800.2008.C52EThe show interfaces fddi example shows that Physical A (Phy-A) completed CMT with its neighbor. The state is active and the display indicates a Physical B-type neighbor.
The sample output indicates cmt signal bits 08/20C for Phy-A. The transmit signal bits are 08. Looking at the PCM state machine, 08 indicates that the port type is A, the port compatibility is set, and the LCT duration requested is short. The receive signal bits are 20C, which indicate the neighbor type is B, port compatibility is set, there is a MAC on the port output, and so on.
The neighbor is determined from the received signal bits, as follows:
Interpreting the bits in the diagram above, the received value equals 0x20C. Bit positions 1 and 2 (0 1) indicate a Physical B-type connection.
The transition states displayed indicate that the CMT process is running and actively trying to establish a connection to the remote physical connection. The CMT process requires state transition with different signals being transmitted and received before moving on to the state ahead as indicated in the PCM state machine. The ten bits of CMT information are transmitted and received in the Signal State. The NEXT state is used to separate the signaling performed in the Signal State. Therefore, in the preceding sample output, the NEXT state was entered 11 times.
Note
The CFM state is thru A in the sample output, which means this interface's Phy-A has successfully completed CMT with the Phy-B of the neighbor and Phy-B of this interface has successfully completed CMT with the Phy-A of the neighbor.
The display (or nondisplay) of the upstream and downstream neighbor does not affect the ability to route data. Since the upstream neighbor is also its downstream neighbor in the sample, there are only two stations in the ring: the network server and the router at address 0800.2008.C52E.
FDDI Task List
Perform the tasks in the following sections to configure an FDDI interface. The first task is required; the remaining tasks are optional.
•
•
•
•
•
•
•
Specify an FDDI
To specify an FDDI interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration
interface fddi number
Begin interface configuration for the Cisco 7000 series.
interface fddi slot/port
Enable FDDI Bridging Encapsulation
Cisco FDDI by default uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface when using the CSC-FCI interface card or FIP.
The CSC-C2/FCIT interface card and FIP fully support transparent and translational bridging for the following configurations:
•
•
•
Enabling FDDI bridging encapsulation places the CSC-C2/FCIT interface or FIP into encapsulation mode when doing bridging. In transparent mode, the FCIT interface or FIP interoperates with earlier versions of the CSC-FCI encapsulating interfaces when performing bridging functions on the same ring. When using the CSC-C2/FCIT interface card or FIP, you can specify the encapsulation method by performing the following task in interface configuration mode:
Specify the encapsulation method for the CSC-C2/FCIT interface card or FIP.
fddi encapsulate
When you are translationally bridging, you have to route routable protocols and translationally bridge the rest (such as LAT).
The CSC-FCI interfaces are always in encapsulating bridge mode, so disabling applies only to CSC-C2/FCIT interfaces.
Note
We are currently aware of problems with the following protocols when bridged between Token Ring and other media: AppleTalk, DECnet, IP, Novell IPX, Phase IV, VINES, and XNS. Further, the following protocols might have problems when bridged between FDDI and other media: Novell IPX and XNS. We recommend that these protocols be routed whenever possible.
Set the Token Rotation Time
You can set the FDDI token rotation time to control ring scheduling during normal operation and to detect and recover from serious ring error situations. To do so, perform the following task in interface configuration mode:
The FDDI standard restricts the allowed time to be greater than 4000 microseconds and less than 165,000 microseconds. As defined in the X3T9.5 specification, the value remaining in the token rotation timer (TRT) is loaded into the token holding timer (THT). Combining the values of these two timers provides the means to determine the amount of bandwidth available for subsequent transmissions.
Set the Transmission Valid Timer
You can set the transmission timer to recover from a transient ring error by performing the following task in interface configuration mode:
Control the Transmission Timer
You can set the FDDI control transmission timer to control the FDDI TL-Min time, which is the minimum time to transmit a Physical Sublayer or PHY line state before advancing to the next Physical Connection Management or PCM state as defined by the X3T9.5 specification. To do so, perform the following task in interface configuration mode:
Modify the C-Min Timer
You can modify the C-Min timer on the PCM from its default value of 1600 microseconds by performing the following task in interface configuration mode:
Modify the TB-Min Timer
You can change the TB-Min timer in the PCM from its default value of 100 milliseconds. To do so, perform the following task in interface configuration mode:
Modify the FDDI Timeout Timer
You can change the FDDI timeout timer in the PCM from its default value of 100 milliseconds. To do so, perform the following task in interface configuration mode:
Control SMT Frame Processing
You can disable and reenable SMT frame processing for diagnostic purposes. To do so, perform one of the following tasks in interface configuration mode:
Disable SMT frame processing.
no fddi smt-frames
Enable SMT frame processing.
fddi smt-frames
Enable Duplicate Address Checking
You can enable the duplicate address detection capability on the FDDI. If the FDDI finds a duplicate address, it displays an error message and shuts down the interface. To enable duplicate address checking, perform the following task in interface configuration mode:
Set the Bit Control
You can set the FDDI bit control to control the information transmitted during the Connection Management (CMT) signaling phase. To do so, perform the following task in interface configuration mode:
Control the CMT Microcode
You can control whether the CMT onboard functions are on or off. The CSC-FCI and CSC-C2/FCIT interface cards and FIP provide CMT functions in microcode. These functions are separate from those provided on the processor card and are accessed through EXEC commands.
The default is for the FCIT and FIP CMT functions to be on. A typical reason to disable is when you work with new FDDI equipment and have problems bringing up the ring. If you disable the CMT microcode, the following actions occur:
•
•
To disable the CMT microcode, perform the following task in interface configuration mode:
Start and Stop FDDI
In normal operation, the FDDI interface is operational once the interface is connected and configured. You can start and stop the processes that perform the CMT function and allow the ring on one fiber to be stopped. To do so, perform either of the following tasks in EXEC mode:
Start CMT processes on FDDI ring.
cmt connect [interface-name [phy-a | phy-b]]
Stop CMT processes on FDDI ring.
cmt disconnect [interface-name [phy-a | phy-b]]
Do not do either of the preceding tasks during normal operation of FDDI; they are performed during interoperability tests.
Control the FDDI SMT Message Queue Size
You can set the maximum number of unprocessed FDDI Station Management (SMT) frames that will be held for processing. Setting this number is useful if the router you are configuring gets bursts of messages arriving faster than the router can process them. To set the number of frames, perform the following task in global configuration mode:
Preallocate Buffers for Bursty FDDI Traffic
The FCI card preallocates three buffers to handle bursty FDDI traffic (for example, NFS bursty traffic). You can change the number of preallocated buffers by performing the following task in interface configuration mode:
Configure a High-Speed Serial Interface (HSSI)
The High-Speed Serial Interface (HSSI) consists of the following components:
•
•
The controller card provides a single, full-duplex, synchronous serial interface capable of transmitting and receiving data at up to 52 megabits per second (Mbps). The HSSI is an approved standard (ANSI/EIA RS-613) providing connectivity to T3 (DS-3), E3, SMDS (at a DS-3 route), and other high-speed wide-area services through a DSU or line termination unit.
•
•
•
HSSI Task List
Perform the tasks in the following sections to configure an HSSI interface. The first task is required; the remaining tasks are optional.
Specify an HSSI
To specify an HSSI and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration.
interface hssi number
Begin interface configuration for the Cisco 7000 series.
interface hssi slot/port
Specify HSSI Encapsulation
The HSSI supports the serial encapsulation methods, except for X.25-based encapsulations. The default method is HDLC. You can define the encapsulation method by performing the following task in interface configuration mode:
Configure HSSI encapsulation.
encapsulation {atm-dxi | hdlc | frame-relay | ppp | sdlc-primary | sdlc-secondary | smds | stun}
For information about PPP, see the section "Configure PPP" in the section "Configure a Synchronous Serial Interface" later in this chapter.
Invoke ATM on an HSSI Line
If you have an ATM DSU, you can invoke ATM over a HSSI line. You do so by mapping an ATM virtual path identifier (VPI) and virtual channel identifier (VCI) to a DXI frame address. ATM-DXI encapsulation defines a data exchange interface that allows a DTE (such as a router) and a DCE (such as an ATM DSU) to cooperate to provide a User-Network Interface (UNI) for ATM networks.
To invoke ATM over a serial line, perform the following tasks in interface configuration mode:
Step 1
encapsulation atm-dxi
Step 2
atm-dxi map protocol address vpi vci [broadcast]1
1 This command is documented in the "ATM Commands" chapter of the Wide-Area Networking Command Reference.
You can also configure the atm-dxi map command on a serial interface.
To configure an ATM interface using an AIP card, see the "Configuring ATM" chapter in the Wide-Area Networking Configuration Guide.
Convert HSSI to Clock Master
You can convert the HSSI interface into a 45-MHz clock master by performing the following task in interface configuration mode:
Configure a Hub Interface
The Cisco 2500 series includes routers that have hub functionality for an Ethernet interface. The hub is a multiport repeater. The advantage of an Ethernet interface over a hub is that the hub provides a star-wiring physical network configuration while the Ethernet interface provides 10BaseT physical network configuration. The router models with hub ports and their configurations are as follows:
•
•
•
We provide SNMP management of the Ethernet hub as specified in RFC 1516.
To configure hub functionality on an Ethernet interface, perform the tasks in the following sections. The first task is required; the remaining are optional.
•
•
•
•
See the "Hub Configuration Examples" section the end of this chapter.
Enable a Hub Port
To enable a hub port, perform the following tasks in global configuration mode:
Step 1
hub ethernet number port [end-port]
Step 2
no shutdown
Disable or Enable Automatic Receiver Polarity Reversal
On Ethernet hub ports only, the hub ports can invert, or correct, the polarity of the received data if the port detects that the received data packet waveform polarity is reversed due to a wiring error. This receive circuitry polarity correction allows the hub to repeat subsequent packets with correct polarity. When enabled, this function is executed once after reset of a link fail state.
Automatic receiver polarity reversal is enabled by default. To disable this feature on a per-port basis, perform the following task in hub configuration mode:
To reenable automatic receiver polarity reversal on a per-port basis, perform the following task in hub configuration mode:
Disable or Enable the Link Test Function
The link test function applies to Ethernet hub ports only. The Ethernet ports implement the link test function as specified in the 802.3 10BaseT standard. The hub ports will transmit link test pulses to any attached twisted pair device if the port has been inactive for more than 8 to 17 milliseconds.
If a hub port does not receive any data packets or link test pulses for more than 65 to 132 milliseconds and the link test function is enabled for that port, that port will enter link fail state and be disabled from transmit and receive functions. The hub port will be reenabled when it receives four consecutive link test pulses or a data packet.
The link test function is enabled by default. To allow the hub to interoperate with 10BaseT twisted-pair networks that do not implement the link test function, the hub's link test receive function can be disabled on a per-port basis. To do so, perform the following task in hub configuration mode:
To reenable the link test function on a hub port connected to an Ethernet interface, perform the following task in hub configuration mode:
Enable Source Address Control
On an Ethernet hub port only, you can configure a security measure such that the port accepts packets only from a specific MAC address. For example, suppose your workstation is connected to port 3 on a hub, and source address control is enabled on port 3. Your workstation has access to the network because the hub accepts any packet from port 3 with your workstation's MAC address. Any packets arriving with a different MAC address cause the port to be disabled. The port is reenabled after 1 minute and the MAC address of incoming packets is checked again.
To enable source address control on a per-port basis, perform the following task in hub configuration mode:
If you omit the optional MAC address, the hub remembers the first MAC address it receives on the selected port, and allows only packets from the learned MAC address.
See the examples of establishing source address control at the end of this chapter in "Hub Configuration Examples."
Enable SNMP Illegal Address Trap (for Cisco 2505, Cisco 2507, and Cisco 2516)
To enable the router to issue an SNMP trap when an illegal MAC address is detected on an Ethernet hub port, perform the following tasks in hub configuration mode:
You may need to set up a host receiver for this trap type (snmp-server host) for a nms to receive this trap type. The default is no trap. For an example of configuring a SNMP trap for an Ethernet hub port, see the section "Hub Configuration Examples" at the end of this chapter.
Configure an ISDN Basic BRI, MBRI, or PRI Interface
ISDN Primary Rate Interface (PRI) is supported on the Cisco 4000, the Cisco 4500, and the Cisco 7000 series routers using T1 or E1 versions of the Multichannel Interface Processor (MIP) card in conjunction with PRI signaling software. Channelized T1 ISDN PRI offers 23 B-channels and 1 D-channel. Channelized E1 ISDN PRI offers 30 B-channels and 1 D-channel.
The Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) is supported on the Cisco 1003 model, Cisco 2500 series, Cisco 3000 series, and Cisco 4000 series routers. ISDN Multiport BRI (MBRI) is supported on the Cisco 4000 and Cisco 4500 only, which have a multichannel NIM. The multichannel card supports one or two BRI port adapters, providing either 4 or 8 ports, respectively.
For information on how to configure ISDN, see the chapter entitled "Configuring ISDN" in the Wide-Area Networking Configuration Guide. For command information, refer to the chapter entitled "ISDN Commands" in the Wide-Area Networking Command Reference.
Note
Configure a LAN Extender Interface
The Cisco 1001 and Cisco 1002 LAN Extenders are two-port chassis that connects a remote Ethernet LAN to a core router at a central site (see ). The LAN Extender is intended for small networks at remote sites.
The remote site can have one Ethernet network. The core router can be a Cisco 2500 series, Cisco 4000 series, Cisco 4500 series, Cisco 4700 series, Cisco 7000 series, or AGS+ router running Cisco IOS Release 10.2(2) or later, which support the LAN Extender host software. The connection between the LAN Extender and the core router is made via a short leased serial line, typically a 56-kbps or 64-kbps line. However, the connection can also be via T1 or E1 lines.
Figure 18 Cisco 1000 Series LAN Extender Connection to a Core Router
is an expanded view of that shows all the components of the LAN Extender connection to a core router. On the left is the core router, which is connected to the LAN Extender as well as to other networks. In the core router, you configure a LAN Extender interface, which is a logical interface that connects the core router to the LAN Extender chassis. In the core router, you also configure a serial interface, which is the physical interface that connects the core router to the LAN Extender. You then bind, or associate, the LAN Extender interface to the physical serial interface.
shows the actual physical connection between the core router and the LAN Extender. The serial interface on the core router is connected by a leased serial line to a serial port on the LAN Extender. This creates a virtual Ethernet connection, which is analogous to having inserted an Ethernet interface processor into the core router.
Figure 19 Expanded View of Cisco 1000 Series LAN Extender Connection
Although there is a physical connection between the core router and the LAN Extender, what you actually manage is a remote Ethernet LAN. shows the connection you are managing, which is a LAN Extender interface connected to an Ethernet network. The virtual Ethernet connection (the serial interface and LAN Extender) has been removed from the figure, and points A and B, which in were separated by the virtual Ethernet connection, are now adjacent. All LAN Extender interface configuration tasks described in this chapter apply to the interface configuration shown in .
Figure 20 LAN Extender Interface Connected to an Ethernet Network
To install a LAN Extender at a remote site, refer to the Cisco 1000 Series Hardware Installation publication.
After the LAN Extender has been installed at the remote site, you need to obtain its MAC address. Each LAN Extender is preconfigured with a permanent (burned-in) MAC address. The address is assigned at the factory; you cannot change it. The MAC address is printed on the LAN Extender's packing box. (If necessary, you can also display the MAC address with the debug ppp negotiation command.) The first three octets of the MAC address (the vendor code) are always the hexadecimal digits 00.00.0C.
You can upgrade software for the LAN Extender on the host router with a TFTP server that is local to the host router.
The LAN Extender and core router communicate using the Point-to-Point Protocol (PPP). Before you can configure the LAN Extender from the core router, you must first enable PPP encapsulation on the serial interface to which the LAN Extender is connected.
You then configure the LAN Extender from the core router—either a Cisco 4000 series or
Cisco 7000 series router—as if it were simply a network interface board. The LAN Extender cannot be managed or configured from the remote Ethernet LAN or via a Telnet session.To configure the LAN Extender, you configure a logical LAN Extender interface on the core router and assign the MAC address from your LAN Extender to that interface. Subsequently, during the PPP negotiation on the serial line, the LAN Extender sends its preconfigured MAC address to the core router. The core router then searches for an available (preconfigured) LAN Extender interface, seeking one to which you have already assigned that MAC address. If the core router finds a match, it binds, or associates, that LAN Extender interface to the serial line on which that MAC address was negotiated. At this point, the LAN Extender interface is created and is operational. If the MAC address does not match one that is configured, the connection request is rejected. illustrates this binding process.
Figure 21 Binding a Serial Line to a LAN Extender Interface
LAN Extender Interface Configuration Task List
To configure a LAN Extender interface, perform the tasks described in the following sections. The first task is required; the remainder are optional.
•
•
•
•
•
To monitor the LAN Extender interface, see the section "Monitor and Maintain the Interface" later in this chapter. For configuration examples, see the "Enabling a LAN Extender Interface Example" and the "LAN Extender Interface Access List Examples" sections at the end of this chapter.
Configure and Create a LAN Extender Interface
To configure and create a LAN Extender interface, you configure the LAN Extender interface itself and the serial interface to which the LAN Extender is physically connected. The order in which you configure these two interface interfaces does not matter. However, you must first configure both interfaces in order for the LAN Extender interface to bind (associate) to the serial interface.
To create and configure a LAN Extender interface, perform the following tasks:
Step 1
or
Configure a LAN Extender on a Cisco 7000.interface lex number
interface lex slot/portStep 2
lex burned-in-address ieee-address
Step 3
ip address ip-address mask1
Step 4
exit2
Step 5
interface serial number
Step 6
encapsulation ppp
Step 7
Ctrl-Z
Step 8
copy running-config startup-config3
1 This command is documented in the "IP Commands" chapter of the Network Protocols Command Reference, Part 1.
2 This command is documented in the "User Interface Commands" chapter of the Configuration Fundamentals Command Reference.
3 This command is documented in the "System Images, Microcode Images, and Configuration File Load Commands" chapter of the Configuration Fundamentals Command Reference.
Note that there is no correlation between the number of the serial interface and the number of the LAN Extender interface. These interfaces can have the same or different numbers.
Note
Define Packet Filters
You can configure specific administrative filters that filter frames based on their source MAC address. The LAN Extender forwards packets between a remote LAN and a core router. It examines frames and transmits them through the internetwork according to the destination address, and it does not forward a frame back to its originating network segment.
You define filters on the LAN Extender interface in order to control which packets from the remote Ethernet LAN are permitted to pass to the core router. (See .) These filters are applied only on traffic passing from the remote LAN to the core router. Filtering on the LAN Extender interface is actually performed in the LAN Extender, not on the core router. This means that the filtering is done using the LAN Extender CPU, thus off-loading the function from the core router. This process also saves bandwidth on the WAN, because only the desired packets are forwarded from the LAN Extender to the core router. Whenever possible, you should perform packet filtering on the LAN Extender.
Figure 22 Packet Filtering on the LAN Extender
You can also define filters on the core router to control which packets from the LAN Extender interface are permitted to pass to other interfaces on the core router. (See .) You do this using the standard filters available on the router. This means that all packets are sent across the WAN before being filtered and that the filtering is done using the core router's CPU.
Figure 23 Packet Filtering on the Core Router
The major reason to create access lists on a LAN Extender interface is to prevent traffic that is local to the remote Ethernet LAN from traversing the WAN and reaching the core router. You can filter packets by MAC address, including vendor code, and by Ethernet type code. To define filters on the LAN Extender interface, perform the tasks described in one or both of the following sections:
•
Note
When defining access lists, keep the following points in mind:
•
•
•
•
•
•
Filter by MAC Address and Vendor Code
You can create access lists to administratively filter MAC addresses. These access lists can filter groups of MAC addresses, including those with particular vendor codes. There is no noticeable performance loss in using these access lists, and the lists can be of indefinite length. You can filter groups of MAC addresses with particular vendor codes by performing the tasks that follow:
Step 1
Step 2
To create a vendor code access list, perform the following task in global configuration mode:
Create an access list to filter frames by canonical (Ethernet-ordered) MAC address.
access-list access-list-number {permit | deny} address mask
Note
Once you have defined an access list to filter by a particular vendor code, you can assign this list to a particular LAN Extender interface so that the interface will then filter based on the MAC source addresses of packets received on that LAN Extender interface. To apply the access list to an interface, perform the following task in interface configuration mode:
Assign an access list to an interface for filtering by MAC source addresses.
lex input-address-list access-list-number
For an example of creating an access list and applying it to a LAN Extender interface, see the section "LAN Extender Interface Access List Examples" in the section "Interface Configuration Examples" at the end of this chapter.
Filter by Protocol Type
You can filter by creating a type-code access list and applying it to a LAN Extender interface.
The LAN Extender interface can filter only on bytes 13 and 14 of the Ethernet frame. In Ethernet packets, these two bytes are the type field. For a list of Ethernet type codes, refer to the "Ethernet Type Codes" appendix in the Bridging and IBM Networking Command Reference. In 802.3 packets, these two bytes are the length field.
To filter by protocol type, perform the following tasks:
Step 1
Step 2
Note
To create a protocol-type access list, perform the following task in global configuration mode:
Create an access list to filter frames by protocol type.
access-list access-list-number {permit | deny} type-code wild-mask
To apply an access list to an interface, perform the following task in interface configuration mode:
Add a filter for Ethernet- and SNAP-encapsulated packets on input.
lex input-type-list access-list-number
For an example of creating an access list and applying it to a LAN Extender interface, see the section "LAN Extender Interface Access List Examples" in the section "Interface Configuration Examples" at the end of this chapter.
Control Priority Queuing
Priority output queuing is an optimization mechanism that allows you to set priorities on the type of traffic passing through the network. Packets are classified according to various criteria, including protocol and subprotocol type. Packets are then queued on one of four output queues. For more information about priority queuing, refer to the "Managing the System" chapter.
To control priority queuing on a LAN Extender interface, perform the following tasks:
•
•
To establish queuing priorities based on the protocol type, perform the following task in global configuration mode:
Establish queuing priorities based on the protocol type.
priority-list list protocol protocol {high | medium | normal | low} 1
or
priority-list list protocol bridge {high | medium | normal | low} list list-number
1 This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference
You then assign a priority list to an interface. You can assign only one list per interface. To assign a priority list to a LAN Extender interface, perform the following task in interface configuration mode:
Assign a priority list to a LAN Extender interface, thus activating priority output queuing on the LAN Extender.
lex priority-group group
Control the Sending of Commands to the LAN Extender
Each time the core router sends a command to the LAN Extender, the LAN Extender responds with an acknowledgment. The core router waits for the acknowledgment for a predetermined amount of time. If it does not receive an acknowledgment in this time period, the core router resends the command.
By default, the core router waits 2 seconds for an acknowledgment from the LAN Extender. You might want to change this interval if your connection to the LAN Extender requires a different amount time. To determine whether commands to the LAN Extender are timing out, use the debug lex rcmd privileged EXEC command. To change this interval, perform the following task in interface configuration mode:
Set the amount of time that the core router waits to receive an acknowledgment from the LAN Extender.
lex timeout milliseconds
By default, the core router sends each command ten times before giving up. The core router displays an error message when it gives up sending commands to the LAN Extender. To change this default, perform the following task in interface configuration mode:
Set the number of times the core router sends a command to the LAN Extender before giving up.
lex retry-count number
Shut Down and Restart the LAN Extender's Ethernet Interface
From the core router, you can shut down the LAN Extender's Ethernet interface. This stops traffic on the remote Ethernet LAN from reaching the core router, but leaves the LAN Extender interface that you created intact.
Note that logically it makes no sense to shut down the serial interface on the LAN Extender. There are no commands that might allow you to do this.
To shut down the LAN Extender's Ethernet interface, perform the following task in interface configuration mode:
To restart the LAN Extender's Ethernet interface, perform the following task in interface configuration mode:
Restart the LAN Extender
To reboot the LAN Extender and reload the software, perform the following task in privileged EXEC mode:
Download a Software Image to the LAN Extender
When the LAN Extender is powered on, it runs the software image that is shipped with the unit. You can download a new software image from a TFTP server or from Flash memory on the core router to the LAN Extender.
To download a software image to the LAN Extender, perform one of the following tasks in privileged EXEC mode:
Download a software image from a TFTP server.
copy tftp lex number
Download a software image from Flash memory.
copy flash lex number
Troubleshoot the LAN Extender
The primary means of troubleshooting the LAN Extender is by using the light emitting diodes (LEDs) that are present on the chassis. This section will help you assist the remote user at the LAN Extender site who can observe the LEDs.
The key to problem solving is to try to isolate the problem to a specific subsystem. By comparing what the system is doing to what it should be doing, the task of isolating a problem is greatly simplified.
The Cisco 1000 series LAN Extender uses multiple LEDs to indicate its current operating condition. By observing the LEDs, any fault conditions that the unit is encountering can be observed. The system LEDs are located on the front panel of your LAN Extender (see ).
Figure 24 LAN Extender LEDs
When there is a problem with the LAN Extender, a user at the remote site should contact you and report the condition of the LEDs located on the front panel of the LAN Extender. You can then use this information to diagnose or verify the operation of the system. explains the LEDs.
Table 6 LED Trouble Indicators
For more complete network troubleshooting information, refer to the Troubleshooting Internetworking Systems.
Configure a Loopback Interface
You can specify a software-only interface called a loopback interface to emulate an interface. It is supported on all platforms. A loopback interface is a virtual interface that is always up and allows BGP and RSRB sessions to stay up even if the outbound interface is down.
You can use the loopback interface as the termination address for BGP sessions, for RSRB connections, or to establish a Telnet session from the device's console to its auxiliary port when all other interfaces are down. You can also use a loopback interface to configure IPX-PPP on asynchronous interfaces. To do so, you must associate an asynchronous interface with a loopback interface configured to run IPX. In applications where other routers or access servers attempt to reach this loopback interface, you should configure a routing protocol to distribute the subnet assigned to the loopback address.
Packets routed to the loopback interface are rerouted back to the router or access server and processed locally. IP packets routed out the loopback interface but not destined to the loopback interface are dropped. This means that the loopback interface serves as the Null 0 interface also.
Note
To specify a loopback interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration.
interface loopback number
Begin interface configuration for the Cisco 7000 series.
interface loopback slot/port
See the section "Run Interface Loopback Diagnostics" later in this chapter.
Configure a Null Interface
The Cisco IOS software supports a "null" interface. This pseudo-interface functions similarly to the null devices available on most operating systems. This interface is always up and can never forward or receive traffic; encapsulation always fails. The only interface configuration command that you can specify for the null interface is no ip redirects.
The null interface provides an alternative method of filtering traffic. You can avoid the overhead involved with using access lists by directing undesired network traffic to the null interface.
To specify the null interface, perform the following task in global configuration mode:
Specify null 0 (or null0) as the interface type and number. The null interface can be used in any command that has an interface type as an argument. The following example configures a null interface for IP route 127.0.0.0:
ip route 127.0.0.0 255.0.0.0 null 0Configure a Synchronous Serial Interface
Synchronous serial interfaces are supported on the following serial network interface cards or systems:
•
•
•
•
•
•
•
The MCI and SCI cards can query the appliques to determine their types for use in reports displayed by the EXEC show commands. However, they do so only at system startup, so the appliques must be attached when the system is started. Use the show interfaces and show controllers mci EXEC commands to display the serial port numbers. These commands provide a report for each interface that the Cisco IOS software supports.
Synchronous Serial Task List
Perform the tasks in the following sections to configure a synchronous serial interface. The first task is required; the remaining tasks are optional.
•
•
•
•
•
•
•
•
•
•
•
Specify a Synchronous Serial Interface
To specify a synchronous serial interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Specify Synchronous Serial Encapsulation
By default, synchronous serial lines use the High-Level Data Link Control (HDLC) serial encapsulation method, which provides the synchronous framing and error detection functions of HDLC without windowing or retransmission. The synchronous serial interfaces support the following serial encapsulation methods:
•
•
•
•
•
•
•
•
You can define the encapsulation method by performing the following task in interface configuration mode:
Configure synchronous serial encapsulation.
encapsulation {atm-dxi | hdlc | frame-relay | ppp | sdlc-primary | sdlc-secondary | smds | stun | x25}
Encapsulation methods are set according to the type of protocol or application you configure in the Cisco IOS software. ATM-DXI is described in this chapter in the section "Invoke ATM over a Serial Line." PPP is described in the next section "Configure PPP." The remaining encapsulation methods are defined in their respective books and chapters describing the protocols or applications. Serial encapsulation methods are also discussed in the Configuration Fundamentals Command Reference in the chapter "Interface Commands" under the encapsulation command.
Configure PPP
The Point-to-Point Protocol (PPP), described in RFCs 1331 and 1332, encapsulates network layer protocol information over point-to-point links. You can configure PPP on the following types of interfaces:
•
•
•
•
Cisco supports the following upper-layer protocols: AppleTalk, Bridging, CLNS, DECnet, IP, IPX, VINES, and XNS.
The software provides PPP as an encapsulation method. It also provides the Challenge Handshake Authentication Protocol (CHAP) and Password Authentication Protocol (PAP) on serial interfaces running PPP encapsulation.
Magic Number support is available on all serial interfaces. PPP always attempts to negotiate for Magic Numbers, which are used to detect looped-back lines. Depending on how the down-when-looped command is configured, the router might shut down a link if it detects a loop.
To configure PPP, complete the tasks in following sections, as needed for your networking applications:
•
•
•
•
Enable PPP Encapsulation
You can enable PPP on serial lines to encapsulate IP and SLIP datagrams. To do so, perform the following task in interface configuration mode:
Enable CHAP or PAP Authentication
Access control using Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP) is available on all serial interfaces that use PPP encapsulation. The authentication feature reduces the risk of security violations on your router or access server. You can configure either CHAP or PAP for the interface.
Note
When CHAP is enabled on an interface, the local router sends a CHAP packet that requests or "challenges" the remote device (a PC, workstation, router, or access server) attempting to connect to the local router to respond.
The challenge consists of an ID, a random number, and either the host name of the local router or the name of the user on the remote device. This challenge is transmitted to the remote device.
The required response consists of two parts:
•
•
When the local router or access server receives the challenge response, it verifies the secret by performing the same encryption operation as indicated in the response and looking up the required response name. The secret passwords must be identical on the remote device and the local router.
Because the secret is never transmitted, other devices are prevented from stealing it and gaining illegal access to the system. Without the proper response, the remote device cannot connect to the local router.
CHAP transactions occur only at the time a link is established. The local router or access server does not request a password during the rest of the call. (The local device can, however, respond to such requests from other devices during a call.)
To use CHAP, you must perform the following tasks:
Step 1
Once you have enabled CHAP, the local router or access server requires a password from remote devices. If the remote device does not support CHAP, no traffic will be passed to that device.
Step 2
Configure the secret or password for each remote system with which authentication is required. As an alternative, you can also configure TACACS.
To enable CHAP authentication, perform the following tasks in interface configuration mode:
Step 1
ppp authentication {chap | pap} [if-needed]
or
ppp authentication {chap | pap} [list-name]Step 2
or
Configure TACACS.username name password secret 1
ppp use-tacacs [single-line] 1
1 This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference.
The optional keyword if-needed can be used only with TACACS or extended TACACS. The optional keyword list-name can only be used with AAA/TACACS+. CHAP is specified in RFC 1334. It is an additional authentication phase of the PPP Link Control Protocol.
CautionIf you use a list-name that has not been configured with the aaa authentication ppp command, you disable PPP on the line.
To specify the password to be used in CHAP or PAP caller identification, perform the following task in global configuration mode:
Configure authentication.
username name password secret1
1 This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference.
Make sure that this password does not include spaces or underscores.
For an example of CHAP, see the section "CHAP with an Encrypted Password Examples" at the end of this chapter. CHAP and PAP are specified in RFC 1334, "The PPP Authentication Protocols."
Enable Link Quality Monitoring (LQM)
Link Quality Monitoring (LQM) is available on all serial interfaces running PPP. LQM will monitor the link quality, and if the quality drops below a configured percentage, the router shuts down the link. The percentages are calculated for both the incoming and outgoing directions. The outgoing quality is calculated by comparing the total number of packets and bytes sent with the total number of packets and bytes received by the destination node. The incoming quality is calculated by comparing the total number of packets and bytes received with the total number of packets and bytes sent by the destination peer.
When LQM is enabled, Link Quality Reports (LQRs) are sent every keepalive period. LQRs are sent in place of keepalives. All incoming keepalives are responded to properly. If LQM is not configured, keepalives are sent every keepalive period and all incoming LQRs are responded to with an LQR.
LQR is specified in RFC 1333, "PPP Link Quality Monitoring," by William A. Simpson of Computer Systems Consulting Services.
To enable LQM on the interface, perform the following task in interface configuration mode:
The percentage argument specifies the link quality threshold. That percentage must be maintained, or the link is deemed to be of poor quality and taken down.
Disable or Reenable Peer Neighbor Routes
The Cisco IOS software automatically creates neighbor routes by default; that is, it automatically sets up a route to the peer address on a point-to-point interface when the PPP IPCP negotiation is completed.
To disable this default behavior or to reenable it once it has been disabled, complete the following tasks in interface configuration mode:
Disable creation of neighbor routes.
no peer neighbor-route
Reenable creation of neighbor routes.
peer neighbor-route
Configure Compression of PPP Data
You can configure point-to-point software compression on serial interfaces that use PPP encapsulation. Compression reduces the size of a PPP frame via lossless data compression. The compression algorithm used is a predictor algorithm (the RAND algorithm), which uses a compression dictionary to predict the next character in the frame.
PPP encapsulations support both predictor and Stacker compression algorithms.
Compression is performed in software and might significantly affect system performance. Cisco recommends that you disable compression if the router CPU load exceeds 65 percent. To display the CPU load, use the show process cpu EXEC command.
If the majority of your traffic is already compressed files, do not use compression.
To configure compression over PPP, perform the following tasks in interface configuration mode:
Step 1
encapsulation ppp
Step 2
compress [predictor | stac]
or
ppp compress [predictor | stac]1
1 Both command forms exist, and they have the same effect.
Configure PPP Reliable Link
PPP reliable link is Cisco's implementation of RFC 1663, "PPP Reliable Transmission," which defines a method of negotiating and using Numbered Mode LAPB to provide a reliable serial link. Numbered Mode LAPB provides retransmission of errored packets across the serial link.
Although LAPB protocol overhead consumes some bandwidth, this can be offset by the use of PPP compression over the reliable link. PPP compression is separately configurable and is not required for use of a reliable link.
PPP reliable link is available only on synchronous serial interfaces, including ISDN BRI and ISDN PRI interfaces. PPP reliable link cannot be used over V.120.
To configure PPP reliable link on a specified interface, complete the following task in interface configuration mode:
Having reliable link enabled does not guarantee that all connections through the specified interface will in fact use reliable link. It only guarantees that the router will attempt to negotiate reliable link on this interface.
Restrictions
PPP reliable link does not work with Multilink PPP.
PPP reliable link is not available on asynchronous serial interfaces.
Troubleshooting
You can determine whether LAPB has been established on a connection by using the show interface command. You can troubleshoot PPP reliable link by using the debug lapb command and the debug ppp negotiations, debug ppp errors, and debug ppp packets commands.
Configure Compression of LAPB Data
You can configure point-to-point software compression on serial interfaces that use Link Access Procedure, Balanced (LAPB) or multi-LAPB encapsulation. Compression reduces the size of a LAPB or multi-LAPB frame via lossless data compression. The compression algorithm used is a predictor algorithm (the RAND algorithm), which uses a compression dictionary to predict the next character in the frame.
Compression is performed in software and might significantly affect system performance. Cisco recommends that you disable compression if the router CPU load exceeds 65 percent. To display the CPU load, use the show process cpu EXEC command.
Predictor compression is recommended when the bottleneck is caused by the load on the router or access server; Stacker compression is recommended when the bottleneck is the result of line bandwidth. Compression is not recommended if the majority of your traffic is already compressed files. Compression is also not recommended for line speeds greater than T1; the added processing time slows performance on fast lines.
If the majority of your traffic is already compressed files, do not use compression.
To configure compression over LAPB, perform the following tasks in interface configuration mode:
Step 1
encapsulation lapb
Step 2
compress [predictor | stac]
To configure compression over multi-LAPB, perform the following tasks in interface configuration mode:
Step 1
encapsulation lapb multi
Step 2
compress [predictor | stac]
When you are using compression, adjust the MTU for the serial interface and the LAPB N1 parameter as in the following example, to avoid informational diagnostics regarding excessive MTU or N1 sizes:
interface serial 0encapsulation lapbcompress predictormtu 1509lapb n1 12072For information about configuring X.25 TCP/IP header compression and X.25 payload compression, see the "Configuring X.25 and LAPB" chapter in the Wide-Area Networking Configuration Guide.
Configure Compression of HDLC Data
You can configure point-to-point software compression on serial interfaces that use HDLC encapsulation. Compression reduces the size of a HDLC frame via lossless data compression. The compression algorithm used is a Stacker (LZS) algorithm.
Compression is performed in software and might significantly affect system performance. We recommend that you disable compression if CPU load exceeds 65 percent. To display the CPU load, use the show process cpu EXEC command.
If the majority of your traffic is already compressed files, you should not use compression.
To configure compression over HDLC, perform the following tasks in interface configuration mode:
Step 1
encapsulation hdlc
Step 2
compress stac
Invoke ATM over a Serial Line
If you have an ATM DSU, you can invoke ATM over a serial line. You do so by mapping an ATM virtual path identifier (VPI) and virtual channel identifier (VCI) to a DXI frame address. ATM-DXI encapsulation defines a data exchange interface that allows a DTE (such as a router) and a DCE (such as an ATM DSU) to cooperate to provide a User-Network Interface (UNI) for ATM networks.
To invoke ATM over a serial line, perform the following tasks in interface configuration mode:
Step 1
encapsulation atm-dxi
Step 2
dxi map protocol address vpi vci [broadcast] 1
1 This command is documented in the "ATM Commands" chapter of the Wide-Area Networking Command Reference.
You can also configure the atm-dxi map command on a HSSI interface.
To configure an ATM interface using an AIP card, see the "Configuring ATM" chapter in the Wide-Area Networking Configuration Guide.
Configure the CRC
The cyclic redundancy check (CRC) on a serial interface defaults to a length of 16 bits. To change the length of the CRC to 32 bits on an FSIP or HIP of the Cisco 7000 series only, complete the following task in interface configuration mode:
Use the NRZI Line-Coding Format
All FSIP interface types on the Cisco 7000 support nonreturn-to-zero (NRZ) and nonreturn-to-zero inverted (NRZI) format. This is a line-coding format that is required for serial connections in some environments. NRZ encoding is most common. NRZI encoding is used primarily with RS-232 connections in IBM environments.
The default configuration for all serial interfaces is NRZ format. The default is no nrzi-encoding. To enable NRZI format, complete the following task in interface configuration mode:
Enable the Internal Clock
When a DTE does not return a transmit clock, use the following interface configuration command on the Cisco 7000 series to enable the internally generated clock on a serial interface:
Invert the Transmit Clock Signal
Delays between the SCTE clock and data transmission indicate that the transmit clock signal might not be appropriate for the interface rate and length of cable being used. Different ends of the wire may have variances that differ slightly. Invert the clock signal to compensate for these factors by completing the following task in interface configuration mode on a Cisco 7000 series:
Set Transmit Delay
It is possible to send back-to-back data packets over serial interfaces faster than some hosts can receive them. You can specify a minimum dead time after transmitting a packet to alleviate this condition. This setting is available for serial interfaces on the MCI and SCI interface cards and for the HSSI or MIP. Perform one of the following tasks, as appropriate for your system, in interface configuration mode:
Set the transmit delay on the MCI and SCI synchronous serial interfaces.
transmitter-delay microseconds
Set the transmit delay on the HSSI or MIP.
transmitter-delay hdlc-flags
Configure DTR Signal Pulsing
You can configure pulsing DTR signals on all serial interfaces. When the serial line protocol goes down (for example, because of loss of synchronization) the interface hardware is reset and the DTR signal is held inactive for at least the specified interval. This function is useful for handling encrypting or other similar devices that use the toggling of the DTR signal to resynchronize. To configure DTR signal pulsing, perform the following task in interface configuration mode:
Ignore DCD and Monitor DSR as Line Up/Down Indicator
This task applies to Quad Serial NIM interfaces on the Cisco 4000 series and Hitachi-based serial interfaces on the Cisco 2500 series and Cisco 3000 series.
By default, when the serial interface is operating in DTE mode, it monitors the Data Carrier Detect (DCD) signal as the line up/down indicator. By default, the attached DCE device sends the DCD signal. When the DTE interface detects the DCD signal, it changes the state of the interface to up.
In some configurations, such as an SDLC multidrop environment, the DCE device sends the Data Set Ready (DSR) signal instead of the DCD signal, which prevents the interface from coming up. To tell the interface to monitor the DSR signal instead of the DCD signal as the line up/down indicator, perform the following task in interface configuration mode:
Configure the serial interface to monitor the DSR signal as the line up/down indicator.
ignore-dcd
Configure the Clock Rate on DCE Appliques
You can configure the clock rate for appliques (connector hardware) on the serial interface of the MCI and SCI cards to an acceptable bit rate. To do so, perform the following task in interface configuration mode:
Specify the Serial Network Interface Module Timing
On Cisco 4000 series routers, you can specify the serial Network Interface Module timing signal configuration. When the board is operating as a DCE and the DTE provides terminal timing (SCTE or TT), you can configure the DCE to use SCTE from the DTE. When running the line at high speeds and long distances, this strategy prevents phase shifting of the data with respect to the clock.
To configure the DCE to use SCTE from the DTE, perform the following task in interface configuration mode:
When the board is operating as a DTE, you can invert the TXC clock signal it gets from the DCE that the DTE uses to transmit data. Invert the clock signal if the DCE cannot receive SCTE from the DTE, the data is running at high speeds, and the transmission line is long. Again, this prevents phase shifting of the data with respect to the clock.
To configure the interface so that the router inverts the TXC clock signal, perform the following task in interface configuration mode:
Specify G.703 Interface Options
This section describes the optional tasks for configuring a G.703-E1 interface on a Cisco 4000 router or Cisco 7000 series router.
Enable Framed Mode
G.703-E1 interfaces have two modes of operation: framed and unframed. By default, G.703-E1 interfaces are configured for unframed mode. To enable framed mode, perform the following task in interface configuration mode:
To restore the default, use the no form of this command or set the starting time slot to 0.
Enable CRC4 Generation
By default, the G.703-E1 CRC4 is not generated. To enable generation of the G.703-E1 CRC4, which is useful for checking data integrity while operating in framed mode, perform the following task in interface configuration mode:
Use Time Slot 16 for Data
By default, time slot 16 is used for signaling. It can also be used for data. To control the use of time slot 16 for data, perform the following task in interface configuration mode:
Specify a Clock
A G.703-E1 interface can clock its transmitted data from either its internal clock or from a clock recovered from the line's receive data stream. By default, the applique uses the line's receive data stream. To control which clock is used, perform the following task in interface configuration mode:
Configure a Token Ring Interface
Cisco supports two types of Token Ring interface cards:
•
•
The Token Ring interface supports both routing (Layer 3 switching) and source-route bridging (Layer 2 switching). Routing and bridging function on a per-protocol basis. For example, IP traffic could be routed while SNA traffic is bridged. Routing features enhance source-route bridges.
The Token Ring MIB variables support the specification in RFC 1231, "IEEE 802.5 Token Ring MIB," by K. McCloghrie, R. Fox, and E. Decker, May 1991. The mandatory Interface Table and Statistics Table are implemented, but the optional Timer Table of the Token Ring MIB is not. The Token Ring MIB has been implemented for the TRIP.
Use the show interfaces, show controllers token, and show controllers cbus EXEC commands to display the Token Ring numbers. These commands provide a report for each ring that Cisco IOS software supports.
Note
By default, the Token Ring interface uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface.
Token Ring Task List
Perform the tasks in the following sections to configure a Token Ring interface. The first task is required; the remaining tasks are optional, unless you are configuring a Token Ring on the CSC-1R or CSC-2R, in which case you must also select a Token Ring speed.
•
•
Specify a Token Ring Interface
To specify a Token Ring interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration.
interface tokenring number
Begin interface configuration for the Cisco 7000 series.
interface tokenring slot/port
Select the Token Ring Speed
The Token Ring interface on the CSC-1R and CSC-2R can run at either 4 or 16 Mbps. These Token Ring interfaces do not default to any particular ring speed; you must select the speed the first time you use them.
CautionConfiguring a ring speed that is wrong or incompatible with the connected Token Ring causes the ring to beacon, which effectively takes down the ring and makes it nonoperational.
To configure the ring speed on the CSC-1R or CSC-2R Token Ring interfaces, perform the following task in interface configuration mode:
Enable Early Token Release
Cisco Token Ring interfaces support early token release, a method whereby the interface releases the token back onto the ring immediately after transmitting rather than waiting for the frame to return. This feature can help to increase the total bandwidth of the Token Ring. To configure the interface for early token release, perform the following task in interface configuration mode:
Configure PCbus Token Ring Interface Management
The Token Ring interface on the AccessPro PC card can be managed by a remote LAN manager over the PCbus interface. Currently, the LanOptics Hub Networking Management software running on an IBM-compatible PC is supported.
To enable LanOptics Hub Networking Management of a PCbus Token Ring interface, perform the following task in interface configuration mode:
Configure a Tunnel Interface
Tunneling provides a way to encapsulate arbitrary packets inside of a transport protocol. This feature is implemented as a virtual interface to provide a simple interface for configuration. The tunnel interface is not tied to specific "passenger" or "transport" protocols, but rather, it is an architecture that is designed to provide the services necessary to implement any standard point-to-point encapsulation scheme. Because tunnels are point-to-point links, you must configure a separate tunnel for each link.
Tunneling has three primary components:
•
•
•
•
•
•
•
illustrates IP tunneling terminology and concepts.
Figure 25 IP Tunneling Terminology and Concepts
To understand the process of tunneling, consider connecting two AppleTalk networks with a non-AppleTalk backbone, such as IP. The relatively high bandwidth consumed by the broadcasting of Routing Table Maintenance Protocol (RTMP) data packets can severely hamper the backbone's network performance. This problem can be solved by tunneling AppleTalk through a foreign protocol, such as IP. Tunneling encapsulates an AppleTalk packet inside the foreign protocol packet, which is then sent across the backbone to a destination router. The destination router then de-encapsulates the AppleTalk packet and, if necessary, routes the packet to a normal AppleTalk network. Because the encapsulated AppleTalk packet is sent in a directed manner to a remote IP address, bandwidth usage is greatly reduced. Furthermore, the encapsulated packet benefits from any features normally enjoyed by IP packets, including default routes and load balancing.
Advantages of Tunneling
There are several situations where encapsulating traffic in another protocol is useful:
•
•
•
•
Figure 26 Providing Workarounds for Networks with Limited Hop Counts
Special Considerations
The following are considerations and precautions to observe when you configure tunneling:
•
•
•
•
•
•
, packets from Host 1 will travel across networks w, q, and z to get to Host 2 instead of taking the path w, x, y, z because it "appears" shorter.Figure 27 Tunnel Precautions: Hop Counts
•
•
•
•
•
%TUN-RECURDOWN Interface Tunnel 0temporarily disabled due to recursive routingIP Tunneling Task List
If you want to configure IP tunneling, you must perform the tasks in the following sections.
•
The tasks in the following tunnel configuration sections are optional.
•
•
•
•
For commands that monitor IP tunnels, see the section "Monitor and Maintain the Interface" later in this chapter. For examples of configuring tunnels, see the section "IP Tunneling Examples" at the end of this chapter.
Specify the Tunnel Interface
To specify a tunnel interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
Begin interface configuration.
interface tunnel number
Begin interface configuration for the Cisco 7000 series.
interface tunnel slot/port
Configure the Tunnel Source
You must specify the tunnel interface's source address by performing the following task in interface configuration mode:
Note
Configure the Tunnel Destination
You must specify the tunnel interface's destination by performing the following task in interface configuration mode:
Configure the Tunnel Mode
The encapsulation mode for the tunnel interface defaults to generic route encapsulation (GRE), so this task is considered optional. However, if you want a mode other than GRE, you must configure it by performing the following task in interface configuration mode:
If you are tunneling AppleTalk, you must use either the AppleTalk Update Routing Protocol (AURP), Cayman or GRE tunneling mode. Cayman tunneling is designed by Cayman Systems and enables routers and access servers to interoperate with Cayman GatorBoxes. You can have Cisco devices at either end of the tunnel, or you can have a GatorBox at one end and Cisco router or access server at the other end. Use Distance Vector Multicast Routing Protocol (DVMRP) mode when a router or access server connects to a mrouted router to run DVMRP over a tunnel. It is required to configure Protocol-Independent Multicast (PIM) and an IP address on a DVMRP tunnel.
CautionDo not configure a Cayman tunnel with an AppleTalk network address.
If you use GRE, you must have only Cisco routers or access servers at both ends of the tunnel connection. When you use GRE to tunnel AppleTalk, you must configure an AppleTalk network address and a zone. Perform the following tasks to tunnel AppleTalk using GRE:
Step 1
interface tunnel number
Step 2
appletalk cable-range start-end [network.node]1
Step 3
appletalk zone zone-name2
Step 4
tunnel source {ip-address | type}
Step 5
tunnel destination {ip-address | hostname}
Step 6
tunnel mode gre ip
1 This command is documented in the "AppleTalk Commands" chapter of the Network Protocols Command Reference, Part 1.
2 This command is documented in the "AppleTalk Commands" chapter of the Network Protocols Command Reference, Part 1.
Configure End-to-End Checksumming
Some passenger protocols rely on media checksums to provide data integrity. By default, the tunnel does not guarantee packet integrity. By enabling end-to-end checksums, the Cisco IOS software drops corrupted packets. To enable such checksums on a tunnel interface, perform the following task in interface configuration mode:
Configure a Tunnel Identification Key
You can optionally enable an ID key for a tunnel interface. This key must be set to the same value on the tunnel endpoints. Tunnel ID keys can be used as a form of weak security to prevent misconfiguration or injection of packets from a foreign source.
The tunnel ID key is available with GRE only.
Note
To configure a tunnel ID key, perform the following task in interface configuration mode:
Configure a Tunnel Interface to Drop Out-of-Order Datagrams
You can optionally configure a tunnel interface to drop datagrams that arrive out of order. This is useful when carrying passenger protocols that behave poorly when they receive packets out of order (for example, LLC2-based protocols). This option is available with GRE only.
To use this option, perform the following task in interface configuration mode:
Configure Asynchronous Host Mobility
Increasingly, remote users are accessing networks through dial-up telephone connections. In contrast to local users who can connect directly into the network, remote users must first dial into an access server.
The access server supports a packet tunneling strategy that extends the internetwork—in effect creating a virtual private link for the mobile user. When a user activates asynchronous host mobility, the access server on which the remote user dials into becomes a remote point-of-presence (POP) for the user's home network. Once logged in, users experience a server environment identical to the one that they experience when they connect directly to the "home" access server.
Once the network layer connection is made, data packets are tunneled at the physical and/or data link layer instead of at the protocol layer. In this way, raw data bytes from dial-in users are transported directly to the "home" access server, which processes the protocols.
illustrates the implementation of asynchronous host mobility on an extended internetwork. A mobile user connects to an access server on the internetwork and, by activating asynchronous host mobility, is connected to a "home" access server configured with the appropriate username. The user sees an authentication dialog or prompt from the "home" system and can proceed as if he or she were connected directly to that device.
Figure 28 Asynchronous Host Mobility
The remote user implements asynchronous host mobility by executing the tunnel command in the User EXEC mode. The tunnel command sets up a network layer connection to the specified destination. The access server accepts the connection, attaches it to a virtual terminal (VTY), and runs a command parser capable of running the normal dial-in services. After the connection is established, data is transferred between the modem and network connection with a minimum of interpretations. When communications are complete, the network connection can be closed and terminated from either end.
Refer to the Cisco Access Connection Guide for information about setting up the network layer connection with the tunnel command.
Understand Subinterfaces
Configuring multiple virtual interfaces, or subinterfaces, on a single physical interface allows greater flexibility and connectivity on the network. A subinterface is a mechanism that allows a single physical interface to support multiple logical interfaces or networks. That is, several logical interfaces or networks can be associated with a single hardware interface. Subinterfaces are implemented in various WAN and LAN protocols, including ATM, Frame Relay, SMDS, X.25, and Novell IPX. For more information about using subinterfaces, refer to the appropriate protocol chapter.
Note
Configure IP Address Pooling on Point-to-Point Links
Point-to-point interfaces must be able to provide a remote node with its IP address through the IP Control Protocol (IPCP) address negotiation process. The IP address can be obtained from a variety of sources. The address can be configured through the command line, entered with an EXEC-level command or provided by TACACS+, Dynamic Host Configuration Protocol (DHCP), or from a locally administered pool.
IP address pooling consists of a pool of IP addresses from which an incoming interface can provide an IP address to a remote node through the IP Control Protocol (IPCP) address negotiation process. It also enhances the flexibility of configuration by allowing multiple types of pooling to be active simultaneously.
The IP address pooling feature now allows the configuration of a global default address pooling mechanism, per-interface configuration of the mechanism, and per-interface configuration of a specific address or pool name.
Peer Address Allocation
A peer IP address can be allocated to an interface through several methods:
•
•
•
•
•
•
•
•
•
The pool configured for the interface is used, unless TACACS+ returns a pool name as part of authentication, authorization, and accounting (AAA). If no pool is associated with a given interface, the global pool named default is used.
Precedence Rules
The following precedence rules of peer IP address support determine which address is used. Precedence is listed from most likely to least likely:
1
2
3
4
5
6
Interfaces Affected
This feature is available on all asynchronous serial, synchronous serial, ISDN BRI, and ISDN PRI interfaces running the Point-to-Point Protocol (PPP) or Serial Line Internet Protocol (SLIP).
Choose the IP Address Assignment Method
The IP address pooling feature now allows configuration of a global default address pooling mechanism, per-interface configuration of the mechanism, and per-interface configuration of a specific address or pool name.
You can define the type of IP address pooling mechanism used on router interfaces in the following ways:
•
•
Define the Global Default Mechanism
The Global Default Mechanism applies to all point-to-point interfaces (asynchronous, synchronous, ISDN BRI, ISDN PRI, and dialer interfaces) that support PPP encapsulation and that have not otherwise been configured for IP address pooling. You can define the Global Default Mechanism to be either DHCP or local address pooling.
To configure the Global Default Mechanism for IP address pooling, perform the tasks in one of following sections:
•
•
After you have defined a Global Default Mechanism, you can disable it on a specific interface by configuring the interface for some other pooling mechanism. You can define a local pool other than the default pool for the interface or you can configure the interface with a specific IP address to be used for dial-in peers.
Define DHCP as the Global Default Mechanism
The Dynamic Host Configuration Protocol (DHCP) specifies the following components:
•
•
To enable DHCP as the Global Default Mechanism, complete the following tasks in global configuration mode:
In Step 2, you can provide as few as one or as many as ten DHCP servers for the proxy-client (the Cisco router or access server) to use. DHCP servers provide temporary IP addresses.
Define Local Address Pooling as the Global Default Mechanism
To specify that the Global Default Mechanism to use is local pooling, complete the following tasks in global configuration mode:
If no other pool is defined, the local pool called default is used.
Configure Per-Interface IP Address Assignment
When you have defined a Global Default Mechanism for assigning IP addresses to dial-in peers, you can then configure the few interfaces for which it is important to have a nondefault configuration.
You can define a nondefault address pool for use by a specific interface, you can define DHCP on an interface even if you have defined local pooling as the Global Default Mechanism, or you can specify one IP address to be assigned to all dial-in peers on an interface.
To define a nondefault address pool for use on an interface, perform the following tasks beginning in global configuration mode:
To define DHCP as the IP address mechanism for an interface, complete the following tasks beginning in global configuration mode:
Specify the interface and enter interface configuration mode.
interface type number
Specify DHCP as the IP address mechanism on this interface.
peer default ip address pool dhcp
To define a specific IP address to be assigned to all dial-in peers on an interface, complete the following tasks beginning in global configuration mode:
Specify the interface and enter interface configuration mode.
interface type number
Specify the IP address to assign.
peer default ip address ip-address
Configure Features Available on Any Interface
The following sections describe optional tasks that you can perform on any type of interface:
•
•
•
Add a Description for an Interface
You can add a description about an interface to help you remember what is attached to it. This description is meant solely as a comment to help identify what the interface is being used for. The description will appear in the output of the following commands: show configuration, show running-config, and show interfaces. When you add a description for a T1 controller interface, it will appear in the output of the show controllers t1 and show running-config commands.
To add a description for any interface but a T1 or E1 controller interface, perform the following task in interface configuration mode. To add a description for a T1 or E1 controller in a Cisco 7000 or Cisco 4000 series router, perform the following task in controller configuration mode:
For examples of adding interface descriptions, see the section "Interface Descriptions Examples" at the end of this chapter.
Configure MOP
You can enable MOP on an interface by performing the following task in interface configuration mode:
You can enable an interface to send out periodic MOP system identification messages on an interface by performing the following task in interface configuration mode:
Control Interface Hold-Queue Limits
Each interface has a hold-queue limit. This limit is the number of data packets that the interface can store in its hold queue before rejecting new packets. When the interface empties one or more packets from the hold queue, it can accept new packets again. You can specify the hold-queue limit of an interface in interface configuration mode as follows:
Specify the maximum number of packets allowed in the hold queue.
hold-queue length {in | out}
Set Bandwidth
Higher-level protocols use bandwidth information to make operating decisions. For example, IGRP uses the minimum path bandwidth to determine a routing metric. TCP adjusts initial retransmission parameters based on the apparent bandwidth of the outgoing interface. Perform the following task in interface configuration mode to set a bandwidth value for an interface:
The bandwidth setting is a routing parameter only; it does not affect the physical interface.
Set Interface Delay
Higher-level protocols might use delay information to make operating decisions. For example, IGRP can use delay information to differentiate between a satellite link and a land link. To set a delay value for an interface, perform the following task in interface configuration mode:
Setting the delay value sets an informational parameter only; you cannot adjust the actual delay of an interface with this configuration command.
Adjust Timers
To adjust the frequency of update messages, perform the following task in interface configuration mode:
You also can configure the keepalive interval, the frequency at which the Cisco IOS software sends messages to itself (Ethernet and Token Ring) or to the other end (HDLC-serial, PPP-serial), to ensure that a network interface is alive. The interval in some previous software versions was 10 seconds; it is now adjustable in one-second increments down to one second. An interface is declared down after three update intervals have passed without receiving a keepalive packet.
When adjusting the keepalive timer for a very low bandwidth serial interface, large packets can delay the smaller keepalive packets long enough to cause the line protocol to go down. You might need to experiment to determine the best value.
Limit Transmit Queue Size
You can control the size of the transmit queue available to a specified interface on the MCI and SCI cards. To limit the size, perform the following task in interface configuration mode:
Adjust Maximum Packet Size or MTU Size
Each interface has a default maximum packet size or maximum transmission unit (MTU) size. This number generally defaults to 1500 bytes. On serial interfaces, the MTU size varies, but cannot be set smaller than 64 bytes. To adjust the maximum packet size, perform the following task in interface configuration mode:
CautionChanging an MTU size on a Cisco 7500 router will result in recarving of buffers and resetting of all interfaces. The following message is displayed:
%RSP-3-Restart:cbus complex
Configure Dial Backup Service
To configure dial backup, associate a secondary serial interface as a backup to a primary serial interface. This feature requires that an external modem, CSU/DSU device, or ISDN terminal adapter (TA) attached to a circuit-switched service be connected on the secondary serial interface. The external device must be capable of responding to a DTR signal (DTR active) by auto-dialing a connection to a preconfigured remote site.
The dial backup software keeps the secondary line inactive (DTR inactive) until one of the following conditions is met:
•
•
These conditions are defined using the interface configuration commands described later in this section.
When the software detects a lost Carrier Detect signal from the primary line device or finds that the line protocol is down, it activates DTR on the secondary line. At that time, the modem, CSU/DSU, or ISDN TA must be set to dial the remote site. When that connection is made, the routing protocol defined for the serial line will continue the job of transmitting traffic over the dialup line.
You can also configure the dial backup feature to activate the secondary line based upon traffic load on the primary line.
The software monitors the traffic load and computes a five-minute moving average. If this average exceeds the value you set for the line, the secondary line is activated, and depending upon how the line is configured, some or all of the traffic will flow onto the secondary dialup line.
You can also specify a value that defines when the secondary line should be disabled and the amount of time the secondary line can take going up or down.
To configure dial backup, perform the following tasks in interface configuration mode:
See examples of configuring dial backup service in the sections "Dial Backup Service When the Primary Line Goes Down Examples," "Dial Backup Service When the Primary Line Reaches Threshold Examples," and "Dial Backup Service When the Primary Line Exceeds Threshold Examples" at the end of this chapter. See also the chapter "Configuring DDR" in the Wide-Area Networking Configuration Guide.
Configure Loopback Detection
When an interface has a backup interface configured, it is often desirable that the backup interface be enabled when the primary interface is either down or in loopback. By default, the backup is only enabled if the primary interface is down. By using the down-when-looped command, the backup interface will also be enabled if the primary interface is in loopback. To achieve this condition, perform the following task in interface configuration mode:
Configure an interface to tell the system it is down when loopback is detected.
down-when-looped
If testing an interface with the loopback command, you should not have loopback detection configured, or packets will not be transmitted out the interface that is being tested.
Understand Online Insertion and Removal (OIR)
The Cisco 7000 series online insertion and removal (OIR) feature allows you to remove and replace CxBus interface processors while the system is on line. You can shut down the interface processor before removal and restart it after insertion without causing other software or interfaces to shut down.
Note
You do not need to notify the software that you are going to remove or install an interface processor. When the route processor is notified by the system that an interface processor has been removed or installed, it stops routing and scans the system for a configuration change. All interface processors are initialized, and each interface type is verified against the system configuration; then the system runs diagnostics on the new interface. There is no disruption to normal operation during interface processor insertion or removal.
Note
Only an interface of a type that has been configured previously will be brought on line; others require configuration. If a newly installed interface processor does not match the system configuration, the interface is left in an administratively down state until the system operator configures the system with the new interfaces.
Hardware (MAC-level) addresses for all interfaces on the Cisco 7000 are stored on an electronically erasable programmable read-only memory (EEPROM) component in the Route Processor (RP) instead of on the individual interface boards. An address allocator in the EEPROM contains a sequential block of 40 addresses (5 interface slots times a maximum of 8 possible ports per slot). Each address is assigned to a specific slot and port address in the chassis, regardless of how the interfaces are configured. This allows interfaces to be replaced online without requiring the system to update routing tables and data structures. Regardless of the types of interfaces installed, the hardware addresses do not change unless you replace the system RP. If you do replace the RP, the hardware addresses of all ports change to those specified in the address allocator on the new RP.
Understand Fast, Autonomous, and SSE Switching Support
Switching is the process by which packets are forwarded. The Cisco IOS software supports four kinds of switching: process switching, fast switching, autonomous switching, and silicon switching.
Monitor and Maintain the Interface
You can perform the tasks in the following sections to monitor and maintain the interfaces:
•
•
•
•
•
•
Monitor Interface Status
The software contains commands that you can enter at the EXEC prompt to display information about the interface including the version of the software and the hardware, the controller status, and statistics about the interfaces. The following table lists some of the interface monitoring tasks. (You can display the full list of show commands by entering the show ? command at the EXEC prompt.) These commands are fully described in the Configuration Fundamentals Command Reference.
Perform the following commands in EXEC mode:
Display the status of the asynchronous interface.
show async status
Display compression statistics on a serial interface.
show compress
Display current internal status information for the interface controller cards.
For the Cisco 7000 or Cisco 4000 series.
show controllers {bri | cbus | fddi | lance | mci | serial | token}
show controllers {cxbus | fddi | serial | e1 | t1 | token}
Display the number of packets of each protocol type that have been sent through the interface.
For the Cisco 7000.
show interfaces [type number] [first] [last] [accounting]
show interfaces [type slot/port] [accounting]
Display the number of packets of each protocol type that have been sent through the asynchronous serial line.
show interfaces async [number] [accounting]
Display the current contents of the routing information field (RIF) cache.
show rif
Display the hardware configuration, software version, the names and sources of configuration files, and the boot images.
show version1
1 This command is documented in the "System Image, Microcode Image, and Configuration File Load Commands" chapter of the Configuration Fundamentals Command Reference.
Monitor the Interface Port
This section applies to the Cisco 7000 series only. The port adapter cable connected to each port determines the electrical interface type and mode of the port. The default mode of the ports is DCE, which allows you to perform a loopback test on any port without having to attach a port adapter cable. Although DCE is the default, there is no default clock rate set on the interfaces. When there is no cable attached to a port, the software actually identifies the port as "Universal, Cable Unattached" rather than either as a DTE or DCE interface.
Use the show controller cxbus command to show information about the interface port. The following example shows an interface port (2/0) that has an RS-232 DTE cable attached and a second port (2/1) that does not have a cable attached:
Cisco 7000# show controller cxbusSwitch Processor 7, hardware version 11.1 microcode version 1.4512 Kbytes of main memory, 128 Kbytes cache memory, 299 1520 byte buffersRestarts: 0 line down, 0 hung output, 0 controller errorFSIP 2, hardware version 3, microcode version 1.0Interface 16 - Serial2/0, electrical interface is RS-232 DTE31 buffer RX queue threshold, 101 buffer TX queue limit, buffer size 1520Transmitter delay is 0 microsecondsInterface 17 -Serial2/1, electrical interface is Universal (cable unattached)31 buffer RX queue threshold, 101 buffer TX queue limit, buffer size 1520To change the electrical interface type or mode of a port online, replace the serial adapter cable and use software commands to restart the interface and, if necessary, reconfigure the port for the new interface. At system startup or restart, the FSIP polls the interfaces and determines the electrical interface type of each port (according to the type of port adapter cable attached). However, it does not necessarily repoll an interface when you change the adapter cable online. To ensure that the system recognizes the new interface type, shut down and reenable the interface after changing the cable.
Monitor the T1 or E1 Controller
This section applies to the Cisco 7000 series only. Because the T1 or E1 line itself is viewed as the controller, perform the following task in EXEC mode to display information about activity on the T1 or E1 line.
Display information about the T1 line.
show controller t1
Display information about the E1 line.
show controller e1
Alarms, line conditions, and other errors are displayed. The data is updated every 10 seconds. Every 15 minutes, the cumulative data is stored and retained for 24 hours. This means at any one time, up to 96 15-minute accumulations are counted in the data display.
Monitor the LAN Extender Interface
To monitor the LAN Extender interface, the Ethernet interface that resides on the LAN Extender, the serial interface that resides on the LAN Extender, or the serial interface connected to the LAN Extender, perform one or more of the following tasks at the EXEC prompt:
For more complete network troubleshooting information, refer to the Troubleshooting Internetworking Systems.
Monitor and Maintain a Hub
You can perform the tasks in the following sections to monitor and maintain the hub:
•
Shut Down the Hub Port
To shut down or disable a hub port, perform the following tasks, beginning in global configuration mode:
Specify the hub number and the hub port (or range of hub ports) and place you in hub configuration mode.
hub ethernet number port [end-port]
Shut down the hub port.
shutdown
See the examples of shutting down a hub port at the end of this chapter in "Hub Configuration Examples."
Reset the Hub or Clear the Hub Counters
To reset the hub or clear the hub counters, perform one of the following tasks in EXEC mode:
Reset and reinitialize the hub hardware.
clear hub ethernet number
Clear the hub counters displayed by the show hub command.
clear hub counters [ethernet number [port [end-port]]]
Monitor the Hub
To display hub information, perform the following task in EXEC mode:
Monitor IP Tunnels
Complete any of the following tasks in EXEC mode to monitor the IP tunnels you have configured:
List tunnel interface information.
show interfaces tunnel unit [accounting]
List the routes that go through the tunnel.
show protocol route 1
List the route to the tunnel destination.
show ip route 2
1 This command is documented in a separate chapter for each protocol. For example, the command show clns route is documented in the "ISO CLNS Commands" chapter of the Network Protocols Command Reference, Part 2.
2 This command is documented in the "IP Commands" chapter of the Network Protocols Command Reference, Part 1.
Clear and Reset the Interface
To clear the interface counters shown with the show interfaces command, enter the following command at the EXEC prompt:
The command clears all the current interface counters from the interface unless the optional arguments are specified to clear only a specific interface type from a specific slot and port number.
Note
Complete the following tasks in EXEC mode to clear and reset interfaces. Under normal circumstances, you do not need to clear the hardware logic on interfaces.
Reset the hardware logic on an interface.
clear interface type number
Reset the hardware logic on an asynchronous serial line.
clear line [number]1
Clear the entire Token Ring RIF cache.
clear rif-cache
1 This command is documented in the Cisco Access Connection Guide.
Shut Down and Restart the Interface
You can disable an interface. Doing so disables all functions on the specified interface and marks the interface as unavailable on all monitoring command displays. This information is communicated to other network servers through all dynamic routing protocols. The interface will not be mentioned in any routing updates. On serial interfaces, shutting down an interface causes the DTR signal to be dropped. On Token Ring interfaces, shutting down an interface causes the interface to deinsert from the ring. On FDDIs, shutting down an interface causes the optical bypass switch, if present, to go into bypass mode.
To shut down an interface and then restart it, perform the following tasks in interface configuration mode:
To check whether an interface is disabled, use the EXEC command show interfaces. An interface that has been shut down is shown as administratively down in the show interfaces command display. See examples in the section "Interface Shutdown Examples" at the end of this chapter.
One reason to shut down an interface is if you want to change the electrical interface type or mode of a Cisco 7000 series port online. You replace the serial adapter cable and use software commands to restart the interface, and if necessary, reconfigure the port for the new interface. At system startup or restart, the FSIP polls the interfaces and determines the electrical interface type of each port (according to the type of port adapter cable attached). However, it does not necessarily repoll an interface when you change the adapter cable online. To ensure that the system recognizes the new interface type, shut down using the shutdown command, and reenable the interface after changing the cable. Refer to your hardware documentation for more details.
Display Diagnostic Information (Cisco 7000 family only)
On the Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series routers, you can display diagnostic information about the controller, interface processor, and port adapters associated with a specified slot. To display this diagnostic information, complete the following task in privileged EXEC mode:
Run Interface Loopback Diagnostics
You can use a loopback test on lines to detect and distinguish equipment malfunctions between line and modem or Channel Service Unit/Digital Service Unit (CSU/DSU) problems on the network server. If correct data transmission is not possible when an interface is in loopback mode, the interface is the source of the problem. The DSU might have similar loopback functions you can use to isolate the problem if the interface loopback test passes. If the device does not support local loopback, this function will have no effect.
You can specify hardware loopback tests on the Ethernet and synchronous serial interfaces, and all Token Ring interfaces (except the CSC-R 4-megabit card) that are attached to CSU/DSUs and that support the local loopback signal. The CSU/DSU acts as a Data Communications Equipment (DCE) device; the router or access server acts as a Data Terminal Equipment (DTE) device. The local loopback test generates a CSU loop—a signal that goes through the CSU/DSU to the line, then back through the CSU/DSU to the router or access server. The ping command can also be useful during loopback operation.
The loopback tests are available on the following interfaces:
•
•
•
•
•
•
•
•
•
•
•
The following sections describe each test.
Note
Enable Loopback Testing on the HSSI
The HSSI allows you to do the following:
•
•
•
•
•
•
These tests apply only when the device supports them and are used to check the data communications channels. The tests are usually performed at the line port rather than the DTE port of the remote CSU/DSU.
The internal loopback concepts are illustrated in .
Figure 29 HSSI Loopback Testing
Enable Loopback Test of the HSSI Applique
You can configure an internal loop on the HSSI applique by performing the following task in interface configuration mode:
Once enabled, the loopback applique command loops the packets on the applique, thereby establishing a loopback inside the device. This command is useful for sending pings to yourself to check the functionality of the applique. The HSSI applique (HSA card) uses an internal 44.736-MHz crystal clock during the applique loopback to drive its internal circuits. Refer to your hardware installation and maintenance publication for more information.
This command is functionally equivalent to entering the loopback command with no arguments; however, when the HSCI card is installed, the configuration displayed after the show running config command is entered will show loopback applique set.
Enable Loopback Test to the DTE
You can loop packets to DTE within the CSU/DSU at the DTE interface, when the device supports this function. Doing so is useful for testing the DTE-to-DCE cable. To loop the packets to DTE, perform the following task in interface configuration mode:
Enable Loopback Test through the CSU/DSU
You can loop packets completely through the CSU/DSU to configure a CSU loop, when the device supports this feature. Doing so is useful for testing the DCE device (CSU/DSU) itself. To configure a CSU loop, perform the following task in interface configuration mode:
Enable Loopback Test over Remote DS-3 Link
You can loop packets through the CSU/DSU, over the Digital signal level 3 (DS-3) link, and to the remote CSU/DSU and back. To do so, perform the following task in interface configuration mode:
Loop packets through the CSU/DSU to a remote CSU/DSU over the DS-3 link.
loopback remote
This command applies only when the device supports the remote function. It is used for testing the data communication channels. The loopback usually is performed at the line port, rather than the DTE port, of the remote CSU/DSU.
Enable HSSI Externally Requested Loopback
The HSA applique on the HSSI contains an LED that indicates the LA, LB, and LC signals transiting through the devices. The CSU/DSU uses the LC signal to request a loopback from the router. The CSU/DSU might want to do this so that its own network management diagnostics can independently check the integrity of the connection between the CSU/DSU and the device.
When the CSU/DSU asserts the LC signal and the router enables the external loopback, the connection is blocked by the loopback, and the router no longer has access to the data communication channel.
Figure 30 illustrates the extent of the signal during an external loopback request.
Figure 30 HSSI External Loopback Request
By default, this feature is disabled on the router. To enable this feature to support those CSU/DSUs that support this function, perform the following task in interface configuration mode:
Enable a two-way internal and external loopback request on HSSI from DSU/CSU.
hssi external-loop-request
If your CSU/DSU does not support this feature, it should not be enabled in the router. This prevents spurious line noise from accidentally tripping the external loopback request line, which would interrupt the normal data flow.
Perform HSCI Card Ribbon Cable Loopback Test
A useful diagnostic is available that allows fault isolation of possible defects on the HSCI card. This diagnostic is not part of the normal system diagnostics, but is offered to help technicians test for controller defects at installation or when the system is upgraded. The diagnostic involves recabling the HSCI card and then entering a diagnostic script. The tasks required to perform this diagnostic are described in the hardware installation and maintenance publication for your router.
Enable Loopback on MCI and SCI Serial Cards
The MCI and SCI serial interface cards support the loopback function when a CSU/DSU or equivalent device is attached to the router. To enable loopback mode on them, perform the following task in interface configuration mode:
