8.1IPTV BC CH VS8000C Software Installation and Configuration 1 PPT 201007 103p

10/1/2012

1

VS8000C Software Installation and Configuration

Contents

Server129 Installation

SOMP Board Installation & Startup SOMP Board Installation & Startup

ZXUSS Configuration

Other Board Startup

IPTV Service Configuration

Follow-up Maintenancep

10/1/2012

2

Installation Preparation

1. The operating system and database have been installed completely. The operating system has installed Windows 2003 Server (with Windows

2003 SP3), and has updated the most-updated key patches from Microsoft website via Windows UpdateMicrosoft website via Windows Update.

The database has installed MS SQL Server 2005.

2. The cable layout has been completed. It is required that Server129 and SOMP eth3 port can ping through each other. The IP address of Internet adapter on server129 is set as 129.0.31.129. Log into SOMP locally, and set the IP address of eth3 as 129.0.31.1.

# ifconfig eth3 129.0.31.1 netmask 255.255.255.0

Installation Steps 1. Run the install file under the installation directory (/oamback_install/).

Choose the language type.

2. Choose the installation mode. For a new office, choose “Install”; for the follow-up upgrading, choose “Upgrade”. Click Next. p pg g, pg

3. Input the same username and password as those of the operating system to be installed, and then verify them.

10/1/2012

3

Installation Steps 4. Choose the installation path.

5. Start the installation.

6. Choose the maintenance equipment type. Here, choose USS100.

7 Initialize the system running environment 7. Initialize the system running environment.

Installation Steps 8. Choose the subsystems to be installed. Here, choose

All.

10/1/2012

4

Installation Steps

9. In communication configuration, set the IP address for the communication between foreground and background. 1)The IP address of foreground host must be set as 129 0 31 1 1)The IP address of foreground host must be set as 129.0.31.1.

2)The server IP address is the local IP address of server129, which must be set as 129.0.31.129.

Note:

The IP address of foreground SOMP configured here will overwrite the IP address manually configured.

On server129 and SOMP server the communication IP On server129 and SOMP server, the communication IP address must be on the 129 segment.

10. After installation completely, restart the computer.

Starting up Server129

On the desktop of server129, find the icon “Server Process Bailiff” and double-click it.

After starting up the services normally find the After starting up the services normally, find the services are all running. Do not disable them, otherwise 129 service will be shut down.

10/1/2012

5

Contents



ZXUSS Configuration

Other Board Startup


Follow-up Maintenance

RIDC DIP Switch Setting

RIDC card is located at the left bottom or right bottom, as shown below.

1 2 3 4 5 6 7 8

Logical Shelf NoLogical Rack NoUndefined

In this figure, the black block indicates the location of DIO switch. If it is in OFF position, by default OFF=1; if it is in ON side, by default ON=0.

10/1/2012

6

RIDC DIP Switch SettingShelf

NoShelf Type RIDC Setting Figure

1 Control Shelf

Rack1 Shelf 2

00000001

2 Control Shelf

Rack1 Shelf 2

00000001

Media Shelf 1

Rack2 Shelf1

00000100

RIDC DIP Switch Setting

3 Control shelf

Rack1 shelf2

00000001

Media shelf1

Rack2 Shelf1

00000100

Media shelf1

Rack2 Shelf1

00000101

10/1/2012

7

SOMP Board Startup Preparation:

1.The 2 CPU on SOMP board have installed the operating system (SUSE 9+SP3), and can be started up successfully.

2.Log into SOMP. (Directly from the terminal, or remotely by the Secure Shell Client tool).

3.Prepare the SOMP version files, which can be acquired from the version server according to the version server.

Board Version type Version path Version list

SOMP Boot startup version \Boot\Linux_Boot\MSCU\ MakeautozxussMSCU_Boot.ext

CPU-X86 version \USS\Release\MSCU\MP\ USS_MSCU_MP_X86_V1.0.01.00T07_H.USS

FPGA version \target_hardware\FPGA\ ZXUSS_MSCU-080101-FPGA_04_H.rbf

Constructed version Server129 _ZXUSS_MSCU-080101-FPGA_04_H.rbf

Constructed configuration Server129 ompcfg.inifile

Initial data /DATA1/ 1．CfgTable.ZDB2．DBVer.ZDB3．VerTable.ZDB

Initial man-machine command

/oamback_install/mml/cmdini/ /home/cmdini/

In the above table, the versions indicated in red are provided by the production line, and the onsite does not need any operation.

Startup Steps

A system RS485

B system RS485

Connectoin of RMSCU rear

plug-in card and background

server

A system eth3

A system VGA

B sysetm VGA

A system RS232

B system RS232

A system USB

B system USB

B system eth3

2826SWBackground server 129

Note: A system (CMP) - CPU2 B system (OMP+CMP) - CPU1

10/1/2012

8

Startup Steps

1. Configure the IP address of SOMP system B. # ifconfig eth3 129.0.31.1 netmask 255.255.255.0

Note: 1) It t b fi d th3 d t 1) It must be configured on eth3 adapter.

2) It must be configured in the command mode, instead of by the yast tool. 2. On SOMP, create the following directories. Note that they are case-

sensitive. Create the following directories strictly as below: 1) /home/VER 2) /home/cmdini 3) /home/dbs

3. Manually upload the related version file to the /home/VER/ direction y pon SOMP board. 1) CPU version: USS_MSCU_MP_X86_V1.0.01T05_H.USS 2) FPGA version: ZXUSS_MSCU-080101-FPGA_04_H.rbf 3) Constructed FPGA version: _ZXUSS_MSCU-080101-FPGA_04_H.rbf 4) Constructed configuration file: ompcfg.ini

Startup Steps4. Copy the initial man-machine command (under the path:

/oamback_install/mml/cmdini/) to the /home/cmdini/ directory on SOMP board.

5. Copy the initial data from /DATA/ to the /home/dbs/ directory on SOMP. Make sure that the final directory structure is as below:Make sure that the final directory structure is as below:

1) CfgTable.ZDB2) DBVer.ZDB3) VerTable.ZDB6. Copy the 3 executable files from the /Boot/Linux_Boot/MSCU/ directory

to the /home/ directory on SOMP board, and add the executable permission.

1) Makeauto 2)2) zxuss 3) MSCU_Boot # chmod +x MSCU_Boot.exe# chmod +x Makeauto zxuss # ./Makeauto ./zxuss # ./MSCU_Boot.exe

10/1/2012

9

SOMP Startup Checking Judge whether the OMP board has been started up according to the following

rules: 1. Check whether the IP address of eth3 has been re-configured as the specified IP

address: 129.0.31.1, and whether the foreground and background can ping through. 2 Check the process of SOMP to see whether there is MSG MSCU MP X8 2. Check the process of SOMP, to see whether there is _MSG_MSCU_MP_X8.

3. Check the status indicator on SOMP board. Under normal situation, run indicator is on and off alternatively; alarm indicator is off; act indicator is always on.

4. After creating NEs on EMS, check whether the NE link status is normal. 5. Check whether the communication between foreground and background is

normal. On server129, press Ctrl+Alt+F12 to see the communication status between server129 and foreground OMC. The Status should be displayed as “true”.

Adding NE

Initial user and password should both be “admin”. There no particular requirements for other items.

10/1/2012

10

Adding NE

1. IP1: 129.0.31.1, It is the original IP of SOMP, and can be modified according to the NE IP setting on OMC. 2. Port: 50573. EMF module: 156. The range of allowed module No for EMS is 144-254, and it is 156 by default. This configuration item should be planned globally, and the local SOMP in the whole network should all be set as 156.

Contents



ZXUSS Configuration

Other Board Startup



10/1/2012

11

Basic Property Configuration


1. NE type: USS.

2. Area code: Filled in according to the actual engineering configuration.

3. Office No: This is the office No that has established link with CDN-M. It is a globally unique office No. It is increased from 1, and should be planned in advance.

4. IP address: Set the IP address of SOMP. After setting this IP address, eth3 of SOMP board will be assigned with this IP address after data synchronization.

5. MAC address: It can be set as any value. According to ZTE specifications, it starts with 00-d0. During the engineering, it follows the format of 00-d0-OfficeNo-RackNo/ShelfNo-SlotNo-ModuleNo, to define the MAC address. The 4th segment in MAC address can follow the example: Rack1 Shelf2=12, Rack2 Shelf1=22.

6. Maintenance IP address 1: Set the remote maintenance IP address of SOMP. It is usually the Internet IP address. Refer to IP planning table.

7. Maintenance IP address 1 mask: Set the remote maintenance address mask of SOMP.

10/1/2012

12

ZXUSS NE Property

ZXUSS NE Property – Configuration Description

1. USS authentication code: Not in use temporarily. It is unified as 1. 2. Timeout forced disconnection time: It is the forced disconnection for

STB timeout, in the unit of second. By default, it is 50 seconds. 3. Temporary channel threshold: It is created when MDU resources

exceed this threshold. It is enabled by default. 4. MDU idle channel threshold: It indicates that the MDU idle resource

threshold of temporary channel is allowed to be created. By default, it is enabled.

5. Moveout user threshold: It is the proportion of move users to the temporary channel after it is created. By default, it is enabled.

6. USS node ID: It is the unitid generated on CDN-Manager, which is6. USS node ID: It is the unitid generated on CDN Manager, which is acquired after iptvcdn portal operation. Refer to the figure.

7. NTP local port: 123.

10/1/2012

13

Physical Resource Configuration

Physical Resource Configuration –Configuration Description

1. Rack No: Increased from 1.

2. Rack type: Choose the rack type as “240-RT_USS_STANDARD”.

3. On the local node, the global rack No cannot be repeated. It is required that the rack No of the control shelf is 1.

4. In the case of multi-shelf, it is required that the control shelf and resource shelf are located on different racks.

10/1/2012

14

Shelf Configuration

1. For a single shelf, the shelf No must be 2, and the shelf type is 240-ST_USS_COMMON_BCTC (control shelf).

2. For mutli-shelf, the control shelf must be Rack1 Shelf2. Except one control shelf the types of other shelves are 240-one control shelf, the types of other shelves are 240-ST_USS_COMMON_BUSR (resource shelf).

3. In the case of global multi-rack, there can be only 1 control shelf, and the other shelves are all resource shelves.

4. It is required that the specific configurations must be the same as DIP switch settings.

Adding Board Configuration

10/1/2012

15

Adding Board Configuration – Configuration Description 1. For each shelf, first configure the MSU board. It can only be

configured in slot 7/8 in active/standby mode. 2. Configure the SOMP board. It can only be configured in slot 9/10 in

the control shelf with the type of MSCU in active/standby modethe control shelf, with the type of MSCU, in active/standby mode. 3. According to the onsite requirements for service bearing, when

several MSCU boards are added, MSCU is also required to locate in the control shelf, in slot 5/6, 11/13, 12/14, 1/3 and 2/4 by sequence. Its type is MSCU, working in active/standby mode.

4. According to the actual board position diagram, add the board of MDU type, working in active/standby mode.

5. MSTU must be set as “no standby” mode, with the type of MSTU. 6. In the case of multi-shelf, MSTU must all be configured in the media

shelf, located in the format of 1/2, 3/4, 5/6, 9/10, 11/12 and 13/14.

Adding Board Configuration – MSTU Active/Standby Configuration

10/1/2012

16

MSTU Active/Standby Configuration –Configuration Description 1. The assignment of active/standby MSTU can only be performed by the 2

MSTU boards.

2. It is required that MSTU in slot 1/3, 2/4, 5/6, 11/13 and 12/14 must be fi d i iconfigured in pair.

3. It is not allowed to configure the board in pair across the shelves.

4. It is not allowed to configure MSTU in odd number. That is, it is not allowed that one MSTU has no match. In case this situation occurs, the commercial department shall take the responsibility.

5. EPG does not belong to USS system, so it does not need to be added.

Logical Resource Configuration

10/1/2012

17

Module 1 Configuration

1. Module type: Choose the module type as shown above, including: yp yp , gSOMP, SMP, MSCU and CSU (currently, the CSU module are configured in module 1 by default, so it does not need to be chosen).

2. Rack/shelf/slot: rack1/shelf2/slot9. 3. CPU No: 1 4. Signaling transfer poll proportion: 1


1. Module type: Module 2# can only choose SMP and MSCU type.

2. Rack/shelf/slot: rack1/shelf2/slot9. 3. CPU No: 2 4. Signaling transfer poll proportion: 1

10/1/2012

18


1. Module type: Module 3# can only choose SMP and yp yMSCU type.

2. Rack/shelf/slot: It is configured according to the actual MSCU slot.

3. CPU No: 1 4. Signaling transfer poll proportion: 1


1 Module type: Module 4# can only choose SMP and MSCU type 1. Module type: Module 4# can only choose SMP and MSCU type. 2. Rack/shelf/slot: It is configured according to the actual MSCU slot. 3. CPU No: 2 4. Signaling transfer poll proportion: 1

10/1/2012

19

Unit Configuration

Add the unit according to the following sequence: All MSU of the current node -> All MDU of the current node -> All MSTU in media shelf 1 (slot 1-> slot 14) -> All MSTU in media shelf 2 (slot 1 -> slot 14)

MSU Unit Configuration

Module No: MSU must be configured on OMP, so MSU must choose module 1.

10/1/2012

20

MDU Unit Configuration

1. Add MDU unit: Module No: According to the restriction of current version,

the MDU unit can only be configured in CSU module, sothe MDU unit can only be configured in CSU module, so MDU can only be configured on module 1#.

2. Modify the subunit: 1) Set subunit 12 as the signaling interface, with the subunit type

as 244-SUT_USS_MDU_SIG. 2) Set other the other remaining subunits (18, 19, 20, 19, 10, 11) as

the media interface, with the subunit type as 232-SUT USS MDU EXTRIP. _ _ _

3. Modify the IP address of external port: Observe the Ethernet port from the backplane of MDU.

From top downward, they correspond to the subunits: 18-19-20-10-11-12.

MDU-10 Subunit – Modifying IP Configuration

1) According to the actual requirements, configure the IP address, subnet mask and default next-hop IP address (gateway IP address) of the external port.

2) MAC address: ZTE adopts the MAC address starting with 00-d0. During the engineering, it is recommended to configure the MAC address according to the following principle: 00-d0-OfficeNo-RackNo/ShelfNo-SlotNo-UnitNo.

3) Layer-3 detection interval, whether to perform changeover, whether there is loopback: These three configurations are not in use temporarily, and adopt the default settings.

4) Optic/Electric port property: Electric port

10/1/2012

21

MDU Unit Configuration

4. Allocate the channel access port: 1) The port can only be added or deleted. When adding the port, input the

starting and ending circuits, with the range of 0-399. 2) Here, the circuit configuration of external port is to allocate the channel ) , g p

access port. That is, when creating the channel, the IP address and port in the live broadcast source SDP file must be configured here, corresponding to the foreground data table r_channelset. If they are not configured or are not consistent, the system returns the failure of MDU application failure when creating the channel; on the non-signaling external port subunit of each MDU, only the first 400 ports need to be configured (inward resource of external port).

3) Note: If the access channel mode is multicast, make sure that there is idle circuit, as the circuit added here cannot be used as the access circuit of multicast. In other words, if USS border node needs to create 100 all-network multicast channels (to receive the uplink multicast code stream), 100 circuits need to be idle; that is, only add 0-299.,

Note: After modifying any MDU configuration and synchronizing the data, all

OMP boards need to be restarted first, and then all MDU boards are restarted.

MSTU Unit Configuration

1. Add MSTU unit: Module No: It is evenly allocated according to actual situation, to avoid

frequent cross-module operations. During the engineering, all MSTU are evenly allocated to each module.are evenly allocated to each module.

2. Modify IP address of external port: Observe the Ethernet port on the MSTU backplane: 11 is the

downward port and 12 is the upward port. 3. Modify the IP address of external port:

