Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

HTTP not working to NAM module

I am working with a client whom has an NM-NAM module installed in their 3825 ISR. I can ping the address of the NAM, as well as connect to it via telnet. The issue at hand is that it will not allow any connections to the web based Traffic Analyzer . I have it configured according to the Cisco documentation. here is the configuration...

# ***** NAM configuration *****

!

# Time: Fri Aug 7 18:35:19 2009

!

# Version: 4.0(1)

!

ip interface internal

!

ip address 172.31.200.2 255.255.255.0

!

ip host "LOMPLSNAM"

!

ip domain "odec.com"

!

ip gateway 172.31.200.1

!

ip broadcast 172.31.200.255

!

ip nameserver 192.168.1.53

!

ip http tacacs+ disable

web-user

user-name kmelton

account-mgmt enable

system-config enable

capture enable

alarm-config enable

collection-config enable

encrypted-password "NWU3Y2YxYzMzOTI5NjgyYjc2ZWEwYjQ1ZWU4NTNkNDVlZTk5NmQ3Zgo="

exit

!

ip http port 80

!

ip http secure port 443

!

ip http server enable

!

ip http secure server enable

I have reloaded the NAM twice, but it does not help.

Thanks

4 REPLIES
Cisco Employee

Re: HTTP not working to NAM module

It looks like you have SSL enabled. Try:

https://172.31.200.2

Community Member

Re: HTTP not working to NAM module

Yeah we had tried that and it still does not answer. We even had a tech try locally on the same network where the NAM is and we cant get to it via https or http. Still answers just fine to SSH and telnet though.

Re: HTTP not working to NAM module

It sounds like an issue with the http server that persists even when the nam reloads.

Try:

1. Change the port of http: ip http port 8080

2. Disable and re-enable ip http: ip http server disable, ip http server enable.

There may be a firewall l in between that could block ports 443 and 80

Cisco Employee

Re: HTTP not working to NAM module

I would suspect a firewall or access-list, then. If you post a show tech from the NAM, I can confirm if the http server is listening on the required ports, but I would bet that something is blocking both tcp/80 and tcp/443 to this device.

268
Views
0
Helpful
4
Replies
CreatePlease to create content