Cisco Headend System Release 2.7

 

16 

4017541 Rev B 

After you add an emulated MUX to the DNCS, your next step is to add another BFS 
QAM to the DNCS database to receive data from that device. This section provides 
instructions for adding another BFS QAM to the DNCS. 

Note: If you already have another BFS QAM in your system, you do not need to add 
one. 

 

Before you add another BFS QAM to the DNCS, you must have your network map. 
If you cannot locate your network map, contact Cisco Services. You must also have 
the following information: 

 

Name of the headend containing the QAM  

 

Name used to identify the QAM  

 

IP address for the QAM (from your system administrator) 

 

MAC address for the QAM  

 

Subnet mask for the QAM (from your system administrator) 

 

Type of input interface that will be receiving data from the associated device 
(ASI, DHEI, or SWIF) 
Note: Verify that the QAM you are using has inputs compatible with the outputs 
of your multiplexing device. 

 

A number that identifies the transport stream going from the QAM out to the 
hubs on your system 

 

Type of modulation the QAM uses (ITU B, 64 QAM or ITU B, 256 QAM) 

 

Frequency of the channel being used to send data from the QAM to the hubs on 
your system 

 

Names of the hubs you want to receive data from this QAM  

 

A number that identifies the input port on this QAM  

 

Name of the headend containing the associated device 

 

Type of device being used to send data to this BFS QAM (based on the device 
you chose when you added a device to the DNCS [for example, MUX])  

 

Name of the device you entered when you added the device to the DNCS 

 

The number you entered as the output port of the device that is physically 
connected to the input port on this BFS QAM