|
|
This chapter describes the procedures that operate on the NE embedded software, and contains the following sections:
The EMS database backup utility allows you to back up the existing configuration of a node to a TFTP server. After the database has been backed up, you can restore the node configuration, if needed. The database restore procedure is described in the "Database Restore" section.
Before beginning the database backup, complete the following tasks:
To back up the system database, perform the following steps starting in node view:
Step 2 Select the Database Backup tab from the NE provision window. (See Figure 14-1.)

Step 3 Complete the following fields to begin the database backup procedure:
Step 4 Click Apply to save the backup configuration.
Step 5 Click Backup to begin the database backup.
The Cisco 6732 software upgrade procedure consists of the following sections:
Before beginning the embedded software upgrade, complete the following tasks:
![]() |
Note When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of COT is mishandled, the entire network can be lost. Upgrade tests and sample enhancements should be made at the edge node. If the upgrade tests fail on the edge nodes, do not attempt to upgrade the COT node. |
Step 2 Double-click the node nameplate to launch the NE provision window.
Step 3 Click Common Control Card Switch Over in the function bar to display the switchover window. (See Figure 14-2.)

Step 4 Look at the Active MCC field. EMS identifies the active MCC.
Step 5 The MCC that is not active is called the standby MCC. For example, if MCC-A is active, then MCC-B is the standby MCC.
Step 6 Click Exit to return to node view.
Step 2 Set the Admin Status field to OutOfService.
Step 3 Click Apply to place the MCC card out of service.
Step 4 Click Exit to return to node view.
Step 2 Click Software Upgrade in the function bar to display the software upgrade window. (See Figure 14-3.)

Step 3 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 4 In the Software Image File Name field, enter SwLoad.fbx.
Step 5 In the Upgrade Software to Main Common Control Card field, select the standby MCC card.
![]() |
Note Upgrade the MCC that is not shown in the Active Main Control Card field. For example, if EMS shows that the active main control card is A, you must select B for the upgrade field. |
Step 6 Click Apply to confirm the host IP address and path to the image filename.
Step 7 Click Upgrade to download the embedded software image into the Flash memory of the standby MCC card.
Step 8 EMS displays a progress bar. Wait until the software upgrade is complete.
![]() |
Caution If EMS is unable to complete the embedded software upgrade, an error message is displayed at the bottom of the NE provision window. This error message is also displayed in the problem list of the MCC card. In this case, do not reset the MCC card; restart the embedded software upgrade process. |
Step 9 Click Exit to return to node view.
Step 10 Select File > Exit from the menu bar to return to net view.
Step 2 Click MCC Reset in the function bar to open the MCC reset window. (See Figure 14-4.)

Step 3 In the Reset MCC field, select the standby MCC (A or B)
Step 4 Click Reset to reset the selected MCC. The MCC begins a reset and initialization procedure.
![]() |
Note Allow 30 to 45 seconds for the MCC to complete the reset procedure. |
Step 5 Click Exit to return to net view.
Step 2 Double-click the standby MCC card. EMS launches the plugin card provisioning window. (See Figure 14-5.)

Step 3 Set the Admin Status field to InService.
Step 4 Click Apply to place the card in service.
Step 5 Click Exit to return to node view.
Step 2 Click Software Upgrade in the function bar to display the software upgrade window.
Step 3 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 4 In the Software Image File Name field, enter SwLoad.fbx.
Step 5 In the Upgrade Software to Main Common Control Card field, select the active MCC card. The active MCC card is identified in the Active Main Control Card field.
Step 6 Click Apply to confirm the host IP address and path to the image filename.
Step 7 Click Upgrade to download the embedded software image into the Flash memory of the active MCC card.
Step 8 EMS displays a progress bar. Wait until the software upgrade is complete.
![]() |
Caution If EMS is unable to complete the embedded software upgrade, an error message is displayed at the bottom of the NE provision window. This error message is also displayed in the problem list of the MCC card. In this case, do not reset the MCC card; restart the embedded software upgrade process. |
Step 9 Click Exit to return to node view.
Step 10 Select File > Exit from the menu bar to return to net view.
Step 2 Click Common Control Card Switch Over in the function bar. (See Figure 14-6.)

Step 3 Click Switch to switch control from the active MCC to the standby MCC.
Step 4 Click Exit to return to node view.
![]() |
Caution The following procedure reboots the line interface modules and effectively takes them out of service. Any traffic being carried on the cards is dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
Step 2 Right-click the node that you are upgrading, and select Node Critical Commands from the popup menu.
Step 3 Click Line Card Reset in the function bar to open the line card reset window. (See Figure 14-7.)

Step 4 Set the Reset field to Yes.
Step 5 In the Equipped Cards list, highlight all line cards to be reset.
![]() |
Note The BPS-HP and AMM service modules do not need to be reset. |
Step 6 Click Apply to reset all selected line cards.
This section describes the software upgrade procedure for the Cisco 6705.
Before beginning the embedded software upgrade, complete the following tasks:
![]() |
Note When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of COT is mishandled, the entire network can be lost. Upgrade tests and sample enhancements should be made at the edge node. If the upgrade tests fail on the edge nodes, do not attempt to upgrade the COT node. |
Perform the following steps to upgrade or install the embedded software:
Step 2 From node view, double-click the node nameplate to launch the NE provision window.
Step 3 Select Software Upgrade from the function bar to display the software upgrade window. (See Figure 14-8.)

Step 4 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 5 In the Software Image File Name field, enter SwLoad.fbx.
Step 6 The Upgrade Software to Main Common Control Card field should be set to A; the Cisco 6705 has only one MCC card, identified as A.
Step 7 Click Apply to confirm the host IP address and path to the image filename.
Step 8 Click Upgrade to download the embedded software image into the Flash memory of the MCC card.
![]() |
Caution If EMS is unable to complete the embedded software upgrade, an error message is displayed in the EMS NE provision window. In this case, do not reset the MCC card; restart the embedded software upgrade process. |
Step 9 The MCC card must be reset before the new embedded software becomes active. Use one of the following procedures to reset the MCC card:
![]() |
Caution Resetting the MCC card also resets all line cards in the Cisco 6705, momentarily placing the line cards out of service. Any traffic being carried on the line cards is lost or dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
This section describes the software upgrade procedure for the Cisco IAD1101.
Before beginning the embedded software upgrade, complete the following tasks:
![]() |
Note When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of COT is mishandled, the entire network can be lost. Upgrade tests and sample enhancements should be made at the edge node. If the upgrade tests fail on the edge nodes, do not attempt to upgrade the COT node. |
Perform the following steps to upgrade or install the embedded software:
Step 2 From node view, double-click the node nameplate to launch the NE provision window.
Step 3 Select Software Upgrade from the function bar to display the software upgrade window. (See Figure 14-9.)

Step 4 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 5 In the Software Image File Name field, enter SwLoad.fbx.
Step 6 The Upgrade Software to Main Common Control Card field should be set to A.
Step 7 Click Apply to confirm the host IP address and path to the image filename.
Step 8 Click Upgrade to download the embedded software image into the Flash memory of the MCC card.
![]() |
Caution If EMS is unable to complete the embedded software upgrade, an error message is displayed in the EMS NE provision window. In this case, do not reset the Cisco IAD1101; restart the embedded software upgrade process. |
Step 9 The Cisco IAD1101 must be reset before the new embedded software becomes active. From the EMS NetView, right-click on the IAD1101 node icon and select Node Critical Commands. Enter the password when prompted, then select the MCC Reset tab.
![]() |
Caution Resetting the Cisco IAD1101 also resets all lines and cards in the Cisco IAD1101, momentarily placing the lines out of service. Any traffic being carried on the line cards is lost or dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
The following embedded software utilities are launched from the node critical commands window:
![]() |
Caution These commands affect service; any user traffic passing through the node will be dropped. |
To launch the node critical commands window, complete the following steps:
Step 2 Select Node Critical Commands.
Step 3 Enter the node critical commands password. The node critical commands window opens, displaying the database restore function.
If necessary, contact your EMS administrator to obtain the correct node critical commands password.
![]() |
Note Your EMS workstation requires a special password file to launch the node critical commands window. If EMS cannot locate the password file, you will not be able to launch the node critical commands window. Contact your EMS administrator to obtain the password file. |
Use the database restore function to restore a backedup database to an MCC on the Cisco 6732 or Cisco 6705. See the "Backing Up the System Database" section for the database backup procedure.
Table 14-10 shows the database restore window.

To restore a backed up database to an MCC, complete the following steps:
Step 2 Click Restore to upload the database file from the TFTP server to the selected MCC.
![]() |
Caution Erasing the database removes all card and line provisioning, including cross connects and inter node connections. |
To erase a database from an MCC, complete the following steps:
Step 2 Click Database Erase in the function bar to open the database erase window. (See Table 14-11.)

Step 3 Select the MCC to be erased in the Database on Main Common Control Card field.
Step 4 Click Erase.
The MCC reset function resets the main control card (MCC) and reloads the embedded software.
![]() |
Caution Resetting the MCC causes all lines and cards in the NE to be reset as well, momentarily placing the line cards out of service. Any traffic being carried on the line cards is lost or dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
To reset the MCC, perform the following steps from the node critical commands window:
Step 2 Click MCC Reset from the function bar to open the MCC reset window. (See Table 14-12.)

Step 3 Select the MCC to be reset (A or B) in the Reset MCC field.
Step 4 Click Reset to reset the selected MCC. Allow several minutes for the MCC to reset and reload the system software.
![]() |
Caution Do not power down the NE or remove the MCC during an MCC reset. The MCC must finish loading the system software before the MCC can be safely powered down, removed, reset, or reprovisioned. |
Step 5 Performing an MCC reset erases the internal clock on the NE. To set the time of day on the NE, see the "Provision NE Clock" section of "Initial Node Provisioning."
The line card reset function resets all selected cards in the NE.
![]() |
Caution The following procedure reboots the selected line cards and effectively takes them out of service. Any traffic being carried on the cards is dropped. Proper planning and system coordination must be exercised to eliminate or reduce the potential for interrupted subscriber service. |
To reset all selected cards in the NE, complete the following steps:
Step 2 Click Line Card Reset on the function bar, to open the line card reset window. (See Figure 14-13.)

Step 3 Highlight all line cards you are resetting in the Equipped Cards list.
Step 4 Set the Reset field to Yes.
Step 5 Click Apply.
The change password function is used to change the node critical commands password. This password is used to launch the node critical commands window. (See Figure 14-14.)
![]() |
Note The node critical commands password is not the password used to log in to EMS. To change the EMS login password for a particular user, see the "EMS User Administration" section of Chapter 15. |
To change the node critical commands password, complete the following steps:
Step 2 Click Change Password on the function bar to open the change password window. (See Figure 14-14.)

Step 3 Complete the following fields to change the node critical commands password:
Step 4 Click Save.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Sep 25 17:03:01 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.