[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Support
for ATM and Frame Relay Interfaces
Support for the vrf-table-label statement over Asynchronous Transfer Mode (ATM) and Frame Relay
interfaces is available on the Juniper Networks routing platforms
summarized in Table 10.
Table 10: Support
for ATM and Frame Relay Interfaces
|
Interfaces
|
J-series
|
M-series Without an Enhanced FPC
|
M-series with an Enhanced FPC
|
M320
|
T-series
|
|
ATM1
|
N/A
|
No
|
No
|
No
|
No
|
|
ATM2 intelligent queuing (IQ)
|
N/A
|
No
|
Yes
|
Yes
|
Yes
|
|
Frame Relay
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
|
Channelized
|
N/A
|
No
|
No
|
No
|
No
|
When you configure the vrf-table-label statement, be aware of the following limitations with ATM
or Frame Relay interfaces:
- The vrf-table-label statement is supported
on ATM interfaces, but with the following limitations:
- ATM interfaces can be configured on a T-series routing
platform, on an M320, or on an M-series router fitted with an enhanced
FPC.
- The interface can only be a PE router interface receiving
traffic from a P router.
- The router must have an ATM2 IQ PIC.
- The vrf-table-label statement is also
supported with Frame Relay encapsulated interfaces, but with the following
limitations:
- Frame Relay interfaces can be configured on a T-series
routing platform, on an M320, or on an M-series router fitted with
an enhanced FPC.
- The interface can only be a PE router interface receiving
traffic from a P router.
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]