Chapter 2 M2000 Routine Maintenance
2.3 Routine Maintenance Items
This section provides daily, weekly, and monthly maintenance items.
2.3.1 Daily Maintenance
Table 2-1 Daily maintenance checklist
SN. Item Operation instruction Remark
Checking operational status of the client Topology Management
T1 Check the operational status of the client
Log in to the M2000 client as admin.
The status bar of the client indicates that the communication between the client and all the servers is normal.
All NE icons on the topology are normal and without any cross.
T2
Display the O&M interface of the network element (NE).
Select the desired NE, right-click the mouse, and then select LMT.
The precondition is that the client PC is installed with the LMT program of this NE. Configuration Management C1 View the configuration information of equipment in the whole network through the centralized configuration management system.
Start the centralized configuration
management system, and expand nodes of the configuration tree on the left to view the configuration data.
C2 Synchronize the configuration data manually.
Select the NE icon on the configuration tree, right click the mouse, and select [Refresh NE]. Fault Management
F1
Check the real-time alarm information.
Check whether the alarm information generated by the host can be viewed on the centralized fault management system.
The NE BAM alarms can be reported accurately and promptly.
F2
Query and browse alarms at the fault management system.
Check whether alarm information can be queried and browsed according to preset conditions at the centralized fault management system.
SN. Item Operation instruction Remark
P1 Check the task statuses.
Check whether there is suspended task in the task list at the centralized performance management system. P2 Check the reporting of performance tasks.
Query the task result and see whether the result can be queried correctly.
All the task results can be reported normally.
If error messages are returned, handle the problem as below:
1. If the returned message is “This task does not exist”, re-register the task. 2. If the returned message is “The object does not exist” or “The object does not respond”, it indicates that the operation results in the change of object and you need to re-register the task, or delete the original object and then add a new one. 3. If the returned task status is
“suspended”, activate this task.
P3 Check the performance task management function. Activate, suspend, or delete a performance task and check whether the operation is successful.
User operation log management U1 View the system log.
Select the menu [View/System Log] on the M2000 remote workstation (RWS). Checking the operational status of server
S1
Check the harddisk space of the server. df -k
Check the "capacity” column in the output result.
Normally, at least 20% of the harddisk space should be available.
If the capacity of a file system approaches 80%, you need to remove the useless files on this system or add harddisk to this system.
SN. Item Operation instruction Remark
S2 Check the time of the M2000 server. date mmddHHMM[[cc]yy][. SS]
The server time must be consistent with the local standard time.
Execute the command date to output the current time. If the result is inconsistent with the local standard time, correct the server time.
For example, to change the time to 14:53:43 on Friday March 28, 2003, execute the following command:
#date 0328145303.43 Fri Mar 28 14:53:43 GMT 2003
S3 Check the CUP usage of the
server. vmstat 5 5
# vmstat 5 5
procs memory page disk faults cpu r b w swap free re mf pi po fr de sr s0 s6 -- -- in sy cs us sy id 0 0 0 1054080 35400 4 16 3 15 12 0 0 15 0 0 0 398 23171 464 13 7 81 0 0 0 1022608 18336 2 1 1 28 27 0 0 13 0 0 0 384 28526 560 16 7 76 0 0 0 1022608 18248 1 0 0 14 9 0 0 18 0 0 0 415 30853 565 16 9 76
The CPU idle ratio cannot be lower than 40%. The id value (idle ratio) under the CPU item cannot be too low.
2.3.2 Weekly Maintenance
Table 2-2 lists the weekly maintenance items of the M2000 system.
Table 2-2 Weekly maintenance checklist
SN. Item Operation instruction Remark
1 Check the database status.
Execute the following command as m2000: $isql -Usa
-Pserver1234
1> sp_helpdb 2> go
The database runs normally. No database is off line. There are at least six databases, including cfgdb, pmdb, alarmdb, comdb, timerdb, and logdb.
SN. Item Operation instruction Remark
2 Check the space of alarmdb.
1>sp_helpdb alarmdb 2> go
3 Check the space of cfgdb. 1>sp_helpdb cfgdb 2> go 4 Check the space of comdb. 1>sp_helpdb comdb 2> go
5 Check the space of pmdb.
1>sp_helpdb pmdb 2> go
6 Check the space of timerdb.
1>sp_helpdb timerdb 2> go
The available space of each database must be 200 MB at least. 7 Check backup files of each database.
Check whether the suffix of each backup file under the directory /export/home/m2000/ba kcup2 contains the date which indicates the day before the file backup day.
The following lists the auto backup policies of the M2000 system:
Incremental backup of logs of five databases at 22:00 every day. The databases include comdb, timerdb, logdb, cfgdb, and pmdb.
Full backup of all the data and logs of six databases (including comdb, timerdb, logdb, cfgdb, pmdb, and alarmdb) at 00:00 every Sunday. Deletion of all the backup files of the previous week under the directory /export/home/m2000/backup2 and moving the log files of the current week from the directory /export/home/m2000/backup to /export/home/m2000/backup2 at 23:57 every Saturday.
Backup of the data and logs to the tape machine (if installed) at 10:00 every Monday. You can replace the tape after 10:00 every Monday to obtain the backup data of the last week.
The system carries out these backup operations automatically.
8 Remove outdated files.
Log in as m2000 and go to the log directory to delete all the files with the suffix “bak”:
rm *.bak
It is recommended you delete the outdated log files periodically.
9 Check the tape machine.
mt status The execution result shows that the status is OK.
2.3.3 Monthly Maintenance
Table 2-3 lists the monthly maintenance items of the M2000 system. The major task is to check the physical equipment of the system.
Table 2-3 Monthly maintenance checklist
SN Item Operation instruction Remark
1
Check the system power indicators.
Observe whether the indicator on each power supply module is on.
In normal case, all the power indicators are on. For example, the following power indicators (green) are on:
z Sun Netra20 active and standby power
supply indicators (DC-A and DC-B)
z POWER indicator z SYSTEM indicator z DISK0-Active z DISK1-Active 2 Check system indicators.
Observe all the indicators on the front and rear panels of the host and disk array.
No maintenance indicator or yellow indicator should be on or flashing. For the Netra20, the POWER and SYSTEM indicators on the front panel should be ON (green).
If an error occurs, the ALARM1, ALARM2, and FAULT indicators are on (yellow).
If the disk array is configured, the RUN indicator should be ON.
3 Check the hardware of the system.
Check all the external indicators.
Confirm that hardware connections are correct and the operation is normal.
LAN Switch: The power indicator is on. The indicator of the network port connected with the network cable is flashing.
If the terminal HUB is configured, the POWER, UNIT, and NET indicators are on, ACTIVE indicator flashes slowly, and the rest indicators are off.