1) According to the actual requirements, configure the IP address, subnet mask and default next-hop IP address (gateway IP address) of the external port.

2) MAC address: ZTE adopts the MAC address starting with 00-d0. During the engineering it is recommended to configure the MAC addressthe engineering, it is recommended to configure the MAC address according to the following principle: 00-d0-OfficeNo-RackNo/ShelfNo-SlotNo-UnitNo.

3) Layer-3 detection interval, whether to perform changeover, whether there is loopback: These three configurations are not in use temporarily, and adopt the default settings.

4) Optic/Electric port property: Electric port

10/1/2012

22

Physical Connection Configuration On the three shelves, add

the interconnection configuration. We must configure the interconnection between MSU on rack2 shelf1 and MSU on rack2 shelf2. Otherwise, the media planes on the two media shelves cannot ping through.

Click “Add”. In the MSU unit No and the connected unit No, choose the unit No ,of the two MSUs that need to be cascaded.

Module Shared Resource Selection Sequence Configuration

The standby module of each module should choose all the other modules, which form a loop by sequenced. For example, the sequence of standby modules for module 1 is 2-3-4, and the sequence of standby modules for module 2 is 3-4-1.

10/1/2012

23

USS Intra-node CDN Quota Content number and channel number: Configured according to the actual

situations. The content number restricts the maximum number of contents that can be released on USS CDN node, while the channel number restricts the maximum number of channels that can be created on USS CDN node. In the current version the maximum number of channels is restricted to 200current version, the maximum number of channels is restricted to 200.

Storage space: Configured according to the disk configuration on this node.

USS Intra-node VCDN Quota Node No: It must be the same as the VCDN No on CDN platform. Content number and channel number: Configured according to the actual

situations. The content number restricts the maximum number of contents that can be released on USS CDN node, while the channel number restricts the maximum number of channels that can be created on USS CDN node In the current version the maximum number of channels isCDN node. In the current version, the maximum number of channels is restricted to 200.

Storage space: Configured according to the disk configuration on this node.

Note: If USS includes several VCDN nodes, several records must be configured here.

Otherwise, it affects the content release of channel creation.

10/1/2012

24

Signaling Configuration – MLSS Configuration

The related configuration of CDN-MANAGER remote server should be the same as that in /home/zxin10/etc/win_mgt.scr on the service Manager server. 1. CDN-MANAGER ID is only a serial number, which can be configured as 1. The name can be

configured as any. 2. IP address: Configured as the Internet floating IP address of service CDN-MANAGER. 2. IP address: Configured as the Internet floating IP address of service CDN MANAGER. 3. Port No: 5000. It should be the same as the listening port of module1 in win_mgt.scr. 4. Office No and Module No: They are configured as the module No and office No of service

Manager. 5. CDN-MANAGER process No: 220. 6. Channel deletion mode and content deletion mode: Forced deletion.

APP Configuration

Configuration method: 1. APP Id can be configured as any (1-255).

2. APP process No: 273. The process No of APP module is 273.

3. APP port No: 4999. Here, it is the CDN-MANAGER port -1, indicating that the link between APP and CP starts from 4999+1.

4. APP process No 2: All are fixed as 463.

10/1/2012

25

MLSS Communication Configuration 1. Communication link No: Currently only one communication link is established in CSU module with

CDN-MANAGER. The link No is configured as 1.

2. MDU subsystem No, MDU subunit No: MDU subunit No is configured as the external port of signaling subunit in MDU unit.

3. MLSS port No: In engineering, all the USS nodes need to be specified. Here, it is configured as p g g, p , g6000.

4. MLSS module No: 1. It should be the same as module1 in win_mgt.ini of CDN-MANAGER.

5. MDU unit No, subunit No: Refer to MDU configuration.

APP Communication Configuration Communication

Link NoAPP Port No APP Realm

NameModule No Associated APP ID

1 6001 1 1 1

2 6002 2 2 1

3 6003 3 3 1

4 6004 4 4 1

10/1/2012

26

STB Configuration

1. MDU subsystem No, MDU subunit No: MDU subunit No is configured as the external port of signaling subunit in MDU unit.

2. STB port No: 554

FTP Server Configuration 1. FTP Server user and password: Both are “iptv”. 2. Single client bandwidth (KB): Filled in as 1000. Here, it cannot be filled

as any value at random. 3. Encryption key: 1.

N t Note: Currently, this configuration is not taken full use of. It is mainly used to acquire

the bandwidth restriction for content distribution, and is used to specify the MSTU user, password and maximum connections when USS is used as the server in future.

10/1/2012

27

Data Transfer 1. Specify the module No as 1, and do

not choose other modules. The system performs the synchronization automatically.

2 Th d t i “ h d2. The command type is “changed tables of the specified module”. If the module capacity configuration is modified, choose ‘R_CONST tale of the specified module”. Then reset the SOMP board. In other situations, choose “changed tables of the specified module”.

3. Transfer type: Choose All. Note: The onsite can perform the operation

of table transferring only after completing all the settings before signaling configuration.

Contents



ZXUSS Configuration

Other Board Startup



10/1/2012

28

Version Canceling Setting This operation is only restricted to the situation that the version already exists

on the onsite board.

Version setting -> Cancel setting, to cancel all the visible versions.

Version maintenance -> Version deletion, to delete all the visible versions.

Uploading Version

The versions are saved under c:\netumen\ ums-svr\zxsscfg\zxsscfg-

i \VERSIONFILE\USS100\USS100version.par\VERSIONFILE\USS100\USS100 on EMS server. The red letters indicates the installation path of EMS software, which should be replaced according to the onsite situation.

The uploaded versions include: MSCU CPU version and FPGA version MSTU CPU versionversion and FPGA version, MSTU CPU version, watchdog version and stream media version, MSU CPU version, MDU microcode version, 85xx version, xscal version.

10/1/2012

29

Version ListBoard Version Type Version Path Version List

MSCU Boot version \Boot\Linux_Boot\MSCU\ MakeautozxussMSCU_Boot.ext

CPU-X86 version \USS\Release\MSCU\MP\ USS MSCU MP X86 V1.0.01.00T07 H.USSCPU X86 version \USS\Release\MSCU\MP\ USS_MSCU_MP_X86_V1.0.01.00T07_H.USS

FPGA version \target_hardware\FPGA\ ZXUSS_MSCU-080101-FPGA_04_H.rbf

MSU CPU-8260 version \USS\Release\MSU\MSU\ USS_MSU_MSU_8260_V1.0.01.00T07.BIN

MDU Microcode version \USS\Release\MDU\MDU\ MSG_MDU_MDU_V1.0.01.00T07.UOF

CPU-85 version USS_MDU_MDU_CPU1_85XX_V1.0.01.00T07.BIN

CPU –XSCAL version USS_MDU_MDU_CPU0_XSCALE_V1.0.01.00T07.BIN

MSTU Boot version \Boot\Linux_Boot\MSTU\bigsmp\ MakeautozxussMSTU Boot bigsmp.exe_ _ g p

CPU-X86 version \USS\Release\MSTU\bigsmp\ USS_MSTU_MSTU_X86_V1.0.01.00T07_H.USS.BIN

Watchdog version \USS\Release\MSTU\WatchDog\ zmsscmd_h

Stream media version \target_hardware\ZMSS\ R_ZMSS_H.rpm

File system library version

\target_hardware\Lib\ USS_MSTU_LIBFS.soUSS_MSTU_LIBIPC.so

Adding Version Enter Version Maintenance -> Add Version -> Browse. Click “Execute” button, and then all versions will be sent to the SOMP board. The

execution process is rather slow. Please wait with patience. After executing the command successfully, there is the success prompt.

10/1/2012

30

Version Specified Loading 1. Rack No and Shelf No: Filled in according to actual onsite situation. Fill in the control shelf.

2. Slot No: Fill in the slot of SOMP board.

3. CPU No: Fill in 1.

After configuration completely, click “>>” and then click “Start to load”. g p y

Board Resetting

After distributing the version, it is required t t th MSUto reset the MSU, MDU and MSCU boards.

10/1/2012

31

Board Startup MSU:

MSU on the control shelf:

1. Directly hot-plug MSU, and do not touch RMSU. 2. Observe whether the run indicator on MSU is on and off alternatively. 3. Check whether the Fabic indicator under MSU is always on. y4. Check whether the network segment 128 of MSU can be pinged through. 5. On the rack diagram, check whether MSU can be started up. 6. Log into MSU via telnet, and input “i” to view the started process. 7. After acquiring versions from OMP, MSU can be started up normally. For any

abnormality, start it up for several times, until it becomes normal. MSU on the media shelf:

1. In EMS data configuration, complete the logic resource configuration. Pay attention that the Logical Resource Configuration – Physical Connection Configuration operation must be performed.

2. Data transmit method: Transmit the tables to the foreground, to make the fi ti d t t k ff tconfiguration data take effect.

3. Power on the MSU board in slot 7/8 on the media shelf, to start it up. 4. MSU on all shelves should be powered on normally, and they are in normal status.

Board Startup MDU: 1. Directly hot-plug MDU, and do not touch RMSU. 2. Check whether the run indicator on MDU is on and off alternatively. 3. Check whether the 128 network segment and IP address of external port can

ping throughping through. 4. Check whether MDU has been configured with IP address via “ifshow”

command. 5. Use the “PrintfArp” command to see the Arp learning of MDU. 6. If it cannot be pinged through, check whether the version has been loaded. MSCU: 1. Log into MSCU board locally, and configure the IP address of eth3. Make sure

that the PC machine that the version exists on can be pinged through. 2. Connect the eth3 port on the MSCU backplane with PC, and copy the 3 version

files for Boot startup to the /home directory For the version details refer tofiles for Boot startup to the /home directory. For the version details, refer to Table 5.2-1.

3. Log into MSCU board, enter the /home/ directory, grant the authority for the startup versions and then run the Boot program.

10/1/2012

32

Board Startup

# chmod +x MSCU_Boot.exe# chmod +x Makeauto zxuss # /Makeauto /zxuss# ./Makeauto ./zxuss # ./MSCU_Boot.exe Note: Start it up twice: During the first startup, the system will

restart; the second startup needs to be manually reset. 4. Check whether the run indicator of MSCU is on and off

alternativelyalternatively. 5. Check whether the 128 network segment of MSCU can

ping through. 6. On the rack diagram, check the status of MSCU. 7. Check the MSCU process.

Board Startup

MSTU:

Currently, the MSTU board needs to be manually started up. After the function has been improved in the future, it will be directly started via EMS,

d th t t ill b th MSU b dand the startup process will be the same as MSU board.

1. Make sure that the operating system is running normally.

2. After login locally, check whether the three hard disks have been partitioned and formatted.

Refer to related manuals for the checking steps.

3. Manually format the 3 new partitions.

linux:/home # mkfs -t xfs /dev/sdb1

Then format sdb sdc sdd in sequence At last run the following command toThen format sdb, sdc, sdd in sequence. At last, run the following command to make sure that the format operation is successfully.

# parted -s /dev/sdb1 print

10/1/2012

33

MSTU Startup Steps 1. Copy the MSTU version files to the /home directory.

2. Enter the /home directory on MSTU board, grant authority for the Boot version, and then start up the board.

# chmod +x MSTU_Boot_bigsmp.exe

# chmod +x Makeauto zxuss

# ./Makeauto ./zxuss

# ./MSTU_Boot_bigsmp.exe

Note:

Start it up twice: During the first startup, the system will restart; the second startup needs to be manually reset.

3. Check the process:

# ps -ef|grep ZMSS

4. Test the FTP function:

# ftp 127.0.0.1 Both the username and password are “iptv”.

Contents



ZXUSS Configuration

Other Board Startup



10/1/2012

34

CDN Platform Configuration

Before CDN platform configuration, make sure that the CP configuration file has been configured correctly.

Node management:

http://ip:8080/iptvcdn System resource management – Node management

1. The ZXUSS parent node should be configured according to the onsite situation.

2. The Node name, Bandwidth Threshold, Storage Threshold, Concurrency Threshold should be filled in according to the onsite situation.

3. Node weight number: Configured as 1.

4. IP segment management mode: Node-level IP segment management

5 POP unit categorization management: Not enabled5. POP unit categorization management: Not enabled

6. Recording mode: Unified storage mode

CDN Platform Configuration

10/1/2012

35

Agent Management Configuration

1. Node name: Choose the ZXUSS node created just now.

2. Agent name, IP: The IP address must be the same as the local IP address of SCP configured in win_mgt.ini of CDN-MANAGER.

3. Port No: 1555

4. Module No and Office No: Fill in the module No and office No of CDN-Manager.

POP Unit Configuration 1. POP unit name: Self-defined.

2. USS unit IP address and USS unit signaling IP address: Fill in the signaling IP address of MDU.

3. USS unit signaling port: 554.

4. USS unit logical space restriction: 750*3*0.8*n/2, n is the number of MSTU board.

5. USS unit logical concurrency restriction: 400*n, n is the number of MSTU board.5. USS unit logical concurrency restriction: 400 n, n is the number of MSTU board.

After adding all the POP units of ZXUSS node, remember the acquired unit ID, and add it in USS global configuration.

10/1/2012

36

ZXUSS Device Management

1. Node name, POP unit name: choose the node and POP unit that have been added in the previous steps.

2. Service unit No: Fill in 1. For all the USS equipment, fill in the service unit No as 1. 3. Module No: Fill in 1. For all the USS equipment, fill in the module No as 1. 4. Office No: It should be the same as that set in the previous step, and should also

associate the configuration file. The office No is globally unique. It starts from 1, and should be well planned.

5. Process No: 436.

USS Unit FTP Management


2. FTP address: Fill in any MSTU external IP address of this USS node.

3. FTP port: 21.

4. FTP username/password: iptv.

10/1/2012

37

VCDN Management

For a new office, make sure that the VCDN serial number and the service provider ID are consistent. Both of them are 1are 1.

Here, pay attention to VCDN serial number, which should be the same as that configured on USS side.

VCDN Node Configuration


2. VCDn node name: Self-defined, which should comply with the global specifications.

3. Channel number that can be created.

4. Reserved space, reserved bandwidth:

5. Whether to enable the aging function: No

10/1/2012

38

Contents



ZXUSS Configuration

Other Board Startup



Remote Management

During the engineering installation, server 129 in each ZXUSS office is required to be installed together with EMS. In the follow-up maintenance, the USS remote maintenance needs to be enabled, to perform the management operation via remote EMS.

1. Configure the remote maintenance IP address on the local SOMP.

10/1/2012

39


Maintenance IP address 1: Set the remote maintenance IP address of SOMP. It is usually a public IP address.

Maintenance IP address 1 mask: Set the remote Maintenance IP address 1 mask: Set the remote maintenance address mask of SOMP.

Configuring OMC Target Route Destination IP: The IP address of remote maintenance EMS. It is usually the

public floating IP address on the service dual-computer EMS.

Destination mask: It is decided by the remote maintenance EMS. Make sure the route is reachable.

Next-hop address: It is the gateway of remote maintenance IP address on local SOMP.

10/1/2012

40

Adding NE via Remote EMS

Adding NE via Remote EMS IP1: Fill in the SOMP remote maintenance IP address for the management of

USS node.

Port: Fixed as 5057.

EMP module: 157 The allowed range for EMS module No is 144-254 For the EMP module: 157. The allowed range for EMS module No is 144 254. For the SOMP on the same USS node, the EMS module No cannot repeat within the global range. As SOMP module No of local USS has been set as 156, EMP is increased by 1 to 157 when adding one remote maintenance EMS; to add another remote maintenance EMS, EMP is filled in as 158, and so on.

10/1/2012

41

Checking Status After Adding NE Note:

If NE is added normally, NE script No cannot be null, the link status should be “normal” and the link ID should not benormal , and the link ID should not be null or “1”.

