Cisco Cisco StadiumVision Mobile Reporter Manual De Mantenimiento
© 2011 Cisco Systems, Inc. All rights reserved.
Page 39 of 94
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.
viewing the status messages on the Console tab at the bottom of the screen in the
Management Dashboard.
Automatically Executing the Provision DMP Command
The Provision DMP operation is automatically initiated if the Enable Auto
Provisioning and Enable Auto Registration keys are set to true in the Dashboard.
The Provision DMP will be skipped if the DMP is in
Provisioning and Enable Auto Registration keys are set to true in the Dashboard.
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 SV 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.
of this workflow command is created or a previously running instance is advanced.
The DMP sends a registration request to the SV 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 SV Director and the DHCP Server for auto registration and provisioning
will be described in a later section.
will be described in a later section.
Auto Registering and Auto Provisioning Multiple DMPs
StadiumVision Director can auto register approximately 200 DMPs at the same
time. As registrations come in, up to 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.
time. As registrations come in, up to 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.
DMP States During Provisioning
While a DMP is being provisioned, it transitions through three states:
Not Ready -> Ready -> Production
Not Ready: The DMP is registered in SV Director but has not been
provisioned.
Ready: The DMP is provisioned in SV Director but has not been assigned to
a Location. Note that all scripting is done on Locations and not on DMPs.
In Production: The DMP is registered, provisioned and assigned to a
Location in SV Director.
As the DMP transitions through these states, you can view the progress on the
Management Dashboard and Control Panel. See
Management Dashboard and Control Panel. See
Manually Executing the Provision DMP Command
As an alternative to using auto provisioning, you can manually execute the
Provision DMP operation to provision one or more DMPs. This operation is
executed from the Dashboard just like any of the other Dashboard commands.
Provision DMP operation to provision one or more DMPs. This operation is
executed from the Dashboard just like any of the other Dashboard commands.