Previous Releases

8.5R3

The following issues have been resolved since JUNOS Release 8.5R3. The identifier following the description is the tracking number in our bug database.

Software Installation

• When you issue the request system partition hard-disk command, the hard disk repartition fails and the disk becomes unusable. The disk can be recovered by taking a snapshot from the compact flash card and rebooting the router. [PR/269493: This issue has been resolved.]

Platform and Infrastructure

• If TCP and UDP probe servers (configured at the [edit services rpm] hierarchy level) are configured on a router and a TCP and a UDP probe is made to it simultaneously from some other router, multiple occurrences of the RMOPD_SENDMSG_FAILURE message are generated and recorded in the system log. [PR/66570: This issue has been resolved.]
• During a Routing Engine switch over, the Flexible PIC Concentrator (FPC) might reset multiple times. [PR/70857: This issue has been resolved.]
• ARP records learned in a VPN routing and forwarding (VRF) instance are not cleared when the peer interface goes down. [PR/82247: This issue has been resolved.]
• If a small form-factor pluggable transceiver (SFP) does not respond to a request for diagnostic data, a message is written to the system log. The message is unnecessary because the failure to respond has no operational impact. [PR/97718: This issue has been resolved.]
• On T-series platforms, if you include the indirect-next-hop statement at the [edit routing-options forwarding-table] hierarchy level for VPN routes, routing ASIC SRAM utilization increases by approximately 30 percent or 8 bytes per route. [PR/98738: This issue has been resolved.]
• Due to changes in the JUNOS TCP/IP networking stack, the output of the show connections CLI command may be different from JUNOS 8.4 and earlier. [PR/103330: This issue has been resolved.]
• PFE might incorrectly log an error (described in the PR). This might happen when there is some sort of aggregate member link status change. [PR/105841: This issue has been resolved.]
• When IPSec is configured on a logical interface and the protocol family is IPv6, graceful Routing Engine switchover (GRES) might fail if an MTU change is attempted on that interface. [PR/230128: This issue has been resolved.]
• J-Series multilink interfaces operate correctly when fragments are in round-robin fashion and arrive in order. However, if the fragments are out of order, then they suffer some latency and packet-loss during reassembly. [PR/240019: This issue has been resolved.]
• When the management interface (fxp0) initialization does not complete, the interface loses network connectivity and does not respond to any commands within the timeout period of 10 milliseconds. [PR/253479: This issue has been resolved.]
• On some Routing Engines, the smartd process may display the following error: “atastandbyarmset”. [PR/253775: This issue has been resolved.]
• Using the "-ox" option with the smartd process is not recommended on mounted devices because it may result in unexpected behavior. [PR/255473: This issue has been resolved.]
• When an address rename operation is performed on Gigabit Ethernet interfaces, filters are removed and then added back. The operation can sometimes be replicated to the backup Routing Engine as a single change. In this scenario, the backup Routing Engine attempts to delete the filter and add it back using the index specified by the master Routing Engine. However, the entry is not deleted, leading to a mismatch in the index usage between the master and slave Routing Engines, which causes the Routing Engine to produce a core file and stop operating. [PR/258927: This issue has been resolved.]
• The UDP ping server does not respond to probes sent through a routing instance other than the default (inet.0). [PR/260097: This issue has been resolved.]
• A multicast enabled router, configured with aggregated Ethernet, or aggregated SONET, interfaces could experience a kernel crash, when the constituent, or aggregate interfaces go down. [PR/264579: This issue has been resolved.]
• When you change interface configuration from point-to-point encapsulation to Frame Relay encapsulation, the routing platform kernel might generate a core file and stop operating. [PR/265025: This issue has been resolved.]
• When IPv6 traffic is present on MLPPP bundles using MultiServices PIC, the Service PIC may core due to excessive logging as a result of invalid checksum calculation. [PR/266214: This issue has been resolved.]
• If there are many aggregate next hops and BGP routes pointing at some of them, a quick link flap combined with the BGP route churn might cause the Packet Forwarding Engine to restart unexpectedly. [PR/268204: This issue has been resolved.]
• With certain traffic patterns, MX-series and M320 routers with 3.0 forwarding ASICs might experience packet loss. To recover, you must reboot the affected DPC. [PR/268274: This issue has been resolved.]
• When FPC is brought online immediately after being taken offline, it may not be properly initialized due to a race condition in timing between the FPC and Routing Engine. [PR/272086: This issue has been resolved.]
• In JUNOS software Release 8.5R1 only, if the router receives an MPLS LSP ping packet, it may cause a kernel memory leak in the network packet buffer and upon exhaustion no packet transfer is possible between the Routing Engine and the Packet Forwarding Engine (PFE). There is no workaround. [PR/273024: This issue has been resolved.]
• Using the set forwarding-options sampling output file filename sampled.pkts, the sampled.pkts file (which should be created in /var/tmp in the router) is not being created. If restart sampling is called, the file gets created. This is because the j-flow license database is not working properly when sampling is configured. A workaround for this issue is to issue the show system license usage command. The license database is then updated and the file is created. [PR/275473: This issue has been resolved.]
• When both BPG multipath and indirect-next-hop are turned on, the next hop referenced by the prefixes for BGP multipath will not be installed in the routing chip, resulting in packet drop. [PR/275586: This issue has been resolved.]
• A large virtual memory size (> 700 MB) is reported for daemons that access the JUNOS configuration database in the output of the show system processes extensive command. The reason for the increase in virtual memory size is because 700 MB of the virtual space is pre-reserved for the JUNOS configuration database. This reserved space is just a placeholder in the daemon's virtual address space. Customers do not need to be concerned by this increase in virtual memory size because the actual amount of physical memory consumed by the configuration database is not affected. [PR/276378: This issue has been resolved.]
• In scenarios where the PFEs are restarted quite frequently, the PFE might crash. Two causes have been identified. One is a race condition with the PIC state, and the other has to do with duplicate family add messages. [PR/276539: This issue has been resolved.]
• When packets are queued for several seconds due to interface congestion, in some cases, packet CRC errors are reported. In other cases, the egress interface stops forwarding traffic (either all traffic is halted or only packets larger than 320 bytes are not forwarded). As a workaround, configure queues with a transmit rate of at least one percent of the line rate. When using strict, high-priority queues, include policers to prevent interface congestion and the starving of lower-priority queues. Another alternative is to use priority, high instead of strict, high queues. [PR/277853: This issue has been resolved.]
• Once protocol tracing is enabled, IO writes to the hard drives might get blocked and daemons sending packets will get behind. This applies only to JUNOS software Release 8.5R2 or higher. [PR/278580: This issue has been resolved.]

User Interface and Configuration

• TACACS+ accounting start/stop requests are incompatible with Cisco ACS. The fix is to add the no-cmd-attribute-value statement at the [edit system tacplus-options] hierarchy level. When this is enabled, the JUNOS software sets the value of the cmd attribute in TACACS+ accounting start and stop requests to a null string. This is the behavior Cisco ACS expects in order to save accounting requests to the Accounting file; otherwise, the requests are saved to the Administration file. [PR/252472: This issue has been resolved.]
• Changing any unrelated configuration causes the apply-groups statement under routing instances to trigger an RPD reinitialization during commit even when the change didn't match any attributes in the group. Also, rollback performs the equivalent of load override instead of load update. This causes the routing protocol process to be reinitialized during commit. [PR/259740: This issue has been resolved.]
• On upgrading to 8.5R1.13, the MOTD might be displayed twice. [PR/268625: This issue has been resolved.]
• If you issue the copy command in edit mode for configurations under the [edit groups] hierarchy, the mgd process exits and dump core. [PR/269034: This issue has been resolved.]
• Commands such as rollback <#> or show | compare rollback <#> take several minutes to complete if the configuration has a policy statement with a term that contains a large number of route-filter entries (in the order of thousands). [PR/272350: This issue has been resolved.]
• The system syslog source-address change does not take effect. As a workaround, you can restart the eventd process (or reboot the Routing Engine). [PR/272434: This issue has been resolved.]
• JUNOS devices cannot be managed by Session and Resource Control (SRC) software. [PR/273117: This issue has been resolved.]
• When you use the configure private command and then change two static routes at the same time at the [routing-options static] hierarchy level, the commit may fail. As a workaround, configure one static route at a time. [PR/273251: This issue has been resolved.]
• Issuing the replace pattern command may terminate the telnet session with mgd core due to a function not being invoked correctly. [PR/274830: This issue has been resolved.]
• A user without maintenance permission cannot su to a non-root user from the shell. [PR/277888: This issue has been resolved.]
• Login class permissions might not work properly for JUNOS software Releases 8.4R1 and higher. [PR/278950: This issue has been resolved.]

Interfaces and Chassis

• On M20 routers, when you start the router with Routing Engine 0 and System and Switch Board (SSB) 0 as master components, issue the request chassis routing-engine master switch command, and then log in to Routing Engine 1 and issue the request chassis ssb master switch and request system reboot commands, the “ONLINE” LED might remain lit on both SSBs. [PR/74283: This issue has been resolved.]
• When you configure point-to-multipoint Frame Relay, the router might generate a core file. [PR/82303: This issue has been resolved.]
• The show vrrp commands which were earlier available only from the top level, has been made available from an LR context as well. [PR/253956: This issue has been resolved.]
• When you issue the request chassis routing-engine master switch command to change Routing Engine mastership, the jnxRedundancySwitchover SNMP trap is not generated. (However, the event is recorded in the system log or chassis process log file if logging is appropriately configured.) [PR/254637: This issue has been resolved.]
• Configuring an interface IPv6 address as preferred or primary will generate a log message similar to the following: "DCD_CONFIG_WRITE_FAILED: Interface 'interface-name' configuration write failed for an IFA CHANGE: Operation not supported". [PR/258531: This issue has been resolved.]
• When you have IPv6 enabled, the IPv6 input transit counter might not work correctly. [PR/260704: This issue has been resolved.]
• Small correction in printing the "expected" value in VRRPD_VIP_COUNT_MISMATCH message for an IPv6 address. [PR/261415: This issue has been resolved.]
• When the committed DLCIs are in the process of coming up, if there are any configuration changes on that specific interface, the DLCIs that are down (or have not yet come up) at that time, will not come up until that IFD is reset (offline and online) or until the logical interfaces are deactivated and activated. If any configuration change is made to the Frame Relay interface when the existing DLCIs that are down, they will not come up until that IFD is reset (offline and online) or until the logical interfaces are deactivated and activated. [PR/261501: This issue has been resolved.]
• When telnet/ssh sessions are negotiated on the router, if enough packets are lost to cause TCP SACK (Selective ACK) to be exercised, SACK errors appear in the logs and might cause the FPCs to disconnect from the Routing Engine. [PR/265957: This issue has been resolved.]
• Input statistics for aggregated Ethernet interfaces incorrectly report zero, regardless of input traffic volume. [PR/266271: This issue has been resolved.]
• The chassis LED status returned by the MIB jnxLEDState does not reflect the actual chassis alarm LED. [PR/266326: This issue has been resolved.]
• SFPCs caused the warning message "WARNING: Unknown FPC 0x1f4" when checking PIC compatibility. [PR/266854: This issue has been resolved.]
• When there is an Address Resolution Protocol (ARP) entry for Virtual IP (VIP), the Virtual Router Redundancy Protocol (VRRP) might not respond to ARP requests for VIP while transitioning to master state. [PR/268627: This issue has been resolved.]
• An error in the chassis process (chassisd) caused a small memory leak when the show chassis hardware extensive command was executed. [PR/268925: This issue has been resolved.]
• On an MX platform, when there is a lot of traffic going to the Routing Engine and the route changes, the Dense Port Concentrator (DPC) might trigger an assertion without dumping core. [PR/269699: This issue has been resolved.]
• When Routing Engine mastership is repeatedly switched, routing information maintained on the master and backup Routing Engine might be out of sync, causing all Packet Forwarding Engines to reset. [PR/271141: This issue has been resolved.]
• When you configure multiple interfaces with vlan-id-range and cover a large number of VLAN IDs, the DPC might restart unexpectedly. [PR/271456: This issue has been resolved.]
• Clocking configuration under so-x/y/z level may conflict with clocking under coc-x/y/z level. Customer should only configure clocking under coc-x/y/z. [PR/272920: This issue has been resolved.]
• For RLSQ multilink feature with GRES, any addition deletion of the member T1/E1 links after GRES switchover will not operate correctly. The work around is to deactivate/activate the entire RLSQ bundle when links are deleted/added after a GRES switchover. [PR/273528: This issue has been resolved.]
• When a shape-rate is configured to a logical interface on IQ2 Ethernet PICs, it may not be applied, and traffic exceeding the preconfigured rate may still go through. [PR/273831: This issue has been resolved.]
• On Ethernet IQ2 PICs, if you change the configuration at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level from forwarding-class to classifiers, the behavior aggregate (BA) classification table mapping might be incorrect. As a workaround, deactivate the virtual circuit and then reactivate it. [PR/275693: This issue has been resolved.]
• On M320 Enhanced 3 FPC, when next term is used in firewall filter term, the firewall filter may block all traffic on interface where the filter is applied. [PR/278325: This issue has been resolved.]
• In VPLS instance on MX series routers, if an interface is configured as nontagged, vlan-maps will not process frames with dual tags. [PR/279669: This issue has been resolved.]

Services Applications

• If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on AS PICs might not be assigned correctly. In some cases, this situation causes the AS PIC to stop functioning. [PR/95019: This issue has been resolved.]
• Flow monitoring version 9 MPLS and MPLS-IPv4 templates do not work on the TX matrix routing platform or on dual Routing Engine routing platforms configured with graceful switchover. When you configure flow monitoring version 9 on a TX matrix routing platform, LCCs will crash. When you configure flow monitoring version 9 on a router configured for graceful switchover, issuing the commit synchronize command will cause the backup Routing Engine to crash. [PR/98372: This issue has been resolved.]
• If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on AS PICs might not be assigned correctly. In some cases, this situation causes the AS PIC to stop functioning. [PR/229287: This issue has been resolved.]

General Routing

• Community expression can be mistakenly interpreted as an extended community instead of a regular community regex. [PR/251510: This issue has been resolved.]

Routing Protocols

• When determining which BGP route to prefer, the JUNOS software does not compare route characteristics in the order specified by RFC 4456, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)." [PR/70687: This issue has been resolved.]
• When two redundant PE routers send multicast traffic towards their MVPN backbone, the JUNOS software might not perform the actions necessary to prevent traffic duplication. [PR/72447: This issue has been resolved.]
• The RPD process may core after upgrading to 7.6R2.6 when upgraded from 7.3R2.9. There is no workaround as of now to avoid the problem. [PR/77495: This issue has been resolved.]
• When a new receiver joins the tree between the source and RP for which there is already a receiver for the same group upstream to the RP, there might be delay for the traffic to be received by the new receiver until the next Register message is received. [PR/228708: This issue has been resolved.]
• When a new PIM neighbor is discovered on an IPv6 network, the appropriate system log message was not filed. [PR/230342: This issue has been resolved.]
• When PIM receives an (*,G) leave and an (S,G) join for an (S,G) entry that has been pruned and when the neighbor entry is deleted, the JP state for the (S,G) join is not deleted, resulting in PIM going in to an infinite loop. [PR/235978: This issue has been resolved.]
• The show bgp summary command output changed to show BGP IPv6 neighbors in sorted order, based on the IPv6 address. [PR/237127: This issue has been resolved.]
• In rare cases, the routing protocol process (rpd) may have an iflist that is different from the kernel's. A subsequent route add may try to use the nhindex of this iflist. The kernel returns an error and the route sits in krt's queue forever. [PR/252489: This issue has been resolved.]
• When you deactivate a large number of routing instances (about 335 or more), LDP sessions might go down and the following message might be written to the system log: "RPD_PPM_WRITE_ERROR: ppm_send: write error on pipe to ppmd (Broken pipe)." [PR/260477: This issue has been resolved.]
• If you issue the show route extensive command while the routing protocol process (rpd) is resolving BGP routes, the process might generate a core file and restart. [PR/260527: This issue has been resolved.]
• ARP entries created by DHCP relay are not programmed as permanent. Therefore, any other ARP request from different users on the same Ethernet segment can overwrite this entry at any time. [PR/264332: This issue has been resolved.]
• For VPLS, when the router-disinguisher is changed on an existing instance, the RPD may be running at high CPU utilization and not responding to the CLI. [PR/270204: This issue has been resolved.]
• The redistribution of OSPF point-to-point (P2P) LAN interfaces from within a routing instance in to the main routing instance can fail, displaying the following log message: “Jan 23 15:24:50 router rpd[6063]: cannot perform nh operation ADDANDGET nhop 0.0.0.0 type unicast index 0 errno 45.” As a workaround, redistribute the interfaces routes within the routing instance in to the main routing instance. [PR/271130: This issue has been resolved.]
• The routing process can restart unexpectedly if it receives a BGP flow NRLI specification with an undefined subcomponent type. [PR/274421: This issue has been resolved.]
• MSDP is reporting that an SA is active when the entry no longer exists. This is why the entry lingers in PIM once it has been deleted in MSDP. [PR/277310: This issue has been resolved.]
• AS path recorded information was being shown at the wrong place. [PR/281023: This issue has been resolved.]
• With a minimum of two PIM ASM routers and receivers on a LAN segment, if interface MISMATCH errors occur, then an s,g entry will not be created. This is applicable for both native PIM configurations as well as multicast VPN configurations. [PR/281662: This issue has been resolved.]

MPLS Applications

• On M series and T series routers, the output of the monitor label-switched-path lsp-name command might show incorrect LSP statistics when the both the secondary and primary path of an LSP are UP and traffic is being forwarded on the secondary path. [PR/80591: This issue has been resolved.]
• The jinstall ugrade error message "task_get_port: getservbyname("ldp", "tcp") failed, using port 646" is a minor warning which can be ignored. However a fix has been checked in for this issue. [PR/102209: This issue has been resolved.]
• A router with a point-to-multipoint transmit-switch connection configured might stop functioning if the transmit label-switched path of the connection flaps. [PR/229175: This issue has been resolved.]
• MVPN P2MP deactivating of the VT interface in a particular VPN, say VPN-A on receiver PE, affects multicast traffic forwarding in other VPNs for a few seconds. Same issue is seen during the activate sequence of the VT interface in VPN-A. [PR/252697: This issue has been resolved.]
• The order of addresses returned as the ERO for an LSP by the SNMP mplsPathExplicitRoute object is reversed from the correct order displayed as the Computed ERO in the output of the show mpls lsp extensive command. [PR/263462: This issue has been resolved.]
• When graceful restart is enabled (by the graceful-restart statement at the [edit routing-options] hierarchy level) and an interface is configured as an egress interface in a CCC switch for a point-to-multipoint LSP (the output-interface statement is included at the [edit protocols connection p2mp-receive-switch] hierarchy level), if the LSP flaps repeatedly, the interface might stop forwarding traffic. [PR/264930: This issue has been resolved.]
• The system can leak next-hop resources when RSVP link protection is enabled. [PR/265295: This issue has been resolved.]
• On M series and T series routers, when an MPLS LSP gets optimized, the MPLS MIB counters associated with the path change event are not updated. [PR/265931: This issue has been resolved.]

VPNs

• When configuring multicast VPN for point to multipoint, the tunnel-limit statement for dynamic selective provider tunnels is not functioning. [PR/250701: This issue has been resolved.]
• A receiver directly attached over an Ethernet connection to a sender PE configured with multicast VPN over point to multipoint fails to receive multicast traffic. No such issue is observed when the receiver is connected over a Sonet or ATM link. [PR/252314: This issue has been resolved.]
• The VT tunnel interface is not recreated upon reboot of Tunnel PIC or FPC reboot holding the Tunnel PIC. As a workaround, deactivate and activate the VT tunnel interface stanza in the interface configuration. [PR/266170: This issue has been resolved.]

Class of Service

• When you configure the EXP classifiers to a routing instance, the class-of-service (CoS) process (cosd) might dump core. [PR/101490: This issue has been resolved.]
• Configuring huge-buffer-temporal in CoS may cause commit to fail when using configure private [PR/265762: This issue has been resolved.]
• If a rewrite rule is not defined at the [edit class-of-service rewrite-rules] hierarchy level for every forwarding class defined at the [edit class-of-service forwarding-classes] hierarchy level, when the class-of-service process restarts (for example, when there is a graceful Routing Engine switchover), the process does not initialize internal data structures correctly. As a workaround, define a rewrite rule for every forwarding class. [PR/268541: This issue has been resolved.]
• On MX960 routers, the class-of-service process does not provide information about SNMP objects whose names begin with "jnxCosQstat." As a result, SNMP queries on those objects fail with an error message. [PR/269419: This issue has been resolved.]
• On Type 4 FPC or T1600 platforms if you change the exp rewrite rules it may trigger an overflow of the L2 programs which will result in incorrect programmed next hop entries and traffic is not forwarded. You need reboot the FPC to recover. [PR/279625: This issue has been resolved.]

Forwarding and Sampling

• On M120 and MX-series routers, if you configure both a firewall filter and interface sampling for ingress traffic on the same interface (by including both the filter and sampling statements at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level), the interface discards all incoming packets. As a workaround, implement input sampling as an action in the then section of a firewall filter. [PR/103206: This issue has been resolved.]
• The implicit DHCP firewall filter is removed from all interfaces once other configuration changes are performed at the firewall or interface level. [PR/261009: This issue has been resolved.]
• Firewall filters that include the source-address statement at the [edit firewall filter filter-name term term-name from] hierarchy level might not process traffic correctly. As a workaround, reorder the terms in the filter. [PR/262491: This issue has been resolved.]
• If you deactivate the nonstop-bridging statement at the [edit protocols layer2-control] hierarchy level and then a graceful Routing Engine mastership switchover occurs, the bridge ID for a routing instance might be reset to all zeros and the port state for some component interfaces in the routing instance might change to "Blocking." Both conditions are reported by the show spanning-tree bridge routing-instance detail command. [PR/264982: This issue has been resolved.]
• If a term in firewall filter specifies a range of values for source or destination address or port, the filter might not match packets as expected. As a workaround, define the addresses and ports explicitly. [PR/265023: This issue has been resolved.]
• When a firewall policer with loss-priority action is used under multiple interfaces, only the first instance of the interface policer will have the right PLP setting behavior. [PR/274346: This issue has been resolved.]
• At the [edit routing-options flow route route-name] hierarchy level, when a range of numeric values is selected for firewall filtering using a statement, the match condition is ignored. Such statements typically include destination-port, port, protocol, and source-port. [PR/275650: This issue has been resolved.]

8.5R2

The following issues have been resolved since JUNOS Release 8.5R2. The identifier following the description is the tracking number in our bug database.

Platform and Infrastructure

• The MultiServices PIC might not work correctly when the PIC is loaded and frequent commands related to the PIC are issued. [PR/81826: This issue has been resolved.]
• When IPSec is configured on a logical interface and the protocol family is IPv6, graceful Routing Engine switchover (GRES) might fail if an MTU change is attempted on that interface. [PR/230128: This issue has been resolved.]
• J-series multilink interfaces behave well when fragments are in round-robin fashion and arrive in order. However, if fragments are out of order, then they will suffer some latency and packet loss during reassembly. [PR/240019: This issue has been resolved.]
• When using file copy FTP, the IP address specified is the source address is not used for establishing a connection with the peer FTP server. [PR/240580: This issue has been resolved.]
• When graceful switchover and RLSQ interfaces are configured, the kernel generates a core file on the backup Routing Engine with the error message "panicstr: rnh_index_alloc: nhindex 116435 could not be allocated." [PR/241502: This issue has been resolved.]
• When an unnumbered Ethernet interface has a loopback address as a donor and if the address configured on the loopback is a subnet address, a ping to the subnet address does not work. [PR/253804: This issue has been resolved.]
• In some situations, the interface counter account doubles the number of packets. [PR/253946: This issue has been resolved.]
• The clear arp command does not function for logical routers. [PR/253957: This issue has been resolved.]
• The show arp command does not function for logical routers. [PR/253958: This issue has been resolved.]
• A router running multicast over aggregate SONET or aggregate Ethernet interfaces could experience a Packet Forwarding Engine crash when a constituent link flaps. [PR/257691: This issue has been resolved.]

User Interface and Configuration

• If you use telnet to connect to the JUNOScript Perl module, the connection fails if the password or login name includes special characters. [PR/241236: This issue has been resolved.]
• Certain JUNOScope wizards (devices, groups, users, schedules, and RADIUS configuration ) do not work with Netscape 7.0. The workaround is to use Netscape 6.2 [PR/260326: This issue has been resolved.]

Interfaces and Chassis

• If a low-speed bundle is congested, the jitter for link fragmentation and interleaving (LFI) traffic is high even though fragmentation is configured for Multilink Point-to-Point Protocol traffic. [PR/77862: This issue has been resolved.]
• If you clear IPv6 statistics, deactivate IPv6 route accounting at the [edit forwarding-options family inet6 route-accounting] hierarchy level, and resume IPv6 traffic across an interface, the "Input bytes" and "Input packets" fields in the output of the show interfaces extensive command might display incorrect values. [PR/99461: This issue has been resolved.]
• On the M120 and MX-series platforms and the M320 Enhanced III FPCs only, forwarding IPv6 transit packets might stop transmitting traffic but still be able to receive traffic. All packets going out this interface will be dropped. To recover, you need to reboot the FPC on M320 platforms, the DPC on the MX-series, or the FEB on M120 platform. There is no workaround. [PR/105266: This issue has been resolved.]
• For Gigabit Ethernet interfaces on J-series Services Routers, the link-mode and speedstatements at the [edit interfaces ge-fpc/pic/port] hierarchy level are mutually dependent; that is, if you include one, you must include the other. If you do not, the interface process generates a warning and uses autonegotiated values. For Gigabit Ethernet interfaces on other routing platform types, the speedstatement is not available, so including the link-mode statement alone is valid. Nevertheless, the interface process writes the following message to its log and the system log: "Speed and linkmode duplex settings are mutually required." (Note further that the ink-mode statement is actually nonoperational on non-J-series routing platforms, because the only valid value for it is the default,'full-duplex'.) [PR/228857: This issue has been resolved.]
• The "accept data" warning message for VRRP might not correctly display the logical unit identifier. [PR/236135: This issue has been resolved.]
• When a PIC detachment process takes a long time for an IQ2 PIC (for example, when a large number of route updates are triggered after an IQ2 PIC is brought offline), the PIC chassis process (pic-chassisd) connection might not be closed properly. [PR/239944: This issue has been resolved.]
• On the J4350 and J6350 Services Routers, the show chassis interfaces extensive command does not display "Carrier Transitions" and certain other statistics properly. [PR/241086: This issue has been resolved.]
• Padded MPLS-encapsulated IPv4 packets that exit an LSP can cause the egress interface to stop forwarding packets. This can happen when the router is configured as a VPN PE, or when the router is the penultimate node of an LSP. The problem only occurs when the packet has been padded to meet the minimum Layer 2 frame size (for example, Ethernet media require frames to be a minimum of 64 bytes long). This issue is applies to the M120 and MX-series platforms and to the M320 Enhanced III FPCs. To recover, reboot the FPC on the M320, the DPC on the MX-series, or the FEB on M120 routing platforms. [PR/251042: This issue has been resolved.]
• The ATM PIC driver might not always use the minimum port shaping rate (of all the ports on a multiport ATM DS3 or E3 PIC) selected for cell transmission shaping, in situations where the DS3 or E3 port parameters are not identical on all ports of a multiport ATM DS3 or E3 PIC. The PIC shaping rate is always updated to conform to the last port setting updated by the PIC software driver, rather than using the minimum port (shaping) rate. There is no syslog message to inform the user of the shaping rate decision applied by the software driver. [PR/252837: This issue has been resolved.]
• On the J-series Services Routers, on 4-port Fast Ethernet Enhanced Physical Interface Modules (ePIMs), interfaces might stop working correctly and lock up a port when operating in half-duplex mode. As a workaround, hard code the link-speed and link-mode to 100m full duplex. [PR/253329: This issue has been resolved.]
• When you configure a logical interface with encapsulation ether-vpls-over-atm-llc, the packets destined for to the Routing Engine are dropped by the Packet Forwarding Engine. [PR/255713: This issue has been resolved.]
• When a Routing Engine assumes mastership, it attempts to reconnect to the Packet Forwarding Engine. The Packet Forwarding Engine sends all the information to the master Routing Engine. The new master Routing Engine then attempts to retrieve SFP information from the PIC, but the PIC fails to send it. [PR/256032: This issue has been resolved.]
• On a M40e router with 4 MS00 PICs and 4 ChOC12, the SONET interface might display remote defect indication (RDI) or alarm indication signal (AIS) alarms when the router is rebooted. [PR/257419: This issue has been resolved.]
• When both PIM and OSPF are configured on an IQ2 PIC, OSPF may lose adjacency if protocol PIM is removed. [PR/257848: This issue has been resolved.]
• After a graceful Routing Engine switchover on the M10i router, alarms might not resynchronize to the new primary Routing Engine. [PR/258034: This problem is resolved.] [PR/258034: This issue has been resolved.]
• On an MX-series router with a 4-port Gigabit Ethernet DPC, when you configure asynchronous notification, it does not function properly. [PR/259304: This issue has been resolved.]
• On the J2320 and J2350 series Services Routers, Gigabit Ethernet interfaces sometimes stop transmitting the packets if Transmit Descriptors are not updated with TransmitDone status properly. To work around this issue, restart pic 0. [PR/261010: This problem is resolved.]

Services Applications

• When you configure twice NAT with static source and static destination translation, the destination port for ICMP flows might change (the ports are supposed to remain unchanged). [PR/96701: This issue has been resolved.]
• If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on AS PICs might not be assigned correctly. In some cases, this situation causes the AS PIC to stop functioning. [PR/229287: This issue has been resolved.]
• On the MultiServices 400 PIC, a memory warning flag might be set even with low traffic rates. [PR/251908: This issue has been resolved.]
• The show services pgcp active-configuration command does not display byte units for the "MG maximum PDU size" and "MGC maximum PDU size" output fields. [PR/256801: This issue has been resolved.]

Routing Protocols

• Trace pointers for some BGP tasks were not updated on reconfiguration. [PR/69321: This issue has been resolved.]
• The show pim source does not display the correct information for both direct and non-direct sources. [PR/253629: This issue has been resolved.]
• PIM anycasts do not working when the source is connected to the Rendezvous Point router. [PR/256637: This issue has been resolved.]
• Route target filtering breaks when the last community received is withdrawn, because the route-filtering logic is being bypassed. Absence of any route target received from the peer is being treated as if 0/0 default was received from the peer. [PR/257011: This issue has been resolved.]
• The show multicast snooping route bridge-domain name source-prefix prefix/length command causes the multicast snooping process (mcsnoopd) to stop functioning. The workaround is not to use the source-prefix option. [PR/257788: This issue has been resolved.]
• The routing processes can generate nonfatal coredumps. [PR/258134: This issue has been resolved.]
• Deconfiguration of a routing instance on a router configured with uRPF may cause the routing process to restart. [PR/259727: This issue has been resolved.]

