Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,we get network issues, if one of our employees build a loop on a desktop switch in his/her office.My test enviroment looks like this.Switch A is a Cisco 4500 with SUP7 and IOS Version 03.03.00.SG. Switch B is an unconfigured Netgear GS108T Desktop...
Hi,I have two questions to PIs device temperature monitoring. 1) We have some stacked switches and some switches in a VSS. Also we have some switches with multiple temperature sensors. For example here the output of a C4506-E with a SUP7.#show env te...
Hi,we are used SNMP traps sent from our core switches to our PI 1.3 server to notify us about link down events. In this scenario we got emails only for link down events on our core switches.Now, we are using PI 2.0. It seems PI 2.0 checks link status...
I found a solution that works for me.I let PI treat Link Down Events as Minor Events.I created a new Virtual Domain and assigned all our Core Switches to this Domain. For this new Domain, I configured PI to send E-Mails on Minor and Major Events (Ope...
Hi,as far as I know, this is not possible. We configured our core switches to send link-up-down events as traps to PI. With this configuration, we got alarms only for link-up-down events on our core switches. We could not restrict it to specific port...
Hi Cuong,our PI 1.3 could display temperature of about 50 % of our devices. I would bet it depends on the hardware. For example PI 1.3 could display temperature of all our 4506-E devices.PI 2.0 can display the temperature of all our devices. We just ...
Hi Cuong,The message "port {0} is down on device {1}" is a bug of PI 1.3. It seems to be solved in PI 2.0. At least I did not see this message since we updated to 2.0.We did not configure the switches to send syslog messages to Prime. So, this could ...
