Cisco Cisco StadiumVision Director Wartungshandbuch
© 2011 Cisco Systems, Inc. All rights reserved.
Page 38 of 94
The Provision DMP operation can be initiated automatically or manually. Each time
the Provision DMP is initiated, one of the following actions occur:
the Provision DMP is initiated, one of the following actions occur:
Create a new instance of the Provision DMP operation and execute from Step 1
in the provisioning flow for each of the selected devices, OR
Advance an already executing Provision DMP operation to the next step for
each of the selected devices, if applicable.
Either of the above two operations will occur regardless of whether the Provision
DMP was manually or automatically initiated. Operation instances are created and
tracked on the SV Director Server.
DMP was manually or automatically initiated. Operation instances are created and
tracked on the SV Director Server.
Table 3 lists the commands that are part of the Provision DMP operation and the
sequence in which they are executed. If any step fails, the overall Provision DMP
operation fails.
sequence in which they are executed. If any step fails, the overall Provision DMP
operation fails.
Table 3. Provision DMP Provisioning Commands
Sequence
Number
Number
Command
Description
1
GetStatus
Retrieve the current settings on the DMP
2
StateTransition
Change the DMP State to 'Not Ready'
3
InitialConfig
Executes the InitialConfig command on the DMP. This command sets the
credentials in the DMP and is executed only if the DMP is in the Factory
Default state. The DMP is rebooted as part of this command execution. A
subsequent DMP registration message will trigger the Workflow to advance to
the next step.
credentials in the DMP and is executed only if the DMP is in the Factory
Default state. The DMP is rebooted as part of this command execution. A
subsequent DMP registration message will trigger the Workflow to advance to
the next step.
4
GetStatus
The GetStatus command retrieves the most current configuration on the DMP.
The GetStatus command is executed at various points of the Provision DMP
workflow and is intended to refresh the DMP state in SV Director so that the
execution of previous Workflow steps are reflected correctly in the SV Director
Database.
The GetStatus command is executed at various points of the Provision DMP
workflow and is intended to refresh the DMP state in SV Director so that the
execution of previous Workflow steps are reflected correctly in the SV Director
Database.
5
FirmwareUpgrade
The SV Director will upgrade the Firmware on the DMP, if required. A DMP
reboot will trigger the Workflow to advance to the next step.
reboot will trigger the Workflow to advance to the next step.
6
GlobalMIB
Deploy the Global DMP Settings on the DMP. This step is performed only if
the device is not conforming with the current Global DMP Settings
the device is not conforming with the current Global DMP Settings
7
GetStatus
Retrieves the most current configuration on the device. Note that a previously
executed FirmwareUpgrade would have changed the version and build strings
to match the currently running firmware on the DMP
executed FirmwareUpgrade would have changed the version and build strings
to match the currently running firmware on the DMP
8
StageTemplate
The Flash Template is staged on the DMP.
9
GetStatus
Retrieves the current configuration from the DMP and saves in the SV Director
Database
Database
10
StateTransition
Sets the DMP State to Ready
11
GetStatus
This final GetStatus is issued to get the most current DMP configuration. It is
not necessary to issue this final GetStatus. However, this command has been
placed in the Provision DMP workflow to work around certain timing issues
that may arise when retrieving the Flash Template status
not necessary to issue this final GetStatus. However, this command has been
placed in the Provision DMP workflow to work around certain timing issues
that may arise when retrieving the Flash Template status