Joe_Public

The problem with that is, you still need to have all your interfaces defined and they show up as down interfaces in Network Summary and Top10 These stats then invalidate your reports. We have two access servers with 3 x 30 interfaces each for ISDN backup. As an example, we had a power outage at our main distribution…

I can't believe this is still not being implemented into the next version. It is such a fundalmental requirement for network monitoring to be able to see and be alerted when a backup line becomes active. It has been used by your competitors for years and is one reason i am still having to use two sets of monitoring tools…

Are we going to get the option to alert when an interface becomes active as opposed to when the interface goes down, so that we can overcome the age old problem of not being able to monitor ISDN lines without having a million and one down interfaces shown in Orion?

Deleted the trigger and re-ran the fixcollation. It failed with a timeout on the trapvarbinds table. I trunkated the table then ran the fix again and this time it completed successfully. I've upgraded to version 8.5.1 SP3 and everything now looks to be working correctly. Thanks for your assistance with this issue Mark.

Quote: ' So you are using stand alone text boxes and not the labels tied with nodes, interfaces etc. correct. How are you using the map? Do you have a background you constantly update and are swapping out the background and editing the map?' I have to use both the lable and a text box if i want to have 2 lines of writing…

Thought i'd try another upgrade this morning but when it runns the configuration wizard it fails with the message ‘[SQL-DMO]The passed ordinal is out of range of the specified collection.’ Has anyone seen this message?When i roll back to ver 8.1.3 everything works fine

Cool .. thanks for your help mdriskell

Case # 37255 I have already tried the upgrade and that is where i see the problem. I get this SQL error on Network Overview. This doesn't happen on ver 8.1.3. I'm running Orion on a virtual server so playing with updates and rolling back isn't a problem. When i roll back to version 8.1.3 everything works again.

Case # 37255. I keep asking for updates, but all i get is the same questions i've already answered and sent information about.

mmm ... i've had one subimtted for weeks and although i keep chasing, they don't come back with any help. I wasn't even told about the SQL fix. It does seem to have made some difference so i may go ahead and upgrade to 8.5.1 again on Monday to see if i still get the errors. Thanks for your help. 

Would that update in real time? If its possible to do that i'll give it a try. I just find it annoying that i have to write my own scripts to replace the default alerting tools that have worked perfectly well up to version 10.x I can understand that people may not want to see interfaces that have an unknown status but…

I contacted support for a different issue (list resources stopped working). The solution i was given also fixed the wireless Thin client issue: 1. Login to your Orion server as a local administrator. Stop all Orion services from Orion Service Manager. Replace Job Engine v1 2. Go to…

You better get used to the passing of space and time if you are waiting for Solarwinds to resolve your issue. I've had a ticket open since 17th March and still have no fix and very little contact. Considering it's an SLX contract i'd expect better !!

I've tried to run this but it comes back with the error: An exception occurred while attempting to fix th 'NodeHasChangedAlert' is not a constraint. Could not drop constraint. See previous errors. Any ideas?

Well as this was another half arsed attempt by solarwinds at giving us ISDN monitoring, the way to do it is quite long winded. I don't know why this should be so difficult, WhatsUpGold has provided this for about the last 8 years., however here's what i did. First all of the ISDN interfaces that receive connecctions i…

Well i hope we can see when ISDN backup lines become active. I can't believe we're still waiting for this !!

Yeah .. thats how i got round the alerting, but the main issue i have is that the Down Interfaces on the main page in NPM doesn't show 'Unknown' interfaces. If you power off a switch, or lose your WAN connection then all the interfaces go into 'unknown' status. These don't show in the Down Interfaces box and i really need…

Hi llancup Have you managed to find a solution to this problem? I've upgraded from 8.1.3 to 8.5.1 SP3 and now find i have ths problem.

Don't do it. 9.5 is slow, unreliable and completely user unfriendly. stick with 8.5 till this becomes more stable.

Never mind ... i've got it working.