Avaya Media Processing Server Series System (Software Release 2.1) Manual do Utilizador descarregar pdf (Página 268)

Avaya Media Processing Server Series System Reference Manual

Page 268 # P0602477 Ver: 3.1.11

enabled), or a user can manually return control back to the primary using the TRIP

manual-failback command. The backup node then resumes primary node

monitoring.

Once the backup node enters active service, there is no longer an available backup to

compensate for component failure of remaining primary nodes. Isolate and fix the

problem on the primary nodes as soon as possible to re-establish the backup facility.

Resources (such as oscar, fax, etc.) might not be immediately available to the

secondary node after failover. The resources first need to be freed before they become

available to the secondary node.

TRIP Failback

The TRIP auto-failback command (used in trip.cfg) allows the primary node to

automatically resume primary call processing once the primary node is up and running

again. If, during startup, TRIP on a primary node detects that a TMS is controlled by a

secondary node (and auto-failback is enabled), the primary node TRIP sends a

failback request to the secondary node TRIP and the secondary node TRIP releases

the TMS. The primary node then acquires the TMS and continues call-processing.

The TRIP manual-failback command provides the user the flexibility of

determining when control should be given back to the primary node, and is only used

when auto-failback is set to "off". This is accomplished via the following TRIP

console/vsh command:

vsh-> trip manual-failback hard

There are two types of failback: hard and soft. During hard failback, the secondary

node releases the TMS immediately and all calls in progress are disconnected

immediately. During soft failback, the secondary node releases the TMS only after all

calls and conferences in progress terminate normally. This prevents loss of any call

service during failback, but causes failback to take an unpredictable amount of time to

complete.

As of this writing, soft failback is not available. However, this can be accomplished by

soft terminating applications on the secondary node prior to issuing the TRIP

manual-failback command on the primary node.

The trip restart-tms command (used in trip.cfg) allows the primary TRIP

process to avoid restarting the TMS (if the TMS is in the READY or STARTUP state)

when the primary TRIP resumes control. This can speed up the total primary node

restart time. However, not restarting the TMS forces the TMS to use the last loaded

configuration. If the TMS requires a new configuration, it has to be manually restarted

(usually by power cycling the system).

Refer to the MPS Command Reference Manual for details of these TRIP commands.

Depending on system configuration, the tmscomm component can run on a secondary

node. However, it will not be restarted during failover and failback.

1 2 ... 263 264 265 266 267 268 269 270 271 272 273 ... 305 306

Sem comentários

Avaya Media Processing Server Series System (Software Release 2.1) Manual do Utilizador Página 268