Using the Content Services Switch
Device Management Software

• Interfaces - Interface number and bridge to VLAN number.

• Circuits - VLAN number, IP address, IP prefix.

• System information - Name, contact, location, description, object ID, system up time.

• Management port - IP address and subnet mask.

• Access - Console, FTP, SNMP, Telnet, XML, console and virtual authentication.

• SNMP traps - Trap hosts, generic traps, enterprise traps.

• Logging - Setup, subsystems, via email.

• Services - Name, IP address, type, protocol, port, domain, weight, maximum connections, keepalives.

• Owners - Owner name, address, billing information, email address, case, DNS exchange policy, DNS load balance method, delete.

• Content rules - Owner name, content name, virtual IP address, TCP/UDP port number, IP protocol, DNS balance, load balance, load threshold, bypass transparent caches, failover, primary sorry server, secondary sorry server, URL, EQL, URQL, add, activate, suspend, delete.

• Services in content rules - Owner name, content rule, service, weight, assign, remove.

• Extension Qualifier Lists (EQLs) - EQL name, description, EQL extensions, add, delete, update.

• Uniform Resource Locator Qualifier Lists (URQLs) - Name, domain, description, add, activate, suspend, delete.

• Uniform Resource Qualifiers (URLs) - Name, domain, description, add, activate, suspend, delete.

• Named keepalives - Name, IP address, description, frequency, maximum failures, method, port, retry period, type, URI, FTP record name, script name, script arguments, add, activate, suspend, delete.

• Proximity - Application Peering Protocol-User Datagram Protocol (APP-UDP), APP, Proximity Database (PDB), Proximity Domain Name Server (PDNS).

• Domain Name Service - DNS record name, DNS record type, IP address, TTL value, DNS record return, keep-alive message type, IP address of local interface to receive, keep-alives, load threshold, DNS peering receive slots, DNS peering send slots, DNS peering interval, DNS server, name server buffers, responder task count, DNS server state.

• Color Recommendations - The minimum graphics required is SVGA (800x600 resolution). For best results, use XGA (1024x768 resolution).

• Browser Support - CSS Device Management requires Microsoft^® Internet Explorer version 5.0 or later, or Netscape^® Communicator version 4.5 or 4.6.

Note   The navigation tree will not display if you are using Netscape Communicator version 4.72, 4.73 or 4.74.

To enable CSS Device Management, enter:

(config)# no restrict web-mgmt
 

To disable CSS device management, enter:

(config)# restrict web-mgmt
 

To determine the state of the device management software on the CSS, enter:

# show running-config
 

!************************* Global ***************************
virtual authentication
no restrict web-mgmt

Note   If CSS Device Management is disabled, the command will not display in the running-config.

You can use ACLs to restrict device management access to specific IP addresses or subnets, or to restrict user access to device management forms. ACLs provide traffic-filtering capabilities by controlling whether packets are forwarded or blocked at the CSS interfaces. You can configure ACLs for routed network protocols, filtering the protocol packets as the packets pass through the CSS.

An ACL consists of clauses that you define. The CSS uses these clauses to determine how to handle each packet it processes. When the CSS examines each packet, it either forwards or blocks the packet based on whether or not the packet matches a clause in the ACL.

Caution ACLs function as a firewall security feature. When you enable ACLs, all traffic that is not configured in an ACL permit clause will be denied. It is extremely important that you first configure an ACL to permit traffic before you enable ACLs. If you do not permit any traffic, you will lose network connectivity. Note that the console port is not affected. It is recommended that you configure either a permit all or a deny all clause depending on your ACL configuration. For example, you could first configure a permit all clause and then configure deny clauses for only the traffic you wish to deny. Or, use the default deny all clause and configure permit clauses only for the traffic you wish to permit.

To access the CSS Device Management:

1. In your Web browser, enter the IP address of the CSS in the Location or Address field (depending on your browser) followed by a colon (:) and the management port number.

For example:

For example, to configure how you and other users access your CSS:

2. Click Access. The Access Configuration form appears in the workspace.

3. Select the appropriate settings from the drop-down lists, then click Update. The software updates the CSS access configuration.

4. Click Cancel to remove any configuration changes you make and return the default values to the configuration form.

5. To get Help on a configuration form and its fields, click Help at the bottom of the configuration form.

For example, CSS Device Management contains a Proximity Database wizard that allows you to configure a CSS 11150 (with 256 MB of memory) as a proximity database (PDB).

Note   Network Proximity requires the Enhanced feature set and the Network Proximity license keys. Refer to Configuring Network Proximity, in the section "Entering Your Proximity License Keys".

To use a configuration wizard, click the wizard name in the Administration tree. Follow the steps in the wizard forms as it guides you through the configuration process.

When establishing a device management session, you may experience a problem where the browser fails to display the initial device management screen. If the browser fails to connect to the CSS management port properly, ensure that: