Comments
-
This would be a nice option because most networking equipment has more than 1 IP address.
-
Same here I think we should have the option to disable certain sensors.
-
Well I have Version 3.6 and I'm still experiencing the same problem. No matter if I have the scripts using the .custom option or not I still have a memory issue. I have ORION NCM but the scripting isn't as powerful as it is in CatTools so this is why I prefer to use CatTools for my IOS Updates. Even after the activities…
-
I already had it set to Clear the Log pane with every action. I even set it to not to log to a file and it doesn't make a difference.
-
I changed my scripts to pushed everything into the .custom file that is loaded with the Device Script and still the same issue. Also on my Reload Function I never do an immediate reload because of losing connectivity so I reload it in a minute which give me time to logout of the device. I have attached the scripts again so…
-
Opening a TAC case with them now.
-
Here's the show inventory for the SFP modules NAME: "TenGigabitEthernet3/1", DESCR: "SFP-10Gbase-SR" PID: SFP-10G-SR NAME: "TenGigabitEthernet3/2", DESCR: "SFP-10Gbase-SR" PID: SFP-10G-SR NAME: "TenGigabitEthernet3/3", DESCR: "SFP-10Gbase-SR" PID: SFP-10G-SR NAME: "TenGigabitEthernet3/4", DESCR: "SFP-10Gbase-SR" PID:…
-
I'll modify my scripts and see what happens from there. I'll give the results after I complete some testing.
-
Well my maintenance ran out the end of last month so I'll wait until a release comes out that fixes the issue and renew my contract then.
-
I installed it as Administrator and I'm running it as the administrator. Also I don't have Vista UAC running. This is x86 and Vista Enterprise Edition SP2. I was watching with Process Explorer and I can see that the dll is started but then it immediately crashes several times and thats when I get the Error but then it will…
-
Using the pseudo code from Cisco on the above information if (entSensorStatus == ok) then if (evaluate(entSensorValue, entSensorThresholdRelation, entSensorThresholdValue)) then if (entSensorThresholdNotificationEnable == true)) then raise_alarm(sensor's entPhysicalIndex); endif endif endif if (Status == ok) then if…
-
Nope, no show snmp mib entity indexmapping but if I snmpwalk against the switch using this oid "1.3.6.1.2.1.47.1.1.1" which is the entity mib, I do get this back from it: SNMPv2-SMI::mib-2.47.1.1.1.1.7.3085 = STRING: "Te3/1 Bias Current Sensor" SNMPv2-SMI::mib-2.47.1.1.1.1.7.3086 = STRING: "Te3/2 Bias Current Sensor"…
-
So I used it and it works great for my custom Report Version Information script but when it comes to backing up the config, it hangs. It says stepping past ---(less but it never does. I've opened a ticket with Solarwinds because this looks to be a bug.
-
I completely forgot about the variations tab. I don't ever use it so I forget its there. Thanks.
-
Okay so digging through this using snmp I can see what ser is saying is true. If you look at my snmpwalk of the interfaces it is set to true on the evaluation of the Bias Sensor, so it isn't a problem with Solarwinds but like ser said it's a problem with Cisco. Current Sensor Value…
-
Yep just found it searching on Cisco SNMP. Thanks
-
That's what is strange. Solarwinds is getting from SNMP but I don't know why it won't show up in the details. Very strange.
-
Here is the script that is causing a problem, I only have one other script and it's based off of this so whatever is fixed in this one will correct my other script. If in fact it is a script problem. Also it is using Mega Bytes and has actually used over 1Gig of memory before but if I use the same amount of devices with an…
-
I'm running 3.5 and have been since it came out. Any script that I write will continue to increase the amount of memory being used but I can run the same amount of devices using an included script and the memory fluctuates like its supposed soI have no idea what is wrong with my scripts compared to an included script.
-
I just went ahead and wrote my own script to pull apart the show version and output the same information that the Report.Version table Activity does. Thanks for the quick response.
-
3.5
-
There is a problem on Cisco's side. If you look at the snmp data it doesn't match up with the cli. Mine had a threshold in SNMP but not in the cli now how is that a Solarwinds problem.
-
My TAC Case is 623992177 and is still active.
-
I had a problem with not getting responses or failures with CatTools waiting for an echo of a command. I had to write custom section in my scripts to send commands and only look for the command itself. The reason is because some older switches or routers for that matter will change how the prompt looks. See CatTools…
-
issue has been resolved after working with Steve Welsh on the issue. It took some major digging but in the end the problem was using the CatTools API within my scripts. After talking to Steve this was never designed to run in an activity but on external scripts which I knew but I didn't know it would cause a problem like…
-
The problem is the sub-routine "SendPostEnterEnableModeCommands()" modifies the cli preference pager option and changes it to disabled. The sub-routine "SendSessionTerminationCommands()" then re-enables the pager. Now the F5 sees a change and I have to go in and manually sync the devices. This is very problematic. I have…
-
A) Either the threshold is set to an incorrect number or B) the SensorThresholdRelation should be a 4 instead of a 2 which is GreaterOrEqual
-
Anybody know what oid that Solarwinds is pulling to get the Bias Sensor Current?
-
This is a 4506-E Supervisor 7 running IOS-XE Software: cat4500e-universalk9.SPA.03.03.00.SG.151-1.SG.bin sh int transceiver If device is externally calibrated, only calibrated values are printed. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. NA or N/A: not applicable, Tx: transmit, Rx: receive. mA:…
-
Here's whats even crazier. If I run the command "show interfaces transceiver detail" this is what I get. mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold…