Upgrading The Os Version During An Rma-Activate Device Workflow; Troubleshooting A Bgp Peer Session On A Device - Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1 Administration Manual

Network and Security Manager Administration Guide

Upgrading the OS Version During an RMA-Activate Device Workflow

Troubleshooting a BGP Peer Session on a Device

302
NOTE: If you are placing an HA device in the RMA state, we highly recommended that
you perform a flash sync immediately after activating and updating that device, This
will ensure that the configuration is synchronized from the device that is not in the RMA
state to the device that is in the RMA state. The flash sync ensures that the two HA
devices are in sync in NSRP. It also ensures that the case sensitivity of the original zone
name is preserved on the device in the RMA state.
As of Release 2007.3, you can use NSM to upgrade the OS version of your replacement
device rather than upgrading it manually.
To upgrade the OS version:
Activate the replacement device. For information about activating a device, see
1.
"Activating a Device" on page 132. After activation, if NSM detects that the replacement
device is running an older OS version than the replaced device, it prompts you to
either continue or reject device activation.
Click Next to put the device in "Firmware upgrade needed" state. If you click Cancel,
2.
the activation fails.
The Software Manager allows you to upgrade the firmware version in the physical device
before RMA. After upgrading, NSM puts the device in the "Update needed" state.
NOTE: The current OS version of the device is also stored in the device object and is
visible in the UI. The directives allowed for this device are "Firmware upgrade," " Adjust
OS version," and "RMA."
Considerations for vsys devices and NSRP directives:
When a device is in the "Firmware upgrade needed" state, directives are not allowed
for its vsys devices.
A peer device cannot perform "Upgrade firmware" and "Adjust OS version" directives
on a cluster member device that is in "Firmware upgrade needed" state, but directives
such as "Update device" and "Import device" are allowed.
NSRP directives are not allowed for either of the two cluster member devices.
To troubleshoot BGP peer configurations, you can connect and disconnect BGP
connections to a specific neighbor. You can also test the TCP connection to a specific
neighbor. To perform these tests, you need to have configured a virtual router and the
BGP dynamic routing protocol on the device, and enabled BGP on the virtual router and
on the interface to the BGP neighbor.
To connect or disconnect to a BGP peer:
Copyright © 2010, Juniper Networks, Inc.