cc/td/doc/product/cable/vod/umg9820
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Starting and Configuring the Cisco uMG9820

Checking Conditions Prior to System Startup

Starting the System

Configuration Tasks

Command Syntax

Configuring Passwords

Configuring GE Ports

Using GE Session Commands

Configuring Management Ports

Configuring the Transport Stream

Configuring and Monitoring QAM Service

Upgrading Software

Managing Configurations

Using the Terminal (Console) Port

Sample Configuration

Using the Terminal (Console) Port

Starting and Configuring the Cisco uMG9820


This chapter describes how to start the system and initially configure your Cisco uMG9820. The chapter presents the following major topics:

Checking Conditions Prior to System Startup

Starting the System

Configuration Tasks

In addition, for a sample running configuration file, see the following:

Sample Configuration


Note The initial configuration of the Cisco uMG9820 is done from a console. Connect a terminal to the Cisco uMG9820's console port using the adapter cable kit provided. See Connecting to the Console Port, page 3-10.


Checking Conditions Prior to System Startup

Ensure the following before you start your Cisco uMG9820:

The processor card is inserted securely in its slot.

The primary VoD network feed has been connected to the GIG1 port.

(Optional) A redundant VoD network feed (if redundancy is required) has been connected to the GIG2 port.

The SFP modules used in the GIG1 and GIG2 ports are compatible with the physical interface to the VoD network.

The NMS port is connected to the LAN that accesses the web-based control interface.

The CAS port is connected to the LAN that supports conditional access.

A terminal is connected to the Cisco uMG9820's console port, using the adapter cable kit provided. The console port is accessed through a terminal emulation package such as Hyperterminal. Use the setting shown in Connecting to the Console Port, page 3-10.

Starting the System

After installing the Cisco uMG9820 and connecting required cables, start the Cisco uMG9820 as follows:


Step 1 At the back of the Cisco uMG9820, insert one end of the power cord into the AC-input receptacle, then insert the other end into the power outlet.

The green power (POWER) LED on the Cisco uMG9820 comes on.

Step 2 Listen for the fans. You should immediately hear them operating.

Step 3 During the boot process, observe the system LEDs.

The front panel LEDs (PS/FAN, PROC, and QAM 1 through 6) transition from off to yellow, then to green, and then to the functionality as described in Table 1-2. If the processor card is not installed on power-up, all LEDs (except the POWER LED) default to off.


Note If the processor card is removed after power-up, all LEDs maintain their current state, except that the PROC CARD LED goes off.


Step 4 Observe the initialization process. When the system boot is complete (after a few seconds), the processor card begins to initialize the interfaces. During this initialization, the LEDs on each port behave differently (most flash on and off).

The LNK LED on each processor card interface comes on when initialization is completed, and the console screen displays a system banner similar to the following:

Enter <CTRL D> to stop Operating System auto-boot: ..... 1

Uncompressing Operating System kernel image file... .................................done Starting kernel .......... RAMDISK: gzip compressed image found at block 0 Thu Apr 8 12:36:52 2004 Bootloader Image File Version : 0.0.12 Ramdisk Image File Version : 1.3.0 Ramdisk Build Date : Thu Apr 1 14:09:19 CST 2004 Kernel Image File Version : 0.2.10 Initializing system ..............................done Starting automatic software upgrade ...Available software upgrade does not differ from previous upgrade ...No action taken



% Shell v1.3.0 uMG9820>

Step 5 If the system completes all the above steps successfully, proceed to Configuration Tasks, for initial software configuration procedures.

Step 6 If the system does not complete each of the steps in the startup procedure, proceed to "Troubleshooting," for troubleshooting recommendations and procedures.


Configuration Tasks

This section presents the following:

Command Syntax

Configuring Passwords

Configuring GE Ports

Configuring Management Ports

Configuring the Transport Stream

Configuring and Monitoring QAM Service

Upgrading Software

Managing Configurations

Using the Terminal (Console) Port

Command Syntax

General syntax and the basic provisioning areas are discussed below:

Syntax Overview

Ethernet Interfaces

QAM Ports

ASI Interface

Console Port Interface

Syntax Overview

Commands use the following general syntax, where variables are in italics and command names and keywords are in bold:

Hostname(mode)# [no] keyword {keyword1 argument1 | keyword2 argument2 | ...} [keyword1 argument1 | keyword2 argument2 | ...], where Hostname and mode are variables, as follows:

Hostname—Is the user-settable name for the unit. In this document, uMG9820 is used in all examples.

(mode)#— Describes the current provisioning mode, such as the following:

uMG9820#—Indicates enable mode

uMG9820(config)#—Indicates configuration mode

uMG9820(config-if)#—Interface mode

uMG9820(config-subif)#—Subinterface mode

no—Some commands have an option to remove the previous configuration using the no prefix. In most cases this restores default settings.

keyword— Describes each command, as in the following examples:

gigabitethernet and fastethernet—Configures the Ethernet ports

qam—Configures the RF QAM port

show—Retrieves configuration data and statistics

video—Defines video-related parameters

Ethernet Interfaces

Ethernet interfaces are addressed as follows:

slot/port

where slot is always zero (0) for Ethernet interface ports. The keywords for Ethernet interface ports are as follows:

gigabitethernet—Gigabit Ethernet port

fastethernet—Fast Ethernet

QAM Ports

The QAM ports are addressed by means of subinterface notation, as follows:

slot/port.qam

with the variables defined below:

slot addresses slots from 1 through 6

port addresses the output ports 1 or 2, counting from left to right (looking at the rear of the unit)

qam addresses the QAM channels 1 or 2, within each port

ASI Interface

The ASI output interface is configured by means of the keyword asi.


Note This port is not functional in initial releases of this product. It is intended for future use.


Console Port Interface

The RS-232 console port is configured by means of the terminal command in configuration mode.

Configuring Passwords

This section covers commands for the following operations:

Enabling and Disabling Passwords for Configuration Mode

Configuring a Telnet Password

Enabling and Disabling Passwords for Configuration Mode

To specify and enable or disable the configuration mode password:

uMG9820(config)# [no] enable password password

where

password = Text string for the password

Example—Set password for entering terminal configuration mode to "cisco":

uMG9820(config)# enable password cisco

Example—Disable password requirement for entering terminal configuration mode:

uMG9820(config)# no enable password

Configuring a Telnet Password

To specify and enable or reset the system Telnet password:

uMG9820(config)# [no] line vty password password

where

password = Text string for the password


Note The default Telnet password is cisco.


Example—Set the password for entering configuration mode when using Telnet to "cisco":

uMG9820(config)# line vty password cisco

Example—Set the password for entering configuration mode when using Telnet to the default value:

uMG9820(config)# no line vty password


Note There are no other line vty commands for the Cisco uMG9820.


Configuring GE Ports

This section covers commands for the following operations on the ports labeled GIG1 and GIG2:

Enabling and Disabling a GE Port

Setting GE Port IP Address and Subnet Mask

Setting GE Port MAC Address

Providing Redundancy for Failover

Retrieving GE Statistics

Retrieving GE Port Status

Enabling and Disabling a GE Port

To enable and disable a GE port:

uMG9820(config-if)# [no] shut

Example—Enable GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no shut

Example—Switch active GE port from 1 to 2:


Note To enable GE port 2, first disable GE port 1 (GIG1), then enable GE port 2 (GIG2).


uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# shut uMG9820(config-if)# exit uMG9820(config)# interface gigabitethernet 0/2 uMG9820(config-if)# no shut

Note Only one GE port can be active at a time. If no shut is applied to GE port 1 and GE 2 is active, shut is applied automatically to GE 2. See Providing Redundancy for Failover. However, both GE ports can be inactive at the same time.


Setting GE Port IP Address and Subnet Mask

To set the IP address and subnet mask for a GE port:

uMG9820(config-if)# ip address IP address subnet mask

where

IP address = Text string for standard IP address

subnet mask = Text string for standard subnet mask

Example—Set IP address to 192.168.0.10 and subnet mask to 255.255.255.0 for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# ip address 192.168.0.10 255.255.255.0

Note The IP address and subnet mask applied to one GE port is automatically applied to both GE ports. See Providing Redundancy for Failover.


Setting GE Port MAC Address

To set the IP address for a GE port:

uMG9820(config-if)# mac-address MAC address

where

MAC address = Text string for standard MAC address in H.H.H format

Example—Set the MAC address to 0000.0123.5678 for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# mac-address 0000.0123.5678

Note The MAC address applied to one GE port is automatically applied to both GE ports. See Providing Redundancy for Failover, below.


Providing Redundancy for Failover

Both GE ports share the same IP and MAC addresses. This facilitates failover in scenarios requiring 1+1 redundancy. To provide for failover between a VoD server and the Cisco uMG9820, you need to split the VoD content stream into two identical streams and feed each stream to a GE port.

Retrieving GE Statistics

To display packet and buffer statistics for the specified GE port:

uMG9820# show interface gigabitethernet slot/port

where

slot = 0

port = 1 or 2

Example—Show the SFP module and hardware data for GE port 1:

uMG9820# show interface gigabitethernet 0/1

GigabitEthernet 0/1 is up, line state is cable not installed. Hardware is Gigabit Ethernet Port, address is 0050.c206.e2c3 IP address is 192.168.145.93 Full-duplex, 1000Mb/s 0 packets input, 0 bytes Received 0 broadcasts (0 multicast) 0 runts, 0 giants 0 input errors, 0 CRC, 0 overrun 0 packets output, 0 bytes 0 output errors

Retrieving GE Port Status

To display the status of the specified GE port:

Link status (up or down)

Packet and buffer counters

uMG9820# show ip interface [brief] gigabitethernet slot/port

where

brief = Optional keyword to display link status only

slot = 0

port = 1 or 2

Example—Show the status of GE port 1:

uMG9820# show ip interface gigabitethernet 0/1

GigabitEthernet 0/1 is down, line state is no module installed. Inbound access list is not set

Example—Show only the link status of GE port 1:

uMG9820# show ip interface brief gigabitethernet 0/1

Interface IP-address OK Method Status Protocol GigabitEthernet0/1 192.168.1.34 NO Manual Up Down

To see the status of all Ethernet ports, use the following command:

Example—Show the status of all Ethernet ports:

uMG9820# show ip interface

FastEthernet 0/1 is Up Internet address is 192.168.145.130, subnet mask is 255.255.255.0 Broadcast address of 192.168.145.255 is valid MTU is 1500 bytes, Metric is 1 FastEthernet 0/2 is Up Internet address is 64.13.20.160, subnet mask is 64.13.20.160 Broadcast address of 64.13.20.160 is valid MTU is 1500 bytes, Metric is 1 GigabitEthernet 0/1 is up, line state is cable not installed. Inbound access list is not set GigabitEthernet 0/2 is down, line state is no module installed. Inbound access list is not set

Example—Show only the link status of all Ethernet ports:

uMG9820# show ip interface brief

Interface IP-address OK Method Status Protocol FastEthernet0/1 192.168.145.130 YES DHCP Up Up FastEthernet0/2 64.13.20.160 YES DHCP Up Down GigabitEthernet0/1 192.168.1.34 NO Manual Up Down GigabitEthernet0/2 0.0.0.0 NO Manual Administratively Down Down

Note To clear counters, use the clear counters command in terminal configuration mode, as follows:

uMG9820(config)# clear counters


Using GE Session Commands

This section covers commands for the following operations:

Setting the UDP Port Assignment

Setting Session Timeouts

Setting Maximum Network Jitter

Setting PID Remapping

Binding a UDP Port to a VoD Server

Retrieving Input Session Data

Retrieving Input Session PSI Data

Setting the UDP Port Assignment

There are two ways to set the UDP port assignment:

Default Method

User-Defined Method


Tip See also the provisioning information provided in Special Issues: UDP.


Default Method

The UDP port is a 16-bit number of the form QQQQQQQQ PPPPPPPP, with a valid range of 0x0100 through 0x18FF, where the bytes are defined as follows:

