|
|
Resolved Known Problems
Release 11.3.0 is based on Release 11.2.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 11.2.0 and have been resolved in this release, or have been resolved since the 11.2.0 release. For more information about particular resolved problems, 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.
CLI
- When you shut down a port, the value of the optical power associated with that port falls below the threshold value. When the value of the optical power falls below the threshold value, the status of the optical warning flag changes to the active state. The IOA driver polls all the optical warning flags every 20 seconds, and if an optical warning flag is active, traps and logs are generated for the respective port until the value of the optical power is restored to normal.
For instance, when two ports are connected back to back in a line module, when you shut one port, the trap is triggered on both ports as optical power falls below the threshold value on both these ports (Tx on the shut port and Rx on the remote port). Traps and logs are also generated when you:
Forwarding
IGMP
- In a router with an ES2 10G ADV LM and ES2-S2 10GE IOA combination and the line module contains a shared tunnel-server port as well as GRE tunnels configured with secure policies for mirroring traffic, multicast group memberships that had been previously established over IGMP interfaces on the router are lost after you perform a stateful SRP switchover on a chassis running JunosE Software Release 11.2.0. [Defect ID 186844]
This problem happens only when both multicast data packets and IGMP packets are transmitted on the network, regardless of whether you perform a stateful SRP switchover. This problem does not occur when only IGMP packets, without multicast data streams, are sent over the network.
In such a scenario, IGMPv2 is enabled on the interfaces using the ip igmp promiscuous command to accept IGMP reports from hosts on any subnet. Although the hosts send new join requests to the router, the router does not send group membership queries to such hosts to enable the creation of fresh memberships. Creation of new memberships fails because the router drops the received group membership reports from hosts. Any subsequent attempt from a host to join the multicast group on the router that has the ES2 10G ADV LM fails. However, after you reload the ES2 10G ADV LM, join requests from hosts succeed and such hosts become members of the multicast group.
Also, this problem of removal of group membership does not occur with the following line module combinations on E Series routers and multicast group memberships are formed properly:
Multicast
|
Copyright © 2010, Juniper Networks, Inc. Report An Error |
|
|