Configuring a Point-to-Multipoint Connection on ATM MICs
Starting in Junos OS Release 18.2R1, MX Series routers containing an ATM MIC (model number: MIC-3D-8OC3-2OC12-ATM) with SFP can communicate with multiple devices through ATM links. With this multipoint support, an ATM MIC can communicate with multiple Layer 3 peers in the ATM network through an ATM switch that is connected to multiple devices or ports, using different virtual circuit identifier (VCI). These devices can be accessed through multipoint port of ATM MIC.
epd-threshold and shaping options are not supported on multipoint-destination configuration statement for ATM MICs.
To enable the multipoint support on an ATM MIC, configure:
The multipoint option at the [edit interfaces interface-name unit logical-unit-number] hierarchy to enable communication with multiple Layer 3 peers on an ATM interface.
The multipoint-destination option with its corresponding vci at the [edit interfaces interface-name unit logical-unit-number family family address address] hierarchy to enable multipoint support on ATM interface.
The inverse-arp option (an optional configuration) to enable inverse ARP for multipoint-destination at the [edit interfaces at-fpc/pic/port unit logical-unit-number family family address address multipoint-destination address] hierarchy. Only responding to inverse ARP request is supported. Generation of Inverse ARP is not supported.
Multipoint-destination address must be configured under [edit interfaces interface-name unit logical-unit-number family family address address] hierarchy. The multipoint-destination address is the IP Address of the device that need to be accessed. It is also mandatory to mention VCI for a particular device for multipoint destination support. While, Inverse-arp is optional configuration which is required to enable inverse ARP.
It is mandatory to configure multipoint destination address along with the VCI and VPI for a point-to-multipoint interface.
To configure the multipoint support on ATM MIC, perform the following tasks:
- In configuration mode, to enable multipoint support navigate
to the [edit interfaces interface-name unit logical-unit-number] hierarchy level.[edit ]user@host# edit interfaces interface-name unit logical-unit-number
For example:
[edit ]user@host# edit interfaces at-1/0/0 unit 0 - By default, all interfaces are assumed to be point-to-point
connections. To configure an interface to be a multipoint connection,
include the multipoint statement at the [edit interfaces interface-name
unit logical-unit-number] hierarchy level.[edit interfaces interface-name unit logical-unit-number]user@host# set multipoint
For example:
[edit interfaces at-1/0/0 unit 0]user@host# set multipoint - After enabling multipoint, set the source address. To
configure the source address, navigate to the [edit interfaces interface-name unit logical-unit-number family family] hierarchy level.[edit interfaces interface-name unit logical-unit-number]user@host# edit family family address address
For example:
[edit interfaces at-1/0/0 unit 0]user@host# edit family inet address 7.0.0.2/24 - Configure the multipoint-destination address along with the virtual circuit identifier (VCI) and virtual
path identifier (VPI).
Note It is mandatory to configure multipoint destination address along with the VCI and VPI for a point-to-multipoint interface.
[edit interfaces interface-name unit logical-unit-number family family address address ]user@host# set multipoint-destination address vci vpi-identifier.vci-identifierFor example:
[edit interfaces at-1/0/0 unit 0 family inet address 7.0.0.2/24 ]user@host# set multipoint-destination 7.0.0.3 vci 100.100 - (Optional) Configure inverse ARP.[edit interfaces interface-name unit logical-unit-number family family address address multipoint-destination address]user@host# set inverse-arp
For example:
[edit interfaces at-1/0/0 unit 0 family inet address 7.0.0.2/24 multipoint-destination 7.0.0.3]user@host# set inverse-arp - Execute the show interfaces command to verify
whether the interface shows the configured multipoint parameters correctly.user@host# show interfaces
interfaces { at-1/0/0 { atm-options { vpi 100; } unit 0 { encapsulation atm-snap; multipoint; family inet { address 7.0.0.2/24 { multipoint-destination 7.0.0.3 { vci 100.100; inverse-arp; } } } } } } - Execute show interface at-1/0/0 command to
verify that point-to-multipoint is shown under the IFL flag field.user@host# show interface at-1/0/0
Logical interface at-1/0/0.0 (Index 362) (SNMP ifIndex 911) Flags: Up Point-To-Multipoint << No-Multicast SNMP-Traps 0x4000 Encapsulation: ATM-SNAP Input packets : 3 Output packets: 3 Protocol inet, MTU: 9176 Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0 Flags: Sendbcast-pkt-to-re Addresses, Flags: Is-Preferred Is-Primary Destination: 7.0.2/24, Local: 7.0.0.2, Broadcast: 7.0.0.255 VCI 100.120 Flags: Active, Inverse-ARP Multipoint destination: 7.0.0.5 <<< Total down time: 0 sec, Last down: Never ARP statistics Received: 0, Sent: 0, Denied: 0, Operation not supported: 0, Bad packet length: 0, Bad protocol: 0, Bad protocol length: 0,