Program 0 (0x00) is always reserved for the Network Information Table (NIT), when one is to be used. The NIT is optional.

QQQQQQQQ = QAM channel (0x01 through 0x18).

PPPPPPPP = Assigned program number (0x01 through FF).


Note A maximum of 16 programs can be active on any single QAM channel at any time, provided the aggregate bit rate of all the programs does not exceed (1) 38.81070 Mbps for 256QAM, or (2) 26.97035 Mbps for 64QAM. (64QAM is not available in initial releases.)


Table 4-1 shows the mappings between the QAM subinterfaces and channels and the UDP ports. All port ranges for each channel are from 1 through 255 (00000001-11111111). Program 0 is represented by numbers such as 256, 512, 768, ... 6144.

Table 4-1 Mapping QAM Subinterfaces and Channels to UDP Ports 

QAM Subinterface
(slot/port.qam)
QAM
Channel
UDP Port Range

1/1.1

1

257-511

1/1.2

2

513-767

1/2.1

3

769-1023

1/2.2

4

1025-1279

2/1.1

5

1281-1535

2/1.2

6

1537-1791

2/2.1

7

1793-2047

2/2.2

8

2049-2303

3/1.1

9

2305-2559

3/1.2

10

2561-2815

3/2.1

11

2817-3071

3/2.2

12

3073-3327

4/1.1

13

3329-3583

4/1.2

14

3585-3839

4/2.1

15

3841-4095

4/2.2

16

4097-4351

5/1.1

17

4353-4607

5/1.2

18

4609-4863

5/2.1

19

4865-5119

5/2.2

20

5121-5375

6/1.1

21

5377-5631

6/1.2

22

5633-5887

6/2.1

23

5889-6143

6/2.2

24

6145-6399


User-Defined Method

You can override the default UDP port mapping for individual QAM channels by specifying the starting UDP port, the increment (sequential or even), and the total number of ports to map. For example, if the starting UDP port is 0x4000, the increment is even, the total number of ports to map is 0x9, and QAM channel 1 is targeted, then UDP ports 0x4000, 0x4002, 0x4004, 0x4006, 0x4008, 0x400A, 0x400C, 0x400E, and 0x4010 are mapped to QAM channel 1.

uMG9820(config-subif)# [no] video udp UDP-port-number {program program-number
[use {even| sequential} count]}

where

UDP-port-number = UDP port number of the desired incoming session to be mapped

If a range is being defined, this number acts as the initial value in the series. Subsequent values are incremented according to either an even or a sequential numbering scheme, as specified by the user.

program-number = Output program number that the sessions are mapped to

If a range is being defined, this number also acts as the initial value in the series. Subsequent values are incremented according to the same numbering sequence as the UDP port number (even or sequential).

use {even | sequential} = Type of sequence to be used for UDP port and program numbering

use even = increment value by two; use sequential = increment value by one

count = Number of UDP ports to be mapped to this QAM channel

Example—Map incoming session on UDP port 5201 to program 10 on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video udp 5201 program 10

Example—Map incoming sessions on UDP ports 8201, 8203, 8205, and 8207 to program numbers 2, 4, 6, and 8, respectively, on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video udp 8201 program 2 use even 4

Example—Remove mapping of UDP ports 8201 to program number 2 on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# no video udp 8201 program 2

Example—Revert all mapping of UDP ports on slot 1, port 1, QAM channel 2 to default mapping behavior:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# no video udp

Special Issues: UDP

Note the following special issues related to UDP:

1. Each MPEG SPTS is encapsulated in UDP datagrams and is assigned a Destination UDP port number by the VoD server.

2. Each UDP datagram can contain a maximum of seven 188-byte MPEG packets. Because only one destination UDP port can be defined for each UDP datagram, all of the MPEG packets contained in a UDP datagram must come from the same program.

3. A maximum of 256 SPTSs, programs, sessions, or UDP port sessions can be sent to the Cisco uMG9820 at a time. The 257th is dropped.

4. The terms "program" and "UDP port session" are used synonymously, because each program (movie) can be uniquely identified by its destination UDP port while it is active. The term "session" is also sometimes used. A UDP port can be mapped to only one QAM channel at any time (For example, if UDP port 5201 is currently mapped to QAM channel 1 and at some point the user maps UDP port 5201 to QAM channel 2, then the mapping between UDP port 5201 and QAM channel 1 is removed automatically.

5. Within the Cisco uMG9820, a user can map any number of UDP port numbers to a QAM channel. Each UDP port mapped to a QAM channel occupies a program space when active. A maximum of 16 programs (or program spaces) can be active on any single QAM channel at any time, provided the aggregate bit rate of all the programs does not exceed 38.81070 Mbps using 256QAM or 26.97035 Mbps using 64QAM (if available). These information rates are dictated by the ITU J.83 Annex B standard.

The implication of this is that QAM channel loading is entirely the responsibility of the end user to manage. Suppose the following:

A user maps more than 16 UDP ports to a QAM channel.

The SPTS for each UDP port is a 3.75-Mbps movie when active.

256QAM is being used.

If an 11th SPTS/UDP port session is requested on that QAM channel, and its addition exceeds the total bandwidth (38.81071 Mbps), then all programs in that channel will be randomly corrupted (their packets dropped) until the bandwidth is reduced by (a) removing a session, or (b) reducing the bandwidth required by one or more sessions.

In summary, the user is responsible for bandwidth management. Although the user can request up to 16 sessions per QAM channel, the total bandwidth for the channel cannot be exceeded. Otherwise, MPEG packets will be randomly dropped from all the sessions on that block. For example, a user can put 16 low-bandwidth (< 2.4 Mbps) sessions on one 256QAM channel, with no problem. However, if the user puts three HDTV (15 Mbps x 3 = 45 Mbps) sessions on that channel all three programs will be randomly corrupted.

6. When default UDP port mapping is used, the range of valid program numbers is restricted to 1 to 255 because only the low-order byte is used to assign the program number. The implication of this is that the user will never see a program number outside the range of 1 to 255 when using default UDP port mapping.

Setting Session Timeouts

To set session timeouts for the GE ports:

uMG9820(config-if)# [no] video timeout {inactive inactive-time | release release-time | queue deallocation-time}

where

inactive-time = Mark sessions as "inactive" if they have not received an IP packet for inactive-time in milliseconds

The default value for inactive-time is the maximum network jitter value (set by user; see Setting Maximum Network Jitter) plus 100 milliseconds.

release-time = Remove system resources and outgoing PSI program references for sessions that have gone to an "inactive" state after release-time in seconds

The default value for release-time is 5 seconds.

deallocation-time = Deallocate system resources for sessions that have gone to an "inactive" state for deallocation-time in seconds

The default value for deallocation-time is 5 minutes.

Example—Set inactive time to 500 milliseconds for all sessions on GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# video timeout inactive 500

Example—Set release time to 10 seconds for all sessions on GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# video timeout release 10

Example—Set deallocation time for the queue to 4 minutes for all sessions on GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# video timeout queue 240

Example—Set inactive time to default value for all sessions on GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no video timeout inactive

Example—Set release time to default value for all sessions on GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no video timeout release

Setting Maximum Network Jitter

To set the maximum allowable network jitter (packet latency) for the specified UDP port session:


Note This setting is not supported in initial releases. It affects the session's overall latency within the unit.


uMG9820(config-if)# [no] video udp UDP-port-number jitter jitter-value

where

UDP-port-number = UDP port number of the desired incoming session for which the maximum network jitter is to be set.

jitter-value = Maximum network jitter value in milliseconds. The jitter value may be set in the range of 10 to 250 milliseconds.

The default jitter-value is 100 milliseconds.

Example—Set maximum network jitter value for UDP port 5201 to 250 milliseconds for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# video udp 5201 jitter 250

Example—Set maximum network jitter value for UDP port 5201 to default value for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no video udp 5201 jitter

Setting PID Remapping

To remap or drop PIDs within an incoming UDP port session:

uMG9820(config-if)# [no] video UDP UDP-port-number in PID-number {out PID-number | drop}

where

UDP-port-number = UDP port number of the desired incoming session that contains the PID to be remapped

in PID-number = PID number to be remapped or dropped

out PID-number = New PID number (in decimal) in the outgoing program

Example—Remap incoming PID 1000 on UDP port 5201 to PID 1001 for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# video udp 5201 in 1000 out 1001

Example—Drop incoming PID 1000 on UDP port 5201 for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if])# video udp 5201 in 1000 drop

Example—Handle PIDs on UDP port 5201 in default manner for GE port 1:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no video udp 5201

Binding a UDP Port to a VoD Server

Where multiple VoD servers are used, it is possible for video session streams to collide on the same UDP port of the Cisco uMG9820. This can be prevented by using source address filtering (on the addresses of the VoD servers) to prevent collisions. The user is responsible for ensuring that only one VoD server in a multiserver installation is actually streaming video to a given UDP port at any time.


Note In initial releases, only one IP address can be assigned to a given UDP port.


Use the command allow in interface configuration mode, as illustrated below.

To bind a UDP port to a VoD server:

uMG9820(config-if)# [no] allow udp UDP-port-number IP-address

Example—Binding UDP Port 6600 to VoD Server Address 172.16.0.6:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# allow udp 6600 172.16.0.6

Example—Unbinding UDP Port 6600 from VoD Server Address 172.16.0.6:

uMG9820# configure terminal uMG9820(config)# interface gigabitethernet 0/1 uMG9820(config-if)# no allow udp 6600 172.16.0.6

Retrieving Input Session Data

To list all the session information, input errors, session state, and continuity count errors:

uMG9820# show interface gigabitethernet slot/port video [session UDP-port-number]

where

slot = 0

port = 1 or 2

UDP-port-number = Number of specific UDP port (optional)

If a specific session UDP port number is provided, then only information on that session is provided. The following information is provided in the response:

User-defined session parameters

Session status (inactive, active, invalid Program Specific Information)

Jitter buffer status (underflow and overflow count) and average fullness

Continuity count errors

Example—Display all active video sessions on GE port 1:

uMG9820# show interface gigabitethernet 0/1 video

Number of active sessions 0 Source Continuity Error Counter 0

Example—Display video session information for UDP port 257 on GE port 1:

uMG9820# show interface gigabitethernet 0/1 video session 257

Current State : Active UDP port number : 257 Output QAM number : 0 Max Jitter Value : 0 Jitter Overflow : 0 Jitter Underflow : 0 Average Fullness : 0 Continuity Errors : 0

Note To clear counters, use the clear counters command in terminal configuration mode, as follows:

uMG9820(config)# clear counters


Retrieving Input Session PSI Data

To list all the Program Specific Information (PSI), such as program number, elementary stream ID and PIDs, for a video session:

uMG9820# show interface gigabitethernet slot/port video psi [session UDP-port-number]

where

slot = 0

port = 1 or 2

UDP-port-number = Number of specific UDP port (optional)

If a specific session UDP port number is provided, then only information on that session is provided.

Example—Display PSI information for all active video sessions on GE port 1:

uMG9820# show interface gigabitethernet 0/1 video psi

Inactive PSI Timeout is 0 seconds. Active PSI Timeout is 5 seconds. Queued PSI Timeout is 300 seconds.

Example—Display PSI information for UDP port 5401 on GE port 1:

uMG9820# show interface gigabitethernet 0/1 video psi session 5401

Number of PIDs : 3 Program Number : 1 Input PMT PID : 501 Output PMT PID : 32 Input PID (Type 81) : 273 Output PID : 33 Input PID (Type 3) : 274 Output PID : 34 Input PID (Type 2) : 272 Output PID : 35

Configuring Management Ports

The management and CAS ports are addressed using the CLI as Fast Ethernet (FE) ports 1 and 2, respectively. This section covers commands for the following operations:

Enabling and Disabling an FE Port

Setting an FE Port IP Address

Setting an FE Port MAC Address

Setting an FE Port in DHCP Mode

Setting the Default Gateway

Setting Boot Mode

Retrieving FE Port Statistics

Enabling and Disabling an FE Port

To enable and disable an FE port:

uMG9820(config-if)# [no] shut

Changes to an FE port's state take effect immediately.


Note In the initial release of this product, only FE port 1 is implemented.


Example—Enable FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-fastethernet[0/1])# no shut

Example—Disable FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# shut

Setting an FE Port IP Address

To set the IP address and subnet mask of an FE port:

uMG9820(config-if)# ip address IP-address subnet-mask

where

IP-address = Text string for standard IP address

subnet-mask = Text string for standard subnet mask

Changes to an FE port's IP address take effect immediately.

Example—Set the IP address to 192.168.0.10 and subnet mask to 255.255.255.0 for FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# ip address 192.168.0.10 255.255.255.0

Setting an FE Port MAC Address

To set the MAC address for an FE port:

uMG9820(config-if)# mac-address MAC-address

where

MAC-address = Text string for a standard MAC address in H.H.H form

Changes to an FE port's MAC address take effect following a reload only if the change is first written to the startup configuration. See Managing Configurations.

Example—Set the MAC address to 0000.0123.5678 for FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# mac-address 0000.0123.5678

Setting an FE Port in DHCP Mode

To instruct the FE port to obtain its IP address information from a Dynamic Host Configuration Protocol (DHCP) server:

uMG9820(config-if)# [no] dhcp

Changes to DHCP mode are immediate. When DHCP is disabled, the IP address reverts to the manually specified value.

Example—Enable DHCP mode for FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# dhcp

Example—Disable DHCP mode for FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# no dhcp

Setting the Default Gateway

To set the IP address of the default gateway for FE ports:

uMG9820(config-fastethernet[slot/port])# ip default-gateway IP-address

where

IP-address = Text string for a standard IP address

Example—Set the default gateway address to 192.168.0.1 for FE port 1:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# ip default-gateway 192.168.0.1

Setting Boot Mode

By default, the system boots from internally stored images. However, it is possible to specify the location of the system and kernel images on a remote file system and enable/disable BootP (bootstrap protocol) mode. These files are obtained over an FE management port.

To enable BootP mode, images, and paths:

uMG9820(config-fastethernet[0/1])# [no] boot {system path | kernel path}

where

system path = Remote-system file path for the system image

kernel path = Remote-system file path for the kernel image

Example—Enable BootP mode:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# boot

Example—Set BootP system path to "ramdisk_img.gz":

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# boot system ramdisk_img.gz

Example—Set BootP kernel path to "zImage":

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# boot kernel zImage

Example—Disable BootP mode:

uMG9820# configure terminal uMG9820(config)# interface fastethernet 0/1 uMG9820(config-if)# no boot

Retrieving FE Port Statistics

To retrieve packet and buffer statistics for an FE port:

uMG9820# show interface fastethernet slot/port

where

slot = 0

port = 1 or 2

Example—Show packet and buffer statistics for FE port 1:

uMG9820# show interface fastethernet 0/1

FastEthernet0/1 Link Encapsulation:Ethernet HW Address 0050.c206.c299 IP Address:192.168.145.130 Broadcast:192.168.145.255 Netmask:255.255.255.0 RX Packets:88 Errors:0 Dropped:0 Overruns:0 Frame:0 TX Packets:6 Errors:0 Dropped:0 Overruns:0 Carrier:0 Collisions:0 TX Queue Length:100 RX bytes:11406 (11.1 kb) TX bytes:913 (913.0 b) Interrupt:14 Gateway:192.168.145.1 DHCP:Enabled BootP:Disabled

Retrieving FE Port Status

To retrieve the status of an FE port:

uMG9820# show ip interface [brief] fastethernet slot/port

where

brief = Optional keyword to display link status only

slot = 0

port = 1 or 2

You can retrieve the following IP statistics for the specified FE port:

Link status (up or down)

Packet and buffer counters

Example—Show the status of FE port 1:

uMG9820# show ip interface fastethernet 0/1

FastEthernet 0/1 is Up Internet address is 192.168.145.130, subnet mask is 255.255.255.0 Broadcast address of 192.168.145.255 is valid MTU is 1500 bytes, Metric is 1

Example—Show only the link status of FE port 1:

uMG9820# show ip interface brief fastethernet 0/1

Interface IP-address OK Method Status Protocol FastEthernet0/1 192.168.145.130 YES DHCP Up Up

Tip You can also use show ip interface and show ip interface brief to see the status of all Ethernet ports, as in Retrieving GE Port Status.



Note To clear counters, use the clear counters command in terminal configuration mode as follows:

uMG9820(config)# clear counters


Configuring the Transport Stream

MPEG-2 Program Specific Information (PSI) uses a variety of messages to inform the MPEG receiver about the content of the program stream, and about the streams that are available within the network.

These commands are applied in subinterface mode to an individual QAM channel,

where

slot = 0, 1, 2, 3, 4, 5, or 6

port = 1 or 2

qam = 1 or 2

Table 4-2 lists the MPEG messages and message components that are addressed by the CLI.

Table 4-2 MPEG Messages and Message Components Addressed by the CLI 

Message
Description

PAT (Program Association Table)

The first message the receiver attempts to acquire from an MPEG stream. The PAT contains a list of the programs in the stream, as well as a pointer to the PMT for each (see below). It also includes the transport stream ID, or TSID. (See Table 4-3.)

PMT (Program Map Table)

A message that describes the elements of a program. Each program has its own PMT. Once a receiver has acquired a PMT message, it has the information needed to find different elements (for example, video and audio) for that program within the stream.

NIT (Network Information Table)

A list of all of the transport streams within the network, along with their associated RF frequencies. The NIT is identified by means of a network-shared NIT ID (NIT PID). This allows the receiver to know what streams are available. (NIT messages are not always present.)


Table 4-3 shows the default TSID assignment for each QAM channel (subinterface).

Table 4-3 Default TSID Assignment for each QAM Subinterfaces 

QAM Subinterface
(slot/port.qam)
Default TSID
(Decimal)
Default TSID
(Hexadecimal)

