© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 4 of 14
●
The service module is added to an operational configuration already equipped with other service
modules or as a replacement of one of them.
Since the Cisco IOS Software major version currently installed is the real factor for the decision, the
customer might need to update the service module to a version either older or newer than the one
preinstalled by manufacturing, depending on the time the spare service module was ordered. In such case
the service disruption is minimal.
●
The service modules have already been deployed in the stack, and a particular bug fix (patch) or a
new functionality requires a software update on either the service module software or the stack
software or both.
All the subsystems in the stack will be updated.
Software Update Options for the Service Module
The service module software can be updated concurrently with Cisco IOS Software update or separately. In the
former case no additional service downtime is caused by the service module update, but longer image download
time due to the introduction of a new image. In the latter case, where only the service modules are updated, an in-
service upgrade procedure is in place to guarantee minimal service disruption.
Simultaneous update with the switch chassis is achieved using the standard Cisco IOS Software CLI command
“archive download-sw” by providing the service module image bundle within the list of Cisco IOS Software images.
This is analogous to the case in which 3750V2 or 3750G switches are present in the same 3750-X stack, requiring
a c3750 image bundle to be specified within the image list.
Software compatibility is enforced by default: the update will be canceled if the new service module image is
incompatible with the new Cisco IOS Software image of the switch chassis. The compatibility check can be
removed by specifying the / no-version-check option. A service module running incompatible software will not be
able to perform Flexible NetFlow, but will still provide uplink traffic functionality, functioning in pass-through mode.
After images have been installed, the new software will be activated after reloading the switch or stack. This will as
well reboot and activate the new software on any service module in the switch/stack. The reload sequence is
accomplished by entering the “reload” command or by specifying the/reload option directly in the “archive
download-sw” CLI.
In a stack topology where only the service modules need to be updated and communication with the distribution
layer is implemented with at least two service modules, an in-service software update procedure is available. The
update procedure consists of the following steps:
1. Install the new software image on all service modules in the stack, using the “archive download-sw
[/no-version-check] <service module image bundle>” CLI command. Do not include the / reload option.
2. After the command completes successfully, reload one service module at a time and wait until the new
software is activated, using the following CLI command. To minimize switchover time, we recommend starting
from “standby” service modules and keeping the “active” service module for last:
switch <slot-number> fru-link reload
(2 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern