HP MSR Router Series. Interface Configuration Guide(V7) Part number: b Software version: CMW710-R0304 Document version: 6PW

Transcription

1 HP MSR Router Series Interface Configuration Guide(V7) Part number: b Software version: CMW710-R0304 Document version: 6PW

2 Legal and notice information Copyright 2015 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. i

3 Contents Bulk configuring interfaces 1 Configuration restrictions and guidelines 1 Configuration procedure 2 Displaying and maintaining bulk interface configuration 2 Configuring Ethernet interfaces 3 Command and hardware compatibility 3 Configuring common Ethernet interface settings 3 Configuring a combo interface (single combo interface) 3 Configuring basic settings of an Ethernet interface or subinterface 4 Configuring the link mode of an Ethernet interface 6 Configuring jumbo frame support 6 Configuring dampening on an Ethernet interface 7 Performing a loopback test on an Ethernet interface 9 Configuring generic flow control on an Ethernet interface 9 Setting the statistics polling interval 10 Configuring a Layer 2 Ethernet interface 10 Configuring storm suppression 10 Setting the MDIX mode of an Ethernet interface 11 Configuring a Layer 3 Ethernet interface or subinterface 12 Setting the MTU for an Ethernet interface or subinterface 12 Setting the MAC address of an Ethernet interface 12 Displaying and maintaining an Ethernet interface or subinterface 13 Configuring WAN interfaces 14 Configuring a serial interface 14 Asynchronous serial interface 14 Synchronous serial interface 14 Configuring an asynchronous serial interface 15 Configuring a synchronous serial interface 16 Configuring a subinterface 17 Displaying and maintaining serial interfaces 17 Configuring an AM interface 18 Configuration procedure 18 Displaying and maintaining AM interfaces 19 Configuring an FCM interface 20 Feature and hardware compatibility 20 Configuration procedure 20 Displaying and maintaining FCM interfaces 21 Configuring an ISDN BRI interface 21 Configuration prerequisites 22 Configuration procedure 22 Displaying and maintaining ISDN BRI interfaces 23 Configuring a CE1/PRI interface 23 Configuring a CE1/PRI interface in E1 mode 25 Configuring a CE1/PRI interface in CE1 mode 25 Configuring a CE1/PRI interface in PRI mode 26 Configuring other CE1/PRI interface parameters 26 Displaying and maintaining CE1/PRI interfaces 27 Configuring a CT1/PRI interface 27 i

4 Configuring a CT1/PRI interface in CT1 mode 28 Configuring a CT1/PRI interface in PRI mode 28 Configuring other CT1/PRI interface parameters 29 Starting a BERT test on a CT1/PRI interface 30 Displaying and maintaining CT1/PRI interfaces 30 Configuring an E1-F interface 31 Configuring an E1-F interface in framed mode 31 Configuring an E1-F interface in unframed mode 32 Configuring other E1-F interface parameters 32 Displaying and maintaining E1-F interfaces 33 Configuring a T1-F interface 33 Configuration procedure 34 Starting a BERT test on a T1-F interface 35 Displaying and maintaining T1-F interfaces 36 Configuring a CE3 interface 36 Configuring a CE3 interface in E3 mode 37 Configuring a CE3 interface in CE3 mode 37 Displaying and maintaining CE3 interfaces 39 Configuring a CT3 interface 39 Configuring a CT3 interface in T3 mode 40 Configuring a CT3 interface in CT3 mode 41 Displaying and maintaining CT3 interfaces 43 Configuring POS interfaces 45 Overview 45 SONET and SDH 45 POS 45 Configuring a standard POS interface 45 Configuring a POS subinterface 47 Displaying and maintaining POS interfaces 47 POS interface configuration examples 47 Directly connecting routers through POS interfaces 47 Connecting routers through POS interfaces across a Frame Relay network 48 Troubleshooting POS interfaces 50 Interface physically down 50 Data link layer down 51 IP packet loss 51 Configuring CPOS interfaces 52 Overview 52 CPOS interfaces 52 Overhead bytes 52 CPOS interface application scenarios 53 Feature and hardware compatibility 53 CPOS interface configuration task list 54 Configuring the operating mode of an interface module 54 Configuring basic settings of a CPOS interface 54 Configuring an E1 channel 55 Configuring a T1 channel 56 Displaying and maintaining CPOS interfaces 57 CPOS interface configuration example 57 Network requirements 57 Configuration procedure 58 Verifying the configuration 59 Troubleshooting CPOS interfaces 59 ii

5 Link protocol status down and loop detected 59 Configuring ATM interfaces 61 Overview 61 ATM and DSL 61 ATM interface types 61 ATM interface features 61 Compatibility information 62 Configuring an ATM OC-3c/STM-1 interface 62 Configuring an ADSL interface 63 Overview 63 Configuration procedure 64 Configuring a G.SHDSL interface 65 Overview 65 Configuration procedure 65 Configuring an ATM subinterface 67 Configuring an EFM interface 67 Configuring an EFM subinterface 69 Displaying and maintaining ATM interfaces 69 Troubleshooting ATM interfaces 70 Interface state error 70 Frequent packet dropping, CRC check errors, and interface state errors 70 Troubleshooting DSL interfaces 71 Configuring loopback, null, and inloopback interfaces 72 Configuring a loopback interface 72 Configuring a null interface 73 Configuring an inloopback interface 73 Displaying and maintaining loopback, null, and inloopback interfaces 73 Support and other resources 75 Contacting HP 75 Subscription service 75 Related information 75 Documents 75 Websites 75 Conventions 76 Index 78 iii

