Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM Alcatel 5620 Adapter: How do I stop an Alcatel alarm from arriving into the Smarts SAM Alcatel 5620 Adapter? (318893)

Last Updated: 3/22/2024Categories: How toTotal Views: 1632Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

How do I stop an Alcatel alarm from arriving into the Smarts SAM Alcatel 5620 Adapter?

Alcatel Alarms that arrive into the Smarts SAM Alcatel 5620 Adapter are generated from the Alcatel device in the following form:

alarm-<alarmName>-<alarmType>-<alarmProbableCause> (the numbers populated by the fm.AlarmObject in Alcatel)

These alarms are then matched using the ASA-Alarm.conf file. If the alarm is not defined in the ASA-Alarm.conf file, it will take the default values given at the start of this file:

DEDUP DEFAULT OFF

SEVERITY DEFAULT 7

EXPIRATION DEFAULT 1296000

NOTARGET 1296000

So a notification will be created with these values. This gives the default SEVERITY and so on for the alarm, which is translated in the ASA-Alarm.conf.

The alarms which are sent from the EMS are called Raw alarms. These alarms are not generated by the Smarts domain managers but are posted by the ASAM adapter to the OI. Hence, these alarms do not have any root cause correlation. The easy way to identify these events is to look at the "Source" of the event. These events will have ASAM adapter as the source. The Alcatel EMS has information specifying the object on which this particular alarm occurred. Using this information the adapter would determine which class to populate. Below is the example of the poller alarm.

Regarding the alarm names, the ems alarm is of the form alarm-31-4-24. Where first number specifies the alarm name, second specifies the alarm type and third specifies the alarm cause. The 1.2 adapter maintains the mapping of these numbers to text. These number to text mapping can be found in the Alcatel 5620 EMS Trouble shooting Guide. The alarm alarm-32-4-24 will have Event: PollerProblem Type: communicationsAlarm, Probable Cause: resyncFailed

The adapter makes use of the "<affectedObjectClassName>netw.NetworkElement</affectedObjectClassName>" to determine the class. Here netw.NetworkElement specifies that the class is Router.

In order to remove an alarm from the notification list, you would have to find the alarm numbers for that specific alarm and create an entry to de-activate it similar to the following:

INACTIVE alarm-abc-def-ghi

Where "abc" is the alarm name, "def" is the alarm type and "ghi" is the alarm probable cause numbers defined on the Alcatel side.

Making the alarm INACTIVE will prevent the adapter from posting these alarm to the OI. There are some alarms which are handled in a special way. A specific example is alarm-243 (SnmpReachabilityAlarm). When this alarm is received, the adapter will set the status of the interfaces to UNKNOWN, SNMP agent status to UNREACHABLE and IP status to TIMEDOUT. This will make the IPAM server to generate a Router Down event. If the alarm-243 is filtered out by making it INACTIVE, then the raw alarm will not be posted to OI. But the Router Down alarm will still be generated by the IPAM. If a router is having poller problem, it is most likely have a SnmpReachabilityAlarm. The poller problem alarm-31 is NOT handled is a special way. So if this is marked INACTIVE, then this alarm will not be posted on OI.

More information can be found in the Alcatel 5620 SAM Adapter "Installation and User's Guide" available on Powerlink.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant