When the OSS is loaded with the U2000-T MIB, the SNMP NBI provides subinterfaces to enable the following functions: reporting alarms automatically and synchronizing alarms.
6.1 U2000 MIB Subinterfaces
When the OSS is loaded with the U2000 MIB, the SNMP NBI provides subinterfaces to enable the following functions: reporting alarms automatically, and synchronizing, clearing,
confirming, acknowledging, unacknowledging, and filtering alarms.
CAUTION
Ensure that the U2000 MIB has been loaded to the OSS. To load the U2000 MIB, set the MIB type to U2000 MIB when deploying the SNMP NBI.
6.1.1 Reporting Real-Time Alarms
You do not need to set any parameters for the OSS to receive alarm packets from the U2000 through the SNMP NBI. After the SNMP NBI is properly deployed on the U2000, alarms will be reported to the OSS in real time.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the U2000, the OSS can receive real-time alarms.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring SNMP.
6.1.2 Changing Filter Criteria
The SNMP NBI allows the OSS dynamically to change filter criteria during its running so only required alarms are reported.
Function
The OSS can call the alarm filter interface to change alarm filter criteria dynamically when the SNMP NBI is working.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.5. The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmFault(3).thirdNMSFaultFilter(5)
Object Type Max Access Description
thirdNMSFaultFilter Octet string read-write Indicates that alarm
filter criteria are changed dynamically.
Setting Method
The OSS can set the value of the MIB node to change the alarm filter criteria. The format is as follows:
IPAddress:Port:AlarmFilterLevel:AlarmCategoryFilter
Table 6-1 Format description - changing filter criteria Field Description
IPAddress Indicates the IP address used by the OSS. This IP address is the trap- receiving IP address preset for third-party NMSs when the SNMP NBI is deployed.
Port Indicates the port used by the OSS. This port is the trap-receiving port preset for third-party NMSs when the SNMP NBI is deployed.
AlarmFilterLe vel
Indicates the severity of an alarm.
Four binary digits are used to represent critical, major, minor, or warning in descending order.
A binary digit is 0 or 1.
l 1: indicates that the alarms of the corresponding alarm severity are filtered out and the OSS cannot receive alarms with the level. l 0: indicates that the alarms of the corresponding alarm severity are
reported and the OSS can receive alarms with the level. AlarmCategor
yFilter
Indicates the category of an alarm.
Six binary digits are used to represent event, fault, clear, acknowledge, unacknowledge or change alarm in descending order.
l 1: indicates that the alarms of the corresponding category are filtered out and the OSS cannot receive alarms with the category.
l 0: indicates that the alarms of the corresponding category are reported and the OSS can receive alarms with the category.
Sample
Prerequisite
l The IP address of the OSS is set to 10.70.73.97 and the port for receiving alarms 6666. l The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms. Purpose
To change the filter criteria as follows: alarm severity (critical or major) and alarm category (fault or clear).
Table 6-2 shows the parameters of this sample.
Table 6-2 Sample parameters - changing filter criteria
Parameter Value MIB Object
The IP of upper-layer NMS 10.70.73.97 10.70.73.97
Receive Trap Port 6666 6666
Alarm Severity to be Reported
Critical, Major 0011
Alarm Category to be Reported
Fault Alarm, Clear 100111
Procedure
The OSS sets thirdNMSFaultFilter to 10.70.73.97:6666:0011:100111. The OSS receives responses from the U2000, indicating that the filter criteria are changed successfully. The OSS will then receive the required alarms only.
6.1.3 Synchronizing Alarms
The SNMP NBI allows the OSS to initiate the synchronization operation to ensure that the alarm information on the OSS and the U2000 is consistent.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data consistency and can also stop synchronization.
After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform the OSS that the alarm synchronization is started.
When the synchronization is complete or stopped, the U2000 will send traps through the SNMP NBI to inform the OSS that the alarm synchronization is ended.
Figure 6-1 Alarm synchronization process
SNMP NBI NMS/OSS
Set alarm
synchronization start node Report alarm synchronization start trap
Report alarm
synchronization result trap All Alarms
are reported Set alarm
synchronization start node Report alarm synchronization stop trap
Report the alarm synchronization stop trap
. . . . . . . . Operation Description
Synchronize alarms 1. The OSS synchronizes alarms.
2. The U2000 sends traps through the SNMP NBI to inform the OSS of the start of alarm synchronization.
3. The U2000 sends traps through the SNMP NBI to report the required alarms saved in the database.
4. After the alarms are reported, the U2000 sends traps through the SNMP NBI to inform the OSS of the end of alarm synchronization. Stop the alarm
synchronization
1. The OSS stops the alarm synchronization.
2. The U2000 sends traps through the SNMP NBI to inform the OSS of the stop of alarm synchronization.
NOTE
For details of the alarm synchronization start trap, see C.3.2 Active Alarm Synchronization Start Trap.
For details of the alarm synchronization result trap, see C.3.3 Active Alarm Report Trap.
For details of the alarm synchronization stop trap, see C.3.4 Active Alarm Synchronization End Trap.
MIB Definition
There are two MIB nodes for alarm synchronization: hwNmNorthboundEventSynchronizationCommandStart and
hwNmNorthboundEventSynchronizationCommandStop. The former indicates start alarm synchronization, while the latter indicates stop alarm synchronization.
The OIDs are 1.3.6.1.4.1.2011.2.15.1.7.7.4 and 1.3.6.1.4.1.2011.2.15.1.7.7.5.
iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization (7).hwNmNorthboundEventSynchronizationCommandStart(4) iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization (7).hwNmNorthboundEventSynchronizationCommandStop(5)
Object Syntax Max Access Description
hwNmNorthboundE ventSynchroniza- tionCommandStart
Octet string read-write Indicates that the
alarm synchronization is started. hwNmNorthboundE ventSynchroniza- tionCommandStop
Octet string read-write Indicates that the
alarm
synchronization is stopped.
Setting Method
Start alarm synchronization.
The OSS can set the value of the MIB node to start alarm synchronization within a specified time. The format is as follows:
IP:port:start time:end time Stop alarm synchronization.
The OSS can set the value of the MIB node to stop alarm synchronization. The format is as follows:
IP:port
NOTE
You do not need to set the start and end time to stop the alarm synchronization.
Table 6-3 Format description - synchronizing alarms Parameter Description
IP Indicates the IP address used by the OSS. This IP address is the trap-
receiving IP address set for third-party NMSs when the SNMP NBI is deployed.
port Indicates the port used by the OSS. This port is the trap-receiving port set
Parameter Description start
time:endtime
Indicates the start and end time for alarm synchronization.
The U2000 reports alarms that are generated during the preset time period.
NOTE
l If the end time is not set, the current system time of the U2000 is used as the end time.
l If the start and end time are not set, all the active alarms are synchronized. l If the end time is set, the start time is mandatory.
l Both the start and end time indicate the time period when alarms are generated on the equipment rather than reported to the U2000.
l The timekeeping standard is universal time coordinated (UTC).
The syntax for start time and end time is:YYYYMMDDhhmmss. l YYYY: Four-digit year. The range of values is 1970 onwards. l MM: Two-digit month. The range of values is 01-12.
l DD: Two-digit date. The range of values is 01-31. l hh: Two-digit hour. The range of value is 00-23. l mm: Two-digit minutes. The range of values is 00-59. l ss: Two-digit seconds. The range of values is 00-59.
Sample
Prerequisite
l The IP address of the upper-layer OSS is set to 10.70.73.97 and the port for receiving alarms is set to 6666.
l The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms. Purpose
To synchronize alarms that are generated between 2011-03-01 00:00:00 and 2011-03-15 00:00:00.
Table 6-4 shows the parameters of this sample.
Table 6-4 Sample parameters - synchronizing alarms
Parameter Value MIB Object
The IP of the upper-layer NMS
10.70.73.97 10.70.73.97
Receive Trap Port 6666 6666
Start time 2011-03-01 00:00:00 20110301000000
Procedure
1. The OSS sets hwNmNorthboundEventSynchronizationCommandStart to:
10.70.73.97:6666:20110301000000:20110315000000
l The OSS receives traps from the U2000, indicating that the synchronization is started. l The U2000 reports alarms saved in the database that are generated during the preset
time period. 2. Optional:
To stop the synchronization, the OSS sets
hwNmNorthboundEventSynchronizationCommandStop to 10.70.73.97:6666. 3. After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.
6.1.4 Acknowledging Alarms
The SNMP NBI allows the OSS to acknowledge alarms on the U2000 by alarm serial number. An acknowledged alarm is an alarm that has been handled.
Function
The OSS can acknowledge U2000 alarms based on the alarm serial numbers.
The alarm status will change after the alarm is acknowledged. If acknowledged alarms are specified as the filter criteria, the OSS will receive the information about state changes along with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an alarm is acknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be acknowledged and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.7. The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmFault(3).hwNmAcknowledgeAlarms(7)
Object Type Max Access Description
hwNmAcknowledg- eAlarms
Octet string read-write Indicates that alarms
are acknowledged based on serial numbers.
NOTE
The GET operation is not supported on this MIB node.
Setting Method
The OSS can set the value of the MIB node to acknowledge the active alarm on U2000. The format is as follows:
Serial Number,Serial Number,...
Table 6-5 Format description - acknowledging alarms Parameter Description Serial Number,Se rial Number,.. .
alarm serial number
Integer, separated by a comma.
Table 6-6 shows the status changes when alarms are acknowledged.
Table 6-6 Alarm states - acknowledging alarms
Sl.No Alarm Status Status Change SET Response Failed List
1 Unacknowledge and Unclear Acknowledge and Unclear Success Empty 2 Unacknowledge and Clear Acknowledge and Clear Success Empty 3 Acknowledge and Unclear Acknowledge and Unclear Success Empty 4 Acknowledge and Clear
NA Success serial number
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical alarms, no data will be returned after you acknowledge these alarms. The life cycle specifies the period in which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms. Purpose
Table 6-7 shows sample parameters.
Table 6-7 Sample parameters - acknowledging alarms
Parameter Value MIB Object
Alarm serial number 20,30,10005,18000 20,30,10005,18000
Procedure
The OSS sets hwNmAcknowledgeAlarms to 20,30,10005,18000. Query the alarm status on the OSS or U2000. The state for the alarm
20,30,10005,18000 is Acknowledge, indicating the alarm is acknowledged successfully. The Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If acknowledged alarms are specified as the filter criteria, the OSS will receive the information about state changes along with the alarms. The alarm time is when the alarm is acknowledged.
6.1.5 Unacknowledging Alarms
The SNMP NBI allows the OSS to unacknowledge alarms on the U2000 by alarm serial number. This function allows you to unacknowledge an acknowledged alarm if necessary.
Function
The OSS can unacknowledge alarms based on alarm serial numbers.
The alarm status will change after the alarm is unacknowledged. If unacknowledged alarms are specified as the filter criteria, the OSS will receive the information about state changes along with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an alarm is unacknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be unacknowledged and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.8. The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmFault(3).hwNmUnAcknowledgeAlarms(8)
Object Type Max Access Description hwNmUnAcknowl-
edgeAlarms
Octet string read-write Indicates that alarms
are unacknowledged based on serial numbers.
NOTE
The GET operation is not supported on this MIB node.
Setting Method
The OSS can set the value of the MIB node to unacknowledge the active alarm on U2000. The format is as follows:
Serial Number,Serial Number,...
Table 6-8 Format description - unacknowledging alarms Parameter Description Serial Number,Se rial Number,.. .
alarm serial number
Integer, separated by a comma.
Table 6-9 shows the state change when alarms are unacknowledged.
Table 6-9 Alarm states - unacknowledging alarms
Sl.No Alarm Status Status Change SET Response Failed List
1 Unacknowledge and Unclear Unacknowledge and Unclear Success Empty 2 Unacknowledge and Clear Unacknowledge and Clear Success Empty 3 Acknowledge and Unclear Unacknowledge and Unclear Success Empty 4 Acknowledge and Clear
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical alarms, no data will be returned after you unacknowledge these alarms. The life cycle specifies the period in which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms. Purpose
To unacknowledge the alarm with the serial number 20,30,10005,18000. Table 6-10 shows the parameters of this sample.
Table 6-10 Sample parameters - unacknowledging alarms
Parameter Value MIB Object
Alarm serial number 20,30,10005,18000 20,30,10005,18000
Step
The OSS sets hwNmUnAcknowledgeAlarms to 20,30,10005,18000.
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000 is Unacknowledge, indicating the alarm is unacknowledged successfully. The
Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If unacknowledged alarms are specified as the filter criteria, the OSS will receive the information about status changes along with the alarms. The alarm time is when the alarm is generated.
6.1.6 Clearing Alarms
The SNMP NBI allows the OSS to clear alarms on the U2000 by alarm serial number. Manually clear the alarm if the U2000 cannot automatically clear the alarm or this alarm does not exist on an NE.
Function
The OSS can clear alarms based on the alarm serial numbers.
The alarm status will change after the alarm is cleared. If cleared alarms are specified as the filter criteria, the OSS will receive the information about status changes along with the alarms.
CAUTION
The Clearance User parameter is SNMP Agent User on the U2000 client after an alarm is cleared by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be cleared and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.6. The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises (1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent (1).hwNmFault(3).hwNmClearAlarms(6)
Object Type Max Access Description
hwNmClearAlarms Octet string read-write Indicates that alarms
are cleared based on serial numbers.
NOTE
The GET operation is not supported on this MIB node.
Setting Method
The OSS can set the value of the MIB node to clear the active alarm on U2000. The format is as follows:
Serial Number,Serial Number,...
Table 6-11 Format description - clearing alarms Parameter Description Serial Number,Se rial Number,.. .
alarm serial number
Integer, separated by a comma.
Table 6-12 Alarm status - clearing alarms
Sl.No Alarm Status Status Change SET Response Failed List
1 Unacknowledge and Unclear Unacknowledge and Clear Success Empty 2 Unacknowledge and Clear Unacknowledge and Clear Success Empty 3 Acknowledge and Unclear Acknowledge and Clear Success Empty 4 Acknowledge and Clear
NA Success serial number
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical alarms, no data will be returned after you clear these alarms. The life cycle specifies the period in which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms. Purpose
To clear the alarm with the serial number 20,30,10005,18000. Table 6-13 shows the parameters of this sample.
Table 6-13 Sample parameters - clearing alarms
Parameter Value MIB Object
Alarm serial number 20,30,10005,18000 20,30,10005,18000
Procedure
The OSS sets hwNmClearAlarms to: 20,30,10005,18000
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000 is Clear, indicating the alarm is cleared successfully. The Clearance User parameter is SNMP Agent User on the U2000 client.
NOTE
If a cleared alarm is also an acknowledged one, it becomes a historical alarm.
If cleared alarms are specified as the filter criteria, the OSS will receive the information about status changes along with the alarms. The alarm time is when the alarm is cleared.
6.2 U2000-T MIB Subinterfaces
When the OSS is loaded with the U2000-T MIB, the SNMP NBI provides subinterfaces to enable the following functions: reporting alarms automatically and synchronizing alarms.
CAUTION
Ensure that the U2000-T MIB has been loaded to the OSS. To load the U2000-T MIB, set the MIB type to U2000-T MIB when deploying the SNMP NBI.
6.2.1 Reporting Real-Time Alarms
You do not need to set any parameters for the OSS to receive alarm packets from the U2000 through the SNMP NBI. After the SNMP NBI is properly deployed on the U2000, alarms will be reported to the OSS in real time.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the U2000, the OSS can receive alarms in real time.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring SNMP.
CAUTION
The reported alarm field for the U2000-T MIB consists of 36 bound variables (VBs). For details, see D.2 Reported Alarm Field by U2000-T MIB.
6.2.2 Synchronizing Alarms
The SNMP NBI allows the OSS to initiate the synchronization operation to ensure that alarms on the OSS and the U2000 are consistent.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data consistency and can also stop the synchronization.
After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform the