Comments
-
Change the drop down from contains any keyword to does not contain. Reversing that logic should filter it. I use similar filters in my environment.
-
I have made that suggestion. The network group currently isn't sending those messages to out SolarWinds or Kiwi syslog instance.
-
I think if it is reporting and IEEE level, they always get full power. The connected device would have to be able to negotiate power levels for that to change. Negotiations are usually on power up though. This device may just "get" full 15.4W possible port output because it didn't ask for a different level. We had that…
-
I had not been able to improve this, but I think I will be reviewing our configuration with what bsciencefiction.tv and @Jay Garcia have tried to see if my problem is one of these.
-
I have heard that the 3560 v2 switched have OIDs and that may be why they are showing up differently.
-
I created a Custom Table Resource to show all the BGP routes with issues. Maybe this will help you.
-
This was happening to us as well on that 30 day cycle. I don't recall which retention setting this is, but there is one that clears the state, and clears old routes out of the database. Then they are free to fire the alert again, especially if those routes are still in the routing tables on the router. The other thing we…
-
It is worth noting that the last NPM update we did reset this and I had to go back and change it again. So some updates seem to change my desired settings.
-
Cisco WS-C3560V2-48-PS-S model 48 port PoE switches are being mis-identified as Wireless Autonomus AP on their node page in Orion NPM. I was asked to post this here in reference to case #121060.
-
Thanks, that I saw, but I can't see any percentage based interface error components for the alert. I did in a page resource, just not the alert.
-
That one is actually from the controller main page. It would be nice if that line was in NPM somewhere and if a device shows up there, that it lists the details of what it found in NPM.
-
The caveat here is this sets the state in Cisco tools, but I don't know that this translates back to NPM.
-
We have had the EOC for a long time, since before I started here. Even the newest version needs improvement. We have tried to create custom views in it for others, but when others log in, they can't see the views. Something isn't right there, and SolarWinds support hasn't figured out what. It isn't the ideal solution right…
-
I will be looking into this. I suspect that there are no current entries in the table between the edge routers and the remote sites. My SQL skills are not far along right now, so adding new entries might be a challenge right now.
-
Cisco Prime is the result of wireless and wired management tool mergers (Cisco WCS and CiscoWorks). The predecessor to Prime we used to use was wireless only. It aggregated our 5508 WLCs in one overseeing device to aggregate data and reports for everything. It also has the ability to push out configuration templates for…
-
I have seen that problem here when shifting things around on our pollers. It is almost always an SNMP problem for us. We have some devices like some APC UPS devices not be able to list to multiple pollers in their configuration. So when a couple were moved to balance loads, those pollers were not allowed to connect and…
-
I got a reply from Cisco yesterday confirming my account stuff was all set up for the SmartAdvisor, so I ran the tool again today. After about an hour of it stuck 2/3 through the items it detected, I got an error.
-
Our security guy and my CIO visibly cringed when I said I had to create a local account rather than use an AD account. They don't like us using local admin accounts on servers here. They want to tie it back to an AD account and only one person associated to it for accountability. Maybe there was a problem tracking…
-
I don't even have all the switches connected correctly in my groups. Some of the groups only show the site router and first internal switch connected and maybe the upstream router. Not sure what I am missing yet.
-
I still have not fully converted over to the new alerting. I am uneasy about missing something if the old vs new methods don't trip at the same times.
-
I don't know if yours is the same problem I have had in the past, but I have had the Settings > Views > Views by Device Type settings be wrong on occasion. If the drop down by the device you are monitoring is set to Cisco ASA, it might miss-identify, or really just display a Cisco ASA summary page instead of what should be…
-
${Interface.Name} should just give the first part (GigabitEthernet1/0/11) without the description. ${Interface.Caption} does give out the name and description with the special character in between in my tests. Either way, I have alerts now that use ${N=SwisEntity;M=InterfaceName} and that only gives out the…
-
There might be a disconnect here. Collecting client signal strength may not mean all of those are shown on the map. They are shown and updated in the wireless tables and seem up to date. I just looked at our Wireless Summary view when selecting clients, and see pretty up to date client signal strengths there. That does not…
-
I am sorry it isn't working for you. It was telling me about a changed device for one with the same model, but a different serial number. But maybe somewhere in the hardware there was enough of a difference it caught it.
-
I never had to give admin rights to the person that needed to adjust a report, but he did have node management rights for the servers he was interested in. Just the windows servers, he didn't have node management rights to linux servers or network gear.
-
I agree with you that the Platform page does, however if you are troubleshooting issues with a user that doesn't have access to that page, it becomes harder to see which web server they are connected to.
-
I have used this view for Cisco devices. It works well. I have also used the Engineer's Toolset Switch Port Mapper to look at what the switch was set for, whether or not it sees an IP on the port or even the MAC address. If it sees the Mac Address, but not the IP Address, verify the port VLAN setting, then verify the…
-
This seemed to work.
-
The interesting thing about that ${N=SwisEntity;M=DetailsUrl} entry is that is what is in the reset condition and that isn't working either.