05-Layer 2—WAN Access Command Reference

HomeSupportResource CenterReference GuidesCommand ReferencesH3C MSR810[830][2600][3600] Routers Command Reference(V7)-R6728-6W10005-Layer 2—WAN Access Command Reference
09-Frame Relay commands
Title Size Download
09-Frame Relay commands 306.69 KB

Frame Relay commands

This feature is supported only on routers installed with the following modules:

·     E1.

·     E1-F.

·     CE3.

·     CPOS.

·     CT3.

·     SAE.

·     T1.

·     T1-F.

This feature is not supported on the following routers:

·     MSR810.

·     MSR810-W.

·     MSR810-W-DB.

·     MSR810-LM.

·     MSR810-W-LM.

·     MSR810-10-PoE.

·     MSR810-LM-HK.

·     MSR810-W-LM-HK.

Basic Frame Relay commands

broadcast

Use broadcast to allow broadcast packets on a virtual circuit (VC).

Use undo broadcast to forbid broadcast packets on a VC.

Syntax

broadcast

undo broadcast

Default

Broadcast packets are forbidden on static VCs and allowed on dynamic VCs.

Views

Frame Relay virtual circuit view

Predefined user roles

network-admin

Usage guidelines

Configure this command if a static VC needs to allow broadcast or multicast packets.

When a VC allows broadcast packets, the broadcast or multicast packets on the Frame Relay interface of the VC are also transmitted on the VC.

Examples

# Allow broadcast packets on the VC identified by DLCI 200.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 200

[Sysname-Serial2/1/0-fr-dlci-200] broadcast

display fr compression iphc

Use display fr compression iphc to display statistics for Frame Relay IPHC.

Syntax

