The following features have been added to JUNOS Release 9.0. Following the description is the title of the manual or manuals to consult for further information. For a complete list of manuals, see Table 5, Table 6, and Table 8.
 |
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 9.0. 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). |
To configure the DSCP value, include the new diffserv dscp (dscp-value | alias | do-not-change) statement at the [edit services pgcp gateway gateway-name h248-properties] hierarchy level. To view the DSCP value for the gate, use the show services pgcp gates gateway-name extensive command. [System Basics, Multiplay Solutions, Services Interfaces]
ISSU provides the following benefits:
With JUNOS 9.0, supported routing platforms are the M320, T320, and T640 routers. For information about supported PICs on these platforms, see the JUNOS High Availability Configuration Guide. Supported protocols are BGP, IS-IS, LDP, and OSPF/OSPFv3. Unsupported PICs do not prevent a unified ISSU. The software issues a warning to indicate that these PICs will restart during the upgrade. Similarly, an unsupported protocol configuration will not prevent a unified ISSU. The software issues a warning that packet loss may occur for the protocol during the upgrade.
|
Note: Unified ISSU does not support extension application packages developed using the Juniper Partner Solution Development Platform (PSDP) SDK. |
To perform a unified ISSU, complete the following steps:
To view information about the ISSU status, issue the show chassis in-service-upgrade command. [High Availability]
This feature is useful for configurations in which you want to use an IP address other than the primary IP address on some of the unnumbered Ethernet interfaces in your network.
To configure a secondary address on a loopback donor interface as the preferred source address for an unnumbered Ethernet interface, include the preferred-source-address option in the unnumbered-address statement at either of the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family inet unnumbered-address interface-name] or [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number family inet unnumbered-address interface-name]. To display the preferred source address of an unnumbered Ethernet interface, use the show interfaces operational mode command. [Network Interfaces]
Juniper ATM2 interfaces are used to terminate ATM DSLAM traffic, then forward this traffic with a circuit-cross-connect (CCC) encapsulation to a local or remote IQ2 interface, where this CCC encapsulation is converted to a stacked VLAN representation for transmission through a VLAN-tagged Ethernet network. [Network Interfaces]
To configure a route to be tracked, include the route statement at the [edit interfaces interface-name unit logical-unit-number family (inet | inet6) address address (vrrp-group | vrrp-inet6-group) track] or [edit logical-router logical-router-name interfaces interface-name unit logical-unit-number family (inet | inet6) address address (vrrp-group | vrrp-inet6-group) track] hierarchy levels. [High Availability, Network Interfaces]
The following commands restart chassisd and DPCs:
All chassis components, except for PEMs and fans, can be brought online or offline using the following commands:
where fru can be scb, fpc, pic, feb, or routing-engine.
When the IPC connection between the pgcpd process and the MultiServices PIC is being reestablished, a synchronization procedure is performed. This synchronization process restores the previous state of gates, and existing H.248 sessions stay alive.
The synchronization process can result in the mismatching of gates. For example, the pgcpd process might detect gates that exist in the Routing Engine, but are missing in the PIC. In this case, the pgcpd process reinstalls the gates on the PIC. Alternatively, if the pgcpd process detects gates that exist on the PIC, but not on the Routing Engine, it removes the gates from the PIC. Another scenario is when the pgcpd process detects gates that exist on the PIC and on the Routing Engine, but the versions of the gates do not match. In this case, the pgpcd process deactivates the gates that do not match. [Multiplay Services Guide, High Availability]
To enable nonstop routing, include the following configuration statements:
To trace nonstop routing synchronization events for RIP or RIPng, include the traceoptions flag nsr-synchronization statement at the [edit protocols rip] or [edit protocols ripng] hierarchy level. [High Availability]
The range that you can configure is from 6 through 65,535. This value is not advertised as the hold time. You continue to configure the advertised BGP hold time by including the hold-time statement. The minimum hold-time value must be less than or equal to the configured hold time or 90 seconds if you do not configure the hold-time statement. [Routing Protocols]
To configure, specify a subnetwork address when configuring the loopback interface (lo0) at the [edit interfaces] hierarchy level. [Routing Protocols, Interfaces]
To configure VSTP, include the vstp statement at the [edit protocols] or [edit routing-instances routing-instance-name protocols] hierarchy level. To enable a VSTP instance for a specified VLAN, include the vlan statement at the [edit protocols vstp] or [edit routing-instances routing-instance-name protocols vstp] hierarchy level. [Routing Protocols]
To enable nonstop routing, include the following configuration statements:
To enable nonstop routing, include the following configuration statements: the graceful-switchover statement at the [edit chassis redundancy] hierarchy level, the nonstop-routing statement at the [edit routing-options] hierarchy level, and the commit synchronize statement at the [edit system] hierarchy level [High Availability]
To create a topology, include the topologies family (inet | inet6) topology (ipv4-multicast | name) statement at the [edit routing-options] hierarchy level.
To configure OSPF for MTR, include the topology (ipv4-multicast | name) topology identifier statement at the [edit protocols ospf] hierarchy level.
To configure a topology-specific metric value for an OSPF interface, include the metric number statement at the [edit protocols ospf area area-id topology-name] hierarchy level.
To configure static routes, include the rib routing-table-name static route destination-prefix statement at the [edit routing-options] hierarchy level.
To configure BGP, include the community identifier statement at the [edit protocols bgp family (inet | inet6) topology] hierarchy level. The community statement is also supported at the hierarchy levels for BGP groups and BGP peers.
For filter-based forwarding, include the topology name statement at the [edit firewall family inet filter name term term-name then] hierarchy level.
Use the show route summary, show route forwarding-table, show route table, and route route rib-groups commands to verify your configuration. To view topology-specific information about your OSPF configuration, use the show ospf operational mode commands. The show ospf route and show ospf log commands now include a topology (default | ipv4-multicast | name) option that enables you display information only about a specific topology. [Routing Protocols Configuration Guide, Routing Protocols and Policies Command Reference]
To configure LDP, BGP, and VPLS interworking, configure the mesh-group statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level. Specify the VPLS identifier using the vpls-id statement at the [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] hierarchy level. You also must specify each PE router that is a part of the mesh group using the neighbor statement at the [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] hierarchy level.
LDP, BGP, and VPLS Interworking do not support the following:
To enable ingress PE router redundancy for P2MP LSPs, specify each backup PE router's IP address using the backups statement at the [edit routing-options backup-pe-group pe-group-name] hierarchy level. You also need to specify a local IPv4 address using the local-address statement at the [edit routing-options backup-pe-group pe-group-name] hierarchy level. To bind a backup PE group to a static route, specify the name of the backup PE router group using the backup-pe-group statement at the [edit routing-options static route destination] hierarchy level. To bind a point-to-point LSP configured between a PE router and a backup PE router group, include the associate-backup-pe-groups statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. To display information about any configured backup PE router groups, issue the show multicast backup-pe-groups operational mode command. [MPLS Applications, Multicast]
LDP, BGP, and VPLS interworking do not support the following:
[VPNs, Feature Guide]
Include the load-balance, per-prefix, and hash-seed number statements at the [edit forwarding-options] hierarchy level. The hash-seed value specifies the router-specific parameter for electing the next hop. The range that you can configure is from 1 through 65,535. If you do not configure the hash-seed value, the router uses the legacy behavior of electing a next hop based only on the destination address. [Policy Framework, MPLS]
Layer 2 support for firewall filter match conditions (MX-series)—The JUNOS software now supports the following firewall filter match conditions for Layer 2 traffic for bridge domains and VPLS routing instances:
This feature helps you manage such network environments by enabling the extended DHCP relay agent to compare option 60 vendor-specific strings received in DHCP client packets against a list of ASCII or hexadecimal strings that you configure on the router. If the option 60 string received in the DHCP client packet matches the configured ASCII or hexadecimal string, you can define one of the following actions for the associated DHCP packets:
If the option 60 string received in the DHCP client packet does not match the configured ASCII or hexadecimal string, you can define one of the following default actions for the associated DHCP packets:
To configure option 60 support for the extended DHCP relay agent, include the relay-option-60 statement at the [edit forwarding-options dhcp-relay] hierarchy level or at the [edit forwarding-options dhcp-relay group group-name] hierarchy level. You can also configure option 60 support for the extended DHCP relay agent on a per logical router and per routing instance basis.
To display the number of discarded DHCP packets containing option 60 vendor-specific information, use the show dhcp relay statistics operational command. [Policy Framework]
A fast update filter is the same as a regular filter defined in the [edit firewall] hierarchy, except that the system can incrementally add or update terms. The fast update filter match is performed based on the most specific defined term.
When a VoIP flow configured through the packet gateway violates the sustained data rate (SDR) by three times the configured rate, fast update filters are installed on the gate to allow the rate-limiting drop action to occur on the PFE instead of the PIC. Filters are in effect until the gate is destroyed.
For each filter, a default term is installed to allow traffic to pass through (otherwise, all traffic is dropped because it is the default firewall action). For example, two terms are listed when there are two filters. You can monitor the status and configuration of the fast update firewalls in the packet gateway by using the show services pgcp active-configuration and the show services pgcp gates extensive command. [Multiplay Solutions; System Basics and Services Command Reference]
Support for GMPLS MIBs (M-series, T-series, and TX Matrix)—Extends read-only support to the following GMPLS MIB:
To access the chassis viewer, click the Chassis Viewer icon in the upper right corner of any J-Web page for an M7i, M10i, M20, M120, or M320 routing platform. A separate page appears to display the image of the chassis and its component parts, including power supplies, individual Physical Interface Cards (PICs), and ports. Major or minor alarm indicators appear in red. [J-Web Graphical Chassis Viewer (M20)]
AIM consists of two components to collect and display problem and intelligence event information as part of the Advanced Insight Solutions (AIS) product:
AIM provides a single point to view incident and intelligence event information for multiple sites on a customer's network. You can specify sites for which you want to view information. The Multi-Site feature requires licensing to create more than one site. [Advanced Insight Solutions]
If Advanced Insight Solutions (AIS) users use the AIM application integration with JUNOScope software to automatically install AI-Scripts, the following required device configuration is automatically configured. However, if the user elects to manually installed AI-Scripts, the following configuration must be manually done at the [edit groups] hierarchy level:
- groups {
-
- juniper-pvs {
-
- system {
-
- scripts {
-
- commit {
- allow-transients;
-
- file jpvs-activate-scripts.slax {
- optional;
- }
- }
- load-scripts-from-flash;
- }
- }
-
- event-options {
-
- destinations {
-
- juniper-junoscope {
-
- archive-sites {
- "ftp://anonymous@10.7.0.124/junoscopepvsdemo";
- }
- }
- }
- }
- }
- }
For AI-scripts, a new statement to configure event scripts has been added. To configure event scripts include the event-script event-script-name statement at the [edit event-options] hierarchy level:
- event-options {
- generate-event;
- policy policy-name;
-
- event-script event-script-name {
- file event-script-name-1;
- }
- destination;
- }
For example, this configuration determines the AIM remote archive location for a device:
- event-options {
-
- destinations {
-
- juniper-junoscope {
-
- archive-sites {
- "ftp://anonymous@10.7.0.124/junoscopepvsdemo";
- }
- }
- }
- }
The AIM application provides an option in general settings called “Information JMB Config Filter Level” that lets the customer specify the amount of intelligence information to share about a device with Juniper Networks: Do not send, Send all information except configuration, Send all information with IP Addresses overwritten, and Send all information.
The AIM licensing validates, authenticates, and manages three types of licenses to control its functionality to customers. The AIM user must provide an install ID and the serial number of the installed AIM application. The AIM Installer stores the date of installation in the database. The Juniper License Management System generates a license file that is electronically sent to the user. The user loads the license file into AIM for activation of the licensed features purchased.
|
Note: Having a license in AIM does not automatically mean that the customer has a license to subscribe to the AIS Base or AIS Proactive services needed for full functionality of the AIS product. |
To get full Advanced Insight Manager product functionality, the customer must purchase the following annual subscriptions for the following device classes from Juniper Support Services (JSS). AIM displays the annual subscriptions purchased for device classes when it connects to JSS.
To deploy JUNOS event scripts to multiple devices, select Configuration > Repository > Scripts. For more information about deploying JUNOS event scripts to multiple devices, see the JUNOScope Software User Guide. For more information about deploying the AI scripts bundle to multiple devices, see the Advanced Insight Solutions (AIS) Guide.
Table 1 lists the JUNOS Extensible Markup Language (XML) operational request tag elements that are new in JUNOS Release 9.0, along with the corresponding CLI command and response tag element for each one.
Table 1: JUNOS XML Tag Elements and CLI Command Equivalents New in JUNOS 9.0
[JUNOS XML Operational Reference]
The following set of system log messages is new in this release:
The following system log messages are new in this release:
The following system log message is no longer documented, either because it indicates internal software errors that are not caused by configuration problems or because it is no longer generated. If this message appears in your log, contact your technical support representative for assistance.
The JADE_AUTH_ERROR tag is renamed as JADE_AUTH_FAILURE. [System Log]
The following configuration statements pertain to applications running on the router but developed by Juniper partners under the Partner Solution Development Program (PSDP), using the JUNOS SDK. For information about these commands, or the PSDP, please contact JTAC.
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |