### JunosE 12.2.0 Release Notes

> ### Known Problems and Limitations

> This section identifies the known problems and limitations in this release. For more information about known problems that were discovered at customer sites, you can log in to the JunosE Knowledge Base at https://www2.juniper.net/kb/, enter the defect ID number in the Search by Keyword field, and click Search.

> #### ANCP

> - On an E320 router that has established 3000 ANCP adjacencies with a client and traffic is initiated, the following behavior occurs sporadically: All existing Telnet sessions are disconnected and no new Telnet sessions can be established for several minutes. [Defect ID 83872]

> #### ATM

> - The line module resets when you issue the show nbma arp command after you have configured NBMA interfaces on an ATM line module. [Defect ID 88491]
> - When 16,000 PPPoA interfaces are configured on an OCx/STMx ATM line module paired with an OC3-4 I/O module in an ERX14xx model, ERX7xx model, or ERX310 router, Ping traffic passing through the line module on the restarting router experiences an outage of 103 seconds, which is beyond the maximum limit, after a unified ISSU from JunosE Release 9.2.0p1-0 to 9.3.0p0-12. This outage does not occur when the same configuration is applied on a Gigabit Ethernet interface. [Defect ID 179794]
> - When you issue the no atm atm1483 auto-configure upperInterfaceType lockout-time command in Profile Configuration mode, the lockout time range does not revert to the default values. [Defect ID 66544]
> - The inPacketOctetDiscards counter in the output of the show atm vc atm interface vcd command includes both inBytesDropped and inBytesUnknownProtocol statistics. The inBytesUnknownProtocol statistics should be displayed by a separate counter.

> At the major interface level, the inPacketDiscards counter includes both inPacketsDropped and inPacketUnknownProtocol statistics. The inPacketUnknownProtocol statistics should be displayed by a separate counter. [Defect ID 44286]

> - When a mirror rule that triggers on username is employed for packet mirroring of dynamic IP subscribers over ATM, removal of the rule does not disable packet mirroring. [Defect ID 175356]

> Work-around: Use a mirror rule that triggers on account session ID rather than on username.

> - When one or more ATM1483 attributes appears in a profile, the show configuration include-defaults command fails to display the default values for all possible ATM1483 attributes. [Defect ID 67157]
> - The output of the show atm arp command displays only 4096 entries when the line module is configured with more than 4096 NBMA ARP entries. [Defect ID 68849]
> - The baseline interface atm command fails for a VCD assigned by the router to F4 OAM circuits. [Defect ID 174482]
> - Unified ISSU is not supported when ILMI is configured on ATM interfaces. [Defect ID 176007/177297]
> - ATM line modules reset after unified ISSU completes at the LAC when an MLPPP bundle with three links are tunneled to the LNS. [Defect ID 178821]
> - For PPPoE, the AAL5 inPacket Discards counter might increment erroneously during call setup when a packet is passed directly to PPPoE for negotiation rather than being discarded. [Defect ID 51757]

> Work-around: Incremental InPacketDiscards during call setup do not necessarily indicate a problem. However, we recommend you investigate an excessive count because that might indicate a connection that cannot be successfully brought up for some reason, such as RADIUS denials or improper configuration.

> #### BFD

> - After you have shut down the interface to the next hop (for the route that is used to establish the BFD session), output for the show bfd session command erroneously indicates the shutdown interface as Management Interface (FastEthernet 6/0). [Defect ID 174271]

> #### CLI

> - When you issue a run show ppp command, the CLI changes the configuration level of the command line to Global Configuration mode rather than remaining at the level from which you issued the command. [Defect ID 52165]

> Work-around: Reissue the commands necessary to reenter the desired mode.

> - The logout subscribers all command may not log out all of the DHCP subscribers. Although the bindings and DHCP addresses are cleared, the show subscribers summary command may display some of the DHCP subscribers. [Defect ID 180176]

> Work-around: Try using the dhcp delete-binding all command. If this does not clear the subscribers, you may want to reload the line module to avoid further issues.

> #### DHCP

> - In the output of the show subscribers ipv6 command, the IPv6 Interface Id field, which denotes the EUI-64 IPv6 address of the subscriber's interface, always displays 0:0:0:0 and the Type field, which denotes the type of the subscriber, always displays unknown for IPv6 subscribers. This problem occurs for IPv6 subscribers in both a dual-stack network that contains both IPv4 and IPv6 subscribers and an environment that contains only IPv6 subscribers. [Defect ID 91618]
> - When 32,000 DHCPv6 subscribers are brought up over multiple virtual routers at a call setup rate (CSR) of 24 calls per second, the DHCPv6 local server stops responding. This problem occurs due to a deadlock between two instances of the DHCPv6 local server running on the router while the DHCPv6 client entry is being updated. [Defect ID 189282]
> - When approximately 10 DHCP subscribers are connected over Agent Circuit Identifier-based (ACI) VLAN subinterfaces, a few of the DHCP requests from clients are returned with negative acknowledgment responses from the DHCP local server. This problem occurs only on ES2 10G LMs and ES2 10G ADV LMs, and not on ES2 4G LMs. [Defect ID 189336]
> - DHCP packets are not forwarded to the DHCP server over dynamically created interfaces when all of the following are true: [Defect ID 180343]
> - DHCP relay or DHCP relay proxy is configured on the router.
> - The client-facing interfaces are created dynamically using bridged Ethernet over static ATM PVCs.
> - The ip auto-detect ip-subscriber command is configured to enable packet detection (packet triggering) and to trigger creation of dynamic subscriber interfaces.

> Work-around: To avoid this defect, do all of the following:

> - Do not use the ip auto-detect ip-subscriber command to enable packet triggering and to create dynamic subscriber interfaces.
> - Ensure that DHCP external server is configured in the virtual router.
> - Ensure that the set dhcp relay inhibit-access-route-creation command is configured in the virtual router to prevent DHCP relay from installing host routes by default.

> #### DHCP External Server

> - With the unique client ID option enabled, when two clients with the same MAC address or client ID are on an interface (where one client is connected over a router and relay and the other client is connected directly), sending a release request from one of the clients might terminate another client. [Defect ID 179759]
> - When DHCP relay and DHCP external server are configured in the same VR with server-sync enabled, bindings are not created in the DHCP external server when DHCP clients on an ATM bulk configuration interface stack and dynamic VLAN over Ethernet stack sends a renew message. [Defect ID 87087]
> - The DHCP renew counter and release counter (displayed with the show ip dhcp-external statistics command) are doubled rather than incremented for each renew and release sent. [Defect ID 78802]
> - When DHCP clients on an S-VLAN over bridged Ethernet stack configuration send a decline message to a router that has DHCP relay and DHCP external server configured in the same VR, the clients bindings are not removed from the DHCP external server. [Defect ID 87086]

> #### DoS Protection

> - A Telnet session closes when sending ipLocalBGP protocol traffic at a rate in the range 4096–4200 packets per second (pps) with suspicious control flow detection enabled. [Defect ID 81974]

> Work-around: When the traffic drops below 4096 pps, open a new Telnet session.

> #### Ethernet

> - When autonegotiation is enabled on Gigabit Ethernet interfaces with the speed automatically negotiate command, issuing the link selection command logs out subscribers. [Defect ID 87185]

> Work-around: Use the following commands to enable auto link selection (GE port redundancy) and to switch from one port to the other port:

> host1(config-if)#no link selection

> host1(config-if)#l ink failover force

> #### File System

> - When the primary SRP module is running JunosE Release 7.2.0 or a higher-numbered release and the standby SRP module is running a release numbered lower than Release 7.2.0 (as in a downgrade situation), you cannot display the files for the standby SRP module. [Defect ID 74104]

> #### Forwarding

> - When performing MAC validation to match subscriber demux entries with ARP host entries, the ES2 10G LM does an exact match, rather than a longest prefix match. The subscriber demux entry source address must be a /32 value matching the IP address of an ARP entry in order to validate the MAC address against that ARP entry. [Defect ID 79641]
> - On an E120 or E320 router that is running JunosE Release 11.2.1, the ES2 10G LM with an ES2-S2 10 GE PR IOA stops egress forwarding because of an egress IXP static RAM (SRAM) parity error. This problem is observed during the removal of the LM from its slot and reinsertion into the same slot when subscriber sessions are established. This behavior also happens when about 6000 subscribers are brought up and user traffic is transmitted. This problem depends on the type of user traffic sent. [Defect ID 189846]
> - When you attach certain hierarchical policies to subinterfaces as input policies, secondary input policies, and output policies, incoming traffic loss can occur when the number of subinterfaces to which the policies are attached exceeds 4600. [Defect ID 86741]
> - An ES2 10G LM resets when you attempt to remove a multicast port in a dual-stack environment that contains both IPv4 and IPv6 subscribers. [Defect ID 189867]
> - When PPPoE over LAG is configured on an interface, and you re-execute the PPPoE-over-LAG configuration before you delete the previous configuration, the ES2 10G LM line module resets. [Defect ID 179639]

> Work-around: Before you can re-execute the PPPoE-over-LAG configuration, delete the existing PPPoE-over-LAG configuration.

> - If you perform unified ISSU from JunosE Release 11.3.0 to a higher-numbered release on a router chassis with an ES2 10G ADV LM that contains a shared tunnel-server port or a dedicated tunnel-server port, the LM resets. The existing dedicated and shared tunnel-server sessions that were configured to terminate on the ES2 10G ADV LM are dropped when the LM resets. The LM comes back online, running the release to which it was upgraded, after it completes the generation of a core dump file. Also, new tunnel-server sessions are established correctly after unified ISSU is completed. [Defect ID 187728]
> - Specifying S-VLAN ranges that partially overlap does not work. [Defect ID 81918]

> For example, the following configuration fails because S-VLAN 22 falls within the previously specified S-VLAN range of 21–23.

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 401 426

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 427 712

> host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 22 22 101 110

> Work-around: You can do either of the following to avoid this problem.

> - Specify each S-VLAN within the partially overlapping range as individual S-VLANs, as in the following example:

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 401 426

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 22 22 401 426

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 23 23 401 426

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 427 712

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 22 22 427 712

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 23 23 427 712

> host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 22 22 101 110

> - Use fully overlapping ranges rather than partially overlapping ranges, as in the following example:

> host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 401 426

> host1(config-if)#lan bulk-config BulkDHCPCnfg1 svlan-range 21 23 427 712

> host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 21 23 101 110

> - Ethernet statistics are incorrectly displayed for virtual port 8 of the ES2-S1 GE-8 IOA when that module is paired with the ES2 10G LM or the ES2 10G Uplink LM. [Defect ID 174784]
> - After you configure fast reroute extensions to RSVP-TE to enable local protection for the ingress router of the primary LSP by using bypass tunnels, forwarding of IPv6 traffic to some of the labeled BGP routes or IPv6 destinations over ES2 10G LMs and ES2 4G LMs fails. [Defect ID 189451]
> - The ES2 10G LM does not support framed routes configured for dynamic subscriber interfaces. [Defect ID 83154]
> - On the ES2 10G LM, a VLAN ID of 0 assigned to an interface can prevent packets from being properly forwarded. [Defect ID 176125]
> - For IP and VLAN policies attached to VLAN subinterfaces on ES2 10G LMs and ES2 10G Uplink LMs, the output policy counters for outgoing control and exception packets are incorrectly displayed in the output of the show ip interface and show vlan subinterface commands. These counters are not incremented correctly in the VLAN policy output section of the output of the show vlan subinterface command and in the IP policy output section of the output of the show ip interface command. [Defect ID 190083]
> - In a scenario in which approximately 2000 GRE tunnels are configured, filter rules are configured in the policy lists to filter traffic on 1000 tunnels, and forward rules are set up in the policy list to forward traffic from 1000 tunnels, 300 Mbps of traffic is initially filtered. A traffic drop is observed for a brief period and traffic filtering resumes shortly thereafter. Gradually, traffic filtering recedes and stops completely, enabling all of the traffic over the GRE tunnels to start flowing. [Defect ID 190203]

> #### GRE

> - After you perform a unified ISSU operation or a stateful SRP switchover from JunosE Releases 11.2.0 through 12.0.0 to JunosE Release 12.1.0, GRE tunnel interfaces configured on ES2 10G ADV line modules that function as shared tunnel-server ports do not appear. This problem occurs only if you configured the tunnel interface as the analyzer interface. [Defect ID 188593]
> - After a stateful SRP switchover operation, if you delete the shared tunnel-server port configured on an LM and configure the shared tunnel-server port on another LM, the GRE tunnels are not transferred from the LM on which the tunnel-server port was deleted to the LM on which the tunnel server was configured. The removed tunnels do not come up until you perform an event that triggers the restoration of the GRE tunnels, such as addition of new tunnels, deletion of other existing tunnels, or configuration of an LM on the router chassis. This problem occurs only with GRE tunnels after the completion of a stateful SRP switchover procedure. [Defect ID 187804]

> Work-around: To correct this problem, create a dummy GRE tunnel interface for temporary purposes using the interface tunnel command. Creation of the dummy tunnel interface causes the previously-configured GRE tunnel-service interfaces to be restored on the changed shared tunnel-server port on the LM. You can delete the dummy tunnel interface after all the GRE tunnel interfaces are up.

> #### Hardware

> - Load balancing of IPv6 traffic with prefixes of lengths other than /128 does not occur properly on LAG interfaces and equal-cost multipath (ECMP) links configured on ES2 4G LMs and GE-2 LMs. [Defect ID 189885]
> - Load balancing of IPv6 traffic with prefixes of lengths other than /128 does not occur properly on access interfaces in a LAG bundle configured on an ES2 10G LM. [Defect ID 189966]

> #### ICR

> - When you configure ICR settings using a CLI macro, ICR commands are run in quick succession. Sometimes, in such a scenario, the active SRP module resets if the event that causes the change of state of the VRRP instance reaches the ICR application before the ICR partition has been created. [Defect ID 184095]

> Work-around: To avoid this problem, add an additional delay of one second using the sleep command in the macro, before the ip vrrp vrid enable command that is written in the macro to enable VRRP instance.

> For example, consider a macro that contains the following commands:

> ip vrrp vrid enable

> ip vrrp vrid icr-partition partitionId

> Modify the macro, as follows, to add a delay of one second before the VRRP instance ID is enabled on the router and a delay of another second before the ICR partition that corresponds to the VRRP instance is created:

> sleep 1

> ip vrrp vrid enable

> sleep 1

> ip vrrp vrid icr-partition partitionId

> - If you saved the running configuration of the router as a script file (.scr) and execute the script to apply the settings on the router, ICR partition configuration commands in the .scr file might fail to add group members to the partition. This problem happens when the subscriber configuration in the .scr file is placed before the ICR partition configuration. However, this problem does not occur if you used a system configuration (.cnf) file to set up the router. [Defect ID 183913]

> Work-around: To correct this problem and enable ICR partitions to be created correctly, make sure that you add the ICR partition configuration before the subscriber interface configuration in the .scr file. You can perform this reordering by modifying the .scr file to place the commands that configure subinterfaces for ICR partitions before the commands used for VLAN-based or S-VLAN-based grouping of subscribers.

> #### IGMP

> - The E Series router IGMPv3 proxy does not operate correctly in the presence of IGMPv2 queriers. [Defect ID 46039/46045]

> Work-around: If an IGMPv2 router is present on the network, do not configure version 3 with the ip igmp-proxy version command on that network interface. (Version 2 is the default.)

> - The default value for the IGMPv3 proxy unsolicited report interval timer should be 1 second rather than 10 seconds (the value for v2). [Defect ID 46040]
> - When more than about 100,000 mapped OIF entries are configured on a virtual router, issuing the no virtual router command for this and other virtual routers does not delete all the virtual routers within the deletion timeout interval (3 minutes). The virtual routers do eventually delete after this timeout. [Defect ID 63882]
> - The E Series router does not log a warning when it receives an IGMPv2 query but is not configured to use IGMPv2 on the interface. [Defect ID 46046]
> - IGMPv3 proxy is not supported. [Defect ID 46038]

> #### IP

> - When a router configured with PIM on a virtual router undergoes multiple warm restarts, the router subsequently hangs when an IP profile is configured. [Defect ID 176470]
> - If you have a large configuration on a hybrid module combination (OC3/STM-1 GE/FE line module with the OC3-2 GE APS I/O module), boot from NVS, and issue the slot erase command before booting has completed, the line module resets. [Defect ID 64104]

> Work-around: To recover from the error, issue the slot reload command anytime after the module begins to reset.

> - Deleting a VRF with 32,000 static subscriber interfaces fails to complete. [Defect ID 82670]

> Work-around: Use a macro to delete all static subscriber interfaces before you delete a VRF.

> - The ip route permanent command does not work properly. [Defect ID 34303]

> Work-around: Issue the ip alwaysup command to prevent the route from being removed from the IP routing table after the interface is shut down.

> - Traffic statistics for dynamic subscriber interfaces associated with Mobile IP subscribers are not maintained as the subscribers move between Mobile IP nodes. Consequently the reported interface statistics are only the values accumulated since the last time a mobile node moved. [Defect ID 174509]
> - When you change the demultiplexer type on a primary interface that has 1024 demultiplexer table entries, the ICC ping threshold times out due to the removal of the old entries and the addition of the new ones. [Defect ID 182218]
> - After an SRP stateful switchover completes on an ERX1410 router configured with a single VPN routing and forwarding instance (VRF) and Network Address Translation (NAT), the SRP module that becomes active after the switchover resets. [Defect ID 180058]

> #### IPSec

> - IPSec tunnels created over Fast Ethernet interfaces fail to come up. [Defect ID 179256]

> Work-around: After you create the tunnel, bounce the tunnel interface by issuing the shutdown/no shutdown command sequence. The tunnel comes up successfully.

> - In a network where you use the tunnel signalling command to specify that the security parameters and keys are configured manually for IPSec tunnels between VRs, the line modules reset when you delete and then re-create the IPSec tunnels. If you attempt to configure the tunnels again after the modules come back up, the line modules reset again.

> Work-around: Configure the IPSec tunnels to use ISASKMP/IKE to negotiate SA and establish keys. [Defect ID 178304]

> #### IS-IS

> - On a router configured with IS-IS and BFD, using the redundancy force srp command to force an SRP switchover sometimes brings down IS-IS and BFD. [Defect ID 179287]
> - IS-IS graceful restart (nonstop forwarding) does not work on the broadcast interface when the restarting router is the designated intermediate system (DIS). Graceful restart works properly when the restarting router is not the DIS. [Defect ID 61496]
> - When you configure the metric-style as wide for two routers connected in an IS-IS domain using the metric-style wide command in Router Configuration mode, both the routers learn the routes of each other correctly by generating and accepting only new-style TLVs with wider metric fields. When you change the metric-style from wide to narrow using the metric-style narrow command to enable the routers to accept only old-style TLVs with a narrow (six-bit) metric field, the routing table is not properly updated and the neighboring routers do not purge the previously learned routes to accept narrow metric fields. The routers continue to use the wider metric fields in the routing tables. [Defect ID 187607]

> #### L2TP

> - On a router configured as an LNS device with two pairs of line modules for high availability and L2TP subscriber sessions, after you perform a stateful line module switchover in one of the pairs, the secondary line module that takes over the role of the primary after the switchover process (ES2 4G LM with Service IOA) might reset. This problem occurs intermittently when subscribers are logging out or are being disconnected. [Defect ID 187732]
> - If you perform a unified ISSU operation on an E120 router or an E320 router that contains two pairs of line modules configured for stateful line module switchover and functions as an LNS device, the SRP module resets during the unified ISSU process. This problem occurs when any one of the following conditions are met: [Defect ID 186910]
> - A certain number of L2TP subscribers are already connected to the router and more subscriber sessions are attempted to be established during the unified ISSU process.
> - The logged-in L2TP subscribers are logged out and the subscriber sessions are attempted to be reestablished.
> - After the initialization phase of the unified ISSU process is started and completed, a stateful line module switchover is performed and another unified ISSU process is performed while more subscribers are logging in.
> - After a unified ISSU completes on a router functioning as an L2TP access concentrator (LAC), traffic outages occur on the L2TP network server (LNS)-facing interface at the LAC in a configuration with 16,000 or 32,000 L2TP sessions over 500 tunnels. [Defect ID 180147]
> - Approximately 25 percent of the total number of L2TP subscriber sessions are terminated and reestablished after a long time (about 25 minutes for 8000 sessions) when an ATM line module on a router that functions as the LAC device is reloaded. [Defect 187515]
> - L2TP subscriber sessions that were previously established are disconnected when you perform a stateful SRP switchover operation in a scaled environment. [Defect ID 187454]
> - When you perform a stateful SRP switchover procedure on an LNS device that contains an ES2 4G LM with Service IOA (tunnel server module), some of the 16,000 subscriber sessions over 16,000 tunnels that are established are terminated. This problem occurs when OSPF is used as the routing protocol between the LAC and LNS devices in the L2TP tunnel, and with the number of L2TP retransmission attempts configured as 10. [Defect ID 187358]

> #### LDP

> - Some of the LDP sessions on ATM line modules do not come up when you perform a unified ISSU operation on an ERX router, which is the restarting router, from JunosE Release 10.3.3 to Release 11.0.3. This problem occurs when an ERX router functions as the restarting router and an E120 or E320 router functions as the helper router. [Defect ID 189588]

> #### MLD

> - MLDv2 proxy is not supported. [Defect ID 46038]
> - The E Series router does not log a warning when it receives an MLDv1 query but is not configured to use MLDv1 on the interface. [Defect ID 46046]
> - The E Series router MLDv2 proxy does not operate correctly in the presence of MLDv1 queriers. [Defect ID 46039/46045]

> Work-around: If an MLDv1 router is present on the network, configure version 1 with the ipv6 mld-proxy version command on that network interface. (Version 2 is the default.)

> - The default value for the MLDv2 proxy unsolicited report interval timer should be 1 second rather than 10 seconds (the value for v1). [Defect ID 46040]

> #### MLPPP

> - Failure to meet all of the following conditions for fragmented packets can result in an incorrect operation during packet classification of the resulting reassembled packet: [Defect ID 50111]
> - The initial fragment of a packet must either contain the entire MLPPP packet or be greater than 128 bytes.
> - The fragment size of the peer must not be lower than 128 bytes.
> - The initial fragment of a packet must be larger than subsequent fragments of that packet.

> #### Mobile IP

> - The setup rate for Mobile IP client sessions decreases when you repeatedly bring a large number of sessions down and back up. [Defect ID 178760]
> - The clear ip mobile binding nai @realm command does not work. [Defect ID 178652]

> Work-around: Use the following version of the command instead:

> clear ip mobile binding nai user@realm
> - The @realm variable and the @ keyword alone do not work for the show ip mobile binding command. [Defect ID 178653]

> Work-around: You can use the user@realm syntax instead to display the binding for a specific user, as in this example:

> host1#show ip mobile binding nai xyz@example.com

> Alternatively, you can display the entire Mobile IP binding table by issuing the show ip mobile binding command without additional options.

> - When mobility bindings are present and you delete the Mobile IP home agent with the no virtual router command, Mobile IP sends a RADIUS Acct-Stop message with no accounting statistics for the subscribers. [Defect ID 179081]

> Work-around: Issue the clear ip mobile binding all command before you issue the no virtual router command. The clear command clears all the MIP subscribers and sends a RADIUS Acct-Stop message with the appropriate accounting statistics for the subscribers.

> #### MPLS

> - When MPLS and IS-IS are configured on Ethernet interfaces, you cannot delete the interface after the IP address is removed. This issue is not a problem on Ethernet VLAN interfaces. [Defect ID 66813]

> Work-around: Issue the no mpls command to disable MPLS, then delete the interface.

> - When you issue a traceroute or trace mpls command to trace the paths of router packets over MPLS interfaces on an ES2 10G LM or ES2 10G Uplink LM, the results include an extra unknown host. [Defect ID 174537]
> - If LSPs are announced into IS-IS, then the IS-IS routes cannot be used for multicast RPF checks, because LSPs are unidirectional. [Defect ID 28526]

> Work-around: Configure static RPF routes with native hops when LSPs are autoroute announced to IGPs.

> - When the IPv4 explicit null label appears anywhere other than at the bottom of the label stack, TTL expiration for this label is not handled correctly. As a result, the traceroute command does not work correctly for LSPs that have the IPv4 explicit null label anywhere other than at the bottom of the label stack. [Defect ID 76037]
> - In a scaled environment with a large number of MPLS RSVP-TE tunnels configured, the states of the hello adjacency instances in the State field in the output of the show mpls rsvp hello instance command are displayed as Down for loopback interfaces. The correct behavior is that the RSVP-TE hello adjacencies must always be in the Up state for loopback interfaces. [Defect ID 189565]

> #### Multicast

> - When you configure more than 10,219 outgoing interfaces (OIFs) on the same ES2 10G LM in a single multicast group, the configuration of the multicast group's OIF membership from the SRP module to the line module exceeds the size of a single message and is sent in fragments.

> Because of this fragmentation, the ES2 10G LM generates the following error message: [Defect ID 81768]

> pc: 0x9e5c88: -> fatalPanic(void) offset: 0x8

> #### Netflow

> - Flow sampling stops after a cold switchover on a router that is configured with 16 VRs and 32 interfaces per VR, when all flows are passing through the configuration (32 flows per VR). [Defect ID 74477]

> Work-around: After the cold switchover is completed, reissue the ip flow-sampling-mode packet-interval 10 command on each VR, even though the command is present in the configuration.

> - The OC3/STM1 GE/FE line module might reset after sending Ethernet traffic into a VPLS network in a test environment when Ethernet packets are flooded to remote VPLS bridges. [Defect ID 74540]

> #### OSPF

> - When PPPoE clients are connected to a router that functions as a LAC on one side of an L2TP tunnel and another router operates as an LNS device on the other side of the tunnel, OSPF graceful restart abruptly terminates at the helper router (which is the LAC device) and a traffic outage occurs. This problem occurs only when the following conditions are met:
> - If you perform a unified ISSU process on the LNS (which is the restarting router)
> - If you configure OSPF as the routing protocol and OSPF graceful restart behavior is configured on both the routers.

> In such a case, during the unified ISSU operation, after the upgrade phase (stateful SRP switchover) is completed at the LNS device, the LAC device stops the graceful restart and the adjacency with LNS goes down. This brief disruption in user data traffic happens if both the unified ISSU and OSPF graceful restart processes take a longer duration than the configured OSPF dead interval and OSPF graceful restart time.

> To avoid this problem of adjacencies between the restarting router and the helper router from being reset, we recommend that you increase the dead interval and graceful restart timer values for the OSPF protocol to appropriate values, based on the level of complexity of the network and configuration settings, to enable OSPF graceful restart to be completed successfully. For example, in certain environments, you need to increase both the OSPF graceful restart timer (by using the graceful-restart restart-time command in Router Configuration mode) and the OSPF dead interval (by using the ip ospf dead-interval command in Interface Configuration mode) values to 300 seconds for graceful restart to complete correctly. [Defect ID 188341]

> #### Policy Management

> - On the E320 router, redirecting a large configuration with thousands of interfaces to a script file can take a long time, perhaps exceeding a half-hour depending on the configuration. [Defect ID 80429]
> - If you have removed the last rule in a policy list, the router generates a warning only after you exit Policy List Configuration mode. If you have removed the last policy rule and then added a classifier group before you exit Policy List Configuration mode, the router does not generate a warning about removing the last rule. [Defect ID 83834]
> - When an MD-Port-Number value greater than 65,535 is sent to an E120 or E320 router by means of a COA request, the value that is displayed in the UDP header of mirrored packets is the actual value minus 65,536. For example, an MD-Port-Number of 65,540 is displayed in the mirrored packet as 4. [Defect ID 84712]
> - When you reload the slot holding a GE-2 or GE-HDE line module and you have configured more than about 2000 policies with rate limiting on that module, the drop count becomes more than expected. This unexpected drop count does not occur when you create the same configuration after you reload the router to the factory-default configuration. [Defect ID 175696]
> - During packet mirroring for secure IPv6 policies, if you configure SNMP secure packet mirroring traps, the traps do not contain any fields to include the IPv6 prefix. However, for IPv4 policies, the IPv6 address field is present in the packet mirroring traps. [Defect ID 189862]
> - On the E120 and E320 routers, when a mirror rule is deleted after a CoA request is sent with Juniper-LI-Action set to No-Action, the existing mirroring session is not disabled. [Defect ID 84826]
> - On E320 line modules that support secure policies, the SRP module enables you to configure more than 1022 secure policies per module. [Defect ID 175756]

> Work-around: To avoid potential performance issues, we recommend that you do not configure more than 1022 secure policies per module.

> - Unified in-service software upgrade (unified ISSU) is not supported on an E120 or E320 router if a hierarchical policy is attached to an external parent group. [Defect ID 177478]
> - When you modify a rate-limit profile in Global Configuration mode after the system is in a scaled state, changes to the rate-limit profile fail owing to lack of adequate policy resources. However, the changed value of the rate-limit profile is displayed in the output of the show rate-limit profile command. [Defect ID 79342]

> Work-around: To avoid this problem, do not update the rate-limit profile in Global Configuration mode in a scaled environment.

> - When you enter the no ip policy-parameter hierarchical parameterName command or no ipv6 policy-parameter hierarchical parameterName command for a hierarchical policy-parameter type in Interface Configuration mode, the explicit reference of the parameter is removed successfully from the interface. However, the Referenced by interfaces field in the output of the show policy-parameter command does not change from the previously configured value to implicit. [Defect ID 183957]

> Work-around: To correct this problem, remove the entire interface configuration.

> #### PPP

> - When line high availability is configured on a router, the following errors appear with statistical information: [Defect ID 187885]
> - The show ppp interface full command output displays erroneous values, mainly for the fields under the Authentication Statistics section, which alternate between 0 and n for each instance of the entry of this command to display accumulated counters since the session was established.
> - The values returned in the Interim-Acct messages are incorrect and inconsistent, which causes wrong values to be displayed for the relevant accounting-related attributes in the radiusSendAttributes event log. The recorded values do not depict the accurate statistics sent across the PPP subscriber interface.

> These problems do not occur when stateful line module switchover is not configured on the router.

> - On a pair of line modules configured for redundancy, if you disable the primary module in the redundancy group, previously established L2TP sessions are not reconnected. This problem occurs with PPP over ATM interfaces and 16,000 L2TP subscriber sessions. However, this problem does not occur with static and dynamic PPPoE over ATM subinterfaces. [Defect ID 187085]

> #### PPPoE

> - The E Series router erroneously accepts a PADI with a payload length of 0 instead of rejecting it and incrementing the PPPoE Invalid PAD packet length counter. [Defect ID 48356]

> #### QoS

> - You cannot paste a load-rebalance command string that uses the percent option into a console or Telnet session from show configuration output because the output displays the % sign rather than the percent keyword that was submitted with the command and the percent sign is not recognized by the CLI. [Defect ID 81705]
> - The dynamic shaping rate calculated by the simple shared shaper can vary because of the variation in the enqueue rate of the constituent queues. Even when the offered load is constant, the mechanism that calculates the enqueue rate introduces a slight variation, introducing a slight variation in the calculated dynamic shaping rate. [Defect ID 80938]
> - The no qos-parameter-define definition command does not delete the specified QoS parameter definition. [Defect ID 176844]

> Work-around: Remove the interface and add the desired QoS parameters when you re-create the interface instead of deleting the definition.

> - The compound shared shaping feature does not work properly on egress forwarding ASIC 2 (EFA2)-based ATM line modules when the shared shaper is queue-controlled as opposed to node-controlled. In a node-controlled configuration, in which you configure the shared-shaping rate on the best-effort scheduler node for the logical interface, integration of the EFA2 and ATM segmentation and reassembly (SAR) schedulers functions properly. However, in a queue-controlled configuration, in which you configure the shared-shaping rate on the best-effort queue for the logical interface, integration of the EFA2 and ATM SAR schedulers does not function properly. [Defect ID 69167]

> Work-around: Use node-controlled compound shared shaping configured on the best-effort scheduler node with EFA2-based ATM line modules.

> - Simple shared shaping does not function correctly when it is used for 32,000 subscribers on an ES2 10G ADV LM. However, when you change the shaper to compound shared shaping, it works properly. Also, simple shared shaping does not function correctly for 16,000 subscribers on an ES2 10G ADV LM. [Defect ID 183512]
> - When 32,000 subscribers with 128,000 QoS queues are brought up on an ES2 10G or ES2 10G ADV LM, the LM resets if you modify the QoS profile that contains the best-effort IP or VLAN node rule, which references a scheduler profile configured with shared shaping rate, to a scheduler profile configured with legacy shaping rate. [Defect ID 183291]

> Work-around: To avoid this problem, apply shared shaping on the best-effort queue, instead of on the best-effort node.

> - When QoS resources such as failure nodes and statistics bins are exhausted because of insufficient memory available on the line module, the failures are properly logged, but additional log messages are generated every 10 minutes that report zero failures. [Defect ID 85105]
> - The CLI erroneously enables you to configure a QoS profile with the ethernet node group command. [Defect ID 80861]
> - On a router that has both an ES2 10G LM and an ES2 4G LM installed, the byte count reported by the show fabric-queue egress-slot command is incorrect. The reported packet count is correct. [Defect ID 80965]
> - When you configure an E120 or E320 router with an ES2 10G ADV LM as a LAC on one side of an L2TP tunnel and as a LNS to receive packets from the LAC on the other side of the tunnel, use RADIUS servers for authentication of subscribers on both sides of the tunnel, and attempt to bring up 16,000 subscribers on the L2TP tunnel, the LM that has subscribers on the LAC side of the tunnel resets when approximately 8000 logged-in subscribers are logged out and try to reestablish the connection. [Defect ID 184118]
> - Only the headings for S-VLAN aggregate statistics are contained in the bulk statistics (.sts) file that collects QoS statistics on egress queues for various interface types. The corresponding aggregate statistics are not displayed in the corresponding data fields. This problem occurs only when the manual method of data transfer from the router to the receivers is employed by using the manual-xfer keyword with the bulkstats collector collect-mode command. This behavior is not observed when the automated collection method is configured using the auto keyword with the bulkstats collector collect-mode command for the agent to transfer the bulk statistics file to the host when the interval for which the collector transfers data from the router to the receivers expires. [Defect ID 187592]

> #### RSVP-TE

> - After stateful SRP switchover, forwarding of VPN traffic might not resume if the core interface that carries an MPLS base tunnel with LDP over RSVP-TE flaps (constantly goes up and down). [Defect ID 182019]

> #### SDX Software and SRC Software

> - If you perform a stateful SRP switchover operation on an E320 Broadband Services Router with an SRP-100 module that acts as an LNS device, the rate-limit profile that is applied from the SRC client does not take effect on the already logged-in subscribers. This problem occurs when all of the following conditions are satisfied:[Defect ID 189540]
> - Stateful line module switchover is activated on the LNS device.
> - Rate-limit profile is associated with the output policy applied on the subscriber interfaces for L2TP sessions.
> - The output policy is configured using the SRC client on the router to the subscribers while they are logging in.

