The following features have been added to JUNOS Release 8.5. Following the description is the title of the manual or manuals to consult for further information. For a complete list of manuals, see Table 4, Table 5, and Table 7.
 |
Note: Juniper Networks will discontinue offering printed documentation for JUNOS software documentation, M-series and T-series hardware installation and PIC guides, and the JUNOScope User Guide, starting with JUNOS Release 8.5. The following model numbers will no longer be available:
Juniper Networks will continue to include printed Quick Start guides with router shipments, and specific installation documentation will continue to be shipped with field-replaceable units (FRUs). |
The T1600 routing node features the following new hardware:
All other craft interface features are the same as on the T640 craft interface.
The T1600 routing node supports:
You can perform an online upgrade of an operational T640 routing node to a T1600 routing node. The T1600 upgrade kit includes five T1600-SIBs, two three-input 240-A power supplies, and one craft interface. The T1600-FPC4 is not included in the upgrade kit, but can be installed after all components of the upgrade kit are installed and operational.
|
Note: T640 routing nodes currently connected to a TX Matrix platform cannot be upgraded to a T1600 routing node. |
[T1600 Hardware Guide]
To enable nonstop routing support for BFD, include the following configuration statements:
You can also configure BFD trace options by including the following configuration statements:
To view BFD state replication status, issue the show bfd session extensive command. The new replicated flag appears in the output for this command when a BFD session has been replicated to the backup Routing Engine. [High Availability]
GRES support for the DHCP relay agent prevents the loss of state information for active DHCP clients. If mastership switches to the backup Routing Engine on routing platforms that contain dual Routing Engines, the secondary DHCP relay agent waits in a warm state and resumes control from the failed primary DHCP relay agent. The new primary DHCP relay agent restores state information about DHCP clients that were active before the switchover to the new master Routing Engine.
To enable GRES support for the extended DHCP relay agent, include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level. You cannot disable graceful Routing Engine switchover support for the extended DHCP relay agent when the entire router is configured for graceful Routing Engine switchover. [High Availability]
When you configure unidirectional mode on an interface, two additional physical interfaces associated with the original parent interface are created on the same port. The new interfaces function as independently operating links. The transmit-only interface is designated by a -tx suffix. The receive-only interface is designated by an -rx suffix. You can configure logical interfaces on both of the child interfaces, but not on the parent interface.
To configure unidirectional links, include the unidirectional statement at the [edit interfaces interface-name] hierarchy level. The configuration can be confirmed using the show extensive interfaces command. You can specify encapsulation, MAC address, and MTU size on the TX and RX links. Attributes common to both RX and TX, such as clocking and framing, are configured on the parent interface. [Network Interfaces and Interfaces Command Reference]
[Network Interfaces]
The PPPoE server is implemented per Ethernet logical interface. The interface can support VLAN tags but does not support stacked VLANs. Multiple PPPoE sessions can be established on the interface to multiple PPPoE clients.
To configure a PPPoE server on an M120 Ethernet logical interface, first specify the ppp-over-ether encapsulation option at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. Then, include the pp0 statement for the pseudo PPPoE physical interface at the [edit interfaces] hierarchy level. Finally, include the server statement at the [edit interfaces pp0.0 unit logical-unit-number pppoe-options] hierarchy level. [Network Interfaces, Interfaces Command Reference]
[Services Interfaces]
Support for rate limiting in voice traffic—Enables you to configure rate limiting for voice traffic. Because PGCP flows involve voice traffic, the flows require quality of service that:
This quality of service is provided through a two-rate three-color policing functionality on the MultiServices PIC. This policer complies with RFC 2698, A Two Rate Three Color Marker, September, 1999. With the rate-limiting capability, the MultiServices PIC can police flows to conform to:
You use rate limiting with PGCP gates. To enable rate limiting for a PGCP gate, you need to provide traffic management package (TMAN) parameters in the PGCP signaling commands that operate on gates. You configure the following parameters on the PGC:
To configure a NAT pool, you can now include an IPv6 address or prefix in the address and address-range statements at the [edit services nat pool] hierarchy level. This NAT pool can also be used by the packet gateway service.
To configure the router to aggregate IPv6 traffic before passing the events to IDS processing, you can include the destination-prefix-ipv6 and source-prefix-ipv6 statements at the [edit services ids rule rule-name term term-name then aggregate] hierarchy level.
You can now view IPv6 addresses for NAT pools using the show services nat pool command. [Services Interfaces; System Basics and Services Command Reference]
|
Note: IPv6 addresses are not supported when the gateway-address statement is configured at the [edit services pgcp] hierarchy level or at the controller-address statement in the [edit services pgcp gateway gateway-name gateway-controller gateway-controller-name] hierarchy level. |
|
Note: IGMP snooping is not supported on integrated routing and bridging (IRB) interfaces. |
[Multicast]
[VPNs]
With queueing dense port concentrators (DPCs), users can specify a shaping rate at the physical interface level and a traffic control profile (output traffic control profile) at the logical interface level. This traffic control profile can specify a shaping rate, a guaranteed rate, and a scheduler map. The scheduler map contains the mapping of queues (forwarding classes) to their respective schedulers (parameters for the queue). Queue parameters can specify a transmit rate and buffer management parameters such as buffer size and drop profile.
In metro Ethernet environments, a VLAN typically corresponds to a customer premises equipment (CPE) device, and the VLANs are identified by an inner VLAN tag on Ethernet frames (called the customer VLAN, or C-VLAN, tag). A set of VLANs can be grouped at the DSL access multiplexer (DSLAM) and identified by using the same outer VLAN tag (called the Service VLAN, or S-VLAN, tag). Hierarchical schedulers enable you to provide shaping and scheduling at both levels in addition to the shaping and scheduling that takes place at the physical interface.
To configure hierarchical CoS schedulers, include the following statements at the [edit class-of-service interfaces] hierarchy level:
To apply hierarchical CoS schedulers to a set of interfaces, include the following statements at the [edit interfaces] hierarchy level:
- interface-set ( ifl-set-name | svlan-set | svlannumber
) {
-
-
ethernet-interface-name {
-
-
interface-parameters;
- }
- }
[Class of Service, Network Interfaces]
|
Note: You cannot enable shaping on aggregated Ethernet interfaces when there is a mixture of ports from IQ and IQ2 PICs in the same bundle. |
[Class of Service, Network Interfaces]
The following sets of system log messages are new in this release:
The following system log messages are new in this release:
The following system log messages are no longer documented, either because they indicate internal software errors that are not caused by configuration problems or because they are no longer generated. If these messages appear in your log, contact your technical support representative for assistance:
The text logged for the ASP_SFW_ALG_PROMOTION_FAILED tag is now “ALG promotion failed. Stateful firewall application stateful-firewall-application-name conflicts with NAT application nat-application-name or conflicts with QoS application; request creation of discard flow”. [System Log]