337
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 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.
During LMI negotiation, the VC information of a DCE interface is transmitted. When too many VCs
are configured on a DCE interface, the negotiation packet carrying the PVC information might
exceed the maximum frame length allowed on the interface. In this case, the LMI negotiation fails.
Examples
# Create a VC with DLCI 100 on 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.
Summary of Contents for MSR810
Page 148: ...136 Related commands timer hold...
Page 331: ...319 Related commands timer hold...