1/1.1

111

0x006F

1/1.2

112

0x0070

1/2.1

121

0x0079

1/2.2

122

0x007A

2/1.1

211

0x00D3

2/1.2

212

0x00D4

2/2.1

221

0x00DD

2/2.2

222

0x00DE

3/1.1

311

0x0137

3/1.2

312

0x0138

3/2.1

321

0x0141

3/2.2

322

0x0142

4/1.1

411

0x019B

4/1.2

412

0x019C

4/2.1

421

0x01A5

4/2.2

422

0x01A6

5/1.1

511

0x01FF

5/1.2

512

0x0200

5/2.1

521

0x0209

5/2.2

522

0x020A

6/1.1

611

0x0263

6/1.2

612

0x0264

6/2.1

621

0x026D

6/2.2

622

0x026E


This section covers commands for the following operations:

Setting PAT Message Parameters

Setting PMT Message Interval

Setting PAT Message Parameters

To set the message field parameters for the outgoing PAT message:

uMG9820(config-subif)# [no] video pat {interval time | tsid tsid | nit-pid pid}

where

time = maximum interval, in milliseconds, between PAT messages

The default value for time is 100 milliseconds.

tsid = Transport stream ID for the output going PAT message. The default value must be unique for each transport stream.

pid = Reference to the NIT PID value in program zero of the PAT message.

The default is to have no reference program zero (program0, which is the NIT PID) in the PAT message.

Example—Set maximum PAT interval to 500 milliseconds on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video pat interval 500

Example—Set the TSID field of the PAT message to 2250 on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video pat tsid 2250

Example—Include program 0 with a reference to PID 4090 in the PAT on slot 1, port 1, QAM channel 2

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video pat nit-pid 4090

Example—Remove program 0 from the PAT message on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# no video pat nit-pid

Setting PMT Message Interval

To set the maximum PMT message interval:

uMG9820(config-subif)# [no] video pmt interval time

where

time = Maximum interval, in milliseconds, between PMT messages

The default value for time is 100 milliseconds.

Example—Set maximum PMT interval to 500 milliseconds on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video pmt interval 500

Configuring and Monitoring QAM Service

This section covers commands for the following operations:

Enabling and Disabling a QAM Channel

Setting QAM Modulation

Setting QAM Frequency

Setting QAM Output Power

Retrieving QAM Statistics

Retrieving QAM Output Video Data

These commands are applied in subinterface mode to an individual QAM channel,

where

slot = 1, 2, 3, 4, 5, or 6

port = 1 or 2

qam = 1 or 2

Enabling and Disabling a QAM Channel

To enable or disable (mute) a QAM channel:

uMG9820(config-subif)# [no] shut

Note The default state for all QAM channels is shut. This prevents interference with existing cable-channel configurations.


Example—Enable QAM output on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# no shut

Example—Disable QAM output on slot 1, port 1, QAM channel 2:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# shut

Setting QAM Modulation

To set the modulation rate for all QAM outputs on the selected QAM card:

uMG9820(config-subif)# [no] video format type

where

type = Modulation scheme. Values are either 64QAM or 256QAM.

The default value for type is 256QAM.


Note The modulation for both channels for a port is set when either channel 1 or channel 2 is addressed. (64QAM is not available in initial releases.)


Example—Set the modulation rate for all QAM outputs on slot 1, port 1, QAM channel 2 to 256QAM:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# video format 256QAM

Example—Set the modulation rate for all QAM outputs on slot 1, port 1, QAM channel 2 to default value:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.2 uMG9820(config-subif)# no video format

Setting QAM Frequency

Figure 4-1 illustrates the QAM channel 1 and channel 2 frequencies in relation to the center frequency.

Figure 4-1 QAM Channel Frequencies

To set the center frequency of the selected QAM channel:

uMG9820(config-subif)# video frequency frequency

where

frequency = QAM channel center frequency in Hz, from 225000000 to 900000000.


Note The frequency for both channels for a port is set when either channel 1 or channel 2 is addressed, and is determined by the center frequency.



Caution Do not set the two 6-MHz QAM channels within a 12-MHz-wide RF channel to the same center frequency. See Special Issues: Selecting QAM Frequencies to Avoid Overlap.

Example—Set the center frequency of slot 1, port 1, QAM channel 1 to 850 MHz:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.1 uMG9820(config-subif)# video frequency 850000000

Note In this example, the center frequency of QAM 1/1.2 is automatically adjusted to 856000000 Hz.


Special Issues: Selecting QAM Frequencies to Avoid Overlap

The frequencies on an RF chain (or block: the circuitry providing the maximum bandwidth of a QAM port—from 3 MHz below the bottom center frequency to 3 MHz above the top center frequency) must not overlap those of the other port on the same QAM card. (For this discussion, the two ports on the same card are referred to as adjacent ports.) The settings of the QAM frequencies (center frequencies) on each channel determine the upper and lower bounds of the RF chain.


Note To maximize reliability and isolation, each RF chain on a given QAM card is a separate circuit, with its own local oscillator (LO). However, if frequencies on both RF chains on a card are set too closely to each other, they can be amplified by the LOs on the adjacent chain—resulting in spurious products. The rules presented in this section ensure the necessary signal isolation.


Note the following rules for selecting QAM frequencies (center frequencies):

1. The two 6-MHz QAM channels within a 12-MHz-wide RF chain cannot be set to the same center frequency. The center frequency of the QAM channel on slot/port.1 is always 6 MHz lower than the center frequency of the QAM channel on slot/port.2.

2. The two 12-MHz-wide RF chains on any QAM card (one chain from port 1 and the other from port 2) must not overlap. The center frequencies for the 6-MHz QAM channels on slot/1.1 and slot/1.2 must be different from the center frequencies for the 6-MHz QAM channels on slot/2.1 and slot/2.2.


Caution The center frequencies of each of the two 12-MHz RF chains must be at least 12 MHz apart.

3. As long as rule 2 is strictly adhered to on each QAM card, it is valid to set up more than one QAM card in a Cisco uMG9820 chassis with the same frequency assignments.

