Cisco Cisco StadiumVision Director
© 2010-2011 Cisco Systems, Inc. All rights reserved.
Page 46 of 47
Considerations for Upgrading DMPs
Cisco StadiumVision Director currently works with DMP 4310Gs and DMP 4305Gs
that meets the requirements specified below.
that meets the requirements specified below.
Table 5. DMP Requirements
Device
Software Release
DMP 4310G
Firmware: SE1.0.3, Build 1138 or Build 1408
DMP 4305G
Firmware: 5.1.1; Kernel: Linux version 2.4.22
For step-by-step instructions for installing DMPs, see the StadiumVision Video
Endpoint (DMP) Design and Implementation Guide.
Endpoint (DMP) Design and Implementation Guide.
Upgrading DMP 4305Gs
When using Cisco StadiumVision Director 2.x with DMP 4305Gs, ensure that you
do the following (in order) via the StadiumVision Management Dashboard:
do the following (in order) via the StadiumVision Management Dashboard:
•
Apply the Initial Config
•
Upgrade the Kernel
•
Upgrade the Firmware
•
Upgrade the StadiumVision Daemon
•
Apply Global DMP settings (as needed)
See the StadiumVision Video Endpoint (DMP) Design and Implementation Guide for
more information.
more information.
Downgrading DMP 4305Gs
With newer DMP 4305Gs (for example, if new DMP 4305Gs are added to an
existing deployment or a defective DMP 4305G is replaced with a newer one), the
DMP may be shipped with a later version of firmware and the kernel than is
supported by Cisco StadiumVision Director. In this case, the firmware and kernel
need to be “downgraded” to enable communication between the DMP and Cisco
StadiumVision Director.
existing deployment or a defective DMP 4305G is replaced with a newer one), the
DMP may be shipped with a later version of firmware and the kernel than is
supported by Cisco StadiumVision Director. In this case, the firmware and kernel
need to be “downgraded” to enable communication between the DMP and Cisco
StadiumVision Director.
Because the Cisco StadiumVision Director cannot communicate with DMPs that
have a later release of the firmware, you cannot use the Management Dashboard to
load the correct firmware and kernel. Also, DMPDM release 5.2 no longer supports
the set_param?init.ROOT_disable=0 command. Therefore, you can not ssh
into the DMP using sysmng or root.
have a later release of the firmware, you cannot use the Management Dashboard to
load the correct firmware and kernel. Also, DMPDM release 5.2 no longer supports
the set_param?init.ROOT_disable=0 command. Therefore, you can not ssh
into the DMP using sysmng or root.