Cisco TV CDS 2.4 RTSP Software Configuration Guide for the Cisco ISM (Integrated Service Module) Line Card
Creating Bulk Configuration Files
Downloads: This chapterpdf (PDF - 248.0KB) The complete bookPDF (PDF - 9.24MB) | Feedback

Creating Bulk Configuration Files

Table Of Contents

Creating Bulk Configuration Files

Introduction

Creating QAM Gateway Bulk Configuration Files

Creating Headend Setup Bulk Configuration Files

Creating Stream Destination Bulk Configuration Files

Creating Route Table Bulk Configuration Files

Creating SNMP Agent Bulk Configuration Files

Creating DNS Server Bulk Configuration Files

Creating NTP Server Bulk Configuration Files

Creating FSI Setup Bulk Configuration Files

Creating RTSP Setup Bulk Configuration Files

Bulk Configuration XML Schema


Creating Bulk Configuration Files


This appendix describes the Bulk Configuration feature and consists of the following topics:

Introduction

Creating QAM Gateway Bulk Configuration Files

Creating Stream Destination Bulk Configuration Files

Creating Route Table Bulk Configuration Files

Creating SNMP Agent Bulk Configuration Files

Creating DNS Server Bulk Configuration Files

Creating NTP Server Bulk Configuration Files

Creating FSI Setup Bulk Configuration Files

Creating RTSP Setup Bulk Configuration Files

Bulk Configuration XML Schema

Introduction

Bulk Configuration provides a method of configuring common parameters for all the servers at one time by using an XML file. Following are the CDSM GUI configuration pages that offer Bulk Configuration:

QAM Gateway

Headend Setup

Stream Destination

NTP Server

Server DNS

SNMP Agent

Route Tables

RTSP Setup

FSI Setup


Note To enable the optional Bulk Configuration feature, see the "Bulk Configuration" section on page D-4.


Creating QAM Gateway Bulk Configuration Files

The QAM Gateway page is used to identify the QAM device (IP address), and to configure the preference settings for the Stream Groups. For Layer 2 networks, there is an option to specify the MAC address of the next hop for each Stream Group and Streamer.


Note Before you can use the Bulk Configuration feature to configure QAM gateways and the headend setup, all Streamers must be associated with a Stream Group. For more information on Stream Groups, see the "Configuring Stream Groups" section on page 3-29.


Table B-1 describes the Bulk Configuration file elements for QAM gateways for gigabit Ethernet streaming.

Table B-1 Bulk Configuration File Elements for Gigabit Ethernet QAM Gateways 

Tag
Elements
Attributes
Description

QAMList

QAM

Marks beginning and end of QAM devices.

QAM

QAMStreamGroupPreference

IP

Defines a QAM device.

QAMStreamGroupPreference

Server

StreamGroupName
QAMMAC
Preference

Maps Stream Groups to the QAM device. The QAMMAC attribute is optional and is only used for Layer 2 networks.

Server

ServerID
GroupID
QAMMAC

Optional. Maps the MAC address of the QAM device to a Streamer. Only used in Layer 2 networks.


For information about the values of the attributes, see the "Configuring QAM Gateways" section on page 3-4. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive.

The Preference attribute can have a value of High or None. These values are case sensitive.


Following is an example of the Bulk Configuration file used to populate the QAM Gateway page. The example is for a Layer 2 network and uses the optional QAMMAC attribute for the QAMStreamGroupPreference and the optional Server element to specify the next hop MAC address.

<QAMList  xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <QAM IP="1.1.1.1">
      <QAMStreamGroupPreference StreamGroupName="SG1" QAMMAC="00:00:00:00:00:01" Preference="High">
             <Server ServerID="50" GroupID="1" QAMMAC="00:00:00:00:00:11" />
       </QAMStreamGroupPreference>            
      <QAMStreamGroupPreference StreamGroupName="SG2" QAMMAC="00:00:00:00:00:02" Preference="None">
              <Server ServerID="55" GroupID="1" QAMMAC="00:00:00:00:00:11" />
     </QAMStreamGroupPreference >
      <QAMStreamGroupPreference StreamGroupName="SG3" QAMMAC="00:00:00:00:00:03" Preference="None"/>
   </QAM>
    <QAM IP="1.1.1.2">
      <QAMStreamGroupPreference StreamGroupName="SG1" QAMMAC="00:00:00:00:00:01" Preference="None"/>
      <QAMStreamGroupPreference StreamGroupName="SG2" QAMMAC="00:00:00:00:00:02" Preference="High"/>
    </QAM>
</QAMList>

Creating Headend Setup Bulk Configuration Files

The Bulk Configuration file for the Headend Setup page consist of service groups to Stream Groups mappings. Table B-2 defines the Bulk Configuration file elements for headend setup.

Table B-2 Bulk Configuration File Elements for Headend Setup 

Tag
Elements
Attributes
Description

Headend

ServiceGroupToStreamGroup

Marks beginning and end of mapping of service groups to Stream Groups.

ServiceGroupToStreamGroup

ServiceGroup
StreamGroup

Maps service groups to Stream Groups.


For information about the values of the attributes, see the "Configuring the Headend Setup" section on page 3-7. Following is an example of the Bulk Configuration file used to populate the Headend Setup page:

<?xml version="1.0" encoding="UTF-8"?>
<Headend
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <ServiceGroupToStreamGroup ServiceGroup="4666669" StreamGroup="NEWTEST" />
    <ServiceGroupToStreamGroup ServiceGroup="4666668" StreamGroup="s234" />
    <ServiceGroupToStreamGroup ServiceGroup="4666664" StreamGroup="NEWTEST" />
    <ServiceGroupToStreamGroup ServiceGroup="4666663" StreamGroup="s234" />
    <ServiceGroupToStreamGroup ServiceGroup="1666669" StreamGroup="NEWTEST123" />
    <ServiceGroupToStreamGroup ServiceGroup="1666668" StreamGroup="s234" />
    <ServiceGroupToStreamGroup ServiceGroup="1666664" StreamGroup="NEWTEST" />
    <ServiceGroupToStreamGroup ServiceGroup="1666663" StreamGroup="s234" />
</Headend>

Creating Stream Destination Bulk Configuration Files

If the Stream Destination is set to IPTV, the Stream Destination page is displayed instead of the QAM Gateway and Headend Setup pages. For more information, see the "Stream Destination" section on page D-4. The Stream Destination page provides a way to associate subnetworks with Stream Groups.

Table B-3 defines the Bulk Configuration file elements for Stream Destination.

Table B-3 Bulk Configuration File Elements for Stream Destination 

Tag
Elements
Attributes
Description

StreamDestinationList

StreamDestination

Marks beginning and end of subnets defined for IPTV.

StreamDestination

StreamGroupPreference

SubnetAddress
SubnetMask

Defines a subnet.

StreamGroupPreference

StreamGroupName
Preference

Maps Stream Groups to the subnet address.


For information about the values of the attributes, see the "Configuring Stream Destinations" section on page 3-8.


Note The Preference attribute can have a value of High or None. These values are case sensitive.


Following is an example of the Bulk Configuration file used to populate the Stream Destination page.

<?xml version="1.0" encoding="UTF-8"?> 
<StreamDestinationList 
     xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs">
     <StreamDestination SubnetAddress="132.2.2.0" SubnetMask="255.255.255.0" >
          <StreamGroupPreference StreamGroupName="NEWTEST" Preference="High" />
          <StreamGroupPreference StreamGroupName="s234" Preference="None" />
     </StreamDestination>
     <StreamDestination SubnetAddress="130.10.10.0" SubnetMask="255.255.255.0" >
          <StreamGroupPreference StreamGroupName="s234" Preference="High" />
          <StreamGroupPreference StreamGroupName="NEWTEST" Preference="None" />
     </StreamDestination>
</StreamDestinationList>

Creating Route Table Bulk Configuration Files

The Route Table page allows you to define multiple subnets on a server. For more information, see the "Configuring the Route Table" section on page 3-66.

Table B-4 defines the Bulk Configuration file elements for the Route Table page.

Table B-4 Bulk Configuration File Elements for Route Tables 

Tag
Elements
Attributes
Description

RouteTableList

RouteTable

