Using a static IP on a Profile Server I need to monitor latency to terminals which use DHCP. Can NetFlow Traffic Analyzer monitor one IP to many IP and log latency? Thanks.
Netflow is a Cisco designed protocol that does not make any attempts to record latency, it's all about bandwidth utilization, so NTA also does not track latency.
There is a feature in NPM called quality of experience that uses an agent and can display aggregated trends of DHCP request latency. Also in NPM there is a feature called Netpath that can validate the average time to get a response on the DHCP request port, but wouldn't actually show the time to resolve a real DHCP request as it is a more network centric feature. Also, SAM can track response time of DHCP requests from the polling engine to a DHCP server. Also with SAM I you can also track average connection latency using the new Application Dependency Mapping feature. Each of these would be using slightly different methods to track the results so the right one to use depends on which modules you have and what you are actually looking to show.
Many thanks for your reply. I'm investigating the Quality of Experience for DHCP latency, and have looked at the criteria for Netpath. I was uncertain if it was possible/useful when setting a static address (Agent) to a Profile server, to DHCP address (two full ranges), seeing login results could be effectively monitored for latency links. We have the SAM module, so I'll look at the Application Dependency Mapping feature as well. Regards SS.
