|
|
Synchronous serial ports can be used for leased-line or dial-up communications. In addition, high-speed lines (E1 or T1) can be configured to support multiple serial interfaces that can themselves be configured as if they were attached to dial-up lines. Finally, dialers can be configured on synchronous serial lines to support dial-on-demand routing.
This chapter presents configuration tasks required to make a serial interface operational. To configure routing and dial capabilities, additional configuration is required. For information about dial-up uses of the serial interfaces, refer to the "Configuring Channelized E1 and Channelized T1" chapter and to the chapters in the "Dial-on-Demand Routing" part of this manual. For protocol-specific routing configuration tasks, see the relevant routing protocol chapters in other volumes of the Cisco IOS software configuration guides.
For a complete description of the synchronous interface commands in this chapter, refer to the "Synchronous Serial Port Setup Commands" chapter of the Dial Solutions Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Perform the tasks in the following sections to configure a synchronous serial interface. The first task is required; the remaining tasks are optional.
For examples of synchronous serial interface configuration, see the "Synchronous Serial Interface Configuration Examples" section at the end of this chapter.
To specify a synchronous serial interface and enter interface configuration mode, perform one of the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Specify an interface and enter interface configuration mode. | interface serial number
interface serial slot/port interface serial slot/port-adapter/port (Cisco 7200 series) interface serial slot/port:channel-group interface serial number:channel-group |
Encapsulation methods are set according to the type of protocol or application you configure in the Cisco IOS software.
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. Synchronous serial interfaces support the following serial encapsulation methods for dial solutions:
In addition, synchronous serial interfaces support the following encapsulation methods that are discussed in other books in the Cisco IOS software documentation set:
These 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.
You can define the encapsulation method for dial solutions by performing the following task in interface configuration mode:
| Task | Command |
|---|---|
| Configure synchronous serial encapsulation for dial solutions. | encapsulation {hdlc | ppp} |
The default is HDLC encapsulation.
To configure PPP (including PPP compression), see the "Configuring Media-Independent PPP" chapter of this manual.
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:
| Task | Command |
|---|---|
| Step 1 Enable encapsulation of a single protocol on the serial line. | encapsulation hdlc |
| Step 2 Enable compression. | compress stac |
| Task | Command |
|---|---|
| Set the length of the CRC. | crc size |
All FSIP interface types on the Cisco 7000 series with RSP7000 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 EIA/TIA-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:
| Task | Command |
|---|---|
| Enable NRZI encoding format. | nrzi-encoding |
When a DTE does not return a transmit clock, use the following interface configuration command on the Cisco 7000 series with RSP7000 to enable the internally generated clock on a serial interface:
| Task | Command |
|---|---|
| Enable the internally generated clock on a serial interface. | transmit-clock-internal |
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 with RSP7000, Cisco 7200 series, and Cisco 7500 series router:
| Task | Command |
|---|---|
| Invert the clock signal on an interface. | invert-transmit-clock |
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:
| Task | Command |
|---|---|
| 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 |
| Task | Command |
|---|---|
| Configure DTR signal pulsing. | pulse-time seconds |
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:
| Task | Command |
|---|---|
| Configure the serial interface to monitor the DSR signal as the line up/down indicator. | ignore-dcd |
| Task | Command |
|---|---|
| Configure the clock rate on serial interfaces. | clock rate bps |
On Cisco 4000 series routers, you can specify the serial NPM 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:
| Task | Command |
|---|---|
| Configure the DCE to use SCTE from the DTE. | dce-terminal-timing enable |
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:
| Task | Command |
|---|---|
| Specify timing configuration to invert TXC clock signal. | dte-invert-txc |
This section describes the optional tasks for configuring a G.703 serial interface:
Interfaces that meet the G.703 electrical and mechanical specifications operate at E1 data rates (2.048 Mbps).
G.703 interfaces have two modes of operation: framed and unframed. By default, serial interfaces on a G.703 port adapter are configured for unframed mode. To enable framed mode, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Enable framed mode. | timeslot start-slot - stop-slot |
To restore the default, use the no form of this command or set the starting time slot to 0.
By default, the G.703 CRC4 is not generated. To enable generation of the G.703 CRC4, which is useful for checking data integrity while operating in framed mode, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Enable CRC4 generation. | crc4 |
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:
| Task | Command |
|---|---|
| Specify that time slot 16 is used for data. | ts16 |
A G.703 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 clock source is the line's receive data stream. To control which clock is used, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Specify the clock used for transmitted data. | clock source {line | internal} |
This section contains the following examples:
For more information about synchronous serial interfaces configured on channelized E1/T1 and used for dialing, see the "Configuring Channelized E1 and Channelized T1" chapter of this manual.
The following example illustrates how to begin interface configuration on a serial interface. It assigns Point-to-Point (PPP) encapsulation to serial interface 0.
interface serial 0 encapsulation ppp
The same example on a Cisco 7500 requires the following commands:
interface serial 1/0 encapsulation ppp
The following example configures a serial interface for DCE mode on a Cisco 7500 series. Because the DTE does not return the Synchronous Clock Transmit Enable (SCTE) signal, the transmit-clock-internal is needed.
interface serial 0/0 ip address 170.1.8.2 255.255.255.0 clockrate 72000 transmit-clock-internal
The following example configures a serial interface for DCE mode on a Cisco 4000 series router. Because the DTE does not return the Synchronous Clock Transmit Enable (SCTE) signal, the dce-terminal-timing-enable is needed. In this example, the default NRZ encoding and 16-bit CRC are accepted.
interface serial 1 clockrate 72000 dce-terminal-timing-enable nrz-encoding
The following example shows a basic configuration for serial interface 9/1/3 on a E1-G.703/G.704 serial port adapter in a Cisco 7500 series router. In this example, the interface is configured for framed (G.704) operation, and timeslot 16 is used for data.
interface serial 9/1/3 ip address 1.1.1.10 255.255.255.0 no keepalive no fair-queue timeslot 1-31 crc4 ts16
The following example shows a configuration for serial interface 1/0/0 on a PA-2JT2 serial port adapter in a Cisco 7500 series router. In this example, the interface is configured to clock data using an internal clock source rather than the default line-derived clock source and to allow the frame alignment search criteria to use CRC5.
interface serial 1/0/0 ip address 1.1.1.10 255.255.255.0 clock source internal crc bits 5 no shutdown
The following example inverts data on serial interface 3/1/0:
interface serial 3/1/0 invert data
The following example inverts the clock signal on serial interface 3/0:
interface serial 3/0 invert txclock
The following example, specifies NRZI mark encoding for serial interface 4/0/2:
interface serial 4/0/2 nrzi-encoding mark
The following example configures a Cisco 7500 series router to acknowledge an E1 line. For an example of configuring circuits refer to the next section; circuits are configured in the same way, whether the line is E1 or T1.
controller e1 3/0 channel-group 0 timeslots 1 channel-group 8 timeslots 5-15, 20-30 channel-group 12 timeslots 2 channel-group 29 timeslots 31
The following example applies only to a Cisco 7500 series router. It configures the router to acknowledge a T1 line and its circuits. Four different circuits (and their corresponding serial interfaces) are defined for the second CxCT1 attached to the MIP in slot 4.
controller t1 4/1 framing esf linecode b8zs channel-group 0 timeslots 1 channel-group 8 timeslots 5,7,12-15, 20 speed 64 channel-group 12 timeslots 2 channel-group 23 timeslots 24
The following example configures circuit 0 for Point-to-Point (PPP) encapsulation:
interface serial 4/1:0 ip address 131.108.13.1 255.255.255.0 encapsulation ppp
The following example configures circuit 8 for IP routing and disables IP route cache:
interface serial 4/1:8 ip address 131.108.1.1 255.255.255.0 no ip route-cache
The following example configures circuit 12 for Frame Relay encapsulation and subinterface support:
interface serial 4/1:12 encapsulation frame-relay ! interface serial 4/1:12.1 ip address 1.1.1.1 255.0.0.0 ! interface serial 4/1:12.2 ip address 2.2.2.2 255.0.0.0
The following example configures circuit 23 for IP routing and enables autonomous switching:
interface serial 4/1:23 ip address 3.3.3.3 255.0.0.0 ip route-cache cbus
The following example shuts down a T1 circuit number 23 running on a Cisco 7500 series router:
interface serial 4/0:23 shutdown
The following example shuts down the entire T1 line physically connected to a Cisco 7500 series router:
controller t1 4/0 shutdown
|
|