Marks beginning and end of defined routes.

RouteTable

Server
Route

Defines a route table.

Server

ServerID
GroupID

Identifies the CDS server.

Route

Network
SubnetMask
Gateway
RouteType

Defines a route.


For information about the values of the attributes, see the "Configuring the Route Table" section on page 3-66. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive.

The RouteType attributes possible values are: cServer Source, cServer Destination, or Stream Control. These values are case sensitive.


Following is an example of the Bulk Configuration file used to populate the Route Table page:

<?xml version="1.0" encoding="UTF-8"?>

<RouteTableList   xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
 
     <RouteTable>
        <Server ServerID="ALL" GroupID="ALL"/>
        <Route Network="3.2.3.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="3.2.5.0" SubnetMask="255.255.255.0" Gateway="1.1.1.1" RouteType="cServer Source" />
        <Route Network="3.2.6.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source"/>
        <Route Network="4.2.7.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="5.2.8.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="2.2.9.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="6.2.10.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="7.2.21.0" SubnetMask="255.255.d255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
     </RouteTable>
 
     <RouteTable>
        <Server ServerID="50" GroupID="1111"/>
        <Server ServerID="51" GroupID="1111"/>
        <Server ServerID="52" GroupID="1111"/>
        <Server ServerID="53" GroupID="1111"/>
        <Route Network="120.2.3.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.4.0" SubnetMask="255.255.255.0" Gateway="1.1.1.11" RouteType="cServer Source" />
        <Route Network="120.2.5.0" SubnetMask="255.255.255.0" Gateway="1.1.1.1" RouteType="cServer Source" />
        <Route Network="120.120.2.6" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.7.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.8.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.9.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.10.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
        <Route Network="120.2.21.0" SubnetMask="255.255.d255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
     </RouteTable>

</RouteTableList>

Creating SNMP Agent Bulk Configuration Files

The SNMP Agent page is used to configure SNMP communication. Table B-5 defines the Bulk Configuration file elements for the SNMP Agent page.

Table B-5 Bulk Configuration File Elements for SNMP Agent 

Tag
Elements
Attributes
Description

SNMPAgentList

SNMPAgent

Marks beginning and end of defined SNMP agents.

SNMPAgent

Server
SNMPCommunity
SNMPTrapStation

Contact
Location

Defines an SNMP agent.

Server

ServerID
GroupID

Identifies the CDS server.

SNMPCommunity

Name
Permissions

Defines the community for the SNMP agent.

SNMPTrapStation

TrapStation
Version

Defines the trap station for the SNMP agent.


For information about the values of the attributes, see the "Configuring the SNMP Agent" section on page 3-69. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive.


Following is an example of the Bulk Configuration file used to populate the SNMP Agent page:

<?xml version="1.0" encoding="UTF-8"?>
<SNMPAgentList 
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >

    <SNMPAgent Contact="TestContact" Location="TestLocation">
        <Server ServerID="ALL" GroupID="ALL"/>
        <SNMPCommunity Name="public" Permissions="Read-Only" />
        <SNMPCommunity Name="public2" Permissions="Read-Only" />
        <SNMPTrapStation TrapStation="77.77.77.77" Version="v1"/>
        <SNMPTrapStation TrapStation="177.77.77.77" Version="v2"/>
    </SNMPAgent>


    <SNMPAgent Contact="XXXX" Location="YYYY">
        <Server ServerID="71" GroupID="1111"/>
        <Server ServerID="72" GroupID="1111"/>
        <Server ServerID="73" GroupID="1111"/>
        <Server ServerID="74" GroupID="1111"/>
        <Server ServerID="75" GroupID="1111"/>
        <SNMPCommunity Name="XXXX" Permissions="Read-Only" />
        <SNMPCommunity Name="YYYY" Permissions="Read-Only" />
        <SNMPTrapStation TrapStation="5.99.99.9" Version="v1"/>
        <SNMPTrapStation TrapStation="55.77.77.77" Version="v2"/>
    </SNMPAgent>
</SNMPAgentList>

Creating DNS Server Bulk Configuration Files

The Server DNS page is used to configure the DNS servers. Table B-6 defines the Bulk Configuration file elements for the Server DNS page.