> If you modify the rate-limit profile attached as the output policy on the subscriber interface and apply the policy using the SRC client after the subscribers have logged in or after a stateful line module switchover is completed, the change in rate-limit profile takes effect for the subscribers.

> #### Server Card Manager (SCM)

> - High availability mode transitions to the pending state when you perform the following steps. The high availability state of the system is displayed in the output of the show redundancy detail command.
> 1. Configure a shared tunnel-server port on an ES2 4G line module that functions as the primary in a redundancy group of line modules.
> 2. Bring up a GRE tunnel on the primary line module.
> 3. Perform a line module redundancy operation to switch over from the currently active primary to the standby module.

> When the system is in the pending state, the SCM application running on the router becomes unsupported for 5 minutes, and then it returns to the active state. The client field in the output of the show redundancy clients command displays the status of the SCM application. [Defect ID 188489]

> #### Service Manager

> - After you activate an independent IPv6 service and issue either of the following commands on the default virtual router or any other virtual router, except the one on which the subscriber session is active, no output is displayed in the CLI interface: [Defect ID 181929]
> - show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier
> - show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier service-session serviceName

> This problem also occurs when a subscriber is authenticated using a RADIUS server for a combined IPv4 and IPv6 service in a dual stack.

> Work-around: To avoid this problem, use the show service-management owner-session ownerName ownerId command to display subscriber session information based on the session owner, instead of the show service-management subscriber-session subscriberName interface interfaceType command to display details on subscriber sessions.

> - Activation of service sessions for a subscriber with DHCPv6 over IPv6 bindings using the CoA method that uses RADIUS Change-of-Authorization-Request (CoA-Request) messages and VSAs does not work if the service session was previously activated using the RADIUS login method that uses Access-Accept messages and VSAs. However, this problem does not occur for IP subscriber service sessions. Also, this problem does not occur if service sessions for subscribers with DHCPv6 over IPv6 bindings are activated only using the CoA method. [Defect ID 189403]

> #### SONET

> - You cannot use the highest sensitivity bit-error rate setting (a value of 9) associated with APS/MSP alarm when you issue the threshold sd-ber command to configure a cOCx/STMx line module with cOC12-APS-capable IOAs. [Defect ID 72861]

> Work-around: Use only a value in the range 5–8 when you issue the threshold sd-ber command for this module combination, as in the following example:

> host1(config)#controller sonet 2/1

> host1(config-controll)#aps group boston

> host1(config-controll)#aps protect

> host1(config-controll)#threshold sd-ber 6

> #### SRC Software and SDX Software

> - When multiple IPv6 interfaces are configured with policies attached from SRC, only some of the IPv6 interfaces have the policies attached. [Defect ID 179498]
> - Changing the SSCC status (enable/disable) while IPv6 interfaces are configured might cause the SRP to reset. [Defect ID 179537]

> #### Stateful SRP Switchover (High Availability) and IP Tunnels

> - When you perform a stateful line module switchover on E120 and E320 routers with an SRP-320 module that is configured with two high availability pairs of line modules, when subscriber sessions are being established, one of the LMs (ES2 4G LM with Service IOA) that functions as the secondary module takes over the role of the primary and reaches the online state. However, the newly configured primary LM resets shortly after it is online and a core dump file is generated. [Defect ID 187860]
> - A packet loss sometimes occurs during stateful SRP switchover when you use the ping command on a router that is configured for OSPF graceful restart, and is connected to a helper router in the OSPF IPv6 broadcast network and another helper router in the OSPF IPv6 backbone area. [Defect ID 181470]
> - ERX7xx model, ERX14xx model, or ERX310 router:
> - When you use the ping command with the IPv6 address of the helper router in the multicast area as the destination address and the loopback address of the helper router in the backbone area as the source address, a packet loss of 2 seconds occurs for the first stateful SRP switchover. However, no packet loss occurs for successive stateful SRP switchovers.
> - When you use the ping command with the IPv6 address of the helper router in the broadcast network as the destination address and no source address when stateful SRP switchover is performed the first time, an identical packet loss occurs. In this case too, no packet loss occurs during subsequent switchovers.
> - E120 router or E320 router:
> - When you use the ping command with the IPv6 address of the helper router in the broadcast network as the destination address and the loopback address of the helper router in the backbone area as the source address, no packet loss occurs.
> - When you use the ping command with the IPv6 address of the helper router in the multicast area as the destination address and no source address, a packet loss of 1–2 seconds sometimes occurs during stateful SRP switchovers.
> - After you configure a high availability pair of line modules on a router, if you administratively disable the slot that is in an online state in which the primary line module resides by entering the slot disable command, the secondary line module takes over by recovering all the applications running on the primary module to a stable state and the slot in which the primary module resides transitions to the disabled (admin) state. If you disable the newly configured online line module in the high availability pair and enable the slot in which the original standby line module resided, it remains in the initializing state. [Defect ID 186211]

> #### Subscriber Management

> - When a dynamic GRE tunnel interface for Mobile IP relocates between SM modules because the original SM reloads, Mobile IP deletes the relocated tunnel interface. [Defect ID 178399]
> - When a subscriber has subscribed for a service, service session accounting records always contains a default Acct-Terminate-Cause value of 10. This value remains unchanged even after you use the terminate-code command to configure a custom mapping between application terminate reasons and RADIUS Acct-Terminate-Cause attributes. [Defect ID 181043]
> - Dynamic subscriber interfaces continue to remain in the down or not present operational state in either of the following scenarios: [Defect ID 81269]
> - If you configured a dynamic interface column, such as a dynamic bridged Ethernet interface, dynamic VLAN interface, or an ATM interface, and when any one of the following conditions is satisfied:
> - The major interface is bounced (shut down and reenabled)
> - The major interface is shut down, which cause the dynamic VLAN interfaces to be removed
> - The physical link goes down and comes back up
> - The line module is removed and reinserted
> - If you configured a static interface column and removed the major interface

