nm-nam url collection

Unanswered Question
Mar 23rd, 2009
User Badges:

Hello,


is it possible to configure the nam to collect url information for http ports other than 80. We have some applications running on non standard http port.


andre

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Mon, 03/23/2009 - 10:23
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Unfortunately, this is not yet possible. The feature has been discussed before, though, but I do not have an ETA.

Joe Clarke Mon, 03/23/2009 - 14:35
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Correction. NAM 4.0 DOES have this capability, even though the help indicates that only tcp/80 is used. In order to use it, you must create a new protocol under Setup > Protocol Directory. The new protocol must have its master port be tcp/80. When that happens, the NAM will process URLs on that port.


The catch is that there is a bug with existing protocols in Protocol Directory. For example, LMS uses tcp/1741 by default, but the existing Protocol Directory entry does not have 1741 as a descendent of tcp/80. Therefore, URL capture does not work on that port.

aeggers Wed, 03/25/2009 - 02:12
User Badges:

hello,


thank you for this information. Do you know when the issue with the protocol directory will be fixed?


andré

Joe Clarke Wed, 03/25/2009 - 09:01
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Should be fixed in the next 4.0 point release. I am not sure when that will be, however. If your port is not already listed in pdir, then you don't have to worry. For example, you can create new protocols for ports like 8080 and 8088, and those will work for URL collection.

aeggers Thu, 03/26/2009 - 06:27
User Badges:

hi joe,


i have added port 8081 to protocol http and it works. Thank you for you support.


André

Actions

This Discussion