New Features in Junos OS Release 10.3 for M Series, MX Series, and T Series Routers

The following features have been added to Junos OS Release 10.3. Following the description is the title of the manual or manuals to consult for further information.

Class of Service

PLP copy for unicast and multicast (T Series routers)—Enables you to configure packet loss priority (PLP) bit copying for ingress and egress unicast and multicast traffic so that classifications and remarking function as intended. To configure, include the copy-plp-all statement at the [edit class-of-service] hierarchy level.
[Class of Service]

Interfaces and Chassis

New 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PD-5-10XGE-SFPP) PIC on T1600, T640, TXP, and TX Matrix routers—With GFPC4, STFPC4, and STFPC4.1, supports the following features:

VRRP
BFD
LSI
Ingress and egress VLAN rewrite for both outer and inner tags
IEEE802.1P rewrite in the egress direction

Extends VRRP and BFD protocols support as for existing 10–Gigabit Ethernet PICs.

Extends LSI support to the PD-5-10XGE-SFPP PIC as for existing 10–Gigabit Ethernet PICs.

Extends support for VLAN rewrites in both ingress and egress directions and for rewriting both inner and outer VLAN tags in the packet in both ingress and egress directions. The supported actions are summarized in the following table:

Table 1: Supported VLAN Rewrite Actions

Input VLAN Map	Output VLAN Map
Operation	none	push	pop	swap	push-push	swap-push	swap-swap	pop-pop	pop-swap
none	Yes	No	No	Yes	No	No	Yes	No	No
push	No	No	Yes	No	No	No	No	No	No
pop	No	Yes	No	No	No	No	No	No	No
swap	Yes	No	No	Yes	No	No	No	No	No
push-push	No	No	No	No	No	No	No	Yes	No
swap-push	No	No	No	No	No	No	No	No	Yes
swap-swap	Yes	No	No	No	No	No	Yes	No	No
pop-pop	No	No	No	No	Yes	No	No	No	No
pop-swap	No	No	No	No	No	Yes	No	No	No

The PD-5-10XGE-SFPP PIC supports egress IEEE802.1P rewrite. You can rewrite to the IEEE802.1P in VLAN tags of egress packets based on the [FC, PLP] => [dot1P Code Point] mapping configuration.

[Network Interfaces]

Next-hop cloning and permutations disabled in T Series Enhanced Scaling FPCs (FPC Type 1-ES, FPC Type 2-ES, FPC Type 3-ES, and FPC Type 4-ES)—The next-hop cloning and permutations are now disabled in these FPCs which have enhanced load balancing capability. As a result, the memory utilization is reduced for a highly scaled system with a high number of next hops on ECMP or aggregated interfaces.
[System Basics]
New 100 Gigabit Ethernet Type 4 PIC (T1600 and TX Matrix)—Supports IEEE 802.3ba on a single optical port 100 Gigabit Ethernet Type 4 PIC in Enhanced FPC4s on T1600 Routers and TX Matrix Routers. One 100 Gigabit Ethernet Type 4 PIC uses two slots of an Enhanced FPC4.
The following software features are supported:
- Layer 2 protocols:
  - Ethernet CCC, Ethernet TCC, Ethernet VPLS, VLAN CCC, Extended VLAN TCC, VLAN VPLS, and Flexible-Ethernet-service
- Layer 3 protocols:
  - IPv4, IPv6, and MPLS
- Flex-VLAN tagging
- MSA compliant MDIO control (optics dependent)
- Optical diagnostics (per optical channel):
  Measured parameters:
  - Internally measured module temperature
  - Internally measured Tx Bias Current
  - Measured Tx output power
  - Measured Rx input power
  Alarms and warnings:
  - Laser bias current high/low alarms and warnings
  - Laser output power high/low alarms and warnings
  - Module temperature high/low alarms and warnings
  - Laser Rx power high/low alarms and warnings
  - Module not ready alarm
  - Module power down alarm
  - Tx data not ready alarm
  - Tx not ready alarm
  - Tx laser fault alarm
  - Tx CDR loss of lock alarm
  - Rx not ready alarm
  - Rx loss of signal alarm
  - Rx CDR loss of lock alarm
- GRES is supported in all PIC and chassis configurations.
- Interface creation:
  - There are 2 physical interfaces when the 100 Gigabit Ethernet PIC is online (et-x/0/0:0 and et-x/0/0:1, where 'x' represents the FPC slot number). Each physical interface represents two internal 50 gigabit Ethernet Packet Forwarding Engines. Two logical interfaces are configured under each physical interface.
  - PFE0 is physical interface '0', PFE1 is physical interface '1'.