display fr compression iphc { rtp | tcp } [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

rtp: Displays statistics for RTP header compression.

tcp: Displays statistics for TCP header compression.

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays IPHC statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays IPHC statistics for the subinterface. If you do not specify an interface, this command displays IPHC statistics for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display IPHC statistics for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not display IPHC statistics for the VC.

·     If you specify only an interface, this command displays IPHC statistics for all VCs on the interface.

Usage guidelines

Frame Relay IPHC statistics are displayed on a per-VC basis. An interface (main interface or subinterface) can have one or more VCs.

Examples

# Display RTP header compression statistics for the VC with DLCI 17 on Serial 2/1/0.

<Sysname> display fr compression iphc rtp interface serial 2/1/0 dlci 17

DLCI: 17, Serial2/1/0

  Received:

    Compressed/Error/Total: 0/0/0 packets

  Sent:

    Compressed/Total: 0/0 packets

    Sent/Saved/Total: 0/0/0 bytes

    Packet-based compression ratio: 0%

    Byte-based compression ratio: 0%

  Connections:

    Rx/Tx: 16/16

    Five-Minute-Miss: 0 (Misses/5Mins)

    Max-Miss: 0

# Display TCP header compression statistics for Serial 2/1/0.

<Sysname> display fr compression iphc tcp interface serial 2/1/0

DLCI: 16, Serial2/1/0

  Received:

    Compressed/Error/Total: 0/0/0 packets

  Sent:

    Compressed/Total: 0/0 packets

    Sent/Saved/Total: 0/0/0 bytes

    Packet-based compression ratio: 0%

    Byte-based compression ratio: 0%

  Connections:

    Rx/Tx: 16/16

    Five-Minute-Miss: 0 (Misses/5Mins)

    Max-Miss: 0

 

DLCI: 17, Serial2/1/0

  Received:

    Compressed/Error/Total: 0/0/0 packets

  Sent:

    Compressed/Total: 0/0 packets

    Sent/Saved/Total: 0/0/0 bytes

    Packet-based compression ratio: 0%

    Byte-based compression ratio: 0%

  Connections:

    Rx/Tx: 16/16

    Five-Minute-Miss: 0 (Misses/5Mins)

    Max-Miss: 0

Table 1 Command output

Field

Description

Received:

  Compressed/Error/Total: 0/0/0 packets

Statistics on received packets:

·     Compressed—Number of compressed packets.

·     Error—Number of error packets.

·     Total—Total number of packets.

Sent:

  Compressed/Total: 0/0 packets

  Sent/Saved/Total: 0/0/0 bytes

  Packet-based compression ratio: 0%

  Byte-based compression ratio: 0%

Statistics on sent packets:

·     Compressed—Number of compressed packets.

·     Total—Total number of packets.

·     Sent—Actual number of bytes sent.

·     Saved—Number of bytes reduced due to the compression.

·     Total—Number of bytes that need to be sent if no compression is performed.

·     Packet-based compression ratio—Ratio of compressed packets to the total number of packets (Compressed/Total x 100%).

·     Byte-based compression ratio—Ratio of saved bytes to the total number of bytes (Saved/Total x 100%).

Connections:

  Rx/Tx

  Five-Minute-Miss: x (Misses/5Mins)

  Max-Miss: x

Statistics on sent packets:

·     Rx—Maximum number of decompression connections when the device acts as the receiving end.

·     Tx—Maximum number of compression connections when the device acts as the transmitting end.

·     Five-Minute-Miss—Number of times an entry failed to be found over the most recent 5 minutes.

·     Max-Miss—Maximum number of times an entry failed to be found.

 

Related commands

fr compression iphc enable

reset fr compression iphc

display fr compression stac

Use display fr compression stac to display statistics for Frame Relay STAC compression.

Syntax

display fr compression stac [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays STAC compression statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays STAC compression statistics for the subinterface. If you do not specify an interface, this command displays STAC compression statistics for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display STAC compression statistics for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not display STAC compression statistics for the VC.

·     If you specify only an interface, this command displays STAC compression statistics for all VCs on the interface.

Usage guidelines

Frame Relay STAC compression statistics are displayed on a per-VC basis. An interface (main interface or subinterface) can have one or more VCs.

Examples

# Display Frame Relay STAC compression statistics for all interfaces.

<Sysname> display fr compression stac

Serial2/1/0

  DLCI: 22

    Uncompressed bytes sent/received: 0/0

    Compressed bytes sent/received: 0/0

    1 min avg ratio output/input: 0.000/0.000

    5 min avg ratio output/input: 0.000/0.000

Table 2 Command output

Field

Description

Uncompressed bytes sent/received

Number of sent/received bytes before compression.

Compressed bytes sent/received

Number of bytes sent/received after compression.

1 min avg ratio output/input

Average ratio of bytes after compression to bytes before compression for every second over the last 1 minute (sent/received).

5 min avg ratio output/input

Average ratio of bytes after compression to bytes before compression for every minute over the last 5 minutes (sent/received).

 

display fr fragment

Use display fr fragment to display statistics for Frame Relay FRF.12 fragmentation.

Syntax

display fr fragment [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays FRF.12 fragmentation statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays FRF.12 fragmentation statistics for the subinterface. If you do not specify an interface, this command displays FRF.12 fragmentation statistics for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display FRF.12 fragmentation statistics for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not display FRF.12 fragmentation compression statistics for the VC.

·     If you specify only an interface, this command displays FRF.12 fragmentation statistics for all VCs on the interface.

Examples

# Display Frame Relay FRF.12 fragmentation statistics for all interfaces.

<Sysname> display fr fragment

Interface Serial2/1/0:

DLCI  Interface      Type              Size (byte)  In/Out/Dropped

200   Serial2/1/0    FRF12(end-to-end) 80           0/0/0

# Display FRF.12 fragmentation statistics for the VC with DLCI 200 on Serial 2/1/0.

<Sysname> display fr fragment interface serial2/1/0 dlci 200

Type: FRF12(end-to-end)

 Size: 80 bytes

 Pre-fragment:

   Output: 0 packets, 0 bytes

 Fragmented:

   Input: 0 packets, 0 bytes

   Output: 0 packets, 0 bytes

 Assembled:

   Input: 0 packets, 0 bytes

 Dropped:

   Input: 0 packets, 0 bytes

   Output: 0 packets, 0 bytes

 Out-of-sequence packets: 0

Table 3 Command output

Field

Description

Size (byte)

Fragment size in bytes.

In/Out/Dropped

Numbers of fragments received/sent/dropped.

Size

Fragment size in bytes.

Pre-fragment

Number of packets to be fragmented.

Fragmented

Number of fragments.

Assembled

Number of fragments reassembled.

Dropped

Number of fragments dropped.

Out-of-sequence packets

Number of out-of-sequence fragments.

Output: 0 packets, 0 bytes

Number of packets or fragments sent, and number of bytes sent.

Input: 0 packets, 0 bytes

Number of fragments received, and number of bytes received.

 

display fr inarp

Use display fr inarp to display statistics for Frame Relay InARP packets.

Syntax

display fr inarp [ interface interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays statistics for the subinterface. If you do not specify an interface, this command displays statistics for all interfaces.

Usage guidelines

You can determine whether Frame Relay InARP is operating correctly based on the output from this command.

Examples

# Display statistics for Frame Relay InARP packets.

<Sysname> display fr inarp

Frame relay InARP statistics for interface Serial2/1/0 (DTE)

  Recvd InARP request  Sent InARP reply  Sent InARP request  Recvd InARP reply

  0                    0                 1                   1

Table 4 Command output

Field

Description

Recvd InARP request

Number of received InARP requests.

Sent InARP reply

Number of sent InARP replies.

Sent InARP request

Number of sent InARP requests.

Recvd InARP reply

Number of received InARP replies.

 

Related commands

fr inarp

display fr ipv6 map

Use display fr ipv6 map to display Frame Relay IPv6 address mapping.

Syntax

display fr ipv6 map [ static | dynamic ] [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

static: Specifies static address mapping.

dynamic: Specifies dynamic address mapping.

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays IPv6 address mapping for the main interface and its subinterfaces. If you specify a subinterface, this command displays IPv6 address mapping for the subinterface. If you do not specify an interface, this command displays IPv6 address mapping for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display IPv6 address mapping for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not display IPv6 address mapping for the VC.

·     If you specify only an interface, this command displays IPv6 address mapping for all VCs on the interface.

Usage guidelines

If you do not specify the static or dynamic keyword, this command displays both static and dynamic address mapping.

Examples

# Display Frame Relay IPv6 address mapping.

<Sysname> display fr ipv6 map

Map statistics for interface Serial2/1/0 (DTE)

  DLCI: 100  IPv6 IND: FE80::56FF:FE00:0  Interface: Serial2/1/0

    Create time: 2014/10/11 09:57:28  Status: Active

    Encapsulation: IETF  Broadcast

  DLCI: 100  IPv6 IND: 10::1  Interface: Serial2/1/0

    Create time: 2014/10/11 09:57:28  Status: Active

    Encapsulation: IETF  Broadcast

  DLCI: 100  IPv6: 10::3  Interface: Serial2/1/0

    Create time: 2014/10/11 09:57:28  Status: Active

    Encapsulation: IETF  Broadcast

Table 5 Command output

Field

Description

Map Statistics for interface Serial2/1/0 (DTE)

IPv6 address-to-DLCI maps for Serial 2/1/0 (a DTE interface).

DLCI: 100

VC identified by the DLCI number.

IPv6 IND 10::1

Address map established with the peer IPv6 address 10::1 through IND.

If IND is absent, the address map is manually configured.

Interface: Serial2/1/0

Interface where the VC was created.

Create time: 2014/10/11 09:57:28

Time when the address map was created.

Status: Active

Status of the address map: Active or Inactive.

Encapsulation: IETF

Encapsulation type for the VC: IETF or Nonstandard.

Broadcast

Broadcast packets are allowed on the VC.

 

display fr lmi

Use display fr lmi to display LMI information.

Syntax

display fr lmi [ interface interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies a main interface by its type and number. If you do not specify an interface, this command displays LMI information for all main interfaces.

Usage guidelines

The LMI protocol sends status enquiry messages and status messages for maintaining Frame Relay links. The output from the command helps you diagnose faults.

Examples

# Display LMI information for all interfaces.

<Sysname> display fr lmi

Frame relay LMI information for interface Serial2/1/0 (DTE, Q933)

  T391DTE: 10 seconds, N391DTE: 6, N392DTE: 3, N393DTE: 4

  Sent status enquiry: 96, Received status: 85

  Status timeout: 3, Discarded messages: 3

Frame relay LMI information for interface Serial2/1/0 (DCE, Q933)

  T392DCE: 15 seconds, N392DCE: 3, N393DCE: 4

  Received status enquiry: 0, Sent status: 0

  Status enquiry timeout: 0, Discarded messages: 0

Table 6 Command output

Field

Description

Frame relay LMI information for interface Serial2/1/0 (DTE, Q933)

Serial 2/1/0 (a Frame Relay interface) is a DTE interface that complies with Q.933 Annex A.

T391DTE: 10 seconds, N391DTE: 6, N392DTE: 3, N393DTE: 4

DTE-side T391 timer (in seconds) configured by using the timer-hold command, N391 counter, N392 counter, and N393 counter.

Sent status enquiry: 96, Received status: 85

Number of status enquiry messages sent out of the interface and number of status messages received on the interface.

Status timeout: 3, Discarded messages: 3

Number of status messages that timed out and number of discarded messages.

Frame relay LMI information for interface Serial2/1/0 (DCE, Q933)

Serial 2/1/0 (a Frame Relay interface) is a DCE interface that complies with Q.933 Annex A.

T392DCE: 15 seconds, N392DCE: 3, N393DCE: 4

DCE-side T392, N392, and N393 values.

Received status enquiry: 0, Sent status: 0

Number of status enquiry messages received on the interface and number of status messages sent out of the interface.

Status enquiry timeout: 0, Discarded messages : 0

Number of status enquiry messages that timed out and number of discarded messages.

 

Related commands

fr lmi n391dte

fr lmi n392dce

fr lmi n392dte

fr lmi n393dce

fr lmi n393dte

fr lmi t392dce

fr lmi type

timer-hold

display fr map

Use display fr map to display Frame Relay address mapping.

Syntax

display fr map [ interface interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main or subinterface. If you specify a main interface, this command displays information for the main interface and its subinterfaces. If you specify a subinterface, this command displays information for the subinterface. If you do not specify an interface, this command displays information for all interfaces.

Usage guidelines

Based on the output from this command, you can determine whether the static address-to-DLCI maps are correct and whether dynamic address mapping is operating correctly.

Examples

# Display Frame Relay address mapping for all interfaces.

<Sysname> display fr map

Map information for interface Serial2/1/0 (DTE)

  DLCI: 100, IP InARP 100.100.1.1, Serial2/1/0

    Creation time: 2012/10/21 14:48:44, Status: Active

  DLCI: 200, IP InARP 100.100.1.1, Serial2/1/0

    Creation time: 2012/10/21 14:34:42, Status: Active

  DLCI: 300, IP 1.1.1.1, Serial2/1/0

    Creation time: 2012/10/21 15:03:35, Status: Active

Table 7 Command output

Field

Description

Map information for interface Serial2/1/0 (DTE)

Frame Relay address mapping for DTE interface Serial 2/1/0.

DLCI: 100, IP InARP 100.100.1.1, Serial2/1/0

The VC identified by DLCI 100 is mapped to the peer IP address 100.100.1.1 through InARP. The VC is configured on the interface Serial 2/1/0. If the InARP keyword is not displayed, the address-to-DLCI map is a static map manually configured.

Creation time: 2012/10/21 14:48:44

Time when the map was created.

Status: Active

State of the address-to-DLCI map:

·     Active.

·     Inactive.

The state of an address-to-DLCI map is the same as the state of the mapped VC.

 

Related commands

fr inarp

fr map ip

display fr pvc

Use display fr pvc to display information on Frame Relay PVCs and statistics about sent and received data.

Syntax

display fr pvc [ interface interface-type interface-number ] [ dlci dlci-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays information for the main interface and its subinterfaces. If you specify a subinterface, this command displays information for the subinterface. If you do not specify an interface, this command displays information for all interfaces.

dlci dlci-number: Specifies a PVC by its DLCI in the range of 16 to 1007. If you specify a PVC, this command displays detailed information about the PVC. If you do not specify a PVC, this command displays brief information about PVCs. In addition to the brief information, the detailed information includes Frame Relay traffic management information.

Examples

# Display brief information on all Frame Relay PVCs and statistics about sent and received data.

<Sysname> display fr pvc

PVC information for interface Serial2/1/0 (DTE, physically up)

  DLCI: 100  Type: Dynamic  Interface: Serial2/1/0

    Encapsulation: IETF  Broadcast

    Creation time: 2012/04/01 23:55:39  Status: Active

    Input: 0 packets, 0 bytes, 0 dropped

    Output: 0 packets, 0 bytes, 0 dropped

  DLCI: 102  Type: Static  Interface: Serial2/1/0.1

    Encapsulation: Nonstandard

    Creation time: 2012/04/01 23:56:14  Status: Active

    Input: 0 packets, 0 bytes, 0 dropped

    Output: 0 packets, 0 bytes, 0 dropped

# Display detailed information on the PVC identified by DLCI 100 and statistics about data sent and received on the PVC.

<Sysname> display fr pvc dlci 100

PVC information for interface Serial2/1/0 (DTE, physically up)

  DLCI: 100  Type: Dynamic  Interface: Serial2/1/0

    Encapsulation: IETF  Broadcast

    Creation time: 2012/04/01 23:55:39  Status: Active

    Input: 0 packets, 0 bytes, 0 dropped

    Output: 0 packets, 0 bytes, 0 dropped

    DE list: 3  DE set packets: 0

    Traffic policing: Active

      CIR ALLOW: 56000 bps  CBS: 56000 bits  EBS: 56000 bits

      Input: 0 packets, 0 bytes, 0 dropped, 0 set DE packets

    Traffic shaping: Inactive

      CIR ALLOW: 56000 bps  CIR: 56000 bps

      CBS: 56000 bits  EBS: 56000 bits

      Current CIR: 56000 bps

      Output: 0 packets, 0 bytes, 0 dropped packets

      Delayed: 0 packets, 0 bytes

      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

Table 8 Command output

Field

Description

PVC information for interface Serial2/1/0 (DTE, physically up)

Information about PVCs on the Frame Relay interface Serial 2/1/0. The interface is a DTE interface and is physically up.

The interface types include:

·     DTE.

·     DCE.

·     NNI.

The physical states include:

·     physically up.

·     physically down.

DLCI: 100, Type: Dynamic,  Interface: Serial2/1/0

The type of the PVC identified by DLCI 100 is Dynamic. It is created on Serial 2/1/0. The PVC types include:

·     Dynamic—The PVC is dynamically learned through LMI.

·     Static—The PVC is statically configured by using the fr map ip or fr dlci command.

Encapsulation: IETF  Broadcast

The encapsulation type of the PVC is IETF. The PVC allows broadcast packets.

The encapsulation types include:

·     IETF.

·     Nonstandard.

Creation time: 2012/1/04/01 23:55:39, Status: Active

Time when the PVC was created and the state of the PVC, which can be Active or Inactive.

Input: 0 packets, 0 bytes, 0 dropped

Number of received packets, number of received bytes, and number of dropped packets.

Output: 0 packets, 0 bytes, 0 dropped

Number of sent packets, number of sent bytes, and number of dropped packets.

DE list: 3  DE set packets: 0

DE list number and number of packets with the DE bit set.

Traffic policing: Inactive

Status of traffic policing:

·     Active.

·     Inactive.

Input : 0 packets, 0 bytes, 0 dropped, 0 set DE packets

Number of received packets, number of received bytes, number of dropped packets, and number of packets with the DE bit set.

Traffic shaping: Inactive

Status of traffic shaping:

·     Active.

·     Inactive.

Output: 0 packets, 0 bytes, 0 dropped packets

Number of sent packets, number of sent bytes, and number of dropped packets after traffic shaping is enabled.

Delayed: 0 packets, 0 bytes

Number of outgoing packets delayed and number of outgoing bytes delayed.

 

Related commands

broadcast

fr dlci

fr encapsulation

fr interface-type

fr map ip

reset fr pvc

fr compression iphc enable

Use fr compression iphc enable to enable Frame Relay IPHC on a Frame Relay interface or VC.

Use undo fr compression iphc enable to disable Frame Relay IPHC on a Frame Relay interface or VC.

Syntax

fr compression iphc enable [ nonstandard ]

undo fr compression iphc enable

Default

Frame Relay IPHC is disabled.

Views

Interface view

Frame Relay virtual circuit view

Predefined user roles

network-admin

Parameters

nonstandard: Specifies the nonstandard encapsulation type. Specify this keyword when the device is interoperating with third-party devices. This keyword supports RTP header compression (but not TCP header compression).

Usage guidelines

IPHC includes the following types:

·     RTP header compression—Compresses the IP/UDP/RTP header in packets.

·     TCP header compression—Compresses the TCP/IP header in packets.

Enabling/disabling IPHC enables/disables both RTP header compression and TCP header compression.

To make IPHC take effect on a link, you must enable Frame Relay IPHC on both ends of the link.

You can configure Frame Relay IPHC on either an interface or VC. The setting on an interface takes effect on all VCs of the interface. The setting on a VC takes effect only on the VC. When the interface setting is different from the VC setting, the VC setting takes effect.

When the encapsulation type is IETF, IPHC negotiation is triggered after you enable IPHC. IPHC takes effect only if IPHC negotiation succeeds.

When the encapsulation type is nonstandard, IPHC takes effect without negotiation. In this case, the encapsulation type must be nonstandard on both ends of the link.

Compression does not stop after you disable IPHC. To stop compression on an interface or PVC, you must also execute the shutdown/undo shutdown command sequence on the interface or PVC.

Examples

# Enable Frame Relay IPHC on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr compression iphc enable

# Enable Frame Relay IPHC on the VC with DLCI 100 on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 100

[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable

Related commands

fr encapsulation

fr compression iphc rtp-connections

Use fr compression iphc rtp-connections to set the maximum number of RTP header-compression connections allowed on a Frame Relay interface or VC.

Use undo fr compression iphc rtp-connections to restore the default.

Syntax

fr compression iphc rtp-connections number

undo fr compression iphc rtp-connections

Default

The maximum number of RTP header-compression connections is 16.

Views

Interface view

Frame Relay virtual circuit view

Predefined user roles

network-admin

Parameters

number: Specifies the maximum number of RTP header-compression connections allowed, in the range of 3 to 1000. When this argument is less than or equal to 256, packets are compressed in COMPRESSED_RTP_8 format. When this argument is greater than 256, packets are compressed in COMPRESSED_RTP_16 format.

Usage guidelines

RTP is a connection-oriented protocol and can carry many RTP connections on one link. The compression algorithm maintains information for each RTP header-compression connection. To save memory resources, you can use this command to specify the maximum number of RTP header-compression connections allowed. For example, if you specify the maximum number as 3, packets of the fourth RTP connection are not compressed.

The maximum number of RTP header-compression connections configured on an interface is inherited by all VCs of the interface. If you set a different maximum number on a VC of the interface, the setting on the VC takes effect.

You can configure this command on an interface or PVC only after you enable IPHC on the interface or PVC. The configuration takes effect on an interface or PVC after you execute the shutdown/undo shutdown command sequence on the interface or PVC. After you disable IPHC, the configuration is deleted.

Examples

# Set the maximum number of RTP header-compression connections to 200 for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr compression iphc enable

[Sysname-Serial2/1/0] fr compression iphc rtp-connections 200

# Set the maximum number of RTP header-compression connections to 200 for the VC with DLCI 100 on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 100

[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable

[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc rtp-connections 200

Related commands

fr compression iphc enable

fr compression iphc tcp-connections

Use fr compression iphc tcp-connections to set the maximum number of TCP header-compression connections allowed on a Frame Relay interface or VC.

Use undo fr compression iphc tcp-connections to restore the default.

Syntax

fr compression iphc tcp-connections number

undo fr compression iphc tcp-connections

Default

The maximum number of TCP header-compression connections is 16.

Views

Interface view

Frame Relay virtual circuit view

Predefined user roles

network-admin

Parameters

number: Specifies the maximum number of TCP header-compression connections allowed, in the range of 3 to 256.

Usage guidelines

TCP is a connection-oriented protocol and can carry many TCP connections on one link. The compression algorithm maintains information for each TCP header-compression connection. To save memory resources, you can use this command to specify the maximum number of TCP header-compression connections allowed. For example, if you specify the maximum number as 3, packets of the fourth TCP connection are not compressed.

The maximum number of TCP header-compression connections configured on an interface is inherited by all VCs of the interface. If you set a different maximum number on a VC of the interface, the setting on the VC takes effect.

You can configure this command on an interface or PVC only after you enable IPHC without specifying the nonstandard keyword on the interface or PVC. The configuration takes effect on an interface or PVC after you execute the shutdown/undo shutdown command sequence on the interface or PVC. After you disable IPHC or re-enable IPHC with the nonstandard keyword, the configuration is deleted.

Examples

# Set the maximum number of TCP header-compression connections to 200 for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr compression iphc enable

[Sysname-Serial2/1/0] fr compression iphc tcp-connections 200

# Set the maximum number of TCP header-compression connections to 200 for the VC with DLCI 100 on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 100

[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable

[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc tcp-connections 200

Related commands

fr compression iphc enable

fr compression stac enable

Use fr compression stac enable to enable Frame Relay STAC compression on a Frame Relay VC.

Use undo fr compression stac enable to disable Frame Relay STAC compression on a Frame Relay VC.

Syntax

fr compression stac enable

undo fr compression stac enable

Default

Frame Relay STAC compression is disabled on a Frame Relay VC.

Views

Frame Relay virtual circuit view

Predefined user roles

network-admin

Usage guidelines

To make STAC compression take effect on a PVC, you must enable STAC compression on both ends of the PVC.

STAC compression works only when the encapsulation type is IETF on both ends of a PVC. If the encapsulation type is not IETF when you enable STAC compression, the system automatically changes the encapsulation type to IETF.

Frame Relay IPHC and STAC compression are mutually exclusive.

Examples

# Enable Frame Relay STAC compression on the VC with DLCI 100 on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 100

[Sysname-Serial2/1/0-fr-dlci-100]fr compression stac enable

fr dlci

Use fr dlci to create a VC and enter its view, or enter the view of an existing VC.

Use undo fr dlci to delete a VC.

Syntax

fr dlci dlci-number

undo fr dlci [ dlci-number ]

Default

No VCs exist.

Views

Interface view (main interface or subinterface view)

Predefined user roles

network-admin

Parameters

dlci-number: Specifies a VC by its DLCI in the range 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.

Usage guidelines

The undo form of this command deletes all VCs if you do not specify the dlci-number argument.

The DLCI of a VC must be unique on a main interface and all its subinterfaces.

On a main DCE or NNI Frame Relay interface or subinterface, you must manually create VCs.

On a main DTE interface, the device can automatically create VCs according to the settings received from the DCE side. If you create VCs manually, make sure the DLCIs of the VCs are the same as those used on the DCE side.

On a DTE subinterface, you must manually create VCs.

When a DCE interface and an NNI interface perform LMI negotiation, the VC information is transmitted. When too many VCs are configured on an interface, the negotiation packet carrying the PVC information exceeds the maximum frame length allowed on the interface. In this case, the LMI negotiation fails.

Examples

# Create a VC with DLCI 100 on the Frame Relay interface (Serial 2/1/0).

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 100

[Sysname-Serial2/1/0-fr-dlci-100]

fr encapsulation

Use fr encapsulation to configure the encapsulation type for a Frame Relay interface or VC.

Use undo fr encapsulation to restore the default.

Syntax

fr encapsulation { ietf | nonstandard }

undo fr encapsulation

Default

The encapsulation type is IETF on a Frame Relay interface. The encapsulation type of a VC is the same as that configured on its Frame Relay interface.

Views

Interface view

Frame Relay virtual circuit view

Predefined user roles

network-admin

Parameters

ietf: Specifies the IETF encapsulation type.

nonstandard: Specifies the nonstandard encapsulation type.

Usage guidelines

The Frame Relay encapsulation types include:

·     IETF—The IETF encapsulation type conforms to RFC 1490.

·     Nonstandard—The nonstandard encapsulation type is compatible with dedicated encapsulation types of mainstream routers.

When a Frame Relay interface is configured with an encapsulation type:

·     The interface sends packets encapsulated in this type.

·     The interface can recognize packets encapsulated in either type.

For the local end and the peer to communicate:

·     If the peer can recognize packets in either type, you can set different encapsulation types on the two ends.

·     If the peer cannot recognize packets in either type,, you must set the same encapsulation type on the two ends.

By default, a VC uses the encapsulation type configured on its Frame Relay interface. The encapsulation type configured for a VC takes precedence over the encapsulation type configured on its Frame Relay interface.

If a VC is enabled with STAC compression, its encapsulation type can only be IETF.

Examples

# Enable Frame Relay encapsulation on Serial 2/1/0, and set the encapsulation type to nonstandard.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr encapsulation nonstandard

# Set the Frame Relay encapsulation type to IETF on the VC with DLCI 200.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr dlci 200

[Sysname-Serial2/1/0-fr-dlci-200] fr encapsulation ietf

fr fragment enable

Use fr fragment enable to enable Frame Relay FRF.12 fragmentation on a Frame Relay interface.

Use undo fr fragment enable to disable Frame Relay FRF.12 fragmentation on a Frame Relay interface.

Syntax

fr fragment enable

undo fr fragment enable

Default

Frame Relay FRF.12 fragmentation is disabled on a Frame Relay interface.

Views

Interface view

Predefined user roles

network-admin

Usage guidelines

This command enables FRF.12 fragmentation on all PVCs of an interface and its subinterfaces.

FRF.12 fragmentation enabled by using this command is end-to-end type.

This command and the fr traffic-shaping command are mutually exclusive on an interface. For more information about Frame Relay traffic shaping, see ACL and QoS Configuration Guide.

Examples

# Enable Frame Relay FRF.12 fragmentation on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr fragment enable

fr fragment size

Use fr fragment size to set the fragment size allowed on a Frame Relay interface.

Use undo fr fragment size to restore the default.

Syntax

fr fragment size size

undo fr fragment size

Default

The fragment size allowed on a Frame Relay interface is 45 bytes.

Views

Interface view

Predefined user roles

network-admin

Parameters

size: Specifies the fragment size in the range of 16 to 1600 bytes.

Examples

# Set the fragment size to 300 bytes on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr fragment size 300

fr inarp

Use fr inarp to enable Frame Relay InARP on a Frame Relay interface.

Use undo fr inarp to disable Frame Relay InARP on a Frame Relay interface.

Syntax

fr inarp ip [ dlci-number ]

undo fr inarp ip [ dlci-number ]

Default

Frame Relay InARP is enabled on a Frame Relay interface.

Views

Interface view

Predefined user roles

network-admin

Parameters

ip: Performs inverse address resolution for IPv4 addresses.

dlci-number: Specifies a VC by its DLCI number. The value range for this argument is 16 to 1007. If you do not specify a VC, all VCs on the interface and on all its subinterfaces are specified.

Usage guidelines

When Frame Relay sends data over an interface, the peer IP addresses must be mapped to the local DLCIs. The address-to-DLCI mapping can be configured automatically through InARP or manually.

If you enable or disable InARP on a Frame Relay interface without specifying a VC, InARP is enabled or disabled on the following VCs:

·     All VCs on the Frame Relay interface.

·     All VCs on each subinterface of the Frame Relay interface.

Examples

# Enable InARP on all VCs of the Frame Relay interface Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr inarp ip

Related commands

display fr inarp

fr inarp interval

fr inarp interval

Use fr inarp interval to set the InARP request interval during an InARP learning process.

Use undo fr inarp interval to restore the default.

Syntax

fr inarp interval interval

undo fr inarp interval

Default

The InARP request interval during an InARP learning process is 60 seconds.

Views

Interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the InARP request interval during an InARP learning process. The value range for this argument is 15 to 300 seconds.

Usage guidelines

The InARP request interval takes effect only when InARP is enabled.

Examples

# Set the InARP request interval during an InARP learning process to 15 seconds on the Frame Relay interface Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr inarp interval 15

Related commands

display fr inarp

fr inarp

fr interface-type

Use fr interface-type to set the type of a Frame Relay interface.

Use undo fr interface-type to restore the default.

Syntax

fr interface-type { dce | dte | nni }

undo fr interface-type

Default

The type of a Frame Relay interface is DTE.

Views

Interface view

Predefined user roles

network-admin

Parameters

dce: Specifies DCE.

dte: Specifies DTE.

nni: Specifies NNI.

Examples

# Set the type of the Frame Relay interface Serial 2/1/0 to DCE.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr interface-type dce

fr ipv6 ind

Use fr ipv6 ind to enable IND for dynamic address mapping on a Frame Relay interface.

Use undo fr ipv6 ind to disable IND for dynamic address mapping on a Frame Relay interface.

Syntax

fr ipv6 ind [ dlci-number ]

undo fr ipv6 ind [ dlci-number ]

Default

IND is disabled on a Frame Relay interface.

Views

Interface view

Predefined user roles

network-admin

Parameters

dlci-number: Specifies a VC by its DLCI number in the range of 16 to 1007. If you do not specify a VC, all VCs on the interface and on all its subinterfaces are specified.

Usage guidelines

IND automatically creates IPv6 address-to-DLCI maps on an interface.

If you enable or disable IND on a Frame Relay interface without specifying a VC, IND is enabled or disabled on the following VCs:

·     All VCs on the Frame Relay interface.

·     All VCs on each subinterface of the Frame Relay interface.

Examples

# Enable IND for all VCs on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr ipv6 ind

fr lmi n391dte

Use fr lmi n391dte to set the DTE-side N391 counter.

Use undo fr lmi n391dte to restore the default.

Syntax

fr lmi n391dte n391-value

undo fr lmi n391dte

Default

The DTE-side N391 counter is 6.

Views

Interface view

Predefined user roles

network-admin

Parameters

n391-value: Sets the DTE-side N391 counter in the range of 1 to 255.

Usage guidelines

This command is available on DTE and NNI interfaces.

A DTE sends status enquiry messages at an interval set by the T391 timer to a DCE. The status enquiry messages include link integrity verification enquiry messages and full status enquiry messages. The ratio of sent link integrity verification enquiry messages to sent full status enquiry messages is (N391–1):1.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DTE. Set the N391 counter to 10.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] fr lmi n391dte 10

fr lmi n392dce

Use fr lmi n392dce to set the DCE-side N392 counter.

Use undo fr lmi n392dce to restore the default.

Syntax

fr lmi n392dce n392-value

undo fr lmi n392dce

Default

The DCE-side N392 counter is 3.

Views

Interface view

Predefined user roles

network-admin

Parameters

n392-value: Sets the DCE-side N392 counter in the range of 1 to 10.

Usage guidelines

This command is available on DCE and NNI interfaces.

A DCE requires a DTE to send a status enquiry message at an interval set by the T392 timer. If the DCE has not received a status enquiry message when the T392 timer expires, the error counter on the DCE increments by one.

The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DCE considers the physical link and all VCs unavailable and will not use them to forward packets.

N392 must be less than N393 on the DCE side.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DCE. Set N392 to 5 and N393 to 6.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dce

[Sysname-Serial2/1/0] fr lmi n392dce 5

[Sysname-Serial2/1/0] fr lmi n393dce 6

fr lmi n392dte

Use fr lmi n392dte to set the DTE-side N392 counter.

Use undo fr lmi n392dte to restore the default.

Syntax

fr lmi n392dte n392-value

undo fr lmi n392dte

Default

The DTE-side N392 counter is 3.

Views

Interface view

Predefined user roles

network-admin

Parameters

n392-value: Sets the DTE-side N392 counter in the range of 1 to 10.

Usage guidelines

This command is available on DTE and NNI interfaces.

A DTE sends a status enquiry message at an interval to a DCE to request the link status. When the DCE receives a status enquiry message, the DCE immediately sends a status message. If the DTE has not received the status message when the T391 timer expires, the error counter on the DTE increments by one.

The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DTE considers the physical link and all VCs unavailable and will not use them to forward packets.

N392 must be less than N393 on the DTE side.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DTE. Set N392 to 5 and N393 to 6.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] fr lmi n392dte 5

[Sysname-Serial2/1/0] fr lmi n393dte 6

fr lmi n393dce

Use fr lmi n393dce to set the DCE-side N393 counter.

Use undo fr lmi n393dce to restore the default.

Syntax

fr lmi n393dce n393-value

undo fr lmi n393dce

Default

The DCE-side N393 counter is 4.

Views

Interface view

Predefined user roles

network-admin

Parameters

n393-value: Sets the DCE-side N393 counter in the range of 1 to 10.

Usage guidelines

This command is available on DCE and NNI interfaces.

A DCE requires a DTE to send a status enquiry message at an interval set by the T392 timer. If the DCE has not received the status enquiry message when the T392 timer expires, the error counter on the DCE increments by one.

The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DCE considers the physical link and all VCs unavailable and will not use them to forward packets.

N392 must be less than N393 on the DCE side.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DCE. Set N392 to 5 and N393 to 6.

<Sysname> system-view

[Sysname] interface serial2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dce

[Sysname-Serial2/1/0] fr lmi n392dce 5

[Sysname-Serial2/1/0] fr lmi n393dce 6

fr lmi n393dte

Use fr lmi n393dte to set the DTE-side N393 counter.

Use undo fr lmi n393dte to restore the default.

Syntax

fr lmi n393dte n393-value

undo fr lmi n393dte

Default

The DTE-side N393 counter is 4.

Views

Interface view

Predefined user roles

network-admin

Parameters

n393-value: Sets the DTE-side N393 counter in the range of 1 to 10.

Usage guidelines

This command is available on DTE and NNI interfaces.

A DTE sends status enquiry messages at an interval to a DCE to request the link status. When the DCE receives a status enquiry message, the DCE immediately sends a status message. If the DTE has not received the status message when the T391 timer expires, the error counter on the DTE increments by one.

The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DTE considers the physical link and all VCs unavailable and will not use them to forward packets.

N392 must be less than N393 on the DTE side.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DTE. Set N392 to 5 and N393 to 6.

<Sysname> system-view

[Sysname] interface serial2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] fr lmi n392dte 5

[Sysname-Serial2/1/0] fr lmi n393dte 6

fr lmi t392dce

Use fr lmi t392dce to set the DCE-side T392 timer.

Use undo fr lmi t392dce to restore the default.

Syntax

fr lmi t392dce t392-value

undo fr lmi t392dce

Default

The DCE-side T392 timer is 15 seconds.

Views

Interface view

Predefined user roles

network-admin

Parameters

t392-value: Sets the DCE-side T392 timer in the range of 5 to 30 seconds.

Usage guidelines

This command is available on DCE and NNI interfaces.

The DCE-side T392 timer defines the longest period that a DCE can wait for a status enquiry message.

The DCE-side T392 timer must be greater than the DTE-side T391 timer set by using the timer-hold command.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DCE. Set the T392 timer to 10 seconds.

<Sysname> system-view

[Sysname] interface serial2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dce

[Sysname-Serial2/1/0] fr lmi t392dce 10

fr lmi type

Use fr lmi type to configure the Frame Relay LMI protocol type.

Use undo fr lmi type to restore the default.

Syntax

fr lmi type { ansi | nonstandard | q933a }

undo fr lmi type

Default

The Frame Relay LMI protocol type is q933a.

Views

Interface view

Predefined user roles

network-admin

Parameters

ansi: Specifies the standard LMI protocol defined in ANSI T1.617 Annex D.

nonstandard: Specifies the nonstandard compatible LMI protocol.

q933a: Specifies the standard LMI protocol defined in Q.933 Annex A.

Usage guidelines

The LMI protocol maintains the Frame Relay PVC table. It can perform the following operations:

·     Notifies the addition of a PVC.

·     Detects the deletion of a PVC.

·     Monitors PVC status changes.

·     Verifies link integrity.

The system usually supports the following LMI protocols:

·     ITU-T Q.933 Annex A.

·     ANSI T1.617 Annex D.

·     Nonstandard compatible LMI protocol.

Examples

# Configure the Frame Relay LMI type as nonstandard compatible protocol on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr lmi type nonstandard

fr map

Use fr map to create a static address-to-DLCI map.

Use undo fr map to delete a static address-to-DLCI map.

Syntax

fr map ip { ip-address | default } dlci-number

fr map ipv6 { ipv6-address | default } dlci-number

undo fr map ip { ip-address | default } dlci-number

undo fr map ipv6 { ipv6-address | default } dlci-number

Default

No static address-to-DLCI maps exist.

Views

Interface view (main interface view or P2MP subinterface view)

Predefined user roles

network-admin

Parameters

ip-address: Specifies the peer IPv4 address.

ipv6-address: Specifies the peer IPv6 address.

default: Creates a default address-to-DLCI map.

dlci-number: Specifies the local VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 5 and 1008 through 1023 are reserved.

Usage guidelines

An address-to-DLCI map can be created automatically by using InARP or IND, or created manually.

·     InARP or IND is suitable for a complex network where the peer devices also support InARP or IND.

·     As a best practice, create address-to-DLCI maps manually when the number of peer hosts is small or when default routes exist.

The IPv4 or IPv6 address in an address-to-DLCI map must be a valid unicast IPv4 or IPv6 address.

When the VC specified in this command does not exist, the VC is automatically created.

Up to one default address-to-DLCI map can be configured on one interface.

Only one address-to-DLCI map can be configured for one IPv4 or IPv6 address on one interface.

Examples

# Create a static address-to-DLCI map on Serial 2/1/0 to map the VC with DLCI 50 to the peer IP address 202.38.163.252.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] fr map ip 202.38.163.252 50

Related commands

display fr map

ipv6 ind holdtime

Use ipv6 ind holdtime to set the IND request interval during the IND learning process.

Use undo ipv6 ind holdtime to restore the default.

Syntax

ipv6 ind holdtime seconds

undo ipv6 ind holdtime

Default

The IND request interval during the IND learning process is 30 seconds.

Views

Interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies the IND request interval in the range of 10 to 120 seconds.

Usage guidelines

This command takes effect only when IND is enabled.

Examples

# Set the type of the Frame Relay interface Serial 2/1/0 to DTE, and set the IND request interval to 15 seconds for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] ipv6 ind holdtime 15

ipv6 ind solicitation retrans-timer

Use ipv6 ind solicitation retrans-timer to set the interval between IND requests that are sent continuously.

Use undo ipv6 ind solicitation retrans-timer to restore the default.

Syntax

ipv6 ind solicitation retrans-timer seconds

undo ipv6 ind solicitation retrans-timer

Default

The interval between IND requests that are sent continuously is 1 second.

Views

Interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies the interval between IND requests that are sent continuously, in the range of 1 to 5 seconds.

Usage guidelines

An interface that fails to receive IND responses within the IND request interval continuously sends IND requests up to three times at the interval set by using this command.

Examples

# Set the type of the Frame Relay interface Serial 2/1/0 to DTE, and set the interval between continuous IND requests to 2 seconds for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] ipv6 ind solicitation retrans-timer 2

link-protocol fr

Use link-protocol fr to enable Frame Relay encapsulation on an interface.

Use undo link-protocol fr to restore the default.

Syntax

link-protocol fr

undo link-protocol fr

Default

PPP encapsulation is enabled on all interfaces except Ethernet interfaces, ATM interfaces, and VLAN interfaces.

 

 

NOTE:

The following routers do not support ATM interfaces:

·     MSR3620-X1.

·     MSR3620-X1-XS.

·     MSR3640-X1.

·     MSR3640-XS.

·     MSR3640-X1-HI.

·     MSR3660-XS.

 

Views

Interface view

Predefined user roles

network-admin

Examples

# Enable Frame Relay encapsulation on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

reset fr compression iphc

Use reset fr compression iphc to clear Frame Relay IPHC statistics.

Syntax

reset fr compression iphc { rtp | tcp } [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

User view

Predefined user roles

network-admin

Parameters

rtp: Clears RTP header compression statistics.

tcp: Clears TCP header compression statistics.

interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command clears IPHC statistics for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. Before you specify a VC, you must specify an interface. If you do not specify a VC, this command clears IPHC statistics for all VCs on an interface.

Examples

# Clear IPHC statistics for all interfaces.

<Sysname> reset fr compression iphc

Related commands

display fr compression iphc

reset fr inarp

Use reset fr inarp to clear dynamic IPv4 address-to-DLCI maps.

Syntax

reset fr inarp [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

User view

Predefined user roles

network-admin

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface.

·     If you specify a main interface, this command clears information for the main interface and its subinterfaces.

·     If you specify a subinterface, this command clears information for the subinterface.

·     If you do not specify an interface, this command clears information for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not clear IPv4 address mapping for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not clear IPv4 address mapping for the VC.

·     If you specify only an interface, this command clears IPv4 address mapping for all VCs on the interface.

Usage guidelines

In some situations, for example, when the network topology changes, the dynamic address-to-DLCI maps will become invalid. Before dynamic address-to-DLCI maps are established again, clear all dynamic address-to-DLCI maps.

Examples

# Clear all dynamic IPv4 address-to-DLCI maps.

<Sysname> reset fr inarp

Related commands

fr inarp

reset fr ipv6 ind

Use reset fr ipv6 ind to clear dynamic IPv6 address-to-DLCI maps.

Syntax

reset fr ipv6 ind [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

User view

Predefined user roles

network-admin

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface.

·     If you specify a main interface, this command clears information for the main interface and its subinterfaces.

·     If you specify a subinterface, this command clears information for the subinterface.

·     If you do not specify an interface, this command clears information for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.

·     If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not clear IPv6 address mapping for the VC.

·     If you specify a subinterface and a VC that is not on the subinterface, this command does not clear IPv6 address mapping for the VC.

·     If you specify only an interface, this command clears IPv6 address mapping for all VCs on the interface.

Examples

# Clear all dynamic IPv6 address-to-DLCI maps.

<Sysname> reset fr ipv6 ind

reset fr pvc

Use reset fr pvc to clear statistics for PVCs.

Syntax

reset fr pvc [ interface interface-type interface-number [ dlci dlci-number ] ]

Views

User view

Predefined user roles

network-admin

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command clears statistics for the main interface and its subinterfaces. If you specify a subinterface, this command clears statistics for the subinterface. If you do not specify an interface, this command clears statistics for all interfaces.

dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.

Examples

# Clear statistics for all PVCs on Serial 2/1/0.

<Sysname> reset fr pvc interface serial 2/1/0

snmp-agent trap enable fr

Use snmp-agent trap enable fr to enable SNMP notifications for Frame Relay.

Use undo snmp-agent trap enable fr to disable SNMP notifications for Frame Relay.

Syntax

snmp-agent trap enable fr

undo snmp-agent trap enable fr

Default

SNMP notifications are disabled for Frame Relay.

Views

System view

Predefined user roles

network-admin

Examples

# Enable SNMP notifications for Frame Relay.

<Sysname> system-view

[Sysname] snmp-agent trap enable fr

timer-hold

Use timer-hold to set the DTE-side T391 timer.

Use undo timer-hold to restore the default.

Syntax

timer-hold seconds

undo timer-hold

Default

The DTE-side T391 timer is 10 seconds.

Views

Interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies the DTE-side T391 timer in the range of 0 to 32767 seconds. The value 0 indicates that the LMI protocol is disabled.

Usage guidelines

This command is available on DTE and NNI interfaces.

The DTE-side T391 timer defines the interval at which the DTE sends status enquiry messages.

The DTE-side T391 timer must be smaller than the DCE-side T392 timer.

Examples

# Set the type of the Frame Relay interface (Serial 2/1/0) to DTE. Set the T391 timer to 15 seconds.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol fr

[Sysname-Serial2/1/0] fr interface-type dte

[Sysname-Serial2/1/0] timer-hold 15

Multilink Frame Relay commands

bandwidth

Use bandwidth to set the expected bandwidth for an MFR interface.

Use undo bandwidth to restore the default.

Syntax

bandwidth bandwidth-value

undo bandwidth

Default

The expected bandwidth (in kbps) for an MFR interface is the interface baud rate divided by 1000.

Views

MFR 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 1000 kbps for MFR4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] bandwidth 1000

default

Use default to restore the default settings for an MFR interface.

Syntax

default

Views

MFR interface view

Predefined user roles

network-admin

Usage guidelines

CAUTION

CAUTION:

The default command might interrupt ongoing network services. Make sure you are fully aware of the impact of this command when you execute it on a live network.

 

This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands. Then use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.

Examples

# Restore the default settings for MFR4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] 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 description of an MFR interface is interface name Interface, for example, MFR4 Interface.

Views

MFR interface view

Predefined user roles

network-admin

Parameters

text: Specifies a description, a case-sensitive string of 1 to 255 characters.

Examples

# Configure the description of MFR4 as mfr4-interface.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] description mfr4-interface

display interface mfr

Use display interface mfr to display MFR interface information.

Syntax

display interface [ mfr [ interface-number ] ] [ brief [ description | down ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

mfr [ interface-number ]: Specifies MFR interfaces. If you do not specify the mfr keyword, this command displays information about all interfaces supported by the device. If you specify the mfr keyword but not the interface-number argument, this command displays information about all MFR interfaces.

brief: Displays brief information about interfaces. If you do not specify this keyword, the command displays detailed information about interfaces.

description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.

down: Displays information about the interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.

Examples

# Display detailed information about MFR4.

<Sysname> display interface mfr 4

MFR4

Current state: DOWN

Line protocol state: DOWN

Description: MFR4 Interface

Bandwidth: 0kbps

Maximum transmission unit: 1500

Hold timer: 10 seconds, retry times: 5

Internet protocol processing: Disabled

Link layer protocol is FR IETF

  LMI DLCI is 0, LMI type is Q.933a, frame relay DTE

  LMI status enquiry sent 0, LMI status received 0

  LMI status timeout 0, LMI message discarded 0

Physical: MFR

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 clearing of counters: Never

Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Input: 0 packets, 0 bytes, 0 dropps

Output: 0 packets, 0 bytes, 0 dropps

Table 9 Command output

Field

Description

Current state

Physical state and administrative 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:

·     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.

Hold timer

Interval for the interface to send keepalive messages.

retry times

Maximum number of times that the interface can resend a hello message when waiting for a hello acknowledgement.

Internet protocol processing: Disabled

The interface is not assigned an IP address and cannot process IP packets.

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 3IP Services Configuration Guide.

·     BOOTP-allocatedBOOTP allocated IP address. For more information, see BOOTP client configuration in Layer 3IP Services Configuration Guide.

·     PPP-negotiated—IP address assigned by a PPP server during PPP negotiation. For more information, see PPP configuration in Layer 2WAN 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 2WAN 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.

Link layer protocol is FR IETF

Encapsulation type of the interface:

·     IETF.

·     Nonstandard.

LMI DLCI is 0, LMI type is Q.933a, Frame Relay DTE

DLCI number used by LMI, LMI type, and port type.

Q.933a LMI and ANSI LMI use DLCI 0, and nonstandard LMI uses DLCI 1023.

LMI status enquiry sent 0, LMI status received 0

Number of sent status enquiry messages and number of received status messages.

LMI status timeout 0, LMI message discarded 0

Number of status messages that timed out and number of discarded messages.

Physical

Physical type of the interface.

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

Statistics on the packets of the following interface output queues:

·     Urgent queue.

·     Protocol queue.

·     FIFO queue.

Last clearing of counters: Never

Time when the interface statistics were last cleared.

Never indicates that the interface statistics have never been cleared since device startup.

Last 300 seconds input rate: 0 bytes/sec, 0 packets/sec

Last 300 seconds output rate: 0 bytes/sec, 0 packets/sec

Average input rate of the interface in the last 5 minutes.

Average output rate of the interface in the last 5 minutes.

Input: 0 packets, 0 bytes, 0 dropps

Number of incoming packets, number of incoming bytes, and number of incoming packets discarded.

Output: 0 packets, 0 bytes, 0 dropps

Number of outgoing packets, number of outgoing bytes, and number of outgoing packets discarded.

 

# Display brief information about MFR4.

<Sysname> display interface mfr 4 brief

Brief information on interface(s) under route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface            Link Protocol Main IP         Description

MFR4                 DOWN DOWN     --

# Display brief information about the MFR interfaces in physically down state.

<Sysname> display interface mfr brief down

Brief information on interface(s) under route mode:

Link: ADM - administratively down; Stby - standby

Interface           Link Cause

MFR4                ADM  Administratively

Table 10 Command output

Field

Description

Brief information on interface(s) under route mode

Brief information about Layer 3 interfaces.

Interface

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. This value is typical of null interfaces and loopback interfaces.

Description

Partial or complete interface description set by using the description command:

·     If you do not specify the description keyword for the display interface brief command, this field displays only the first 27 characters of the interface description.

·     If you specify the description keyword for the display interface brief command, this field displays the complete interface description.

Cause

Cause for the physical link state of an interface to be DOWN:

·     Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty).

·     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.

 

Related commands

fr interface-type

fr lmi type

timer-hold

display mfr

Use display mfr to display information about MFR bundles and bundle links.

Syntax

display mfr [ interface interface-type interface-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. The specified interface must be a main interface (MFR interface or physical interface).

verbose: Displays detailed information, including the number of control messages sent and received. If you do not specify this keyword, the command displays only configuration and status information.

Usage guidelines

If you specify an MFR interface without the verbose keyword, this command displays the configuration and status information for the specified bundle and all its bundle links.

If you specify a physical interface without the verbose keyword, this command displays the configuration and status information for the specified bundle link and its bundle.

If you specify an MFR interface with the verbose keyword, this command displays detailed information about the specified n MFR interface and all its bundle links.

If you specify a physical interface with the verbose keyword, this command displays detailed information about the specified bundle link and its bundle.

Examples

# Display the configuration and status information for all MFR bundles and bundle links.

<Sysname> display mfr

Bundle interface: MFR1  Bundle state: Up  Bundle class: A

  Bundle name: MFR1  Peer bundle name: MFR2

  Fragment: Enabled  MFR bundle fragment size: 222 bytes

    Original packets assembled/fragmented (input/output): 0/0

    Dropped fragments (input/output): 0/0

    Unassigned fragments: 0

  Bundle links:

    Serial2/1/0  Physical state: Up  Link state: Up  Link name: Serial2/1/0

Table 11 Command output

Field

Description

Bundle state

Operating state of the MFR interface:

·     UpThe interface is physically up.

·     DownThe interface is physically down.

·     Administratively downThe interface is administratively down.

Bundle class

Bandwidth class, which is fixed at class A. A class A bundle is brought up when one or more bundle links come up. The bundle goes down when the last bundle link is down.

Fragment

Indicates whether fragmentation is enabled.

MFR bundle fragment size

Maximum fragment size allowed for bundle links.

Original packets assembled/fragmentized (input/output)

Number of assembled packets on the bundle interface and number of unfragmented packets before being sent by the MFR interface.

Dropped fragments (input/output)

Number of incoming/outgoing packets dropped on the MFR interface.

Unassigned fragments

Number of fragments that have not been assembled.

Serial2/1/0  Physical state: Up  Link state: Up   Link name: Serial2/1/0

Information about a bundle link:

·     Physical layer state:

¡     Up.

¡     Down.

¡     Administratively down.

·     Link layer state:

¡     Add sentThe interface sent an Add_link message and started connection establishment.

¡     Ack rxThe interface received an Add_link acknowledgement and is expecting an Add_link message from the peer.

¡     Add rxThe interface received an Add_link message and is expecting an Add_link acknowledgement from the peer.

¡     UpThe bundle link was successfully negotiated, and the interface can send frames.

¡     IdleThe bundle link was removed.

¡     DownThe bundle link was physically down.

¡     Down idleThe bundle link was physically down and removed.

·     The bundle link name is the name of the physical interface by default.

 

# Display detailed information about all MFR bundles and bundle links.

<Sysname> display mfr verbose

Bundle interface: MFR1  Bundle state: Up  Bundle class: A

  Bundle name: MFR1  Peer bundle name: MFR2

  Fragment: Enabled  MFR bundle fragment size: 222 bytes

    Original packets assembled/fragmented (input/output): 0/0

    Dropped fragments (input/output): 0/0

    Unassigned fragments: 0

  Bundle links:

    Serial2/1/0

      Link name: Serial2/1/0  Peer link name: Serial2/1/0

      Physical state: Up  Link state: Up  Cause code: None

      Timer: ACK 4 seconds  Hello 10 seconds

      Retry: Max 2  Current 0

      Bundle link negotiation statistics:

        Hello (Tx/Rx):           10/10 packets

        Hello_ack (Tx/Rx):       10/10 packets

        Add_link (Tx/Rx):        4/2 packets

        Add_link_ack (Tx/Rx):    2/1 packets

        Add_link_rej (Tx/Rx):    0/0 packets

        Remove_link (Tx/Rx):     0/0 packets

        Remove_link_ack (Tx/Rx): 0/0 packets

        Packets dropped (input/output): 0/0

      Bundle link fragment statistics:

        MFR fragments(input/output): 0/0

Table 12 Command output

Field

Description

Physical state

Operating state of the physical interface:

·     UP—The interface is physically up.

·     DOWN—The interface is physically down.

·     Administratively down—The interface has been administratively shut down.

Link state

Operating state of the link protocol on the bundle link:

·     Add sentThe interface sent an Add_link message and started connection establishment.

·     Ack rxThe interface received an Add_link acknowledgement and is expecting an Add_link message from the peer.

·     Add rxThe interface received an Add_link message and is expecting an Add_link acknowledgement from the peer.

·     UpThe bundle link was successfully negotiated, and the interface can send frames.

·     IdleThe bundle link was removed.

·     DownThe bundle link was physically down.

·     Down idleThe bundle link was physically down and removed.

Cause code

Cause code for a bundle link state:

·     NoneInitial state.

·     Ack timer expiredThe ACK timer expires.

·     Bundle link idleThe bundle link is not operational.

·     Inconsistent bundlePossible configuration mismatch detected.

·     Loopback detectedThe bundle link has detected a potential loopback condition.

·     Unexpected add_linkAn ADD_LINK message was received when the bundle link was in up state.

·     OtherGeneric failure cause described by text in diagnostic element.

Timer: Ack

Amount of time for which the bundle link waits for a hello or Add_link acknowledgement before retransmitting a hello message or an Add_link message (for initial synchronization).

Hello

Interval for the bundle link to send hello messages.

Retry: Max

Maximum number of times that the bundle link can retransmit a hello or Add_link message before receiving a hello or Add_link acknowledgement.

Current

Number of retries that have been made.

Hello (Tx/Rx)

Number of hello messages sent/received.

Hello_ack (Tx/Rx)

Number of hello acknowledgements sent/received.

Add_link_ack (Tx/Rx)

Number of Add_link acknowledgements sent/received.

An Add_link acknowledgement notifies the peer that the local end received an Add_link message.

Add_link_rej (Tx/Rx)

Number of Add_link reject messages sent/received.

An Add_link_rej message notifies the peer that the local end rejected an Add_link message.

Remove_link (Tx/Rx)

Number of Remove_link messages sent/received.

A Remove_link message notifies that the local end is removing a bundle link from the bundle.

Remove_link_ack (Tx/Rx)

Number of Remove_link acknowledgements sent/received.

A Remove_link acknowledgement notifies the peer that the local end received a Remove_link message.

Packets dropped (input/output)

Number of incoming/outgoing packets dropped.

MFR fragments (input/output)

Number of fragments sent/received by the bundle link.

 

Related commands

mfr bundle-name

mfr fragment size

mfr fragment enable

mfr link-name

mfr retry

mfr timer ack

mfr timer hello

fr mfr

Use fr mfr to bind a physical interface to an MFR interface.

Use undo fr mfr to remove all physical interfaces from an MFR interface.

Syntax

fr mfr mfr interface-number

undo fr mfr

Default

A physical interface is not bound to any MFR interface.

Views

Interface view

Predefined user roles

network-admin

Parameters

interface-number: Specifies an MFR interface by its number. The value range for this argument is 0 to 1023.

Usage guidelines

Before configuring this command, make sure the physical interface is enabled with MFR encapsulation. A maximum of 16 physical interfaces can be bound to an MFR interface.

You can bind a physical interface to a nonexistent MFR interface. However, the binding takes effect only when the MFR interface is created. When a physical interface is removed from an MFR interface, MFR settings on the physical interface are not deleted.

To remove a physical interface from an MFR interface, you can also configure a different encapsulation type from MFR by using the link-protocol command.

After MFR encapsulation is enabled on a physical interface, the interface cannot be configured with any FR-related commands except MFR commands. In addition, the queuing type on the interface can be configured only as FIFO. If the interface uses another queuing type before you enable MFR encapsulation, the interface is forced to use FIFO after you enable MFR encapsulation.

Make sure a physical interface is on the same card as the MFR interface to which the interface is to be bound.

Examples

# Enable MFR encapsulation on Serial 2/1/0, and bind it to MFR4.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

[Sysname-Serial2/1/0] fr mfr mfr 4

Related commands

link-protocol mfr

interface mfr

Use interface mfr to create an MFR interface or subinterface and enter its view, or enter the view of an existing MFR interface or subinterface.

Use undo interface mfr to delete an MFR interface or subinterface.

Syntax

interface mfr { interface-number | interface-number.subnumber [ p2mp | p2p ] }

undo interface mfr { interface-number | interface-number.subnumber }

Default

No MFR interface or subinterfaces exist.

Views

System view

Predefined user roles

network-admin

Parameters

interface-number: Specifies a number for the MFR interface. The value range for this argument is 0 to 1023.

interface-number.subnumber: Specifies a number for the MFR subinterface. The interface-number argument represents the number of the main MFR interface. The subnumber argument represents the number of the MFR subinterface. The value range for this argument is 0 to 1023.

p2mp: Specifies an MFR subinterface as a point-to-multipoint subinterface. By default, an MFR subinterface is a point-to-multipoint subinterface.

p2p: Specifies an MFR subinterface as a point-to-point subinterface.

Usage guidelines

Before creating an MFR subinterface, make sure the main MFR interface already exists.

An MFR interface is physically up when a minimum of one of its physical interfaces is up. An MFR interface is physically down when its last physical interface is down. The link layer state of an MFR interface is negotiated by using LMI messages.

Examples

# Create an interface named MFR4, and create a point-to-multipoint subinterface.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] quit

[Sysname] interface mfr 4.1

[Sysname-MFR4.1]

link-protocol mfr

Use link-protocol mfr to enable MFR encapsulation on an interface.

Syntax

link-protocol mfr

Default

PPP encapsulation is enabled on all interfaces except Ethernet interfaces, ATM interfaces, and VLAN interfaces.

 

 

NOTE:

The following routers do not support ATM interfaces:

·     MSR3620-X1.

·     MSR3620-X1-XS.

·     MSR3640-X1.

·     MSR3640-XS.

·     MSR3640-X1-HI.

·     MSR3660-XS.

 

Views

Interface view

Predefined user roles

network-admin

Examples

# Enable MFR encapsulation on Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

Related commands

fr mfr

mfr bundle-name

Use mfr bundle-name to set a bundle name for an MFR interface.

Use undo mfr bundle-name to restore the default.

Syntax

mfr bundle-name name

undo mfr bundle-name

Default

The bundle name is represented by MFR plus the bundle number, for example, MFR4.

Views

MFR interface view

Predefined user roles

network-admin

Parameters

name: Specifies a bundle name, a case-sensitive string of 1 to 49 characters.

Usage guidelines

You cannot set a bundle name as a string in the form of MFR + number.

Each MFR bundle has a bundle name, and the peer device can identify an MFR bundle by using the bundle name. Bundle names at the two ends of a bundle can be different. Bundle names must be unique on the same device.

The bundle names at both ends are used during the bundle link negotiation phase. After changing the bundle name of an MFR interface, you must execute the shutdown and undo shutdown commands on the interface to make the new bundle name take effect.

Examples

# Set the bundle name to bundle1 for MFR4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] mfr bundle-name bundle1

Related commands

display mfr

mfr fragment enable

Use mfr fragment enable to enable fragmentation on an MFR interface.

Use undo mfr fragment enable to disable fragmentation on an MFR interface.

Syntax

mfr fragment enable

undo mfr fragment enable

Default

Fragmentation is disabled on an MFR interface.

Views

MFR interface view

Predefined user roles

network-admin

Usage guidelines

With fragmentation enabled, an MFR interface fragments packets larger than the set fragment size and sends the fragments over bundle links in a round robin manner. The receiving end reassembles the fragments.

Examples

# Enable fragmentation on MFR 4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] mfr fragment enable

Related commands

display mfr

mfr fragment size

Use mfr fragment size to set the maximum fragment size allowed on an MFR interface.

Use undo mfr fragment size to restore the default.

Syntax

mfr fragment size size

undo mfr fragment size

Default

The maximum fragment size allowed on an MFR interface is 300 bytes.

Views

MFR interface view

Predefined user roles

network-admin

Parameters

size: Specifies the fragment size in the range of 60 to 1500 bytes.

Usage guidelines

With fragmentation enabled, an MFR interface fragments packets larger than the set fragment size and sends the fragments over bundle links in a round robin manner. This reduces the transmission delay of real-time packets.

Examples

# Set the maximum fragment size allowed on MFR 4 to 70 bytes.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] mfr fragment-size 70

Related commands

display mfr

mfr link-name

Use mfr link-name to set the bundle link name for a Frame Relay interface.

Use undo mfr link-name to restore the default.

Syntax

mfr link-name name

undo mfr link-name

Default

The bundle link name is the name of the physical interface, for example, Serial 2/1/0.

Views

Frame Relay interface view

Predefined user roles

network-admin

Parameters

name: Specifies the bundle link name, a case-sensitive string of 1 to 49 characters.

Usage guidelines

Use link-protocol mfr to enable MFR encapsulation on a Frame Relay interface before configuring the mfr link-name command on the interface.

The bundle link name identifies the bundle link to the peer device and enables the local device to determine which bundle links are bound to which bundles. The bundle link names in a bundle must be unique on the same device. The local and peer bundle link names can be different.

The local and peer bundle link names are used during the bundle link negotiation phase. After changing the bundle link name on an interface, you must execute the shutdown and undo shutdown commands on the interface to make the new bundle link name take effect.

Examples

# Set the bundle link name to bl1 for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

[Sysname-Serial2/1/0] mfr link-name bl1

Related commands

link-protocol mfr

mfr retry

Use mfr retry to set the maximum number of times that a bundle link can resend a hello message when waiting for a hello acknowledgement.

Use undo mfr retry to restore the default.

Syntax

mfr retry retries

undo mfr retry

Default

The maximum number of retries is 2.

Views

Frame Relay interface view

Predefined user roles

network-admin

Parameters

retries: Specifies the maximum number of retries, in the range 1 to 5.

Usage guidelines

A bundle link maintains link status by periodically sending hello messages to its peer end. If the bundle link sends a hello message but does not receive a hello acknowledgement, it will resend the hello message. If the bundle link still receives no acknowledgements after the maximum number of retries is reached, the system determines that the line protocol on the bundle link is down.

Before configuring this command, make sure you have used the link-protocol mfr command to enable MFR encapsulation on the Frame Relay interface.

Examples

# Set the maximum number of retries to 3 for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

[Sysname-Serial2/1/0] mfr retry 3

Related commands

link-protocol mfr

mfr timer ack

mfr timer hello

mfr timer ack

Use mfr timer ack to set the amount of time that a bundle link waits for a hello acknowledgment before resending the hello message.

Use undo mfr timer ack to restore the default.

Syntax

mfr timer ack seconds

undo mfr timer ack

Default

The wait time for a hello acknowledgment is 4 seconds.

Views

Frame Relay interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies the wait time in the range 1 to 10 seconds.

Usage guidelines

A bundle link maintains link status by periodically sending hello messages to its peer end. If the bundle link sends a hello message but does not receive a hello acknowledgement, it will resend the hello message. If the bundle link still receives no acknowledgements after the maximum number of retries is reached, the system determines that the line protocol on the bundle link is down.

Before configuring this command, make sure you have used the link-protocol mfr command to enable MFR encapsulation on the Frame Relay interface.

Examples

# Set the wait time to 6 seconds for Serial 2/1/0.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

[Sysname-Serial2/1/0] mfr timer ack 6

Related commands

link-protocol mfr

mfr timer hello

mfr retry

mfr timer hello

Use mfr timer hello to set the interval at which a bundle link sends hello messages.

Use undo mfr timer hello to restore the default.

Syntax

mfr timer hello seconds

undo mfr timer hello

Default

A bundle link sends hello messages at the interval of 10 seconds.

Views

Frame Relay interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies the interval in the range 1 to 180 seconds.

Usage guidelines

Before configuring this command, make sure you have used the link-protocol fr mfr command to enable MFR encapsulation on the Frame Relay interface.

Examples

# Configure Serial 2/1/0 to send a hello message every 15 seconds.

<Sysname> system-view

[Sysname] interface serial 2/1/0

[Sysname-Serial2/1/0] link-protocol mfr

[Sysname-Serial2/1/0] mfr timer hello 15

Related commands

link-protocol mfr

mfr retry

mfr timer ack

mfr timer lost-fragment

Use mfr timer lost-fragment to set the amount of time that an MFR interface waits for an expected fragment.

Use undo mfr timer lost-fragment to restore the default.

Syntax

mfr timer lost-fragment seconds

undo mfr timer lost-fragment

Default

An MFR interface waits for an expected fragment for 30 seconds before it declares the fragment lost.

Views

MFR interface view

Predefined user roles

network-admin

Parameters

seconds: Specifies a value for the wait timer, in the range of 1 to 255 seconds.

Usage guidelines

The receiving end buffers the fragments of a packet before receiving all fragments of the packet. If any fragments are missing, the received fragments stay in the buffer. This processing wastes buffer resources.

The wait timer starts when the receiving end receives the first fragment of a packet. When the wait timer expires, the receiving end checks whether all fragments are received. If not all fragments are received, the receiving end discards all received fragments of the packet to release buffer resources.

Examples

# Set the wait time to 20 seconds for MFR 4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] mfr timer lost-fragment 20

Related commands

mfr fragment enable

mfr window-size

Use mfr window-size to set the maximum number of fragments that can be held by the window used in the sliding window algorithm when an MFR interface reassembles received fragments.

Use undo mfr window-size to restore the default.

Syntax

mfr window-size number

undo mfr window-size

Default

The sliding window size is the number of physical interfaces in an MFR bundle.

Views

MFR interface view

Predefined user roles

network-admin

Parameters

number: Specifies the sliding window size in the range 1 to 16.

Examples

# Set the sliding window size to 8 for MFR4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] mfr window-size 8

Related commands

fr mfr

reset counters interface

Use reset counters interface to clear interface statistics.

Syntax

reset counters interface [ mfr [ interface-number | interface-number.subnumber ] ]

Views

User view

Predefined user roles

network-admin

Parameters

mfr: Specifies MFR interfaces or subinterfaces.

interface-number: Specifies an MFR interface by its number.

interface-number.subnumber: Specifies an MFR subinterface. The interface-number argument represents the number of the main MFR interface. The subnumber argument represents the number of the MFR subinterface. The value range for this argument is 0 to 1023.

Usage guidelines

Use this command to clear history statistics before you collect traffic statistics for a time period.

·     If you do not specify the mfr keyword, this command clears statistics for all interfaces.

·     If you specify the mfr keyword but without the interface-number or interface-number.subnumber argument, this command clears statistics for all MFR interfaces or subinterfaces.

Examples

# Clear statistics for MFR4.

<Sysname> reset counters interface mfr 4

shutdown

Use shutdown to shut down an MFR interface.

Use undo shutdown to restore the default.

Syntax

shutdown

undo shutdown

Default

An MFR interface is up.

Views

MFR interface view

Predefined user roles

network-admin

Examples

# Shut down MFR4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] shutdown

sub-interface rate-statistic

Use sub-interface rate-statistic to enable subinterface rate statistics collection on an MFR interface.

Use undo sub-interface rate-statistic to disable subinterface rate statistics collection on an MFR interface.

Syntax

sub-interface rate-statistic

undo sub-interface rate-statistic

Default

Subinterface rate statistics collection is disabled on an MFR interface.

Views

MFR interface view

Predefined user roles

network-admin

Usage guidelines

This command is resource intensive. When you use this command, make sure you fully understand its impact on system performance.

Examples

# Enable subinterface rate statistics collection on MFR 4.

<Sysname> system-view

[Sysname] interface mfr 4

[Sysname-MFR4] sub-interface rate-statistic