UPC Nederland Expert Cluster Trap Receiver
The UPC Nederland Expert Cluster Trap Receiver receives all alarm traps sent from other DMAs.
About
This connector captures all alarm traps, in order to visualize what the active alarms on other clusters are.
Installation and configuration
Creation
SNMP main connection
This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
SNMP CONNECTION:
- IP address/host: The polling IP of the device, e.g., 192.168.10.2
SNMP Settings:
- Port number: The port of the connected device, by default 161.
- Get community string: The community string used when reading values from the device. The default value is public.
- Set community string: The community string used when setting values on the device. The default value is private.
Configuration
To configure the connector, you must do the following:
- On the General page, the parameter Trap Source IP needs to be filled in. The value you fill in can be a single IP address or a comma-separated list of IP addresses. These addresses can contain * and ? wildcards.
- On the DMA that will send the alarm traps, all the Custom Trap Bindings need to be included as a filter. For this, the elements can be selected of which the alarms need to be forwarded. However, note that information events should not be included in the alarm filter.
Usage
General
This page contains the Trap Source IP parameter. For more info on this parameter, refer to the "Configuration" section above.
This page also contains the Alarm Traps table, which displays all alarms that came in through traps. When an alarm is cleared, it will automatically be removed from the table. However, it is possible that alarms are not cleared, for example when the element is stopped on the source DMA. To manually delete a row from the table, select it in Cube, right-click and select the option Delete Selected Rows.
The connector processes the following bindings from a trap:
| Binding | OID | Comments | Mandatory | Column Name in table Alarm Traps |
|---|---|---|---|---|
| System name | 1.3.6.1.2.1.1.5 | Possible values: - Element name - DataMiner name |
Yes | Element Name |
| Parameter description | 1.3.6.1.4.1.8813.1.1.2.2.1 | Yes | Parameter Name | |
| Value | 1.3.6.1.4.1.8813.1.1.2.2.2 | Possible values (depending on the type): - Octet string - Integer |
Value | |
| Severity | 1.3.6.1.4.1.8813.1.1.2.2.3 | Possible values: - Critical Low/High - Major Low/High - Minor Low/High - Warning Low/High - Normal - Information - Timeout - Error - Notice |
Severity | |
| OID | 1.3.6.1.4.1.8813.1.1.2.2.4 | Default value: Device OID + Parameter OID | OID | |
| Timestamp | 1.3.6.1.4.1.8813.1.1.2.2.5 | A fixed time format is used: | Time | |
| 'yyyy-mm-dd HH:MM:SS'. | ||||
| Alarm type | 1.3.6.1.4.1.8813.1.1.2.2.6 | Possible values: - Escalated - Dropped - New alarm - Cleared - Acknowledged - Resolved - Unresolved - Comment Added - Masked - Unmasked - Dropped from critical - Dropped from major - Dropped from minor - Dropped from warning - Escalated from warning - Escalated from minor - - Flipped - Service impact changed - Value changed - Name changed - RCA level changed |
Alarm Type | |
| Alarm status | 1.3.6.1.4.1.8813.1.1.2.2.7 | Possible values: - Cleared - Open - Masked |
Status | |
| Name of owner | 1.3.6.1.4.1.8813.1.1.2.2.8 | Owner | ||
| User status | 1.3.6.1.4.1.8813.1.1.2.2.9 | Possible values: - Not assigned - Acknowledged - Resolved - Unresolved |
User Status | |
| Comment added by user | 1.3.6.1.4.1.8813.1.1.2.2.10 | Comment | ||
| Source | 1.3.6.1.4.1.8813.1.1.2.2.11 | Possible values: - Automation Engine - Correlation Engine - DataMiner System - External - Mobile Gateway - Service Monitor - Unknown - Watchdog |
Source | |
| Display value | 1.3.6.1.4.1.8813.1.1.2.2.12 | (formatted) | Yes | Display Value |
| Element description | 1.3.6.1.4.1.8813.1.1.2.2.13 | Element Description | ||
| Trap description | 1.3.6.1.4.1.8813.1.1.2.2.14 | (as defined in SNMP Manager) | Trap Description | |
| Element RCA | 1.3.6.1.4.1.8813.1.1.2.2.15 | -1 = Not defined | Element RCA | |
| Parameter RCA | 1.3.6.1.4.1.8813.1.1.2.2.16 | -1 = Not defined | Parameter RCA | |
| Alarm ID | 1.3.6.1.4.1.8813.1.1.2.4.0.0 or 1.3.6.1.4.1.8813.1.1.2.4.1.1 |
Alarm ID | ||
| DataMiner ID | 1.3.6.1.4.1.8813.1.1.2.4.0.1 or 1.3.6.1.4.1.8813.1.1.2.4.1.2 |
Yes | DataMiner ID | |
| Element ID | 1.3.6.1.4.1.8813.1.1.2.4.0.2 or 1.3.6.1.4.1.8813.1.1.2.4.1.3 |
Element ID | ||
| Parameter ID | 1.3.6.1.4.1.8813.1.1.2.4.0.3 or 1.3.6.1.4.1.8813.1.1.2.4.1.4 |
Parameter ID | ||
| Type ID | 1.3.6.1.4.1.8813.1.1.2.4.0.4 or 1.3.6.1.4.1.8813.1.1.2.4.1.5 |
Possible values: - Escalated (8) - Dropped (9) - New alarm (10) - Cleared (11) - - Resolved (20) - Unresolved (21) - Comment Added (22) - Unmasked (27) - Dropped from critical (31) - Dropped from major (32) - Dropped from minor (33) - Dropped from warning (34) - Escalated from warning (35) - Escalated from minor (36) -Escalated from major (37) - Flipped (38) - - Value changed (41) - Name changed (42) - RCA level changed (43) - Properties changed (50) |
Type ID | |
| State ID | 1.3.6.1.4.1.8813.1.1.2.4.0.7 or 1.3.6.1.4.1.8813.1.1.2.4.1.6 |
Possible values: - Cleared (11) - Open (12) - Masked (25) |
State ID | |
| Severity ID | 1.3.6.1.4.1.8813.1.1.2.4.0.8 or 1.3.6.1.4.1.8813.1.1.2.4.1.7 |
Possible values: - Critical (1) - Major (2) - Minor (3) - Warning (4) - Normal (5) - Information (13) - Timeout (17) - Error (24) - Notice (28) |
Severity ID | |
| Severity range | 1.3.6.1.4.1.8813.1.1.2.4.0.9 or 1.3.6.1.4.1.8813.1.1.2.4.1.8 |
Possible values: - Normal (5) - High (6) -Low (7) |
Severity Range | |
| Previous alarm ID | 1.3.6.1.4.1.8813.1.1.2.4.0.10 or 1.3.6.1.4.1.8813.1.1.2.4.1.9 |
Previous Alarm ID | ||
| User status ID | 1.3.6.1.4.1.8813.1.1.2.4.0.11 or 1.3.6.1.4.1.8813.1.1.2.4.1.10 |
Possible values: - Not assigned (18) - Acknowledged (19) - Resolved (20) - Unresolved (21) |
User Status ID | |
| Alarm root ID | 1.3.6.1.4.1.8813.1.1.2.4.0.14 or 1.3.6.1.4.1.8813.1.1.2.4.1.11 |
Yes | Alarm Root ID | |
| Source ID | 1.3.6.1.4.1.8813.1.1.2.4.0.15 or 1.3.6.1.4.1.8813.1.1.2.4.1.12 |
Possible values: - DataMiner (16) - Correlation engine (23) - Automation engine (26) |
Source ID | |
| Table display index | 1.3.6.1.4.1.8813.1.1.2.4.0.16 or 1.3.6.1.4.1.8813.1.1.2.4.1.13 |
Table Display Index | ||
| Full RCA level | 1.3.6.1.4.1.8813.1.1.2.4.0.17 or 1.3.6.1.4.1.8813.1.1.2.4.1.14 |
A 32-bit integer | ||
| Service RCA: Byte 4 | Service RCA Level | |||
| Parameter RCA: Byte 3 | Parameter RCA Level | |||
| Element RCA: Bytes 2 and 1 | Element RCA Level | |||
| Element type | 1.3.6.1.4.1.8813.1.1.2.4.0.19 or 1.3.6.1.4.1.8813.1.1.2.4.1.15 |
Element Type | ||
| Root time | 1.3.6.1.4.1.8813.1.1.2.4.0.22 or 1.3.6.1.4.1.8813.1.1.2.4.1.16 |
A fixed time format is used: 'yyyy-mm-dd HH:MM:SS'. | Root Time | |
| Table index (primary key) | 1.3.6.1.4.1.8813.1.1.2.4.0.23 or 1.3.6.1.4.1.8813.1.1.2.4.1.17 |
Table Index | ||
| Protocol name | 1.3.6.1.4.1.8813.1.1.2.4.0.24 or 1.3.6.1.4.1.8813.1.1.2.4.1.18 |
Protocolname | ||
| Alarm presence | 1.3.6.1.4.1.8813.1.1.2.4.0.25 or 1.3.6.1.4.1.8813.1.1.2.4.1.19 |
Alarm Presence | ||
| Service impact | 1.3.6.1.4.1.8813.1.1.2.4.1.0 or 1.3.6.1.4.1.8813.1.1.2.5.1.1 |
Service Impact | ||
| Platform Service | 1.3.6.1.4.1.8813.1.1.2.4.4.1.80.108.97.116.102. 111.114.109.32.83.101.114.118.105.99.101 |
Element property Platform Service | Platform Service | |
| Region | 1.3.6.1.4.1.8813.1.1.2.4.4.1. 82.101.103.105.111.110 or 1.3.6.1.4.1.8813.1.1.2.4.4.3. 82.101.103.105.111.110 |
Element or alarm property Region | Region | |
| Customers Impacted | 1.3.6.1.4.1.8813.1.1.2.4.4.3.67.117.115. 116.111.109.101.114.115.32.73.109. 112.97.99.116.101.100 |
Alarm property Customers Impacted | Customers Impacted | |
| Event Tag | 1.3.6.1.4.1.8813.1.1.2.4.4.3.69. 118.101.110.116.32.84.97.103 |
Alarm property Event Tag | Event Tag | |
| Friendly Event Description | 1.3.6.1.4.1.8813.1.1.2.4.4.3.70.114.105.101. 110.100.108.121.32.69.118.101.110.116.32. 68.101.115.99.114.105.112.116.105.111.110 |
Alarm property Friendly Event Description | Friendly Event Description | |
| Impacted Services | 1.3.6.1.4.1.8813.1.1.2.4.4.3.73.109.112.97.99. 116.101.100.32.83.101.114.118.105.99.101.115 |
Alarm property Impacted Services | Impacted Services | |
| Parameters | 1.3.6.1.4.1.8813.1.1.2.4.4.3.80.97.114.97.109. 101.116.101.114.115 |
Alarm property Parameters | Parameters | |
| Source | 1.3.6.1.4.1.8813.1.1.2.4.4.3. 83.111.117.114.99.101 |
Alarm property Source | Source Property | |
| Trigger IVR | 1.3.6.1.4.1.8813.1.1.2.4.4.3.84.114.105.103. 103.101.114.32.73.86.82 |
Alarm property Trigger IVR | Trigger IVR | |
| Event Description | 1.3.6.1.4.1.8813.1.1.2.4.4.3.69.118.101.110.116. 32.68.101.115.99.114.105.112.116.105.111.110 |
Alarm property Event Description | Event Description |
General (version 1.0.0.7)
From version 1.0.0.7 onwards, a queue is introduced in order to prevent all the alarms from being added to the Alarm Traps table immediately. The parameter Maximum Active Alarm Count defines the maximum number of active alarms (i.e., alarms with another severity than Normal (=5), in the Severity ID column) that can be present in the Alarm Traps table, before a new active alarm will be queued.
If there are more active alarms, these will be queued until there is room in the Alarm Traps table again. If an alarm goes back to state Normal while it is queued, it will be removed from the queue, and it will therefore never enter the Alarm Traps table. Alarms in the queue are processed in a first-in-first-out (FIFO) manner. This means that the alarm that first entered the queue will be the first alarm that leaves the queue and enters the Alarm Traps table.
The connector also allows the user to remove rows from the Alarm Traps table by selecting Delete Selected Rows from the context menu. When this action is executed and there are still alarms left in the queue, these alarms will be transferred to the Alarm Traps table, until either this table holds the maximum allowed number of active alarms or the queue is empty.
Note: When the Maximum Active Alarm Count parameter is changed during operation, two options are possible:
- The maximum number of active alarms is increased: In this case, alarms from the queue will be transferred to the Alarm Traps table, until either this table holds the maximum allowed number of active alarms or the queue is empty.
- The maximum number of active alarms is reduced: In this case, it is possible that the Alarm Traps table contained more alarms than is now allowed. If this is the case, alarms are queued back to the queue in such a way that these alarm will be processed first when there is room in the Alarm Traps table again.
***[**version 1.0.0.12]***From version 1.0.0.12 onwards, this connector works along with the Ziggo SAM Event Combiner connector.A new parameter called Trigger IVR Type was added to specify which table of the Combiner element the alarms' information will be sent to (HFC or B2B).Two new columns were added to the Alarm Traps table that display the results of the correlation process returned by the Combiner element:
- Correlated Trigger IVR - The most technical path that will group the alarms and generate one correlated alarm.
- Impact - This column will only be set on "HFC" trap receivers and displays the number of B2B alarms under a correlated alarm.