mcbridea

You can't use AD authentication services if you are not part of a domain.* *Except....there is a function called LDS that would allow a work around but this would need to be implemented by an AD expert.

Volume 2 is on IP SLA, Volume 3 is on NetFlow. The New to Networking series is technology specific rather than product specific. I am starting a series on product implementations though. The first one will be on alerting and alert logic, the second one may be on APM or NTA. Not sure at this point.

Can you see what your Orion and NTA licenses are? Launch license Manager. Does your NetFlow module match the Orion SL number?

I'll let the PM chime in on that as an FER. My concern is that if you start placing options that affect alerts in different places, it may complicate alert troubleshooting and application.

As a workaround you can bounce the NetFlow service.

It is impossible to connect several times in a millisecond. Can you do a paket capture on the Linux bot and see what is really happening?

You are correct. There used to be a way to do this but we had an issue where admins were shooting themselves in the foot by removing their admin views. I'll move this to feature requests.

Hi Robert, Thanks for the kind words. I'll contact you by IM/email. Andy

I'm still looking at ways to do this. What type of device are you connecting to? If it is a Cisco device, does it have IP SLA responder enabled? Are there any other IP SLA operations going to this device? Andy

Can you give me some config snippets and NTA sereen shots?

I recommend browsing the MIB on the stack agent.

Dual processor will work.

http://mcbride-vm-dec-/Orion/Apm/Summary.aspx http://mcbride-vm-dec-/Orion/VIM/Summary.aspx http://mcbride-vm-dec-/Orion/SummaryView.aspx?ViewName=NPM%20Summary

Strange - can you open a ticket on that one?

I see. You could use the Universal Device Poller (UnDP) to polls the accessible OIDs. Note that several of the IODs are listed as not accessible. The Orion NPM admin guide has a good section on using the UnDP.

Hi Count, We have seen large environments run without this issue and smaller ones have the issue so it's not scale alone causing it. Some of the issue may be coming from the NTA deployment and overall environment. BTW SP2 is in support and will GA soon. It continues to improve performance. Andy

I knew it! :)

Now that is odd. When I did the calculations for 15 minutes I actually got 5.7 GB. That is why I said 7-8 is realsitic. I'll have this tested if you open a ticket on it.

Check the graph setting and ensure it is pointing to the correct UnDP.

Check you DNS resolution settings. If you set it to On Demand you can resolve the domain.

See this thread ->

Yes - that is true

Wouldn't NTA 4.x be recommended here?

Next I'd try a MIB walk on that device to see if there is anything strange in the IF tables.

Thanks for sending the link. The doc does need to be updated to reflect new capabilities. So that I can better understand, how many interfaces are you needing to have in the resource? If you have more that a few this chart will be very difficult to read. If that is the case, I recommend creating a report and add the…

Please open a ticket. The IP SLAM product team will have to comment on status.

If you have set the availability polling at 120 seconds and the Node Warning Level at 300 seconds (I think that is what you are saying) then the maximum downtime is time difference between the device ping failure and the next ICMP poll (an uncontrollable variable) + the Node warning level , 300 sec. The fast poll will…

I noticed your export is set to UDP 9996. The default port for NTA is 2055. If you change the port to 2055 you should receive flows. You can change the port on NTA to 9996 in NetFlow Settings, that may be easier than changing the exporter.

Hmmm. Please open a ticket on that one. May be a bug.

Also see this thread on a possible IOS bug with these symptoms.