MPLS Applications

• A router configured with a point-to-multipoint transmit-switch connection might stop functioning if the transmit label-switched path of the connection flaps. [PR/229175: This issue has been resolved.]
• You might encounter an interoperability issue when Cisco IOS-XR or IOS includes the node-id sub-object as part of the RRO in Reseveration messages. The JUNOS software is unable to find the next-next-hop router's interface address to signal a node-protecting bypass LSP. [PR/237491: This issue has been resolved.]
• MVPN P2MP deactivating of a vt interface in a particular VPN, say VPN-A on receiver PE, affects multicast traffic forwarding in other VPNs for a few seconds. This issue is also experienced during the activate sequence of the vt interface in VPN-A. [PR/252697: This issue has been resolved.]
• If an MPLS LSP configured with fast reroute is not advertised in to the IGP, that LSP might reuse an old unicast list and cause traffic drops. [PR/253352: This issue has been resolved.]
• If the authentication method for a LDP session is changed from using authentication-key to using authentication-key-chain or vice-versa, other unrelated LDP sessions may flap in addition to the affected LDP session flapping. [PR/258395: This issue has been resolved.]
• If there are many LSP flaps, used for the p2mp-receive-switch, and graceful restart is enabled, the interface might stop forwarding traffic. To recover, you need to deactivate and then activate the protocol connection p2mp-receive-switch configuration. As a workaround, disable graceful restart [PR/264930: This issue has been resolved.]

VPNs

• When configuring multicast VPN for point to multipoint, the tunnel-limit statement for dynamic selective provider tunnels is not functioning. [PR/250701: This issue has been resolved.]
• A receiver directly attached over an Ethernet connection to a sender PE configured with multicast VPN over point to multipoint fails to receive multicast traffic. No such issue is observed when the receiver is connected over a Sonet or ATM link. [PR/252314: This issue has been resolved.]
• When you configure the vlan-tags statement under routing instances for a VPLS or a virtual switch instance, the JUNOS software might produce commit check errors messages. The workaround is to use the vlan-tags statement in the configuration for interfaces only. [PR/256958: This issue has been resolved.]

Class of Service

• On the M320 and T-series routing platforms, when you map multiple forwarding classes to the same queue and then include the multiple of those definitions in the scheduler map, the configuration might fail. [PR/103370: This issue has been resolved.]
• The behavior aggregate (BA) classifier is not applied to a logical interface configured with the encapsulation ether-over-atm-llc statement. [PR/255742: This issue has been resolved.]
• For IQ PICs on the M-series and T-series routers and Enhancing Queueing DPCs on the MX-series routers, when you configure a scheduler map with a queue configured with priority strict-high, in certain situations such as when a PIC is bounced, the incorrect queue buffer might be calculated. [PR/256263: This issue has been resolved.]
• When a PIC goes offline and then online, the following message might display on the Packet Forwarding Engine console: “cosman_compute_mad_state: No ifd for ifd_index <ifd index value>.” The message does not indicate any effect on the operation of the rouer unless a temporal or delay buffer configuration is present on the router. [PR/257814: This issue has been resolved.]
• If you configure a traffic shaper of over 75 MB on a Gigabit Ethernet interface, its overall throughput might decrease. For Gigabit Ethernet interfaces, configure shapers with a size of less than 75 MB. [PR/257951: This issue has been resolved.]

Forwarding and Sampling

• If you configure a policer with a burst size limit larger than 67 MB, interfaces to which the policer is applied might not forward traffic. On some platforms the limit is higher, and the limit also depends on the available bandwidth. [PR/99758: This issue has been resolved.]
• Firewall filter source-address match sometimes does not function properly because of corner cases during firewall optimization. The workaround is to rearrange the term order of the filter. [PR/262491: This issue has been resolved.]

Network Management

• When you configure an SNMP client list with a logical router, clients are not restricted. [PR/254574: This issue has been resolved.]

8.4R2

The following issues have been resolved since JUNOS Release 8.4R2. The identifier following the description is the tracking number in our bug database.

Platform and Infrastructure

• Messages like the following might appear in the system log, indicating that the system clock went backward by 1 microsecond: "check_kernel_exec_time: microuptime() went backwards (seconds.microseconds –> seconds.microseconds)." There is no operational effect. [PR/77411: This issue has been resolved.]
• On M20 routers, if you take an FPC offline, extract a PIC, reinsert the PIC, and attempt to bring the FPC online, the online operation might fail, the System and Switching Board (SSB) might dump core, and the router might reboot automatically. [PR/78988: This issue has been resolved.]
• Under some circumstances, the interface process (ifd) is interfering with the operation of an LSI interface. [PR/102431: This issue has been resolved.]
• If tricolor marking is configured on an interface and the interface is repeatedly disabled and enabled, memory that has been allocated might not be released properly. [PR/232472: This issue has been resolved.]
• If there are large numbers of routes and next hops, the MultiServices PIC might not be able to allocate enough memory to install all of them in to its internal database. [PR/235368: This issue has been resolved.]
• If a routing platform uses an aggregated Ethernet interface as the only internal (IGP) facing interface and has many external peering sessions on other interfaces not traversing the aggregated Ethernet interface, when the aggregated Ethernet interface goes down and up several times, the memory buffer of the routing platform might overflow. This can cause a switchover to the backup Routing Engine (on dual Routing Engine platforms) or cause the Routing Engine to become unreachable (on single Routing Engine platforms). [PR/236258: This issue has been resolved.]
• On MX-series Ethernet Services Routers with VPLS, when a core-facing interface that is configured for integrated routing and bridging (IRB) changes to be a regular routing interface, traffic might be discarded. As a workaround, restart the chassis process (chassisd). [PR/237212: This issue has been resolved.]
• If you configure a large number of MD5 authentication keys for BGP sessions, and then deactivate and reactivate the keys, the router might generate a commit error, and MD5 authentication might not be applied on some of the BGP sessions. [PR/237690: This issue has been resolved.]

User Interface and Configuration

