|
|
Release Highlights
Release 12.0.0 includes the features described in this section.
AAA
- Support for Per Virtual Router Domain-Name Stripping
JunosE Software now enables you to strip domain names for a virtual router and specify what portion of the resulting user name to strip. When the domain name is stripped, the resulting string acts as a user name for that subscriber for RADIUS authentication and accounting.
The following new commands have been introduced to support the strip domain-name functionality:
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, the strip-domain functionality was available for the domain map configuration only. It can now be configured per virtual router.
IP
- Support for Sending ICMP Unreachable Messages for Static Routes Configured on Null Interfaces
You can now configure the router to send ICMP unreachable messages back to the originator when ping and traceroute packets reach the null 0 interface configured with a static route.
To configure the router to discard packets received on the null 0 interface that contains a static route and send ICMP unreachable messages to the originator, use the reject keyword with the ip route ipAddress ipMask null 0 command for IPv4 traffic and the ipv6 route prefix null 0 command for IPv6 traffic in Global Configuration or VRF Configuration mode.
Alternatively, to configure the router to discard packets received on the null 0 interface that contains a static route and not send ICMP unreachable messages to the originator, use the discard keyword with the ip route ipAddress ipMask null 0 command for IPv4 traffic and the ipv6 route prefix null 0 command for IPv6 traffic.
You can use the ICMP Unreach field that has been added to the output of the show ip static and show ipv6 static commands to view whether the sending of ICMP unreachable messages is enabled for null 0 interfaces.
The following commands have been modified to support transmission of ICMP unreachable messages for null 0 interfaces as next-hop points configured with static routes:
As part of this feature, the Juniper Networks INET MIB has been added to the JuniperMibs folder that contains the Juniper Networks enterprise-specific (proprietary) MIBs to support sending of ICMP unreachable messages for static IPv6 routes configured on null 0 interfaces. The INET MIB extends the protocol- independent inetCidrRouteTable MIB object present in the IP Forwarding Table MIB.
The following SNMP MIB objects have been added to the Juniper Networks INET MIB to support the functionality of sending ICMP unreachable messages for packets that reach null 0 interfaces as next-hops:
- juniInetStaticRouteTable—Contains a list of IPv6 static routes configured on this entity. The object definitions and indexing for this table are closely aligned with the inetCidrRouteTable object in the protocol-independent IP Forwarding Table MIB.
- juniInetStaticRouteEntry—Defines the attributes of an IPv6 static route, such as the prefix length of the IPv6 address and IPv6 address of the next-hop to reach the destination prefix.
- juniInetRouteStaticNullIntf—Configures an IPv6 static route with the null 0 interface as the next-hop to discard packets that arrive at the ingress interface.
The following enhancements have been made to the Juniper Networks IP MIB:
- The juniIpRouteStaticNullIntf MIB object has been added, which configures an IPv4 static route with the null 0 interface as the next-hop to discard packets that reach the ingress interface by sending or not sending an ICMP unreachable message.
- The juniIpRouteStaticNullIntf MIB object has been defined in the juniInetStaticRouteTable, which is an extension of the inetCidrRouteTable object. Currently, this table is implemented for IPv6 static routes only. IPv4 static routes are still accessed using the juniIpRouteStaticTable object. Such a method of access for IPv4 static routes is performed for synchronization with the usage of the inetCidrRouteTable object in lower-numbered releases of JunosE Software.
The following line module combinations on E Series routers support the functionality to configure the router to send ICMP unreachable messages for static routes configured on null 0 interfaces:
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, all packets that reached the null 0 interface with a static route as the next-hop were discarded by default.
Multicast
- Support for Including the Multicast Admission Bandwidth Limit of the Join Interface While Applying Multicast Admission Control
JunosE Software now enables you to include the bandwidth limit of the join interface while applying multicast admission control. In an OIF mapping scenario where the DSLAM performs per-subscriber multicast admission control to determine which subscriber interface data arriving on the mapped interface must be replicated, the router must also take into account the bandwidth limit of the subscriber join interface.
As a part of this feature, the oif-detail keyword has been added to the show ip mroute and show ipv6 mroute commands.
The following commands have been enhanced to support inclusion of the multicast bandwidth limit of the join interface:
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, in an OIF mapping scenario, all join interfaces were either blocked or admitted based on the admission bandwidth limit configured on the mapped interface.
- Enhanced Logging Support for Blocked Interfaces Exceeding the Configured Multicast Admission Bandwidth Limit
JunosE Software now generates logs for each subscriber interface and outgoing interface that is blocked when the multicast admission bandwidth limit on either the mapped interface or the join interface is exceeded.
As part of this feature, the mgtmGeneral event log category has been enhanced to display details of the multicast stream being blocked, the interface being blocked, the configured admission bandwidth limit, current bandwidth limit, and the reason for blocking.
Change in existing behavior: Existing feature extended as described here.
SNMP
- System MIB Support for Display of Maximum Fan Speed
Support has been added to the Juniper Networks System MIB to enable you to display the maximum fan speed state for the line module or IOA installed in a specific slot in the router. The juniSystemTempStatus object, which denotes the temperature status of a system, has been modified in the Juniper Networks System MIB to include a new attribute for the temperature sensor state to display the maximum fan speed state. A new temperature state, maxFanSpeed, has been added to reflect the state of fans running at their maximum speed.
Change in existing behavior: Existing feature extended as described here.
System Logging
Tunneling
|
Copyright © 2011, Juniper Networks, Inc. Report An Error |
|
|