Table B-6 Bulk Configuration File Elements for DNS Server 

Tag
Elements
Attributes
Description

DNSList

DNS

Marks the beginning and ending of the DNS settings

DNS

Server
DomainSuffix
DNSServer

Defines the DNS server settings.

Server

ServerID
GroupID

Identifies the CDS server.

DomainSuffix

Defines the domain suffix.

DNSServer

Defines the DNS server.


.

For information about the values of the attributes, see the "Configuring the Server Level DNS" section on page 3-71. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive. The Permission attribute can have the value of Read-Only or Read-Write.


Following is an example of the Bulk Configuration file used to populate the Server DNS page:

<<?xml version="1.0" encoding="UTF-8"?>

<DNSList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <DNS>
        <Server ServerID="ALL" GroupID="ALL"/>
        <DomainSuffix>first.sp.com</DomainSuffix>
        <DomainSuffix>second.abc.com</DomainSuffix>
        <DomainSuffix>third.xyz.com</DomainSuffix>
        <DNSServer>152.1.1.10</DNSServer>
        <DNSServer>222.2.2.11</DNSServer>
    </DNS>
</DNSList>

Creating NTP Server Bulk Configuration Files

The NTP Server page is used to configure the NTP servers. Table B-7 defines the Bulk Configuration file elements for the NTP Server page.

Table B-7 Bulk Configuration File Elements for NTP Server 

Tag
Elements
Attributes
Description

NTPServerList

NTPServer

Marks the beginning and ending of the NTP settings.

NTPServer

Server
NTPServerIP

Defines the NTP settings.

Server

ServerID
GroupID

Identifies the CDS server.

NTPServerIP

Defines the NTP server.


For information about the values of the attributes, see the "Configuring the Server Level NTP" section on page 3-72. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive.


Following is an example of the Bulk Configuration file used to populate the NTP Server page:

<<?xml version="1.0" encoding="UTF-8"?>

<NTPServerList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <NTPServer>
        <Server ServerID="ALL" GroupID="ALL"/>
        <NTPServerIP>198.168.1.10</NTPServerIP>
        <NTPServerIP>172.31.2.11</NTPServerIP>
    </NTPServer>
</NTPServerList>

Creating FSI Setup Bulk Configuration Files

The FSI Setup page is used to configure the FSI. Table B-8 defines the Bulk Configuration file elements for the FSI Setup page.

Table B-8 Bulk Configuration File Elements for FSI Setup 

Tag
Elements
Attributes
Description

FSISetupList

FSISetup

Marks the beginning and ending of the FSI settings.

FSISetup

Server

IPAddress
ServerPort
FTPClientPort
FTPOutServerPort
FTPOutLoginTTL
LogLevel
ContentRootPath
AsyncCallbackURL

Defines the FSI settings.

Server

ServerID
GroupID

Identifies the CDS server.


For information about the values of the attributes, see the "Configuring FSI Setup" section on page 3-80. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive. The LogLevel attribute can have the value of High, Low, or Off.


Following is an example of the Bulk Configuration file used to populate the FSI Setup page:

<?xml version="1.0" encoding="UTF-8"?>

<FSISetupList 
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >

     <FSISetup IPAddress="171.1.1.1" 
          ServerPort="333" 
          FTPClientPort="555" 
          FTPOutServerPort="5001" 
          FTPOutLoginTTL="64"
          LogLevel="Off" 
          ContentRootPath="/videcontent/" 
          AsyncCallbackURL="http://1.1.1.1/test.php" >

          <Server ServerID="61" GroupID="1111"/>
     </FSISetup>
</FSISetupList>

Creating RTSP Setup Bulk Configuration Files

The RTSP Setup page is used to configure the RTSP. Table B-9 defines the Bulk Configuration file elements for the RTSP Setup page.

Table B-9 Bulk Configuration File Elements for RTSP Setup 

Tag
Elements
Attributes
Description

RTSPSetupList

RTSPSetup

Marks the beginning and ending of the RTSP settings.

RTSPSetup

Server
RTSPClientList

See the RTSP Setup Fields table for a description of the values and the applicable fields for your RTSP deployment.

