 |
Note: Before you install the T640-FPC2-ES or the T640-FPC4-1P-ES in a T640 routing node, all SIBs must be SIB version B, or T640–SIBs for T640 nodes connected to a TX matrix. [PIC Guides] |
Resolved Issues in JUNOS Release 9.6 for M Series, MX Series, and T Series RoutersResolved Issues in JUNOS Release 9.6 for M Series, MX Series, and T Series RoutersThe following features have been added to JUNOS Release 9.5. Following the description is the title of the manual or manuals to consult for further information.
However, you can configure the excess-rate statement to control an independent set of parameters for bandwidth sharing in the excess region of a Frame Relay data-link connection identifier (DLCI) on an MS PIC. You configure the excess-rate statement at the [edit class-of-service traffic-control-profile] hierarchy level.
[Network Interfaces, Class of Service]
However, you can configure the translation-tables statement to replace the arriving ToS bit pattern to a user-defined value. You configure the translation-tables statement at the [edit class-of-service] hierarchy level.
This feature follows exactly the same configuration rules as the Enhanced IQ PIC. [Class of Service]
Rate-limit and excess rate/excess priority option—You can configure bandwidth sharing rate limits, excess rate, and excess priority at the queue level on the following routers:
You configure rate limits when you have a concern that low latency packets (such as high or strict-high priority packets for voice) might starve low-priority and medium-priority packets. In JUNOS software, the low latency queue is implemented by rate limiting packets to the transmit bandwidth. The rate limiting is performed immediately before queueing the packet for transmission. All packets which exceed the rate limit are dropped, not queued.
By default, if the excess priority is not configured for a queue, the excess priority will be the same as the normal queue priority. If none of the queues have an excess rate configured, then the excess rate will be the same as the transmit rate percentage. If at least one of the queues has an excess rate configured, then the excess rate for the queues which do not have an excess rate configured will be set to zero.
When the physical interface is on queuing hardware such as the IQ, IQ2, IQE PICs, or MX-series DPCs, these features are not supported.
You cannot configure both rate limits and buffer sizes on these Packet Forwarding Engines.
Four levels of excess priorities are supported: low, medium-low, medium-high, and high.
All queues can be rate limited, whether eight or four queues are configured. The queue is shaped by limiting the queue to the transmit rate and reducing the queue buffer size to 1 millisecond. For example, a rate-limited queue (scheduler) with a configured transmit rate of 100 Mbps has a delay buffer of 1 millisecond of 100 megabytes, and the queue is shaped (rate controlled) to 100 Mbps. The queue output will be exactly 100 Mbps and the 1 millisecond buffer is available to absorb any transmission bursts. Any traffic above and beyond this limit is tail-dropped and in statistics this traffic is counted as rate-limited drops.
To configure rate limits for non-queuing Packet Forwarding Engines, include the shaping rate statement at the [edit class-of-service schedulers scheduler-name] hierarchy level.
To configure the excess rate for non-queuing Packet Forwarding Engines, include the excess-rate at the [edit class-of-service schedulers scheduler-name] hierarchy level.
To configure the excess priority for non-queuing Packet Forwarding Engines, include the excess-priority at the [edit class-of-service schedulers scheduler-name] hierarchy level.
The relationship between the configured guaranteed rate, excess rate, guaranteed priority, excess priority, and offered load is not always obvious. The following tables show the expected throughput of a Gigabit Ethernet port with various bandwidth sharing parameters configured on the queues. [Class of Service]
|
Note: Before you install the T640-FPC2-ES or the T640-FPC4-1P-ES in a T640 routing node, all SIBs must be SIB version B, or T640–SIBs for T640 nodes connected to a TX matrix. [PIC Guides] |
However, the JUNOS software does not support the following features for nonstop active routing on RSVP-TE LSRs:
[High Availability]
Unified ISSU support on additional hardware—Extends the unified ISSU support to the following routing platforms and PICs:
Enhanced IQ2 PICs (IQ2-E):
[High Availability]
E-LMI interoperates with an Operations, Administration, and Management (OAM) protocol, such as Connectivity Fault Management (CFM), that runs within the provider network to collect OAM status. CFM runs at the provider maintenance level (User Network Interface (UNI) UNI-N to UNI-N with up Management End Points (MEPs) at the UNI). E-LMI relies on the CFM for end-to-end status of Ethernet virtual connections (EVCs) across CFM domains (SVLAN domain or VPLS).
To configure E-LMI, include the connectivity-fault-management, evcs, and lmi statements at the [edit protocols oam ethernet] hierarchy level. [Network Interfaces]
To trigger ETH-DM, use the monitor ethernet delay-measurement (one-way | two-way) (remote-mac-address | mep identifier) maintenance-domain name maintenance-association ma-id [count count] [wait time] operational command.
To enable hardware assisted time stamping in reception path, use the performance-monitoring hardware-assisted-timestamping statement at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level.
To retrieve the last 100 ETH-DM statistics per session, two show commands are provided; one for all (all OAM frame counters and ETH-DM) statistics and one for ETH-DM statistics only.
To retrieve all statistics for given session, use the show oam ethernet connectivity-fault-management mep-statistics maintenance-domain name maintenance-association name [local-mep identifier] [remote-mep identifier] [count count] command.
To retrieve only ETH-DM stats for given session, use the show oam ethernet connectivity-fault-management delay-statistics maintenance-domain name maintenance-association name [local-mep identifier] [remote-mep identifier] [count count] command.
[Network Interfaces]
[Network Interfaces, PIC Guide]
[Network Interfaces, PIC Guide]
To specify the auto-negotiation speed, use the speed < (auto | 1 Gbps | 100 Mbps | 10 Mbps)> statement under the [edit interface ge-/fpc/pic/port] hierarchy level.
To set port speed negotiation to a specific rate, set the port speed to either 1 Gbps, 100 Mbps, or 10 Mbps. If the negotiated speed and the interface-speed do not match, the link will not be brought up.
If you set the auto-negotiation speed auto option, then the port speed is negotiated.
You can disable Auto MDI/MDIX using the no-auto-mdix statement under the [edit interface ge-/fpc/pic/port gigether-options] hierarchy level.
Use the show interfaces ge-fpc/pic/port brief command to display the auto negotiation of speed and auto MDI/MDIX states.
[Network Interfaces]
IQ PICs:
IQE PICs:
Standard PICs:
To configure the BERT period on T1 interfaces, use the bert-period seconds statement at the [edit interfaces t1-fpc/pic/port t1-options] hierarchy level. The range is from 1 through 86400 seconds. The default value is 240 seconds.
To configure the BERT period on E1 interfaces, use the bert-period seconds statement at the [edit interfaces e1-fpc/pic/port e1-options] hierarchy level. The range is from 1 through 86400 seconds. The default period is 10 seconds.
You can use the show interfaces t1-fpc/pic/port extensive | find BERT command to display T1 PIC BERT results.
You can use the show interfaces e1-fpc/pic/port extensive | find BERT command to display E1 PIC BERT results.
[Network Interfaces]
[Network Interfaces, MX-series Hardware Guide]
For inter-PSD forwarding, each PSD that needs to communicate with another PSD must have a Tunnel PIC attached. To configure inter-PSD forwarding on a PSD, include the following statements at the [edit interfaces] hierarchy level of the associated PSDs:
- xt-fpc/pic/port {
-
- unit unit-number {
- peer-psd psdn;
- peer-interface logical-interface-name;
- encapsulation frame-relay;
- point-to-point;
- dlci dlci-value;
- }
- }
Currently, only Frame Relay encapsulation is supported for inter-PSD forwarding. [JUNOS PSD Configuration Guide].
JUNOS software supports the following rewrite operations under ethernet-ccc and ethernet-vpls encapsulations:
push-push and pop-pop operations are not supported on Ethernet IQ PICs. Ethernet IQ2 PICs support all the above mentioned rewrite operations.
M320 and M120 platforms with the following PICs, support this feature:
Ethernet IQ PICs:
Ethernet IQ2 PICs:
Enhanced Ethernet IQ2E PICs:
MX platforms with the following DPCs support this feature:
In the input-vlan-map, only the push and push-push operations are permitted. Similarly, only pop and pop-pop operations are permitted in the output-vlan-map. For push and push-push operations, the tag parameters must be explicitly specified. All other rules for configuring input-vlan-map and output-vlan-map remain the unchanged.
To configure an input VLAN map, use the input-vlan-map statement and options at the [edit interfaces interface-name fpc/pic/port unit number] hierarchy level.
To configure an output VLAN map, use the output-vlan-map statement and options at the [edit interfaces interface-name fpc/pic/port unit number] hierarchy level.
|
Note: Unit encapsulation must be set to either ethernet-ccc or ethernet-vpls or input VLAN map and output VLAN map settings will not be valid. |
You can use the show interface interface-name dpc/pic/port command to display the Index, SNMP ifIndex, flags, In(push), Out(pop), and Encapsulation parameters. [Network Interfaces]
You can configure the load-balancing hash key for Layer 2 traffic to use fields in the Layer 3 and Layer 4 headers inside the frame payload for load-balancing purposes using the payload statement. You can configure the statement to look at layer-3 (and source-address-only or destination-address-only packet header fields) or layer-4 fields. You configure this statement at the [edit forwarding-options hash-key family multiservice] hierarchy level. [Layer 2 Configuration Guide, Policy, and Network Interfaces]
The revised commands are:
You can now display information on P2MP LSPs by issuing these commands on either the ingress router of the P2MP LSP or from any of the routers along any of the sub-LSP paths. [Routing Protocols Reference]
To disable hierarchical bandwidth adjustment for all subscribers on a multicast interface, include the no-qos-adjust statement at the [edit routing-options multicast interface [interface-names] reverse-oif-mapping] hierarchy level.
To display the multicast bandwidth consumed on the subscriber interfaces, issue the show multicast interfaces command. [Multicast, Subscriber Access]
The default behavior for the IGMP snooping process on an MX-series router can be changed to ignore the spanning-tree topology change messages. To ignore the spanning-tree topology change messages, include the ignore-stp-topology-change statement at the [edit routing-instances routing-instance-name bridge-domains bridge-domain-name multicast-snooping-options] hierarchy level.
[Multicast, MX-series Layer 2 Configuration Guide]
You can enable dynamic reuse of data MDT group addresses. Dynamic reuse of data MDT group addresses allows multiple multicast streams to share a single MDT and multicast provider group address. For example, three streams can use the same provider group address and MDT tunnel. When the feature is enabled, new streams are assigned to a particular MDT in a round-robin fashion. Note that if the provider tunnel is being used by multiple customer streams, it might result in egress routers receiving customer traffic that is not requested by the attached customer sites. This is similar to what happens if multiple customer streams are sent on the default MDT tunnel.
To enable dynamic reuse of data MDT group addresses, include the data-mdt-reuse statement. The data-mdt-reuse statement can be configured at the [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim mdt] and [edit routing-instances routing-instance-name protocols pim mdt] hierarchy levels. [Multicast, Routing Protocols and Policies Command Reference]
To configure a dynamic database, enter the configure dynamic command to be placed in the [edit dynamic] hierarchy. At the [edit dynamic policy-options] hierarchy level, you can configure the following statements: as-path as-path-name, as-path-group group-name, community community-name, condition condition-name, prefix-list prefix-list-name, and policy-statement policy-statement-name. No other configuration is supported at the [edit dynamic] hierarchy level.
All the policies that you configure in the dynamic database can be referred to in policies configured in the standard configuration under the [edit policy-options] hierarchy level. To define a routing policy based on the dynamic database configuration, include the dynamic-db statement at the [edit policy-options policy-statement policy-statement-name] hierarchy level in the standard configuration mode. You can also include the dyanmic-db statement at the following hierarchy levels: [edit policy-options as-path as-path-name, [edit policy-options as-path-group group-ame], [edit policy-options community community-name, [edit policy-options condition condition-name], and [edit policy-options prefix-list prefix-list-name]. In this way, you can define any of these policy objects using the dynamic database configuration. You can then apply any of these policies that reference the dynamic database configuration to a routing policy configured in the standard configuration. For example, include the dynamic-db statement at the [edit policy-options prefix-list p11] hierarchy level to create a prefix list, p11, that references the dynamic database configuration. You can then include the prefix-list p11 statement at the [edit policy-options policy-statement policy-statement-name from] hierarchy level in the standard configuration to define a routing policy that matches on a prefix list configured in the dynamic database.
Currently, BGP is the only protocol to which you can apply routing policies configured in the dynamic database. You must use the standard configuration mode to apply routing policies configured in the dynamic database. For example, you configure policy-statement dyn-policy1 at the [edit dynamic] hierarchy level. You then define a routing policy based on the dynamic database configuration by including the dynamic-db statement at the [edit policy-options policy-statement dyn-policy1] hierarchy level. You can then apply the dyn-policy-1 routing policy at the [edit protocols bgp group group-name neighbor address export] or [edit protocols bgp group group-name neighbor address import] hierarchy level in the standard configuration mode. [Policy]
You can also configure multiple port-mirroring instances for VPLS, IPv6, and VPLS traffic with each instance specifying different input sampling properties and output mirror destination properties. Multiple port-mirroring instances were previously supported only on the MX-series routers. To configure a port-mirroring instance, include the instance port-mirroring-instance-name statement at the [edit forwarding-options port-mirroring] hierarchy level. To configure a family address type for a port-mirroring instance, include the family (inet | inet6 | vpls) statement at the [edit forwarding-options port-mirroring instance port-mirror-instance-name] hierarchy level. To configure input properties for a port-mirroring instance, include the input statement at the [edit forwarding-options port-mirroring instance port-mirroring-instance-name] hierarchy level. To configure output properties for a port-mirroring instance, include the output statement at the [edit forwarding-options port-mirroring family (inet | inet6 | vpls)] hierarchy level. You can also associate a port-mirroring instance with a specific FPC on an M320 router and with a specific FEB on an M120 router. To associate a port-mirroring instance with a specific FPC on an M320 router, include the port-mirror-instance instance-name statement at the [edit chassis fpc number] hierarchy level. To associate a port-mirroring instance with a specific FEB on an M120 router, include the port-mirror-instance instance-name statement at the [edit chassis feb slot number] hierarchy level. You can associate only one port mirroring instance with each FPC on an M320 router and with each FEB on an M120 router. In addition, on an M120 router, you cannot configure a port mirroring instance on a FEB configured as a backup FEB. [Policy, System Basics]
To configure this option, the blade bay data includes support for a new routing platform type: Standalone Control Element (PRDSCE). The SCE platform does not have forwarding plane (PFE) support and does not require RSD connectivity. The platform has network connectivity by fxp0 and fxp1 interfaces only. [JUNOS PSD Configuration Guide]
You can enable support for alternate loop-free routes on any IS-IS interface. Because it is common practice to enable LDP on an interface for which IS-IS is already enabled, this feature also provides support for LDP label-switched paths (LSPs).
The level of backup coverage available through IS-IS routes depends on the actual network topology and is typically less than 100 percent for all destinations on any given router. You can extend backup coverage to include RSVP LSP paths.
The JUNOS software provides two mechanisms to enable fast reroute for IS-IS using alternate loop-free routes: link protection and node-link protection. When you enable link protection or node-link protection on an IS-IS interface, the JUNOS software creates an alternate path to the primary next hop for all destination routes that traverse a protected interface. Link protection offers per-link traffic protection. Use link protection when you assume that only one link might become unavailable but that the neighboring node on the primary path would still be available through another interface. Node-link protection establishes an alternate path through a different router altogether. Use node-link protection when you assume that access to a node is lost when a link is no longer available.
To enable link protection for all destination routes that traverse a specific interface, include the link-protection statement at the [edit protocols isis interface interface-name] hierarchy level. To enable node-link protection for all destination routes that traverse a specific interface, include the node-link-protection statement at the [edit protocols isis interface interface-name] hierarchy level. By default, all the interfaces in a routing instance can function as backup interfaces for a protected interface. To exclude a specific interface from functioning as a backup for a protected interface, include the no-eligible-backup statement at the [edit protocols isis interface interface-name] hierarchy level. You can enhance backup coverage for IS-IS routes and LDP LSP paths by configuring RSVP LSPs as additional backup paths. Include the backup statement at the [edit mpls label-switched-path lsp-name]. You must also specify the address of the egress router for the LSP by including the to address statement at the [edit mpls label-switched-path lsp-name] hierarchy level.
Several new commands are available to support this new feature. Use the show isis backup label-switched-path command to display which MPLS LSPs have been designated as backup paths. To display shortest-path-first (SPF) calculations for each neighbor, use the show isis backup spf results command. Use the show isis backup coverage command to display how many nodes and prefixes for each address family are protected. In addition, the show isis detail command has been enhanced to display the type of protection, link or link-node, applied to each interface. [Routing Protocols, Routing Protocols and Policies Command Reference]
Optionally, you can configure how often to send data to the monitoring station with the statistics-timeout seconds statement. The default is 1 hour. You can also configure a memory threshold to stop collecting BMP data when it is exceeded as well as a time interval to wait before reestablishing a BMP session that has ended after exceeding the memory threshold. Use the memory-lmit bytes statement to configure the memory threshold The default is 10 MB. To configure the interval to wait before reestablishing the BMP session, include the memory-connect-timeout seconds statement. The default is 10 minutes. [Routing Protocols]
To reduce the possibility of fragmentation and to protect against packet loss, include the tcp-mss mss-value statement to specify an appropriate TCP MSS value.
If the router receives a TCP packet with the SYN bit and MSS option set and the MSS option specified in the packet is larger than the MSS value specified by the tcp-mss statement, the router replaces the MSS value in the packet with the lower value specified by the tcp-mss statement.
To configure a TCP MSS value, include the tcp-mss statement at the [edit services service-set service-set-name] hierarchy level:
The range for the tcp-mss mss-value parameter is from 536 to 65,535.
To view statistics of SYN packets received and SYN packets whose MSS value is modified, issue the show services service-sets statistics tcp-mss operational mode command. [Services Interfaces, System Basics]
To configure the new feature, include the flow-tap-lite statement at the [edit services] hierarchy level and assign the designated tunnel interface for use by the dynamic flow capture process (dfcd). The original flow-tap feature and the new version share the same Dynamic Tasking Control Protocol (DTCP) SSH architecture to install the DTCP filters and authenticate users. [Services Interfaces, Feature Guide]
When a call cannot be admitted due to a CAC violation, the call request is rejected with a code 403.
To configure a controller file, enter the controller-name statement at the [edit services border-signaling-gateway gateway gateway-name admission-control] hierarchy level.
To enforce the admission control on dialogs, enter the following statements at the [edit services border-signaling-gateway gateway gateway-name admission-control controller-name dialogs] hierarchy level: maximum-concurrent, committed-attempts-rate, committed-burst-size.
To enforce admission control on transactions, enter the following statements at the [edit services border-signaling-gateway gateway gateway-name admission-control controller-name transactions] hierarchy level: maximum-concurrent, committed-attempts-rate, committed-burst-size.
To assign a CAC controller to a policy action, enter the admission-control statement at the [edit services border-signaling gateway gateway-name new-transaction-policy policy-name term term-name then] hierarchy level.
You can use the following show commands to display information about call admission control:
[Multiplay Solutions, Services Interfaces, System Basics Command Reference]
To configure TWAMP, include the twamp statement at the [edit services rpm] hierarchy as previously documented, but do not specify the twamp-server statement for any interface. There are no new CLI statements associated with this feature and the existing operational commands function as documented. [Services Interfaces]
To configure the mode, include the authentication-mode statement at the [edit services twamp server] hierarchy level and specify the value authenticated or encrypted. [Services Interfaces]
Flow aggregation template enhancements—Adds the following new fields to the flow record templates used for version 9 flow aggregation:
Operational Commands
For ease of operation the CLI now enables the user to present each vBGF separately. The new syntax is show services pgcp xxxxx gateway gw-name, where xxxxx represents the desired display. For example, to display vBGF-5 statistics use show services pgcp statistics gateway vBGF-5 .
Similarly, to display all existing vBGFs use the wildcard “*” to replace the gateway name: for example, show services pgcp statistics gateway * .
Trace Options
You can now configure trace options for extraction and storage of log information for the H.248 stack, the BGF core, and SBC utilities. To configure, include one or more of the following statements at the [edit services pgcp traceoptions flag] hierarchy level: session-trace, h.248-stack, bgf-core, sbc-util.
[Multiplay Solutions, Services Interfaces, System Basics Command Reference]
In JUNOS Release 9.5, AACL is supported only on MultiServices DPCs running on MX-series platforms. It is configured in a similar way to other rules-based services such as NAT, CoS, and stateful firewall. To configure AACL, include rule specifications for match criteria and actions at the [edit services application-aware-access-list] hierarchy level. You can chain AACL rules along with other service rules by including them in a service-set definition at the [edit services service-set] hierarchy level, as previously documented. There are no new operational commands associated specifically with AACL. [Services Interfaces]
To configure properties for statistics output, include the policy-decision-statistics-profile statement at the [edit accounting-options] hierarchy level. A new traceoptions configuration is available at the [edit services local-policy-decision-function] hierarchy level. To configure a dynamic profile to attach a specified service-set to an interface, include the service statement at the [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family inet] hierarchy level. The following new operational commands are supported:
[Services Interfaces, System Basics and Services Command Reference]
For information about how to purchase JUNOS software licenses, contact your Juniper Networks sales representative. [Software Installation and Upgrade Guide]
DHCP relay proxy helps improve security for service providers by hiding internal DHCP servers from the view of the attached DHCP clients and providing denial of service (DOS) protection. Also, in a network with multiple DHCP servers, DHCP relay proxy reduces access network traffic by forwarding a single lease to a client. In contrast to the extended DHCP relay, the extended DHCP relay proxy can be used in a logical router.
To configure DHCP relay proxy support, include the proxy-mode statement at the [edit forwarding-options dhcp-relay overrides] hierarchy level or the [edit forwarding-options dhcp-relay group overrides] hierarchy level.
The extended DHCP relay proxy is not compatible with the J-series DHCP server. Also, you cannot configure both the extended DHCP relay proxy and the extended DHCP local server on the same interface. [Subscriber Access]
JUNOS subscriber access scaling values—The following subscriber access scaling values are supported in this release:
The CLI has been enhanced to add the services hierarchy to the following additional hierarchies:
This feature enables you to configure a Mobile IP subscriber in a routing instance in a specific logical router based on the vendor-specific attributes (VSAs) returned from the RADIUS server during authentication of the subscriber.
Multiple logical router and routing instance support is available only when you configure local authentication for Mobile IP. When you instead configure RADIUS authentication, only the default logical router and routing instance are supported.
Only the local option is available for the order statement; the aaa option is not supported for nondefault logical routers and routing instances. Otherwise, all previously supported Mobile IP configuration statements are available at the new hierarchy levels. [Subscriber Access]
The format for the string is:
addr [/maskLen] [nexthop [cost]] [tag tagValue] [distance distValue]
[Subscriber Access]
Framed routes are used so traffic from the subsets can traverse the subscriber interface. By applying framed routes, you can extend the per-subscriber interface management to any subnetworks behind the dynamic subscriber interface.
To dynamically configure framed routes using values specified in Framed-Route Attribute [22], include the new junos-framed-route-ip-address-prefix variable with the route statement at the [edit dynamic profiles profile-name routing-options access] hierarchy level. For each route, you can configure variables for the next-hop IP address (junos-framed-route-nexthop), the cost metric (junos-framed-route-cost), and the preference value (junos-framed-route-distance).
Configuring support for access-internal variables is optional, but it ensures that if the next-hop value is missing in the Framed-Routes Attribute [22], values from the access-internal variables are used instead. To configure access-internal variables, include the new junos-subscriber-ip-address variable with the route statement at the [edit dynamic profiles profile-name routing-options access-internal] hierarchy level. For each access-internal variable, you can configure variables for the qualified next-hop (junos-underlying-interface) and the MAC address (junos-mac-address).
To monitor framed routes, issue the show route protocol access command. To monitor access-internal variables, issue the show route protocol access-internal command.
[Subscriber Access]
In this release the aggregate-clients statement enables you to either merge (the default action; available in a previous release) or replace the firewall filters, CoS schedulers, and IGMP configuration of multiple DHCP clients that share the same VLAN logical interface. When you choose to merge software components, the behavior is as follows:
When you choose to replace software components, each new client session replaces the previous session.
You can configure the aggregate-clients attribute for all interfaces or for groups of interfaces. This feature supports static VLANs. [Subscriber Access]
To configure ANCP for an individual VLAN, include the access-identifier statement at the [edit protocols ancp interfaces interface-name] hierarchy level. The access identifier no longer has to be unique across the router. Now it must only be unique for individual ANCP neighbors. You must specify neighbor ip-address in the access-identifier statement when the access identifier is unique only for a neighbor.
You can now configure the maximum number of discovery table entries accepted from neighbors. To configure this limit globally for all ANCP neighbors, include the maximum-discovery-table-entries statement at the [edit protocols ancp] hierarchy level.
You can now specify several ANCP parameters for individual neighbors in addition to setting global parameters for all neighbors. Individual neighbor configurations take precedence over the global configuration.
To configure individual neighbor parameters, you can include any of the following statements at the [edit protocols ancp neighbor ip-address] hierarchy level:
The output for the show ancp cos and show ancp subscriber commands has been enhanced to support this feature. For access identifers that are not unique across the network, you can issue the show ancp subscriber identifier identifier-string neighbor ip-address command to display subscriber information for a particular neighbor associated with the access identifier. [Subscriber Access, Protocols Command Reference]
To enable the WiMAX feature for Mobile IP, include the wimax statement at the new [edit services mobile-ip access-type] hierarchy level. To disable the WiMAX feature, include the generic statement at the [edit services mobile-ip access-type] hierarchy level.
To determine which release and version number of the WiMAX Forum Network Architecture is supported by the current Mobile IP implementation, enter the show mobile-ip wimax release command.
Reauthentication of WiMAX subscribers is not currently supported. [Subscriber Access, System Basics and Services Command Reference]
New and deprecated system log tags—The following system log message is new in this release:
The following system log messages are new in this release:
The following system log messages are no longer documented:
Backward compatibility is maintained by creating software links from /var/logs/logical-system-name to /var/logical-systems/logical-system-name.
The new file system access for each logical system enables logical system users to view trace logs and modify logical system files. Logical system administrators have full access to view and modify all files specific to the logical system.
[System Basics]
To configure checksum values for commit scripts, include the appropriate hash algorithms at the [edit system scripts commit file file-name checksum] hierarchy level. To configure checksum values for operations scripts, include the appropriate hash algorithms at the [edit system scripts op file file-name checksum] hierarchy level. To configure checksum values for events scripts, include the appropriate hash algorithms at the [edit event-options event-script file file-name checksum] hierarchy level.
To view the calculated checksum value, issue the file checksum (md5 | sha-256 | sha1) operational mode command. [Automation, System Basics and Services Command Reference]
You enable automatic configuration of VLANs by including the vlan-id statement in a dynamic profile at the [edit dynamic-profiles profile-name] hierarchy level and by referencing the dynamic profile in the auto-configure statement at the [edit interfaces interface-name] hierarchy level.
Using the vlan-id statement, you specify the junos-vlan-id variable for the VLAN ID. This statement and variable combination obtains an actual VLAN ID from a range of VLAN IDs that you specify at the [edit interfaces interface-name ] hierarchy level.
You enable automatic configuration of stacked VLANS by defining a dynamic stacked VLAN profile and using the vlan-tags statement at the [edit dynamic-profiles] hierarchy level. In the vlan-tags statement, you specify the junos-stacked-vlan-id variable for the outer VLAN ID and the junos-vlan-id variable for the inner VLAN ID. This statement and variable combination obtains an actual outer and inner stacked VLAN ID from a range of VLAN IDs that you specify.
You define VLAN or stacked VLAN ranges with the auto-configure statement at the [edit interfaces interface-name] hierarchy level. To define VLAN ranges, include the vlan-ranges statement at the [edit interfaces interface-name auto-configure] hierarchy level. You must then specify the dynamic VLAN profile using the dynamic-profile statement at the [edit interfaces interface-name auto-configure vlan-ranges] or [edit interfaces interface-name auto-configure vlan-ranges] hierarchy level, the VLAN interface type (inet) by using the accept statement at the [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile] or [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile] hierarchy level, and finally specify the VLAN ranges that you want accessing clients to use with the ranges statement at the [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile] or [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile] hierarchy level.
When specifying values for the low-tag and high-tag variables for the vlan-ranges or stacked-vlan-ranges statement, you can define tag ranges from 1 to 4094 or use the any option to specify the use of the entire VLAN range. You can use the clear auto-configuration interfaces interface-name command to manually remove a dynamically-created VLAN or stacked VLAN interface.
|
Note: You can only remove dynamically-created VLANs or stacked VLANs when no subscribers are using the interface either directly on that VLAN interface or on a separate IP DEMUX interface using that VLAN as its underlying interface. |
[Network Interfaces; Subscriber Access Configuration Guide]
When you configure the l3vpn-composite-nexthop statement and issue the commit command, the BGP session is immediately restarted. For more information, see PR 292173. [VPNs]
To prioritize a VPLS routing instance, configure the fast-reroute-priority statement at the [edit routing-instances routing-instance-name forwarding-options] hierarchy level. You can configure a priority of high, medium, or low. [VPNs]
The following extranet MVPN topologies are supported:
The configuration for extranet next-generation MVPNs relies on existing configuration statements.
If there is more than one MVPN routing instance on a PE router, extranet next-generation MVPNs require VT interfaces to be configured on all MVPN routing instances on a PE router that is designated to receive traffic from the same source. If there is only one MVPN routing instance on a PE router that has receivers for a particular source, the MVPN routing instance does not need to have a VT interface configured. VT interfaces are not required for unicast routing instances which can still rely upon label-switching interfaces (LSIs).
PIM-DM is not supported in the MVPN SP core for Draft-Rosen.
To configure a VLAN ID list, use the vlan-id-list list statement at the [edit interfaces interface-name-fpc/pic/portunit unit-number] hierarchy level.
To configure a group of VLAN tags, use the vlan-tags < (inner | inner-list list)> statement at the [edit interfaces interface-name-fpc/pic/port] hierarchy level.
|
Note: TPID is not supported with inner-list. |
An example configuration for this feature follows:
- interfaces {
-
- ge-1/1/0 {
- vlan-tagging;
- encapsulation flexible-ethernet-services;
-
- unit 10 {
- encapsulation vlan-ccc;
- vlan-id-list [20 30-40 45];
- }
- }
-
- ge-1/1/1 {
- flexible-vlan-tagging;
- encapsulation flexible-ethernet-services;
-
- unit 10 {
- encapsulation vlan-ccc;
- vlan-tags outer 200 inner-list [50-60 80 90-100];
- }
- }
- }
[Network Interfaces]
To configure a static pseudowire, include the static statement at the [edit protocols l2circuit neighbor address interface interface-name] hierarchy level. You must also configure the incoming-label label statement and outgoing-label label statement at the [edit protocols l2circuit neighbor address interface interface-name static] hierarchy level. You can also configure the static statement and sub-statements at the [edit protocols l2circuit neighbor address interface interface-name backup-neighbor neighbor] hierarchy level. If you configure the neighbor as static, you must configure the backup neighbor as static as well.
Note that when you configure static pseudowires, you need to manually compare the encapsulation, TDM bit rate, and control word of the router with the remote peer router and ensure that they match, otherwise the data path can be affected. For example, data would be forwarded from one end of the pseudowire, but would be dropped at the other end as there is a mismatch in the encapsulation, TDM bit rate, or control word.
You can also make it possible to ping a static pseudowire by configuring the send-oam statement at the [edit protocols l2circuit neighbor address interface interface-name static] hierarchy level. If you configure the send-oam statement, it applies to the backup neighbor as well. Once you have enabled this statement, you can ping the static pseudowire by issuing the ping mpls l2circuit command.
The command output of the show l2circuit connection command has been modified to indicate if a pseudowire on a router is static. The Layer 2 circuit interface is labeled with SP (meaning static pseudowire). [VPNs]
Table 1: JUNOS XML Tag Elements and CLI Command Equivalents New in JUNOS 9.5
[JUNOS XML API Operational Reference]
