Unavailability Of Tacacs+ Services During Unified Issu; Interruption In Traffic Forwarding For Layer 3 Routing Protocols During Unified Issu - Juniper SERVICE AVAILABILITY - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x Service Availability Configuration Guide
link only if the defect persists for more than 2.5 seconds, unified ISSU does not cause
the links to be brought down. However, the remote T3 devices must also wait 2.5
seconds before declaring an alarm. If the equipment on the far end of the T3
connection generates an alarm immediately rather than waiting, the link goes down,
causing the higher layers to also go down for the remote equipment.
Related Topics

Unavailability of TACACS+ Services During Unified ISSU

During the upgrade phase of unified ISSU, TACACS+ services are unavailable. If you
have configured AAA authentication for Telnet (with the aaa new-model command)
this lack of availability affects CLI authentication, authorization, and accounting
activities.
CLI login and privilege authentication cannot succeed during a unified ISSU unless
you configure at least one of the alternate authentication methods with the aaa
authentication login command: enable, line, or none.
Similarly, CLI exec and command authorization cannot succeed during a unified
ISSU unless you configure one of the alternate authorization methods with the aaa
authorization command: if-authenticated or none.
Because there is no alternate method of accounting other than TACACS, CLI exec
and command accounting does not work during this phase.
Related Topics

Interruption in Traffic Forwarding for Layer 3 Routing Protocols During Unified ISSU

The routing protocols are affected by two interruptions in traffic forwarding caused
by the unified in-service software upgrade during the upgrade phase.
92
Unavailability of TACACS+ Services During Unified ISSU
Application Support for Unified ISSU on page 71
Application Support for Unified ISSU on page 71
Switchover from active to standby SRP module When the active SRP module
running the current release switches over to the standby SRP module running
the upgrade release, the routing protocols and all other applications restart. A
control plane outage of 30–40 seconds prevents the protocols from sending
hellos or keepalive messages.
The protocols must gracefully restart to come back online, recover their routing
state on the newly active SRP module, and respond to their peers. Therefore,
you must enable graceful restart for all protocols before you begin the unified
in-service software upgrade. All neighbors of the routing protocols must also be
configured to support graceful restart.
A data plane outage of about 1 second for the E120 and E320 routers and about
4 seconds for the ERX1440 router also takes place during the switchover of the
fabric from the active primary SRP module to the standby SRP module.