Temp .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.2 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.3 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.4 CPU .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.2 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.3 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.4.0 (rollup of all CPU) Memory .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.1 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.2 Power Supplies .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.2 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.3 Fans .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.2 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.3 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.4 .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.5
For traffic monitoring it is a little more tricky since they can be spread out into many different mib files depending on what type of traffic you are trying to monitor. You can a work processor (like Microsoft Word) and be able to search each MIB that way, but it is time consuming. A MIB browser is definitely the best way to browse network device MIBs, as it lets you load all MIB files at once and search all at once. It also parses the files into an easy-to-read format. I have used Adventnet MIB browser in years past which worked very well, but there are surely many others out there that would work for you needs as well.
Thanks for the anwsers. I found the MIB and try to exploit them with MIBBrowser. I foud the different OIDs for temperature and other stuff but not yet for port traffic monitoring.
What i need for traffic is quite basic. Switches are used for iSCSI SAN only (one dedicated vlan, 1 network) and i only need to see global traffic in and out (in MB/s) on each interface.
vt1012
212 Posts
0
January 7th, 2014 08:00
The sensor OIDs for the 70xx are as follows:
Temp
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.2
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.3
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.4
CPU
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.2
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.3
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.4.0 (rollup of all CPU)
Memory
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.1
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.2
Power Supplies
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.2
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.3
Fans
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.2
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.3
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.4
.1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.5
For traffic monitoring it is a little more tricky since they can be spread out into many different mib files depending on what type of traffic you are trying to monitor. You can a work processor (like Microsoft Word) and be able to search each MIB that way, but it is time consuming. A MIB browser is definitely the best way to browse network device MIBs, as it lets you load all MIB files at once and search all at once. It also parses the files into an easy-to-read format. I have used Adventnet MIB browser in years past which worked very well, but there are surely many others out there that would work for you needs as well.
Hope this helps!
-B
wadcyr8
2 Posts
0
January 9th, 2014 19:00
Hi All,
Thanks for the anwsers. I found the MIB and try to exploit them with MIBBrowser. I foud the different OIDs for temperature and other stuff but not yet for port traffic monitoring.
What i need for traffic is quite basic. Switches are used for iSCSI SAN only (one dedicated vlan, 1 network) and i only need to see global traffic in and out (in MB/s) on each interface.
I will continue my search in the MIBs,
regards
cmoorehsu
3 Posts
0
January 30th, 2014 19:00
Would you mind sharing the OIDs you've found? I'm in the situation. Thanks