Cisco Cisco StadiumVision Director Wartungshandbuch
© 2012 Cisco Systems, Inc. All rights reserved.
Page 49 of 103
Note: You can see more detail about the steps and sub steps being performed by
viewing the status messages on the Console tab at the bottom of the screen in the
Management Dashboard. Do not be alarmed if you see a sub step being repeated.
This is normal as the process is iterative. For example, once a DMP has been
upgraded the FirmwareUpgrade step will be repeated in order to confirm that the
DMP is now running the expected firmware version.
viewing the status messages on the Console tab at the bottom of the screen in the
Management Dashboard. Do not be alarmed if you see a sub step being repeated.
This is normal as the process is iterative. For example, once a DMP has been
upgraded the FirmwareUpgrade step will be repeated in order to confirm that the
DMP is now running the expected firmware version.
Automatically Executing the Provision DMP Command
The Provision DMP operation is automatically initiated if both the Enable Auto
Provisioning and Enable Auto Registration keys are set to true in the Dashboard,
and if StadiumVision Director is configured to indicate DHCP is in use under
SV_Director_Config
Provisioning and Enable Auto Registration keys are set to true in the Dashboard,
and if StadiumVision Director is configured to indicate DHCP is in use under
SV_Director_Config
System_ConfigGlobal_DMP_SettingsCommonDHCP".
The Provision DMP will be skipped if the DMP is in the “Ready” or “In Production”
state. Whenever a registration message is received from the DMP, a new instance
of this workflow command is created or a previously running instance is advanced.
The DMP sends a registration request to the Cisco StadiumVision Director every
time it is rebooted, assuming that DHCP is enabled and the DHCP Server is
appropriately configured. Several of the commands in the Provision DMP workflow
require the DMP to be rebooted. Such commands will automatically reboot the DMP
as needed.
state. Whenever a registration message is received from the DMP, a new instance
of this workflow command is created or a previously running instance is advanced.
The DMP sends a registration request to the Cisco StadiumVision Director every
time it is rebooted, assuming that DHCP is enabled and the DHCP Server is
appropriately configured. Several of the commands in the Provision DMP workflow
require the DMP to be rebooted. Such commands will automatically reboot the DMP
as needed.
Preparing Cisco StadiumVision Director and the DHCP Server for auto-registration
and provisioning will be described in a later section.
and provisioning will be described in a later section.
Auto-Registering and Auto-Provisioning Multiple DMPs
There is no hard limit as to how many auto-registrations StadiumVision Director can
handle at the same time. However, as registrations come in, a maximum of 50 auto-
registered DMPs can be provisioned in parallel. The remaining DMPs are queued
for provisioning and as DMPs complete the provisioning process, new DMPs are
provisioned.
handle at the same time. However, as registrations come in, a maximum of 50 auto-
registered DMPs can be provisioned in parallel. The remaining DMPs are queued
for provisioning and as DMPs complete the provisioning process, new DMPs are
provisioned.
Note that the limit of 50 is the maximum number of DMPs that StadiumVision will
send commands at any given point in time. However, more than 50 DMPs may end
up being provisioned simultaneously since different DMPs may be in different
states. For example, DMPs that are in the middle of a reboot are skipped until these
send commands at any given point in time. However, more than 50 DMPs may end
up being provisioned simultaneously since different DMPs may be in different
states. For example, DMPs that are in the middle of a reboot are skipped until these
StateTransition
Sets the DMP State to ‘Ready’
SetAppUpdate
Yet another update to the status info displayed on the TV
Verification
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
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
SetAppUpdate
Update the status info displayed on the TV to show ‘Completed!’