|
|
This chapter tells you how to use the on-line Web Console, a graphical user interface (GUI), to set or change the system configuration and monitor system activity. The Web Console application communicates with the system by translating HTML pages into Cisco IOS commands. You can enter similar configuration parameters for your system using the command-line interface (CLI).
The Cisco 6400 ships with the Asynchronous Transfer Mode (ATM) address autoconfigured by Cisco Systems, allowing the switch to automatically configure attached end systems using the Interim Local Management Interface (ILMI) protocol and to establish itself as a node in a single-level Private Network-Network Interface (PNNI) routing domain.
The ILMI and PNNI protocols, when used with an IP address autoconfiguration mechanism such as Dynamic Host Configuration Protocol (DHCP) or Bootstrap Protocol (BOOTP), allow the Cisco 6400 to be entirely self-configured. Before using the Web Console to configure your Cisco 6400, you must assign an IP address or use DHCP to obtain an address for the system.
This chapter discusses the following topics:
Before you can use the Web Console to configure your Cisco 6400 you must install the Web Console pages. You can run the Web Console from the local PCMCIA disk0: (the default) or from a TFTP server. After the pages are installed, they can be updated at any time using the procedure described in the "Loading New Web Console Pages" section.
Automation installation of the Web Console requires a PCMCIA disk with a Web Console software image of Cisco IOS Release 12.0(5)DB or later. If your Web Console software is an earlier release, see the following procedures for manual installation of the Web Console.
To let the NSP install the Web Console application automatically, follow these steps starting in privileged EXEC mode:
Step 1 Insert the PCMCIA disk with the Web Console pages into the disk0: slot of the NSP.
Step 2 Use the dir disk0: command to make sure that the c6400s-html.tar.120-5.DB file (indicated with the arrow below) is on the disk.
Switch# dir disk0: Directory of disk0:/
3 -rw- 628224 Jan 01 2000 00:08:55 c6400s-html.tar.120-5.DB 376 -rw- 2134 Jan 05 2000 22:05:27 startup.config 109760512 bytes total (109130154 bytes free) Switch#
Step 3 Type reload. This will reboot the NSP.
Switch# reload
After rebooting, the NSP checks at disk0: for a Web Console image. If the Web Console image is present, the NSP automatically installs the Web Console application.
To install and run the Web Console application from the PCMCIA disk, follow these steps starting in privileged EXEC mode:
Step 1 Insert the PCMCIA disk with the Web Console pages into the disk0: slot of the NSP.
Step 2 Create a directory, nsp-html, for the Web Console files on disk0:
Switch# mkdir disk0:/nsp-html
Step 3 Install the Web Console pages from disk0: to the nsp-html directory. Enter the following:
Switch# archive tar /xtract disk0:c6400s-html.tar disk0:/nsp-html
To install and run the Web Console application from a TFTP server, follow these steps:
Step 1 Insert the PCMCIA disk with the Web Console pages into the disk0: slot of the NSP.
Step 2 Set the HTTP path by entering the following command. You must supply the TFTP server name and directory.
Switch# ip http path tftp://tftpservername/yourdir/nsp-html
Step 3 Copy the Web Console image from disk0: of the NSP to the TFTP server with the following command:
Switch# copy disk0:c6400s-html.tar tftp://tftpservername/yourdir
Step 4 In the directory with the Web Console image on the TFTP server, uncompress the image by typing tar -xvf c6400s-html.tar
After you have installed Web Console on the NSP, open a browser (Netscape Navigator 4.x or above or Microsoft Internet Explorer 4.x or above) on any other workstation, using the following settings:
Enter the IP address of the management Ethernet on the Cisco 6400 as the URL and press Enter to run the Web Console.
The Cisco 6400 Web Console is an embedded HTML web site residing on PCMCIA disk0: or on your TFTP server. You can assign a bookmark to the Web Console access page and use the other browser functions as you would with any web site. You can also use the live image of the switch on the Web Console Status page to monitor switch activity and confirm configuration changes without having to go into the wiring closet. Online help is available on all pages.
Web Console pages function much like other GUIs. When you display a Web Console page, it contains the current settings that have been defined for the switch. You change the system configuration by entering information into fields, adding and removing list items, or selecting check boxes.
Changes made by entering information into fields become part of the running (current) configuration when you click Apply, a button that appears on every page. If you make a mistake and want to retype an entry, click Reset to undo the information you entered. The exception to this procedure occurs when you are making changes to lists. Items added or removed from lists immediately become part of the running configuration, and you do not need to click Apply.
Table 3-1 lists the parameters that you can configure using Web Console.
| Feature | Default Setting | Web Console Page |
|---|---|---|
Management | ||
Switch IP address, subnet mask, domain, and default gateway | 0.0.0.0 | Management IP |
IP static route | None | Management IP |
DNS server identification | Enabled | Management IP |
NRP Configuration | ||
NRP configuration information | None | NRP |
Redundancy |
|
|
Active CPU and autosynchronization characteristics | Disabled | Redundancy |
Slot redundancy, primary/secondary configuration | Disabled | Redundancy |
Subslot redundancy, primary/secondary configuration | Disabled | Redundancy |
Subscriber |
|
|
Set up new subscribers, list current subscribers | Enabled | Subscriber |
Diagnostics |
|
|
System monitoring | Enabled | Status |
Security |
|
|
Switch name, password, domain, and ATM address | None | System |
System reload and core dump options | None | Advanced System Configuration |
SNMP contact information | None | SNMP Management |
Trap manager | 0.0.0.0 | SNMP Management |
Community strings | public/private | SNMP Management |
You can apply the changes you make using the Web Console to the current system configuration by clicking Apply on any of the Web Console pages. When you click Apply, the Update page is displayed. (See Figure 3-1.)
The Update page allows you to confirm the changes you just made to the system configuration, before actually applying them to the running configuration of your switch. This page also indicates whether or not any errors occurred when the information was transferred to the operating system. If you are sure that you want to apply the changes to the running configuration, click Update Page. If you want to discard your changes, click Close.
The startup configuration file contains the IP addresses, passwords, and any other parameters you entered when you first configured the system. The system maintains the configuration by reloading this file when it restarts. However, the startup configuration file might not have the configuration that is currently operating the system. Changes made through the Web Console or the command-line interface (CLI) take effect immediately but must be explicitly saved to be included in the startup configuration.
The configuration file that is loaded when the switch is restarted with the switch software in Flash memory. This file is not necessarily the same as the running configuration. If you want the running configuration to be the configuration used when the switch restarts, use the Save As button on each Web Console page to save the running configuration to the startup configuration file in memory.
To save the configuration to bootflash, the startup-config, the TFTP server, or one of the PCMCIA disks, follow these steps:
Step 1 Click the Save As button in the left frame on any of the Web Console pages.
The Save As window is displayed. (See Figure 3-2.)
Step 2 Click the button that corresponds to where you want the configuration you just entered to be stored.
Step 3 Enter a filename if you are saving to a file.
Step 4 Click the Save button.
The switch must have an IP address before you can access the Web Console. Follow the prompts when you install the switch to assign an IP address and other IP information. See the Cisco 6400 UAC Hardware Installation and Maintenance Guide for more information.
Follow these steps to access the Web Console:
Step 1 Install the Web Console. Refer to the "Installing the Web Console" section.
Step 2 Enter the IP address of the NSP management Ethernet in the URL field.
Step 3 Click Enter. The Cisco Systems Access page is displayed. (See Figure 3-3.)
Step 4 Click Web Console to display the Cisco 6400 System Configuration page. (See Figure 3-4.)
From the Access page, you can also Telnet to the switch, show interfaces, show diagnostics, monitor the switch, and display technical support information.
You can also access Cisco Connection Online (CCO), the Cisco Systems customer web site, from the Web Console home page. From CCO, you can download the latest software and display the latest Cisco 6400 UAC documentation.
The Basic System Configuration page acts as the system home page. (See Figure 3-4.) To display this page, click Web Console on the Cisco Systems Access page. To display the main page in Web Console, click System on the action bar.
After you have started the Web Console and displayed the Cisco 6400 home page (Figure 3-4), you can use the action bar at the top of each page to move between pages. Figure 3-5 lists the functions that are available for each action bar selection.
This information is usually entered once and not changed. Click Apply after entering information in the fields, Revert to return values to the previous settings, or Save As to save the configuration. Each of the fields is described in Table 3-2.
| Field | Description |
|---|---|
Name of system | Enter a name for the Cisco 6400 system. |
Mgmt ATM Address | Pre-assigned ATM address is entered automatically. |
Contact Name | Enter a name. |
Enable password | Enter the enable password for the system. |
Confirm password | Reenter the enable password for the system. |
Mgmt Ethernet address | Displays the Ethernet address for the CPU. (Display only, use the Mgmt IP page to change the IP address.) |
Domain name | Displays the name of the domain of the system. (Display only, use the Mgmt IP page to change the domain name.) |
For more information about setting your basic configuration, see "Configuring the Node Switch Processor."
Access the advanced configuration parameters by clicking the Advanced button on the System Configuration page. The Advanced parameters are displayed below the basic parameters.
(See Figure 3-6.)
Enter the System Reload Options and Core Dump parameters described in Table 3-3 and then click Apply.
| Field | Description |
|---|---|
System Reload Options |
|
System Image File | Enter the path and name of the Cisco IOS image file to be loaded when the system reboots. |
Configuration File | Enter the path and the name of the configuration file that the image file reads to configure the system. |
Core Dump |
|
User Name of FTP Server | Enter a valid user name for the FTP server where you want the core dump file sent. |
Password of FTP Server | Enter a valid password for the FTP server where you want the core dump file sent. |
Hostname/Address of FTP Server | Enter the host name and address for the FTP server where you want the core dump file sent. |
Core Dump Filename | Enter the name you want used for the core dump file. |
Use the Reboot System button on this page to reboot the system at any time.
This section describes the files used by the system when it reloads its software. Some of these files reside in memory, either bootflash or disk. To determine the names of the files to use, enter the dir command at the CLI. Here is an example of the display that results:
switch# dir bootflash:
Directory of bootflash: 2 -rwx 843947 Mar 01 1993 00:02:18 6400-h-mz-112.8-SA 4 drwx 3776 Mar 01 1993 01:23:24 nsp-html 66 -rwx 130 Jan 01 1970 00:01:19 env_vars 68 -rwx 1296 Mar 01 1993 06:55:51 config.text 1728000 bytes total (456704 bytes free)
To view the system reload settings, use the show bootvar command as follows:
switch# show bootvar
BOOT variable = disk0:c6400-wp-mz,12; CONFIG_FILE variable does not exist BOOTLDR variable does not exist Configuration register is 0x2101
Use the Redundancy page to set up redundant CPUs, slots, and subslots. This page also allows you to set the primary/secondary relationship between redundant pairs. To display this page, click Redundancy on the action bar.
Figure 3-7 shows the slots and subslots listed on the redundancy page.
For more information about configuring redundancy, see "Configuring System Features."
To set redundancy for a pair of CPUs, slots, or subslots, do the following:
Step 1 Click the Associate check box for the pair.
Step 2 Choose the primary slot or subslot by clicking the appropriate button.
Step 3 Click Apply.
For the CPU, you can also set the configuration synchronization option as described in the "Synchronize Redundant NSPs or NRPs" section.
To manage the IP address used for the management Ethernet port, static IP routes, and DNS servers, use the Mgmt IP page. (See Figure 3-8.) To display this page, click Mgmt IP on the action bar.
| Caution Changing the switch IP address on this page will end your Web Console session. If this occurs, you can restart Web Console by entering the new IP address in the browser URL field. |
The IP address of the switch is entered or changed through the Setup program or the command-line interface. If you change it on this page, the new value takes effect when you click Apply and could cause you to lose contact with the switch. When entering data in the IP Configuration fields, you can always select Revert to return the page to its previous state. You might need to contact a network administrator to obtain the IP address information.
Follow these steps to enter the IP parameters for the management Ethernet:
Step 1 Enter the subnet mask (Mgmt Ethernet Mask) for the switch.
Step 2 Enter the broadcast address for the switch.
Step 3 Enter the domain name of the management Ethernet.
Step 4 Enter the IP address of the default gateway, or router. This field is filled automatically if a discovery protocol finds a router connected to a switch port.
Step 5 Click Apply to save the current information to your running configuration.
Step 6 Click Save As to save the current information to your configuration file, Flash memory, disk, or TFTP server.
Static routes for the management Ethernet are manually entered into the Static Address table. They are not aged (dropped) from the table when not in use, and they are not lost when the system resets. To set IP static routes used on the Ethernet management network, follow these steps:
Step 1 Enter the destination network Ethernet address for the new static route in the Network Address field.
Step 2 Enter the subnet mask for the static route in the Prefix Mask field.
Step 3 Enter the IP address for the next hop router in the Gateway (Next Hop) field.
Step 4 Click <<Add<<.
To remove static routes, follow these steps:
Step 1 Select the static route you want to remove from the list of current IP routes.
You must remove the last static route entry unless you have a default gateway specified. Otherwise, you will no longer be able to access the Web Console on this system.
Step 2 Click Remove.
A domain name server (DNS) converts domain names into their corresponding IP addresses. To define DNS servers that are used on the Ethernet management network, follow these steps:
Step 1 Enter the Ethernet address of a new DNS in the New Server field.
Step 2 Click <<Add<<.
To remove a DNS, follow these steps:
Step 1 Select the DNS you want to remove from the list of current servers.
Step 2 Click Remove.
Use the SNMP page (see Figure 3-9) to perform the following tasks:
For more information about configuring SNMP management options, see "Configuring the Node Switch Processor."
System Option information is used by network management applications to identify the switch on a topology map. To begin entering the information, proceed as follows:
Step 1 Enter a name to be used for the system.
Step 2 Enter the location of the system.
Step 3 Enter the name of a person or organization associated with the system.
Step 4 Click Apply to save the current information to your running configuration.
Step 5 Click Save As, to save the current information to your configuration file, Flash memory, disk, or TFTP server.
Read Only | Enables requests accompanied by the string to display MIB-object information |
Read and Write | Enables requests accompanied by the string to display MIB-object information and to set MIB objects |
To supply a community string, proceed as follows:
Step 1 Enter a character string in the String field.
Step 2 Click Read Only or Read and Write.
Step 3 Click <<Add<<.
To remove community strings, select a string from the Current Strings list and click Remove.
A trap manager is a management station that receives and processes traps.
Follow these steps to add a trap manager:
Step 1 Enter the IP address or name of the station in the IP Address field.
Step 2 Enter a character string in the Community field. This string can be any length.
Step 3 Select the class of traps that the trap manager is to receive. Select a check box to enable one or all of the following:
Trap on config---Generate traps on all changes to the switch configuration.
Trap on SNMP---Generate the supported SNMP traps.
Trap on TTY---Generate the serial-port-related TTY traps.
Step 4 Click <<Add<<.
To remove trap managers, follow these steps:
Step 1 Select a manager from the Current Managers list and click Remove.
Step 2 Click Apply to save the current information to your running configuration.
Step 3 Click Save As, to save the current information to your configuration file, Flash memory, disk, or TFTP server.
The NRP page allows you to display information about any of the node route processors (NRPs) installed in the Cisco 6400 chassis. To display the NRP page (Figure 3-10), click NRP in the action bar.
Use the Subscriber page (see Figure 3-11) to set and display the cross connections for each of your current system subscribers. Subscribers are defined according to the ingress and egress ports, the VPI, and VCI. To display the Subscriber page, click Subscriber in the action bar.
For more information about configuring virtual circuits for your subscribers, see the section "Configuring Internal Cross-Connections" section.
To add new subscribers and set up the virtual circuits, follow these steps:
Step 1 Select the ATM interface into which the subscriber packets arrive at the switch.
Step 2 Enter the incoming virtual path identifier (VPI).
Step 3 Enter the incoming virtual channel identifier (VCI).
Step 4 Enter the outgoing (egress) ATM interface. This is the other side of the cross connection.
Step 5 Enter the outgoing VPI and VCI.
Step 6 Click <<Add<<.
The new subscriber information is displayed in the Current Subscriber list.
To remove subscribers, follow these steps:
Step 1 Select a subscriber from the list of subscribers.
Step 2 Click Remove.
Step 3 Click Apply to save the current subscribers to your running configuration.
Step 4 Click Save As, to save the current subscribers to your configuration file, Flash memory, disk, or TFTP server.
This page has a live image (see Figure 3-12) of the system that displays much of the same information as the LEDs on the front of the system. You can use this image in the following ways:
Cisco 6400 systems are shipped with the Web Console pages described in this chapter. However, from time to time, you might want to load updated Web Console pages into local memory (either Flash memory or Flash disk) on your system.
To load new Web Console pages onto your system, perform the following tasks from the privileged EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| copy tftp://tftpservername/../c6400s-html.tar disk0:c6400s-html.tar | Copy the new tar file with the Web Console pages to disk0. | ||
| rename disk0:nsp-html disk0:nsp-html.old | Rename the existing Web Console directory to save the current pages before extracting the new pages. | ||
| List the contents of the tar archive accessible at the URL shown. | |||
| archive tar /xtract source destination | Unpack the Web Console Web pages and store them in the specified location. |
After you have verified that the new Web Console pages are working properly, you can delete the old Web Console directory (nsp-html.old). Commonly, this procedure is performed at the same time that a new IOS image is downloaded. The IOS image is typically stored in Flash, and the HTML pages are usually stored on Flash disk (disk0:); however, the operating system allows you to specify any valid file system location as the destination.
The following example shows how to extract files on the TFTP server named boothost and install them on disk0: on the NSP:
Switch# archive tar /xtract tftp://tftpservername/directory/c6400s-html.tar disk0:
Posted: Mon Nov 15 12:45:44 PST 1999
Copyright 1989-1999©Cisco Systems Inc.