5. After adding NE successfully, the user can add the USS nodes of the whole network on one remote maintenance EMS, to make the unified management remotely.

NTP Configuration

NTP Server configuration: 1. After the NTP Server is determined, its NTP service

d t b bl d d th t k t f llneeds to be enabled, and the network segments of all other NTP clients should be added. Otherwise, when the NTP client initiates a request, NTP Server won’t respond.

2. After modifying the configuration completely, restart the NTP service.

# /etc/init.d/xntpd restart (suse)

10/1/2012

42

USS NTP Configuration

Parameters for Adding NTP Server

Server IP address: Fill in the IP address of NTP server.

Protocol port No: 123 (UDP)

Whether the server adopts GMT: 1-yes

NTP synchronization period: 20s by default

10/1/2012

43

Border NTP Configuration

After configuring NTP, if NTP signaling packets can be captured on NTPcan be captured on NTP server, it indicates that NTP configuration is correct. Wait for a few minutes on USS, and log into SOMP and MSTU to check the time.

EMS Toolkit

Command Line Terminal Advantages of using the command line

terminal:terminal: 1. When EMS graphic interface fails to

operate due to version problems, the command line terminal can be used to execute commands.

2. Some functions are not realized on the man-machine interface, but can be realized via the command line operation. For example acquire the table name listFor example, acquire the table name list GET_MPTABLE_LIST.

3. The command line terminal can execute the batch processing operations.

10/1/2012

44

Probe

The function of a probe is to check the content of foreground database, and check the status of foreground equipment.

Introduction to foreground database: The management of USS1 database can be described from different data The management of USS1 database can be described from different data

sources, including: USS node description data, related data of file system, internal data of USS node, service-related data, CDN load balancing and resource selection mechanism data.

1. USS node description data includes: 1) Configuration table, type table and data table of rack, shelf, board and CPU;2) Information table of NE configuration; 3) Configuration table and relationship table of module, unit, subunit and circuit; 4) Version table for board running; 5) User stream resource data and its value type parameter table; 2. The related data of file system includes: 1) System data of FAS equipment; 2) File naming space data; 3) Chunk naming space data; 4) Storage data of FAS data description block.

10/1/2012

45

3. Internal data of USS node: 1) CDN-related table;

2) VCDN-related table;

3) Equipment resource table;

4) MDU2400 subcard statistics information table;

5) Channel-related table;

6) Node networking configuration table;

7) CDN MANAGER APP d FTP fi ti t bl 7) CDN-MANAGER, APP and FTP configuration table;

8) USS node configuration table

4. Service-related data: 1) Content distribution table;

2) Channel information table;

3) Recording plan table;

4) VOD plan description table;

5) Program list information table.

5. CDN load balancing and resource selection h i d t i l dmechanism data includes:

1) MSTU specific impact factor table;

2) Service description table;

3) MSTU resource occupancy statistics table

10/1/2012

46

Common Tables

1. Content distribution table R_CDNCAP

The content description table R_CDNCAP describes the quota of CDN within USS node, mainly related to the content service operation. On the protocol level, it is processed uniformly by CSU, so this configuration table is allocated with modules. The occupancy statistics information such as current content and channels are put into this table, because the content number and channel number of the current system needs to be saved in the same way as static data, different from the dynamic statistics information such as user concurrent stream and bandwidth.

Content Distribution Table Field name Type Explanation

NodeID BYTE[NODEID_MAX] Node ID, the length is 18.

Contentmax DWORD The number of content that can be created, including the recorded content

Chnlmax WORD The number of channels created, including the virtual channel

Disksize DWORD Maximum storage space size that can is allowed to be requested

Contentnum DWORD Number of content currently added, including the recording content (generated on the foreground, and protected during transmitting)

Chnlnum WORD Number of channel currently created, including the virtual channel (generated on the foreground, and protected during transmitting)

Useddisksize DWORD Storage space currently occupied. This storage space is different from the real disk capacity on FAS equipment, and the stripe backup can be ignored. If the stripe backup is taken into consideration, specify the copy number when adding or recording content, and then decide the space according to the copy number (generated on the foreground, and protected during transmitting).

10/1/2012

47

Content Distribution Table R_CONTENT Field name Type Explanation

CID BYTE[20] Content ID

VCDNID BYTE[VCDNID_MAX] VCDN ID

T k d T k IDTasked Task ID

Nodeid BYTE [NODEID_MAX] Node ID

Fullname BYTE [CNAME_LENGTH] Full path of content, used to specify the destination storage path of this USS. It does not include the root directory of storage content set on USS. It is needed in CDN-MANAGER redirection.

Csize DWORD Content size

Mediatype DWORD Media resource encoding type

Duration DWORD File duration. Unit: second

Donetime BYTE [USS_TIMELENGTH] Content record generation time

Count DWORD Content access times

Status BYTE Content release status

Sdp BYTE[SDPLENGTH_MAX] File SDP description

User Stream Resource Data R_STREAM

Field name Data type Explanation

SubSystem BYTE Subsystem No inside the system

Unit WORD Unit No inside the subsystemUnit WORD Unit No inside the subsystem

Sunit BYTE Subunit No inside the unit

Index WORD Circuit No inside the subunit

Stime DB_SEIZERS_TIME

Starting time for resource occupancy (dynamic field, not configured on the background)

Time DWORD Terminating time (dynamic field, not configured on the background)

