Unsolved

This post is more than 5 years old

2303

April 16th, 2019 17:00

Manage S3048-ON switch via OME 3.0

Hi all,

We have a 6 x S3048-ON switches stacked together.

We are trying to configure the stack so that it can be managed in OME 3.0. Basically we just want any alerts to be send to OME so we can be notified.

We configured the SNMP in the stack as follow:

mgr-B1#show running-config snmp
!
snmp-server community dice-mgr-network ro
snmp-server enable traps bgp
snmp-server enable traps snmp authentication coldstart linkdown linkup syslog-reachable syslog-unreachable
snmp-server enable traps vrrp
snmp-server enable traps lacp
snmp-server enable traps entity
snmp-server enable traps stack
snmp-server enable traps stp
snmp-server enable traps ecfm
snmp-server enable traps vlt
snmp-server enable traps xstp
snmp-server enable traps isis
snmp-server enable traps config
snmp-server enable traps envmon cam-utilization fan supply temperature
snmp-server enable traps ecmp
snmp-server enable traps mac
snmp-server host 192.168.30.202 traps version 1 dice-mgr-network udp-port 162

Then we added the stack management IP to OME via SNMP protocol which was successful. But we found the message displayed by OME is rather too general, for example if I unplug a PS of the switch it displays:

Apr 16, 2019 12:00:04 PM
System Health
Health Status of Managed device
Device health has deteriorated.

 

So I am wondering if this is the limitation of the OME 3.0 or I have missed some configuration in somewhere?

 

Cheers,

Derrick

April 16th, 2019 21:00

Ok, I have made some progress by changing version from 1 to 2c

 

snmp-server host 192.168.30.202 traps version 2c dice-mgr-network udp-port 162

And now OME definitely receives more traps from the stack. But many of the traps are unknown to OME such as:

 

Unknown trap received with enterprise OID: .1.3.6.1.4.1.6027.3.26.1.5 specific trap ID: 26 generic trap ID: 1 and variable bindings: 1.3.6.1.4.1.6027.3.26.1.5.2.1=2, 1.3.6.1.4.1.6027.3.26.1.5.2.2=PSU_FAN_STATUS: Fan 1 in PSU 2 of Unit 3 is up, 1.3.6.1.4.1.6027.3.26.1.5.2.5=0, 1.3.6.1.4.1.6027.3.26.1.5.2.3=3, 1.3.6.1.4.1.6027.3.26.1.5.2.6=1, 1.3.6.1.4.1.6027.3.26.1.5.2.7=2, 1.3.6.1.4.1.6027.3.26.1.5.2.9=-1, 1.3.6.1.4.1.6027.3.6.1.1.2.0=83, from address: 192.168.30.80

I checked the MIB section of OME it looks like there are lots of network traps already. I am wondering what other MIB I may need to import to OME?

 

Cheers,

D

Moderator

 • 

9.6K Posts

 • 

116 Points

April 17th, 2019 09:00

Hi,
I don’t see a way to get the full logs with OME, you could configure a syslog server separately though.

0 events found

No Events found!

Top