2012/10/1

ZXUSS VS8000C Multimedia Server Troubleshooting

Version 1.0

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

2012/10/1

Boards of VS8000C
front
1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6

rear
7 8 9 10 11 12 13 14

M S T U

M S C U

M S T U

M S C U

M D U

M D U

M S U

M S U

S O M P

S O M P

E P G

M S T U

E P G

M S T U

R M S T U

R M S C U

R M S T U

R M S C U

R M D U

R M D U

R M S U

R M S U

R S O M P

R S O M P

R M S T U

R M S T U

R M S T U

R M S T U

MSTU+RMSTU MDU+RMDU MSCU+RMSCU MSU+RMSU SOMP+RSOMP EPG

Media Storage Transmit Unit Media Distribute Unit Media Service Control Unit Media Switch Unit System Operation Main Processor installed in MSTU

Common Log Paths of VS8000C

VS8000C background 129 logs are stored in C:/zxmsg/R06.

channel-side logs (M00*_*_CHANNEL.log) database-side logs (M00*_*_DBS.log).

PP logs of MSTUs are stored in /home. Streaming media logs of MSTUs are stored in /var/ZMSS. File system logs of MSTUs are stored in /var/ztefs.

2012/10/1

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

Method of Rectifying Common Channel Faults

The process of creating a channel is as follows:

On the service portal, issue a broadcast source file. On the service portal, create a channel. Create a channel in VS8000C. VS8000C submits the result to MLSS.

CAUTION: Only one channel can be created for an SDP broadcast source file.

2012/10/1

Common Channel Faults

Creating a Channel Fails and MLSS Parameter Error Is Displayed on the CDN
1. View the channel log in 129 background R06 to find Channel Code of the currently created channel. 2. In the channel log, find the causes of parameter errors during channel creation through Channel Code. 3. On the service portal, modify the parameters and create a channel again. If the error occurs again, repeat g g p step 2.

VS8000C Returns GETMDU Error Code

1. Note that the first 400 circuits of MDU are used for channel access. 2. Log in to the EMS and choose EMS Configuration Management > Data Management > Dynamic Data Management > Circuit Status Observation to view whether MDU resources are normal. 3. In the 3 I th EMS probe, view the R_CONTENT table. b i th R CONTENT t bl

2012/10/1

VS8000C Returns GETMDU Error Code

4. If the channel code stream access mode is unicast, choose EMS Configuration Management > Data Management > Logical Configuration > Unit and Correlative Attribute Configuration to check the IP and PORT in the SDP file.

VS8000C Returns GETMDU Error Code

2012/10/1

VS8000C Returns GETMDU Error Code

5. check whether the first 400 circuits of MDU media interfaces are configured to be in half-fixed circuit activated state state.

Common Channel Faults

Creating a Channel Fails and OPEN_MDU_FAIL Is Displayed on the CDN

Check whether an SDP file is used repeatedly. If the channel access mode is unicast, check whether the access MDU external-interface SLN in the SDP file is used repeatedly. If the channel access mode is multicast, check whether the access multicast address and IP address in the SDP file are used repeatedly.

2012/10/1

Common Channel Faults

Creating a Channel Fails and ErrCode_GETMSTU_FAIL Is Displayed on the CDN

1. Choose EMS Configuration Management > Data Management > Dynamic Data Management > Circuit Status Observation to view whether the MSTU resource is in normal status. 2. In the R_SUNIT table of the EMS probe, check whether the streaming media sub-unit of the MSTU is in normal status. 3. Check the DBS log in 129 background R06.

Common Channel Faults

Creating a Channel Fails and ErrCode_ADDCHANNELCONFIG_FAIL Is Displayed on th CDN Di l d the

1. Log in to the EMS and choose EMS Configuration Management > Data Management > Signaling Configuration > CDN Configuration to check whether channel and content configuration capacity are normal. 2. On the 129 background and view the *_DBS.log file on the primary OMP to find the cause of database channel addition error.

2012/10/1

Common Faults of the Content Delivery Module

Content Delivery Fails but VS8000C Does Not Receive Content Delivery Message
1. Check the status of the WINTCP link. 2. If the WINTCP link is in normal , check whether the node configuration of the CDN is correct. 3. View the content delivery log in the 129 background. Through Content ID, check whether the log contains the keyword "receive ftp down" and check whether the y p carried node ID and vcdn ID are consistent with those configured on the VS8000C.

Common Faults of the Content Delivery Module

Content Delivery Fails and the MSTU Submits Error Codes