Status WORD Circuit status (dynamic field, not configured on the background)

Count WORD Circuit occupancy times (dynamic field, not configured on the background)

ip IPADDR

10/1/2012

48

User Stream Resource Data R_STREAM

Field name Data type Explanation

Udpport WORD UDP port No (dynamic field, not configured on the background)

h l d DWORD Ch l dchannelcode DWORD Channel code

Rescpu DWORD CPU capacity used this time (dynamic field, not configured on the background)

resfileio DWORD File system IO capability used this time (dynamic field, not configured on the background)

resinrev DWORD Internal inward bandwidth used this time (dynamic field, not configured on the background)

resinsend DWORD Internal outward bandwidth used this time (dynamic field, not configured on the background)

resextrev DWORD External inward bandwidth used this time (dynamic field, not configured on the background)

resextsend DWORD External outward bandwidth used this time (dynamic field, not configured on the background)

isvod DBBOOL

Subunit Relationship Table R_SUNIT System WORD Description

SubSystem BYTE Subsystem No

Unit WORD Unit No

Sunit BYTE CPU/DSP/ASIC/E1/T1 No inside the unit

SUnitType WORD CPU/DSP/ASIC/E1/T1 subunit type

PreQUE WORD When QUE is changed because the subunit type is modified, this field saves the QUE before modification.

QUE WORD Subunit No inside the same type of subunit

PreSunitSeq WORD

SunitSeq WORD

IPMedia IPA IP address of the media plane in subunit

MACT BYTE C fi ti th d f MAC dd f b it di lMACType BYTE Configuration method of MAC address of subunit media plane

LocalPortNum WORD Internal FE/GE port number of NEs related to the subunit

Info DWORD CRC4 working mode of related E1 of subunit. 0, CRC multi-frame; 1, dual-frame; 2, CAS multi-frame; 3, CAS multi-frame with CRC

Status DWORD Status

ExtSUNITTYPE WORD Subunit type defined on peripheral devices

Tag DWORD CAS setting

Tag1 DWORD CAS setting

10/1/2012

49

USS Subunit Extra Relationship Table R_SUNITEX

System WORD Explanation

SubSystem BYTE Subsystem No

Unit WORD Unit No

S it BYTE CPU/DSP/ASIC/E1/T1 N i id th itSunit BYTE CPU/DSP/ASIC/E1/T1 No inside the unit

SUnitType WORD CPU/DSP/ASIC/E1/T1 subunit type

Macmedia T_MAC Media plane AMC address of subunit (DSP, CPU or ASIC)

Mgpcm BYTE

Mghwset WORD Related hw group of the subunit. Usually the hw group is associated with the unit. Here, it is standby.

MgRackno WORD Rack No of the subunit

MgShelfno BYTE Shelf No of the subunitMgShelfno BYTE Shelf No of the subunit

MgSlotno BYTE Slot No of the subunit

MgHw WORD Related HW of the subunit (Valid for DT of inter-module connection or remote user unit)

UDPbaseport WORD Starting port No inside the VTC and RTP subunit

UDPportstep BYTE Number of occupied ports for each channel of VTC and RTP

VTCparaid BYTE VTC subunit parameter ID, associated with r_vtcpara

USS Subunit Extra Relationship Table R_SUNITEX

RTPIP IPA IP address of external port on MDU or MSTU

RTPMASK IPA IP mask of external port on MDU or MSTU

RTPNEXTHOP IPA Default next-hop of external port on MDU or MSTUp p

ExtSUNITTYPE WORD Subunit type defined on J10

Tag BYTE 0: signaling mode; 1: COMM mode

Tag1 DWORD Appended property

Tag2 DWORD Appended property

payload DWORD Encoding capacity level of VTC subunit

slcingain BYTE

slcoutgain BYTEslcoutgain BYTE

vtccapnum WORD Used capacity of VTC subunit (dynamic field, not configured on the background)

pcm BYTE PCM No of ISUP switch office

subcard BYTE Subcard No of VTC board

dspno BYTE DSP No inside the subcard of VTC board

10/1/2012

50

MSTU Resource Occupancy Statistics Table R_MSTURES

Field name Type Explanation

Subsystem BYTE Subsystem No

Unit WORD Unit No

Restype BYTE Resource type. 1: CPU resource

Resmax DWORD Maximum value of resource

Restorehigh BYTE Maximum reservation percentage of the file system: 0-100

Restorelow BYTE Minimum reservation percentage of the file system: 0-100

Ftpstorehigh BYTE Maximum reservation percentage of FTP: 0-100

Ftpstorelow BYTE Minimum reservation percentage of FTP: 0-100

Resblock DWORD[2] Number of blocked bandwidth on ports, recording the two ports respectively.

Filesysused DWORD Occupied resources of the file system

Serused DWORD Occupied services

Ftpused DWORD Occupied FTP

Isalarm BYTE Whether the alarm has been sent, to avoid sending alarms repeatedly

SignalingTracing WINTCP Signaling Tracing

10/1/2012

51

Signaling Tracing RTSP Signaling Tracing

Diagnosis Testing Diagnosis testing is to test the communication of each units within the media server

module, and check whether the server hardware is working normally, so as to locate and process faults in time, and guarantee that the media server is working normally.

The diagnosis testing includes the real-time testing, routine testing and batch commands

10/1/2012

52

Documents

8.1IPTV BC CH VS8000C Software Installation and Configuration 1 PPT 201007 103p