6 Bulk configuring interfaces You can enter interface range view to bulk configure multiple interfaces with the same feature instead of configuring them one by one. For example, you can execute the shutdown command in interface range view to shut down a range of interfaces. Configuration restrictions and guidelines When you bulk configure interfaces in interface range view, follow these restrictions and guidelines: In interface range view, only the commands supported by the first interface are available. The first interface is specified with the interface range command. You cannot enter the view of some interfaces by using the interface interface-type { interface-number interface-number.subnumber } command, for example, BRI 1/1/1:1. Do not configure any of these interfaces as the first interface in the interface range. Do not assign both an aggregate interface and any of its member interfaces to an interface range. Some commands, after being executed on both an aggregate interface and its member interfaces, can break up the aggregation. No limit is set on the maximum number of interfaces in an interface range. The more interfaces in an interface range, the longer the command execution time. The maximum number of interface range names is limited only by the system resources. To guarantee bulk interface configuration performance, HP recommends that you configure fewer than 1000 interface range names. After a command is executed in interface range view, one of the following situations might occur: The system displays an error message and stays in interface range view. It means that the execution failed on member interfaces in the interface range. If the execution failed on the first member interface in the interface range, the command is not executed on any member interfaces. If the execution failed on non-first member interfaces, the command takes effect on the other member interfaces. The system returns to system view. It means that: The command is supported in both system view and interface view. The execution failed on a member interface in interface range view and succeeded in system view. The command is not executed on the subsequent member interfaces. You can use the display this command to verify the configuration in interface view of each member interface. In addition, if the configuration in system view is not needed, use the undo form of the command to remove the configuration. 1

7 Configuration procedure 1. Enter system view. system-view 2. Enter interface range view. 3. (Optional.) Display commands available for the first interface in the interface range. 4. Use available commands to configure the interfaces. 5. (Optional.) Verify the configuration. interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-5> interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-5> ] Enter a question mark (?) at the interface range prompt. Available commands depend on the interface. display this By using the interface range name command, you assign a name to an interface range and can specify this name rather than the interface range to enter the interface range view. Displaying and maintaining bulk interface configuration Execute the display command in any view. Task Display information about the interface ranges created by using the interface range name command. Command display interface range [ name name ] 2

8 Configuring Ethernet interfaces Your device supports the following types of Ethernet interfaces: Layer 2 Ethernet interfaces Physical Ethernet interfaces operating at the data link layer (Layer 2) to switch packets. Layer 3 Ethernet interfaces Physical Ethernet interfaces operating at the network layer (Layer 3) to route packets. You can assign an IP address to a Layer 3 Ethernet interface. Layer-configurable Ethernet interfaces Physical Ethernet interfaces that can be configured to operate in bridge mode as Layer 2 Ethernet interfaces or in route mode as Layer 3 Ethernet interfaces. Layer 3 Ethernet subinterfaces Logical interfaces operating at the network layer. You can assign an IP address to a Layer 3 Ethernet subinterface. To enable a Layer 3 Ethernet interface to transport packets for multiple VLANs, you must create Layer 3 subinterfaces on the Layer 3 Ethernet interface. For information about how a Layer 3 Ethernet subinterface sends and receives VLAN-tagged packets, see Layer 2 LAN Switching Configuration Guide. Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: MSR1002-4/1003-8S. MSR2003. MSR / MSR3012/3024/3044/3064. Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers. Configuring common Ethernet interface settings This section describes the settings common to Layer 2 Ethernet interfaces, Layer 3 Ethernet interfaces, and Layer 3 Ethernet subinterfaces. For more information about the settings specific to Layer 2 Ethernet interfaces or subinterfaces, see "Configuring a Layer 2 Ethernet interface." For more information about the settings specific to Layer 3 Ethernet interfaces or subinterfaces, see "Configuring a Layer 3 Ethernet interface or subinterface." Configuring a combo interface (single combo interface) A combo interface is a logical interface that physically comprises one fiber combo port and one copper combo port. The two ports share one forwarding channel and one interface view. As a result, they cannot work simultaneously. When you activate one port, the other port is automatically disabled. In the interface view, you can activate the fiber or copper combo port, and configure other port attributes such as the interface rate and duplex mode. 3

