Goline Logo

News

  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

SNMP Monitoring APC UPS – Useful OIDs

Paolo Caparrelli Networking 22 June 2022

Monitoring APC UPS – Useful OIDs

 Battery capacity
1.3.6.1.4.1.318.1.1.1.2.2.1.0
Value type Gauge Float
Division = 1
Value %

Run Time Remaining
1.3.6.1.4.1.318.1.1.1.2.2.3.0
Value type Gauge Integer
Division = 6000
Value minutes

Battery Temperature
1.3.6.1.4.1.318.1.1.1.2.3.2.0
Value type Gauge Float
Division = 10
Value °

Battery Actual Voltage
1.3.6.1.4.1.318.1.1.1.2.3.4.0
Value type Gauge Float
Division = 10
Value VDC

Input Line Voltage
1.3.6.1.4.1.318.1.1.1.3.3.1.0
Value type Gauge Float
Division = 10
Value VAC

Output Voltage
1.3.6.1.4.1.318.1.1.1.4.3.1.0
Value type Gauge Float
Division = 10
Value VAC

Output Load
1.3.6.1.4.1.318.1.1.1.4.3.3.0
Value type Gauge Integer
Division = 10
Value %

Input Frequency
1.3.6.1.4.1.318.1.1.1.3.3.4.0
Value type Gauge Integer
Division = 10
Value Hz

Output Frequency
1.3.6.1.4.1.318.1.1.1.4.3.2.0
Value type Gauge Integer
Division = 10
Value Hz

Last Battery Test Status
1.3.6.1.4.1.318.1.1.1.7.2.3.0
Division = 1
Value #
Set Value lookup on channel

Battery replace
1.3.6.1.4.1.318.1.1.1.2.2.4.0
Division = 1
Value #
Set Value lookup on channel


Monitoring APC UPS – Useful OIDs
If you feel moved to monitor your APC UPS, here are some of the OIDs you'll want to use. These OIDs definitely work with the APC AP9617 management card which plugs in the back of APC devices.

General

UPS Type .1.3.6.1.4.1.318.1.1.1.1.1.1.0

String containing UPS model, eg: Smart-UPS 1000

Battery Information

Battery capacity .1.3.6.1.4.1.318.1.1.1.2.2.1.0

Battery capacity as % of total

Battery temperature .1.3.6.1.4.1.318.1.1.1.2.2.2.0

Battery temperature in Celcius of Farenheit – depending on how UPS is configured

Battery runtime remain .1.3.6.1.4.1.318.1.1.1.2.2.3.0

Total battery runtime available based on current load.

Battery replace .1.3.6.1.4.1.318.1.1.1.2.2.4.0

If result = 2 then battery needs replacing (1 = ok)

UPS Input

Input voltage .1.3.6.1.4.1.318.1.1.1.3.2.1.0

Input voltage, to the UPS device

Input frequency .1.3.6.1.4.1.318.1.1.1.3.2.4.0

Input frequency in Hz

Reason for last transfer .1.3.6.1.4.1.318.1.1.1.3.2.5.0

String containing reason for last transfer to battery power

1 No events
2 High line voltage
3 Brownout
4 Loss of mains power
5 Small temporary power drop
6 Large temporary power drop
7 Small spike
8 Large spike
9 UPS self test
10 Excessive input voltage fluctuation

UPS Output

Output voltage .1.3.6.1.4.1.318.1.1.1.4.2.1.0

Output voltage from the UPS

Output frequency .1.3.6.1.4.1.318.1.1.1.4.2.2.0

Output frequency in Hz

Output load .1.3.6.1.4.1.318.1.1.1.4.2.3.0

Output load expressed as % of capacity

Output current .1.3.6.1.4.1.318.1.1.1.4.2.4.0

Output current in Amps

Diagnostics

Comms .1.3.6.1.4.1.318.1.1.1.8.1.0

Whether SNMP agent is communicating with UPS device 1 = yes, 2 = no

Last Self Test result .1.3.6.1.4.1.318.1.1.1.7.2.3.0

Result of last self test as text string. eg: pass or fail.

Last Self Test date .1.3.6.1.4.1.318.1.1.1.7.2.4.0

Date of last self test

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x