Comments
-
here's another one : Siemens OpenStage 40 Ip Phone SysObjectID : 1.3.6.1.4.4329.2.38.3.1.2 Same for the OpenStage 60 model... Regards, Sera
-
Hey Dayzt, i did the same. worked for me. but i had to reconfigure my menu bars as well as we have direct "custom links" to maps there. regards, josch
-
thank you for your reply. I tried 1 space, 2 spaces and 3 spaces. Still the discovery turns up with no node discovered. Kind of losing hope on this :-(
-
Thank you, Ng, I'll give it a try. cheers, josch
-
I'm playing around with the network discovery also. I can't get it to work either. Here's how my seedfile.txt looks like : Settings Auto Select Subnets = FALSE Auto Select Subnet Size = 17 PING Timeout = 2000 Max Concurrent PINGs = 350 Inter PING Delay = 100 PINGs Per IP Address = 2 SNMP Timeout = 1500 SNMP Retries = 2 Max…
-
mark, i did the upgrade to version 8.1.0 ... still i have the error. got a hint for me ? regards, josch
-
denny, thank you for your reply. inserting spaces fixed the problem. but... i only want to insert specific nodes. network discovery starts to scan the complete (estimated) subnet. anyway to avoid this ? if network discovery needs to scan all subnets of any of the given IPs... this would take days :-) another thing : it…
-
thx network guru. this solved the problem for me.
-
i'm having the same problem. i'd like to filter out all router within a specific ip address range and their BRI0 IF down. got no clue.
-
rwsim, we made a little quick-and-dirty solution for this problem. the keyword being "custom property". - create a custom property for the switchports you want to monitor. we name it "downtime" - create an alert for the switchports you want to monitor every time the switchport goes up, the alert writes the current date…
-
hey don, we had similar problems. what really boosted performance : create a simple start page with very few nodes and information displayed. this significantly improved the performance of the web interface. mihi est propositum in taberna mori
-
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
-
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…
-
Hey asl-support, could you send me the files ? I'd like to test it out here with our installation. regards, sera mihi est propositum in taberna mori
-
No, not yet. I think there are simply too many nodes to monitor (approx. 1000 nodes). After updating to ver. 7.8.2 it works fine now. Seems like the promised performance improvements worked I want to be able to group my nodes ! Argh !
-
I had the same problem. My startup-page took more than 1 minute to load My solution : create a custom startup-page with only the most important devices (i use the 6500 catalysts from our backbone) -> it will load really fast ! time to load now : 2 seconds hope this helps, it worked for me. mihi est propositum in taberna…
-
hey network guru, thanks for your tips. i solved in another way : i just created a view with 3 colum layout with each colum containing three views containing different telephone prefix areas, ranging from 01-09. as hopefully there are only a couple of nodes down at the same time, it's pretty easy to see in which region…
-
sounds too bad. i got approx. 800 routers here to add... network discovery is not an option (many different subnets). so i guess i need to manually add the devices some workmates from austria are trying to figure out a script way to add them. maybe they are succesfull ? if so, i'll post it here.
-
thx network guru for the answer. this sound pretty much like a pain in the a**. is there anyway to add a number of nodes from a list ? network discovery is not an option, the nodes are not in the same subnet.
-
thx a lot ! had the same problem. it works now.
-
Hello Don ! In the meantime the trial period for the Wireless Network Pack has expired... so I had to uninstall it. But I'd really like to understand this problem. So if you want to contact me, feel free to do so. Real Name : Joachim Kiefer Company : Filiadata GmbH Telephone number should be stored in your customer…
-
I did use the "Wireless Networks" application. However, the displayed data is simply wrong. The AP itself shows me zero clients connected, the "all active sessions" view shows me every laptop. strange. mihi est propositum in taberna mori
-
hey lars, i didn't do anything special when i added the AP's. some data can be read, some is unretrievable. strange behaviour. to me it looks like the management pack isn't really ready to be shipped. it's of no use at all for us since we only use CISCO devices. being unable to rely on the collected data from ORION... we…
-
thanks don, that solved the problem. must have overlooked the parameter.
-
well, we use two different monitoring programs here. we use orion primarily to keep historical data of nodes availability and traffic charts. it's our backup alarming system. but with this increase in maintenance fee... we are thinking about kicking it out of our data centers. on top of all, i submitted a bug which heavily…
-
hey mike, we are using 2x intel xeon @ 3,2 ghz 4 gb ram monitoring 1200 nodes + 9000 interfaces. running smooth... backup via IBM TSM scheduling every day at 05:00. we copy the full harddrive. regards, sera mihi est propositum in taberna mori
-
hey NG, figured that out too. But the scheduled rediscovery of the 836's sets the interfaces values back to the wrong speed values... which kind of suc***s. same problem with our 2950 switches here. interface bandwidth detection results in 10MBps (!), generating high interface load alarms. anyone has a permament solution…
-
We had the same problem with all our Cisco 836 Routers. Solarwinds couldn't figure out the correct port speed of the ADSL-Interface. As i'm too lazy to correct port speed manually on 800 routers (hey, grouping would be nice!), i disabled the alerts. The same problem occurs on Cisco 2950 switches and their gigabit-if's.…
-
i'm monitoring i.e. Cisco 3548XL in the same LAN segment. sometimes they generate an UP-alarm without sending any DOWN-notice or events. strange behaviour.
-
hm. strange. now that you mention it... there is no event logged for these alarms. now i'm stuck too. anyone got an idea ?