9 Configuration prerequisites Before you configure combo interfaces, complete the following tasks: Determine the combo interfaces on your device. Identify the two physical interfaces that belong to each combo interface according to the marks on the device panel. Use the display interface command to determine which port (fiber or copper) of each combo interface is active: If the copper port is active, the output includes "Media type is twisted pair, Port hardware type is 1000_BASE_T." If the fiber port is active, the output does not include this information. Also, you can use the display this command in the view of each combo interface to display the combo interface configuration: If the fiber port is active, the combo enable fiber command exists in the output. If the copper port is active, the combo enable fiber command does not exist in the output. Changing the active port of a combo interface 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Activate the copper combo port or fiber combo port. interface interface-type interface-number combo enable { copper fiber } By default, the copper combo port is active. Configuring basic settings of an Ethernet interface or subinterface You can configure an Ethernet interface to operate in one of the following duplex modes: Full-duplex mode The interface can send and receive packets simultaneously. Half-duplex mode The interface can only send or receive packets at a given time. Autonegotiation mode The interface negotiates a duplex mode with its peer. You can set the speed of an Ethernet interface or enable it to automatically negotiate a speed with its peer. For a 100-Mbps or 1000-Mbps Layer 2 Ethernet interface, you can also set speed options for autonegotiation. The two ends can select a speed only from the available options. Configuring an Ethernet interface 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Set the description for the Ethernet interface. interface interface-type interface-number description text The default setting is interface-name Interface. For example, GigabitEthernet2/0/1 Interface. 4

10 4. Set the duplex mode for the Ethernet interface. 5. Set the speed for the Ethernet interface. 6. Set the expected bandwidth for the Ethernet interface. 7. Restore the default settings for the Ethernet interface. 8. Bring up the Ethernet interface. duplex { auto full half } speed { auto } bandwidth bandwidth-value default undo shutdown By default: The duplex mode is full for 10-GE interfaces. The duplex mode is auto for other Ethernet interfaces. Fiber ports do not support the half keyword. Support for the keywords of the command depends on the interface type. For more information, see Interface Command Reference. By default, the auto keyword is used. By default, the expected bandwidth (in kbps) is the interface baud rate divided by By default, Ethernet interfaces on an MSR3000 router are up, and Ethernet interfaces on other routers are down. Configuring an Ethernet subinterface When you configure an Ethernet subinterface, follow these restrictions and guidelines: To transmit and receive packets through an Ethernet subinterface, you must associate it with a VLAN. For more information, see Layer 2 LAN Switching Configuration Guide. To transmit packets between a local Ethernet subinterface and a remote Ethernet subinterface, configure them with the same subinterface number and VLAN ID. To configure an Ethernet subinterface: 1. Enter system view. system-view 2. Create an Ethernet subinterface. 3. Set the description for the Ethernet subinterface. 4. Restore the default settings for the Ethernet subinterface. 5. Set the expected bandwidth for the Ethernet subinterface. 6. Bring up the Ethernet subinterface. interface interface-type interface-number.subnumber description text default bandwidth bandwidth-value undo shutdown The default setting is interface-name Interface. For example, GigabitEthernet2/0/1.1 Interface. By default, the expected bandwidth (in kbps) is the interface baud rate divided by By default, Ethernet subinterfaces on an MSR3000 router are up, and Ethernet subinterfaces on other routers are down. 5

11 Configuring the link mode of an Ethernet interface CAUTION: After you change the link mode of an Ethernet interface, all commands (except the shutdown and combo enable commands) on the Ethernet interface are restored to their defaults in the new link mode. Ethernet interfaces operate differently depending on the hardware structure of interface cards: Some Ethernet interfaces can operate only as Layer 2 Ethernet interfaces (in bridge mode). Some Ethernet interfaces can operate only as Layer 3 Ethernet interfaces (in route mode). Some Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can set the link mode to bridge or route for these Ethernet interfaces. To configure the link mode of an Ethernet interface: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Configure the link mode of the Ethernet interface. interface interface-type interface-number port link-mode { bridge route } By default, the following interfaces operate in bridge mode: Ethernet interfaces on the following modules: DSIC-9FSW. HMIM-8GSW. HMIM-24GSW. SIC-4FSW. SIC-4GSW. SIC-4GSW-PoE Interfaces GigabitEthernet 0/3 through GigabitEthernet 0/26 on MSR routers. Interfaces GigabitEthernet 0/3 through GigabitEthernet 0/50 on MSR routers. The interface GigabitEthernet 0/27 on an MSR router is a fiber port and can operate only in route mode. Configuring jumbo frame support An Ethernet interface might receive frames larger than the standard Ethernet frame size during high-throughput data exchanges, such as file transfers. These frames are called jumbo frames. The Ethernet interface processes jumbo frames in the following ways: When the Ethernet interface is configured to deny jumbo frames, the Ethernet interface discards jumbo frames. 6

12 When the Ethernet interface is configured with jumbo frame support, the Ethernet interface performs the following operations: Processes jumbo frames within the specified length. Discards jumbo frames that exceed the specified length. To configure jumbo frame support in interface view: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Configure jumbo frame support. interface interface-type interface-number jumboframe enable [ value ] By default, the device allows jumbo frames within 1536 bytes to pass through all Layer 2 Ethernet interfaces. If you set the value argument multiple times, the most recent configuration takes effect. Configuring dampening on an Ethernet interface Parameters The interface dampening feature uses an exponential decay mechanism to prevent excessive interface flapping events from adversely affecting routing protocols and routing tables in the network. Suppressing interface state change events protects the system resources. If an interface is not dampened, its state changes are reported. For each state change, the system also generates an SNMP trap and log message. After a flapping interface is dampened, it does not report its state changes to the CPU. For state change events, the interface only generates SNMP trap and log messages. Penalty The interface has an initial penalty of 0. When the interface flaps, the penalty increases by 1000 for each down event. It does not increase for up events. Ceiling The penalty stops increasing when it reaches the ceiling. Suppress-limit The accumulated penalty that triggers the device to dampen the interface. In dampened state, the interface does not report its state changes to the CPU. For state change events, the interface only generates SNMP traps and log messages Reuse-limit When the accumulated penalty decreases to this reuse threshold, the interface is not dampened. Interface state changes are reported to the upper layers. For each state change, the system also generates an SNMP trap and log message. Decay The amount of time (in seconds) after which a penalty is decreased. Max-suppress-time The maximum amount of time the interface can be dampened. If the penalty is still higher than the reuse threshold when this timer expires, the penalty stops increasing for down events. The ceiling is equal to 2 (Max-suppress-time/Decay) reuse-limit. It is not user configurable. 7

13 Figure 1 shows the change rule of the penalty value. The lines t 0 and t 2 indicate the start time and end time of the suppression, respectively. The period from t 0 to t 2 indicates the suppression period, t 0 to t 1 indicates the max-suppress-time, and t 1 to t 2 indicates the complete decay period. Figure 1 Change rule of the penalty value Penalty t0 t1 t2 Ceiling Suppress limit Reuse limit Time Not suppressed Suppressed Not suppressed Configuration restrictions and guidelines When you configure dampening on an Ethernet interface, follow these restrictions and guidelines: The dampening command and the link-delay command cannot be configured together on an interface. The dampening command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the upper-layer protocols. Do not enable the dampening feature on an interface with RRPP, MSTP, or Smart Link enabled. Configuration procedure To configure dampening on an Ethernet interface: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Enable dampening on the interface. interface interface-type interface-number dampening [ half-life reuse suppress max-suppress-time ] By default, interface dampening is disabled on Ethernet interfaces. 8

14 Performing a loopback test on an Ethernet interface If an Ethernet interface does not work correctly, you can perform a loopback test on it to identify the problem. An Ethernet interface in a loopback test does not forward data traffic. Loopback tests include the following types: Internal loopback test Tests all on-chip functions associated with the Ethernet interface. External loopback test Tests the hardware of the Ethernet interface. To perform an external loopback test on the Ethernet interface, connect a loopback plug to the Ethernet interface. The device sends test packets out of the Ethernet interface, which are expected to loop over the plug and back to the Ethernet interface. If the Ethernet interface fails to receive any test packets, the hardware of the Ethernet interface is faulty. Configuration restrictions and guidelines When you perform loopback tests, follow these restrictions and guidelines: On an administratively shut down Ethernet interface (displayed as in ADM or Administratively DOWN state), you cannot perform an internal or external loopback test. During a loopback test on an Ethernet interface, the speed, duplex, mdix-mode, and shutdown commands are not available on the Ethernet interface. During a loopback test on an Ethernet interface, the Ethernet interface operates in full duplex mode. When the loopback test is complete, the Ethernet interface restores to its duplex setting. Configuration procedure To perform a loopback test on an Ethernet interface: 1. Enter system view. system-view 2. Enter Ethernet interface view. interface interface-type interface-number 3. Perform a loopback test. loopback { external internal } By default, no loopback test is performed. Configuring generic flow control on an Ethernet interface To avoid dropping packets on a link, you can enable generic flow control at both ends of the link. When traffic congestion occurs at the receiving end, the receiving end sends a flow control (Pause) frame to ask the sending end to suspend sending packets. Generic flow control includes the following types: TxRx-mode generic flow control Enabled by using the flow-control command. With TxRx-mode generic flow control enabled, an interface can both send and receive flow control frames: When congestion occurs, the interface sends a flow control frame to its peer. When the interface receives a flow control frame from its peer, it suspends sending packets to its peer. Rx-mode generic flow control Enabled by using the flow-control receive enable command. With Rx-mode generic flow control enabled, an interface can receive flow control frames, but it cannot send flow control frames: When congestion occurs, the interface cannot send flow control frames to its peer. 9

15 When the interface receives a flow control frame from its peer, it suspends sending packets to its peer. To handle unidirectional traffic congestion on a link, configure the flow-control receive enable command at one end and the flow-control command at the other end. To enable both ends of a link to handle traffic congestion, configure the flow-control command at both ends. To enable generic flow control on an Ethernet interface: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Enable generic flow control. interface interface-type interface-number Enable TxRx-mode generic flow control: flow-control Enable Rx-mode generic flow control: flow-control receive enable By default, generic flow control is disabled on an Ethernet interface. Setting the statistics polling interval To set the statistics polling interval in system view: 1. Enter system view. system-view 2. Set the statistics polling interval. flow-interval interval By default, the statistics polling interval is 300 seconds. To display the interface statistics collected in the last statistics polling interval, use the display interface command. Configuring a Layer 2 Ethernet interface Configuring storm suppression The storm suppression feature ensures that the size of a particular type of traffic (broadcast, multicast, or unknown unicast traffic) does not exceed the threshold on an interface. When the broadcast, multicast, or unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the traffic drops below this threshold. Configuration restrictions and guidelines The configured suppression threshold value in pps or kbps might be converted into a multiple of a step supported by the chip. As a result, the effective suppression threshold might be different from the configured one. For information about the suppression threshold that takes effect, see the prompt on the device. 10

