we added LAN switches (L2/L3) to the PI2.0. There are some strange things:
Thing 1 Alarms - configured the switch like this:
logging buffered 16384
logging host xxx.xxx.xxx.xxx
Port 1- 24 Access Ports
no logging event link-status
logging event link-status
-> But the Prime Infrastructure generate up/down Errors of the access Ports
Deploy a custom template with stopping interface availability polling.
But didn't work.
-> How can we stop polling? Or configure the switch not to have up/down errrors from access ports?
Thing 2 - configured the switch like this:
snmp-server enable traps envmon fan shutdown supply temperature status
3750x with two power supplies, move one of them and syslog arrived at the prime.
But there is no alarm. I can see also the event in the local logfile.
Is saw that this is not supported at the moment - is that right?
If so, when will this be supported?
What global config parameter are recommended for L2/L3 switches logging/syslog?
well let's see if port groups is the solution.
All the other things are just workarounds and we are confused how to treat LAN switches.
Our customers used templates for access switches to tell the device what is necessary to monitor. If prime does it from now, we should have the information what is necessary to configure on Switches.
I'll let you know, if we have the right answer.
I have exactly the same issue.
- snmp traps are disabled on access ports
- log messages are disabled on access ports
- interface health monitoring is deployed only to a dynamic port group which is containing the uplink ports.
But we were flooded by link down alarms from accedd ports. :-(
Any idea what I'm doing wrong? Thank you!