Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 113)

Base System Configuration

# P0602477 Ver: 3.1.11 Page 113

On the back of each VRC, there is a number selector that defines the number of the

chassis. (See VRC Rear Panel on page 26.) Ensure that these are uniquely set (starting

at 0) for each chassis in the system. This number corresponds to the chassis number to

be used in the [DTCMAP] section of the tms.cfg file.

A logical TMS number (TMS1, TMS2, etc.) is assigned to each TMS in the system.

Each TMS must have a primary VOS subcomponent bound to it. Typically, TMS1 is

bound to VOS1, TMS2 is bound to VOS2, and so on. If a redundant or backup MPS

node is used in the system, the MPS components on that node are also aliased to

secondary VOSs. Typically TMS1 is bound to VOS101, TMS2 is bound to VOS102,

and so on.

Under the Config column, is the configuration name ([CONFIG_NAME]) for each

TMS. This defines the configuration definition to use for each TMS. (See TMS

Resource Definition Section on page 108.)

There should always be uncommented BIND statements for each NIC in the chassis.

Only the Chassis Num and Chassis Slot (i.e., 7 and 8) should be entered, with

the remaining columns each containing a dash (-). If the chassis contains a Hub-NIC,

there is no need for NIC bind statements, or they can be commented out.

1 2 ... 108 109 110 111 112 113 114 115 116 117 118 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 113