16 Configuration procedure To set storm suppression thresholds on an Ethernet interface or subinterface: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Enable broadcast suppression and set the broadcast suppression threshold. 4. Enable multicast suppression and set the multicast suppression threshold. 5. Enable unknown unicast suppression and set the unknown unicast suppression threshold. interface interface-type interface-number broadcast-suppression { ratio pps max-pps kbps max-kbps } multicast-suppression { ratio pps max-pps kbps max-kbps } unicast-suppression { ratio pps max-pps kbps max-kbps } By default, broadcast suppression is disabled. By default, multicast suppression is disabled. By default, unknown unicast suppression is disabled. Setting the MDIX mode of an Ethernet interface IMPORTANT: Fiber ports do not support the MDIX mode setting. A physical Ethernet interface has eight pins, each of which plays a dedicated role. For example, pins 1 and 2 transmit signals, and pins 3 and 6 receive signals. You can use both crossover and straight-through Ethernet cables to connect copper Ethernet interfaces. To accommodate these types of cables, a copper Ethernet interface can operate in one of the following Medium Dependent Interface-Crossover (MDIX) modes: MDIX mode Pins 1 and 2 are receive pins and pins 3 and 6 are transmit pins. MDI mode Pins 1 and 2 are transmit pins and pins 3 and 6 are receive pins. AutoMDIX mode The interface negotiates pin roles with its peer. To enable a copper Ethernet interface to communicate with its peer, set the MDIX mode of the interface by following these guidelines: Typically, set the MDIX mode of the interface to AutoMDIX. Set the MDIX mode of the interface to MDI or MDIX only when the device cannot determine the cable type. When a straight-through cable is used, configure the interface to operate in an MDIX mode different than its peer. When a crossover cable is used, perform one of the following tasks: Configure the interface to operate in the same MDIX mode as its peer. Configure either end to operate in AutoMDIX mode. To set the MDIX mode of an Ethernet interface: 1. Enter system view. system-view 11

17 2. Enter Ethernet interface view. 3. Set the MDIX mode of the Ethernet interface. interface interface-type interface-number mdix-mode { automdix mdi mdix } By default, a copper Ethernet interface operates in auto mode to negotiate pin roles with its peer. Configuring a Layer 3 Ethernet interface or subinterface Setting the MTU for an Ethernet interface or subinterface The maximum transmission unit (MTU) of an Ethernet interface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of an interface. To set the MTU for an Ethernet interface or subinterface: 1. Enter system view. system-view 2. Enter Ethernet interface or subinterface view. 3. Set the MTU of the Ethernet interface or subinterface. interface interface-type { interface-number interface-number.subnumber } mtu size The default setting is 1500 bytes. Setting the MAC address of an Ethernet interface In a network, when the Layer 3 Ethernet interfaces of different devices have the same MAC address, the devices might fail to communicate correctly. To eliminate the MAC address conflicts, use the mac-address command to modify the MAC addresses of Layer 3 Ethernet interfaces. To set the MAC address of an Ethernet interface: 1. Enter system view. system-view 2. Enter Ethernet interface view. 3. Set the MAC address of the Ethernet interface. interface interface-type interface-number mac-address mac-address The default MAC address of a Layer 3 Ethernet interface varies by device model. 12

18 Displaying and maintaining an Ethernet interface or subinterface Execute display commands in any view and reset commands in user view. Task Display interface traffic statistics. Display traffic rate statistics of interfaces in up state over the last statistics polling interval. Display the operational and status information of the specified interfaces. Display information about dropped packets on the specified interfaces. Display the Ethernet module statistics (centralized devices in standalone mode). Display the Ethernet statistics (distributed devices in standalone mode/centralized devices in IRF mode). Display the Ethernet statistics (distributed devices in IRF mode). Clear interface or subinterface statistics. Clear the statistics of dropped packets on the specified interfaces. Clear the Ethernet module statistics (centralized devices in standalone mode). Clear the Ethernet statistics (distributed devices in standalone mode/centralized devices in IRF mode). Clear the Ethernet statistics (distributed devices in IRF mode). Command display counters { inbound outbound } interface [ interface-type [ interface-number interface-number.subnumber ] ] display counters rate { inbound outbound } interface [ interface-type [ interface-number interface-number.subnumber ] ] display interface [ interface-type [ interface-number interface-number.subnumber ] ] [ brief [ description down ] ] display packet-drop { interface [ interface-type [ interface-number ] ] summary } display ethernet statistics display ethernet statistics [ slot slot-number ] display ethernet statistics [ chassis chassis-number slot slot-number ] reset counters interface [ interface-type [ interface-number interface-number.subnumber ] ] reset packet-drop interface [ interface-type [ interface-number ] ] reset ethernet statistics reset ethernet statistics [ slot slot-number ] reset ethernet statistics [ chassis chassis-number slot slot-number ] 13

