Configuring Frame Relay Iphc - HPE FlexNetwork MSR series Configuration Manual

multiple subinterfaces. The subinterfaces and main interfaces can all be configured with virtual
circuits to connect to peer devices.
Frame Relay subinterfaces include the following types:
•
Point-to-point (P2P) subinterface—A P2P subinterface connects to a single peer device.
•
Point-to-multipoint (P2MP) subinterface—A P2MP subinterface connects to multiple peer
devices. A P2MP subinterface can be configured with multiple virtual circuits. An
address-to-DLCI map can be configured for each virtual circuit and its connected peer network
address. Address-to-DLCI maps can be dynamically configured through InARP or manually
configured.
The methods of configuring a virtual circuit and address-to-DLCI map for P2P subinterfaces and
P2MP subinterfaces have the following differences:
•
P2P subinterface—Because a P2P subinterface has only one peer address, the peer address
is determined when a virtual circuit is configured for the subinterface. You cannot configure
static address-to-DLCI maps or enable InARP for a P2P subinterface.
•
P2MP subinterface—For a P2MP subinterface, a peer address can be mapped to the local
DLCI through static address-to-DLCI maps or InARP. To enable InARP for dynamic address
mapping on a P2MP subinterface, you only need to enable InARP on the main interface. If static
address-to-DLCI maps are needed, you must configure a static address-to-DLCI map for each
virtual circuit.
To configure a Frame Relay subinterface:
Step
1. Enter system view.
2. Create a subinterface and
enter subinterface view.
3. Configure a virtual circuit on
the
subinterface.
4. Configure address mapping.

Configuring Frame Relay IPHC

IP header compression (IPHC) reduces the amount of bandwidth consumed by packet headers. It is
typically used for voice communication on low-speed links.
IPHC includes the following types:
•
RTP header compression—Compresses the IP/UDP/RTP header (40 bytes in total) in
packets.
•
TCP header compression—Compresses the TCP/IP header (40 bytes in total) in packets.
For the duration of a connection, some fields in the RTP/UDP/IP or TCP/IP header do not change,
and other fields change in a predictable way. The IPHC compressor and decompressor maintain the
fields that do not change and the fields that change in a predictable way. The compressor only needs
to transmit the fields of a header that change.
Command
system-view
interface
interface-number.subnumber
[ p2mp | p2p ]
See
Frame Relay
Relay virtual
See
address
interface-type
"Configuring local Frame
circuits."
"Configuring Frame Relay
mapping."
230
Remarks
N/A
By default, no Frame Relay
subinterfaces exist.
If you do not specify
subinterface type when you
create a Frame Relay interface,
a P2MP subinterface is created.
On a Frame Relay subinterface,
virtual circuits must be created
manually.
Available on
subinterfaces.
a
P2MP