Adding Support for a Trap
This procedure describes how to create a single event that represents a trap or a set of traps of the same type. If you want to add support for multiple traps of different types, see Adding Support for Multiple Traps Simultaneously.
Use the VCB to add support for an unsupported trap, as follows:
Step 1 In the VCB tool, go to the VNE Drivers tab.
Step 2 Click on the arrow next to the VNE driver on which you want the additional traps to be supported.
Figure 6-1 Expanded VNE Driver Properties Showing Parsing Rules
Step 3 Click the Trap Parsing Rule link to show a list of traps associated with this parsing rule.
Step 4 Click
Add from MIB
. This launches a wizard which enables you to analyze a specified MIB and select the traps to be supported.
Step 5 Click
Browse
and select the MIB file you want to upload to the Prime Network gateway. You can upload an individual MIB file or a zip file containing multiple MIB files. The file extension should be .mib or .my, .zip, or no extension. If you select a zip file, a list of the contained MIBs is displayed. You can select one or more of these MIBs to upload.
A list of MIB dependencies is displayed. A green check mark indicates that the dependency file has been found on the server.
Figure 6-2 MIB Dependencies
Step 6 If any of the dependencies is not found, click
Browse
and select the dependency file to upload.
Step 7 Click
Next
. A list of traps is displayed. A red icon to the left of the trap indicates that it is not supported. A green icon indicates that the trap is already supported.
Step 8 Check the check box next to the trap(s) to be supported. If you select multiple traps, they must be of the same type (i.e., they must have the same prefix). Click
Next
.
At this point, an event is created. Each trap you selected becomes a subtype of the new event. The Event Definition wizard is displayed to enable you to complete the definition of the new event.
Step 9 Click on Step 1 - Event Definition and provide the following information:
-
Event name and OID—these are pre-populated but can be changed if necessary. The OID is the common prefix of the OIDs of the selected subtypes.
-
Category—predefined category from 3GPP standards (according to ITU-T Recommendations X.733 and X.736). You can change the category if necessary.
-
Nature—defines whether the event is automatically cleared by a clearing event or it needs to be manually cleared. Possible values are:
– ADAC (Automatically Detected Automatically Cleared)—The event is automatically detected and automatically cleared by the system. For example, “link down” event. Select this option if the event has a clearing event, for example, “link up”.
– ADMC (Automatically Detected Manually Cleared)—The event must be manually cleared by the user. For example, “DWDM fatal error” syslog. Select this option if the event does not have a clearing event.
Step 10 To define the criteria by which this trap will be considered a flapping event, check the Flapping check box. This would be relevant for network or communication related events that potentially could change state frequently. For example, link up/down, BGP neighbor up/down. When an event is flapping, Prime Network generates a single event indicating the flapping status and does not generate an additional event for each state change.
Enter the following information to define flapping criteria:
-
Clear Interval—The flapping event will be cleared when the flapping has stopped for the specified time interval (in milliseconds).
-
Flapping Interval and Flapping Threshold—To be defined as a flapping event, the event must change state every X milliseconds (Flapping Interval), and must occur Y consecutive times (Flapping Threshold). For example, if the Flapping Interval is 60000 msecs (one minute) and the Flapping Threshold is 5, the event must change state five times, every one minute, in order to be considered flapping.
-
Update Interval and Update Threshold—An update event indicating that the event is still flapping will be sent either when the specified Update Interval has passed or when the event is received more times than the specified Update Threshold. For example, if the Update Interval is 100000 msecs and the Update Threshold is 500, an update event will be generated if the event remains flapping for longer than 100000 msecs or if the event is received more than 500 times, whichever occurs first.
Step 11 Click on Step 2 - Subtype Definition. You will see that a subtype has been created for each unsupported trap you selected. Edit the information for each subtype as required:
|
|
Name
|
Enter a unique name for the event subtype
|
Description to be Displayed
|
Enter a string that describes the event subtype. You can include dynamic values in the description string to provide more details. See Adding Parameter Values to Event Descriptions.
|
Severity
|
Select the severity to be attributed to the subtype.
|
Ticketable
|
Check the check box if you want Prime Network to create a ticket for this event if there is no root cause event to which it can be correlated. If you make a subtype ticketable, a ticket will be generated for it. When a non-ticketable subtype of the same event arrives (for example, a warning or clearing event), the ticket will be updated.
|
Auto-Clear
|
Check the check box if you want Prime Network to automatically clear the event. Prime Network clears a ticket if all of its events either are cleared or are configured for automatic clearing.
|
Correlate
|
Check the check box if you want the event to be correlated to a root-cause alarm.
|
In addition, if you selected the Flapping check box in the previous step, you will see that Flapping subtypes have been created. By default, the flapping subtype consists of the event name and the flapping subtype name. This can be changed as required; for example, you can also change the severity of the flapping subtype so that it matches the severity of the event.
Step 12 Click on Step 3 - Subtype Identification. In this step, you define how Prime Network will differentiate between the subtypes, as follows:
|
|
By Tr
apOID
|
Select this option if each subtype has a unique OID. In the Replacing Rules section, specify the OID suffix for each subtype. The OID suffix must be an integer.
|
By Varbind Value
|
Select this option if the subtypes have the same trap OID and you want to use one of the varbind values to differentiate between the subtypes. In the Replacing Rules section, select the required varbind from the drop-down menu or enter free text, and then define the values for each subtype.
|
By Varbind OID
|
Select this option if there is a varbind for each subtype. In the Replacing Rules section, specify the common prefix of the varbind OIDs and the suffix for each subtype.
|
Step 13 Click on Step 4 - Association, in which you associate the event with the VNE. Specify the following information:
|
|
Source Type
|
The entity to which the event should be associated.
|
|
ManagedElement Key
|
Select this option if there is no specific interface or other component of the VNE from which the event is generated.
|
Interface Key From Ifindex
|
Creates the interface device component key from the ifIndex and associates the event with the appropriate interface layer.
|
Interface Key From Ifname
|
Associates the event with a specific interface that you specify in the Interface Identifier field.
|
Logical Container Key
|
Associates the event with a designated logical container that you select in the Logical Container field.
|
ModuleDC Key Given EntPhysicalIndex
|
Associates the event with a designated module DC.
|
ModuleDC With SlotSubslot Value Key
|
Associates the event with the corresponding module, based on the slot number.
|
Pw Interface Key From Tunnelindex
|
Associates trap events with the designated pseudowire tunnel interface.
|
Logical Container
|
Applicable only when the source type is Logical Container Key. This field lists the various logical containers for which the VCB supports event association. For example, BGP traps/syslogs can be associated with the MP-BGP type container, ISIS events with the ISIS System container, and so on.
|
Instance Identifier Location
|
Specify whether the identifier of the event is based on a value or a varbind OID.
|
Instance Identifier Varbind OID
|
Select the varbind that contains the instance information. Prime Network uses varbind OID to locate the varbind in the trap PDU and locates the instance information from either the OID or the value depending what was selected as the instance identifier location (OID or value).
|
Source Location
|
Specify whether the event source can be found in a value or a varbind OID
|
Source Varbind ID
|
Select the varbind that contains the source information. Prime Network uses varbind OID to locate the varbind in the trap PDU and locates the source information from either the OID or the value depending what was selected as the source location (OID or value).
|
Step 14 Optionally, click on Step 5 - Expedite if you want the device to be polled immediately for inventory updates upon receipt of the event, instead of waiting for the next polling cycle which may take up to twenty four hours for VNEs using reduced polling. Click
Add
to create an expedite rule and provide the following information:
|
|
Level
|
-
Select VNE Component if the expedite command will run on a component of the VNE.
-
Select VNE if the expedite command will run on the VNE level.
|
Class
|
Shows the VNE-level or the component-level command classes. Select the command class that contains the relevant expedite command.
|
Command Name
|
Shows the commands belonging to the selected class. Select the relevant command.
|
Delay
|
Delay (in milliseconds). By default, the command will be executed immediately upon receipt of the event (default value is 0).
|
Key
|
Component level only. This is the entity by which the component will be identified. If the source type is the same as the source type specified for association, there is no need to specify the key again here.
|
Note Command expedition might result in unnecessary polling of devices which puts a load on the device and might affect performance. Therefore, before creating command expedition rules, consider whether the event is specific to a particular VNE or common to all VNEs and might affect the performance of VNEs using regular polling.
Step 15 Click on Step 6 - Pattern to determine which VNE drivers will be extended to support this event. This is determined by selecting the parsing rule groups per scheme that will be extended. The event will be supported on all VNE drivers that use the specified parsing rule groups.
Step 16 Click
Add
to select additional parsing rule groups, as required, either for the Product or IpCore scheme.
Note Certain parsing rules groups inherit from other groups. If you select multiple groups, make sure that your selection does not include a base (parent) group as well as the group that inherits from the base group. See Parsing Rule Group Inheritance Structure for the relationship between parsing rule groups.
Step 17 Click Finish. A dialog box displays a list of the traps that were added.
Step 18 If you want to enable support for additional traps, click Select Different Trap, otherwise click Close.
Adding Support for Multiple Traps Simultaneously
This procedure describes how to add support for multiple traps at once. The traps do not have to be of the same type. This enables you to add support for traps in bulk, without having to add support for each trap individually. This procedure can be used if you want to add support for a large number of events that do not require complex processing, on the managed element level.
Note The traps added using this procedure will be associated at the managed element level only (not at the interface level or any other DC). In addition, you will not be able to expedite a command upon receiving events added using this method.
To add support for traps in bulk:
Step 1 In the VCB tool, go to the VNE Drivers tab.
Step 2 Click on the arrow next to the VNE driver on which you want the additional traps to be supported.
Figure 6-3 Expanded VNE Driver Properties Showing Parsing Rules
Step 3 Click the Trap Parsing Rule link to show a list of traps associated with this parsing rule.
Step 4 Click
Add from MIB
. This launches a wizard which enables you to analyze a specified MIB and select the traps to be supported.
Step 5 Click
Browse
and select the MIB file you want to upload to the Prime Network gateway. You can upload an individual MIB file or a zip file containing multiple MIB files. The file extension should be .mib or .my, .zip, or no extension. If you select a zip file, a list of the contained MIBs is displayed. You can select one or more of these MIBs to upload.
A list of MIB dependencies is displayed. A green check mark indicates that the dependency file has been found on the server.
Figure 6-4 MIB Dependencies
Step 6 If any of the dependencies is not found, click
Browse
and select the dependency file to upload.
Step 7 Click
Next
. A list of traps is displayed. A red icon to the left of the trap indicates that it is not supported. A green icon indicates that the trap is already supported.
Figure 6-5 Trap Selection
Step 8 Select the Bulk Upload check box.
Step 9 Select the traps you want to add or check the Select All check box.
Step 10 Click Next. At this point, an event is created for each selected trap. The traps are listed in a table. Default values are provided for all mandatory attributes of the traps. You can edit these values inline in the table.
Figure 6-6 Trap Table
Step 11 Optional. You can combine multiple traps in a single event as subtypes of the event. To do this, make the event name the same for all the traps you want to combine in a single event.
Step 12 Click Finish. A dialog box displays a list of the traps that were added.
Step 13 If you want to enable support for additional traps, click Select Different Trap, otherwise click Close. The traps you added now appear in the table of supported traps. You can edit a trap at any stage by selecting it and clicking Edit.