19 Configuring WAN interfaces This chapter describes how to configure interfaces for connecting to WAN networks, including Frame Relay, ATM, and ISDN. Available WAN interfaces include the asynchronous serial interface, synchronous serial interface, ATM interface, ISDN BRI interface, and CE1/PRI interface. For more information about ATM interfaces, see "Configuring ATM interfaces." Configuring a serial interface Asynchronous serial interface The following types of asynchronous serial interfaces are available: Synchronous/asynchronous serial interface operating in asynchronous mode. The interface type name is Serial. Dedicated asynchronous serial interface. The interface type name is Async. You can connect a modem or ISDN terminal adapter to an asynchronous serial interface for dial-up connection. An asynchronous serial interface can operate in protocol or flow mode. Protocol mode Data is transmitted in packets. The link layer protocol can only be PPP. The network layer protocol is typically IP. Flow mode Data is transmitted as character flows. This mode is typically used in human-machine interaction scenarios such as dial-up access. After the physical connection is established, you can send commands to set up a link with the asynchronous serial interface, and then configure the device. Synchronous serial interface Synchronous serial interfaces refer to synchronous/asynchronous serial interfaces operating in synchronous mode. They provide serial communication channels for synchronous data transmission. The interface type name is Serial. A synchronous serial interface operates in DCE or DTE mode. Two directly connected synchronous serial interfaces must operate in different modes. In DCE mode, the interface provides timing for synchronization and sets the baud rate. In DTE mode, the interface accepts the timing signal and baud rate from the DCE. The synchronous serial interfaces on the device typically operate as DTE. You can connect a synchronous interface to various types of cables, including V.24, V.35, X.21, RS449, and RS530. Typically, the device can automatically recognize the cable type and select electrical properties. The synchronous serial interface supports multiple data link layer protocols, including PPP, HDLC, and Frame Relay. The interface supports network layer protocols, such as IP. 14

20 Configuring an asynchronous serial interface This section only describes the interface properties configuration. Depending on the network requirements, you might also need to configure PPP, DDR, IP address, firewall, and interface backup. To configure an asynchronous serial interface: 1. Enter system view. system-view 2. Enter asynchronous serial interface view. 3. (Optional.) Configure the interface description. 4. Configure a synchronous or asynchronous serial interface to operate as an asynchronous serial interface. interface async interface-number or interface serial interface-number description text physical-mode async By default, the description of an asynchronous serial interface is interface name Interface, for example, Serial2/1/0 Interface. By default, a synchronous or asynchronous serial interface operates as a synchronous serial interface. Skip this step if the interface is an asynchronous interface. 5. Set the operating mode. async mode { flow protocol } The default is the protocol mode. 6. (Optional.) Enable level detection. 7. (Optional.) Enable local loopback. detect dsr-dtr loopback By default, level detection is enabled. By default, local loopback is disabled. 8. Set the MTU. mtu size The default setting is 1500 bytes. 9. Set the keepalive interval. timer-hold seconds The default setting is 10 seconds. 10. Set the maximum number of keepalive attempts. 11. Set the MRU for an interface operating in flow mode. 12. (Optional.) Set the intended bandwidth for the asynchronous serial interface. 13. (Optional.) Restore the default settings for the asynchronous serial interface. 14. Bring up the asynchronous serial interface. timer-hold retry retry phy-mru mrusize bandwidth bandwidth-value default undo shutdown The default setting is 5. The interface determines that the remote end has been down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. The default MRU is 1700 bytes. By default, the expected bandwidth (in kbps) is the interface baud rate divided by By default, an asynchronous serial interface is up. 15

21 Configuring a synchronous serial interface This section only describes the interface properties configuration. Depending on the network requirements, you might also need to configure the data link layer protocol, DDR, IP address, firewall, and interface backup. To configure a synchronous serial interface: 1. Enter system view. system-view 2. Enter synchronous serial interface view. 3. Configure a synchronous or asynchronous serial interface to operate as a synchronous serial interface. 4. (Optional.) Configure the interface description. interface serial interface-number physical-mode sync description text By default, a synchronous or asynchronous serial interface operates as a synchronous serial interface. By default, the description of a synchronous serial interface is interface name Interface, for example, Serial2/1/0 Interface. 5. Set the link layer protocol. link-protocol { fr hdlc ppp } The default is PPP. 6. Set the digital signal coding format. 7. Set the baud rate. 8. Set the clock selection mode. 9. (Optional.) Set transmit-clock or receive-clock signal inversion on the DTE side. code { nrz nrzi } baudrate baudrate virtualbaudrate virtualbaudrate On DTE side: clock { dteclk1 dteclk2 dteclk3 dteclk4 dteclk5 dteclkauto } On DCE side: clock { dceclk1 dceclk2 dceclk3 } invert { transmit-clock receive-clock } The default is non-return-to-zero (NRZ). The default is bps. Use the baudrate and virtualbaudrate commands at the DCE and DTE ends, respectively. The default is dceclk1 for the DCE side and dteclk1 for the DTE side. By default, clock signal inversion is disabled. 10. Set the MTU. mtu size The default is 1500 bytes. 11. Set the CRC mode. crc { none } The default is 16-bit CRC. 12. Set the number of interframe filling tags. 13. (Optional.) Enable level detection. 14. (Optional.) Enable data carrier detection (DCD). 15. (Optional.) Enable local loopback. itf number number detect dsr-dtr detect dcd loopback The default is four. By default, level detection is enabled. By default, DCD is enabled. By default, local loopback is disabled. 16

