Sierra Video DashBoard Control System - Manual (Page 42)

5–2 • DataSafe™ DashBoard User Manual (Iss. 03)
DataSafe Overview
This section briefly outlines the DataSafe feature. DataSafe enables you to replace a failed card
and apply the original card parameters to the working card. This feature is enabled or disabled on
a slot-by-slot basis and currently defaults to OFF. DataSafe also enables you to save card
parameters to a file, and later restore those parameters to one or more cards of the same type.
Multiple configuration sets can be stored if required. This gives you the flexibility of configuring
a large number of cards identically from a single stored configuration.
This feature is available for frames using the MFC-8310-N and MFC-8320-N series cards only.
Figure 5.1 DataSafe Tab Overview
1. DataSafe Tab in the Device View
The DataSafe Tab is available in the Device View of a MFC-8310-N series or MFC-8320-N
series Network Controller Card. The tab lists the cards installed in the frame in slot ascending
order. The following items are displayed in the tab:
• Slot Name — The slot name is set in the Card Slots Names field of the Setup Tab. The
physical slot that the card is installed in is indicated by the number in brackets after the
Slot Name. For more information on re-naming slots, refer to the section “Re-naming an
openGear Slot in the Tree View” on page 6-2.
• Card Type and Software Rev fields — This area indicates the card installed in the slot
and the software version. The information is displayed in the form of xxxx :: #### :: y
where xxxx represents the card type, #### represents the software revision, and y
represents the card status. If the field is blank, there is no saved data for this slot. For
example, in Slot 3 of Figure 5.1, the UDC-8225 is running with software version 2.11
while Slot 2 does not have a card installed.
• Correct Mismatch fields — This area includes the Update Slot button. Clicking this
button automatically updates the slot with the new card information indicated in the
Conflict field.
• Conflict fields — This field is blank if the card currently in the slot has the same card
type and software version as the saved DataSafe data. When the software version or the
card type do not match the saved data for the slot, the Conflict field for that slot is
populated with the new information, alerting the user that a new configuration is
available for that slot. The information is displayed in the form of xxxx :: #### :: y where
xxxx represents the card type, #### represents the software revision, and y represents the
card status. If the field is blank, there is no saved data for this slot.
1
2
3