1. In the content delivery log or EMS user data area, find the SLN resource occupied by content delivery. In the content delivery log of background 129, find the cause of the MSTU submitting error. 2. Open the PP log of the MSTU to view the cause of PP submitting error. In most cases, the error occurs due to internal return error of streaming media. In this case, view the streaming media log to locate the cause.

2012/10/1

Common Faults of the Content Delivery Module

Content Delivery Fails and Addition to the Database Fails

Log in to the EMS and choose Configuration Management > Data Configuration Management > Logical Resource Configuration to check the CDN(VCDN) value in the VS8000C node. Log in to the EMS and choose Configuration Management > Data Configuration Management > Logical Resource Configuration > Module Capacity Configuration to check the maximum system content capacity of module 1.

Common Faults of the Content Delivery Module

STB Program on Demand SETUP Fails and Wait Mlss Timeout Is Returned

If the DESCRIB message is successful, it indicates that the program on demand works properly. If SETUP fails, it indicates that there is no MSTU available. Then check the MSTU resources.

2012/10/1

Common Faults of the Content Delivery Module

Blank Screen Is Displayed During STB Broadcasting

1. Check whether the channel is in normal status. 2. If the channel is in normal status, capture the STB media packets . 3. Check whether the channel code stream is in normal status. 4. Check the MDU outgoing user data area

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

10

2012/10/1

Obtaining MSTU Resources Fails

The information CheckMstu: this mstu channelnum is full,Unit %d! indicates that channel access or carousel channel instead of temporary trans coding channel applies for an MSTU resource and the number of channels on this unit is already 50 (the channelnum field in the r_unitex table), so the unit cannot access any channel. View the streaming media sub-unit status of the unit. CheckMstu: this mstu ResType %d is not enough,Unit %d! %d! indicates checking whether this types of resources are all occupied in the R_MSTURES table. "CheckMstu: this mstu ResType %d ftpstore not enough,Unit %d!" indicates that content push-up and dropdown fail to apply for resources.

Obtaining MSTU Resources Fails

Get mstures err ,Sln not enough in unit %d ,slnnum %d! indicates that obtaining circuit resources fails. check mstures err ,rtpip not config in unit %d and sunit check rtpip %d ! indicates that the applied external interface resource is in abnormal status (including sub-unit status status != 0 r_sunitex.rtpip == 0 || r_sunitex.rtpip == 0xffffffff in the r_sunit table). The sub-unit is unavailable if one condition exists Check whether the unit has normal internal interface sub subunits (9, 10). The status == 0 field in the r_sunti table indicates that the status is normal.

11

2012/10/1

Resources Submitted by VS8000C Node Are Collected Inaccurately

1. In the EMS probe, view the r_moduleex table to check whether the modules queried are complete. 2. 2 In the r moduleex table of all modules check whether r_moduleex modules, Validstrm (idle resources) and busystrm (number of users) recorded in the module are correct. 3. On module 1, check whether Validstrm (idle resources) and Busystrm (number of users) recorded in each module are the same as the number of the corresponding modules (compared with the results queried in step 2) 2).

Resources Submitted by VS8000C Node Are Collected Inaccurately 4.On module 1, sum up all Validstrm (idle resources) and Busystrm (number of users) and then compare th them with th parameter values i th ith the t l in the 41000 message in Wintcp signaling tracing. 5. Check whether the MLSS version configured on the VS8000C is the same as the actual MLSS version.

12

2012/10/1

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

Terminal Displays WAIT CONFIG FROM FLR Repeatedly

Symptom:

After the MSTU is started, the FAC or FAS process is not started and the terminal displays [ FAS POWER t t t d d th t i l di l ON ] WAIT CONFIG FROM FLR !!!" or [ FAC POWER ON]WAIT CONFIG FROM FLR !!!" repeatedly.

13

2012/10/1

Terminal Displays WAIT CONFIG FROM FLR Repeatedly

Cause:

The FAC or FAS process obtains configuration from the FLR b t no response i returned. but is t d Check whether the FLR process runs properly, whether the MSTU communicates with the OMP properly, and whether the FLR data is configured.

Solution:

Disk Status Submitted by MSTU Is Abnormal

Symptom:

After the MSTU is started, the FAC and FAS processes run properly b t the number of disks submitted b th l but th b f di k b itt d by the MSTU is insufficient or the disk status is abnormal. A fault occurs in the disk, the disk is not mounted properly, or data is configured incorrectly.

Cause:

14

2012/10/1

Disk Status Submitted by MSTU Is Abnormal

Solution:
1. Run the cat /proc/partitions command to check the disk. 2. 2 If only the disk instead of the partitions is displayed by running the cat /proc/partitions command, for example, /dev/sdb instead of /dev/sdb1 is displayed, it indicates that the disk is not partitioned. 3. If the disk is mounted properly but the disk information is not displayed in the HDDEV table in the probe, a problem occurs in data configuration. Therefore, configure the information about the disk such as COUPLEID correctly.

Disk Status Submitted by MSTU Is Abnormal

4. Run the cat /proc/mounts command to check whether the disk is mounted. If the disk is not mounted, the disk may not be formatted mounted correctly. Run the parted s /dev/sdb1 print command to check whether the disk is partitioned. If the file system type is not displayed, run the mkfs.xfs f /dev/sdb1 command to format the disk.

15

2012/10/1

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

Failure to Start the Master OMP

Procedure for Starting the Master OMP

1. 2. 3. 4. Start the SUSE 9 operating system. Execute the autostart script. Execute the Boot program. Access the local configuration file and start the CPU version. 5. Load the FPGA version after the CPU version is started. 6. Power-on the processes of the board.

16

2012/10/1

Failure to Start SUSE 9

The disk space is insufficient. The operating system goes in single-user mode.

Executing the Auto start Script

To set auto start of the OMP board, do as follows:

1. Copy zxVS8000C, MSCU_Boot.exe, Makeauto from the th version room t /h i to /home on th MSCU b d the board. 2. Go to the /home directory on the MSCU board, and then set executable right to /home/ Makeauto and /home/MSCU_Boot.exe. 3. In the /home directory on the MSCU board, execute the command ./Makeauto ./zxVS8000C.

17

2012/10/1

Executing the Boot Program

First check whether autostart is set. Check whether the file /etc/init.d/zxVS8000C exists and whether it i executable. h th is t bl Check whether the file /home/MSCU_Boot.exe exists and whether it is executable. If the MSCU board is reset when the Boot program is executed, check the file /home/BootErrLog.log f the cause of the /h /B tE L l for th f th resetting.

Downloading Configuration Files from the Master OMP

A configuration file, such as cpu.ini, fpga.ini, ompboot.inf, and ompcfg.inf, does not exist in the /home/VER di t th /h /VER directory on th master OMP the t board

Solution: Construct the OMP version again, and start the master OMP board at least once by using the Boot program.

The configuration files fail to be downloaded from the master OMP board because the free disk space on the slave OMP board is insufficient.

Solution: Delete files that are not needed.

18

2012/10/1

Downloading Configuration Files from the Master OMP

The FTP service is not started on the master OMP board. Solution: check whether the FTP service is started normally on the master OMP board.

Contents

Overview Service Module Data Module File System Module Supporting Module Bearer Module

19

2012/10/1

Failure to Start Streaming Media

Because the MSTU External Network Port Configuration Is Incorrect and No IP Address or Route Is C fi R t I Configured d
1. Check whether the network cable is connected correctly. 2. After the network cable is connected, log in to the MSTU board, check the link status of the network port. 3. If the preceding configurations are correct, check whether the IP address and the routes of the corresponding unit are configured in the database.

Incorrect MDU External Network Configuration

Incorrect MDU External Network Port Configuration with no IP Address or Route Configured

20

2012/10/1

Incorrect MDU External Network Configuration

Check whether the configured external network port is connected to a switch; If a network cable is connected, check the port state:

If the port flag is set to 0, the port is Down. If the port flag is set to 1, the port is Up.

If the port state is Up, check whether the IP address and route of th corresponding port are dd d t f the di t configured in the database.

No Code Stream for Live Channels

Fault:

After channels are created and a user demands a live channel, the STB receives no media stream. h l th i di t An MDU receives the code streams of a live channel through an external media port

Causes:

21

2012/10/1

Solutions

1. The flow of upstream media stream is code streams -> MDU -> MDU (MSTU).

(1)Check whether code streams interrupt in an access channel (2)Telnet to the 2400 subcard of the access channel. Check the forwarding of media streams. (3)Telnet to the 85xx subcard. Check whether the subscriber data of the incoming channel is correctly g y configured. (4)Telnet to the 2400 subcard. Check whether settings of the level-2 forwarding table are correct.

Solutions

2. The flow of downstream media streams is MDU -> MDU (MSTU).

(1)Telnet to the 2400 subcard of the outgoing channel. Check the forwarding of outgoing media streams. (2)Telnet to the 85xx subcard. Check whether the subscriber data of the incoming channel is correctly configured. ( ) (3)Telnet to the 2400 subcard. Check whether the learning information of the ARP table is correct.

22

2012/10/1

23