22 16. Set the keepalive interval. timer-hold seconds The default setting is 10 seconds. 17. Set the maximum number of keepalive attempts. timer-hold retry retry The default setting is 5. The interface determines that the remote end has been down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. 18. Set the line idle-code. idle-code { 7e ff } The default is 0x7E. 19. (Optional.) Enable RTS signal reverse. 20. (Optional.) Set the intended bandwidth for the synchronous serial interface. 21. (Optional.) Restore the default settings for the synchronous serial interface. 22. Bring up the synchronous serial interface. reverse-rts bandwidth bandwidth-value default undo shutdown By default, RTS signal reverse is disabled. By default, the expected bandwidth (in kbps) is the interface baud rate divided by By default, a synchronous serial interface is up. Configuring a subinterface 1. Enter system view. system-view 2. Create a subinterface and enter its view. 3. Configure the interface description. interface serial interface-number.subnumber [ p2mp p2p ] description text By default, the description of a subinterface is interface-name Interface. 4. Set the MTU. mtu size The default MTU is 1500 bytes. 5. Set the expected bandwidth for the subinterface. 6. Restore the default settings for the subinterface. bandwidth bandwidth-value default By default, the expected bandwidth (in kbps) is the interface baud rate divided by Bring up the subinterface. undo shutdown By default, a subinterface is up. Displaying and maintaining serial interfaces Execute display commands in any view and reset commands in user view. 17

