Figure 2: NBMA Interface Stack
Unlike standard point-to-point ATM interfaces and broadcast-oriented Ethernet
interfaces, NBMA interfaces form a point-to-multipoint connection. For example,
you can use NBMA to connect a router to multiple stations.
An NBMA interface consists of a single ATM 1483 subinterface that has two or more
VCs. You can add circuits to an existing ATM 1483 subinterface at any time. New
circuits become usable after they have valid ARP table entries. NBMA circuits support
only IP directly over ATM 1483.
The software restricts NBMA interfaces so that all circuits reside on the same physical
interface. An NBMA interface can use as many PVCs as are available on a physical
port.
ARP Table
To maintain the Address Resolution Protocol (ARP) table, you can use either static
mapping via the CLI or Inverse ARP (InARP). InARP provides a way of determining
the IP address of the device at the far end of a circuit. For NBMA interfaces, InARP
enables automatic creation of ARP table entries for each circuit on the interface.
You must enable InARP when you create a PVC by using the
atm pvc
command.
After you configure InARP, a protocol mapping between an ATM PVC and a network
address is learned dynamically as a result of the exchange of InARP packets.
Static Map Versus Inverse ARP
If the device at the other end of a circuit does not support InARP, static mapping is
required for that circuit. One of these two methods must be used to generate an ARP
table entry for each circuit of the NBMA interface.
InARP and static mapping are complementary within an NBMA subinterface, but are
not compatible with regard to individual circuits. If InARP is configured on a circuit,
the corresponding virtual circuit descriptor (VCD) cannot be present in a static map
applied to that interface.
Aging
ARP table entries, with the exception of those declared static, are aged out based on
an aging interval defined on a subinterface basis. For the purposes of aging, entries
produced via a static map are treated as static ARP table entries. InARP-generated
entries are also treated as static; however, the InARP state machine automatically
14
■
ATM NBMA
JUNOSe 11.1.x Link Layer Configuration Guide
Summary of Contents for JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010
Page 6: ...vi...
Page 8: ...viii JUNOSe 11 1 x Link Layer Configuration Guide...
Page 26: ...xxvi List of Figures JUNOSe 11 1 x Link Layer Configuration Guide...
Page 34: ...2 Chapters JUNOSe 11 1 x Link Layer Configuration Guide...
Page 230: ...198 Monitoring VLAN and S VLAN Subinterfaces JUNOSe 11 1 x Link Layer Configuration Guide...
Page 258: ...226 Monitoring 802 3ad Link Aggregation JUNOSe 11 1 x Link Layer Configuration Guide...
Page 334: ...302 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Page 394: ...362 Monitoring Multiclass MLPPP JUNOSe 11 1 x Link Layer Configuration Guide...
Page 406: ...374 Monitoring POS JUNOSe 11 1 x Link Layer Configuration Guide...
Page 468: ...436 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Page 498: ...466 Monitoring Bridged Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Page 546: ...514 Monitoring Cisco HDLC JUNOSe 11 1 x Link Layer Configuration Guide...
Page 747: ...Part 2 Index Index on page 717 Index 715...
Page 748: ...716 Index JUNOSe 11 1 x Link Layer Configuration Guide...
Page 774: ...742 Index JUNOSe 11 1 x Link Layer Configuration Guide...