Cisco Systems 4.1 Dust Collector User Manual


 
5-8
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 5 Understanding RME Device State Transition
States in RME 4.x
If the device is reachable: NetConfig attempts to fulfill the selected job options, and deploys the
configuration to the device. If the device was in the Pre-deployed or Pending states, Device
Management is informed that the device is now contactable.
If the device not reachable: The configuration deployment to this device is marked as failed, and no
state change is requested for.
Software Image Upgrade
To perform Image Distribution by Device (Advanced):
Step 1 Select the Image Distribution by Device (advanced) task. The inventory data is not required.
Step 2 Enter the image, target device and the target destination on the device. The devices can be in the Normal,
Pending, or Pre-deployed states.
For each device Software Management attempts to get required data to do the verification.
Examples of the data required for this verification include the boot loader version for IOS devices, or
the Version running on the supervisor for a Card to be upgraded, and physical attributes like free flash
on the given partition.
The exhaustive data list is device type specific and will be provided in the Software Management design
documents. This data is got from Inventory via ADI.
If verification is possible with the data for the device, Software Management does the verification and
marks the device as verification passed or failed.
If there is insufficient data for this operation, Software Management marks the device as skipped due to
insufficient data, however if the user had specified best-effort verification, the job gets scheduled for
execution with the skipped devices included.
If you had chosen mandatory verification, job creation fails.
At execution time, Software Management attempts to contact each device.
If the device is contactable, and Software Managemente’s internal checks work out, the image is
downloaded to the device, and this device is marked as successful.
If the device was in pending or pre-deployed states at the time of job execution, Software
Management will inform Device Management that the device was contacted.
If the device is not contactable at the job execution time, Software Management will mark this
download as failed, and will continue on with the rest of the devices in the job. No state changes will
be effected.