Issue with DX NetOps Spectrum Southbound Gateway after modifying AlartMap file
Article ID: 371971
Updated On:
Products
Issue/Introduction
We configured a trap for a Southbound Gateway integration as follows:
# vmwTrapProblemActive vmwAlertAliveServerName
1.3.6.1.4.1.6876.4.50.1.6.46 0x051206fd 1.3.6.1.4.1.6876.4.50.1.2.1(1,0)\
# vmwAlertEntityName
1.3.6.1.4.1.6876.4.50.1.2.2(16,0)
The purpose of the above configuration is to take the value of varbind 16 (vmwAlertEntityName) and check if there is a device model in the database with that model name. If so, forward the event to that model.
If not, then take the value of varbind 1 (vmwAlertAliveServerName) and check for an EventModel with that name and if found, then forward the event to that model. If no EventModel, then dynamically create one and forward the event to the new model.
The above worked.
However, it was decided to reverse the value of the varbinds to the following:
# vmwTrapProblemActive vmwAlertAliveServerName
1.3.6.1.4.1.6876.4.50.1.6.46 0x051206fd 1.3.6.1.4.1.6876.4.50.1.2.1(16,0)\
# vmwAlertEntityName
1.3.6.1.4.1.6876.4.50.1.2.2(1,0)
Notice the value of vmwAlertEntityName is not saved to varbind 1 and the value of vmwAlertAliveServerName is not saved to varbind 16.
After doing this, Southbound Gateway no longer worked as expected.
The following event is generated on the associated EventAdmin model even though there is a device model in the database with a model name of "ModelName":
Jun 19, 2024, 8:01:54 AM EDT testit Device testit of type EventAdmin - Error processing event 0xfff00003 - Details: Spectrum contains 0 models with the name ModelName
Environment
Version: Any
Component: Application Southbound Gateway
Resolution
This issue will be addressed in a future release of Spectrum.
Feedback
