Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Using the third party SNMP devices (Cisco Prime Infrastructure) to monitor the 9630 by SNMP (Network Management Card 2)

APC UPS Data Center & Enterprise Solutions Forum

Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • APC UPS, Critical Power, Cooling and Racks
  • APC UPS Data Center & Enterprise Solutions Forum
  • Using the third party SNMP devices (Cisco Prime Infrastructure) to monitor the 9630 by SNMP (Network Management Card 2)
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
BillP
Administrator BillP Administrator
5060
voidstar_apc
Janeway voidstar_apc
196
Erasmus_apc
Sisko Erasmus_apc
112
Teken
Spock Teken
109
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to APC UPS Data Center & Enterprise Solutions Forum
Solved
Anonymous user
Not applicable

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

0 Likes
3
2297
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

Using the third party SNMP devices (Cisco Prime Infrastructure) to monitor the 9630 by SNMP (Network Management Card 2)

My main purpose is trying to use the third party SNMP devices to monitor UPS' alarm and to be informed when the UPS is off line and its battery is dead.

First of all , I would like to know what difference between SNMP polling and SNMP traps.  

For SNMP traps:     If I will let the third party SNMP device to receive the SNMP traps , How do I let the third party SNMP device understand the UPS' trap  and translate those traps to a readable Alarm message?

For SNMP polling:   I already imported the UPS' MIB (file: powernet407) to the third party SNMP devices.  But I see there are so many Tables (see below picture) in the MIB.  I do not know which Table is for checking if the battery dead , which table is for checking if the UPS is dead ? 

2200_mib1.jpg

Labels
  • Labels:
  • UPS Management Devices & PowerChute Software
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

0 Likes
0
2297
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

Traps are the notification portion of the SNMP protocol - when something happens, you get an alert that it occurred. For Network Management Cards, you can also tell it how often you want it to be delayed, repeat, and up to how many alerts.

Polling is the combination of a request and a response. You request data at the rate you specify (every minute, 5 minutes, etc) and you receive a request to that request with a value in integer, timeticks, or string depending on the information.

Typically, customers use both but it is not required. Polling is good for trending data over time where as traps are ideal to know when a condition occurs, such as replace battery. Here is another good supplement -> Trap and Polling

For a UPS device, you'll want to look at anything that begins with ups or is in the ups subtree. The PowerNet MIB contains all of the APC products in it and all of their OIDs. There are also OIDs not specific to APC information that are responded to that most SNMP devices, no matter the vendor, will respond to.

Can you clarify what type of UPS your Network Management Card is in? I can provide a helpful spreadsheet for some NMC applications that could tell you what events map to which traps so like "self test failed" or "bad battery" will identify what trap number to use.

As far as the particular tool, I am not quite sure how you can configure it to do specific actions based on traps but we can at least get you set up to receive them. Often, they have descriptions that are pretty straight forward but you may want to configure specific strings or map them to an action, i.e. log a ticket in your ticketing system.

Lastly, it may be helpful to load the APC PowerNet MIB into a MIB browser tool (such as GetIf or iReasoning) to browse the MIB and read the descriptions of the particular OIDs if your Cisco tool does not have an integrated MIB browser. Another option is to do an SNMP walk (which will GET/request all possible OIDs) in order to identify all of the possible items that you could poll. In your MIB browser, you'll find the ups subtree by navigating to .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups (or .1.3.6.1.4.1.318.1.1.1) and you can actually look at all the traps at .iso.org.dod.internet.private.enterprises.apc.apc# (or .1.3.6.1.4.1.318.0) and then you'll see the different trap numbers. The trap numbers will change the last number in the numerical identifier - .1.3.6.1.4.1.318.54 - would be trap #54.

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 3
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

0 Likes
0
2297
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

Check .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsBattery.upsAdvBattery.upsAdvBatteryReplaceIndicator / .1.3.6.1.4.1.318.1.1.1.2.2.4 for replace battery or not and .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsOutput.upsBasicOutput.upsBasicOutputStatus / .1.3.6.1.4.1.318.1.1.1.4.1.1 for the status of the UPS (if it is online or on battery or any other state).

Reply

Link copied. Please paste this link to share this article on your social media post.

Anonymous user
Not applicable

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

0 Likes
0
2297
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

My main purpose is trying to use the third party SNMP devices to monitor UPS' alarm and to be informed when the UPS is off line and its battery is dead.

First of all , I would like to know what difference between SNMP polling and SNMP traps.  

For SNMP traps:     If I will let the third party SNMP device to receive the SNMP traps , How do I let the third party SNMP device understand the UPS' trap  and translate those traps to a readable Alarm message?

For SNMP polling:   I already imported the UPS' MIB (file: powernet407) to the third party SNMP devices.  But I see there are so many Tables (see below picture) in the MIB.  I do not know which Table is for checking if the battery dead , which table is for checking if the UPS is dead ? 

2200_mib1.jpg

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

0 Likes
0
2298
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-01 05:30 AM . Last Modified: ‎2024-03-05 01:31 AM

Traps are the notification portion of the SNMP protocol - when something happens, you get an alert that it occurred. For Network Management Cards, you can also tell it how often you want it to be delayed, repeat, and up to how many alerts.

Polling is the combination of a request and a response. You request data at the rate you specify (every minute, 5 minutes, etc) and you receive a request to that request with a value in integer, timeticks, or string depending on the information.

Typically, customers use both but it is not required. Polling is good for trending data over time where as traps are ideal to know when a condition occurs, such as replace battery. Here is another good supplement -> Trap and Polling

For a UPS device, you'll want to look at anything that begins with ups or is in the ups subtree. The PowerNet MIB contains all of the APC products in it and all of their OIDs. There are also OIDs not specific to APC information that are responded to that most SNMP devices, no matter the vendor, will respond to.

Can you clarify what type of UPS your Network Management Card is in? I can provide a helpful spreadsheet for some NMC applications that could tell you what events map to which traps so like "self test failed" or "bad battery" will identify what trap number to use.

As far as the particular tool, I am not quite sure how you can configure it to do specific actions based on traps but we can at least get you set up to receive them. Often, they have descriptions that are pretty straight forward but you may want to configure specific strings or map them to an action, i.e. log a ticket in your ticketing system.

Lastly, it may be helpful to load the APC PowerNet MIB into a MIB browser tool (such as GetIf or iReasoning) to browse the MIB and read the descriptions of the particular OIDs if your Cisco tool does not have an integrated MIB browser. Another option is to do an SNMP walk (which will GET/request all possible OIDs) in order to identify all of the possible items that you could poll. In your MIB browser, you'll find the ups subtree by navigating to .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups (or .1.3.6.1.4.1.318.1.1.1) and you can actually look at all the traps at .iso.org.dod.internet.private.enterprises.apc.apc# (or .1.3.6.1.4.1.318.0) and then you'll see the different trap numbers. The trap numbers will change the last number in the numerical identifier - .1.3.6.1.4.1.318.54 - would be trap #54.

Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of