HPE FlexNetwork MSR Series Comware 5 Layer 2 - Wan Access Configuration Guide

92
A P2P subinterface connects a single remote device and a P2MP subinterface connects multiple
remote devices. A P2MP subinterface can be configured with multiple virtual circuits, each of which
sets up an address map with its connected remote network address to distinguish different
connections. Address maps can be manually set up, or dynamically set up by InARP or IND.
The methods to configure a virtual circuit and address map for P2P subinterfaces and P2MP
subinterfaces are different, as follows:
• P2P subinterface—Because only one peer address exists for a P2P subinterface, the peer
address is determined when a virtual circuit is configured for the subinterface. You do not need
to configure dynamic or static address mapping for P2P subinterface.
• P2MP subinterface—For a P2MP subinterface, a peer address can be mapped to the local
DLCI through static address mapping or InARP. The InARP or IND configuration only needs to
be configured on the main interface. If static address mapping is required, it is necessary to set
up static address map for each virtual circuit.
To configure a frame relay subinterface:
Step Command Remarks
1. Enter system
view.
system-view
N/A
2. Create a
subinterface and
enter subinterface
view.
interface
interface-type
interface-number.subnumber [
p2mp
|
p2p
]
By default, a frame relay
subinterface operates in
p2mp
mode.
3. Configure a virtual
circuit on the
frame relay
subinterface.
See "
Configuring a frame relay local virtual
circu
it
."
On a frame relay subinterface,
virtual circuits must be created
manually and be identical to
those created at the DCE end.
4. Configure address
mappings.
See "
Configuring frame relay address
mappi
ngs
."
Optional for a P2P subinterface.
Required for a P2MP
subinterface.
Configuring Annex G
ANSI T1.617 Annex G (Annex G, for short) defines the way to transmit X.25 packets through frame
relay virtual circuits. In an Annex G implementation, the acknowledgement/retransmission and
flow-control mechanism used in X.25 are invoked to provide reliable transmission. Annex G can also
connect X.25 networks through FR networks. It helps you to migrate from X.25 network to FR
network and protects the investment on X.25 effectively.
Configuring an Annex G interface
When you configure an Annex G interface, follow these guidelines:
• Because Annex G is not compliant with Inverse-ARP, configure a static FR mapping for the
destination IP address.
• For the two Annex G interfaces of a virtual circuit, configure one as the DTE and the other as the
DCE.
To configure an Annex G interface:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter interface view.
interface
interface-type
interface-number
N/A

HPE FlexNetwork MSR Series Specifications

General

Brand	HPE
Model	FlexNetwork MSR Series
Category	Network Router
Language	English