Comments
-
3/5/2025 2:03:20 PM 03258 stacking: ST2-CMDR: Member switch with Member ID 3 removed due to loss of communication Source Time 3/5/2025 2:03:21 PM Source XXXXXXXXXXX (XXX.XXX.XXX.XXX) Vendor HPE Machine Type Aruba JL258A 2930F-8G-PoE+-2SFP+ Switch Log Type Syslog Level Warning Facility 22 Facility Name local use 6 Severity…
-
Syslog 3/5/2025 2:03:20 PM 03258 stacking: ST2-CMDR: Member switch with Member ID 3 removed due to loss of communication Source Time 3/5/2025 2:03:21 PM Source XXXXXXXXXXX (XXX.XXX.XXX.XXX) Vendor HPE Machine Type Aruba JL258A 2930F-8G-PoE+-2SFP+ Switch Log Type Syslog Level Warning Facility 22 Facility Name local use 6…
-
Agreed I am doing this via trap currently
-
Look in Syslog for 03258 stacking you will see an alert if you pull one in test the clearance for this is to put in a statement for stack active
-
Will take one soon
-
So my trigger is 03258 stacking I will the fire a log generated alert Clearance stack active
-
Madness why create search by vendor or device if you cannot select ? Not a feature request but a bug
-
Yes agreed
-
Syslog trap then alert from trap 3/5/2025 2:03:20 PM 03258 stacking: ST2-CMDR: Member switch with Member ID 3 removed due to loss of communication Source Time 3/5/2025 2:03:21 PM Source XXXXXXXXXXX (XXX.XXX.XXX.XXX) Vendor HPE Machine Type Aruba JL258A 2930F-8G-PoE+-2SFP+ Switch Log Type Syslog Level Warning Facility 22…
-
Thanks I am still awaiting updates linked them to your case
-
But during that time i assume you would not be monitoring?
-
Yeah i get what you are saying re Log analyzer hence me creating my solution on a serial number not populating
-
Morning there are other ways to tackle this one is via syslog, if the message contain 03258 stacking or 03262 stacking then rule fires a condition to create an alert. The clearance for this is message contains stack active. Another way via polling is to create a custom poller to obtain the serial numbers of the stack…
-
I am in the early phases of support only uploaded diagnostic yesterday will keep you posted
-
If you search for an AP by name it still works
-
Yes I have the same issue 01971355
-
Watching this as we are also looking at deploying could you expand if this buddy drop caused further issues please?
-
I resolved it by setting up the custom poller but it worries me that something I assume is working is not and I have to create custom pollers.
-
Solarwinds stated this as design! Here is the actual response from Solarwinds I hope you are doing well. The issue you are experiencing is due to Orion's design, which removes Hardware Sensors if the status differs from "OK". We recommend you create a Universal Device Poller, as you've already done, and then make an alert…
-
Its a table so setting it like this worked, i will now raise the case with Solarwinds why it is not working OOB
-
Back at work today I took screengrabs I am looking for status of either OK (so I can reverse the logic) or fault_input neither of which are listed. When I show list I get 940 objects
-
The problem I have now is when trying to create the custom poller alert I cannot find the value i need listed and "unknown" does not work. I am looking for state of FAULT_INPUT Here is my current rule. Its a drop down menu and does not list OK (if it did I could use if not OK) or fault_input, I list unknown and it does not…
-
Case raised Case # 01094547
-
No its still something I need to revisit I put a band aid on by setting up some traps then alerts from the traps
-
No its still something I need to revisit I put a band aid on by setting up some traps then alerts from the traps
-
Yes passes SNMP test just fine
-
Which release can we expect this functionality to be in please?
-
thank you
-
thank you for your help on this
