Table Of Contents
WebNS Device Management User Interface Overview
Browser and Platform Support
WebNS Device Management User Interface
Supported Features in the Device Management User Interface
CSS Configuration Form Features
CSS Monitor Form Features
CSS Summary Form Features
WebNS Device Management User Interface Overview
The WebNS Device Management user interface is an HTML-based Web application that you use to configure and manage a Cisco 11500 series content services switch (CSS). The WebNS Device Management user interface is part of the WebNS system software included with each CSS. The Device Management user interface allows you to configure and monitor a CSS. You can manage a single CSS or, using multiple browser windows, you can manage multiple CSSs.
You access the WebNS Device Management user interface from a Web browser (Microsoft Internet Explorer is recommended). The Web browser typically connects to the Device Management user interface through the CSS Ethernet Management port.
This chapter includes the following topics:
•
Browser and Platform Support
•
WebNS Device Management User Interface
•
Supported Features in the Device Management User Interface
Browser and Platform Support
The WebNS Device Management user interface has the following requirements:
•
Color Recommendations—The minimum display resolution required is SVGA (800x600 resolution). For best results, use XGA (1024x768 resolution).
•
Browser Support—The WebNS Device Management user interface requires Microsoft Internet Explorer version 5.0 or later, or Netscape Navigator 4.08, Communicator 4.51 or 4.71.
Note
If the entire navigation tree does not display in Netscape Navigator or Communicator, press Shift, then click Reload to refresh your browser. The navigation tree will not display if you are using Netscape Communicator version 4.72, 4.73 or 4.74.
WebNS Device Management User Interface
The Device Management user interface is divided into four areas or frames:
•
Navigation Tree—The Navigation tree (located in the lower left frame of the browser window) lists Configuration, Monitor, and Summary options arranged by category. Many of these options are the same as those found in the Command Line Interface (CLI). Each icon in the Navigation Tree corresponds to a Configuration form, a Monitor form, or a Summary form. Click the form name in the Navigation tree to display the associated form in the Workspace frame.
•
Workspace Frame—The Workspace is a large frame that displays the Configuration form, Monitor form, or Summary form corresponding to the navigation tree option that you select. A form may contain a single task or may involve a configuration form that includes multiple steps designed to simplify the process of setting up basic services on your CSS.
•
Cisco Logo—Clicking the Cisco Systems logo in the upper left corner opens a secondary browser window that links to Cisco.com, the Cisco Systems corporate Web site.
•
Banner—Clicking the Content Services Switch banner opens a secondary browser window linking to the Cisco.com Web site.
Figure 1-1 provides a typical example of a WebNS Device Management user interface form.
Figure 1-1 WebNS Device Management User Interface Example
Supported Features in the Device Management User Interface
The Device Management user interface offers many of the same CSS capabilities that are available through the Command Line Interface (CLI). This section summarizes the supported CSS features, divided by:
•
CSS Configuration Form Features
•
CSS Monitor Form Features
•
CSS Summary Form Features
CSS Configuration Form Features
The Device Management user interface offers many of the same CSS configuration capabilities that are available through the Command Line Interface (CLI). All Configuration forms are available under the Configuration Navigation Tree. The list below summaries the Configuration forms and associated parameters:
•
Interface—Interface name, VLAN number, VLAN type (bridge or trunk).
•
Circuit—VLAN number, IP address, IP prefix length.
•
MIB-II 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.
•
SNTP—State, server IP address, version, poll-interval, SNTP server state, seconds since last update.
•
SNMP traps—Trap hosts, generic traps, enterprise traps (such as login failure, redundancy, service, DoS LAND attack, and so on).
•
Logging—Logging host and logging disk filename, subsystems, and via email.
•
RADIUS—RADIUS client, primary Remote Authentication Dial-In User Server (RADIUS) server, and secondary RADIUS server.
•
Portmapping—Global portmapping, no-flow DNS portmapping.
•
Service—Name, Adaptive Session Redundancy, IP address, type, protocol, port, domain, weight, maximum connections, string, cache bypass, bypass host tag, transparent host tag, keepalive type.
•
Owner—Owner name, address, billing information, e-mail address, case, DNS exchange policy, DNS load-balancing method.
•
Content rule—Owner name, Adaptive Session Redundancy, 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, persistence, application type, sticky connection parameters, URL, EQL, URQL.
•
Services in content rule—Owner name-content rule, service name, weight.
•
Source group—Name, Adaptive Session Redundancy, IP address, port-mapping parameters.
•
Services in source group—Source group, service name, service type.
•
Extension Qualifier Lists (EQLs)—EQL name, description.
•
EQL Extension—EQL extension, extension description.
•
Uniform Resource Locator Qualifier Lists (URQLs)—Name, domain, description.
•
Uniform Resource Locators (URLs)—URQL, number, URL, description.
•
Named keepalive—Name, IP address, description, frequency, maximum failures, method, port, retry period, type, URI, FTP record name, script name, script arguments, script output.
•
Port Mapping—Global port mapping, no-flow DNS port mapping.
•
Redundancy—Box-to-box redundancy, VIP/interface redundancy, Adaptive Session Redundancy (ASR), Inter-Switch Communications (ISC).
•
Proximity—APP, APP session, APP-UDP, Proximity Database (PDB), Proximity Domain Name Server (PDNS).
•
Domain Name System—DNS server, DNS forwarder, DNS peer, domain acceleration, domain cache, DNS record, DNS Sticky, acceleration candidate, Content Routing Agent (CRA), CRA domain, CRA alias.
•
SSL Accelerator—SSS proxy list, SSL proxy list cipher suite, SSL backend server proxy list, SSL backend server proxy list cipher suite, assign proxy list to service.
•
Save Configuration—Copy running configuration to start configuration, copy running configuration to startup configuration and archive startup configuration.
CSS Monitor Form Features
There are a number of forms in the Device Management user interface that allow you to view statistical information about the CSS. All Monitor forms are available under the Monitor Navigation tree. Monitor forms include: Owner, Content Rule, Content Service, Proximity APP-UDP, Proximity RTT Probe, DNS Server, DNS Forwarder, DNS Proximity, DNS Content Routing Agent, Flow Statistics, and Denial of Service.
CSS Summary Form Features
There are a number of forms in the Device Management user interface that allow you to view configuration and summary statistical information about the CSS. All Summary forms are available under the Summary Navigation tree. Summary forms include: Boot Configuration, Interfaces, Trunked Interfaces, Logging Subsystems, Trap Hosts, RADIUS, Show Service, Show Owner, Show Content, Show Keepalive, Content Service Usage, Services, Content Services, Source Groups, Source Group Services, Owners, Content Rules (Summary, Main, Advanced Balance, and String), URQLs, URLs, EQLs, EQL Extensions, Named Keepalives, Service Keepalives, Box-to-Box Redundancy (Summary, Protocol, Circuits, Physical Links), Proximity APP Sessions, DNS Records, DNS Record Keepalives, DNS Domain Cache, DNS Acceleration Candidates, Content Routing Agent Domains, Denial of Service Attacks, Chassis, Session Processors, and System Resources.