27.03.2013 Views

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ip http cable-monitor<br />

5-58<br />

<strong>Cisco</strong> <strong>Broadband</strong> <strong>Cable</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Guide</strong><br />

Chapter 5 <strong>Cable</strong> CPE <strong>Command</strong>s<br />

When the cable access router has established connectivity with the CMTS over the cable interface,<br />

a service technician can use a web browser to remotely access the router and display the desired<br />

information.<br />

When the cable network is not operational and the cable access router is not online, the subscriber<br />

can access the tool with a PC connected to the router’s Ethernet ports. Technicians can then prompt<br />

the user for the information they need to determine the source of the problem.<br />

Enabling the <strong>Cable</strong> Monitor also enables the <strong>Cisco</strong> web server that is onboard the cable access router,<br />

which is the equivalent to entering the ip http server command. However, when the <strong>Cable</strong> Monitor is<br />

enabled, all other access, including CLI access, to the onboard web server is automatically disabled.<br />

Note When the <strong>Cable</strong> Monitor is enabled in the startup configuration file, the messages “Starting DNS<br />

process” and “Terminating DNS process” can appear in the messages displayed during boot-up on the<br />

console. These messages are normal and can be ignored.<br />

Disabling the <strong>Cable</strong> Monitor using the no ip http cable-monitor command also automatically disables<br />

the <strong>Cisco</strong> web server, which is the equivalent of giving the no ip http server command. When disabling<br />

the <strong>Cable</strong> Monitor, the console might display warning messages similar to the following:<br />

% monitor-209.165.202.131 is not in the database.<br />

% monitor-192.168.100.1 is not in the database.<br />

% Range [209.165.202.131, 209.165.202.131] is not in the database.<br />

% Range [192.168.100.1, 192.168.100.1] is not in the database.<br />

These messages can be ignored because they are simply confirming that the IP addresses used for the<br />

<strong>Cable</strong> Monitor are no longer being used for that purpose.<br />

The URL-IP-address and URL-mask arguments also specify that the class C private network<br />

192.168.100.0 is the default address pool for the temporary DHCP server that activates when the cable<br />

interface goes down.<br />

Note The <strong>Cable</strong> Monitor web interface does not work with the <strong>Cisco</strong> Easy VPN Remote web interface. To<br />

access the <strong>Cable</strong> Monitor web interface, you must first disable the <strong>Cisco</strong> Easy VPN Remote web<br />

interface with the no ip http ezvpn command, and then enable the <strong>Cable</strong> Monitor with the ip http<br />

cable-monitor command.<br />

Examples The following example shows how to enable the <strong>Cable</strong> Monitor for advanced mode, in which all status<br />

and diagnostic pages are displayed:<br />

Router(config)# ip http cable-monitor advance<br />

Router(config)#<br />

The following example shows how to disable both the <strong>Cable</strong> Monitor and the <strong>Cisco</strong> web server,<br />

preventing all web server access to the <strong>Cisco</strong> uBR924 cable access router:<br />

Router(config)# no ip http cable-monitor<br />

Router(config)#<br />

OL-1581-05

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!