l Do not modify the system time when the T2000 is running. Set the system time when you
install the T2000.
– If the system time of the server needs to be modified, log out of the T2000 server and
then modify the system time. After the modification, restart the T2000 server.
– If the system time of the client needs to be modified, log out of the T2000 client and
then modify the system time. After the modification, restart the T2000 client.
l Do not modify the name and IP address of the computer where the T2000 server is installed,
unless required. Otherwise, the communication among NEs may fail.
Precautions for the Operation of the T2000
When you operate the T2000, be aware of the following precautions:
l When the T2000 is running, ensure that the data is consistent between the T2000 and the
NE.
– When the data on an NE has been configured and the NE runs properly, use the upload
or synchronization function to keep the data consistent between the T2000 and the NE.
– When the NE data stored on the NE has errors and the NE data stored on the T2000 is
correct, use the download or restoration function to keep the data consistent between the T2000 and the NE.
l To change the configuration data, abide by the following rules:
– Before you change the configuration data, upload the NE data to keep the NE data
consistent between the T2000 and the NE.
– Before you change the configuration data, back up the NE database and the T2000
database, so that the data can be restored in the case of an operation failure.
– After you change the configuration data, back up the NE database and the T2000
database, so that the data can be restored in the case of an NE anomaly.
l Before you set parameters, query the latest data from the NE.
l Be very careful before a dangerous operation is performed. Usually the T2000 presents a
prompt to remind of the danger before a dangerous operation is performed.
l Periodically back up the MO data to minimize the loss caused by system anomalies. – Back up the MO data of the T2000 every month.
– When the service configuration data is changed, immediately back up the MO data of
the T2000.
l Periodically clear outdated backup data to ensure that there is sufficient disk space for new
backup data.
l For an T2000 system that has multiple clients, you are recommended to use only one client
2
Routine maintenance
About This Chapter
Routine maintenance includes the remote maintenance (on the T2000) and spare parts maintenance. Check the current state of the equipment to determine the working condition of the equipment in time and to prevent any problem from occurring; Check the spare parts to ensure that the spare parts can replace faulty components that operate in the network when a board is faulty.
2.1 Routine Maintenance Items and Periods
To ensure the stable and long-term running of the equipment, the equipment should be periodically maintained. This section describes the routine maintenance items and maintenance periods of the equipment according to different maintenance scenarios.
2.2 Guide and Record Table for Routine Maintenance in the NMS Center
To ensure the normal running of the equipment, check the running status of the equipment, back up the data periodically by using the T2000 and record the maintenance results at the network management center.
2.3 Field Maintenance and Record Table for Outdoor Equipment
To ensure the smooth operation of the ODU, you need to periodically check the ODU on site and record the associated information.
2.4 Guide and Record Table for Routine Maintenance of the Spare Parts
To ensure that the spare parts of the equipment are normal, check the spare parts in the storehouse regularly and record the check results.
2.1 Routine Maintenance Items and Periods
To ensure the stable and long-term running of the equipment, the equipment should be periodically maintained. This section describes the routine maintenance items and maintenance periods of the equipment according to different maintenance scenarios.
Table 2-1 lists the routine maintenance items and periods. Table 2-1 Maintenance items and periods
Maintena nce Owner
Maintena
nce Site Maintenance Item Maintenance Period
T2000 operator
NMS center Checking the status of the NE and boards Daily
Browsing network-wide alarms Daily
Browsing abnormal events Daily
Browsing the current performance events Daily Browsing the performance events of the
RMON statistics group
Daily
Checking the optical power Daily
Browsing DCN Communication Status Daily
Browsing the running status of dynamic tunnel Daily
Browsing the PW working status Daily
Browsing the history performance events Monthly Browsing the RMON history performance
events
Monthly Backing up the MO data of the T2000 Monthly
Backing up the NE database Monthly
Testing the IF 1+1 Switching Monthly
Maintenanc e engineer
Installation site
Checking the ODU Half-yearly
Checking the Hybrid Coupler Half-yearly
Checking the Antenna Half-yearly
Checking IF Cables Half-yearly
Maintenanc e engineer
Spare parts center
2.2 Guide and Record Table for Routine Maintenance in the
NMS Center
To ensure the normal running of the equipment, check the running status of the equipment, back up the data periodically by using the T2000 and record the maintenance results at the network management center.
2.2.1 Checking the Status of the NE and Boards
Regularly check the status of the NE and boards on the NE. In this way, the anomalies can be detected and then handled in time.
2.2.2 Browsing Network-Wide Alarms
Regularly browse alarms to detect and rectify faults in time.
2.2.3 Browsing Abnormal Events
Regularly browse performance events of an NE. In this way, you can determine the current running status of the NE and avoid the faults that are likely to occur.
2.2.4 Browsing the Current Performance Events
Browse the current performance events periodically to check the current running state of the equipment. In this way, potential faults can be eliminated in time.
2.2.5 Browsing the Performance Events of the RMON Statistics Group
Browse the performance events of the RMON statistics group periodically. this helps you to learn the running status of the ports and links, and the quality of services (QoS).
2.2.6 Checking the Optical Power
If the mean transmitted power and the receive power of the optical interface is excessively low or high, bit errors occur or the optical components may be damaged, and thus services are affected. To prevent this problem from occurring, you should check the optical power regularly of every optical interface of the optical interface board.
2.2.7 Browsing the History Performance Events
Browse the history performance events periodically to learn the long-term running state of the equipment. In this way, potential faults can be eliminated in time.
2.2.8 Browsing the RMON History Performance Events
Browse the history RMON performance events periodically. This helps you to understand the running status of the ports and channels, and the long-term quality of services.
2.2.9 Backing up the MO Data of the T2000
Periodically back up the T2000 MO data. When the T2000 data is lost, use the MO data to fast restore the T2000 data.
2.2.10 Backing up the NE Database
To ensure that the NE data can be quickly restored after the database of the system control board is lost or the power failure occurs to the equipment, you should back up the NE database periodically.
2.2.11 Testing the IF 1+1 Switching
Periodically testing the IF 1+1 switching helps you to check whether the equipment can switch over normally.
2.2.12 Maintenance Record Table
2.2.1 Checking the Status of the NE and Boards
Regularly check the status of the NE and boards on the NE. In this way, the anomalies can be detected and then handled in time.
Prerequisite
l The T2000 must be started in the NMS center.
l The NE must be configured and the NE configuration data must be uploaded to the T2000. l You must be a T2000 user with the "NE Monitor" authority or higher.