23 Task Display serial interface information. Display information about asynchronous serial interfaces. Command display interface [ serial [ interface-number ] ] [ brief [ description down ] ] display interface [ async [ interface-number ] ] [ brief [ description down ] Clear statistics for serial interfaces. reset counters interface [ serial [ interface-number ] ] Clear statistics for asynchronous serial interfaces. reset counters interface [ async [ interface-number ] ] Configuring an AM interface The analog modem (AM) interface combines the functionality of the asynchronous serial interface and analog modem. The AM interface supports most of the commands available on asynchronous serial interfaces and modems. When you configure an AM interface, you can treat it as a special asynchronous serial interface. AM interfaces provide dial-in and dial-out services for analog dial-up users. The actual connect rates depend on the network conditions, including the line quality and connection protocol. The AM interface can provide the following maximum downstream and upstream rates: If the peer (typically an ISP) uses a digital modem, the AM interface can use the V.90 Modem standard to set up connections. The maximum downstream rate is 56 kbps, and the maximum upstream rate is 33.6 kbps. If the peer (typically a subscriber) uses an analog modem (or an AM interface), the AM interface can use the V.34 Modem standard to set up connections. The maximum downstream and upstream rates are both 33.6 kbps. Configuration procedure The AM interface supports all commands available on the asynchronous interface and the modem, except for the modem auto-answer and baudrate commands. For more information about modem configuration, see Layer 2 WAN Configuration Guide. In addition, to set the baud rate for an AM interface, you must use the speed command in user line view. For more information, see Fundamentals Configuration Guide. This section only describes the interface properties configuration. Depending on the network requirements, you might also need to configure PPP, DDR, IP address, firewall, and interface backup. To configure an AM interface: 1. Enter system view. system-view 2. Enter AM interface view. interface analogmodem { interface-number interface-number:15 } 18

24 3. Set the coding format of the modem. 4. (Optional.) Configure the interface description. country-code area-name description text The default is united-states. For more information about this command, see Layer 2 WAN Command Reference. By default, the description of an AM interface is interface name Interface, for example, Analogmodem2/4/0 Interface. 5. Set the operating mode. async-mode { flow protocol } 6. (Optional.) Enable local loopback. loopback By default, an AM interface operates in flow mode. When an AM interface is operating in flow mode, no data link layer protocol is available. When operating in protocol mode, the AM interface uses PPP as the data link layer protocol. By default, local loopback is disabled. 7. Set the MTU. mtu size The default setting is 1500 bytes. 8. Set the keepalive interval. timer-hold seconds The default setting is 10 seconds. 9. Set the maximum number of keepalive attempts. 10. (Optional.) Eliminate the pulses with a width less than μs. 11. Set the MRU for an AM interface operating in flow mode. 12. (Optional.) Set the intended bandwidth for the AM interface. 13. (Optional.) Restore the default settings for the AM interface. timer-hold retry retry eliminate-pulse phy-mru mrusize bandwidth bandwidth-value default The default setting is 5. The interface determines that the remote end has been down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. By default, the pulses with a width less than μs are eliminated. The default MRU is 1700 bytes. This command is not available on AM interfaces created through channelization. By default, the expected bandwidth (in kbps) is the interface baud rate divided by Bring up the AM interface. undo shutdown By default, an AM interface is up. Displaying and maintaining AM interfaces Execute display commands in any view and reset commands in user view. 19

25 Task Display AM interface information. Clear statistics for AM interfaces. Command display interface [ analogmodem [ interface-number ] ] [ brief [ description down ] ] reset counters interface [ analogmodem [ interface-number ] ] Configuring an FCM interface Fast Connect Modem (FCM) interfaces are dedicated for POS access. They use CCITT V.22 or CCITT V.29 to complete POS dial-up and access in a short time. An FCM interface has the following features: Achieves reliable ring detection and off-hook in a short time. Compatible with standard protocols to interoperate with POS devices of other mainstream vendors. Able to respond to POS calls and access the POS device. Feature and hardware compatibility Hardware MSR1002-4/1003-8S MSR2003 MSR / MSR3012/3024/3044/3064 MSR4060/4080 FCM interface compatibility No No No Yes Yes Configuration procedure An FCM interface has the same configuration as an asynchronous serial interface, except that an FCM interface does not support hardware and software flow control and cannot operate in flow and TTY modes. FCM interfaces apply only to POS terminal access. You need to configure POS terminal access parameters. For more information, see Terminal Access Configuration Guide. To configure an FCM interface: 1. Enter system view. system-view 2. Enter FCM interface view. 3. (Optional.) Configure the interface description. interface fcm { interface-number interface-number:15 } description text By default, the description of an FCM interface is interface name Interface, for example, Fcm2/4/0:15 Interface. 20

26 4. Set the PCM for the FCM interface. pcm { a-law u-law } The default is a-law. 5. Set the MTU. mtu size The default setting is 1500 bytes. 6. Set the keepalive interval. timer-hold seconds The default setting is 10 seconds. 7. Set the maximum number of keepalive attempts. 8. (Optional.) Set the intended bandwidth for the AM interface. 9. (Optional.) Restore the default settings for the AM interface. timer-hold retry retry bandwidth bandwidth-value default The default setting is 5. The interface determines that the remote end has been down if it does not receive a keepalive response after the maximum number of keepalive attempts have been made. By default, the expected bandwidth (in kbps) is the interface baud rate divided by Bring up the AM interface. undo shutdown By default, an AM interface is up. Displaying and maintaining FCM interfaces Execute display commands in any view and reset commands in user view. Task Display FCM interface information. Command display interface [ fcm [ interface-number ] ] [ brief [ description down ] ] Clear statistics for FCM interfaces. reset counters interface [ fcm [ interface-number ] ] Configuring an ISDN BRI interface Integrated services digital network (ISDN) provides all-digital terminal-to-terminal services and fulfills the fully digitized delivery of services integrating voice, data, graphics, and video. ISDN implements digital transmission on a user loop and provides end-to-end digitization. As a standardized digital interface, ISDN BRI interface can forward digital and analog information. The most commonly used ISDN standards include ITU-T I.430, Q.921, and Q.931 recommendations. All devices that meet ITU-T ISDN standards can access an ISDN network. ITU-T I.411 standardizes the ISDN user-network interface and provides a reference configuration for ISDN access. As shown in Figure 2, the reference configuration contains the following elements: Function groups Sets of functions required for accessing an ISDN network. Network terminal 1 (NT1) Implements the functionality of the first layer in the OSI reference model, such as subscriber-line transmission, loop test, and D-channel competition. Network terminal 2 (NT2) Implements the functionality of layers 1 through 3. NT2 is also known as the intelligent network terminal. 21

27 Category-1 terminal equipment (TE1) User equipment compliant with the ISDN interface provisions. TE1 is also known as the ISDN standard terminal. Digital phone-set is an example of TE1. Category-2 terminal equipment (TE2) User equipment incompliant with the ISDN interface provisions. TE2 is also known as non-isdn standard terminal equipment. Terminal adapter (TA) Provides adaptation for TE2 to access a standard ISDN interface. Reference points Points used to differentiate function groups. R Reference point between a non-isdn equipment and TA. S Reference point between a user terminal and NT2. T Reference point between NT1 and NT2. U Reference point between NT1 and line terminal. Figure 2 Referential ISDN user-network interface configuration Configuration prerequisites Before you configure an ISDN BRI interface, verify the following items: Interface type (ISDN BRI U or ISDN BRI S/T) provided by your telecom service provider You must identify this information before you purchase a router. You must perform this task because the UNI implementation of a service provider might deviate from ITU-T I.411. Availability of digital service The router requires digital transmission. You must subscribe to the digital call service for an ISDN line. Connection type (point-to-point or point-to-multipoint) Because ISDN supports semi-permanent connections, you can use an ISDN leased line to connect two permanent points. To connect more than two points, use a point-to-multipoint connection. Availability of the calling line identification function This function can filter calling numbers on an ISDN line to block unauthorized users from the router. Configuration procedure ISDN BRI interfaces are used for dialup purposes. For more information about dial-up configuration, see Layer 2 WAN Configuration Guide. To configure an ISDN BRI interface: 22