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 IP: How the SystemRestarted event is enabled and processed (520248)

Last Updated: 12/17/2018Categories: How toTotal Views: 2247Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

Below are the steps to enable the SystemRestarted event:

1) In Polling and Thresholds Console that is attached to the IP Availability Manager, click the Thresholds tab >> system resource groups: Switches, Routers, Hubs and Bridges, and Other Systems.

2) To enable the SystemRestarted event for a particular system resource group, click its Connectivity setting, set the EnableGenericOIEvent parameter to ENABLED, accept or modify the value of the MaxUpTimeThreshold parameter,click Apply and reconfigure to save the changes.
Note :- Repeat this process for each system resource group.

3)  Open the tpmgr-param.conf file from IP installation directory using sm_edit utility and Set the EnableSystemRestart parameter to TRUE and accept or modify the values of the OITrapAdapterHost and the OITrapAdapterPort parameters, save the changes and close the file.
<base_dir>/IP/smarts/bin/sm_edit  ../conf/discovery/tpmgr-param.conf
The modified version of the tpmgr-param.conf file is saved to the <base_dir>/IP/smarts/local/conf/discovery directory.

4) Execute the following command to reload the tpmgr-param.conf file
<base_dir>/IP/smarts/bin/sm_tpmgr -s  <IP manager domain name > --load-conf=tpmgr-param.conf

5) Open the trap_mgr.conf from SAM installation bin using sm_edit utility and uncomment the following trap definition
<base_dir>/SAM/smarts/bin/sm_edit ../conf/icoi/trap_mgr.conf
#System restart traps

BEGIN_TRAP .1.3.6.1.4.1.733 6 13
ClassName: SNMPTrap
InstanceName: $V1$
ElementClassName: $V2$
ElementName: $V1$
EventName: SystemRestarted
Severity: 3
EventText: System Restarted
Expiration: 600
State: NOTIFY
UnknownAgent: CREATE
END_TRAP

BEGIN_TRAP * 0 0
ClassName: SNMPTrap
InstanceName: $SYS$
EventName: SystemRestarted
Severity: 5
Expiration: 600
State: NOTIFY
EventType: MOMENTARY
END_TRAP

BEGIN_TRAP * 1 0
ClassName: SNMPTrap
InstanceName: $SYS$
EventName: SystemRestarted
Severity: 5
Expiration: 600
State: NOTIFY
EventType: MOMENTARY
END_TRAP

6) Save and close the file.The modified version of the trap_mgr.conf file is saved to the <base_dir>/SAM/smarts/local/conf/icoi directory.

How the SystemRestarted event is enabled and processed

Related Information

The class name and instance name of the system for which the SystemRestarted notification applies are listed in the ElementClassName and ElementName attributes of the notification definition.

If the Trap Adapter Platform was running before you edited the trap_mgr.conf file, restart the Trap Adapter Platform

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