Defines the RTSP settings.

Server

ServerID
GroupID

Identifies the CDS server.

RTSPClientList

RTSPClient

Marks the beginning and ending of the RTSP clients.

RTSPClient

ReceivePort
SendPOrt
ReceiveBuffer
Model
Transport

Defines the RTSP client.


For information about the values of the attributes, see the "Configuring RTSP Setup" section on page 3-75. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the "Configuring the Servers" section on page 3-58.


Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive.


Following are examples of the Bulk Configuration file used to populate the RTSP Setup page for the different RTSP deployment types:

DSM-CC RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="1.1.1.1"
               BackofficeTimeout="3000"
               RTSPServerIP="121.1.1.2"
               LSCPAddress="1.1.1.1" 
               LSCPPort="1111" 
               LSCPResponsePadding="on" 
               RTSPServerPort="5000"
               LogLevel="Off"
               MaintenanceMode="on">

        <Server ServerID="5" GroupID="111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

RTSP RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="121.1.1.1"
               LoopingSessionTimeout="11000"
               SessionInactivityTimeout="22000" 
               BackofficeTimeout="33000"
               RTSPServerIP="171.1.1.2"
               RTSPServerPort="15000"
               ReconnectIP="12.1.1.3"
               ReconnectPort="9000"
               MaxHistory="5"
               LogLevel="high"
               MaintenanceMode="off">
        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="3111" SendPort="9222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="3999" SendPort="9888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>

</RTSPSetupList>

NGOD RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="1.1.1.1"
               BackofficeTimeout="3000"
               SessionInactivityTimeout="22000" 
               RTSPServerIP="121.1.1.2"
               RTSPServerPort="5000"
               LSCPAddress="1.1.1.1" 
               LSCPPort="1111" 
               LSCPResponsePadding="on" 
               ComponentName="xyz" 
               LogLevel="low"
               MaintenanceMode="on">

        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

IPTV RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="1.1.1.1"
               SessionInactivityTimeout="22000" 
               LogLevel="high"
               MaintenanceMode="on">

        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

EventIS on-vpath RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="172.1.1.1"
               BackofficeTimeout="3000"
               SessionInactivityTimeout="22000" 
               AuthenticationManagerIP="121.1.1.2"
               AuthenticationManagerPort="5000" 
               BandwidthManagerIP="121.1.1.2"
               BandwidthManagerPort="5000"
               BackupBandwidthManagerIP="1.1.1.1" 
               BackupBandwidthManagerPort="1111" 
               LogLevel="high" 
               MaintenanceMode="off">

        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

EventIS off-vpath RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="172.1.1.1"
               SessionInactivityTimeout="22000" 
               AuthenticationManagerIP="121.1.1.2"
               AuthenticationManagerPort="5000"
               ServerIP="10.1.1.1" 
               ServerPort="5555" 
               StreamControlIP="191.1.1.2" 
               StreamControlPort="9000" 
               LogLevel="high" 
               MaintenanceMode="off">

        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

Quative RTSP Deployment

<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
    xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
    <RTSPSetup MasterStreamingIP="172.1.1.1"
               SessionInactivityTimeout="2000" 
               CallbackServerIP="129.1.1.2"
               CallbackServerPort="4000" 
               LogLevel="low" 
               MaintenanceMode="on">

        <Server ServerID="2" GroupID="1111"/>
        <RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
        <RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
    </RTSPSetup>
</RTSPSetupList>

Bulk Configuration XML Schema

The XML Schema file describes and dictates the content of the XML file. The BulkConfiguration.xsd file contains the XML schema.

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
           xmlns:ws="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs"
           targetNamespace="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" > 

<!-- Configure/Server/ elements  -->

    <xs:element name="Server">
        <xs:complexType>
            <xs:attribute name="ServerID"   type="xs:string"    use="required"/>
            <xs:attribute name="GroupID"    type="xs:string"    use="required"/>
            <xs:attribute name="QAMMAC"     type="xs:string"/>
        </xs:complexType>
    </xs:element>

<!-- Configure/System/QAMGateway/ elements  --> 

    <xs:element name="QAMStreamGroupPreference">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="StreamGroupName"    type="xs:string"/>
            <xs:attribute name="QAMMAC"             type="xs:string"/>
            <xs:attribute name="Preference"         type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="TSIDOutLink">
        <xs:complexType>
            <xs:attribute name="Index"              type="xs:nonNegativeInteger"/>
            <xs:attribute name="TSIDOut"            type="xs:string"/>
            <xs:attribute name="TSIDOutLinkStatus"  type="xs:string"/>
            <xs:attribute name="ServiceGroup"       type="xs:string"/>     
            <xs:attribute name="RFNumber"           type="xs:string"/>  
        </xs:complexType>
    </xs:element>

    <xs:element name="QAMASILink">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:TSIDOutLink"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>        
            <xs:attribute name="Number"             type="xs:string"/>
            <xs:attribute name="TSIDIn"             type="xs:string"/>
            <xs:attribute name="TSIDInLinkStatus"   type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="QAMLink">
        <xs:complexType>
            <xs:attribute name="Status"         type="xs:string"/>
            <xs:attribute name="ServiceGroup"   type="xs:string"/>
            <xs:attribute name="RFNumber"       type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="GQAMLink">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:TSIDOutLink"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="ServiceGroup"   type="xs:string"/>
            <xs:attribute name="RFNumber"       type="xs:string"/>
       </xs:complexType>
    </xs:element>

    <xs:element name="QAM">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:QAMStreamGroupPreference"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:QAMLink"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:QAMASILink"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:GQAMLink"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="IP"         type="xs:string"/>
            <xs:attribute name="Type"       type="xs:string"/>
            <xs:attribute name="GQAMPort"   type="xs:positiveInteger"/>
       </xs:complexType>
   </xs:element>

    <xs:element name="QAMList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:QAM" 
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/System/StreamDestination/ elements  -->

    <xs:element name="StreamGroupPreference">
        <xs:complexType>
            <xs:attribute name="StreamGroupName"    type="xs:string"/>
            <xs:attribute name="Preference"         type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="StreamDestination">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:StreamGroupPreference"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="SubnetAddress"  type="xs:string"/>
            <xs:attribute name="SubnetMask"     type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="StreamDestinationList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:StreamDestination" 
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/System/Headend/ elements -->  

    <xs:element name="ServiceGroupToStreamGroup">
        <xs:complexType>
            <xs:attribute name="ServiceGroup"   type="xs:string"/>
            <xs:attribute name="StreamGroup"    type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="Headend">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:QAM"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:ServiceGroupToStreamGroup"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
   </xs:element>

