Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

strange "up" messages and workaround ?

hey guys,

i have a strange problem here : i'm monitoring more than 50 CISCO 3548XL's here at the office. from time to time (preferably at night) we get a pager alarm stating that one of the switches (which one changes randomly) is "up" again. but it never went down.
ok, seems like the switch went to "unknown" state and "up" before it Orion considered it "down". since my alerts says "notify on status change", the pager alert seems correct. here comes the "but"... the switch never went to "unknown" state.
what i want to do now : Orion should report the switch state "up" only if the previous state was "down". alert suppression, got that in mind.
do i have to setup one alert for each device ?
i can't say "alert me when status of switch %1 is up if status of switch %1 has been down"...

hope someone understands my crude ideas here :-/

mihi est propositum in taberna mori

Find more posts tagged with

Accepted answers

All comments

DonYonce

I would change this alert from "anytime the status changes" to trigger when the switch port is "down".
It's probably switching into "warning" or "unknown" and then back to "up" before the notification gets out.

snowjay

I'm monitoring close to 100 Cisco switches (3500 varieties) and have never had that problem. But all my alerts are set to send an alert when they are "down" and send a reset when they are "up". I don't care about unknown or warning states.

bleearg13

Is it at all possible that you have an underlying network issue occurring? I've seen really bizarre things happen when spanning tree is not configured properly in a network that needs it. Unplugging a server on one switch would cause a completely different switch or node to "go down".

Seraphym

thanks for your feedback on this topic.

in fact some switches change to warning and then to up status really quick. so the node never goes down. it looks like just one polling can't reach the node. node goes to warning, next polling reaches target, node goes up.
i now changed the alert to notify only when a node goes "really" down. the up-notification is disabled.
@bleearg13 : had spanning tree in mind too. but all the servers connected to the switches are up and running without one second of downtime or non-availability.

mihi est propositum in taberna mori

Seraphym

maybe I found the solution.
the database maintenance jobs runs every night at 02:00 pm. the messages were always sent between 02:00 and 04:00. maybe our machine is simply not powerful enough. I thought 3,0 GHz and 4 GB ram should be enough...

mihi est propositum in taberna mori