- 802.3 link aggregation:
  - Two logical interfaces are created for each 100 Gigabit Ethernet PIC. To utilize bandwidth beyond 50 gigabits per second, an aggregate interface must be explicitly configured on the 100 Gigabit Ethernet PIC that includes the two 50 gigabit interfaces.
  - Each 100 Gigabit Ethernet aggregate consumes one of the router wide aggregate Ethernet devices pools. You cannot have a number of 100 Gigabit Ethernet PICs that exceeds the router wide limit, which is 128 for Ethernet.
  - In each aggregate bundle, each 100 Gigabit Ethernet PIC consumes 2 members. Hence, an aggregate bundle that consists purely of 100 Gigabit Ethernet PICs supports a maximum of half of the software limit for the number of members. Therefore, with a maximum of 16 links, up to 8 100 gigabit Ethernet links are supported.
- Software Packet Forwarding Engine features:
  - Supports all Gigabit Ethernet PIC classification, firewall filter, queuing model, and rewrite functionality.
- Egress Traffic Performance:
  - Maximum egress throughput is 100 gigabits per second on the physical interface with 50 gigabits per second on the two assigned logical interfaces.
- Ingress Traffic Performance:
  - Maximum ingress throughput is 100 gigabits per second on the physical interface with 50 gigabits per second on the two assigned logical interfaces.
- Interoperability:
  - 100 Gigabit Ethernet PICs support interconnection only with the same interface type; interoperability with interfaces from other vendors is not supported.
[Network Interfaces, Interfaces Command Reference, Hardware]
64-bit Junos OS on a JCS1200 route reflector—Extends support for 64-bit Junos OS infrastructure on JCS1200 installations. The main benefits from this enhancement are memory and performance improvements; there are no additions or changes to the CLI statements or functionality. A mixture of 32-bit and 64-bit images in the same JCS chassis is a supported configuration. The only application supported currently is the Junos OS route reflector application.
[Junos OS PSD Configuration Guide]

Junos OS XML API and Scripting

New Junos OS XML API operational request tag elements—Table 2 lists the Junos OS Extensible Markup Language (XML) operational request tag elements that are new in Junos OS Release 10.3 along with the corresponding CLI command and response tag element for each one.

Table 2: Junos OS XML Tag Elements and CLI Command Equivalents New in Junos OS 10.3

Request Tag Element	CLI Command	Response Tag Element
<get-sha256- checksum-information> get_sha256_checksum_ information	file checksum sha-256	<checksum- information>
<get-sha1- checksum-information> get_sha1_checksum_ information	file checksum sha1	<checksum- information>
<request- services-flow- collector-destination> request_services_ flow_collector_destination	request services flow-collector change-destination	<flow-collector- destination- response>
<request-services-flow-collector- test-file-transfer > request_services_ flow_collector_test_file_transfer	request services flow-collector-test- file-transfer	<flow-collector- test-file-transfer- response>
<get-service- border-signaling- gateway- embedded-spdf> get_service_ border_signaling_ gateway_embedded _ spdf	show services border-signaling- gateway embedded- spdf	<bsg-embedded- spdf>
<get-service- border-signaling- gateway- embedded- spdf-status> get_service_ border_signaling_ gateway_embedded_ spdf_status	show services border-signaling- gateway embedded- spdf status	<bsg-embedded- spdf-status>

[Junos OS XML API Operational Reference]

Multicast

Automatic multicast tunneling support (MX Series routers)—Automatic multicast tunneling (AMT) facilitates dynamic multicast connectivity between multicast-enabled networks across islands of unicast-only networks. This enables service providers, content providers, and their customers that do not have multicast connectivity end-to-end to participate in delivering multicast traffic.
AMT dynamically establishes unicast-encapsulated tunnels between well-known multicast-enabled relay points (AMT relays) and network points reachable only through unicast (AMT gateways).
The AMT protocol provides for discovery and handshaking between relays and gateways to establish tunnels dynamically without requiring explicit per-tunnel configuration.
AMT relays are typically routers with native IP multicast connectivity that aggregate a potentially large number of AMT tunnels.
AMT gateways are devices that require connection to the IP multicast network but lack multicast routing capability or direct connection to multicast-capable routers. Gateways may be either individual hosts or routers that are partitioned from the larger multicast infrastructure.
AMT is described in detail in Automatic IP Multicast Without Explicit Tunnels (AMT), draft-ietf-mboned-auto-multicast-09.txt.
To configure the AMT protocol, include the amt configuration statement at the [edit protocols] hierarchy level.
amt {traceoptions {file ...flag all;flag errors;flag normal;flag packets;flag tunnels;}relay {family {inet {local-address <ip-address>;anycast-prefix <ip-prefix>/<ip-prefix-len>;}}secret-key-timeout <minutes>;tunnel-limit <number>;}}
To configure the IGMP attributes of AMT relay tunnels, include the amt configuration statement at the [edit protocols igmp] hierarchy level.
igmp {amt {relay {defaults {(accounting | no-accounting);group-policy [ policy-names ];ssm-map ssm-map-name;version version-number;query-interval interval-seconds;query-response-interval interval-seconds;robust-count count;}}}}
AMT logical interfaces are created dynamically and have an interface identifier in the format ud-FPC/PIC/Port.unit.
To display summary information about the AMT protocol, use the show amt summary operational mode command.
To display tunnel state information for active AMT tunnels, use the show amt tunnel operational mode command.
To display AMT protocol message counts and error statistics, use the show amt statistics operational mode command.
To display the multicast source and group addresses for an interface, use the show igmp group terse operational mode command.
To display gateway IP addresses and UDP port numbers for AMT logical interfaces, use the show interfaces detail operational mode command.
To display default parameters for active AMT interfaces, use the show igmp interface operational mode command.
To clear AMT tunnel states, use the clear amt tunnel operational mode command.
[Multicast, Network Interfaces]

Routing Policy and Firewall Filters

Lower policer limit (TX Matrix, M320, and T Series routers)—Enables you to configure a lower policer limit of 8000 instead of 32,000. To configure the policer limit, include the bandwidth-limit statement at the [edit firewall policer policer-name] hierarchy level.
[Routing Policy]

Routing Protocols

Support for clearing the VPN tag—To prevent routing loops in OSPF domain ID configurations, a VPN tag is configured for Type 5 LSAs if the DN bit is not supported on the provider edge (PE) router. To clear the VPN tag when it is no longer needed (when the DN bit is supported on the PE router), include the no-domain-vpn-tag statement at the [edit routing-instances routing-instances-name ospf | ospf3] hierarchy level.
[Routing Protocols]
Support for route leaking when router is in overload mode—You can enable a router to leak route information to the network even if the overload mode has been configured on your routing device. To enable your router to leak route information, include the allow-route-leaking option when you specify the overload statement at the [edit protocols isis] hierarchy level. Note that route leaking will not work if the router is in dynamic overload mode, when the router resources such as the prefix limit, have been exceeded.
[Routing Protocols]
Support for dropping and ignoring path attributes during BGP neighbor updates—You can filter out invalid or undesired path attributes from BGP updates during inbound processing. Invalid path attributes may be a result of using incorrect implementation of the software or nonstandard private path attributes. To drop or ignore path attributes, include the drop-path-attributes or ignore-path-attributes statement at the [edit protocols bgp group group-name neighbor interface] hierarchy level. You can specify which path attributes to drop or ignore, except for mandatory attributes such as origin, AS path, and next hop. In addition, you cannot specify the mp_reach and mp_unreach attributes because they are network-layer reachability information (NLRI) attributes.
[Routing Protocols]
Support for display of flood next-hop branch overflow condition—When you are adding or changing a flood next hop, the maximum number of flood next-hop branches you can add to the kernel is limited to 32. When this limit is exceeded, only a subset of the flood next-hop branches will be installed in the kernel. A message stating that the flood next-hop branches exceeded the maximum will be displayed in the output for the show route extensive and the show route details commands.
[Routing Protocols]

Services Applications

Packet sampling on T Series routers—Extends support for per Packet Forwarding Engine packet sampling and sampling instances to T640, T1600, and TX Matrix installations. The configuration and behavior previously documented for other platforms now applies to T Series routers; there are no additions or changes to the CLI statements and commands.
[Services Interfaces]

Subscriber Access Management

Junos OS subscriber access scaling values (M120, M320, and MX Series routers)—A spreadsheet is available online that lists the DHCP, PPP, and PPPoE scaling values supported for Junos OS subscriber management beginning with Junos OS Release 10.1. Access the spreadsheet from the Downloads box at http://www.juniper.net/techpubs/en_US/junos10.2/information-products/pathway-pages/
subscriber-access/index.html.