NetBrain's Traceroute function does not consistently apply user-specified max hops and timeout values during execution, with some device platforms disregarding these inputs entirely. This enhancement would ensure the Traceroute engine reliably enforces configured max hops and timeout parameters across all supported device types. Consistent parameter enforcement would give customers predictable, accurate trace results and reduce troubleshooting effort caused by unexpected trace behavior on specific platforms.
Open
Enforce configured max hops and timeout values in Traceroute execution
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain Universityor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
