Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-WAN interface commands | 1.01 MB |
reset counters interface async
reset counters interface serial
reset counters interface analogmodem
Basic CE1/PRI interface commands
channel-set (CE1/PRI interface)
data-coding (CE1/PRI interface)
frame-format (CE1/PRI interface)
Basic CT1/PRI interface commands
channel-set (CT1/PRI interface)
data-coding (CT1/PRI interface)
frame-format (CT1/PRI interface)
reset counters interface serial
WAN interface commands
This feature is supported only when the router has SAE, AS, ASE, BS, E1, E1-F, T1, T1-F, POS, CPOS, CE3, CT3, or AM interface modules installed.
Because the MSR3620-X1, MSR3620-X1-XS, MSR3620-X1-WiNet, MSR3640-X1, MSR3640-XS, MSR3640-X1-HI, and MSR3660-XS devices do not support AM, ISDN BRI, CE3, or CT3 interfaces, related commands are not supported on these devices.
Common WAN interface commands
bandwidth
Use bandwidth to configure the expected bandwidth of an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
AM interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
Serial subinterface view
T1-F interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.
Examples
# Set the expected bandwidth to 50 kbps for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] bandwidth 50
default
Use default to restore the default settings for an interface.
Syntax
default
Views
AM interface view
CE1/PRI interface view
CE3 interface view
CT1/PRI interface view
CT3 interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
Serial subinterface view
T1-F interface view
Predefined user roles
network-admin
Usage guidelines
|
|
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impact of this command when you use it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies and system restrictions. You can use the display this command in interface view to check for these commands, and use their undo forms or follow the command reference to restore their respective default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings of Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] default
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The interface description uses the interface name Interface format, for example, Serial2/1/0 Interface.
Views
AM interface view
CE1/PRI interface view
CE3 interface view
CT1/PRI interface view
CT3 interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
Serial subinterface view
T1-F interface view
Predefined user roles
network-admin
Parameters
text: Specifies the description, a case-sensitive string of 1 to 255 characters.
Examples
# Configure the description of Serial 2/1/0 as router-interface.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] description router-interface
mtu
Use mtu to set the MTU for an interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an interface is 1500 bytes.
Views
AM interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
Serial subinterface view
T1-F interface view
Predefined user roles
network-admin
Parameters
size: Sets the maximum transmission unit (MTU) in bytes.The value range for this argument is 128 to 1650 for serial interfaces, serial subinterfaces, AM interfaces, E1-F interfaces, and T1-F interfaces. The value range for this argument is 128 to 1500 for FCM interfaces and ISDN BRI interfaces.
Usage guidelines
The MTU setting affects IP packet assembly and fragmentation on the interface.
After configuring the MTU for a WAN interface, you must use the shutdown command and then the undo shutdown command on the interface for the modification to take effect.
Examples
# Set the MTU to 1430 bytes for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] mtu 1430
shutdown
Use shutdown to shut down an interface.
Use undo shutdown to restore the default.
Syntax
shutdown
undo shutdown
Default
A WAN interface is up.
Views
AM interface view
CE1/PRI interface view
CE3 interface view
CT1/PRI interface view
CT3 interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
Serial subinterface view
T1-F interface view
Predefined user roles
network-admin
Examples
# Shut down Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] shutdown
timer-hold
Use timer-hold to set the keepalive interval.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The keepalive interval is 10 seconds.
Views
AM interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
T1-F interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval at which an interface sends keepalive packets. The value range is 0 to 32767 seconds.
Usage guidelines
On an interface encapsulated with PPP, FR, or HDLC, the data link layer sends keepalive packets at keepalive intervals to detect the availability of the remote end. The data link layer determines that the peer end is down if it does not receive a response after the maximum number of keepalive attempts have been made. The data link layer then reports the link down event to the upper-layer protocols.
To set the maximum number of keepalive attempts, use the timer-hold retry command.
On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive interval to 15 seconds for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] timer-hold 15
timer-hold retry
timer-hold retry
Use timer-hold retry to set the maximum number of keepalive attempts.
Use undo timer-hold retry to restore the default.
Syntax
timer-hold retry retries
undo timer-hold retry
Default
The maximum number of keepalive attempts is 5.
Views
AM interface view
E1-F interface view
FCM interface view
ISDN BRI interface view
Serial interface view
T1-F interface view
Predefined user roles
network-admin
Parameters
retries: Specifies the maximum number of keepalive attempts, in the range of 1 to 255.
Usage guidelines
The interface determines that the remote end is down if it does not receive a response after the maximum number of keepalive attempts have been made.
This command applies to interfaces encapsulated with PPP, FR, or HDLC. To set the keepalive interval, use the timer-hold command.
On a slow link, increase the maximum number of keepalive attempts to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the maximum number of keepalive attempts to 10 for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] timer-hold retry 10
Related commands
timer-hold
Serial interface commands
async-mode
Use async-mode to set the operating mode of an asynchronous serial interface.
Use undo async-mode to restore the default.
Syntax
async-mode { flow | protocol }
undo async-mode
Default
An asynchronous serial interface operates in protocol mode.
Views
Asynchronous serial interface view
Synchronous/asynchronous serial interface view
Predefined user roles
network-admin
Parameters
flow: Configures the interface to operate in flow mode.
protocol: Configures the interface to operate in protocol mode.
Usage guidelines
Before you can execute this command on a synchronous/asynchronous interface, you must use the physical-mode async command to configure the interface to operate in asynchronous mode.
To configure PPP on an asynchronous interface, you must place the interface in protocol mode.
Examples
# Configure Async 2/4/0 to operate in flow mode.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] async-mode flow
# Configure Serial 2/1/0 to operate in flow mode.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] async-mode flow
Related commands
physical-mode
baudrate
Use baudrate to set the baud rate for a synchronous serial interface.
Use undo baudrate to restore the default.
Syntax
baudrate baudrate
undo baudrate
Default
The baud rate is 64000 bps on a synchronous serial interface.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
baudrate: Specifies a baud rate (in bps) for a serial interface. The baud rate range on a synchronous serial interface depends on the applied physical electric specifications.
· For V.24 DTE/DCE, available baud rates (in bps) are:
|
Baud rates |
|
|
|
1200 |
9600 |
56000 |
|
2400 |
19200 |
57600 |
|
4800 |
38400 |
64000 |
· For V.35 DCE/DCE, X.21 DTE/DCE, EIA/TIA-449 DTE/DCE, and EIA-530 DTE/DCE, available baud rates (in bps) are:
|
Baud rates |
|
|
|
1200 |
57600 |
384000 |
|
2400 |
64000 |
512000 |
|
4800 |
72000 |
1024000 |
|
9600 |
115200 |
2048000 |
|
19200 |
128000 |
4096000 |
|
38400 |
192000 |
8192000 bps |
|
56000 |
256000 |
|
Usage guidelines
Take the physical electric specifications of the cable into consideration when you set the baud rate for a serial interface.
The baud rate used by a DCE-DTE pair is determined by the DCE.
Examples
# Set the baud rate to 115200 bps on the DCE-side Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] baudrate 115200
Related commands
virtualbaudrate
clock
Use clock to set the clock selection mode for a synchronous serial interface.
Use undo clock to restore the default.
Syntax
clock { dteclk1 | dteclk2 | dteclk3 | dteclk4 | dteclk5 | dteclkauto }
clock { dceclk1 | dceclk2 [no-auto-invert] | dceclk3 [no-auto-invert] }
undo clock
Default
The DTE-side clock is dteclk1 and the DCE-side clock is dceclk1.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
dteclk1: Sets the interface clock selection mode to DTE clock option 1.
dteclk2: Sets the interface clock selection mode to DTE clock option 2.
dteclk3: Sets the interface clock selection mode to DTE clock option 3.
dteclk4: Sets the interface clock selection mode to DTE clock option 4.
dteclk5: Sets the interface clock selection mode to DTE clock option 5.
dteclkauto: Sets the interface clock selection mode to DTE auto-negotiation.
dceclk1: Sets the interface clock selection mode to DCE clock option 1.
dceclk2: Sets the interface clock selection mode to DCE clock option 2.
dceclk3: Sets the interface clock selection mode to DCE clock option 3.
no-auto-invert: Disables auto clock invert.
This keyword is supported only on the HMIM-8SAE interface cards.
Usage guidelines
In DTE mode, the synchronous serial interface supports the clock { dteclk1 | dteclk2 | dteclk3 | dteclk4 | dteclk5 | dteclkauto } command.
In DCE mode, the synchronous serial interface supports the clock { dceclk1 | dceclk2 [no-auto-invert] | dceclk3 [no-auto-invert] } command.
A synchronous serial interface can operate as a DCE or DTE.
· As a DCE, the interface provides the DCEclk clock for the DTE.
· As a DTE, the interface accepts the clock provided by the DCE. Because transmitting and receiving clocks of synchronization devices are independent, the receiving clock of a DTE device can be either the transmitting or receiving clock of the DCE device. The transmitting clock of a DTE device can be either the transmitting or receiving clock of the DCE device. Therefore, five clock options are available for a DTE device.
In Figure 1, TxClk represents transmitting clock, and RxClk represents receiving clock.
Figure 1 Selecting a clock for a synchronous serial interface
Table 1 describes the four clock selection options for a synchronous serial interface operating as a DTE. The clock preceding the equal sign (=) is the DTE clock, and the clock that follows the equal sign is the DCE clock.
Table 1 Clock options available for a synchronous serial interface operating as a DTE
|
Clock selection option |
Description |
|
DTEclk1 |
TxClk = TxClk, RxClk = RxClk. |
|
DTEclk2 |
TxClk = TxClk, RxClk = TxClk. |
|
DTEclk3 |
TxClk = RxClk, RxClk = TxClk. |
|
DTEclk4 |
TxClk = RxClk, RxClk = RxClk. |
|
DTEclk5 |
TxClk = Local, RxClk = Local. |
Table 2 describes the clock selection options for a synchronous serial interface operating as a DCE. The clock preceding the equal sign (=) is the DCE clock, and the clock that follows the equal sign is the clock signal source.
Table 2 Clock options available for a synchronous serial interface operating as a DCE
|
Clock selection option |
Description |
|
DCEclk1 |
TxClk = Local, RxClk = Local. |
|
DCEclk2 |
TxClk = Local, RxClk = Line. |
|
DCEclk3 |
TxClk = Line, RxClk = Line. |
Examples
# Configure Serial 2/1/0 operating as a DTE to use the clock selection option dteclk2.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] clock dteclk2
code
Use code to configure the digital signal coding format on a synchronous serial interface.
Use undo code to restore the default.
Syntax
code { nrz | nrzi }
undo code
Default
The digital signal coding format is NRZ.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
nrz: Sets the digital signal coding format to nonreturn to zero (NRZ).
nrzi: Sets the digital signal coding format to nonreturn to zero inverted (NRZI).
Examples
# Set the digital signal coding format to NRZI on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] code nrzi
crc
Use crc to set the CRC mode for a synchronous serial interface.
Use undo crc to restore the default.
Syntax
crc { 16 | 32 | none }
undo crc
Default
16-bit CRC is used.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
16: Specifies 16-bit CRC.
32: Specifies 32-bit CRC.
none: Disables CRC.
Examples
# Configure Serial 2/1/0 to use 32-bit CRC.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] crc 32
detect dcd
Use detect dcd to enable data carrier detection (DCD) on a serial interface.
Use undo detect dcd to disable DCD on a serial interface.
Syntax
detect dcd
undo detect dcd
Default
DCD is enabled on a serial interface.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
When determining whether a synchronous serial interface is up, the system detects by default the DSR signal, DCD signal, and presence of cable connection. The interface is considered to be up only when the three signals are all valid.
Examples
# Enable DCD on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] detect dcd
Related commands
detect dsr-dtr
detect dsr-dtr
Use detect dsr-dtr to enable level detection on a serial interface.
Use undo detect dsr-dtr to disable level detection on a serial interface.
Syntax
detect dsr-dtr
undo detect dsr-dtr
Default
Level detection is enabled on a serial interface.
Views
Asynchronous serial interface view
Synchronous serial interface view
Synchronous/asynchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
In level detection, the system detects the following items for the data service unit (DSU) or the channel service unit (CSU):
· Data set ready (DSR) signals.
· Data terminal ready (DTR) signals.
If the level detection is disabled on an asynchronous serial interface, the system skips the cable detection, and automatically reports the serial interface up event. The DTR and DSR are also reported up.
If the level detection is enabled on an asynchronous serial interface, the system detects the DSR signal and the external cable. The interface is considered to be up only when the DSR signal is valid.
When determining whether a synchronous serial interface is up, the system detects by default the DSR signal, DCD signal, and presence of a cable connection. The interface is considered to be up only when the three signals are all valid.
If level detection is disabled on a synchronous serial interface, the system considers the interface to be up after detecting the cable connection. The DTR and DSR are also reported as up.
Examples
# Enable DCD on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] detect dsr-dtr
# Enable DCD on Async 2/4/0.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] detect dsr-dtr
Related commands
detect dcd
display interface async
Use display interface async to display information about an asynchronous serial interface.
Syntax
display interface async [ interface-number ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
async [ interface-number ]: Specifies an asynchronous serial interface by its number. If you do not specify the async keyword, this command displays information about all interfaces. If you specify the async keyword without specifying an interface, this command displays information about all asynchronous serial interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays physically down interfaces and their down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about Async 2/4/0.
<Sysname> display interface async 2/4/0
Async2/4/0
Current state: DOWN
Line protocol state: DOWN
Description: Async2/4/0 Interface
Bandwidth: 9kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet protocol processing: Disabled
Link layer protocol: PPP
LCP: initial
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: 6 hours 39 minutes 25 seconds
Last clearing of counters: Never
Current system time:2017-12-14 10:00:37
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-12-14 09:47:16
Physical layer: asynchronous, Baudrate: 9600 bps
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Input:
1 packets, 0 bytes
0 broadcasts, 0 multicasts
1 errors, 0 runts, 0 giants
0 crc, 0 align errors, 0 overruns
0 aborts, 0 no buffers, 1 frame errors
Output:
0 packets, 0 bytes
0 errors, 0 underruns, 0 collisions
0 deferred
DCD: DOWN, DTR: UP, DSR: DOWN, RTS: UP, CTS: DOWN
# Display brief information about Async 2/4/0.
<Sysname> display interface async 2/4/0 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Asy2/4/0 DOWN DOWN --
# Display brief information about all asynchronous serial interfaces in a down state.
<Sysname> display interface async brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Asy2/4/0 ADM Administratively
Table 3 Command output
|
Field |
Description |
|
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
|
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
|
|
Description |
Description of the interface. |
|
|
Bandwidth |
Expected bandwidth of the interface. |
|
|
Maximum transmission unit |
MTU of the interface. |
|
|
Hold timer |
Interval at which the interface sends keepalive packets. |
|
|
retry times |
Maximum number of keepalive attempts. The interface determines that the remote end is down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. |
|
|
Internet address: ip-address/mask-length (Type) |
IP address of the interface and type of the address in parentheses. Possible IP address types include: · Primary—Manually configured primary IP address. · Sub—Manually configured secondary IP address. If the interface has both primary and secondary IP addresses, the primary IP address is displayed. If the interface has only secondary IP addresses, the lowest secondary IP address is displayed. · DHCP-allocated—DHCP allocated IP address. For more information, see DHCP client configuration in Layer 3—IP Services Configuration Guide. · BOOTP-allocated—BOOTP allocated IP address. For more information, see BOOTP client configuration in Layer 3—IP Services Configuration Guide. · PPP-negotiated—IP address assigned by a PPP server during PPP negotiation. For more information, see PPP configuration in Layer 2—WAN Access Configuration Guide. · Unnumbered—IP address borrowed from another interface. · Cellular-allocated—IP address allocated through the modem-manufacturer's proprietary protocol. For more information, see 3G/4G modem management in Layer 2—WAN Access Configuration Guide. · MAD—IP address assigned to an IRF member device for MAD on the interface. For more information, see IRF configuration in Virtual Technologies Configuration Guide. · MTunnel—IP address of the multicast tunnel interface (MTI), which is the same as the IP address of the MVPN source interface. For more information, see multicast VPN configuration in IP Multicast Configuration Guide. |
|
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
|
Link layer protocol |
Link layer protocol of the interface. |
|
|
LAP: initial |
LAP has been successfully initialized. |
|
|
Output queue - Urgent queuing: Size/Length/Discards Output queue - Protocol queuing: Size/Length/Discards Output queue - FIFO queuing: Size/Length/Discards |
Information about the urgent, protocol, and FIFO output queues: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
|
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
|
Last clearing of counters |
The most recent time that the reset counters interface async command was executed. This field displays Never if this command has not been executed since the device startup. |
|
|
Physical layer |
Physical layer information. |
|
|
Baudrate |
Baud rate of the interface. |
|
|
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average input rates (in Bps, bps, and peps) for the last 300 seconds. |
|
|
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average output rates (in Bps, bps, and peps) for the last 300 seconds. |
|
|
Input: 1 packets, 0 bytes 0 broadcasts, 0 multicasts 1 errors, 0 runts, 0 giants 0 crc, 0 align errors, 0 overruns 0 aborts, 0 no buffers, 1 frame errors |
Incoming traffic statistics for the interface: · broadcasts—Number of incoming broadcast packets. · multicasts—Number of incoming multicast packets. · errors—Number of error packets detected at the physical layer. · runts—Number of incoming undersized packets. · giants—Number of incoming oversized packets. · crc—Number of incoming normal-size packets with CRC errors. · align errors—Number of incoming packets with alignment errors. · overruns—Number of packet drops because the input rate of the interface exceeded the queuing capability. · frame errors—Number of packets with framing errors. · aborts—Number of anomalous errors. · no buffers—Number of packet drops because the receive buffer is full. |
|
|
Output: 0 packets, 0 bytes 0 errors, 0 under runs, 0 collisions 0 deferred |
Outgoing traffic statistics for the interface: · errors—Number of error packets detected at the physical layer. · under runs—Number of packets that fail to be forwarded because the interface reads from memory at a slower speed than it forwards packets. · collisions—Number of packets that the interface stopped transmitting because packet collisions were detected during transmission. · deferred—Number of packets that the interface deferred to transmit because of detected collisions or timeout events. |
|
|
DCD: DOWN, DTR: UP, DSR: DOWN, RTS: UP, CTS: DOWN |
Status of Data Carrier Detect (DCD), Data Terminal Ready (DTR), Data Set Ready (DSR), Request to Send (RTS), and Clear to Send (CTS) signals. For more information about DSR, DTR, and DCD, see "detect dcd." |
|
|
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
|
|
Interface |
Abbreviated interface name. |
|
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
|
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. |
|
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
|
Description |
Description of the interface. |
|
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). |
|
Related commands
reset counters interface async
display interface serial
Use display interface serial to display information about serial interfaces.
Syntax
display interface serial [ interface-number ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
serial [ interface-number ]: Specifies a serial interface by its number. If you do not specify the serial keyword, this command displays information about all interfaces. If you specify the serial keyword without specifying an interface, this command displays information about all serial interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays physically down interfaces and their down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about Serial 2/1/0.
<Sysname> display interface serial 2/1/0
Serial2/1/0
Current state: UP
Line protocol state: UP
Description: Serial2/1/0 Interface
Bandwidth: 64kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet Address: 9.9.9.6/24 Primary
Link layer protocol: PPP
LCP: opened
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: 6 hours 39 minutes 25 seconds
Last clearing of counters: Never
Current system time:2017-12-14 10:00:37
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-12-14 09:47:16
Physical layer: synchronous, Baudrate: 64000 bps
Interface: DCE
Cable type: V35
Clock mode: DCECLK1
Last 300 seconds input rate: 2.40 bytes/sec, 19 bits/sec, 0.20 packets/sec
Last 300 seconds output rate: 2.40 bytes/sec, 19 bits/sec, 0.20 packets/sec
Input:
6668 packets, 80414 bytes
0 broadcasts, 0 multicasts
0 errors, 0 runts, 0 giants
0 crc, 0 align errors, 0 overruns
0 aborts, 0 no buffers, 1 frame errors
Output:
6670 packets, 80446 bytes
0 errors, 0 underruns, 0 collisions
0 deferred
DCD: UP, DTR: UP, DSR: UP, RTS: UP, CTS: UP
# Display brief information about Serial 2/1/0.
<Sysname> display interface serial 2/1/0 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Ser2/1/0 UP UP(s) --
# Display brief information about all serial interfaces in down state and the causes.
<Sysname> display interface serial brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Ser2/1/0 ADM Administratively
Table 4 Command output
|
Field |
Description |
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
|
Description |
Description of the interface. |
|
Bandwidth |
Expected bandwidth of the interface. |
|
Maximum transmission unit |
MTU of the interface. |
|
Hold timer |
Interval at which the interface sends keepalive packets. |
|
retry times |
Maximum number of keepalive attempts. The interface determines that the remote end is down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. |
|
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
Link layer protocol |
Link layer protocol of the interface. |
|
LCP: opened |
A PPP connection is established successfully. |
|
Output queue - Urgent queuing: Size/Length/Discards Output queue - Protocol queuing: Size/Length/Discards Output queue - FIFO queuing: Size/Length/Discards |
Information about the urgent, protocol, and FIFO output queues: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
Last clearing of counters |
The most recent time that the reset counters interface serial command was executed. This field displays Never if this command has not been executed since the device startup. |
|
Physical layer |
Physical layer information. |
|
Baudrate |
Baud rate of the interface. |
|
Interface: DCE Cable type: V35 Clock mode: DCECLK1 |
Synchronizes the clock mode on the DCE side of the interface. |
|
Last 300 seconds input rate 2.40 bytes/sec, 19 bits/sec, 0.20 packets/sec |
Average input rates (in Bps, bps, and pps) for the last 300 seconds. |
|
Last 300 seconds output rate 2.40 bytes/sec, 19 bits/sec, 0.20 packets/sec |
Average output rates (in Bps, bps, and pps) for the last 300 seconds. |
|
Input: 6668 packets, 80414 bytes 0 broadcasts, 0 multicasts 0 errors, 0 runts, 0 giants 0 crc, 0 align errors, 0 overruns 0 aborts, 0 no buffers, 1 frame errors |
Incoming traffic statistics for the interface: · broadcasts—Number of incoming broadcast packets. · multicasts—Number of incoming multicast packets. · errors—Number of error packets detected at the physical layer. · runts—Number of incoming undersized packets. · giants—Number of incoming oversized packets. · crc—Number of incoming normal-size packets with CRC errors. · align errors—Number of incoming packets with alignment errors. · overruns—Number of packet drops because the input rate of the interface exceeded the queuing capability. · frame errors—Number of packets with framing errors. · aborts—Number of anomalous errors. · no buffers—Number of packet drops because the receive buffer is full. |
|
Output: 6670 packets, 80446 bytes 0 errors, 0 underruns, 0 collisions 0 deferred |
Outgoing traffic statistics for the interface: · errors—Number of error packets detected at the physical layer. · underruns—Number of packets that fail to be forwarded because the interface reads from memory slower than it forwards packets. · collisions—Number of packets that the interface stopped transmitting because packet collisions were detected during transmission. · deferred—Number of packets that the interface deferred to transmit because of detected collisions or timeout events. |
|
DCD: DOWN, DTR: UP, DSR: DOWN, RTS: UP, CTS: DOWN |
Status of Data Carrier Detect (DCD), Data Terminal Ready (DTR), Data Set Ready (DSR), Request to Send (RTS), and Clear to Send (CTS) signals. For more information about DSR, DTR, and DCD, see "detect dcd." |
|
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
|
Interface |
Abbreviated interface name. |
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. |
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
Description |
Description of the interface. |
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). |
Related commands
reset counters interface serial
eliminate-pulse
Use eliminate-pulse to eliminate the pulses with a width less than 3.472 μs.
Use undo eliminate-pulse to restore the default.
Syntax
eliminate-pulse
undo eliminate-pulse
Default
Pulses with a width less than 1.472 μs are eliminated.
Views
Asynchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
This command applies to 8ASE and 16ASE interface cards.
Before you execute this command on a synchronous/asynchronous interface, you must use the physical-mode async command to configure the interface to operate in asynchronous mode.
Use this command to improve the signal reliability in an environment with intensive line interference.
This command is not available if the baud rate of the asynchronous serial interface is 115200 bps. After you configure this command, do not set the baud rate of the interface to 115200 bps.
To configure the baud rate of an asynchronous serial interface, use the speed command in user line view. For more information about the speed command, see Fundamentals Command Reference.
Examples
# Eliminate the pulses with a width less than 3.472 μs on Async 2/4/0.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] eliminate-pulse
Related commands
physical-mode
idle-code
Use idle-code to set the line idle code of a synchronous serial interface.
Use undo idle-code to restore the default.
Syntax
idle-code { 7e | ff }
undo idle-code
Default
The line idle code of a synchronous serial interface is 7e.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
7e: Sets the line idle code to 7e (hexadecimal).
ff: Sets the line idle code to ff (hexadecimal).
Usage guidelines
In most cases, a synchronous serial interface uses 7e (hexadecimal) to identify the idle state of the line. You might need to set the line idle code to ff (hexadecimal) to interoperate with devices that use ff as the line idle code.
Examples
# Set the line idle code to ff for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] idle-code ff
interface async
Use interface async to enter asynchronous serial interface view.
Syntax
interface async interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an asynchronous serial interface by its number.
Examples
# Enter the view of Async 2/4/0.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0]
interface serial
Use interface serial to create a serial subinterface and enter its view, or enter the view of an existing serial interface or serial subinterface.
Use undo interface serial to remove a serial subinterface.
Syntax
interface serial { interface-number | interface-number.subnumber [ p2mp | p2p ] }
undo interface serial interface-number.subnumber
Default
No serial subinterfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a serial interface by its number.
interface-number.subnumber: Specifies a serial subinterface by its number. The interface-number argument specifies the number of the serial interface. The subnumber argument specifies the subinterface index in the range of 0 to 1023.
p2mp: Sets the subinterface type to point-to-multipoint. By default, a serial subinterface is P2MP type.
p2p: Sets the subinterface type to point-to-point.
Usage guidelines
A subinterface can be created only when the upper data link layer protocol of the serial interface is FR.
Examples
# Create serial subinterface Serial 2/1/0.1.
<Sysname> system-view
[Sysname] interface serial 2/1/0.1
[Sysname-Serial2/1/0.1]
Related commands
link-protocol
invert receive-clock
Use invert receive-clock to invert the receive-clock signal on the DTE-side synchronous serial interface.
Use undo invert receive-clock to restore the default.
Syntax
invert receive-clock
undo invert receive-clock
Default
Receive-clock signal inversion is disabled on DTE-side synchronous serial interfaces.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
You might need to invert the receive-clock signal on a DTE-side serial interface to eliminate the half clock-period delay on the line. This command is necessary only when the DTE-side serial interface is connected to some special DCE devices. In common applications, do not invert the clock.
Examples
# Invert the receive-clock on DTE-side synchronous serial interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] invert receive-clock
Related commands
invert transmit-clock
invert transmit-clock
Use invert transmit-clock to invert the transmit-clock signal on the DTE-side synchronous serial interface.
Use undo invert transmit-clock to restore the default.
Syntax
invert transmit-clock
undo invert transmit-clock
Default
Transmit-clock signal inversion is disabled on DTE-side synchronous serial interfaces.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
You might need to invert the transmit-clock signal on a DTE-side serial interface to eliminate the half clock-period delay on the line. This command is necessary only when the DTE-side serial interface is connected to some special DCE devices. In common applications, do not invert the clock.
Examples
# Invert the transmit-clock on DTE-side synchronous serial interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] invert transmit-clock
Related commands
invert receive-clock
itf
Use itf to set the number of interframe filling tags.
Use undo itf to restore the default.
Syntax
itf number number
undo itf number
Default
The number of interframe filling tags is 4.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
number number: Sets the number of interframe filling tags, in the range of 0 to 14. An interframe filling tag is one byte in length.
Examples
# Set the number of interframe filling tags to 5.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] itf number 5
link-protocol
Use link-protocol to configure the data link layer protocol for an interface.
Syntax
link-protocol { fr | hdlc | mfr | ppp | stlp }
undo link-protocol
Default
A synchronous serial interface uses PPP as the data link layer protocol.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
fr: Specifies the FR data link layer protocol.
hdlc: Specifies the HDLC data link layer protocol.
mfr: Specifies the MFR data link layer protocol.
ppp: Specifies the PPP data link layer protocol.
stlp: Specifies the STLP data link layer protocol.
Examples
# Specify HDLC as the data link layer protocol of Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol hdlc
loopback
Use loopback to enable loopback on a serial interface.
Use undo loopback to disable loopback on a serial interface.
Syntax
loopback
undo loopback
Default
Loopback is disabled on a serial interface.
Views
Asynchronous serial interface view
Synchronous serial interface view
Synchronous/asynchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
Examples
# Enable loopback on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] loopback
# Enable loopback on Async 2/4/0.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] loopback
loopback-test
Use loopback-test to initiate a loopback test on a synchronous serial interface.
Syntax
loopback-test [ -c count | -p { pattern | special { ascending | descending | random } } | -s packetsize | -t timeout ] * interface interface-type interface-number
Default
No loopback test is performed on a synchronous serial interface.
Views
Any view
Predefined user roles
network-admin
Parameters
-c count: Specifies the number of test packets to be sent. The value range is 1 to 4294967295, and the default is 5.
-p: Specifies how the packet payload will be filled.
· pattern: Fills the payload with a fixed pattern. The value is a hexadecimal number in the range of 0 to ffffffff. For example, if this argument is specified as ff, the payload is filled with repeated strings of ff. By default, the test packet payload is filled with alternating hexadecimal numbers 55 and aa.
· special: Fills the payload with a dynamic hexadecimal number pattern.
¡ ascending: Fills the payload with hexadecimal numbers 00 to ff in ascending order.
¡ descending: Fills the payload with hexadecimal numbers ff to 00 in descending order.
¡ random: Fills the payload with random hexadecimal numbers in the range of 00 to ff.
-s packetsize: Specifies the test packet size in bytes, excluding the 8-byte packet header. The value range is 0 to 1688, and the default is 52.
-t timeout: Specifies the amount of time the local end waits for a response from the remote end. The value range is 0 to 5000 milliseconds, and the default is 2000 milliseconds. Increase the time value on a slow link.
interface interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
This command is available only on synchronous serial interfaces that are created for E1, T1, E1-F, and T1-F interfaces.
Use this command to test whether the remote end is enabled with loopback. In the loopback test, the interface sends the specified number of test packets to the remote end. If the remote end is enabled with loopback, the test packets can be looped back to the interface.
The quality of the path between the interface and the remote end can be measured based on the loopback test statistics. For more information about the loopback test statistics, see Table 5.
Examples
# Perform a loopback test on Serial 2/1/0.
<Sysname> loopback-test interface serial 2/1/0
Loopback test on Serial2/1/0: 52 data bytes, Press CTRL_C to break
Received from Serial2/1/0: bytes=52 sequence=1 time=1 ms
Received from Serial2/1/0: bytes=52 sequence=2 time=1 ms
Received from Serial2/1/0: bytes=52 sequence=3 time=1 ms
Received from Serial2/1/0: bytes=52 sequence=4 time=1 ms
Received from Serial2/1/0: bytes=52 sequence=5 time=1 ms
--- Serial2/1/0 loopback test statistics ---
5 packet(s) transmitted
5 packet(s) received
0 packet(s) lost
0 packet(s) error
0.00% packet loss
0.00% packet error
Round-trip min/avg/max = 1/1/1 ms
Test result: Loopback is enabled on the remote end.
|
Field |
Description |
|
Loopback test on Serial2/1/0: 52 data bytes, press CTRL_C to break |
Test whether loopback is enabled on the remote end of Serial 2/1/0. The payload in each test packet is 52 bytes. Press Ctrl+C to abort the test. |
|
Received from Serial2/1/0: bytes=52 sequence=1 time=1 ms |
Statistics for the response packets received on Serial 2/1/0: · bytes—Number of bytes in the payload of the response packet. · sequence—Sequence number of the response packet, which is used to determine whether a packet is lost, disordered, or repeated. · time—Round-trip time. If no response packets were received within the timeout time, Wait time out is displayed. |
|
--- Serial2/1/0 loopback test statistics --- |
Statistics on data received and transmitted in the loopback test. |
|
5 packet(s) transmitted |
Number of test packets sent. |
|
5 packet(s) received |
Number of response packets received. |
|
0 packet(s) lost |
Number of test packets for which no responses were received. |
|
0 packet(s) error |
Number of error packets received. |
|
0.00% packet loss |
Packet loss ratio. |
|
0.00% packet error |
Packet error ratio. |
|
Round-trip min/avg/max = 1/1/1 ms |
Minimum/average/maximum round-trip time in milliseconds. |
|
Test result |
Test result: · Loopback is enabled on the remote end. · Loopback is not enabled on the remote end. · Loopback might be enabled on the remote end. |
Related commands
loopback
fe1 loopback
ft1 loopback
phy-mru
Use phy-mru to set the MRU for an asynchronous serial interface operating in flow mode.
Use undo phy-mru to restore the default.
Syntax
phy-mru mrusize
undo phy-mru
Default
The MRU of an asynchronous serial interface is 1700 bytes.
Views
Asynchronous serial interface view
Synchronous/asynchronous serial interface view
Predefined user roles
network-admin
Parameters
mrusize: Sets the maximum receive unit (MRU). The value range for this argument is 4 to 1700 bytes.
Usage guidelines
This command applies only to interfaces operating in asynchronous flow mode.
Examples
# Set the MRU to 1500 bytes for Async 2/4/0 operating in flow mode.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] async-mode flow
[Sysname-Async2/4/0] phy-mru 1500
# Set the MRU to 1500 bytes for Serial 2/1/0 operating in flow mode.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] physical-mode async
[Sysname-Serial2/1/0] async-mode flow
[Sysname-Serial2/1/0] phy-mru 1500
Related commands
async-mode
physical-mode
physical-mode
Use physical-mode to set the operating mode of a synchronous/asynchronous serial interface.
Use undo physical-mode to restore the default.
Syntax
physical-mode { async | sync }
undo physical-mode
Default
Synchronous/asynchronous serial interfaces operate in synchronous mode.
Views
Synchronous/asynchronous serial interface view
Predefined user roles
network-admin
Parameters
async: Sets a synchronous/asynchronous serial interface to operate in asynchronous mode.
sync: Sets a synchronous/asynchronous serial interface to operate in synchronous mode.
Examples
# Set Serial 2/1/0 to operate in asynchronous mode.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] physical-mode async
reset counters interface async
Use reset counters interface async to clear asynchronous serial interface statistics.
Syntax
reset counters interface async [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
async [ interface-number ]: Specifies an asynchronous serial interface by its number. If you do not specify the async keyword, this command clears statistics for all interfaces. If you specify the async keyword without specifying an interface, this command clears statistics for all asynchronous serial interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for Async 2/4/0.
<Sysname> reset counters interface async 2/4/0
Related commands
display interface async
reset counters interface serial
Use reset counters interface serial to clear serial interface statistics.
Syntax
reset counters interface serial [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
serial [ interface-number ]: Specifies a serial interface by its number. If you do not specify the serial keyword, this command clears statistics for all interfaces. If you specify the serial keyword without specifying an interface, this command clears statistics for all serial interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for Serial 2/1/0.
<Sysname> reset counters interface serial 2/1/0
Related commands
display interface serial
reverse-rts
Use reverse-rts to reverse RTS signal.
Use undo reverse-rts to restore the default.
Syntax
reverse-rts
undo reverse-rts
Default
RTS signal reverse is disabled.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Usage guidelines
When this command is configured, the remote end is not allowed to send data while the local end is sending data.
Use this command only for debugging purposes.
Examples
# Reverse the RTS signal.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] reverse-rts
virtualbaudrate
Use virtualbaudrate to set a virtual baud rate for a DTE-side interface.
Use undo virtualbaudrate to remove the virtual baud rate.
Syntax
virtualbaudrate virtualbaudrate
undo virtualbaudrate
Default
The virtual baud rate for a synchronous serial interface is 64000 bps.
Views
Synchronous serial interface view
Predefined user roles
network-admin
Parameters
virtualbaudrate: Specifies a virtual baud rate (in bps). Available values are:
|
Virtual baud rates |
|
|
|
1200 |
57600 |
384000 |
|
2400 |
64000 |
512000 |
|
4800 |
72000 |
1024000 |
|
9600 |
115200 |
2048000 |
|
19200 |
128000 |
4096000 |
|
38400 |
192000 |
|
|
56000 |
256000 |
|
Usage guidelines
When operating as a DTE, the serial interface automatically sets its baud rate to be the same as the DCE side through negotiation.
If you use this command to set the baud rate of a DTE-side interface, you must make sure the baud rate is the same as the DCE-side interface.
If the clock selection mode of the serial interface is dteclk5, the configured virtual baud rate is the line rate.
Configure the baudrate command on the DCE side and the virtualbaudrate command on the DTE side only when the interface is operating in synchronous mode. Do not configure the two commands at the same end of a link.
On the DCE side, the display interface command displays the baud rate of the interface. On the DTE side, the command displays the virtual baud rate of the interface.
Examples
# Set the virtual baud rate to 19200 bps on the DTE-side interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] virtualbaudrate 19200
Related commands
baudrate
clock
AM interface commands
async-mode
Use async-mode to set the operating mode of an AM interface.
Use undo async-mode to restore the default.
Syntax
async-mode { flow | protocol }
undo async-mode
Default
An AM interface operates in flow mode.
Views
AM interface view
Predefined user roles
network-admin
Parameters
flow: Configures the interface to operate in flow mode (interactive mode).
protocol: Configures the interface to operate in protocol mode.
Examples
# Configure Analogmodem 2/4/0 to operate in protocol mode.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0] async-mode protocol
display interface analogmodem
Use display interface analogmodem to display information about an AM interface.
Syntax
display interface analogmodem [ interface-number ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
analogmodem [ interface-number ]: Specifies an AM interface by its number. If you do not specify the analogmodem keyword, this command displays information about all interfaces. If you specify the analogmodem keyword without specifying an interface, this command displays information about all AM interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays physically down interfaces and their down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about Analogmodem 2/4/0.
<Sysname> display interface analogmodem 2/4/0
Analogmodem2/4/0
Current state: DOWN
Line protocol state: DOWN
Description: Analogmodem2/4/0 Interface
Bandwidth: 57kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet protocol processing: Disabled
Link layer protocol: PPP
LCP: initial
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: 6 hours 39 minutes 25 seconds
Last clearing of counters: Never
Current system time:2017-12-14 10:00:37
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-12-14 09:47:16
Physical layer: asynchronous, Baudrate: 57600 bps
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Input:
0 packets, 0 bytes
0 broadcasts, 0 multicasts
0 errors, 0 runts, 0 giants
0 crc, 0 align errors, 0 overruns
0 aborts, 0 no buffers, 1 frame errors
Output:
0 packets, 0 bytes
0 errors, 0 underruns, 0 collisions
0 deferred
DCD: DOWN, DTR: UP, DSR: UP, RTS: UP, CTS: UP
# Display brief information about Analogmodem 2/4/0.
<Sysname> display interface analogmodem 2/4/0 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
AM2/4/0 DOWN DOWN --
# Display brief information about all AM interfaces in a down state and the causes.
<Sysname> display interface analogmodem brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
AM2/4/0 ADM Administratively
Table 6 Command output
|
Field |
Description |
|
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
|
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
|
|
Description |
Description of the interface. |
|
|
Bandwidth |
Expected bandwidth of the interface. |
|
|
Maximum transmission unit |
MTU of the interface. |
|
|
Hold timer |
Interval at which the interface sends keepalive packets. |
|
|
retry times |
Maximum number of keepalive attempts. The interface determines that the remote end is down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. |
|
|
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
|
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
|
Link layer protocol |
Link layer protocol of the interface. |
|
|
LCP: initial |
LCP has been successfully initialized. |
|
|
Output queue - Urgent queuing: Size/Length/Discards Output queue - Protocol queuing: Size/Length/Discards Output queue - FIFO queuing: Size/Length/Discards |
Information about the urgent, protocol, and FIFO output queues: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
|
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
|
Last clearing of counters |
The most recent time that the reset counters interface analogmodem command was executed. This field displays Never if this command has not been executed since the device startup. |
|
|
Physical layer |
Physical layer information. |
|
|
Baudrate |
Baud rate of the interface. |
|
|
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average input rates (in Bps, bps, and pps) for the last 300 seconds. |
|
|
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average output rates (in Bps, bps, and pps) for the last 300 seconds. |
|
|
Input: 0 packets, 0 bytes 0 broadcasts, 0 multicasts 0 errors, 0 runts, 0 giants 0 crc, 0 align errors, 0 overruns 0 aborts, 0 no buffers, 1 frame errors |
Incoming traffic statistics for the AM interface: · broadcasts—Number of incoming broadcast packets. · multicasts—Number of incoming multicast packets. · errors—Number of error packets detected at the physical layer. · runts—Number of incoming undersized packets. · giants—Number of incoming oversized packets. · crc—Number of incoming normal-size packets with CRC errors. · align errors—Number of incoming packets with alignment errors. · overruns—Number of packet drops because the input rate of the interface exceeded the queuing capability. · frame errors—Number of packets with framing errors. · aborts—Number of anomalous errors. · no buffers—Number of packet drops because the receive buffer is full. |
|
|
Output: 0 packets, 0 bytes 0 errors, 0 underruns, 0 collisions 0 deferred |
Outgoing traffic statistics for the interface: · errors—Number of error packets detected at the physical layer. · underruns—Number of packets that fail to be forwarded because the interface reads from memory at a slower speed than it forwards packets. · collisions—Number of packets that the interface stopped transmitting because packet collisions were detected during transmission. · deferred—Number of packets that the interface deferred to transmit because of detected collisions or timeout events. |
|
|
DCD: DOWN, DTR: UP, DSR: DOWN, RTS: UP, CTS: DOWN |
Status of Data Carrier Detect (DCD), Data Terminal Ready (DTR), Data Set Ready (DSR), Request to Send (RTS), and Clear to Send (CTS) signals. |
|
|
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
|
|
Interface |
Abbreviated interface name. |
|
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
|
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. |
|
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
|
Description |
Description of the interface. |
|
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). |
|
Related commands
reset counters interface analogmodem
eliminate-pulse
Use eliminate-pulse to eliminate the pulses with a width less than 3.472 μs.
Use undo eliminate-pulse to restore the default.
Syntax
eliminate-pulse
undo eliminate-pulse
Default
Pulses with a width less than 1.472 μs are eliminated.
Views
AM interface view
Predefined user roles
network-admin
Usage guidelines
This command applies to 8ASE and 16ASE interface cards.
Use this command to improve the signal reliability in an environment with intensive line interference.
This command is not available if the baud rate of the interface is 115200 bps. After you configure this command, do not set the baud rate of the interface to 115200 bps.
To configure the baud rate of an AM interface, use the speed command in user line view. For more information about the speed command, see Fundamentals Command Reference.
Examples
# Eliminate the pulses with a width less than 3.472 μs on interface Analogmodem 2/4/0.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0] eliminate-pulse
interface analogmodem
Use interface analogmodem to enter AM interface view.
Syntax
interface analogmodem { interface-number | interface-number:15 }
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an AM interface by its number.
interface-number:15: Specifies the AM interface created on a CE1/PRI interface. The interface-number argument specifies the number of the CE1/PRI interface.
Examples
# Enter the view of Analogmodem 2/4/0.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0]
# Enter the view of Analogmodem 2/4/0:15.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0:15
[Sysname-Analogmodem2/4/0:15]
loopback
Use loopback to enable loopback on an AM interface.
Use undo loopback to disable loopback on an AM interface.
Syntax
loopback
undo loopback
Default
Loopback is disabled on an AM interface.
Views
AM interface view
Predefined user roles
network-admin
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
Examples
# Enable loopback on Analogmodem 2/4/0.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0] loopback
phy-mru
Use phy-mru to set the MRU for an AM interface operating in flow mode.
Use undo phy-mru to restore the default.
Syntax
phy-mru mrusize
undo phy-mru
Default
The MRU of an AM interface operating in flow mode is 1700 bytes.
Views
AM interface view
Predefined user roles
network-admin
Parameters
mrusize: Sets the MRU. The value range for this argument is 4 to 1700 bytes.
Usage guidelines
This command applies only to interfaces operating in asynchronous flow mode.
Examples
# Set the MRU to 1500 bytes for Analogmodem 2/4/0 operating in flow mode.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0] async-mode flow
[Sysname-Analogmodem2/4/0] phy-mru 1500
Related commands
async-mode
reset counters interface analogmodem
Use reset counters interface analogmodem to clear AM interface statistics.
Syntax
reset counters interface analogmodem [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
analogmodem [ interface-number ]: Specifies an AM interface by its number. If you do not specify the analogmodem keyword, this command clears statistics for all interfaces. If you specify the analogmodem keyword without specifying an interface, this command clears statistics for all AM interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for Analogmodem 2/4/0.
<Sysname> reset counters interface analogmodem 2/4/0
Related commands
display interface analogmodem
FCM interface commands
display interface fcm
Use display interface fcm to display information about an FCM interface.
Syntax
display interface fcm [ interface-number ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
fcm [ interface-number ]: Specifies an FCM interface by its number. If you do not specify the fcm keyword, this command displays information about all interfaces. If you specify the fcm keyword without specifying an interface, this command displays information about all FCM interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays physically down interfaces and their down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about FCM 2/4/0:15.1.
<Sysname> display interface fcm 2/4/0:15.1
Fcm2/4/0:15.1
Current state: DOWN
Line protocol state: DOWN
Description: Fcm2/4/0:15.1 Interface
Bandwidth: 9kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet protocol processing: Disabled
Link layer protocol: PPP
LCP: initial
Last link flapping: 6 hours 39 minutes 25 seconds
Last clearing of counters: Never
Current system time:2017-12-14 10:00:37
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-12-14 09:47:16
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Input:
0 packets, 0 bytes
0 broadcasts, 0 multicasts
0 errors, 0 runts, 0 giants
0 CRC, 0 align errors, 0 overruns
0 frame errors, 0 aborts, 0 no buffers
Output:
0 packets, 0 bytes
0 errors, 0 underruns, 0 collisions
0 deferred
# Display brief information about FCM 2/4/0:15.
<Sysname> display interface fcm 2/4/0:15 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Fcm2/4/0:15 DOWN DOWN --
# Display brief information about all FCM interfaces in a down state and the causes.
<Sysname> display interface fcm brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Fcm2/4/0:15 ADM Administratively
Table 7 Command output
|
Field |
Description |
|
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
|
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
|
|
Description |
Description of the interface. |
|
|
Bandwidth |
Expected bandwidth of the interface. |
|
|
Maximum transmission unit |
MTU of the interface. |
|
|
Hold timer |
Interval at which the interface sends keepalive packets. |
|
|
retry times |
Maximum number of keepalive attempts. The interface determines that the remote end is down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. |
|
|
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
|
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
|
Link layer protocol |
Link layer protocol of the interface. |
|
|
LCP: initial |
LCP has been successfully initialized. |
|
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
|
Last clearing of counters |
The most recent time that the reset counters interface fcm command was executed. This field displays Never if this command has not been executed since the device startup. |
|
|
Last 300 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average input rates (in Bps, bps, and pps) for the last 300 seconds. |
|
|
Last 300 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average output rates (in Bps, bps, and pps) for the last 300 seconds. |
|
|
Input: 0 packets, 0 bytes 0 broadcasts, 0 multicasts 0 errors, 0 runts, 0 giants 0 CRC, 0 align errors, 0 overruns 0 frame errors, 0 aborts, 0 no buffers |
Incoming traffic statistics for the interface: · broadcasts—Number of incoming broadcast packets. · multicasts—Number of incoming multicast packets. · errors—Number of error packets detected at the physical layer. · runts—Number of incoming undersized packets. · giants—Number of incoming oversized packets. · crc—Number of incoming normal-size packets with CRC errors. · align errors—Number of incoming packets with alignment errors. · overruns—Number of packet drops because the input rate of the interface exceeded the queuing capability. · frame errors—Number of packets with framing errors. · aborts—Number of anomalous errors. · no buffers—Number of packet drops because the receive buffer is full. |
|
|
Output: 0 packets, 0 bytes 0 errors, 0 underruns, 0 collisions 0 deferred |
Outgoing traffic statistics for the interface: · errors—Number of error packets detected at the physical layer. · underruns—Number of packets that fail to be forwarded because the interface reads from memory at a slower speed than it forwards packets. · collisions—Number of packets that the interface stopped transmitting because packet collisions were detected during transmission. · deferred—Number of packets that the interface deferred to transmit because of detected collisions or timeout events. |
|
|
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
|
|
Interface |
Abbreviated interface name. |
|
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
|
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. |
|
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
|
Description |
Description of the interface. |
|
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). |
|
Related commands
reset counters interface fcm
interface fcm
Use interface fcm to enter FCM interface view.
Syntax
interface fcm { interface-number | interface-number:15 }
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an FCM interface by its number.
interface-number:15: Specifies the FCM interface created on a CE1/PRI interface. The interface-number argument specifies the number of the CE1/PRI interface.
Examples
# Enter the view of FCM 2/4/0.
<Sysname> system-view
[Sysname] interface fcm 2/4/0
[Sysname-Fcm2/4/0]
# Enter the view of FCM 2/4/0:15.
<Sysname> system-view
[Sysname] interface fcm 2/4/0:15
[Sysname-Fcm2/4/0:15]
pcm
Use pcm to set the PCM for an FCM interface.
Use undo pcm to restore the default.
Syntax
pcm { a-law | u-law }
undo pcm
Default
The PCM of an FCM interface is a-law.
Views
FCM interface view
Predefined user roles
network-admin
Parameters
a-law: Specifies the companding A-law, used in most parts of the world other than North America and Japan, such as China, Europe, Africa, and South America.
µ-law: Specifies the companding µ-Law, used in the United States of America.
Usage guidelines
Companding laws are used to quantize signals unevenly to reduce noise and improve signal-to-noise ratio.
According to CCITT, when devices in two countries use different companding schemes to communicate, the side using µ-Law is responsible for converting signals to A-law.
Examples
# Set the PCM to u-law for FCM 2/4/0:15.
<Sysname> system-view
[Sysname] interface fcm0/1/4:15
[Sysname-Fcm2/4/0:15] pcm u-law
reset counters interface fcm
Use reset counters interface fcm to clear FCM interface statistics.
Syntax
reset counters interface fcm [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
fcm [ interface-number ]: Specifies an FCM interface by its number. If you do not specify the fcm keyword, this command clears statistics for all interfaces. If you specify the fcm keyword without specifying an interface, this command clears statistics for all FCM interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for FCM 2/4/0:15.
<Sysname> reset counters interface fcm 2/4/0:15
Related commands
display interface fcm
ISDN BRI interface commands
activate
Use activate to activate a BRI interface.
Syntax
activate
Default
A BRI interface is not activated.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
If no calling exists on a BRI interface, the BRI interface is not activated. This command enables you to activate such an interface.
Examples
# Activate BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] activate
display interface bri
Use display interface bri to display information about BRI interfaces.
Syntax
display interface bri [ interface-number ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
bri [ interface-number ]: Specifies a BRI interface by its number. If you do not specify the bri keyword, this command displays information about all interfaces. If you specify the bri keyword without specifying an interface, this command displays information about all BRI interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays physically down interfaces and their down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about BRI 2/4/0.
<Sysname> display interface bri 2/4/0
Bri2/4/0
Current state: DOWN
Line protocol state: UP (spoofing)
Description: Bri2/4/0 Interface
Bandwidth: 128kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Baudrate: 128000 bps
Timeslot(s) Used: 1, 2
Internet protocol processing: Disabled
Link layer protocol: PPP
LCP: initial
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: 6 hours 39 minutes 25 seconds
Last clearing of counters: Never
Current system time:2017-12-14 10:00:37
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-12-14 09:47:16
Last 5 seconds input rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Last 5 seconds output rate: 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec
Input:
0 packets, 0 bytes
0 errors, 0 runts, 0 giants,
0 crc, 0 align errors, 0 overruns,
0 aborts, 0 no buffers
0 frame errors
Output:
0 packets, 0 bytes
0 errors, 0 underruns, 0 collisions
# Display brief information about BRI 2/4/0.
<Sysname> display interface bri 2/4/0 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Bri2/4/0 ADM UP(s) --
# Display brief information about all BRI interfaces in a down state and the causes.
<Sysname> display interface bri brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Bri2/4/0 ADM Administratively
Table 8 Command output
|
Field |
Description |
|
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
|
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
|
|
Description |
Description of the interface. |
|
|
Bandwidth |
Expected bandwidth of the interface. |
|
|
Maximum transmission unit |
MTU of the interface. |
|
|
Hold timer |
Interval at which the interface sends keepalive packets. |
|
|
retry times |
Maximum number of keepalive attempts. The interface determines that the remote end is down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. |
|
|
Baudrate |
Baud rate of the interface. |
|
|
Timeslot(s) Used |
Time slot used by the interface. |
|
|
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
|
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
|
Link layer protocol |
Link layer protocol of the interface. |
|
|
LCP: initial |
LCP has been successfully initialized. |
|
|
Output queue - Urgent queuing: Size/Length/Discards Output queue - Protocol queuing: Size/Length/Discards Output queue - FIFO queuing: Size/Length/Discards |
Information about the urgent, protocol, and FIFO output queues: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
|
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
|
Last clearing of counters |
The most recent time that the reset counters interface bri command was executed. This field displays Never if this command has not been executed since the device startup. |
|
|
Last 5 seconds input rate 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average input rates (in Bps, bps, and pps) for the last 5 seconds. |
|
|
Last 5 seconds output rate 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec |
Average output rates (in Bps, bps, and pps) for the last 5 seconds. |
|
|
Input: 0 packets, 0 bytes 0 errors, 0 runts, 0 giants 0 crc, 0 align errors, 0 overruns 0 aborts, 0 no buffers 0 frame errors |
Incoming traffic statistics for the interface: · errors—Number of incoming error packets detected at the physical layer. · runts—Number of incoming undersized packets. · giants—Number of incoming oversized packets. · crc—Number of incoming normal-size packets with CRC errors. · align errors—Number of incoming packets with alignment errors. · overruns—Number of packet drops because the input rate of the interface exceeded the queuing capability. · aborts—Number of anomalous errors. · no buffers—Number of packet drops because the receive buffer is full. · frame errors—Number of packets with framing errors. |
|
|
Output:0 packets, 0 bytes 0 errors, 0 underruns, 0 collisions 0 deferred |
Outgoing traffic statistics for the interface: · errors—Number of error packets detected at the physical layer. · underruns—Number of packets that fail to be forwarded because the interface reads from memory at a slower speed than it forwards packets. · collisions—Number of packets that the interface stopped transmitting because packet collisions were detected during transmission. · deferred—Number of packets that the interface deferred to transmit because of detected collisions or timeout events. |
|
|
Brief information of interfaces in route mode: |
Brief information about Layer 3 interfaces. |
|
|
Interface |
Abbreviated interface name. |
|
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
|
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. |
|
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
|
Description |
Description of the interface. |
|
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). |
|
Related commands
reset counters interface bri
interface bri
Use interface bri to enter BRI interface view.
Syntax
interface bri interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a BRI interface by its number.
Examples
# Enter the view of BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0]
loopback
Use loopback to enable external loopback on an ISDN BRI interface.
Use undo loopback to disable external loopback on an ISDN BRI interface.
Syntax
loopback { b1 | b2 | both | remote }
undo loopback
Default
External loopback is disabled on an ISDN BRI interface.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
b1: Enables external loopback on B1 channel.
b2: Enables external loopback on B2 channel.
both: Enables external loopback on B1 and B2 channels.
remote: Enables external loopback on B1, B2 and D channels.
Examples
# Enable external loopback on B1 and B2 channels of BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] loopback both
reset counters interface bri
Use reset counters interface bri to clear BRI interface statistics.
Syntax
reset counters interface bri [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
bri [ interface-number ]: Specifies a BRI interface by its number. If you do not specify the bri keyword, this command clears statistics for all interfaces. If you specify the bri keyword without specifying an interface, this command clears statistics for all BRI interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for BRI 2/4/0.
<Sysname> reset counters interface bri 2/4/0
Related commands
display interface bri
Basic CE1/PRI interface commands
alarm-detect
Use alarm-detect to enable RAI detection on an interface.
Use undo alarm-detect to disable RAI detection on an interface.
Syntax
alarm-detect rai
undo alarm-detect rai
Default
RAI detection is enabled on an interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
rai: Remote Alarm Indication (RAI).
Usage guidelines
This command is applicable when the interface operates in CE1 mode.
Examples
# Enable RAI detection on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] alarm-detect rai
cable (CE1/PRI interface)
Use cable to set the cable type for a CE1/PRI interface.
Use undo cable to restore the default.
Syntax
cable { long | short }
undo cable
Default
The long keyword applies.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
long: Specifies the attenuation of the receiver as –43 dB.
short: Specifies the attenuation of the receiver as –10 dB.
Examples
# Set the cable length matching E1 2/3/0 to short.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] cable short
cable-type
Use cable-type to set the cable impedance for a CE1/PRI interface.
Use undo cable-type to restore the default.
Syntax
cable-type { 75 | 120 }
undo cable-type
Default
The cable impedance is 75 ohm.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
75: Specifies 75 ohm.
120: Specifies 120 ohm.
Usage guidelines
This command is supported only on E1T1 interfaces operating in E1 mode.
Examples.
# Set the cable impedance to 120 ohm for E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] cable-type 120
channel-set (CE1/PRI interface)
Use channel-set to bundle timeslots on a CE1/PRI interface into a channel set.
Use undo channel-set to cancel the bundling.
Syntax
channel-set set-number timeslot-list list
undo channel-set [ set-number ]
Default
No channel sets exist on an interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
set-number: Specifies the number of the channel set for the timeslot bundle. The value range is 0 to 30.
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 31.
Usage guidelines
A CE1/PRI interface in CE1 or PRI mode is physically divided into 32 timeslots numbered 0 through 31. All the timeslots except timeslot 0 can be bundled into multiple channel sets. For each channel set, the system automatically creates a serial interface that has the same logical features as a standard synchronous serial interface.
The serial interface name uses the serial interface-number:set-number format. The interface-number argument specifies the CE1/PRI interface number. The set-number argument specifies the channel set number.
A PRI set cannot coexist with a channel set on a CE1/PRI interface.
Examples
# Bundle timeslots 1, 2, 5, 10 through 15, and 18 into channel set 0 on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] channel-set 0 timeslot-list 1,2,5,10-15,18
Related commands
pri-set
clock (CE1/PRI interface)
Use clock to set the clock mode of a CE1/PRI interface.
Use undo clock to restore the default.
Syntax
clock { master | slave }
undo clock
Default
The clock mode of a CE1/PRI interface is slave.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of an interface is master, it uses the internal clock source. When the clock mode of an interface is slave, it uses the line clock source.
Set the clock mode for an interface according to its operating mode:
· When the interface is operating in DCE mode, set its clock mode to master.
· When the interface is operating in DTE mode, set its clock mode to slave.
Examples
# Set the clock mode to master for CE1/PRI interface E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] clock master
clock-change auto
Use clock-change auto to enable automatic clock mode switchover on an interface.
Use undo clock-change auto to disable automatic clock mode switchover.
Syntax
clock-change auto
undo clock-change auto
Default
Automatic clock mode switchover is disabled on an interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Usage guidelines
When automatic clock mode switchover is enabled, the interface automatically switches to the master clock mode when both of the following conditions exist:
· The interface uses the slave clock mode.
· The interface receives an alarm indication signal (AIS), loss of signal (LOS), or loss of frame (LOF) alarm.
After the alarm is cleared, the interface automatically switches back to the slave mode.
When automatic clock mode switchover is disabled, the interface uses the user-configured clock mode.
Examples
# Enable automatic clock mode switchover for E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] clock-change auto
Related commands
clock
code (CE1/PRI interface)
Use code to set the line code format for a CE1/PRI interface.
Use undo code to restore the default.
Syntax
code { ami | hdb3 }
undo code
Default
The line code format is HDB3 for the CE1/PRI interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
ami: Specifies the alternate mark inversion (AMI) line code format.
hdb3: Specifies the high-density bipolar 3 (HDB3) line code format.
Usage guidelines
An interface must use the same line code format as its remote end.
For the interface to operate correctly, configure the data-coding inverted command on the interface if the AMI format is used.
Examples
# Set the line code format to AMI for E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] code ami
Related commands
data-coding
controller e1
Use controller e1 to enter CE1/PRI interface view.
Syntax
controller e1 interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CE1/PRI interface by its number.
Examples
# Enter E1 2/3/0 interface view.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0]
data-coding (CE1/PRI interface)
Use data-coding to enable user data inversion on a CE1/PRI interface.
Use undo data-coding to restore the default.
Syntax
data-coding { inverted | normal }
undo data-coding
Default
Data inversion is disabled on a CE1/PRI interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
inverted: Enables user data inversion.
normal: Disables user data inversion.
Usage guidelines
To prevent 7e in valid data from being mistaken for padding characters, HDLC inserts a zero after every five consecutive ones in the data stream. In data inversion, each bit one is inverted to bit zero, and each bit zero is inverted to bit one. After the inversion, at least a bit one is present in every eight consecutive bits.
When AMI encoding is used on an E1 interface, data inversion eliminates the presence of multiple consecutive zeros.
The data inversion setting must be the same on the CE1/PRI interfaces at two ends of an E1 line.
Examples
# Enable user data inversion on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] data-coding inverted
detect-ais
Use detect-ais to enable alarm indication signal (AIS) detection on an interface.
Use undo detect-ais to disable AIS detection.
Syntax
detect-ais
undo detect-ais
Default
AIS detection is enabled on an interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Usage guidelines
This command takes effect when a CE1/PRI interface operates in E1 mode.
Examples
# Enable AIS detection on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] detect-ais
display controller e1
Use display controller e1 to display information about CE1/PRI interfaces.
Syntax
display controller [ e1 [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
e1 [ interface-number ]: Specifies a CE1/PRI interface by its number. If you do not specify the e1 keyword, the command displays information about all CE1/PRI interfaces, CPOS interfaces, CE3 interfaces, CT1/PRI interfaces, and CT3 interfaces. If you specify the e1 keyword without specifying an interface, the command displays information about all CE1/PRI interfaces.
Examples
# Display information about E1 2/3/0.
<Sysname> display controller e1 2/3/0
E1 2/3/0
Current state: UP
Description: E1 2/3/0 Interface
Last clearing of counters: Never
Current system time:2017-11-11 15:51:05
Last time when physical state changed to up:2017-11-11 15:51:00
Last time when physical state changed to down:2017-11-11 15:50:51
Basic Configuration:
Work mode: E1 framed, Cable type: 75 Ohm unbalanced
Frame-format: no-crc4, Line code: hdb3, Source clock: slave
Idle code: 7e, Itf type: 7e, Itf number: 4, Loop back: not set
Alarm State:
Receiver alarm state is None.
Historical Statistics:
Data in current interval (3398 seconds elapsed):
Loss Frame Alignment: 0 seconds, Framing Error: 1 seconds
CRC Error: 0 seconds, Alarm Indication: 0 seconds
Loss-of-signals: 1 seconds, Code Violations: 1 seconds
Slip: 0 seconds, E-Bit error: 0 seconds
Table 9 Command output
|
Field |
Description |
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
Description |
Description of the interface. |
|
Work mode |
Operating mode of the interface: E1 or CE1. |
|
Cable type |
Cable type of the interface. |
|
Frame-format |
Framing format of the E1 interface. |
|
Line code |
Line code: AMI or HDB3. |
|
Source clock |
Clock source used by the interface: master or slave. |
|
Idle code |
Idle code: 7e or ff. |
|
Itf type |
Interframe filling tag: 7e or ff. |
|
Itf number |
Number of interframe filling tags between two successive frames. |
|
Loopback |
Loopback state. |
|
Historical Statistics |
Statistics for the interface. |
|
Last clearing of counters |
The most recent time that the reset counters controller e1 command was executed. This field displays Never if this command has not been executed since the device startup. |
|
Data in current interval (3398 seconds elapsed): Loss Frame Alignment: 0 seconds, Framing Error: 1 seconds CRC Error: 0 seconds, Alarm Indication: 0 seconds Loss-of-signals: 1 seconds, Code Violations: 1 seconds Slip: 0 seconds, E-Bit error: 0 seconds |
Error statistics for the current interval. |
Related commands
reset counters controller e1
frame-format (CE1/PRI interface)
Use frame-format to set the framing format for a CE1 interface.
Use undo frame-format to restore the default.
Syntax
frame-format { crc4 | no-crc4 }
undo frame-format
Default
The framing format on a CE1 interface is no-CRC4.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
crc4: Sets the framing format to CRC4.
no-crc4: Sets the framing format to no-CRC4.
Usage guidelines
A CE1/PRI interface in CE1 mode supports both CRC4 and no-CRC4 framing formats. Only CRC4 supports four-bit CRC on physical frames.
Examples
# Set the framing format to CRC4 on E1 2/3/0.
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] frame-format crc4
idle-code (CE1/PRI interface)
Use idle-code to set the line idle code on a CE1/PRI interface.
Use undo idle-code to restore the default.
Syntax
Idle-code { 7e | ff }
undo idle-code
Default
The line idle code on a CE1/PRI interface is 7e.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
7e: Sets the line idle code to 7e (hexadecimal).
ff: Sets the line idle code to ff (hexadecimal).
Usage guidelines
The line idle code is sent in timeslots that are not bundled into logical channels.
Examples
# Set the line idle code to 7e on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] idle-code 7e
itf (CE1/PRI interface)
Use itf to set the type and number of interframe filling tags on a CE1/PRI interface.
Use undo itf to restore the default.
Syntax
itf { number number | type { 7e | ff } }
undo itf { number | type }
Default
The interframe filling tag is 7e. The number of interframe filling tags is 4.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
number number: Sets the number of interframe filling tags, in the range of 0 to 14. An interframe filling tag is one byte in length.
type: Specifies the interframe filling tag type.
7e: Sets the interframe filling tag type to 7e (hexadecimal).
ff: Sets the interframe filling tag type to ff (hexadecimal).
Usage guidelines
Interframe filling tags are sent when no service data is sent on the timeslots that are bundled into logical channels on the CE1/PRI interface.
If the ff interframe filling tag is used on a CE1/PRI interface in E1 mode, consecutive ones sent when the line is idle might trigger AIS alarms. To prevent false AIS alarms, use the undo detect-ais command to disable AIS detection.
Examples
# Set the type of interframe filling tag to ff on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] itf type ff
# Set the number of interframe filling tags to 5 on E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] itf number 5
loopback (CE1/PRI interface)
Use loopback to enable loopback and set the loopback mode on an interface.
Use undo loopback to disable loopback on an interface.
Syntax
loopback { local | payload | remote }
undo loopback
Default
Loopback is disabled on a CE1/PRI interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
local: Sets the interface to operate in local loopback mode.
payload: Sets the interface to operate in external payload loopback mode.
remote: Sets the interface to operate in external loopback mode.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
You can bundle timeslots on the CE1/PRI interface to form a serial interface and encapsulate it with PPP. After you enable loopback on this serial interface, it is normal that the state of the link layer protocol is reported as down.
Examples
# Set E1 2/3/0 to operate in internal loopback mode.
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] loopback local
pri-set (CE1/PRI interface)
Use pri-set to bundle timeslots on a CE1/PRI interface into a PRI set.
Use undo pri-set to remove the bundle.
Syntax
pri-set [ timeslot-list list ]
undo pri-set
Default
No PRI set exists on a CE1/PRI interface.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 31.
Usage guidelines
On a CE1/PRI interface in PRI mode, timeslots 0 to 31 are used as follows:
· Timeslot 0 is used for frame synchronization control (FSC).
· Timeslot 16 is used as the D channel for signaling transmission.
· Other timeslots are used as B channels for data transmission.
You can create only one PRI set on a CE1/PRI interface. This PRI set can include any timeslots except timeslot 0, and it must include timeslot 16. Timeslot 16 cannot form a bundle that includes only itself. The attempt to bundle only timeslot 16 will fail.
If no timeslots are specified in this command, all timeslots except timeslot 0 are bundled into an interface in the form of 30B + D.
A PRI set cannot coexist with a channel set on a CE1/PRI interface.
Examples
# Bundle timeslots 1, 2, and 8 through 12 into a PRI set on CE1/PRI interface E1 2/3/0.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] pri-set timeslot-list 1,2,8-12
Related commands
channel-set
reset counters controller e1
Use reset counters controller e1 to clear CE1/PRI interface statistics.
Syntax
reset counters controller e1 [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CE1/PRI interface by its number. If you do not specify this argument, the command clears statistics for all CE1/PRI interfaces.
Usage guidelines
The reset counters interface command clears statistics for all interfaces.
To display CE1/PRI interface statistics, use the display controller e1 command.
Examples
# Clear statistics for CE1/PRI interface E1 2/3/0.
<Sysname> reset counters controller e1 2/3/0
Related commands
display controller e1
using (CE1/PRI interface)
Use using to set the operating mode of a CE1/PRI interface.
Use undo using to restore the default.
Syntax
using { ce1 | e1 }
undo using
Default
A CE1/PRI interface operates in channelized mode.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
ce1: Sets the interface to operate in channelized mode.
e1: Sets the interface to operate in E1 mode.
Usage guidelines
A CE1/PRI interface can operate in channelized or unchannelized mode.
· Channelized modes include CE1 mode and PRI mode. In CE1 or PRI mode, the CE1/PRI interface is physically divided into 32 timeslots numbered 0 through 31. Timeslot 0 is used for FSC.
· Unchannelized modes include E1 mode.
¡ For a CE1/PRI interface in E1 mode, the system automatically creates a 2.048 Mbps serial interface. The interface name uses the serial interface-number:0 format. The interface-number argument specifies the CE1/PRI interface number. This interface has the same logical features as a standard synchronous serial interface.
Examples
# Set E1 2/3/0 to operate in E1 mode.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] using e1
work-mode
Use work-mode to set a CE1/PRI interface to synchronous or asynchronous mode.
Use undo work-mode to restore the default.
Syntax
work-mode { async | sync }
undo work-mode
Default
A CE1/PRI interface operates in synchronous mode.
Views
CE1/PRI interface view
Predefined user roles
network-admin
Parameters
async: Specifies the asynchronous mode.
sync: Specifies the synchronous mode.
Usage guidelines
This command is available for CE1/PRI interfaces on the DHMIM-1E1POS1DM card. Their physical type is PHY_E1POSDM.
Typically, the CE1/PRI interfaces on the DHMIM-1E1POS1DM card are used to connect to POS terminals. For correct transaction transmission, you must set these interfaces to synchronous or asynchronous mode depending on the operating mode of their connected POS terminals.
· Set a CE1/PRI interface to synchronous mode if the connected POS terminal is operating in synchronous dial-up mode. The device will use the serial or FCM interface created for the CE1/PRI interface to transmit transactions.
· Set a CE1/PRI interface to asynchronous mode if the connected POS terminal is operating in asynchronous dial-up mode. The device will use the serial or AM interface created for the CE1/PRI interface to transmit transactions.
Examples
# Set the CE1/PRI interface E1 2/3/0 to asynchronous mode.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] work-mode async
Related commands
pri-set
Basic CT1/PRI interface commands
alarm-detect
Use alarm-detect to enable RAI detection on an interface.
Use undo alarm-detect to disable RAI detection on an interface.
Syntax
alarm-detect rai
undo alarm-detect rai
Default
RAI detection is enabled on an interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
rai: Remote Alarm Indication (RAI).
Usage guidelines
This command is applicable when the framing format used on the interface is ESF.
Examples
# Enable RAI detection on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] alarm detect rai
alarm-threshold
Use alarm-threshold to set LOS, AIS, or LFA alarm thresholds on a CT1/PRI interface.
Use undo alarm-threshold to restore the default.
Syntax
alarm-threshold { ais { level-1 | level-2 } | lfa { level-1 | level-2 | level-3 | level-4 } | los { pulse-detection | pulse-recovery } value }
undo alarm-threshold { ais | lfa | los { pulse-detection | pulse-recovery } }
Default
For AIS and LFA, the alarm threshold is level-1.
For LOS, the pulse-detection threshold is 176, and pulse-recovery threshold is 22. A LOS alarm is generated if the number of pulses detected within 176 pulse intervals is less than 22.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
ais: Specifies an alarm indication signal (AIS) alarm.
· level-1: Specifies the condition when the number of zeros in the bit stream of an SF or ESF frame is less than or equal to 2.
· level-2: Specifies one of the following conditions:
¡ In an SF frame, the number of zeros is less than or equal to 3 in the bit stream.
¡ In an ESP frame, the number of zeros is less than or equal to 5 in the bit stream.
lfa: Specifies a loss of frame alignment (LFA) alarm.
· level-1: Specifies the condition when two of four frame alignment bits are lost.
· level-2: Specifies the condition when two of five frame alignment bits are lost.
· level-3: Specifies the condition when two of six frame alignment bits are lost.
· level-4: Specifies the condition when errors are detected in four consecutive ESF frames. This keyword is available only for ESF frames.
los: Specifies a loss of signal (LOS) alarm.
· pulse-detection: Specifies the pulse detection duration threshold of the LOS alarm, in units of pulse intervals.
· pulse-recovery: Specifies the pulse threshold of the LOS alarm.
value: Specifies the value of the pulse-detection threshold or pulse-recovery threshold.
· For the pulse-detection threshold, this argument is in the range of 16 to 4096.
· For the pulse-recovery threshold, this argument is in the range of 1 to 256.
If the number of the pulses detected during the total length of the specified pulse detection intervals is smaller than the pulse-recovery threshold, a LOS alarm occurs.
Examples
# Set the number of detection intervals to 300 for the pulse detection duration threshold.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] alarm-threshold los pulse-detection 300
bert (CT1/PRI interface)
Use bert to start a bit error rate test (BERT) on an interface.
Use undo bert to stop the BERT test running on an interface.
Syntax
bert pattern { 2^20 | 2^15 } time minutes [ unframed ]
undo bert
Default
No BERT test is performed on an interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
pattern: Sets a BERT pattern.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· 2^20: Specifies the pattern length (in bits) as two to the twentieth power.
time minutes: Sets the duration (in minutes) of a BERT test. The minutes argument is in the range of 1 to 1440.
unframed: Sets the test pattern to cover the overhead bits of the frame.
Usage guidelines
The CT1/PRI interface supports only the 2^15 and 2^20 BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of the BERT test, use the display controller t1 command.
Examples
# Run a 10-minute 2^20 BERT test on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] bert pattern 2^20 time 10
Related commands
display controller t1
cable (CT1/PRI interface)
Use cable to set the cable attenuation and length on a CT1/PRI interface.
Use undo cable to restore the default.
Syntax
cable { long { 0db | -7.5db | -15db | -22.5db } | short { 133ft | 266ft | 399ft | 533ft | 655ft } }
undo cable
Default
The cable length is long 0db on a CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
long: Matches 199.6-meter (655-feet) and longer cable length. The options for this parameter include 0db, -7.5db, -15db, and -22.5db. The attenuation parameter is selected depending on the signal quality received at the receiving end. No external CSU is needed.
short: Matches a cable length shorter than 199.6 meters (655 feet). The options for this parameter include 133ft, 266ft, 399ft, 533ft, and 655ft. The length argument is selected depending on the actual transmission distance.
Usage guidelines
You can use this command to adapt signal waveform to different transmission conditions such as the quality of the signal received by the receiver. If the signal quality is good, you can use the default setting. The CT1/PRI interface does not need an external CSU device.
Examples
# Set the cable length to 40.5 meters (133 feet) on CT1/PRI interface T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] cable short 133ft
channel-set (CT1/PRI interface)
Use channel-set to bundle timeslots on a CT1/PRI interface into a channel set.
Use undo channel-set to remove a channel set.
Syntax
channel-set set-number timeslot-list list [ speed { 56k | 64k } ]
undo channel-set [ set-number ]
Default
No channel sets exist on a CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
set-number: Number of the channel set for the timeslot bundle. The value range is 0 to 23.
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 24.
speed { 56k | 64k }: Speed of the timeslot bundle (the channel set) in kbps. If 56k is selected, the timeslots are bundled into n × 56 kbps bundles. If 64k (the default) is selected, the timeslots are bundled into n × 64 kbps bundles.
Usage guidelines
A CT1/PRI interface is divided into 24 timeslots numbered 1 through 24. In actual applications, all the timeslots can be bundled into multiple channel sets. For each channel set, the system automatically creates a serial interface that has the same logical features as a standard synchronous serial interface.
The serial interface name uses the serial interface-number:set-number format. The interface-number argument specifies the CT1/PRI interface number. The set-number argument specifies the channel set number.
A PRI set cannot coexist with a channel set on a CT1/PRI interface.
Examples
# Bundle timeslots 1, 2, 5, 10 through 15, and 18 into channel set 0 on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] channel-set 0 timeslot-list 1,2,5,10-15,18
Related commands
pri-set
clock (CT1/PRI interface)
Use clock to set the clock mode of a CT1/PRI interface.
Use undo clock to restore the default.
Syntax
clock { master | slave }
undo clock
Default
The clock mode of a CT1/PRI interface is slave.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of a CT1/PRI interface is master, it uses the internal clock source. When the clock mode of a CT1/PRI interface is slave, it uses the line clock source.
Set the clock mode for a CT1/PRI interface as follows:
· When the CT1/PRI interface is operating in DCE mode, set its clock mode to master.
· When the interface is operating in DTE mode, set its clock mode to slave.
· When two CT1/PRI interfaces on two routers are directly connected, configure the two ends with different clock modes.
· When the CT1/PRI interface on a router is connected to a switch, the CT1/PRI interface on the router operates as a DTE. The switch operates as a DCE. Set the clock mode of the CT1/PRI interface on the router to slave to accept the clock provided by the switch.
Examples
# Set the clock mode to master on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] clock master
code (CT1/PRI interface)
Use code to set the line code format for a CT1/PRI interface.
Use undo code to restore the default.
Syntax
code { ami | b8zs }
undo code
Default
The line code format is B8ZS for the CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
ami: Specifies the AMI line code format.
b8zs: Specifies the bipolar 8-zero substitution (B8ZS) line code format.
Usage guidelines
A CT1/PRI interface must use the same line code format as its remote end.
For the interface to operate correctly, configure the data-coding inverted command on the interface if the AMI format is used.
Examples
# Set the line code format to AMI for T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] code ami
Related commands
data-coding
controller t1
Use controller t1 to enter CT1/PRI interface view.
Syntax
controller t1 interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CT1/PRI interface by its number.
Examples
# Enter the view of T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0]
data-coding (CT1/PRI interface)
Use data-coding to enable user data inversion on a CT1/PRI interface.
Use undo data-coding to restore the default.
Syntax
data-coding { inverted | normal }
undo data-coding
Default
Data inversion is disabled on a CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
inverted: Enables user data inversion.
normal: Disables user data inversion.
Usage guidelines
To prevent 7e in valid data from being mistaken for padding characters, HDLC inserts a zero after every five consecutive ones in the data stream. In data inversion, each bit one is inverted to bit zero, and each bit zero is inverted to bit one. After the inversion, at least a bit one is present in every eight consecutive bits.
When AMI encoding is used on a T1 interface, data inversion eliminates the presence of multiple consecutive zeros.
The data inversion setting must be the same on the CT1/PRI interfaces at two ends of a T1 line.
Examples
# Enable user data inversion on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] data-coding inverted
display controller t1
Use display controller t1 to display information about CT1/PRI interfaces.
Syntax
display controller [ t1 [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
t1 [ interface-number ]: Specifies a CT1/PRI interface by its number. If you do not specify the t1 keyword, the command displays information about all CT1/PRI interfaces, CPOS interfaces, CE3 interfaces, CE1/PRI interfaces, and CT3 interfaces. If you specify the t1 keyword without specifying an interface, the command displays information about all CT1/PRI interfaces.
Examples
# Display information about T1 2/4/0.
<Sysname> display controller t1 2/4/0
T1 2/4/0
Current state: UP
Description: T1 2/2/2/1 Interface
Last clearing of counters: Never
Current system time:2017-11-11 16:11:54
Last time when physical state changed to up:2017-11-11 16:04:52
Last time when physical state changed to down:2017-11-11 16:04:49
Basic Configuration:
Work mode: T1 framed, Cable type: 100 Ohm balanced
Frame-format: esf, fdl: none, Line code: b8zs
Source clock: slave, Data-coding: normal
Idle code: ff, Itf type: ff, Itf number: 2
Loop back: not set
Alarm State:
Receiver alarm state is Loss-of-Signal
Transmitter is sending remote alarm
Pulse density violation detected
SendLoopCode History:
Inband-llb-up: 0 times, Inband-llb-down: 0 times
Fdl-ansi-llb-up: 0 times, Fdl-ansi-llb-down: 0 times
Fdl-ansi-plb-up: 0 times, Fdl-ansi-plb-down: 0 times
Fdl-att-plb-up: 0 times, Fdl-att-plb-down: 0 times
BERT state:(stopped, not completed)
Test pattern: 2^15, Status: Not Sync, Sync Detected: 0
Time: 0 minutes, Time past: 0 minutes
Bit Errors (since test started): 0 bits
Bits Received (since test started): 0 Kbits
Bit Errors (since latest sync): 0 bits
Bits Received (since latest sync): 0 Kbits
Historical Statistics:
Last link flapping: 6 hours 39 minutes 25 seconds
Data in current interval (285 seconds elapsed):
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 286 seconds
Slip: 7 seconds, Fr Loss: 286 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 286 seconds
Data in Interval 1:
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm Secs: 901 seconds
Slip: 22 seconds, Fr Loss: 901 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 901 seconds
Data in Interval 2:
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 900 seconds
Slip: 23 seconds, Fr Loss: 900 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 900 seconds
Total Data (last 2 15 minute intervals):
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 2087 seconds
Slip: 52 seconds, Fr Loss: 2087 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 2087 seconds
Table 10 Command output
|
Field |
Description |
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
Description |
Description of the interface. |
|
Basic Configuration |
Basic configurations of the interface. |
|
Work mode |
Operating mode of the interface. |
|
Cable type |
Cable type of the interface. |
|
Frame-format |
Frame format configured on the interface: ESF or SF. |
|
fdl |
FDL format: ANSI, ATT, or none. |
|
Line code |
Line code: AMI or B8ZS. |
|
Source clock |
Clock source used by the interface: master or slave. |
|
Data-coding |
Normal or inverted. |
|
Idle code |
Idle code: 7e or ff. |
|
Itf type |
Type of interframe filling tag: 7e or ff. |
|
Itf number |
Number of interframe filling tags. |
|
Loop back |
Loopback setting on the interface: local, payload, remote, or not set. |
|
Receiver alarm state is Loss-of-Signal |
Type of received alarm: none, LOS, LOF, RAI, or AIS. |
|
Transmitter is sending remote alarm. |
Type of transmitted alarm: RAI, or none. |
|
Pulse density violation detected |
The detected pulse density is incompliant with the specification. |
|
SendLoopCode History: Inband-llb-up: 0 times, Inband-llb-down: 0 times Fdl-ansi-llb-up: 0 times, Fdl-ansi-llb-down: 0 times Fdl-ansi-plb-up: 0 times, Fdl-ansi-plb-down: 0 times Fdl-att-plb-up: 0 times, Fdl-att-plb-down: 0 times |
History of loopback code sending to the peer end, including the number of transmissions for each type of code, and the type of the last sent code. |
|
BERT state |
BERT test state: · completed—The test has been completed. · stopped—The test has been manually terminated. · running—The test is running. |
|
Test pattern |
Test pattern in use (2^20 or 2^15). |
|
Status |
Whether synchronization is being performed. |
|
¡ Sync Detected |
Number of detected synchronizations. |
|
Time |
Duration of the BERT test. |
|
Time past |
Time that has elapsed. |
|
Bit Errors (since test started) |
Number of bit errors received since the start of the BERT test. |
|
Bits Received (since test started) |
Number of bits received since the start of the BERT test. |
|
Bit Errors (since latest sync) |
Number of bit errors received since last synchronization. |
|
Bits Received (since latest sync) |
Number of bits received since last synchronization. |
|
Historical Statistics |
Historical statistics for the interface. |
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
Last clearing of counters |
The most recent time that the reset counters controller t1 command was executed. This field displays Never if this command has not been executed since the device startup. |
|
Data in current interval (285 seconds elapsed): Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 286 seconds Slip: 7 seconds, Fr Loss: 286 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 286 seconds |
Statistics in the current interval. The statistical items, such as AIS alarm, LOS signal, and LFA, are provided according to the T1 specifications for the physical layer. For more information, see ANSI T1.403 and AT&T TR 54016. |
|
Data in Interval 1: Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm Secs: 901 seconds Slip: 22 seconds, Fr Loss: 901 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 901 seconds |
Statistics spanning the first interval. The statistical items are the same as those provided by the statistics spanning the current interval. |
|
Data in Interval 2: Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 900 seconds Slip: 23 seconds, Fr Loss: 900 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 900 seconds |
Statistics spanning the second interval. The statistical items are the same as those provided by the statistics spanning the current interval. |
|
Total Data (last 2 15 minute intervals): Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 2087 seconds Slip: 52 seconds, Fr Loss: 2087 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 2087 seconds |
Statistics spanning the last two intervals. The statistical items are the same as those provided by the statistics spanning the current interval. |
Related commands
reset counters controller t1
fdl
Use fdl to set the behavior of the CT1/PRI interface on the FDL in ESF framing.
Use undo fdl to restore the default.
Syntax
fdl { ansi | att | both | none }
undo fdl
Default
FDL in ESF framing is disabled (none).
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
ansi: Specifies ANSI T1.403 for facilities data link (FDL).
att: Specifies AT&T TR 54016 for FDL.
both: Specifies both ANSI T1.403 and AT&T TR 54016 for FDL.
none: Disables FDL.
Usage guidelines
Facility Data Link (FDL) is an embedded 4 kbps overhead channel within the ESF format for transmitting alarm information, performance statistics, or loopback code. FDL uses ANSI T1.403 and ATT TR 54016. You can change the setting depending on the setting at the far end.
Examples
# Implement AT&T FDL on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] fdl att
frame-format (CT1/PRI interface)
Use frame-format to set the framing format on a CT1/PRI interface.
Use undo frame-format to restore the default.
Syntax
frame-format { esf | sf }
undo frame-format
Default
The framing format on a CT1/PRI interface is esf.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
esf: Sets the framing format to extended super frame (ESF).
sf: Sets the framing format to super frame (SF).
Usage guidelines
CT1/PRI interfaces support the following framing formats:
· ESF format—Allows you to test the system without affecting the ongoing service.
· SF format—Provides more significant bits for user data transmission because multiple frames can share the same FSC and signaling information.
Examples
# Set the framing format to SF for T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] frame-format sf
idle-code (CT1/PRI interface)
Use idle-code to set the line idle code on a CT1/PRI interface.
Use undo idle-code to restore the default.
Syntax
Idle-code { 7e | ff }
undo idle-code
Default
The line idle code on a CT1/PRI interface is 7e.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
7e: Sets the line idle code to 7e (hexadecimal).
ff: Sets the line idle code to ff (hexadecimal).
Usage guidelines
The line idle code is sent in the timeslots that are not bundled into logical channels on the interface.
Examples
# Set the line idle code to 7e on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] idlecode 7e
itf (CT1/PRI interface)
Use itf to set the type and the number of interframe filling tags on a CT1/PRI interface.
Use undo itf to restore the default.
Syntax
itf { number number | type { 7e | ff } }
undo itf { number | type }
Default
On a CT1/PRI interface, the interframe filling tag is 7e, and the number of interframe filling tags is 4.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
number number: Sets the number of interframe filling tags, in the range of 0 to 14. An interframe filling tag is one byte in length.
type: Specifies the interframe filling tag type.
7e: Sets the interframe filling tag type to 7e (hexadecimal).
ff: Sets the interframe filling tag type to ff (hexadecimal).
Usage guidelines
Interframe filling tags are sent when no service data is sent on the timeslots that are bundled into logical channels on a CT1/PRI interface.
Examples
# Set the type of interframe filling tag to ff on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] itf type ff
# Set the number of interframe filling tags to 5 on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] itf number 5
loopback (CT1/PRI interface)
Use loopback to enable a type of loopback on a CT1/PRI interface.
Use undo loopback to disable loopback on a CT1/PRI interface.
Syntax
loopback { local | payload | remote }
undo loopback
Default
Loopback is disabled on a CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
local: Enables local loopback.
payload: Enables external payload loopback.
remote: Enables remote loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
You can bundle timeslots on a CT1/PRI interface to form a serial interface and encapsulate it with PPP. After you enable loopback on this serial interface, it is normal that the state of the link layer protocol is reported as down.
Examples
# Enable local loopback on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] loopback local
pri-set (CT1/PRI interface)
Use pri-set to bundle timeslots into a PRI set on a CT1/PRI interface.
Use undo pri-set to remove the timeslot bundle.
Syntax
pri-set [ timeslot-list list ]
undo pri-set
Default
No PRI set exists on a CT1/PRI interface.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 24.
Usage guidelines
You can create only one PRI set on a CT1/PRI interface.
In the PRI set, timeslot 24 is used as the D channel for signaling transmission, and other timeslots are used as B channels for data transmission. When you bundle timeslots into a PRI set, the D channel (timeslot 24) is automatically bundled.
If no timeslot is specified, all timeslots are bundled into an interface similar to an ISDN PRI interface in the form of 23B + D.
For the PRI set, the system automatically creates a serial interface that has the same logical features as an ISDN PRI interface. The serial interface name uses the serial number:23 format. The number argument specifies the CT1/PRI interface number.
A PRI set cannot coexist with a channel set on a CT1/PRI interface.
Examples
# Bundle timeslots 1, 2, and 8 through 12 into a PRI set on T1 2/4/0.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] pri-set timeslot-list 1,2,8-12
Related commands
channel-set
reset counters controller t1
Use reset counters controller t1 to clear CT1/PRI interface statistics.
Syntax
reset counters controller t1 [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CT1/PRI interface by its number. If you do not specify this argument, the command clears statistics for all CT1/PRI interfaces.
Usage guidelines
The reset counters interface command clears statistics for all interfaces.
To display CT1/PRI interface statistics, use the display controller t1 command.
Examples
# Clear statistics for the CT1/PRI interface T1 2/4/0.
<Sysname> reset counters controller t1 2/4/0
Related commands
display controller t1
sendloopcode
Use sendloopcode to send remote loopback control code.
Syntax
sendloopcode { fdl-ansi-llb-down | fdl-ansi-llb-up | fdl-ansi-plb-down | fdl-ansi-plb-up | fdl-att-plb-down | fdl-att-plb-up | inband-llb-down | inband-llb-up }
Default
No remote loopback control code is sent.
Views
CT1/PRI interface view
Predefined user roles
network-admin
Parameters
fdl-ansi-llb-down: Sends ANSI-compliant LLB deactivation request code in the FDL to remove remote loopback.
fdl-ansi-llb-up: Sends ANSI-compliant line loopback (LLB) activation request code in the FDL to start remote loopback.
fdl-ansi-plb-down: Sends ANSI-compliant PLB deactivation request code in the FDL to remove remote loopback.
fdl-ansi-plb-up: Sends ANSI-compliant payload loopback (PLB) activation request code in the FDL to start remote loopback.
fdl-att-plb-down: Sends AT&T-complaint PLB deactivation request code in the FDL to remove remote loopback.
fdl-att-plb-up: Sends AT&T-complaint PLB activation request code in the FDL to start remote loopback.
inband-llb-down: Sends in-band LLB deactivation request code in compliance with the ANSI or AT&T implementation to remove remote loopback.
inband-llb-up: Sends in-band line loopback (LLB) activation request code compliant with the ANSI and AT&T implementation to start remote loopback.
Usage guidelines
You can configure loopback on the remote CT1/PRI interface by sending loopback request code. Before you configure this command, make sure the remote CT1/PRI interface can automatically receive the loopback control code.
In LLB mode, all 193 bits (one synchronization bit and 192 effective payload bits) in a T1 PCM frame are looped back. In PLB mode, only 192 effective payload bits are looped back.
The format of loopback code is compliant with ANSI T1.403 or AT&T TR 54016.
In SF framing, LLB code is sent using the effective bandwidth. In ESF framing, both LLB code and PLB code are sent and received in the FDL.
Use this command in conjunction with the far-end T1 device. The far-end device must be able to set loopback mode depending on the detected loopback code. The sending of remote loopback control code lasts 5 seconds without affecting the operation of other interfaces.
Examples
# Send in-band LLB activation request code.
<Sysname> system-view
[Sysname] controller t1 2/4/0
[Sysname-T1 2/4/0] sendloopcode inband-llb-up
E1-F interface commands
clock-change auto
Use clock-change auto to enable automatic clock mode switchover on an E1-F interface.
Use undo clock-change auto to disable the automatic clock mode switchover on an E1-F interface.
Syntax
clock-change auto
undo clock-change auto
Default
Automatic clock mode switchover is disabled on an E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Usage guidelines
When automatic clock mode switchover is enabled, the interface automatically switches to the master clock mode when both of the following conditions exist:
· The interface uses the slave clock mode.
· The interface receives an alarm indication signal (AIS), loss of signal (LOS), or loss of frame (LOF) alarm.
After the alarm is cleared, the interface automatically switches back to the slave clock mode.
When automatic clock mode switchover is disabled, the interface uses the user-configured clock mode.
Examples
# Enable automatic clock mode switchover for the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] clock-change auto
Related commands
fe1 clock
crc
Use crc to configure CRC mode for an E1-F interface.
Use undo crc to restore the default.
Syntax
crc { 16 | 32 | none }
undo crc
Default
The CRC mode for an E1-F interface is 16-bit CRC.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
16: Specifies 16-bit CRC.
32: Specifies 32-bit CRC.
none: Disables CRC.
Examples
# Specify 32-bit CRC on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] crc 32
display fe1
Use display fe1 to display information about E1-F interfaces.
Syntax
display fe1 [ serial interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
serial interface-number: Specifies an E1-F interface by its number. If you do not specify an interface, this command displays information about all E1-F interfaces.
Usage guidelines
If the specified interface is a common serial interface rather than an E1-F interface, the system displays a prompt.
Examples
# Display information about the E1-F interface Serial 2/1/0.
<Sysname> display fe1 serial 2/1/0
Serial2/1/0
Basic Configuration:
Work mode: E1 framed, Cable type: 75 Ohm unbalanced
Frame format: no-crc4
Line code: hdb3, Source clock: slave
Idle code: 7e, Itf type: 7e, Itf number: 4
Loopback: not set
Alarm State:
Receiver alarm state is None.
Transmitter is sending remote alarm.
Historical Statistics:
Data in current interval (19349 seconds elapsed):
Loss Frame Alignment: 129 seconds, Framing Error: 0 seconds
CRC Error: 0 seconds, Alarm Indication: 0 seconds
Loss-of-signals: 129 seconds, Code Violations: 0 seconds
Slip: 0 seconds, E-Bit Error: 0 seconds
Table 11 Command output
|
Field |
Description |
|
Cable type |
Cable type of the interface (75 ohm unbalanced or 120 ohm balanced). |
|
Frame-format |
Framing format: CRC4 or no-CRC4. |
|
Line Code |
Line code format: AMI or HDB3. |
|
Source clock |
Clock source used by the interface: master or slave. |
|
Idle code |
Idle code: 7e or ff. |
|
Itf type |
Interframe filling tag: 7e or ff. |
|
Itf number |
Number of interframe filling tags. |
|
Loopback |
Whether loopback is configured on the interface. |
|
Data in current interval (19349 seconds elapsed): Loss Frame Alignment: 129 seconds, Framing Error: 0 seconds CRC Error: 0 seconds, Alarm Indication: 0 seconds Loss-of-signals: 129 seconds, Code Violations: 0 seconds Slip: 0 seconds, E-Bit Error: 0 seconds |
Time duration that each error lasts within the interval. The errors include frame misalignment, frame errors, alarms, loss of signals, code violation, and frame slipping. |
fe1 alarm-detect
Use fe1 alarm-detect to enable RAI detection on an E1-F interface.
Use undo fe1 alarm-detect to disable RAI detection on an E1-F interface.
Syntax
fe1 alarm-detect rai
undo fe1 alarm-detect rai
Default
RAI detection is enabled on an E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
rai: Remote Alarm Indication (RAI).
Usage guidelines
This command is applicable when the interface operates in framed mode.
Examples
# Disable RAI detection on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] undo fe1 alarm-detect rai
Related commands
fe1 unframed
fe1 cable
Use fe1 cable to set the cable length for an E1-F interface.
Use undo fe1 cable to restore the default.
Syntax
fe1 cable { long | short }
undo fe1 cable
Default
The long keyword applies.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
long: Supports long cables.
short: Supports short cables.
Examples
# Set the cable length type to short on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 cable short
fe1 cable-type
Use fe1 cable-type to set the cable impedance for an E1-F interface.
Use undo fe1 cable-type to restore the default.
Syntax
fe1 cable-type { 75 | 120 }
undo fe1 cable-type
Default
The cable impedance is 75 ohm.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
75: Specifies 75 ohm.
120: Specifies 120 ohm.
Usage guidelines
This command is supported only on E1T1-F interfaces operating in E1-F mode.
Examples
# Set the cable impedance to 120 ohm for the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 cable-type 120
fe1 clock
Use fe1 clock to set the clock mode of an E1-F interface.
Use undo fe1 clock to restore the default.
Syntax
fe1 clock { master | slave }
undo fe1 clock
Default
The clock mode for an E1-F interface is slave.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of an E1-F interface is master, it uses the internal clock source. When the clock mode of an E1-F interface is slave, it uses the line clock source.
Set the clock mode for an E1-F interface as follows:
· When the E1-F interface is operating in DCE mode, set its clock mode to master.
· When the E1-F interface is operating in DTE mode, set its clock mode to slave.
Examples
# Set the clock mode to master for the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 clock master
Related commands
clock-change auto
fe1 code
Use fe1 code to set the line code format for an E1-F interface.
Use undo fe1 code to restore the default.
Syntax
fe1 code { ami | hdb3 }
undo fe1 code
Default
The line code format is HDB3 for the E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
ami: Specifies the AMI line code format.
hdb3: Specifies the HDB3 line code format.
Usage guidelines
An E1-F interface must use the same line code format as its remote end. For the interface to operate correctly, configure the fe1 data-coding inverted command if the AMI format is used.
The SIC-2E1-F interface modules do not support the AMI format.
Examples
# Set the line code format to AMI for the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 code ami
Related commands
fe1 data-coding
fe1 data-coding
Use fe1 data-coding to enable or disable user data inversion for an E1-F interface.
Use undo fe1 data-coding to restore the default.
Syntax
fe1 data-coding { inverted | normal }
undo fe1 data-coding
Default
User data inversion is disabled for an E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
inverted: Enables user data inversion.
normal: Disables user data inversion.
Usage guidelines
To prevent 7e in valid data from being mistaken for padding characters, HDLC inserts a zero after every five consecutive ones in the data stream. In data inversion, each bit one is inverted to bit zero, and each bit zero is inverted to bit one. After the inversion, at least a bit one is present in every eight consecutive bits.
When AMI encoding is used on an E1-F interface, data inversion eliminates the presence of multiple consecutive zeros.
The data inversion setting must be the same at the two ends of an E1-F line.
The SIC-2E1-F interface modules do not support data inversion.
Examples
# Enable user data inversion on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 data-coding inverted
Related commands
fe1 code
fe1 detect-ais
Use fe1 detect-ais to enable AIS detection on an E1-F interface.
Use undo fe1 detect-ais to disable AIS detection on an E1-F interface.
Syntax
fe1 detect-ais
undo fe1 detect-ais
Default
AIS detection is enabled on an E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Usage guidelines
This command is available when the E1-F interface is operating in unframed mode.
Examples
# Enable AIS detection on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 detect-ais
Related commands
fe1 unframed
fe1 frame-format
Use fe1 frame-format to set the framing format for an E1-F interface.
Use undo fe1 frame-format to restore the default.
Syntax
fe1 frame-format { crc4 | no-crc4 }
undo fe1 frame-format
Default
The framing format of an E1-F interface is no-CRC4.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
crc4: Sets framing format to CRC4.
no-crc4: Sets framing format to no-CRC4.
Usage guidelines
An E1-F interface in framed mode supports both CRC4 and no-CRC4 framing formats. Only CRC4 supports four-bit CRC on physical frames.
Examples
# Set the framing format to crc4 for the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 frame-format crc4
Related commands
fe1 unframed
fe1 idle-code
Use fe1 idle-code to set the line idle code on an E1-F interface.
Use undo fe1 idle-code to restore the default.
Syntax
fe1 idle-code { 7e | ff }
undo fe1 idle-code
Default
The line idle code on an E1-F interface is 7e.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
7e: Sets the line idle code to 7e (hexadecimal).
ff: Sets the line idle code to ff (hexadecimal).
Usage guidelines
The line idle code is sent in the timeslots that are not bundled into logical channels on the interface.
Examples
# Set the line idle code to 7e on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 idlecode 7e
fe1 itf
Use fe1 itf to set the type and number of interframe filling tags on an E1-F interface.
Use undo fe1 itf to restore the default.
Syntax
fe1 itf { number number | type { 7e | ff } }
undo fe1 itf { number | type }
Default
On an E1-F interface, the interframe filling tag is 7e, and the number of interframe filling tags is 4.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
number number: Sets the number of interframe filling tags, in the range of 0 to 14. An interframe filling tag is one byte in length.
type: Specifies the type of interframe filling tag type.
7e: Sets the interframe filling tag type to 7e (hexadecimal).
ff: Sets the interframe filling tag type to ff (hexadecimal).
Usage guidelines
The bundled timeslots on the E1-F interface send interframe filling tags when no service data is present.
When an E1-F interface is operating in unframed mode and the interframe filling tag type is set to ff, all "1" data will be transmitted on the line when no service data is present, which can easily trigger AIS alarms. To prevent generation of AIS alarms in this situation, execute the undo fe1 detect-ais command to disable AIS detection.
Examples
# Set the type of interframe filling tag to ff on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 itf type ff
# Set the number of interframe filling tags to 5 on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 itf number 5
fe1 loopback
Use fe1 loopback to enable a type of loopback on an E1-F interface.
Use undo fe1 loopback to disable loopback on an E1-F interface.
Syntax
fe1 loopback { local | payload | remote }
undo fe1 loopback
Default
Loopback is disabled on an E1-F interface.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
local: Enables internal loopback.
payload: Enables external payload loopback.
remote: Enables external loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
The three loopback modes cannot be used simultaneously on an E1-F interface.
Examples
# Enables internal loopback on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 loopback local
fe1 timeslot-list
Use fe1 timeslot-list to bundle timeslots on an E1-F interface.
Use undo fe1 timeslot-list to restore the default.
Syntax
fe1 timeslot-list list
undo fe1 timeslot-list
Default
All the timeslots on an E1-F interface are bundled to form a 1984 kbps interface.
Views
E1-F interface view
Predefined user roles
network-admin
Parameters
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 31.
Usage guidelines
Timeslot bundling results in interface rate change. For example, if you bundle timeslots 1 through 10, the interface rate is 10 × 64 kbps.
You can create only one channel set on an E1-F interface. For the channel set, the system creates one synchronous serial interface. The number of the serial interface is identical to the number of the E1-F interface.
On a CE1/PRI interface, you can create multiple channel sets. For each set, the system automatically creates a synchronous serial interface.
Timeslot 0 on E1-F interfaces is used for transmitting synchronization information. A bundling operation only involves timeslots 1 through 31.
When the E1-F interface is operating in unframed mode, the fe1 timeslot-list command is invalid.
Examples
# Bundle timeslots 1, 2, 5, 10 through 15, and 18 on the E1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 timeslot-list 1,2,5,10-15,18
Related commands
fe1 unframed
fe1 unframed
Use fe1 unframed to configure an E1-F interface to operate in unframed mode.
Use undo fe1 unframed to restore the default.
Syntax
fe1 unframed
undo fe1 unframed
Default
An E1-F interface operates in framed mode.
Views
E1-F interface view
Predefined user roles
network-admin
Usage guidelines
In unframed mode, an E1-F interface is a 2048 kbps interface without timeslot division and has the same logical features as a standard synchronous serial interface.
In framed mode, an E1-F interface is physically divided into 32 timeslots numbered 0 through 31, with timeslot 0 for synchronization.
Examples
# Set the E1-F interface Serial 2/1/0 to operate in unframed mode.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fe1 unframed
Related commands
fe1 timeslot-list
reset counters interface serial
Use reset counters interface serial to clear serial interface statistics.
Syntax
reset counters interface serial [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
serial [ interface-number ]: Specifies a serial interface by its number. If you do not specify the serial keyword, this command clears statistics for all interfaces. If you specify the serial keyword without specifying an interface, this command clears statistics for all serial interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for Serial 2/1/0.
<Sysname> reset counters interface serial 2/1/0
T1-F interface commands
crc
Use crc to configure the CRC mode on a T1-F interface.
Use undo crc to restore the default.
Syntax
crc { 16 | 32 | none }
undo crc
Default
The CRC mode is 16-bit CRC.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
16: Specifies 16 bit CRC.
32: Specifies 32 bit CRC.
none: Disables CRC.
Examples
# Specify 32-bit CRC on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] crc 32
display ft1
Use display ft1 to display information about a T1-F interface.
Syntax
display ft1 [ serial interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
serial interface-number: Specifies a T1-F interface by its number. If you do not specify an interface, this command displays information about all T1-F interfaces.
Usage guidelines
If the specified interface is a common serial interface rather than a T1-F interface, the system displays a prompt.
Examples
# Display information about the T1-F interface Serial 2/1/0.
<Sysname> display ft1 serial 2/1/0
Serial2/1/0
Basic Configuration:
Work mode: T1 framed, Cable type: 100 Ohm balanced
Frame-format: esf, fdl: none, Line code: b8zs
Source clock: slave, Data-coding: normal
Idle code: ff, Itf type: ff, Itf number: 2
Loopback: not set
Alarm State:
Receiver alarm state is Loss-of-Signal.
Transmitter is sending remote alarm.
Pulse density violation detected.
SendLoopCode History:
Inband-llb-up: 0 times, Inband-llb-down: 0 times
Fdl-ansi-llb-up: 0 times, Fdl-ansi-llb-down: 0 times
Fdl-ansi-plb-up: 0 times, Fdl-ansi-plb-down: 0 times
Fdl-att-plb-up: 0 times, Fdl-att-plb-down: 0 times
BERT state:(stopped, not completed)
Test pattern: 2^15, Status: Not Sync, Sync Detected: 0
Time: 0 minutes, Time past: 0 minutes
Bit Errors (since test started): 0 bits
Bits Received (since test started): 0 Kbits
Bit Errors (since latest sync): 0 bits
Bits Received (since latest sync): 0 Kbits
Historical Statistics:
Data in current interval (285 seconds elapsed):
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 286 seconds
Slip: 7 seconds, Fr Loss: 286 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 286 seconds
Data in Interval 1:
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 901 seconds
Slip: 22 seconds, Fr Loss: 901 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 901 seconds
Data in Interval 2:
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 900 seconds
Slip: 23 seconds, Fr Loss: 900 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 900 seconds
Total Data (last 2 15 minute intervals):
Line Code Violations: 0, Path Code Violations: 0
Ais Alarm: 0 seconds, Los Alarm: 2087 seconds
Slip: 52 seconds, Fr Loss: 2087 seconds
Line Err: 0 seconds, Degraded: 0 minutes
Errored: 0 seconds, Bursty Err: 0 seconds
Severely Err: 0 seconds, Unavail: 2087 seconds
Table 12 Command output
|
Field |
Description |
|
Basic Configuration |
Basic configurations for the interface. |
|
Work mode |
T1 interface operating mode: T1 or CT1. |
|
Cable type |
Cable type of the interface, 100 ohm balanced in this sample output. |
|
Frame-format |
Frame format configured on the interface: ESF or SF. |
|
fdl |
FDL format: ANSI, ATT, or none. |
|
Line code |
AMI or B8ZS. |
|
Source clock |
Clock source used by the interface: master or slave. |
|
Data-coding |
Normal or inverted. |
|
Idle code |
Idle code: 7e or ff. |
|
Itf type |
Type of inter-frame filling tags: 7e or ff. |
|
Itf number |
Number of inter-frame filling tags. |
|
Loop back |
Loopback setting on the interface: local, payload, remote, or not set. |
|
Receiver alarm state is Loss-of-Signal |
Type of received alarm: none, LOS, LOF, RAI, or AIS. |
|
Transmitter is sending remote alarm |
Type of transmitted alarm: RAI or none. |
|
Pulse density violation detected |
The detected pulse density is incompliant with the specification. |
|
SendLoopCode History: Inband-llb-up: 0 times, Inband-llb-down: 0 times Fdl-ansi-llb-up: 0 times, Fdl-ansi-llb-down: 0 times Fdl-ansi-plb-up: 0 times, Fdl-ansi-plb-down: 0 times Fdl-att-plb-up: 0 times, Fdl-att-plb-down: 0 times |
History of loopback code sending to the far-end, including the number of transmissions for each type of code, and the type of the last sent code. (For more information, see "ft1 sendloopcode.") |
|
BERT state |
BERT test state: · completed—The test has been completed. · stopped—The test has been manually terminated. · running—The test is running. |
|
Test pattern |
Test pattern in use: 2^15 or 2^20. |
|
Status |
Whether the interface is being synchronized: · Sync—The interface is being synchronized. · Not Sync—The interface is not being synchronized. |
|
Sync Detected |
Number of detected synchronizations. |
|
Time |
Duration of the BERT test. |
|
Time past |
Time that has elapsed. |
|
Bit Errors (since test started) |
Number of bit errors received since the start of the BERT test. |
|
Bits Received (since test started) |
Number of bits received since the start of the BERT test. |
|
Bit Errors (since latest sync) |
Number of bit errors received since the last synchronization. |
|
Bits Received (since latest sync) |
Number of bits received since the last synchronization. |
|
Historical Statistics: |
Historical statistics for the interface. |
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
Last clearing of counters |
The most recent time that the reset counters interface serial command was executed. This field displays Never if this command has not been executed since the device startup. |
|
Data in current interval (285 seconds elapsed): Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 286 seconds Slip: 7 seconds, Fr Loss: 286 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 286 seconds |
Statistics spanning the current interval. The statistical items, such as AIS alarm, LOS signal, and LFA, are provided according to the T1 specifications for the physical layer. For more information, see ANSI T1.403 and AT&T TR 54016. |
|
Data in Interval 1: Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 901 seconds Slip: 22 seconds, Fr Loss: 901 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 901 seconds |
Statistics spanning the first interval. The statistical items are the same as those provided by the statistics spanning the current interval. |
|
Data in Interval 2: Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 900 seconds Slip: 23 seconds, Fr Loss: 900 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 900 seconds |
Statistics spanning the second interval. The statistical items are the same as those provided by the statistics spanning the current interval. |
|
Total Data (last 2 15 minute intervals): Line Code Violations: 0, Path Code Violations: 0 Ais Alarm: 0 seconds, Los Alarm: 2087 seconds Slip: 52 seconds, Fr Loss: 2087 seconds Line Err: 0 seconds, Degraded: 0 minutes Errored: 0 seconds, Bursty Err: 0 seconds Severely Err: 0 seconds, Unavail: 2087 seconds |
Statistics spanning the last two intervals. The statistical items are the same as those provided by the statistics spanning the current interval. |
ft1 alarm-detect
Use ft1 alarm-detect to enable RAI detection on an interface.
Use undo ft1 alarm-detect to disable RAI detection on an interface.
Syntax
ft1 alarm-detect rai
undo ft1 alarm-detect rai
Default
RAI detection is enabled on an interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
rai: Remote Alarm Indication (RAI).
Usage guidelines
This command is applicable when the framing format on the interface is ESF.
Examples
# Disable RAI detection on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] undo ft1 alarm-detect rai
Related commands
ft1 frame-format
ft1 alarm-threshold
Use ft1 alarm-threshold to set LOS, AIS, or LFA alarm thresholds on a T1-F interface.
Use undo ft1 alarm-threshold to restore the default.
Syntax
ft1 alarm-threshold { ais { level-1 | level-2 } | lfa { level-1 | level-2 | level-3 | level-4 } | los { pulse-detection | pulse-recovery } value }
undo ft1 alarm-threshold { ais | lfa | los { pulse-detection | pulse-recovery } }
Default
For AIS and LFA, the alarm threshold is level-1.
For LOS, the value of pulse-detection is 176 and the value of pulse-recovery is 22. A LOS alarm is generated if the number of pulses detected within 176 pulse intervals is less than 22.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
ais: Specifies an AIS alarm.
· level-1: Specifies the condition when the number of zeros in the bit stream of an SF or ESF frame is less than or equal to 2.
· level-2: Specifies one of the following conditions:
¡ In an SF frame, the number of zeros is less than or equal to 3 in the bit stream.
¡ In an ESP frame, the number of zeros is less than or equal to 5 in the bit stream.
lfa: Specifies an LFA alarm.
· level-1: Specifies the condition when two of four frame alignment bits are lost.
· level-2: Specifies the condition when two of five frame alignment bits are lost.
· level-3: Specifies the condition when two of six frame alignment bits are lost.
· level-4: Specifies the condition when errors are detected in four consecutive ESF frames. This keyword is available only for ESF frames.
los: Specifies a LOS alarm.
· pulse-detection: Specifies the pulse detection duration threshold of the LOS alarm, in units of pulse intervals.
· pulse-recovery: Specifies the pulse threshold of the LOS alarm.
value: Specifies the value of the pulse-detection threshold or pulse-recovery threshold.
· For the pulse-detection threshold, this argument is in the range of 16 to 4096.
· For the pulse-recovery threshold, this argument is in the range of 1 to 256.
If the number of the pulses detected during the total length of the specified pulse detection intervals is smaller than the pulse-recovery threshold, a LOS alarm occurs. For example, if the two thresholds take their defaults, a LOS alarm is generated if the number of pulses detected within 176 pulse intervals is less than 22.
Examples
# Set the number of detection intervals to 300 for the pulse detection duration threshold.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 alarm-threshold los pulse-detection 300
Related commands
ft1 frame-format
ft1 bert
Use ft1 bert to start a BERT test on a T1-F interface.
Use undo ft1 bert to stop the BERT test running on a T1-F interface.
Syntax
ft1 bert pattern { 2^20 | 2^15 } time minutes [ unframed ]
undo ft1 bert
Default
No BERT test is performed on a T1-F interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
pattern: Sets a BERT pattern.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· 2^20: Specifies the pattern length (in bits) as two to the twentieth power.
time minutes: Sets the duration (in minutes) of a BERT test. The minutes argument is in the range of 1 to 1440.
unframed: Sets the test pattern to cover the overhead bits of the frame.
Usage guidelines
The T1-F interface supports only the 2^15 and 2^20 BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of a BERT test, use the display ft1 command.
Examples
# Run a 10-minute 2^20 BERT test on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 bert pattern 2^20 time 10
Related commands
display ft1
ft1 cable
Use ft1 cable to set the cable attenuation and length on a T1-F interface.
Use undo ft1 cable to restore the default.
Syntax
ft1 cable { long decibel | short length }
undo ft1 cable
Default
The cable attenuation length on a T1-F interface is long 0db.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
long decibel: Matches 199.6-meter (655-feet) and longer cable length. The decibel argument can be 0db, -7.5db, -15db, or -22.5db, depending on the signal quality at the receiving end. No external CSU is required.
short length: Matches a cable length shorter than 199.6 meters (655 feet). The length argument can be 133ft, 266ft, 399ft, 533ft, or 655ft, depending on the actual transmission distance.
Usage guidelines
You can use this command to adapt the signal waveform to different transmission conditions such as the quality of the signal received by the receiver. If signal quality is good, use the default setting.
Examples
# Set the cable length to 133 feet (40.5 meters) on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 cable short 133ft
Related commands
ft1 frame-format
ft1 clock
Use ft1 clock to set the clock mode of a T1-F interface.
Use undo ft1 clock to restore the default.
Syntax
ft1 clock { master | slave }
undo ft1 clock
Default
The clock mode of a T1-F interface is slave.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of a T1-F interface is master, it uses the internal clock source. When the clock mode of a T1-F interface is slave, it uses the line clock source.
Set the clock mode for a T1-F interface as follows:
· When the T1-F interface is operating in DCE mode, set its clock mode to master.
· When the T1-F interface is operating in DTE mode, set its clock mode to slave.
· When two T1-F interfaces on two routers are directly connected, configure the two ends with different clock modes.
· When the T1-F interface on a router is connected to a switch, the T1-F interface on the router operates as a DTE. The switch operates as a DCE. Set the clock mode to slave for the T1-F interface on the router to accept the clock provided by the switch.
Examples
# Set the clock mode to master on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 clock master
ft1 code
Use ft1 code to set the line code format for a T1-F interface.
Use undo ft1 code to restore the default.
Syntax
ft1 code { ami | b8zs }
undo ft1 code
Default
The line code format is B8ZS for the T1-F interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
ami: Specifies the AMI line code format.
b8zs: Specifies the B8ZS line code format.
Usage guidelines
A T1-F interface must use the same line code format as its remote end. For the interface to operate correctly, configure the ft1 data-coding inverted command if the AMI format is used.
Examples
# Set the line code format to AMI for the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 code ami
Related commands
ft1 data-coding
ft1 data-coding
Use ft1 data-coding to enable or disable user data inversion for a T1-F interface.
Use undo ft1 data-coding to restore the default.
Syntax
ft1 data-coding { inverted | normal }
undo ft1 data-coding
Default
Data inversion is disabled for a T1-F interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
inverted: Enables user data inversion.
normal: Disables user data inversion.
Usage guidelines
To prevent the string 7e in valid data from being used as paddings, HDLC inserts a zero after every five consecutive ones in the data stream. In data inversion, each bit one is inverted to bit zero, and each bit zero is inverted to bit one. After the inversion, at least a bit one is present in every eight consecutive bits.
When AMI encoding is used on a T1-F interface, data inversion eliminates the presence of multiple consecutive zeros.
At the two ends of a T1-F line, the data inversion settings must be the same.
Examples
# Enable user data inversion on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 data-coding inverted
Related commands
ft1 code
ft1 fdl
Use ft1 fdl to set the behavior of a T1-F interface on the FDL in ESF framing.
Use undo ft1 fdl to restore the default.
Syntax
ft1 fdl { ansi | att | both | none }
undo ft1 fdl
Default
FDL is disabled (none).
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
ansi: Specifies ANSI T1.403 for FDL.
att: Specifies AT&T TR 54016 for FDL.
both: Specifies both ANSI T1.403 and AT&T TR 54016 for FDL.
none: Disables FDL.
Usage guidelines
FDL is an embedded 4 kbps overhead channel within the ESF format for transmitting performance statistics or loopback code.
You can change the setting depending on the setting at the far end.
Examples
# Set ANSI FDL on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 fdl ansi
Related commands
ft1 frame-format
ft1 frame-format
Use ft1 frame-format to set the framing format for a T1-F interface.
Use undo ft1 frame-format to restore the default.
Syntax
ft1 frame-format { esf | sf }
undo ft1 frame-format
Default
The framing format on a T1-F interface is esf.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
esf: Sets the framing format to ESF.
sf: Sets the framing format to SF.
Usage guidelines
T1-F interfaces support the following framing formats:
· ESF format—Allows you to test the system without affecting the ongoing service.
· SF format—Provides more significant bits for user data transmission because multiple frames can share the same FSC and signaling information.
Examples
# Set the framing format to SF for the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 frame-format sf
Related commands
ft1 fdl
ft1 idle-code
Use ft1 idle-code to set the line idle code on a T1-F interface.
Use undo ft1 idle-code to restore the default.
Syntax
ft1 idle-code { 7e | ff }
undo ft1 idle-code
Default
The line idle code on a T1-F interface is 7e.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
7e: Sets the line idle code to 7e (hexadecimal).
ff: Sets the line idle code to ff (hexadecimal).
Usage guidelines
The line idle code is sent in the timeslots that are not bundled into logical channels on the interface.
Examples
# Set the line idle code to 7e on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 idlecode 7e
ft1 itf
Use ft1 itf to set the type and the number of interframe filling tags on a T1-F interface.
Use undo ft1 itf to restore the default.
Syntax
ft1 itf { number number | type { 7e | ff } }
undo ft1 itf { number | type }
Default
On a T1-F interface, the interframe filling tag is 7e, and the number of interframe filling tags is 4.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
number number: Sets the number of interframe filling tags, in the range of 0 to 14. An interframe filling tag is one byte in length.
type: Specifies the interframe filling tag type.
7e: Sets the interframe filling tag type to 7e (hexadecimal).
ff: Sets the interframe filling tag type to ff (hexadecimal).
Usage guidelines
Interframe filling tags are sent when no service data is sent on the timeslots bundled into logical channels on a T1-F interface.
Do not use the ft1 itf type ff command if both the ft1 code ami command and the ft1 data-coding inverted command are configured. Otherwise, the T1-F interface will not operate correctly.
Examples
# Set the type of interframe filling tag to ff on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 itf type ff
# Set the number of interframe filling tags to 5 on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 itf number 5
Related commands
ft1 code
ft1 data-coding
ft1 loopback
Use ft1 loopback to enable a type of loopback on a T1-F interface.
Use undo ft1 loopback to disable loopback on a T1-F interface.
Syntax
ft1 loopback { local | payload | remote }
undo ft1 loopback
Default
Loopback is disabled on a T1-F interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
local: Enables internal loopback.
payload: Enables external payload loopback.
remote: Enables external loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
The three loopback modes cannot be used simultaneously on a T1-F interface.
Examples
# Enable local loopback on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 loopback local
ft1 sendloopcode
Use ft1 sendloopcode to send remote loopback control code.
Syntax
ft1 sendloopcode { fdl-ansi-llb-down | fdl-ansi-llb-up | fdl-ansi-plb-down | fdl-ansi-plb-up | fdl-att-plb-down | fdl-att-plb-up | inband-llb-down | inband-llb-up }
Default
No remote loopback control code is sent.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
fdl-ansi-llb-down: Sends ANSI-compliant LLB deactivation request code in the FDL to remove the remote loopback.
fdl-ansi-llb-up: Sends ANSI-compliant line loopback (LLB) activation request code in the FDL to start remote loopback.
fdl-ansi-plb-down: Sends ANSI-compliant PLB deactivation request code in the FDL to remove the remote loopback.
fdl-ansi-plb-up: Sends ANSI-compliant payload loopback (PLB) activation request code in the FDL to start remote loopback.
fdl-att-plb-down: Sends AT&T-complaint PLB deactivation request code in the FDL to remove the remote loopback.
fdl-att-plb-up: Sends AT&T-complaint PLB activation request code in the FDL to start the remote loopback.
inband-llb-down: Sends in-band LLB deactivation request code compliant with the ANSI or AT&T implementation to remove the remote loopback.
inband-llb-up: Sends in-band line loopback (LLB) activation request code compliant with the ANSI or AT&T implementation to start the remote loopback.
Usage guidelines
You can configure loopback on the remote T1-F interface by sending a loopback request code.
In LLB mode, all 193 bits (one synchronization bit and 192 effective payload bits) in a T1 PCM frame are looped back. In PLB mode, only 192 effective payload bits are looped back.
The format of the loopback code is compliant with ANSI T1.403 or AT&T TR 54016.
In SF framing, LLB code is sent using the effective bandwidth (timeslots 1 through 24). In ESF framing, both LLB code and PLB code are sent and received in the FDL in ESF frames.
You can use this command only when the remote T1-F interface can automatically detect loopback request code from the network.
Examples
# Send in-band LLB activation request code.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 sendloopcode inband-llb-up
Related commands
ft1 frame-format
ft1 timeslot-list
Use ft1 timeslot-list to bundle timeslots on a T1-F interface.
Use undo ft1 timeslot-list to restore the default.
Syntax
ft1 timeslot-list list [ speed { 56k | 64k } ]
undo ft1 timeslot-list
Default
All the timeslots on the T1-F interface are bundled to form a 1536 kbps interface.
Views
T1-F interface view
Predefined user roles
network-admin
Parameters
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 24.
speed { 56k | 64k }: Time slot bundling speed in kbps. If 56k applies, timeslots are bundled into an n × 56 kbps bundle. If 64k (the default) applies, timeslots are bundled into an n × 64 kbps bundle.
Usage guidelines
Timeslot bundling results in interface rate change. For example, if you bundle timeslots 1 through 10, the interface rate is 10 × 64 kbps or 10 × 56 kbps.
You can create only one channel set on a T1-F interface. For the channel set, the system creates one synchronous serial interface. The number of the serial interface is identical to the number of the T1-F interface.
On a CT1/PRI interface, you can create multiple channel sets. For each set, the system automatically creates a synchronous serial interface.
Examples
# Bundle timeslots 1, 2, 5, 10 through 15, and 18 on the T1-F interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ft1 timeslot-list 1,2,5,10-15,18
reset counters interface serial
Use reset counters interface serial to clear serial interface statistics.
Syntax
reset counters interface serial [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
serial [ interface-number ]: Specifies a serial interface by its number. If you do not specify the serial keyword, this command clears statistics for all interfaces. If you specify the serial keyword without specifying an interface, this command clears statistics for all serial interfaces.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
Examples
# Clear statistics for Serial 2/1/0.
<Sysname> reset counters interface serial 1/0
CE3 interface commands
bert
Use bert to start a BERT test on a CE3 interface.
Use undo bert to stop the BERT test running on a CE3 interface.
Syntax
bert pattern { 2^7 | 2^11 | 2^15 | qrss } time number [ unframed ]
undo bert
Default
No BERT test is performed on a CE3 interface.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
pattern: Sets a BERT pattern.
· 2^7: Specifies the pattern length (in bits) as two to the seventh power.
· 2^11: Specifies the pattern length (in bits) as two to the eleventh power.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· qrss: Specifies the pattern length (in bits) as two to the twentieth power. In this pattern, the maximum number of consecutive zeros is 14.
time number: Sets the duration (in minutes) of a BERT test. The number argument is in the range of 1 to 1440.
unframed: Sets the overhead bits of the padding frames for a BERT test.
Usage guidelines
The CE3 interface supports the 2^7, 2^11, 2^15, and QRSS BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of a BERT test, use the display controller e3 command.
Examples
# Run a 10-minute QRSS BERT test on CE3 interface E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] bert pattern qrss time 10
clock
Use clock to set the clock mode of a CE3 interface.
Use undo clock to restore the default.
Syntax
clock { master | slave }
undo clock
Default
The clock mode for a CE3 interface is slave.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of a CE3 interface is master, it uses the internal clock source. When the clock mode of a CE3 interface is slave, it uses the line clock source.
When connected to a SONET/SDH transmission device, the CE3 interface must use the slave clock. The clock provided by the transmission device is more precise.
If two CE3 interfaces are directly connected, you must configure the two ends with different clock modes.
Examples
#Set the clock mode to master for CE3 interface E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] clock master
controller e3
Use controller e3 to enter CE3 interface view.
Syntax
controller e3 interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CE3 interface by its number.
Examples
# Enter the view of interface E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0]
display controller e3
Use display controller e3 to display information about CE3 interfaces.
Syntax
display controller [ e3 [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
e3 [ interface-number ]: Specifies a CE3 interface by its number. If you do not specify the e3 keyword, the command displays information about all CE3 interfaces, CPOS interfaces, CT1/PRI interfaces, CE1/PRI interfaces, and CT3 interfaces. If you specify the e3 keyword without specifying an interface, the command displays information about all CE3 interfaces.
Usage guidelines
This command also displays information about each E1 line on the CE3 interface if the interface is operating in CE3 mode.
Examples
# Display information about E3 2/4/0.
<Sysname> display controller e3 2/4/0
E3 2/4/0
Current state: UP
Description: E3 2/4/0 Interface
Frame-format: G751, line code: HDB3, clock: slave
national-bit: 1, Current mode: CE3, loopback: not set, Alarm: none
ERROR: 2 BPV, 0 EXZ, 0 FrmErr, 0 FEBE
BERT state: (stopped, not completed)
Test pattern: 2^7, Status: Not Sync, Sync Detected: 0
Time: 2 minutes Time past: 2 minutes
Bit errors (since test started): 0 bits
Bits received (since test started): 0 Mbits
Bit errors (since latest sync): 0 bits
Bits received (since latest sync): 0 Mbits
E3 2/4/0 CE1 1: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 2: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 3: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 4: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 5: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 6: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 7: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 8: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 9: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 10: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 11: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 12: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 13: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 14: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 15: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
E3 2/4/0 CE1 16: up
Frame-format: NO-CRC4, clock: slave, loopback: not set
Receiver alarm state: none
BERT state: (stopped, not completed)
Table 13 Command output
|
Field |
Description |
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
Description |
Description of the interface. |
|
Frame-format |
Frame format configured on the interface: CRC4 or NO CRC4. |
|
Line Code |
Line code: AMI or B8ZS. |
|
clock |
Clock source used by the interface: master or slave. |
|
National-bit |
International bit. |
|
Current mode |
Operating mode of the interface: E3 or CE3. |
|
Loopback |
Loopback setting on the interface. |
|
Alarm |
Alarm state. |
|
BERT state |
BERT test state on the E3 interface: · completed—The test has been completed. · stopped—The test has been manually terminated. · running—The test is running. |
|
Test pattern |
Test pattern in use: 2^20 or 2^15. |
|
Status |
Whether the interface is being synchronized. |
|
Sync Detected |
Number of detected synchronizations. |
|
Time |
Duration of the BERT test. |
|
Time past |
Time that has elapsed. |
|
Bit Errors (since test started) |
Number of bit errors received since the start of the BERT test. |
|
Bits Received (since test started) |
Number of bits received since the start of the BERT test. |
|
Bit Errors (since latest sync) |
Number of bit errors received since the last synchronization. |
|
Bits Received (since latest sync) |
Number of bits received since the last synchronization. |
|
E3 2/4/0 CE1 1 |
Physical state of the E1 channel: up or down. |
|
Frame-format |
Frame format configured on the E1 channel: ESF or SF. |
|
clock |
Clock source used by the E1 channel: master or slave. |
|
loopback |
Loopback setting on the E1 channel. |
|
Receiver alarm state |
Alarm state of received by the E1 channel, LOS, LOF, AIS, or RAI. |
|
BERT state |
BERT test state on the E1 channel: · completed—The test has been completed. · stopped—The test has been manually terminated. · running—The test is running. |
Related commands
reset counters controller e3
e1 bert
Use e1 bert to start a BERT test for an E1 channel created on a CE3 interface.
Use undo e1 bert to stop the BERT test running on an E1 channel created on a CE3 interface.
Syntax
e1 line-number bert pattern { 2^11 | 2^15 | 2^20 | 2^23 | qrss } time number [ unframed ]
undo e1 line-number bert
Default
No BERT test is performed.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 channel number in the range of 1 to 16.
pattern: Sets a BERT pattern.
· 2^11: Specifies the pattern length (in bits) as two to the eleventh power.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· 2^20: Specifies the pattern length (in bits) as two to the twentieth power.
· 2^23: Specifies the pattern length (in bits) as two to the twenty-third power.
· qrss: Specifies the pattern length (in bits) as two to the twentieth power. In this pattern, the maximum number of consecutive zeros is 14.
time number: Sets the duration (in minutes) of a BERT test. The number argument is in the range of 1 to 1440.
unframed: Sets the overhead bits of the padding frames for a BERT test.
Usage guidelines
E1 channels created on CE3 interfaces support the 2^11, 2^15, 2^20, 2^23, and QRSS BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of a BERT test running on an E1 channel created on a CE3 interface, use the display controller e3 command.
Examples
# Run a 10-minute QRSS BERT test on E1 channel 1 created on CE3 interface E3 2/4/0.
<Sysname> system-view
[Sysname] interface e3 2/4/0
[Sysname-E3 2/4/0] e1 1 bert pattern qrss time 10
Related commands
display controller e3
e1 channel-set
Use e1 channel-set to bundle timeslots into a channel set on an E1 line.
Use undo e1 channel-set to remove a timeslot bundle.
Syntax
e1 line-number channel-set set-number timeslot-list list
undo e1 line-number channel-set set-number
Default
No channel sets exist on an E1 line.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
set-number: Specifies the number of a channel set created by timeslot bundling on the E1 line, in the range of 0 to 30.
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 31.
Usage guidelines
A CE3 interface can be channelized into 64 kbps lines and the timeslots on each E1 line can be bundled into up to 31 channels.
When an E1 line operates in framed (CE1) mode, you can bundle timeslots on it into channel sets. For each channel set, the system automatically creates a serial interface named serial number/line-number:set-number. For example, the serial interface formed by channel set 0 on the first E1 line on E3 2/4/0 is numbered 2/4/0/1:0. This interface can operate at n × 64 kbps, where n is the number of bundled timeslots. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Create a 128 kbps serial interface on E1 channel 1 on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 channel-set 1 timeslot-list 1,2
Related commands
e1 unframed
e1 clock
Use e1 clock to set the clock mode for an E1 line on a CE3 interface.
Use undo e1 clock to restore the default.
Syntax
e1 line-number clock { master | slave }
undo e1 line-number clock
Default
The clock mode for an E1 line on a CE3 interface is slave.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of an E1 line is master, it uses the internal clock source. When the clock mode of an E1 line is slave, it uses the line clock source.
When the CE3 interface is operating in channelized mode, you can set a separate clock mode for each E1 line on it.
Examples
# Set the clock mode to slave for E1 line 1 on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 clock slave
e1 frame-format
Use e1 frame-format to set the framing format for an E1 line.
Use undo e1 frame-format to restore the default.
Syntax
e1 line-number frame-format { crc4 | no-crc4 }
undo e1 line-number frame-format
Default
The framing format for an E1 line is no-CRC4.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
crc4: Sets the frame format to CRC4.
no-crc4: Sets the frame format to no-CRC4.
Usage guidelines
Configure this command only when the specified E1 line is operating in framed mode. To set an E1 line to operate in framed mode, use the undo e1 unframed command.
Examples
# Set the framing format to CRC4 for E1 line 1 on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 frame-format crc4
Related commands
e1 unframed
e1 loopback
Use e1 loopback to enable a type of loopback on an E1 line.
Use undo e1 loopback to disable loopback on an E1 line.
Syntax
e1 line-number loopback { local | payload | remote }
undo e1 line-number loopback
Default
Loopback is disabled on E1 lines.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
local: Enables internal loopback.
payload: Enables external payload loopback.
remote: Enables external loopback.
Usage guidelines
Examples
# Enable internal loopback on E1 line 1 of E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 loopback local
e1 shutdown
Use e1 shutdown to shut down an E1 line on a CE3 interface.
Use undo e1 shutdown to restore the default.
Syntax
e1 line-number shutdown
undo e1 line-number shutdown
Default
E1 lines are up on a CE3 interface.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
Usage guidelines
Shutting down or bringing up an E1 line also shuts down or brings up the serial interface created for it.
Examples
# Shut down E1 line 1 on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 shutdown
e1 unframed
Use e1 unframed to set an E1 line on a CE3 interface to operate in unframed mode (E1 mode).
Use undo e1 unframed to restore the default.
Syntax
e1 line-number unframed
undo e1 line-number unframed
Default
An E1 line on a CE3 interface operates in framed mode (CE1 mode).
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies an E1 line number in the range of 1 to 16.
Usage guidelines
An E1 line in unframed mode does not contain the frame control information or support timeslot division. The system automatically creates a 2048 kbps serial interface named serial number/line-number:0 for it. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Set E1 line 1 on E3 2/4/0 to operate in unframed mode.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] e1 1 unframed
Related commands
e1 channel-set
fe3
Use fe3 to configure a CE3 interface to operate in FE3 mode and set the DSU mode or the subrate.
Use undo fe3 to restore the default.
Syntax
fe3 { dsu-mode { 0 | 1 } | subrate number }
undo fe3 { dsu-mode | subrate }
Default
DSU mode 1 (the Kentrox mode) is used, and the subrate is 34010 kbps.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
dsu-mode: Specifies the DSU mode.
|
Keyword |
DSU mode (vendor) |
Subrate range |
Total number of subrate grades |
|
0 |
Digital Link |
358 to 34010 kbps in steps of 358 kbps |
95 |
|
1 |
Kentrox |
500 to 24500 kbps in steps of 500 kbps 34010 kbps |
50 |
subrate number: Specifies a subrate for the CE3 interface. The value range for the number argument is 1 to 34010 kbps.
Usage guidelines
This command is applicable only to CE3 cards that support FE3.
This command is available only in E3 mode.
FE3 mode is a nonstandard E3 application mode. FE3 subrate ranges and the number of subrate grades vary by vendor. You can use the fe3 command to configure the device to be compatible with the FE3 DSU modes listed in Table 14.
After you set the subrate by using the fe3 subrate command, the CE3 interface searches the subrate levels corresponding to the DSU mode in which it is operating. The CE3 interface selects the subrate level that is closest to that set by the fe3 subrate command as its subrate. The device adjusts the hardware to allow for the subrate.
You can use the display interface serial interface-number:0 command to check the DSU mode setting, the subrate, the actual rate, and the baud rate of a CE3 interface. The actual rate does not include the overhead bits. The baud rate is the actual E3 line rate (34368 kbps), with the overhead bits counted in.
Examples
# Configure E3 2/4/0 to operate in FE3 mode. Set the DSU mode to 1 and the subrate to 3000 kbps.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] using e3
[Sysname-E3 2/4/0] fe3 dsu-mode 1
[Sysname-E3 2/4/0] fe3 subrate 3000
loopback
Use loopback to set the loopback mode of a CE3 interface.
Use undo loopback to disable loopback on a CE3 interface.
Syntax
loopback { local | payload | remote }
undo loopback
Default
Loopback is disabled on a CE3 interface.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
local: Enables internal loopback.
payload: Enables external payload loopback.
remote: Enables external loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
If a CE3 interface encapsulated with PPP is placed in a loopback, the state of the link layer protocol is reported as down.
Examples
# Enable internal loopback on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] loopback local
national-bit
Use national-bit to configure the national bit on a CE3 interface.
Use undo national-bit to restore the default.
Syntax
national-bit { 0 | 1 }
undo national-bit
Default
The national bit on a CE3 interface is 1.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
0: Sets the national bit to 0 for national communication.
1: Sets the national bit to 1 for international communication.
Examples
# Set the national bit to 0 on E3 2/4/0.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] national-bit 0
reset counters controller e3
Use reset counters controller e3 to clear CE3 interface statistics.
Syntax
reset counters controller e3 interface-number
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CE3 interface by its number. If you do not specify this argument, the command clears statistics for all CE3 interfaces.
Usage guidelines
The reset counters interface command clears statistics for all interfaces.
To display CE3 interface statistics, use the display controller e3 command.
Examples
# Clear statistics for the CE3 interface E3 2/4/0.
<Sysname> reset counters controller e3 2/4/0
Related commands
display controller e3
using
Use using to configure the operating mode of a CE3 interface.
Use undo using to restore the default.
Syntax
undo using
Default
A CE3 interface operates in channelized mode.
Views
CE3 interface view
Predefined user roles
network-admin
Parameters
ce3: Sets the CE3 interface to operate in channelized (CE3) mode.
e3: Sets the CE3 interface to operate in unchannelized (E3) mode.
Usage guidelines
You can configure E1 lines only when the CE3 interface is operating in channelized mode.
When the CE3 interface is operating in unchannelized mode, the system automatically creates a 34.368 Mbps serial interface named serial number/0:0 for it. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Configure E3 2/4/0 to operate in unchannelized mode.
<Sysname> system-view
[Sysname] controller e3 2/4/0
[Sysname-E3 2/4/0] using e3
CT3 interface commands
alarm
Use alarm to enable a CT3 interface to detect/send alarm signals.
Use undo alarm to remove the alarm signal detection/sending setting.
Syntax
alarm { detect | generate { ais | febe | idle | rai } }
undo alarm { detect | generate { ais | febe | idle | rai } }
Default
Periodic alarm detection is enabled.
Default
Alarm signal sending is disabled.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
detect: Enables periodical alarm signal detection.
generate: Sends alarm signals for line state test.
· ais: Alarm indication signal.
· febe: Far end block error signal.
· idle: Idle signal.
· rai: Remote alarm indication signal.
Usage guidelines
At startup, periodical alarm signal detection is enabled on the CT3 interface. When the interface detects LOS, LOF, or AIS signals, it sends RAI signals to its peer.
The supported alarm signals (LOS, LOF, AIS, RAI, FEBE, and idle) are ANSI T1.107-1995 compliant.
You can configure the CT3 interface to send a type of alarm signal. To send another type of signal, you must first remove the previous setting by using the undo alarm command. If a RAI signal is present because an LOS, LOF, or AIS alarm is detected, you must first use the undo alarm detect command to remove the signal.
To display the real-time alarm state on the CT3 interface, use the display controller t3 command.
Examples
# Enable periodical alarm signal detection on CT3 interface T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] alarm detect
# Enable CT3 interface T3 2/4/0 to send AIS alarm signals.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] alarm generate ais
Related commands
display controller t3
bert
Use bert to start a BERT test on a CT3 interface.
Use undo bert to stop the BERT test running on a CT3 interface.
Syntax
bert pattern { 2^7 | 2^11 | 2^15 | qrss } time number [ unframed ]
undo bert
Default
No BERT test is performed on a CT3 interface.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
pattern: Sets a BERT pattern.
· 2^7: Specifies the pattern length (in bits) as two to the seventh power.
· 2^11: Specifies the pattern length (in bits) as two to the eleventh power.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· qrss: Specifies the pattern length (in bits) as two to the twentieth power. In this pattern, the maximum number of consecutive zeros is 14.
time number: Sets the duration of a BERT test, in the range of 1 to 1440 minutes.
unframed: Sets the test pattern to cover the overhead bits of the frame.
Usage guidelines
The CT3 interface supports the 2^7, 2^11, 2^15, and QRSS BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of the BERT test, use the display controller t3 command.
Examples
# Run a 10-minute QRSS BERT test on CT3 interface T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] bert pattern qrss time 10
cable
Use cable to configure the cable length on a CT3 interface.
Use undo cable to restore the default.
Syntax
cable feet
undo cable
Default
The cable length on a CT3 interface is 49 feet (14.9 meters).
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
feet: Cable length in the range of 0 to 450 feet (0 to 137.2 meters).
Usage guidelines
The cable length in this command refers to the distance between the router and the cable distribution rack.
Examples
# Set the cable length to 50 feet (15.24 meters) on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] cable 50
clock
Use clock to set the clock mode of a CT3 interface.
Use undo clock to restore the default.
Syntax
clock { master | slave }
undo clock
Default
The clock mode for a CT3 interface is slave.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of a CT3 interface is master, it uses the internal clock source. When the clock mode of a CT3 interface is slave, it uses the line clock source.
When connected to a transmission device, the CT3 interface must use the slave clock. The clock provided by the transmission device is more precise.
When two CT3 interfaces are directly connected, you must configure the two ends with different clock modes.
Examples
# Set the clock mode to master for T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] clock master
controller t3
Use controller t3 to enter CT3 interface view.
Syntax
controller t3 interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CT3 interface by its number.
Examples
# Enter the view of T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0]
display controller t3
Use display controller t3 to display information about CT3 interfaces.
Syntax
display controller [ t3 [ interface-number ] [ t1 line-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
t3 [ interface-number ]: Specifies a CT3 interface by its number. If you do not specify the t3 keyword, the command displays information about all CT3 interfaces, CPOS interfaces, CT1/PRI interfaces, CE1/PRI interfaces, and CE3 interfaces. If you specify the t3 keyword without specifying an interface, the command displays information about all CT3 interfaces.
t1 line-number: Specifies a T1 line by its number.
Usage guidelines
In addition to the state information about the CT3 interface, the command displays information about each T1 line on the CT3 interface if the interface is operating in CT3 mode.
Examples
# Display information about T3 2/4/0.
<Sysname> display controller t3 2/4/0
T3 2/4/0
Current state: UP
Description: T3 2/4/0 Interface
Last clearing of counters: Never
Current system time:2017-11-11 17:25:32
Last time when physical state changed to up:2017-11-11 17:25:26
Last time when physical state changed to down:2017-11-11 09:59:32
Basic Configuration:
Work mode: CT3, cable length: 49 feet
Frame-format: C-BIT Parity, line code: B3ZS
Source clock: slave, loopback: not set
Alarm state:
Receiver alarm state is none
MDL state:
No message is sent now.
Message data elements:
EIC: line, LIC: line, FIC: line, UNIT: line
PFI: line, PORT_NO: line, GEN_NO: line
Periodical detection: disabled
FEAC state:
No code is sent now.
Periodical detection is enabled, no code received now.
BERT state:(stopped, not completed)
Test pattern: 2^7, Status: Not Sync, Sync Detected: 0
Time: 0 minutes, Time past: 0 minutes
Bit errors (since test started): 0 bits
Bits received (since test started): 0 Mbits
Bit errors (since latest sync): 0 bits
Bits received (since latest sync): 0 Mbits
Historical Statistics:
Last link flapping: 6 hours 39 minutes 25 seconds
Data in current interval (22 seconds elapsed):
Line Code Violations: 0 seconds Far End Block Error: 0 seconds
C-Bit Coding Violation: 0 seconds
P-bit Coding Violation: 0 seconds
Framing Bit Err: 0 seconds, Severely Err Framing: 0 seconds
C-bit Err: 0 seconds, C-bit Severely Err: 0 seconds
P-bit Err: 0 seconds, P-bit Severely Err: 0 seconds
Unavailable: 0 seconds, Line Err: 0 seconds
T3 2/4/0 CT1 1: up
Frame-format: ESF, clock: slave, loopback: not set
FDL Performance Report: disabled
Transmitter is sending none
Receiver alarm state is none
Line loop back deactivate code using inband signal last sent
BERT state:(stopped, not completed)
Test pattern: 2^11, Status: Not Sync, Sync Detected: 0
Time: 0 minutes, Time past: 0 minutes
Bit errors (since test started): 0 bits
Bits received (since test started): 0 Kbits
Bit errors (since latest sync): 0 bits
Bits received (since latest sync): 0 Kbits
Table 15 Command output
|
Field |
Description |
|
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
|
Description |
Description of the interface. |
|
Last clearing of counters |
The most recent time that the reset counters controller t3 command was executed. This field displays Never if this command has not been executed since the device startup. |
|
Basic Configuration |
Basic configurations of the interface. |
|
Work mode |
Operating mode of the interface: CT3 or T3. |
|
cable length |
Cable length supported by the interface. |
|
Frame-format |
Frame format: C-bit parity or M23. |
|
Source clock |
Clock source used by the interface: master or slave. |
|
loopback |
Loopback setting on the interface: local, remote, payload, or not set. |
|
Receiver alarm state is none |
Type of the received alarm: none, LOS, LOF, RAI, or AIS. If the interface receives a LOS, LOF, or AIS alarm and sends out an RAI alarm, Transmitter is sending RAI is displayed. |
|
No message is sent now. |
No MDL message is being sent. If an MDL message, path or idle-signal for example, is being sent, Message sent now: path. idle signal is displayed. |
|
Message data elements |
MDL data elements. |
|
EIC: line, LIC: line, FIC: line, UNIT: line |
EIC, LIC, FIC, and UNIT are four elements present in all types of MDL messages. Their values are user configurable and default to line. |
|
PFI: line, PORT_NO: line, GEN_NO: line |
FI is contained in MDL path messages, PORT_NO in MDL idle signal messages, and GEN_NO in MDL test signal messages. Their values are user configurable and default to line. |
|
Periodical detection |
State of periodical detection of MDL. Periodical MDL message detection is disabled by default at the startup of the router. When this function is enabled, Periodical detection is enabled is displayed. When MDL messages are detected, information about detected MDL messages is displayed. |
|
No code is sent now. DS3 Line Loop Back Deactivate was last sent. |
No FEAC signal is sent. The FEAC signal sent last time is DS3 Line Loop Back Deactivate. |
|
Periodical detection is enabled, no code received now. |
Periodical detection of FEAC is enabled and no FEAC signal is received now. Periodical FEAC signal detection is enabled by default at the startup of the router. |
|
DS3 Line Loop Back Deactivate last received. |
The FEAC signal received last time is DS3 Line Loop Back Deactivate. |
|
BERT state:(stopped, not completed) |
BERT state: completed, stopped (not completed), or running. |
|
Test pattern: 2^7, Status: Not Sync, Sync Detected: 0 |
Test pattern in use (such as 2^7, 2^11, 2^15, and QRSS), 2^7 in this sample output; synchronization state, and the number of detected synchronizations. |
|
Time |
Duration of the BERT test. |
|
Time past |
Time that has elapsed. |
|
Bit errors (since test started) |
Number of bit errors received since the start of the BERT test. |
|
Bits received (since test started) |
Number of bits received since the start of the BERT test. |
|
Bit errors (since latest sync) |
Number of bit errors received since the last synchronization. |
|
Bits received (since latest sync) |
Number of bits received since the last synchronization. |
|
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
Data in current interval (22 seconds elapsed): |
Statistics spanning the current 15-minute interval. |
|
Line Code Violations |
Line code violations: BPV, or EXZ. |
|
Far End Block Error |
Far-end block error. |
|
C-Bit Coding violation |
C-bit coding violation. |
|
P-bit Coding Violation |
P-bit coding violation. |
|
Framing Bit Err |
Framing bit error. |
|
Severely Err Framing Secs |
Severely erroneous second. |
|
C-bit Err Secs |
C-bit erroneous second. |
|
C-bit Severely Err Secs |
C-bit severely erroneous second. |
|
P-bit Err Secs |
P-bit erroneous second. |
|
P-bit Severely Err Secs |
P-bit severely erroneous second. |
|
Unavailable Secs |
Service unavailable second. |
|
Line Err Secs |
Line erroneous second, during which LOS, BPV, EXZ, C-bit, P-bit, and other errors occur. |
|
Data in Interval 1: |
Statistics spanning interval 1. |
|
Total Data (last 17 15 minute intervals) |
Total data spanning the last 17 intervals. |
|
T3 2/4/0 CT1 1 is up |
State of T1 line on the CT3 interface: up or down. In this output sample, T1 line 1 is up. |
|
Frame-format ESF, clock slave, loopback not set |
Information about the T1 line: · Framing format—ESF or SF. · Clock source—Slave for the line clock and master for the internal clock. · Loopback—Local, remote, payload, or not set. |
|
FDL Performance Report is disabled |
Transmission of PPR in the FDL is disabled. You can enable it by using the t1 set fdl ansi command. |
|
Transmitter is sending RAI |
The transmitter of the T1 line is sending RAI signals. When the T1 line receives LOS, LOF, or AIS signals, it sends RAI signals. |
|
Receiver alarm state is LOF |
Type of alarm signal that the T1 line can receive: LOS, LOF, AIS, or RAI. |
|
Line loop back activate code using inband signal last sent |
The loopback code sent last time is in-band LLB activation request code. |
Related commands
reset counters controller t3
feac
Use feac to enable far end and control signal (FEAC) channel signal detection and transmission on a CT3 interface.
Use undo feac to remove the current FEAC settings.
Syntax
feac { detect | generate { ds3-los | ds3-ais | ds3-oof | ds3-idle | ds3-eqptfail | loopback { ds3-line | ds3-payload } } }
undo feac { detect | generate { ds3-los | ds3-ais | ds3-oof | ds3-idle | ds3-eqptfail | loopback { ds3-line | ds3-payload } } }
Default
On a CT3 interface, periodical FEAC channel signal detection is enabled, and FEAC signal transmission is disabled.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
detect: Enables periodical FEAC channel signal detection.
generate: Generates a specific type of FEAC signal.
· ds3-los: Specifies the DS3 LOS signal.
· ds3-ais: Specifies the DS3 AIS signal.
· ds3-oof: Specifies the DS3 OOF signal.
· ds3-idle: Specifies the DS3 idle signal.
· ds3-eqptfail: Specifies DS3 equipment failure signal.
loopback: Sends a specific type of loopback code for activating a specific loopback.
· ds3-line: Specifies far-end line loopback.
· ds3-payload: Specifies payload loopback.
Usage guidelines
FEAC is a channel formed by using the third C-bit in the first subframe in C-bit framing. The channel is used for the following purposes:
· Transmits alarm state signals for line test.
· Transmits loopback control code to activate or deactivate far-end loopback during a loopback test.
According to ANSI T1.107a, the framing format of FEAC channels is bit-oriented protocol (BOP).
After far-end loopback is activated by using the feac generate loopback { ds3-line | ds3-payload } command, you can remove it by using the undo form of the command.
Before you configure far-end loopback by using this command, disable FEAC detection on the local end to prevent loopback deadlock. Loopback deadlock occurs when the local end enables loopback after detecting the loopback code sent back by the far end.
To display the transmitting and receiving state of the FEAC channel, use the display controller t3 command.
Examples
# Enable FEAC channel signal detection on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] feac detect
# Send DS3 LOS signal on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] feac generate ds3-los
# On T3 2/4/0, send loopback code to the far end to place the far end in a line loopback.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] feac generate loopback ds3-line
Related commands
display controller t3
frame-format
Use frame-format to set the framing format for a CT3 interface.
Use undo frame-format to restore the default.
Syntax
frame-format { c-bit | m23 }
undo frame-format
Default
The framing format for a CT3 interface is C-bit.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
c-bit: Sets the framing format to C-bit.
m23: Sets the framing format to m23.
Usage guidelines
This command is available only in channelized mode.
Examples
# Set the framing format to m23 for T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] frame-format m23
Related commands
using
ft3
Use ft3 to configure a CT3 interface to operate in FT3 mode and set the DSU mode or the subrate, or enable payload scrambling for the interface.
Use undo ft3 to restore the default.
Syntax
ft3 { dsu-mode { 0 | 1 | 2 | 3 | 4 } | subrate number | scramble }
undo ft3 { dsu-mode | subrate | scramble }
Default
DSU mode 0 (the Digital Link mode) is used, and the subrate is 44210 kbps. Payload scrambling is disabled.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
dsu-mode: Specifies the DSU mode.
|
Keyword |
DSU mode (vendor) |
Subrate range |
Total number of subrate grades |
|
0 |
Digital Link |
300 to 44210 kbps in steps of 300746 bps |
147 |
|
1 |
Kentrox |
1500 to 35000 kbps in steps of 500000 bps 44210 kbps |
69 |
|
2 |
Larscom |
3100 to 44210 kbps in steps of 3157835 bps |
14 |
|
3 |
Adtran |
75 to 44210 kbps in steps of 75187 bps |
588 |
|
4 |
Verilink |
1500 to 44210 kbps in steps of 1578918 bps |
20 |
subrate number: Specifies the subrate for the CT3 interface. The number argument is in the range of 1 to 44210 (in kbps).
scramble: Enables payload scrambling for the CT3 interface.
Usage guidelines
This command is applicable only to CT3 cards that support FT3.
This command is available only in T3 mode.
FT3 (Fractional T3 or Subrate T3) mode is a nonstandard E3 application mode. FE3 subrate ranges and the number of subrate grades vary by vendor. You can use the ft3 command to configure the device to be compatible with the FE3 DSU modes listed in Table 16.
After you set the subrate by using the ft3 subrate command, the T3 interface searches the subrate levels corresponding to the DSU mode in which it is operating. The T3 interface selects the subrate level that is closest to subrate level set by the ft3 subrate command. The device adjusts the hardware to allow for the subrate.
Use the ft3 scramble command to enable payload scrambling for the interface. Payload scrambling improves line quality by preventing the presence of long strings of all 1s or all 0s.
You can use the display interface serial interface-number:0 command to check the following settings of a CT3 interface:
· DSU mode.
· Subrate.
· Actual rate.
The actual rate does not count in the overhead bits.
· Baud rate.
The baud rate is the actual T3 line rate (44736 kbps), with the overhead bits counted in.
· Payload scrambling setting.
Examples
# Configure T3 2/4/0 to operate in the FT3 mode. Set the DSU mode to 1 and the subrate to 3000 kbps. Enable payload scrambling for the interface.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] using t3
[Sysname-T3 2/4/0] ft3 dsu-mode 1
[Sysname-T3 2/4/0] ft3 subrate 3000
[Sysname-T3 2/4/0] ft3 scramble
loopback
Use loopback to enable a type of loopback on a CT3 interface.
Use undo loopback to disable loopback on a CT3 interface.
Syntax
loopback { local | payload | remote }
undo loopback
Default
Loopback is disabled on CT3 interfaces.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
local: Enables internal loopback.
payload: Enables external payload loopback.
remote: Enables external loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
If a CT3 interface encapsulated with PPP or HDLC is placed in a loopback, the state of the link layer protocol is reported as down.
Examples
# Enable internal loopback on interface T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] loopback local
mdl
Use mdl to configure MDL message detection and transmission on a CT3 interface.
Use undo mdl to restore the default.
Syntax
mdl { data { eic string | fic string | gen-no string | lic string | pfi string | port-no string | unit string } | detect | generate { idle-signal | path | test-signal } }
undo mdl [ data [ eic | fic | gen-no | lic | pfi | port-no | unit ] | detect | generate [ idle-signal | path | test-signal ] ]
Default
Periodic MDL detection is disabled. CT3 interfaces do not send MDL messages.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
data: Sets MDL message parameters. If you do not specify a parameter, a default string of line is set in the MDL messages.
· eic string: Specifies the equipment identification code, a string of 1 to 10 characters. This parameter is contained in all three types of MDL messages.
· fic string: Specifies the frame identification code, a string of 1 to 10 characters. This parameter is contained in all three types of MDL messages.
· gen-no string: Specifies the generator number, a string of 1 to 38 characters. This parameter is specific to test signal messages.
· lic string: Specifies the location identification code, a string of 1 to 11 characters. This parameter is contained in all three types of MDL messages.
· pfi string: Specifies the path facility identification, a string of 1 to 38 characters. This parameter is specific to path messages.
· port-no string: Specifies the port number in idle signal message, a string of 1 to 38 characters. This parameter is specific to idle signal messages.
· unit string: Specifies the unit, a string of 1 to 6 characters. This parameter is contained in all three types of MDL messages.
detect: Enables periodical MDL message detection.
generate: Sends a specific type of MDL message.
· idle-signal: Specifies MDL idle signal messages.
· path: Specifies MDL path messages.
· test-signal: Specifies MDL test signal messages.
Usage guidelines
MDL is a channel formed by using the three C-bits in the fifth subframe in C-bit framing. According to ANSI T1.107a, MDL can transmit path, idle signal, and test signal messages. The data framing format is LAPD for MDL messages.
To send idle signal, path, and test signal messages simultaneously, repeat the mdl command to specify the idle-signal, path, and test-signal keywords.
To display the receiving and transmission status of the MDL link, use the display controller t3 command.
Examples
# Enable MDL detection on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] mdl detect
# Set LIC to hello for CT3 interface T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] mdl data lic hello
# Send path messages on CT3 interface T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] mdl generate path
Related commands
display controller t3
reset counters controller t3
Use reset counters controller t3 to clear CT3 interface statistics.
Syntax
reset counters controller t3 [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a CT3 interface by its number. If you do not specify this argument, the command clears statistics for all CT3 interfaces.
Usage guidelines
The reset counters interface command clears statistics for all interfaces.
To display CT3 interface statistics, use the display controller t3 command.
Examples
# Clear statistics for T3 2/4/0.
<Sysname> reset counters controller t3 2/4/0
Related commands
display controller t3
t1 alarm
Use t1 alarm to enable a T1 line on a CT3 interface to detect/send alarm signals.
Use undo t1 alarm to remove the alarm signal detection/sending setting.
Syntax
t1 line-number alarm { detect | generate { ais | rai } }
undo t1 line-number alarm { detect | generate { ais | rai } }
Default
On a CT3 interface, periodical alarm detection is enabled, and alarm signal sending is disabled.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
detect: Specifies periodical alarm signal detection.
generate: Sends a specific type of alarm signals. These alarm signals are used for line status test.
· ais: Alarm indication signal.
· rai: Remote alarm indication signal.
Usage guidelines
At startup, periodical alarm signal detection is enabled on all T1 lines on the CT3 interface. When a T1 line detects LOS, LOF, or AIS signals, it sends RAI signals to its peer.
The supported alarm signals (LOS, LOF, AIS, RAI, FEBE, and idle) are ANSI T1.403 compliant.
Only one type of alarm signal can be sent on a T1 line at a time. To send another type of signal, you must first remove the previous setting by using the undo t1 alarm command. If a RAI signal is present because an LOS, LOF, or AIS alarm is detected, you must first use the undo t1 alarm detect command to remove the signal.
To display the real-time alarm state on T1 lines, use the display controller t3 command.
Examples
# Enable periodical alarm signal detection on T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 alarm detect
# Enable T1 line 1 on T3 2/4/0 to send AIS alarm signals.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 alarm generate ais
Related commands
display controller t3
t1 bert
Use t1 bert to start a BERT test on a T1 line on a CT3 interface.
Use undo t1 bert to stop the BERT test running on a T1 line on a CT3 interface.
Syntax
t1 line-number bert pattern { 2^11 | 2^15 | 2^20 | 2^23 | qrss } time number [ unframed ]
undo t1 line-number bert
Default
No BERT test is performed.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
pattern: Sets a BERT pattern.
· 2^11: Specifies the pattern length (in bits) as two to the eleventh power.
· 2^15: Specifies the pattern length (in bits) as two to the fifteenth power.
· 2^20: Specifies the pattern length (in bits) as two to the twentieth power.
· 2^23: Specifies the pattern length (in bits) as two to the twenty-third power.
· qrss: Specifies the pattern length (in bits) as two to the twentieth power. In this pattern, the maximum number of consecutive zeros is 14.
time number: Sets the duration of a BERT test, in the range of 1 to 1440 minutes.
unframed: Sets the test pattern to cover the overhead bits of the frame.
Usage guidelines
T1 lines on CT3 interfaces support the 2^11, 2^15, 2^20, 2^23, and QRSS BERT patterns defined in ITU O.151, ITU O.153, and ANSI T1.403-1999.
To perform a BERT test, the local end sends out a pattern. The pattern is looped over on the line and sent back to the local end. The local end examines the received pattern for bit error rate to help determine the line condition. You must configure loopback to allow the transmitted pattern to loop back from a point on the line. For example, enable far-end loopback on the remote interface.
To display the state and result of the BERT test, use the display controller t3 command.
Examples
# Run a 10-minute QRSS BERT test on T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 bert pattern qrss time 10
Related commands
display controller t3
t1 channel-set
Use t1 channel-set to bundle timeslots into a channel set on a T1 line.
Use undo t1 channel-set to remove a channel set.
Syntax
t1 line-number channel-set set-number timeslot-list list [ speed { 56k | 64k } ]
undo t1 line-number channel-set set-number
Default
No channel sets exist on a T1 line.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
set-number: Specifies the number of a channel set created by timeslot bundling on a T1 line, in the range of 0 to 23.
timeslot-list list: Specifies a comma-separated list of timeslot items. An item can be an individual timeslot or a timeslot range. Use a hyphen (-) to separate the start and end timeslot numbers of a range. The value range for the timeslot number is 1 to 24.
speed { 56k | 64k }: Speed of the timeslot bundle (the channel set) in kbps. If 56k is selected, the timeslots are bundled into an n × 56 kbps bundle. If 64k, the default, is selected, the timeslots are bundled into an n × 64 kbps bundle.
Usage guidelines
When a T1 line is operating in framed (CT1) mode, you can bundle timeslots on it. For each channel set, the system automatically creates a serial interface named serial number/line-number:set-number. This interface operates at n × 64 kbps or n × 56 kbps, where n is the number of bundled timeslots. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Create a 128 kbps serial interface through timeslot bundling on T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 channel-set 1 timeslot-list 1,2
Related commands
t1 unframed
t1 clock
Use t1 clock to set the clock mode of a T1 line on a CT3 interface.
Use undo t1 clock to restore the default.
Syntax
t1 line-number clock { master | slave }
undo t1 line-number clock
Default
The clock mode of a T1 line on a CT3 interface is slave.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
master: Sets the clock mode to master.
slave: Sets the clock mode to slave.
Usage guidelines
When the clock mode of a T1 line is master, it uses the internal clock source. When the clock mode of a T1 line is slave, it uses the line clock source.
When a CT3 interface is operating in channelized mode, its T1 lines might use separate clocks.
Examples
# Set the clock mode to slave for T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 clock slave
t1 fdl
Use t1 fdl to set the behavior of a T1 line on the FDL in ESF framing.
Use undo t1 fdl to disable FDL of T1.
Syntax
t1 line-number fdl { ansi | att | both | none}
undo t1 line-number fdl
Default
FDL is disabled in ESF framing.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
ansi: Specifies ANSI T1.403 for FDL.
att: Specifies AT&T TR 54016 for FDL.
both: Specifies both ANSI T1.403 and AT&T TR 54016 for FDL.
none: Disables the use of FDL on the T1 line.
Usage guidelines
FDL is an embedded 4 kbps overhead channel within the ESF format for transmitting periodical performance report (PPR) statistics or loopback code.
According to ANSI T1.403, the format of PPR is LAPD, and the format of loopback code is BOP.
The t1 set fdl command only starts PPR transmission. It cannot enable loopback code transmission or detection.
This command only applies to channelized T1 lines with a T1 frame format of ESF.
Examples
# Set the FDL to be ANSI T1.403 compliant for T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 fdl ansi
Related commands
t1 frame-format
t1 frame-format
Use t1 frame-format to set the framing format for a T1 line.
Use undo t1 frame-format to restore the default.
Syntax
t1 line-number frame-format { esf | sf }
undo t1 line-number frame-format
Default
The framing format of a T1 line is ESF.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
esf: Sets the T1 line to use the ESF format.
sf: Sets the T1 line to use the SF format.
Usage guidelines
You can configure this command only when the T1 line is operating in framed mode. To configure a T1 line to operate in framed mode, use the undo t1 unframed command.
Examples
# Set the framing format to SF for T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 frame-format sf
Related commands
t1 unframed
t1 loopback
Use t1 loopback to enable a type of loopback for a T1 line on a CT3 interface.
Use undo t1 loopback to disable loopback for a T1 line on a CT3 interface.
Syntax
t1 line-number loopback { local | payload | remote }
undo t1 line-number loopback
Default
Loopback is disabled on T1 lines.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
local: Enables internal loopback.
payload: Enables payload loopback mode.
remote: Enables external loopback.
Usage guidelines
Loopback is intended for testing only. Disable the feature when the interface is operating correctly.
If a T1 line encapsulated with PPP or HDLC is in loopback mode, the state of the link layer protocol is reported as down.
Examples
# Enable internal loopback on T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 loopback local
t1 sendloopcode
Use t1 sendloopcode to set the loopback mode of a far-end T1 line.
Use undo t1 sendloopcode to remove the corresponding setting.
Syntax
t1 line-number sendloopcode { fdl-ansi-line-up | fdl-ansi-payload-up | fdl-att-payload-up | inband-line-up }
undo t1 line-number sendloopcode { fdl-ansi-line-up | fdl-ansi-payload-up | fdl-att-payload-up | inband-line-up }
Default
No loopback mode is set.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number, in the range of 1 to 28.
fdl-ansi-line-up: Sends ANSI-compliant LLB activation request code in the FDL to start remote loopback.
fdl-ansi-payload-up: Sends ANSI-compliant PLB activation request code in the FDL to start remote loopback.
fdl-att-payload-up: Sends AT&T-compliant PLB activation request code in the FDL to start remote loopback.
inband-line-up: Sends in-band LLB activation request code compliant with the ANSI and AT&T implementation to start remote loopback.
Usage guidelines
Loopback is an effective method of diagnosis. You can place a far-end device into loopback mode either at the command line on it or by sending loopback control code to it. The types and formats of loopback control code supported on T1 interfaces are compliant with ANSI T1.403.
Loopback can be divided into line loopback and payload loopback. The data stream is looped back at the framer only in the line loopback.
You can transmit loopback control code by using the in-band signal (the 192 effective bandwidth bits or all 193 bits of T1) or the FDL in ESF frames.
Examples
# Send the in-band signal on T1 line 1 on T3 2/4/0 to place the far-end T1 line in line loopback mode.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 sendloopcode inband-line-up
t1 show
Use t1 show to have a quick look at the line state of a T1 line on a CT3 interface.
Syntax
t1 line-number show
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
show: Displays the physical line state of the specified T1 line.
Examples
# Display line state of T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 show
T3 2/4/0 CT1 1: up
Frame-format: ESF, clock: slave, loopback: not set
FDL Performance Report: disabled
Transmitter is sending RAI
Receiver alarm state is LOF
Line loop back activate code using inband signal last sent
BERT state:(stopped, not completed)
Test pattern: 2^11, Status: Not Sync, Sync Detected: 0
Time: 0 minutes, Time past: 0 minutes
Bit errors (since test started): 0 bits
Bits received (since test started): 0 Kbits
Bit errors (since latest sync): 0 bits
Bits received (since latest sync): 0 Kbits
Table 17 Command output
|
Field |
Description |
|
T3 2/4/0 CT1 1 is up |
State of T1 line 1 on the CT3 interface: up or down. |
|
Frame-format |
Framing format of T1: ESF or SF. |
|
clock |
Clock source used by the T1 line: master or slave. |
|
loopback |
Loopback state or mode: local, remote, payload, or not set. |
|
FDL Performance Report is disabled |
Transmission of PPR in the FDL is disabled. You can enable it by using the t1 set fdl ansi command. |
|
Transmitter is sending RAI |
The transmitter of the T1 line is sending RAI signals. When the T1 line receives LOS, LOF, or AIS signals, it sends RAI signals. |
|
Receiver alarm state is LOF |
Type of alarm signal that the T1 line can receive: LOS, LOF, AIS, or RAI. |
|
Line loop back activate code using inband signal last sent |
The loopback code sent last time is in-band LLB activation request code. |
|
BERT state |
BERT test state: running, complete, or stopped (not completed). |
|
Test pattern |
Test pattern in use. |
|
Status |
Synchronization state. |
|
Sync Detected |
Number of detected synchronizations. |
|
Time |
Duration of the BERT test. |
|
Time past |
Time that has elapsed. |
|
Bit errors (since test started) |
Number of bit errors received since the start of the BERT test. |
|
Bits received (since test started) |
Number of bits received since the start of the BERT test. |
|
Bit errors (since latest sync) |
Number of bit errors received since the last synchronization. |
|
Bits received (since latest sync) |
Number of bits received since the last synchronization. |
t1 shutdown
Use t1 shutdown to shut down a T1 line on a CT3 interface.
Use undo t1 shutdown to bring up a T1 line.
Syntax
t1 line-number shutdown
undo t1 line-number shutdown
Default
T1 lines on a CT3 interface are up.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
Usage guidelines
Shutting down or bringing up a T1 line also shuts down or brings up the serial interface created for it.
Examples
# Shut down T1 line 1 on T3 2/4/0.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 shutdown
t1 unframed
Use t1 unframed to set a T1 line on a CT3 interface to operate in unframed mode (T1 mode).
Use undo t1 unframed to set a T1 line on a CT3 interface to operate in framed mode (CT1 mode).
Syntax
t1 line-number unframed
undo t1 line-number unframed
Default
T1 lines on a CT3 interface are operating in framed mode.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
line-number: Specifies a T1 line number in the range of 1 to 28.
Usage guidelines
A T1 line in unframed mode does not contain frame control information or support timeslot division. The system automatically creates a 1544 kbps serial interface named serial number/line-number:0. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Set T1 line 1 on T3 2/4/0 to operate in unframed mode.
<Sysname> system-view
[Sysname] controller t3 2/4/0
[Sysname-T3 2/4/0] t1 1 unframed
Related commands
t1 channel-set
using
Use using to configure the operating mode of a CT3 interface.
Use undo using to restore the default.
Syntax
using { ct3 | t3 }
undo using
Default
A CT3 interface operates in channelized mode.
Views
CT3 interface view
Predefined user roles
network-admin
Parameters
ct3: Sets the CT3 interface to operate in channelized mode.
t3: Sets the CT3 interface to operate in unchannelized mode.
Usage guidelines
You can only configure T1 lines on CT3 interfaces in channelized mode.
When a CT3 interface operates in unchannelized mode, the system automatically creates a 44.736 Mbps serial interface named serial number/0:0 for it. This interface has the same logical features as a standard synchronous serial interface. You can configure this serial interface in the same way you configure a standard synchronous serial interface.
Examples
# Configure T3 2/4/0 to operate in unchannelized mode.
<Sysname> system-view
[Sysname] controller t3 2/4/0