Table 4-4 lists both invalid (examples 1 and 2) and valid (examples 3 and 4) QAM center frequency schemes. For an explanation of each example, see the Notes following the table.


Note These frequency assignments are for illustration only.


Where the assignments are invalid, it is because the RF chains on the ports on the same card overlap completely or partially.

Where the assignments are valid, the same frequencies can be assigned to more than one QAM card in a chassis—as long as the above rules are not violated on those cards.

Table 4-4 Sample Invalid and Valid QAM Center Frequency Schemes 

Invalid
Valid
Example
Port
Chain Range, MHz
Channel
Center Frequency
Example
Port
Chain Range, MHz
Channel
Center Frequency

1

1

347-359

slot/1.1

350

4

1

347-359

slot/1.1

350

slot/1.2

356

slot/1.2

356

2

slot/2.1

350

359-371

slot/2.1

362

slot/2.2

356

slot/2.2

368

2

1

347-359

slot/1.1

350

5

2

347-359

slot/1.1

350

slot/1.2

356

slot/1.2

356

2

353-365

slot/2.1

356

459-471

slot/2.1

462

slot/2.2

362

slot/2.2

468

3

1

839-851

slot/1.1

842

6

1

839-851

slot/1.1

842

slot/1.2

848

slot/1.2

848

2

851-863

slot/2.1

854

2

853-865

slot/2.1

856

slot/2.2

860

slot/2.2

862


Notes

Example 1 (Invalid): RF chains on adjacent ports overlap completely.

Example 2 (Invalid): RF chains on adjacent ports overlap partially.

Example 3 (Invalid): RF chains on adjacent ports overlap (the top frequency of one chain is the same as that on the bottom of the chain on the adjacent port).

Example 4 (Valid): RF chains overlap, but are on the same port.

Example 5 (Valid): RF chains do not overlap, and are on the same port.

Example 6 (Valid): RF chains do not overlap, and are on different adjacent ports.

Setting QAM Output Power

To set the combined output power level for a QAM port:

uMG9820(config-subif)# video power power

where

power = QAM power assignment in dBmV. The value can be from 50 to 60, in one-unit increments.

Example—Set the output power level of slot 1, port 1, QAM channel 1 to 50 dBmV:

uMG9820# configure terminal uMG9820(config)# interface qam 1/1.1 uMG9820(config-subif)# video power 50

Note The output power for both channels for a port is set when either channel 1 or channel 2 is addressed.


Retrieving QAM Statistics

To display QAM statistics for a specified QAM channel:

uMG9820# show interface qam slot/port.qam

where

slot = 1, 2, 3, 4, 5, or 6

port = 1 or 2

qam = 1 or 2

Example—Show QAM statistics for slot 1, port 1, QAM channel 1:

uMG9820# show interface qam 1/1.1

Output Frequency : 249000000 Hz Output RF Power Level : 46.0 dBmV Output RF Attenuation : 19.6 dB Port Enable : Enabled Channel Enable : Enabled QAM Mode : 256 Encode State : Annex B Interleaver Depth : 128,1 Bytes per packet : 188 Gain Compensation : Active RF block ALC setting : Enabled RF block ALC power : 46.0 dBmV Temperature : 46.0C +/- 3C Alarm Codes :

Retrieving QAM Output Video Data

To display video program data for a specified QAM channel:

uMG9820# show interface qam slot/port.qam video

where

slot = 1, 2, 3, 4, 5 or 6

port = 1 or 2

qam = 1 or 2

The following information is retrieved:

Transport stream ID (TSID) and NIT PID

PAT and PMT interval

Bitrate through this QAM

PSI data for each program

Example—Show video program data for slot 1, port 1, QAM channel 1:

uMG9820# show interface qam 1/1.1 video

TSID: 111 NIT-PID: 0 PAT Interval: 100 PMT Interval: 100 Average Bitrate: 0 bps Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0 Program (INACTIVE): 0

Upgrading Software

This section covers commands for the following operation:

Initiating a Software Upgrade from a File Server

Initiating a Software Upgrade from a File Server

To configure and perform an upgrade from a remote server:

uMG9820# upgrade {server ip address | filename remote filename | now {force }}

where

server ip address = IP address of the server where the upgrade files are stored

remote filename = Name of the upgrade file stored on the remote system

now = Perform the software upgrade if the specified file has a higher version number than that of software currently installed

force = Perform the software upgrade to the specified file, regardless of software version

Example—Specify 192.168.3.7 as the IP address of the server where the upgrade software resides:

uMG9820# upgrade server 192.168.3.7

Example—Specify "newsoftware.tar" as the upgrade filename:

uMG9820# upgrade filename newsoftware.tar

Example—Upgrade to the new software immediately:

uMG9820# upgrade now

Example—Upgrade to the new software immediately, even if it is older than the currently installed version:

uMG9820# upgrade now force

Managing Configurations

This section covers commands for the following operations:

Saving a Running Configuration to the Startup Configuration

Restoring the Startup Configuration to the Running Configuration

Saving a Configuration to a TFTP Server

Retrieving a Configuration from a TFTP Server

Displaying Configuration Files

Saving a Running Configuration to the Startup Configuration

To save the current running-configuration settings to a storage location for the startup-configuration settings (except for the case where a BootP configuration is used):

uMG9820# copy running-config startup-config

where

running-config = Current running configuration settings (in RAM)

startup-config = Stored configuration settings that are loaded at startup

Example—Copy the running configuration settings to the startup configuration file:

uMG9820# copy running-config startup-config

Restoring the Startup Configuration to the Running Configuration

To load the stored startup-configuration settings to the running configuration settings (overwriting current running-configuration settings, and appending changes to the file):

uMG9820# copy startup-config running-config

where

running-config = current running-configuration settings

startup-config = stored configuration settings that are loaded at startup

Example—Copy the stored startup configuration settings to the running configuration:

uMG9820# copy startup-config running-config

Saving a Configuration to a TFTP Server

To save either the current running-configuration settings or the startup-configuration settings to a default or user-specified TFTP server:

uMG9820# copy {running-config | startup-config} tftp URL

where

running-config = current running-configuration settings

startup-config = stored configuration settings that are loaded at startup

URL = location of a specific filename on TFTP server if the default TFTP server is not used


Note Use TFTP, not FTP, to send and retrieve files between the Cisco uMG9820 and a server.


Example—Save the startup-configuration settings to the default TFTP server:

uMG9820# copy startup-config tftp

Example—Save the current running configuration settings to a file called "runcfgdate" on a TFTP server with IP address 192.168.2.45:

uMG9820# copy running-config tftp://192.168.2.45/tftpfiles/runcfgdate

Retrieving a Configuration from a TFTP Server

To restore either the current running-configuration settings or the startup-configuration settings from the default or user-specified TFTP server:

uMG9820# copy tftp URL {running-config | startup-config}

where

running-config = Current running-configuration settings

startup-config = Stored configuration settings that are loaded at startup

URL = location of a specific filename on a TFTP server if the default TFTP server is not used

Example—Restore the current running-configuration settings from the default TFTP server:

uMG9820# copy tftp running-config

Example—Restore the startup-configuration settings from the default TFTP server:

uMG9820# copy tftp startup-config

Example—Restore the current running-configuration settings from a file called "runcfgdate" on a TFTP server with IP address 192.168.2.45:

uMG9820# copy tftp://192.168.2.45/tftpfiles/runcfgdate running-config

Displaying Configuration Files

To display either the current running-configuration settings or the startup-configuration settings:

uMG9820# show {running-config | startup-config}

where

running-config = Current running-configuration settings

startup-config = Stored configuration settings that are loaded at startup

Example—Show the current running-configuration settings:

uMG9820# show running-config

Note For an example of output, see Sample Configuration.


Example—Show the startup-configuration settings:

uMG9820# show startup-config

Using the Terminal (Console) Port

The terminal or console port allows the CLI to be accessed through the RS-232 interface.


Note The RS-232 port parameters are fixed and cannot be edited. The parameters are as follows:

9600 bits per second, 8 data bits, no parity, 1 stop bit


Sample Configuration

The following example illustrates the results of the show running-config command on a Cisco uMG9820.

uMG9820#show run

upgrade server 192.168.145.10 upgrade filename umg9820-1_3_0-1.tar.gz hostname uMG9820 configure terminal no logging server snmp-server community private RW snmp-server host 192.168.142.73 traps version 1 private snmp-server host 192.168.142.73 private snmp-server community public RO snmp-server host 0.0.0.0 traps version 1 public snmp-server host 0.0.0.0 public interface fastethernet 0/1 no shut no boot debug no boot ip address 192.168.2.108 255.255.255.0 ip default-gateway 192.168.145.1 mac-address 0050.c206.c31d dhcp interface fastethernet 0/2 shut mac-address 0050.c206.c2a2 dhcp interface gigabitethernet 0/1 ip address 192.168.1.34 255.255.255.0 mac-address 0050.c206.c0aa no shut no negotiation auto no video timeout inactive no video timeout release no video timeout queue interface gigabitethernet 0/2 shut configure terminal no logging console no logging level terminal speed 9600 terminal parity none terminal databits 8 terminal stopbits 1 interface qam 6/1.1 video udp 5377 program 11 interface qam 1/1.1 no video pat tsid no video pat nit-pid video pmt interval 100 video pat interval 100 video format 256QAM video interleaver 128,4 video frequency 531000000 video power 60.4 no video mute no video alc no shut interface qam 1/1.2 no video pat tsid no video pat nit-pid no shut interface qam 1/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 59.4 no video mute no video alc no shut interface qam 1/2.2 no video pat tsid no video pat nit-pid no shut interface qam 2/1.1 no video pat tsid no video pat nit-pid video format 256QAM video interleaver 128,4 video frequency 531000000 video power 61.7 no video mute no video alc no shut interface qam 2/1.2 no video pat tsid no video pat nit-pid no shut interface qam 2/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 61.2 no video mute no video alc no shut interface qam 2/2.2 no video pat tsid no video pat nit-pid no shut interface qam 3/1.1 no video pat tsid no video pat nit-pid video format 256QAM video interleaver 128,4 video frequency 531000000 video power 58.0 no video mute video alc no shut interface qam 3/1.2 no video pat tsid no video pat nit-pid no shut interface qam 3/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 57.0 no video mute video alc no shut interface qam 3/2.2 no video pat tsid no video pat nit-pid no shut interface qam 4/1.1 no video pat tsid no video pat nit-pid video format 256QAM video interleaver 128,4 video frequency 531000000 video power 63.2 no video mute no video alc no shut interface qam 4/1.2 no video pat tsid no video pat nit-pid no shut interface qam 4/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 61.9 no video mute no video alc no shut interface qam 4/2.2 no video pat tsid no video pat nit-pid no shut interface qam 5/1.1 no video pat tsid no video pat nit-pid video format 256QAM video interleaver 128,4 video frequency 531000000 video power 61.1 no video mute no video alc no shut interface qam 5/1.2 no video pat tsid no video pat nit-pid no shut interface qam 5/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 61.1 no video mute no video alc no shut interface qam 5/2.2 no video pat tsid no video pat nit-pid no shut interface qam 6/1.1 no video pat tsid no video pat nit-pid video format 256QAM video interleaver 128,4 video frequency 531000000 video power 62.4 no video mute no video alc no shut interface qam 6/1.2 no video pat tsid no video pat nit-pid no shut interface qam 6/2.1 no video pat tsid no video pat nit-pid video frequency 255000000 video power 62.0 no video mute no video alc no shut interface qam 6/2.2 no video pat tsid no video pat nit-pid no shut uMG9820#

Using the Terminal (Console) Port

The terminal or console port allows the CLI to be accessed through the RS-232 interface.


Note The RS-232 port parameters are fixed and cannot be edited. The parameters are as follows:

9600 bits per second, 8 data bits, no parity, 1 stop bit




hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Oct 7 16:03:42 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.