<!-- Configure/Server/RouteTables/ elements  -->

    <xs:element name="Route">
        <xs:complexType>
            <xs:attribute name="Network"    type="xs:string"/>
            <xs:attribute name="SubnetMask" type="xs:string"/>
            <xs:attribute name="Gateway"    type="xs:string"/>
            <xs:attribute name="RouteType"  type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="RouteTable">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:Route"
                            minOccurs="0"
                            maxOccurs="unbounded" />
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="RouteTableList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:RouteTable"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/Server/SNMP/ elements  --> 

    <xs:element name="SNMPCommunity">
        <xs:complexType>
            <xs:attribute name="Name"           type="xs:string"/>
            <xs:attribute name="Permissions"    type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="SNMPTrapStation">
        <xs:complexType>
            <xs:attribute name="TrapStation"    type="xs:string"/>
            <xs:attribute name="Version"        type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="SNMPAgent">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:SNMPCommunity"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:SNMPTrapStation"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="Contact"        type="xs:string"/>
            <xs:attribute name="Location"       type="xs:string"/>
        </xs:complexType>
   </xs:element>

    <xs:element name="SNMPAgentList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:SNMPAgent"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/Server/RTSP/ elements  -->

    <xs:element name="RTSPClient">
        <xs:complexType>
            <xs:attribute name="ReceivePort"    type="xs:positiveInteger"/>
            <xs:attribute name="SendPort"       type="xs:positiveInteger"/>
            <xs:attribute name="ReceiveBuffer"  type="xs:positiveInteger"/>
            <xs:attribute name="Model"          type="xs:string"/>
            <xs:attribute name="Transport"      type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="RTSPSetup">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:RTSPClient"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>    
            <xs:attribute name="MasterStreamingIP"          type="xs:string"/>
            <xs:attribute name="LoopingSessionTimeout"      type="xs:positiveInteger"/>
            <xs:attribute name="SessionInactivityTimeout"   type="xs:positiveInteger"/>
            <xs:attribute name="BackofficeTimeout"          type="xs:positiveInteger"/>
            <xs:attribute name="RTSPServerIP"               type="xs:string"/>
            <xs:attribute name="RTSPServerPort"             type="xs:positiveInteger"/>
            <xs:attribute name="ReconnectIP"                type="xs:string"/>
            <xs:attribute name="ReconnectPort"              type="xs:positiveInteger"/>
            <xs:attribute name="MaxHistory"                 type="xs:nonNegativeInteger"/>
            <xs:attribute name="LogLevel"                   type="xs:string"/>
            <xs:attribute name="MaintenanceMode"            type="xs:string"/>
            <xs:attribute name="LSCPAddress"                type="xs:string"/>
            <xs:attribute name="LSCPPort"                   type="xs:positiveInteger"/>
            <xs:attribute name="LSCPResponsePadding"        type="xs:string"/>
            <xs:attribute name="ComponentName"              type="xs:string"/>
            <xs:attribute name="BandwidthManagerIP"         type="xs:string"/>
            <xs:attribute name="BandwidthManagerPort"       type="xs:positiveInteger"/>
            <xs:attribute name="AuthenticationManagerIP"    type="xs:string"/>
            <xs:attribute name="AuthenticationManagerPort"  type="xs:positiveInteger"/>
            <xs:attribute name="BackupBandwidthManagerIP"   type="xs:string"/>
            <xs:attribute name="BackupBandwidthManagerPort" type="xs:positiveInteger"/>
            <xs:attribute name="CallbackServerIP"           type="xs:string"/>
            <xs:attribute name="CallbackServerPort"         type="xs:positiveInteger"/>
            <xs:attribute name="ServerIP"                   type="xs:string"/>
            <xs:attribute name="ServerPort"                 type="xs:positiveInteger"/>
            <xs:attribute name="StreamControlIP"            type="xs:string"/>
            <xs:attribute name="StreamControlPort"          type="xs:positiveInteger"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="RTSPSetupList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:RTSPSetup"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/Server/FSI/ elements  -->

    <xs:element name="FSISetup">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
            <xs:attribute name="IPAddress"          type="xs:string"/>
            <xs:attribute name="ServerPort"         type="xs:positiveInteger"/>
            <xs:attribute name="FTPClientPort"      type="xs:positiveInteger"/>
            <xs:attribute name="FTPOutServerPort"   type="xs:positiveInteger"/>
            <xs:attribute name="FTPOutLoginTTL"     type="xs:positiveInteger"/>
            <xs:attribute name="LogLevel"           type="xs:string"/>
            <xs:attribute name="ContentRootPath"    type="xs:string"/>
            <xs:attribute name="AsyncCallbackURL"   type="xs:string"/>
        </xs:complexType>
    </xs:element>

    <xs:element name="FSISetupList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:FSISetup"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/Server/DNS elements  -->

    <xs:element name="DomainSuffix" type="xs:string"/>

    <xs:element name="DNSServer" type="xs:string"/>

    <xs:element name="DNS">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:DomainSuffix"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:DNSServer"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
           </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="DNSList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:DNS"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
           </xs:sequence>
        </xs:complexType>
    </xs:element>

<!-- Configure/Server/NTPServer elements  -->

    <xs:element name="NTPServerIP" type="xs:string"/>

    <xs:element name="NTPServer">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:Server"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
                <xs:element ref="ws:NTPServerIP"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
           </xs:sequence>
        </xs:complexType>
    </xs:element>

    <xs:element name="NTPServerList">
        <xs:complexType>
            <xs:sequence>
                <xs:element ref="ws:NTPServer"
                            minOccurs="0"
                            maxOccurs="unbounded"/>
           </xs:sequence>
        </xs:complexType>
    </xs:element>

</xs:schema>