|
|
Release Highlights
Release 12.3.0 includes the features described in this section.
DHCP
- Support for DHCP External Server, DHCP Local Server, DHCP Relay, and DHCP Relay Proxy on POS Access Interfaces
The following packet over SONET (POS) module combinations on E Series routers now support configuration of the DHCP external server, DHCP local server, DHCP relay, and DHCP relay proxy applications, alone or in combination, when the POS module is the access interface:
You can configure DHCP external server, DHCP local server, DHCP relay, and DHCP relay proxy on these POS modules in either a virtual router (VR) or a VPN routing and forwarding instance (VRF).
As part of this feature, the pos keyword has been added to the existing ip dhcp-local limit command. To specify the maximum number of IP addresses that the DHCP local server application can supply to all POS access interfaces or to a specific POS access interface, in the range 0–96000, use the ip dhcp-local limit command with the new pos keyword. For example:
! Set the IP address limit for all POS access interfaces to 1000
host1(config)#ip dhcp-local limit pos 1000
! Set the IP address limit for the specified POS access interface to 2000
host1(config)#ip dhcp-local limit interface pos 5/0/0 2000
! Restore the IP address limit for all POS access interfaces to the default value, ! 48000
host1(config)#no ip dhcp-local limit pos
To display the maximum number of IP address leases available for POS access interfaces, use the existing show ip dhcp-local limits command. For example:
host1#show ip dhcp-local limits*****************************************DHCP Local Server Address LimitsATM Limit - 48000VLAN Limit - 48000POS Limit - 1000Ethernet Limit - 48000Change in existing behavior: Existing feature extended as described here.
HTTP
- Preservation of the Original URL During Subscriber Session Redirection
The HTTP local server now supports the preservation of the original URL as a variable in the redirect URL.
You can use the ip http redirectUrl and ipv6 http redirectUrl commands to enable preservation of the original URL. For example:
host1(config-profile)#ip http redirectUrl "http://ispite.redirect.com/accessDenied.do?url=%(url)" preserveOriginalUrl
The following commands have been enhanced to support this feature:
Change in existing behavior: New feature added as described here.
IP
- Support for Configuring the Transmission of GARP Packets
Gratuitous Address Resolution Protocol (GARP) is a method of establishing an association between a logical IP address and a hardware address whenever an interface is created or the state of the interface shifts to the operationally up state.
In a fully scaled environment, transmission of a large number of GARP messages when a large number of secondary IP addresses are configured on an IP interface can create a storm of GARP packets. In such network topologies, reducing the number of GARP packets transmitted or disabling their transmission for interface changes reduces performance impact on the router and improves the processing efficiency of the router.
On Ethernet interfaces, you can now modify the number of GARP packets transmitted on a specific interface by using the ip gratuitous-arps command in Interface Configuration mode. You can also disable the transmission of GARP packets by using the no version of this command.
Regardless of whether transmission of GARP packets is disabled or the number of packets to be sent is modified using the ip gratuitous-arps command, one GARP is always sent for each virtual address of a VRRP interface and three GARPs are always sent when a failover occurs to the secondary link of the redundant port on GE-2 and GE-HDE line modules that are paired with GE-2 SFP I/O modules, 2xGE APS I/O SFP modules, and GE-2 APS I/O SFP modules, with physical link redundancy.
The following line module combinations on E Series routers support the configuration of transmission of GARP packets:
- On ERX14xx models, ERX7xx models, and the ERX 310 router:
- On E120 and E320 routers:
- ES2 4G line modules with ES2-S1 GE-4 IOA
- ES2 4G line modules with ES2-S1 GE-8 IOA
- ES2 4G line modules with ES2-S1 10GE IOA
- ES2 10G line modules with ES2-S1 GE-8 IOA
- ES2 10G ADV line modules with ES2-S1 GE-8 IOA
- ES2 10G line modules with ES2-S3 GE-20 IOA
- ES2 10G ADV line modules with ES2-S3 GE-20 IOA
- ES2 10G line modules with ES2-S2 10GE PR IOA
- ES2 10G ADV line modules with ES2-S2 10GE PR IOA
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, you could not disable the transmission of GARP packets or modify the number of GARP packets to be sent in response to creation of an IP interface or the transmission of the interface state from down to up.
IPv6
- Support for Route Tags for IPv6 Static Routes
You can now assign optional route tags for IPv6 static routes. The route tag is a 32-bit number in the range 0-4294967295. The default tag value is 0.
The tag keyword and tagVal variable have been added to the ipv6 route command to support this feature. The route tag can be used for route redistribution to routing protocols using route maps similar to the IPv4 static route redistribution.
The following command has been modified to support this feature:
The output of the following commands have been updated to support this feature:
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, you cannot assign a tag value to IPv6 static routes.
- Support for Configuring IPv6 HTTP Redirect URL from Profile Configuration Mode
You can now provide initial provisioning and service selection for the subscriber by using the IPv6 HTTP redirect URL feature. You use the ipv6 http redirectUrl command from the Profile Configuration mode to specify the URL to which a subscriber's initial Web browser session is redirected, as shown in this example:
host1(config)# profile guidEnt6
host1(config-profile) # ipv6 http redirectUrl http://ispite.redirect.comThe following commands have been enhanced to support this feature:
The following line module combinations on E Series routers support the configuration of the IPv6 HTTP redirect URL functionality:
Change in existing behavior: Existing feature extended as described here.
Policy Management
- Support for Statistics Collection for Output Policies on Tunnel Interfaces Based on Fragments
You can now configure the policy manager application to collect and store statistical counters for output policies attached to tunnel interfaces as a measure of the number of fragments. In certain network environments, it might be useful to monitor and track the outgoing traffic from a tunnel interface to which policies are applied in terms of number of fragments, instead of monitoring the outgoing policed traffic in terms of number of packets.
You can use the enable-frag-stats command in Global Configuration mode to enable the generation and storage of output policy statistics for tunnel interfaces as a number of fragments. By default, the output policy counters for tunnel interfaces is calculated as a number of packets.
You can enter the show enable-frag-stats command to verify whether collection of output policy statistics for traffic on tunnel interfaces is enabled. The packets field in the IP policy output section of the show ip interface tunnel interfaceSpecifier displays the number of packets or fragments transmitted from the tunnel interface for which output policies are applied. The value for the packets field denotes the measure of packets or fragments, depending on whether you enabled the collection of output policy statistics using the enable frag-stats command.
The following line module combinations on E Series routers support the configuration of output policy statistics collection in number of fragments:
The following commands have been added to support the control of client packets forwarded from DHCP relay:
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, the output policy counters for IP interfaces always displayed the statistics as number of packets. You could not configure the policy manager to collect statistics based on number of fragments transmitted from an outgoing IP interface.
PPP
- Support for Enabling the Sequencing of NCP Packets for POS Interfaces with PPP Encapsulation
You can now configure the packet over SONET (POS) physical interfaces that are configured with PPP encapsulation to be transitioned to the up state and enable the establishment of PPP sessions, even when the Network Control Protocol (NCP) packets are received out-of-sequence. By default, PPP sessions are established and POS interfaces are moved to the up state only when the NCP packets arrive in a sequence format.
You can use the no ppp ncp-Ordering-Required command in Global Configuration mode to cause the PPP sessions to be established, regardless of whether the NCP packets arrive in sequence. In such a case, the POS interfaces set up with PPP encapsulation move to the up state even when NCP packets are not in order. You can use the ppp ncp-Ordering-Required command in Global Configuration mode to cause the PPP sessions to be established only when the NCP packets arrive in sequence. In such a scenario, the POS interfaces with PPP encapsulation become active only if the NCP packets arrive in sequence.
Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, you could configure the POS interfaces configured with PPP encapsulation to be transitioned to the up state, when NCP packets were received in an out-of-order format, only using a shell command.
SDX Software and SRC Software
- Transfer of QoS Profile Attachment Information to PDP
JunosE Software now supports sending of the local QoS profile attachment information to the Policy Decision Point for a virtual router. To enable this feature, use the sscc option send-local-qos-profile-config command in Global Configuration mode.
The following command has been modified in this release:
The output of the following command has been modified in this release:
Change in existing behavior: New feature added as described here.
|
Copyright © 2011, Juniper Networks, Inc. Report An Error |
|
|
