Cisco Headend System Release 2.7
Chapter 3 Enabling CVT Downloads on the DNCS
42
4017541 Rev B
Gather Information for the osmAutoMux.cfg File
You must describe the network topology to the OSM to support bootloader in an
Automux environment. To do this, you enter the following types of records in the
/dvs/dvsFiles/OSM/osmAutoMux.cfg file.
Automux environment. To do this, you enter the following types of records in the
/dvs/dvsFiles/OSM/osmAutoMux.cfg file.
QAM (QAM transport stream ID to headend mapping)
HUB (hub ID to headend mapping)
SESS (session to headend mapping)
This section provides procedures for gathering all of the information you need to
build your osmAutoMux.cfg file. You can record the information you gather in the
worksheets provided later in this chapter or in your own worksheets.
build your osmAutoMux.cfg file. You can record the information you gather in the
worksheets provided later in this chapter or in your own worksheets.
Obtaining Output TSIDs
Complete these steps to find and record the output Transport Stream ID (TSID)
information required for the osmAutoMux.cfg file.
1 From the DNCS Administrative Console, click the Network Element
information required for the osmAutoMux.cfg file.
1 From the DNCS Administrative Console, click the Network Element
Provisioning tab.
2 Click QAM. The QAM List window opens.
3 Using the information in the QAM List window, record the name and the output
TSID for each of the following QAM types in the order presented.
Primary (local) BFS QAM for the primary headend
Video QAMs for the primary headend
Secondary BFS QAM for the secondary headend
Video QAMs for the secondary headend
BFS QAM for an additional headend (if applicable)
Video QAMs for an additional headend (if applicable)