Avaya 555-233-223 Manuel D’Utilisation

Page de 48
8LI9TPSEHERH(S[RPSEH4VSGIWW
 10
Avaya™ ATM WAN Survivable Processor Manager Installation and Configuration
1SHMJ]MRK8VERWPEXMSRWJSVXLI;74W
ASP Manager does not download an exact copy of the translations to the WSPs. If it did, it 
would overwrite critical connectivity information that allows the WSP to communicate with 
other systems. Instead, after uploading translations from the main server, ASP Manager 
makes some minor adjustments to the translations; for example, changing IP address, port, 
and node name information, as appropriate, to work on the given WSP. 
(S[RPSEHMRK8VERWPEXMSRWXSXLI;74W
Once ASP Manager has uploaded translations from the main server, it issues the 
status atm 
wsp
 command on the main server. If the WAN Processor Role field contains a value of 
“pending”, no WSP data is available and ASP Manager logs an error. If the WAN Processor 
Role field contains any other value, ASP Manager can then display the name, number, and 
link status of each WSP in the network. 
ASP Manager then connects and logs in to each WSP, using login IDs and passwords that 
have previously been set up on the WSPs and specified in ASP Manager. ASP Manager issues 
the status atm wsp command on each WSP. If the WAN Processor Role field contains a 
value of “spare” and the State field contains a value of “standby,” then ASP Manager issues 
the save translations removable-media command, and then the download 
translations
 command. If the WAN Processor Role and the State fields contain any other 
values, then ASP Manager aborts the save translations and the download and logs an error. 
After ASP Manager downloads translations successfully, it does one of two things: for 
anything prior to DEFINITY ECS Release 10 systems, it issues a reset system 4 disk 
command; for DEFINITY ECS
 
Release 10 and later systems, it issues a reset system 3 disk 
preserve-license command. These commands reboot the WSP in a forced-standby mode. 
This terminates the connection between the WSP and ASP Manager. 
Several minutes later, ASP Manager attempts to reconnect to the rebooted WSP. If it fails, it 
tries again in another several minutes. If it fails again, it logs an error in its status log. If it 
succeeds, ASP Manager modifies the translations. Precisely how depends on whether or not 
the main server has the “critical reliability” feature enabled.