|
|
This chapter provides procedures for some commonly performed Cisco ONS 15200 tasks, including creating a new user, backing up the database, and upgrading the Subnetwork Manager.
To add a user to the database, perform the following steps. See the "Create User" section for more information about the create user command. See the "Password" section for more information on password restrictions.
Step 1 Log in as an administrator to the NCB where you want to add a user.
Step 2 At the NCB:> prompt, type create user <username>, where username is the name of the user you are creating. Press Enter. The user is created and you are now at the user name directory.
Step 3 Type password <userpass>, where userpass is the password you want to assign that user. Press Enter.
Step 4 Type privileges administrator, privileges guest or privileges operator, depending on the user privilege level you want to assign that user. Press Enter.
Step 5 To list the parameter values for that user, type l v and press Enter.
Step 6 To save the user name to the NCB, type commit user username and press Enter. The user name will automatically be restored after the system restarts.
Before you can back up the database, you must know the IP address of the system and make sure your PC is properly configured to communicate with the 15200 system. Contact your system administrator for more information about your network configuration.
If you want the database files to be saved in a particular folder, make sure the destination folder is created on your PC's C:\ drive.
Perform the following steps to back up the 15200 database:
Step 1 To open a command prompt window, select Start > Programs and select Command Prompt (it may be under Accessories).
Step 2 At the C:\ prompt, type cd <foldername>, where foldername is the destination folder where you want to save the database files. Press Enter.
Step 3 To ftp the 15200, type ftp <ipaddress>, where ipaddress is the IP address of the 15200 system whose database you want to back up. Press Enter.
Step 4 At the ftp prompt, log in as a user with administrator privileges.
Step 5 To list all of the database files, type dir and press Enter.
Step 6 Type get <filename>, where filename is the name of the first file that appears in the list, and press Enter.
Step 7 Repeat Step 6 for all of the files listed after the dir command.
Step 8 In your C:\ directory, find the destination folder and verify that all of the files you extracted are there.
Step 9 Close the ftp window.
Using the CLI, you can view performance monitoring (PM) and event logs for a particular CLIP module using after saving them to a spreadsheet program such as Microsoft Excel. See "General Commands" for information on the event and PM logs.
Perform the following steps to view the event or either performance monitoring log through spreadsheet software.
Step 1 Start a telnet session and log in as an operator user.
Step 2 Type open followed by pmlog15, pmlog24, or eventlog. Press Enter.
Step 3 At the log's prompt, type read and press Enter to make sure there are events recorded in the log you want to export.
Step 4 Start an FTP session and log in as an administrative user.
Step 5 To change the directory to the drive that contains the log files, type cd /1 and press Enter.
Step 6 To see a list of all files in that directory, type dir and press Enter.
Step 7 To change the PC's directory to the folder where you want to store the log file, type lcd followed by folder name.
Step 8 To place a copy of the log into the folder on your local PC drive, type get followed by pmlog15, pmlog24, or eventlog and press Enter.
Step 9 Open the spreadsheet program where you want to view the log and import the file.
Before you upgrade the Subnetwork Manager (SNM), perform the database back up procedure (see the "Backing Up the Database (Windows)" section) and obtain the location of the SNM upgrade files on your PC. You must also be connected to the 15200 over an Ethernet cross-over or straight cable, depending on how you are connected to the network.
Perform the following steps to upgrade the SNM from a previous 1.0.x software version to a subsequent 1.0.y version:
Step 1 To telnet the 15200, type telnet <ipaddress>, where ipaddress is the IP address of the 15200 system where you want to log in. Press Enter.
Step 2 Log in as a user with administrator privileges.
Step 3 At the NCB:> prompt, type configure system and press Enter.
Step 4 At the NCB:= prompt, type remove 0 qdbs.cfg and press Enter.
Step 5 Type remove 0 snm.out, where snm.out is the name of the boot file, and press Enter.
Step 6 Type defrag 0 and press Enter. (This process may take up to a minute.)
Step 7 Type ldboot 0 snm.out 10 and press Enter.
Step 8 Close the telnet session.
Step 9 To copy the SNM upgrade files from your local drive, open a command prompt window by selecting Start > Programs and select Command Prompt (it may be under Accessories).
Step 10 At the C:\ prompt, type cd <foldername>, where foldername is the folder where the new snm.out and qdbs.cfg files reside. Press Enter.
Step 11 To ftp the 15200, type ftp <ipaddress>, where ipaddress is the IP address of the 15200 system where you want to copy the SNM upgrade. Press Enter.
Step 12 At the ftp prompt, log in as a user with administrator privileges.
Step 13 Type ascii and press Enter.
Step 14 Type put qdbs.cfg and press Enter.
Step 15 Type bin and press Enter.
Step 16 Type put snm.out and press Enter.
Step 17 Close the ftp window.
Step 18 To telnet the 15200, type telnet<ipaddress>, where ipaddress is the IP address of the 15200 system where you want to log in. Press Enter.
Step 19 Log in as a user with administrator or operator privileges.
Step 20 At the NCB:> prompt, type configure system and press Enter.
Step 21 At the NCB:= prompt, type reboot and press Enter. The system will reboot with the upgraded SNM.
Perform the following steps to upgrade the SNM from a 1.0 software version to 1.1. You must first upload a slightly modified version of SNM 1.0, snm-1.0_to_1.1_upgrade. This version has an extra command, commit upgrade, that performs an inventory of all CLIP modules, SNMs, and the sub-network, and produces a command file, upgrade.cfg, that is stored on the NCB.
Step 1 Open a command prompt window and change to the directory where the folder that contains the SNM Upgrade version files resides by typing cd followed by the path to that folder.
Step 2 To list all files in SNM Upgrade folder, type dir. Make sure that the snm.out and qdbs.cfg files are present.
Step 3 Open another command prompt window and change to the directory where the folder that contains the SNM Upgrade version files resides by typing cd followed by the path to that folder.
Step 4 To ftp the 15200 system you want to upgrade, type ftp <ipaddress>, where ipaddress is the IP address of the NCB that contains the SNM to be upgraded. Press Enter.
Step 5 Log in as an administrator.
Step 6 To delete the snm.out file, type delete snm.out and press Enter.
Step 7 Repeat Step 6 for the qdbs.cfg file.
Step 8 Start a telnet session and log into the CLI as an operator.
Step 9 Type configure system.. Press Enter.
Step 10 Type list 0 and press Enter. Confirm that the snm.out and qdbs.cfg files are marked for deletion.
Step 11 To delete the snm.out and qdbs.cfg files type defrag 0 and press Enter.
Step 12 Return to the ftp session window and type put snm.out to copy the snm.out file to the SNM on the NCB.
Step 13 Repeat Step 12 for the qdbs.cfg file.
Step 14 To exit the ftp session, type bye and press Enter.
Step 15 Return to the telnet session window, type reboot, and press Enter. The NCB will reboot. (This may take a 30-45 seconds.)
Step 16 Press Enter. You will see the following message: Connection to host lost.
Step 17 Start a new telnet session and log in as an operator.
Step 18 Type show inventory and make sure all of the CLIPs in the system appear in the inventory.
Step 19 To create the upgrade.cfg file, type commit upgrade and press Enter.
Step 20 Type configure system and press Enter.
Step 21 To make sure the upgrade.cfg file was created, type list 0 and press Enter. You should see the upgrade.cfg file in the list of files.
Step 22 Type exit and press Enter. Repeat to exit the telnet session.
Step 23 Repeat Steps 3 through 17 using the location of the 1.1 software version files.
Step 24 Open a command prompt window and type ftp <ipaddress>, where ipaddress is the IP address of the NCB that contains the SNM to be upgraded. Press Enter.
Step 25 Log in as an administrator.
Step 26 Type delete network.cfg and press Enter to delete the network.cfg file.
Step 27 Type bye to exit the ftp session.
Step 28 Return to the telnet session. Type show inventory and observe that the NCB is the only object in the inventory.
Step 29 To set the unitid for this SNM to snm1, type configure snm snm_xxx and press Enter. Type unitid snm_1. and press Enter.
Step 30 To commit the change to the database, type commit. Then type exit to go back to the first command level.
Step 31 Type show inventory and press Enter. Make sure all of the hardware in the ONS 15200 system appears in the inventory. If all of CLIP modules do not appear in the inventory, repeat this step. (This process may take 30-45 seconds.)
Step 32 Execute the upgrade.cfg file by typing source 0 upgrade.cfg and press Enter. You will see commands scroll down the window as the script is executed.
The system will automatically create necessary objects and make configurations to reflect the system inventory. The upgrade.cfg command file is a script that performs the following actions:
Step 33 After the commands executed by the script are complete, type configure system to enter system configuration mode.
Step 34 Type list 0 and press Enter to verify that the files are marked for deletion.
Step 35 Type defrag 0 and press Enter to remove the marked files.
Step 36 Type exit and press Enter to return to the NCB:> prompt.
Step 37 Type configure network and press Enter.
Step 38 Type configure mcu mcuname, where mcuname is the name of the MCU you want to configure, and press Enter.
Step 39 Type show inventory and press Enter. Make sure all of the hardware in the ONS 15200 system appears in the inventory.
Posted: Mon Sep 30 20:31:24 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.