MCP core software load patch installation 79
Procedure Steps
Step Action
1Log on to the primary System Manager as the AA role (ntappadm) using SSH.
2Change directory:
cd /var/mcp/install
3Run the patching script:
./mcpPatch.pl
The progress of the patching process displays. The database is patched first, followed by the System Manager.
When the database and System Manager are patched, the System Manager restarts.
4Log on to the MCP System Management Console.
The System Manager is started and in the Active state, running on the desired load.
Patching the Network Elements
Use this procedure to patch the Network Elements. If a Network Element is supported in a fault tolerant mode such as a Session Manager, one instance will be in active state and the other one will be in hot standby state. When the active instance is shut down to be patched, the standby instance becomes active to prevent loss of service.
For
For more information about Network Elements and their associated service impacts during patch upgrades, see Table 11 "Service impacts to Network Elements during patching" (page 79).
Table 11
Service impacts to Network Elements during patching
Network Element | Client impact |
| Subscriber impact |
|
|
|
|
Accounting | When the accounting manager |
| None. |
Managers | is stopped, billing information |
|
|
| continues to be cached on the |
|
|
| session manager servers as |
|
|
| disk space allows. After the |
|
|
| Accounting Manager is back in |
|
|
| service, the cached information |
|
|
|
|
| |
|
| ||
| Application Server 5300 | ||
| Nortel AS 5300 Installation | ||
| 01.04 | ||
| 4 November 2008 | ||
