Errata

This section lists outstanding issues with the documentation.

Interfaces and Chassis

• The show interfaces command output does not show operation, administration, and maintenance (OAM) F4 cell statistics for interfaces that are configured for cell relay promiscuous virtual path identifier (VPI) mode. [Command Reference: Interfaces]
• In the JUNOS software implementation, the term logical interfaces generally refers to interfaces you configure by including the unit statement at the [edit interfaces interface-name] hierarchy level. As such, logical interfaces have the logical unit number at the end of the interface name, such as ge-0/0/0.1 or t1-0/0/0:0.1, where the logical unit number is 1. Although channelized interfaces are generally thought of as logical or virtual, the JUNOS software treats T3, T1, and NxDS0 interfaces within a channelized IQ PIC as physical interfaces. For example, both t3-0/0/0 and t3-0/0/0:1 are treated as physical interfaces by the JUNOS software. In contrast, t3-0/0/0.2 and t3-0/0/0:1.2 are considered logical interfaces because they have the .2 at the end of the interface names. [Network Interfaces]
• If you include the scheduler-map-chassis derived statement at the [edit class-of-service interfaces interface-name] hierarchy level, packet loss might occur when you subsequently add or remove logical interfaces at the [edit interfaces interface-name] hierarchy level. [Network Interfaces]
• For SONET/SDH interfaces you configure on Channelized OC3 IQ, Channelized OC12 IQ, and Channelized STM1 IQ PICs, aggregated SONET/SDH is not supported. [Network Interfaces]
• For Channelized OC3 IQ PICs, if you need remote loopback on a far-end DS0 interface, and you are running a bit error rate test (BERT) from the local DS0 interface, you must set the remote loopback on the far-end router's associated channelized T1 (ct1) interface. To do this, include the loopback remote statement at the [edit interfaces ct1-fpc/pic/port t1-options] hierarchy level. [Network Interfaces]

Routing Protocols

• Data-MDTs and Tunnel PICs in multicast VPNs—Each Tunnel PIC supports 512 multicast tunnel (mt) interfaces. Configurations for multicast over Layer 3 VPNs based on Internet draft draft-rosen-vpn-multicast-06.txt, Multicast in MPLS/BGP IP VPNs, that allow more than 512 multicast tunnels require another Tunnel PIC. Both default multicast tunnels and data-MDTs contribute to this total. There are typically two default multicast tunnels (one for encapsulation and the other for decapsulation). If a router with a single Tunnel PIC tries to create more than 512 default multicast tunnels or data-MDTs, no traffic flows for the excess tunnels.

  For example, a configuration that allows 500 data-MDTs requires only a single Tunnel PIC (500 + 2 = 502). However, a configuration that allows 1000 data-MDTs requires two Tunnel PICs (1000 + 2 = 1002). Up to 1024 multicast tunnels are supported with two Tunnel PICs. [Multicast]

• Enabling PGM—To configure the Pragmatic General Multicast (PGM) protocol, you must include the pgm statement at the [edit protocols] hierarchy level. [Multicast]
• Next-hop groups support (M-series routers, except the M320 router)—You can configure the next-hop-group statement at the [edit forwarding-options] hierarchy level only on M5, M7i, M10, M10i, M20, M40, M40e, and M160 routers. [Feature Guide]

VPNs

• When a Layer 2 circuit fails, Asynchronous Transfer Mode (ATM) interfaces that are configured for atm-ccc-vc-mux (ATM virtual circuit [VC] for CCC) ATM Adaptation Layer 5 (AAL5) encapsulation send F5 OAM remote detect indication (RDI) cells instead of F5 OAM alarm indication signal (AIS) cells. [VPNs]