> These scenarios might occur if you administratively issue the shutdown and no shutdown commands on the major interface in which the dynamic interface column is configured.

> Work-around: Use the no interface ip ipAddress command to remove the dynamic subscriber interfaces. Although you can use the dhcp delete-binding command to remove the DHCP binding and the dynamic subscriber interfaces, the DHCP client does not detect the binding removal and retains the lease.

> - If you perform a unified ISSU procedure with 11,000 L2TP subscriber sessions connected across two pairs of line modules enabled for stateful switchover, and more clients attempt to connect in such a scenario, the unified ISSU process fails and the chassis undergoes a cold restart. [Defect ID 188079]

> #### System

> - Beginning with JunosE Release 11.0.0, the FPGA upgrade feature has been enhanced to reduce the booting time of the system. The FPGA upgrade operation takes place only if a system requirement, such as a cyclic redundancy check (CRC) mismatch, occurs. On E120 and E320 routers, if you upgrade the system from a release that supports the enhanced FPGA upgrade (such as 11.0.3), downgrade the system to a release numbered lower than 11.0.0 that does not contain the enhanced the FPGA upgrade mechanism (for example, 9.0.1p0-7-5-2 or 10.2.1p0-2), and then upgrade the router again to a release that supports the enhanced FPGA upgrade mechanism, the SRP-100 or SRP-320 modules might not upgrade the FPGA correctly. [Defect ID 190012]

> In JunosE Release 12.2.0, the SRP module that has an FPGA revision number that is different from 0xbd26 denotes this problem. This error can occur with both unified ISSU or cold upgrade operations. However, this condition does not occur when the SRP module is reset after being powered off and turned on, or when the SRP module is unplugged and reinserted into the same slot.

> - You cannot use a configuration script to boot the E320 router. [Defect ID 80304]
> - A single space is present between the string "lag" and the name of the LAG bundle in the COPS handler messages that are sent. This behavior causes the policy manager to not service video-on-demand (VOD) requests properly. [Defect ID 189872]
> - If you hot swap an IOA and then remove it again before that IOA's OK or FAIL LED is illuminated, the associated line module can reset. [Defect ID 177313/177267]

> Work-around: Ensure that you firmly insert the IOA into the chassis when you hot swap IOAs. Do not attempt a second hot swap of an IOA that has not indicated that it completed the first hot swap cycle. You can remove the IOA when either its OK or FAIL LED is illuminated.

> - Memory leak is observed with the SRP-100 module while subscribers are being brought up on a LAC device and the active link between the LAC device and the LNS device in an L2TP tunnel is flapping. This problem occurs when the following steps are performed: [Defect ID 189353]
> 1. Two redundant links connect the LAC device to the LNS device in the L2TP tunnel.
> 2. DHCPv6 subscribers over PPPoE interfaces connected to a LAC device are attempted to be brought up.
> 3. The active link between the LAC and LNS devices flaps continuously 1000 times using the shutdown and no shutdown commands.
> 4. Memory-related output information is collected at a base condition where the active link is up again and no subscriber is connected to the router.

> When you perform each iteration of the preceding four steps, the amount of free memory on the SRP-100 module decreases and validates a memory leak.

> - If your router is in Manual Commit mode, then you must issue the write memory command before you perform an SRP module switch or a manual reload. You must do this even when you have made no changes to the system configuration and the file systems are synchronized. [Defect ID 44469]

> #### TCP

> - The SRP module resets in any of the following circumstances on an E320 router that has a line module configured with 5000 ANCP adjacencies: [Defect ID 176916]
> - When you issue the issu initialization command from the console and then reload the line module from a Telnet session.
> - When the client that has the 5000 ANCP clients resets or an intermediate switch resets.
> - When you reload the line module.

> #### Unified ISSU

> - Unified ISSU is not supported with 8000 bridged Ethernet interfaces on an OC3/STM1 GE/FE ATM line module. [Defect ID 178811/178797/
>   179547]
> - ATM line modules might reset after a unified ISSU when you attempt to add memory to a VLAN subinterface in a large bridged Ethernet configuration. [Defect ID 178798]
> - Under certain conditions, a unified ISSU from JunosE Release 9.2.0p1-0 to the current release fails, and causes the SRP module and the ES2 4G LM to reset. [Defect ID 179975]
> - During the unified ISSU operation, if you modify the router configuration after the initialization phase of the process is completed and before you issue the issu start command to commence the upgrade phase of the unified ISSU process, the unified ISSU procedure completes successfully and the stateful SRP switchover process begins to synchronize between the active and standby SRP modules. When the synchronization process is in progress, the standby SRP module reloads for the second time. After the second reload of the standby SRP module ends, the synchronization process also ends properly.

> Although the standby SRP module reloads for the second time when it is synchronized with the upgraded release, normal router operations, such as handling of subscriber sessions and forwarding of traffic, remain unaffected. [Defect ID 185517]

> - When any of the subsystems is excluded for a JunosE release, a unified ISSU to that release fails to apply conversion code to all of the line modules. As a result, the line modules reset when they come up with that release. [Defect ID 179595]

> Work-around: To prevent the exclusion of a subsystem file from the release, do the following before you upgrade to a new JunosE release that supports unified ISSU:

> 1. Issue the show subsystems file fileName.rel command, where fileName is the name of the software release file, to determine whether any of the subsystem files are excluded from the release.
> 2. For each subsystem file that is excluded, issue the no exclude-subsystem subsystemName command to remove the exclusion for the specified subsystem file.

> If you copied the software release to the router before removing the subsystem file from the exclusion list, you must copy the release to the router again to ensure that all subsystem files are included in the release.

> - When you perform a unified ISSU operation after link flaps in a network from JunosE Release 10.3.3 to Release 11.2.x on a router that contains ES2 4G LMs and is configured with MPLS applications (L3VPNs, L2VPNs, and VPLS), all the ES2 4G LMs reset after the upgrade is completed. [Defect ID 189178]

Copyright © 2011, Juniper Networks, Inc. Report An Error