• If the configuration includes a commit script that uses the jcs:invoke routine, the router fails to boot successfully. [PR/95960: This issue has been resolved.]
• When you activate and deactivate VRF routing instances, the routing protocol process might generate a core file and stop operating. [PR/102088: This issue has been resolved.]
• In JUNOS Release 8.2 and later releases, user permissions are sometimes not calculated correctly. As a result, users might not be able to perform actions for which they have the required permission. [PR/229424: This issue has been resolved.]
• If the syslog host is configured and you commit a configuration change to the event process, an event policy execution causes the child event process to freeze. A subsequent commit operation to the event process causes the main event process to fail. The child event process remains active. [PR/230064: This issue has been resolved.]
• If the event process (eventd) receives corrupted data from another process, it might generate a core file. [PR/236599: This issue has been resolved.]
• If a NETCONF client sends the <commit/> tag to a router on which commit synchronize is the default commit method, the <rpc-reply> tag element generated by the NETCONF server might not be well-formed XML. [PR/241659: This issue has been resolved.]

Interfaces and Chassis

• On Channelized STM1 PICs, a tributary unit alarm indication signal (TU-AIS) alarm enabled for one channel might cause another channel to shut down. [PR/55357: This issue has been resolved.]
• On M160 and M40e routers, when you commit a configuration change, the router might generate a system log message that erroneously reports the master Packet Forwarding Engine Clock Generator (PCG) status as removed or offline. [PR/58716: This issue has been resolved.]
• When you manually disable the active Automatic Protection Switching (APS) interface to switch between the working and protect circuits, APS might not function properly. [PR/71083: This issue has been resolved.]
• With JUNOS Release 8.0 or later, some XENPAK transceivers might report spurious temperature, laser bias, laser output, and receive optical power alarms that are cleared again after about 10 seconds. There is no operational impact. [PR/98428: This issue has been resolved.]
• On J-series Services Routers, configuring more than one VRRP group on a port puts the port in to promiscuous mode. Forwarding performance can be affected, and duplicate ICMP messages might be sent in response to the ping command. This problem applies to 1-port Gigabit Ethernet ePIMs on all J-series platforms, and built-in Gigabit Ethernet interfaces on the J4350 and J6350 Services Routers. [PR/99796: This issue has been resolved.]
• When graceful Routing Engine switchover is configured and a switchover occurs, the kernel might reset and generate a core file. [PR/101359: This issue has been resolved.]
• On M320 routers, if the ingress and egress interfaces used for a TCC connection are installed in different types of FPCs (one in a standard FPC, another in an Enhanced III FPC), TCC encapsulation does not work. As a workaround, install the PICs in the same type of FPC. [PR/102997: This issue has been resolved.]
• When a switchover event occurs on a routing platform with a configuration that includes a large number of IPv6 routing instances, the Routing Engine that was previously the master might not be able to synchronize the kernel database. [PR/105268: This issue has been resolved.]
• If configuration for an interface is defined in both an internal system file and the JUNOS configuration, an internal database maintained by interface process (dcd) might include invalid pointers. When the process tries to free the pointers, it generates a core file. [PR/231145: This issue has been resolved.]
• When graceful restart is configured for routing protocols on a TX Matrix router, multicast routing might fail when a member link of an aggregated Ethernet interface is taken down. [PR/231772: This issue has been resolved.]
• On T640 and M320 routing platforms, if you configure link services IQ (LSQ) services and a link PIC to provide links to the LSQ bundles, when the FPC that houses the link PIC is taken offline, the show interfaces command might display invalid statistics for interfaces on the PIC. [PR/234521: This issue has been resolved.]
• The link fault management process might fail when you add an interface configuration to a deactivated hierarchy, and then roll back the configuration. [PR/234753: This issue has been resolved.]
• On a Channelized DS3 IQ PIC with loopback enabled for ct1 or t1 interfaces in a bundle, if you use the configuration mode copy command to create a new interface in the bundle based on one of the existing interfaces, the new interface does not come online until the PIC resets. [PR/235228: This issue has been resolved.]
• Adding or deleting a T1 member link causes one to two packets to drop on unrelated multilink PPP interfaces. [PR/236014: This issue has been resolved.]
• If you use an ATM2 Intelligent Queuing (IQ) interface as the protect circuit of an Automatic Protection Switching (APS) connection, and a graceful Routing Engine switchover (GRES) event occurs, the logical interface might be marked as hardware down rather than device down. If an APS circuit switchover happens after the GRES switchover, the ATM2 IQ interface does not clear the aps_disable flag, and traffic loss might occur on the connection. [PR/236610: This issue has been resolved.]
• When IPv6 route accounting is configured on a TX Matrix platform (the route-accounting statement is included at the [edit forwarding options family inet6] hierarchy level), the configuration is not copied to the T640 routing nodes in the matrix. As a result, the fields in the IPv6 transit statistics section of the output from the show interfaces command do not increment. [PR/237054: This issue has been resolved.]
• When a graceful Routing Engine switchover occurs and a member link of an aggregated Ethernet interface is taken offline, multicast traffic might not be rerouted through other member links as expected. [PR/237098: This issue has been resolved.]
• If you apply more than one class-of-service rewrite rule to interfaces on an IQ2 PIC, only the first rule works correctly on all interfaces. [PR/238250: This issue has been resolved.]

Services Applications

• If you perform numerous commit operations, the key management process (kmd) might generate a core file and stop operating because of an incorrect memory allocation procedure. [PR/232085: This issue has been resolved.]
• When multiple Layer 2 Tunneling Protocol (L2TP) tunnels from different tunnel groups are being set up simultaneously, the same tunnel identifier might be assigned to more than one tunnel, and some tunnel attributes might be assigned to the wrong L2TP session. As a workaround, issue the clear services l2tp tunnel command to clear the L2TP tunnels. [PR/233184: This issue has been resolved.]
• If the configuration includes certain features (for example, firewalls), service PICs do not come online if it takes the Packet Forwarding Engine more than 2␣minutes to establish communication between PICs and the Routing Engine. [PR/236926: This issue has been resolved.]
• When two or more IQ2 PICs are installed on an M7i, M10i, or M120 router, Layer␣2 Tunneling Protocol (L2TP) policer sessions are not established correctly. As a workaround, issue the request chassis pic fpc-slot slot-number pic-slot slot-number command to take all but one of the PICs offline. [PR/237356: This issue has been resolved.]

Routing Protocols

• Label aggregation is not working properly when route reflection is also configured in Layer 3 VPN networks. [PR/228039: This issue has been resolved.]
• When you use the clear bgp damping address command to remove a damped route from a routing table and specify a prefix on the address (for example, clear bgp damping 10.0.0.8/30), the route might not be removed. (Damped routes are listed as hidden in the output of the show route damping suppressed terse command.) [PR/231502: This issue has been resolved.]
• Configuring a PIM bootstrap export policy (including the export statement at the [edit protocols pim rp bootstrap family family-name] hierarchy level) has no effect. PIM bootstrap import policies work as expected. [PR/232200: This issue has been resolved.]
• If a local route is imported from another routing instance, it might not be installed in to the forwarding table. A message like the following might appear in the system log: “timestamp router rpd[PID]: KRT ADD for 10.10.10.10/32 => { ifl interface-index addr 10.10.10.10 } failed, error "ENOENT -- Item not found".” [PR/234918: This issue has been resolved.]
• The Route Distinguisher field in the output of the show route receive-protocol command reports the value configured on the local router (by the route-distinguisher statement at the [edit routing-instances routing-instance-name] hierarchy level), instead of the route-distinguisher value configured on the remote PE router. [PR/239698: This issue has been resolved.]

MPLS Applications

• If the configuration for an LSP includes more than 16 equal-cost multipaths (ECMPs), RSVP might not function correctly. [PR/228338: This issue has been resolved.]
• RSVP PATH messages are not bundled when RSVP aggregation is negotiated on a point-to-point link. [PR/234545: This issue has been resolved.]
• The mplsLspPathUp and mplsLspPathDown SNMP traps are enabled when either or both of the (syslog␣|␣no-syslog) and (trap␣|␣no-trap) statements are included at the [edit protocols mpls log-updown] hierarchy level. The correct behavior is for the traps to be enabled only when the trap-path-down and trap-path-up statements are included at the [edit protocols mpls log-updown] hierarchy level. [PR/237464: This issue has been resolved.]

VPNs

• If you configure a Layer 2 circuit across a logical tunnel interface that uses ethernet-vpls encapsulation, the Layer 2 circuit connection might not come up. As a workaround, use ethernet encapsulation on the logical tunnel interface. [PR/100161: This issue has been resolved.]
• On a provider edge (PE) router configured with multiprotocol BGP-based multicast VPNs and connected directly to a receiver, if you modify the multicast VPN import target with the import-target statement at the [edit routing-instances routing-instance-name mvpn route-target] hierarchy level, the BGP route reflector might fail to readvertise the multicast VPN routes. As a workaround, issue the clear bgp neighbor soft command on the route reflector to force it to readvertise all the multicast VPN routes without resetting the BGP sessions. [PR/104192: This issue has been resolved.]
• On MX-series Ethernet Services Routers, if the VPLS configuration includes the no-tunnel-services statement (meaning that an LSI is used instead of a virtual tunnel), customer edge (CE)-facing interfaces sometimes discard traffic. In the output from the show interfaces command, the list in the Flags field for the logical interface might include the CCC-Down or Hardware-Down flag. As a workaround, deactivate and reactivate the CE interface. [PR/234756: This issue has been resolved.]
• For MX-series routers, if you change the route distinguisher used for a VPLS routing instance, VPLS connections might not come up. As a workaround, deactivate and then reactivate the VPLS routing instance. [PR/235048: This issue has been resolved.]

Class of Service

• When the combination of interface types configured on a channelized IQ PIC requires an amount of memory that exceeds the maximum available, some of the interfaces might not handle traffic correctly. [PR/102932: This issue has been resolved.]
• Some JUNOS processes, including the class-of-service process (cosd), might not correctly release memory that they have allocated. [PR/230771: This issue has been resolved.]
• A class-of-service EXP classifier applied to a VRF routing instance does not work correctly for traffic received by a PIC housed in an Enhanced Scaling FPC (FPC4). [PR/233694: This issue has been resolved.]
• If you configure 600 T1 links and 255 Multilink Frame Relay (FRF.16) bundles on link services queuing (LSQ) interfaces in an AS PIC or MultiServices PIC, then downgrade the routing platform to JUNOS Release 8.4R1 from a later release, the downgrade might fail the validation process and generate the following error message: “Current configuration not compatible with /var/tmp/jinstall-8.4R1.13-domestic-signed.tgz”. As a workaround, deactivate the class-of-service configuration, downgrade to JUNOS Release 8.4R1, and then reactivate the class-of-service configuration. [PR/234031: This issue has been resolved.]
• Over T3 or E3 links on J-series Services Routers, traffic that is assigned strict-high priority might be discarded when large-packet high-priority traffic is sent together with small-packet low-priority traffic, and the high-priority queue's buffer size is much lower than that of the low-priority queue. As a workaround, configure a shaper with its rate set to match the line rate. [PR/234626: This issue has been resolved.]
• Deactivating and then activating an interface causes packet loss on other ports of the same PIC. [PR/238314: This issue has been resolved.]

Forwarding and Sampling

• On an M120 router, if the then statement in a firewall filter (at the [edit firewall filter filter-name term term-name] hierarchy level) includes both a policer statement and a count statement, the filter might not handle packets as specified by the configuration. [PR/105465: This issue has been resolved.]
• On MX-series or M120 routers, if you use a tunnel services-based PIC to configure multiple VPLS instances over virtual loopback tunnel (VT) interfaces, and then include the no-tunnel-services statement to direct VPLS traffic over label-switched interface (LSI) logical interfaces instead of the VT interfaces, in some cases, the VPLS traffic might stop even though the VPLS connections remain up. As a workaround, deactivate and reactivate interfaces in the affected VPLS instances. [PR/228411: This issue has been resolved.]
• If you apply the same firewall to both IPv4 and IPv6 traffic on an interface by including the input-list statement at the [edit interfaces interface-name unit logical-unit-number family inet filter] and [edit interfaces interface-name unit logical-unit-number family inet6 filter] hierarchy levels, the clear firewall filter interface-name command clears the counters for IPv4 bytes and packets but not for IPv6 bytes and packets (in the output from the show firewall filter interface-name command). [PR/229016: This issue has been resolved.]

Network Management

• Bridge domain instances are not listed in the VacmContextTable table after a Routing Engine switchover or restart of the SNMP process. [PR/233765: This issue has been resolved.]