Port Data Rate Monitoring Cessation; Vc And Vp Statistics Monitoring Halts Unified Issu Progress; Unexpected Dhcp Behavior During Unified Issu; Dhcp Packet Capture Halted On Line Modules - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SERVICE AVAILABILITY CONFIGURATION GUIDE 2010-10-08 Configuration Manual

Port Data Rate Monitoring Cessation

VC and VP Statistics Monitoring Halts Unified ISSU Progress

Related
Documentation

Unexpected DHCP Behavior During Unified ISSU

DHCP Packet Capture Halted on Line Modules

Related
Documentation

Unexpected Denial-of-Service Protection Behavior During Unified ISSU

Copyright © 2010, Juniper Networks, Inc.
ATM does not respond to incoming OAM loopback cells during the upgrade for a period
of less than 30 seconds. The lack of response might cause ATM peers to declare VCC
(VPC) down.
The monitoring of ATM port data rates is halted during a unified in-service software
upgrade. Monitoring resumes immediately after the unified ISSU operation is completed.
The data rates reported by the show atm interface command are inaccurate for the
period of one configured load interval after unified ISSU is completed.
A unified in-service software upgrade cannot proceed if VC or VP statistics monitoring
is in progress.
Application Support for Unified ISSU on page 115
The following aspects of DHCP behavior during unified ISSU are different than the behavior
during normal router operations.
The DHCP packet capture application supports unified ISSU in that its configuration does
not halt a unified in-service software upgrade. However, packet capture on line modules
is halted during the upgrade phase. Packets are not captured and buffered for later
forwarding to the SRP module during this phase. Capture resumes automatically during
the service restoration phase.
Application Support for Unified ISSU on page 115
The denial-of-service (DoS) protection application freezes its state when the in-service
software upgrade is initiated. Any suspicious control flow, protocol, or priority remains
suspicious until unified ISSU completes.
Freezing the DoS protection state prevents any active control flows from interfering with
the system while the unified ISSU is in progress. However, no new control flows, protocols,
or priorities are monitored for suspicious activity, and no suspicious activity can be
detected until the upgrade is completed.
NOTE: Because of this limitation on DoS functionality, we recommend that
you do not initiate unified ISSU until all suspicious control flows, protocols,
and priorities have been resolved.
Chapter 5: Configuring a Unified In-Service Software Upgrade
125