cc/td/doc/product/dsl_prod/c600s/c676
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuration Procedures

Configuration Procedures

3.1 Purpose

This chapter provides information about configuring your Cisco 676.


Note It is recommended that only one command line application be used to configure the Cisco 676 at any given time. For example, Telnet and the serial management interface should not be used simultaneously.

Also please note that all
configuration procedures are performed in the enable (root) mode.

3.2 Checklist


Table 3-1: Checklist for Configuration

Configuration Procedures Page Number

Logon to the CBOS

3-2

Select a Connection Mode

3-4

Bridging Mode Procedures or Routing Mode Procedures

3-4 or 3-6

Configure the Ethernet Port (eth0)

3-8

Configure the WAN Ports and ATM Virtual Connections

3-10

Create Routing Tables

3-14

Enable IP Filtering

3-15

Configure Applications

3-16

3-16

3-17

3-21

3-25

3-27

3-19

3-18

3-27

Configure Timeout Values

3-27

Update the CBOS Prompt

3-28

Setting Passwords

3-28

Save Configuration Changes

3-29

Evaluate System Activity and Performance

3-29

Retrieve Cisco 676 Statistics

3-30

3.3 Logon to the CBOS

After connecting all the Cisco 676 cables, turning on your Cisco 676, and starting your terminal access program (as shown in the "Setting Up the Cisco 676 Hardware Environment" section), press the Enter key until the CBOS login screen appears. When you see the welcome screen, you can logon to CBOS.

Hello!
CBOS v2.0.1
 
User Access Verification
Password:


Note If you have not set any passwords for the 676, without entering a password press the Enter key when the system prompts you for a password to enter CBOS .

After you logon to CBOS and before proceed any further with your configuration process, check the version of the CBOS to verify the version number and date reflect the most recent firmware update: cbos# show version.

If the CBOS is out of date, get the latest version from your service provider or from Cisco. See the TFTP command in the "TFTP Server" section, for more information on how to update the Cisco 676 firmware.

3.3.1 Operation Modes

The CBOS implements two operational modes: exec and enable. CBOS defaults to exec mode when you log in. The exec mode grants program execution (read-only) privileges to a user. To read or write changes to NVRAM, you must work in enable mode. Follow the steps below to invoke the enable mode:

    1. Type enable at the exec mode command line:
    cbos>
    cbos> enable

    2. Enter a password when CBOS prompts you:
    Password:


Note If you have not set any passwords for the 676, press the Enter key when the system prompts you for a password to enter CBOS. If you have not preset a password, you can still logon to the CBOSe.

You are now in enable mode. The system prompt appears as shown:

cbos#

3.4 Select a Connection Mode

The CBOS supports two kinds of connection modes: bridging and routing. Routing mode has two options: Configurationless Provisioning (default) and Manual Provisioning.


Note Routing and bridging cannot be used simultaneously.

3.5 Bridging Mode Procedures

When the Cisco 676 operates in bridge mode, it behaves like a wire connecting a local PC directly to a service provider's network. Bridge data is encapsulated using the RFC1483 protocol to enable data transport. Because bridges operates at a MAC layer only, applications requiring IP communication, such as Telnet, TFTP, RADIUS, Syslog, Ping, and the web interface, are not available unless a management VC is configured.

Cisco currently supports a learning bridge mode. The VPI/VCI configuration of the Cisco 676 is unaffected by the operational mode (bridging versus routing) of the device.

Cisco also provides a method of configuring and managing the bridged 676 by enabling a management mode. With rfc1483 management enabled, you can manage the router using telnet. The following commands are accessable through the managed bridge:

The following procedure shows how to set up the 676 for bridging management.


Note You must be in the enable mode to do the procedure below. You must perform the procedure in the sequence as shown.

    1. To enable RFC1483 bridging, enter:
    set bridging rfc1483 enabled

    2. To enable management of the bridge, enter:

The IP address that is assigned to the router, must be an IP address that is on the same network segment (subnet) that is being bridged. Assigning IP addresses in this fashion enables access via telnet, to the router for management functions.

For more information on using the set bridging command, see the Cisco Broadband Operating System User's Guide.

The rules that govern the bridge command are:

If you choose bridging as your connection mode, see also the following sections:

3.6 Routing Mode Procedures

Routing mode supports two types of configuration procedures: configurationless and manual provisioning.

3.6.1 Configurationless Provisioning

Three 676 applications compose the configurationless provisioning feature: DHCP client, DHCP server, and NAT. With these applications enabled, you can use the 676 without following the procedures described in this chapter such as the "Bridging Mode Procedures" section or the "Configure the WAN Ports and ATM Virtual Connections" section. See the following section to enable configurationless provisioning..

Enabling Configurationless Provisioning

For each of the applications the show < application > command reports if the feature is enabled . Follow the steps below to enable the configurationless provisioning feature for the 676. You must be in the enable mode to do this procedure.

    1. Enable the DHCP client:
    set dhcp client enabled

    2. To check whether this feature is enabled, enter the following command:
    show dhcp client

    3. Enable the DHCP server:
    set dhcp server enabled

    4. To check whether this feature is enabled, enter the following command:
    show dhcp server

    5. Enable NAT:
    set nat enabled

    6. To check whether this feature is enabled, enter the following command:
    show nat

    7. Write the changes to NVRAM:
    write

    8. Reboot the 676:
    reboot

When the 676 reboots, configurationless provisioning is enabled.

Disabling Configurationless Provisioning

Follow the steps below to disable the configurationless provisioning feature for the 676. You must be in the enable mode to do this procedure.

    1. Disable the DHCP client:
    set dhcp client disabled

    2. Disable the DHCP server:
    set dhcp server disabled

    3. Disable NAT:
    set nat disabled

    4. Write the changes to NVRAM:
    write

    5. Reboot the 676:
    reboot


Note After you disable the configurationless provisioning feature, you must manually configure the 676.

Changing Configurationless Provisioning

Use the commands below to change the components of configurationless provisioning:

For a complete description of each of these commands, see the Cisco Broadband Operating System User's Manual.

3.6.2 Manual Provisioning

If you disable Configurationless Provisioning, see the following steps for manual provisioning: from the "Configure the Ethernet Port (eth0)" section through the "Evaluate System Activity and Performance" section

3.7 Configure the Ethernet Port (eth0)

To configure the Ethernet port, you must assign an IP address and netmask to the port. Follow the steps below to configure your IP address and your netmask. When setting the IP address of a particular interface, the netmask is set automatically unless it is explicitly specified. Substitute your own IP address for the ones shown in steps two through four.

You must be in the enabled mode to do this procedure.

    1. Logon to the CBOS (cbos# ) using the serial connection.


Note When changing the 676 IP configuration, use the serial managment connection to ensure you maintain your session connection to CBOS.

    2. To set the IP address (and your netmask), follow the example of the following command:
    set interface eth0 address 192.168.34.9

    3. To set the destination IP address for the WAN port, enter the following:
    set interface wan0-0 dest 192.168.34.10

    4. To save your changes, enter:
    write

    5. To allow the system to come up with these new settings, reboot the Cisco 676 by entering:
    reboot

    6. Log back on to the CBOS to continue.

For more detailed information on the set interface command, see the Cisco Broadband Operating System User's Guide.

3.8 Configure the WAN Ports and ATM Virtual Connections

The Cisco 676 has two types of WAN ports: physical (wan0) and logical (wan0-x). The physical WAN port connects the Cisco 676 to the Wide Area Network. The logical WAN port or ports allow you to create virtual WAN connections for plural destinations. When configuring the hysical WAN port, you can change the default line rate settings. To configure logical WAN ports, you must provision ATM virtual connections and optionally set ScalaRate for each logical connection. The instructions for each are shown below.

3.8.1 Set the ADSL Line Rates (wan0)

The Cisco 676 uses its RADSL functionality to automatically train up to the ideal line speed. By default, the 676 is provisioned with rates of 9.9 Mbps downstream and .93 Mbps upstream. This enables the maximum operative rate as determined by the Central Office ADSL equipment.


Note Optimal line rates are dependent upon the Central office equipment base and optimal line conditions.

Follow the procedure below to change line rate settings.

    1. To show the current line rate enter:
    cbos# show rate

    2. To set the ADSL downstream rate to 7168Kbps, enter:
    cbos# set interface wan0 rate down 7168

    3. To set the upstream rate to 680Kbps, enter:
    cbos# set interface wan0 rate up 680

    4. To save your changes, enter:
    cbos# write

    5. To exit the CBOS, enter:
    cbos# quit

On the Cisco 676, the WAN0 port is always ready to send and receive network traffic.You may need to define an ATM Virtual Connection (VC) when communicating across an ATM network. There are two types of ATM connections: (1) virtual paths, identified by virtual path identifiers (VPI); and (2) virtual circuit, identified by the combination of a VPI and a virtual circuit identifier (VCI). Because the Cisco 676 connects to the Cisco 6100, the subscriber side VPI/VCI settings are not seen by the ATM network. All subscriber side VCs use VPI 1 by default.

Cisco 676 comes pre-configured with one VC already established. Each VC is expressed as WAN0-x, where x is a number between one and four.

To set the maximum number of VCs, enter
cbos# set interface wan0 maxvcs <n>


The valid ranges for the
VPI and VCI addresses is shown in the following table.


Table 3-2: VPI/VCI Address Ranges
VPI <count> VPI Range VCI Range

1

0

0..255

2

0..1

0..127

4

0..3

0..63

8

0..7

0..31

Changing VPI Settings

    1. To set the VPI number to 2, enter:
    set interface wan0-1 vpi 2


Note If you try to enter the command set interface wan0-1 on a connection that is already open, the system prompts you to close that connection before you change the VPI setting. Close the connection by entering: set interface wan0-1 close.

    2. To begin using this connection with the new settings, enter:
    set interface wan0-1 open

    3. Repeat steps 1 and 2 for every VPI assignment you want to make.

    4. To save the new WAN port configuration, enter:
    write

    5. To exit the CBOS, enter:
    quit

Changing VCI Settings

    1. To set the VCI number to 4, enter:
    set interface wan0-0 vci 4


Note If you try to enter the command set interface wan0-0 on a connection that is already open, the system prompts you to close that connection before you change the VCI setting. To do this enter the command set interface wan0-0 close.

Also, if there is an Ethernet packet in transmission to the wano-o port, the wan0-0 connection can reopen. Enter the following command to ensure the wan0-0 port remains closed during configuration: set interface wan0-0 disable.

    2. To begin using this connection with the new settings, enter:
    set interface wan0-0 open

    3. Repeat steps 1 and 2 for every VCI assignment you want to make.

    4. To save the new WAN port configuration, enter:
    write

    5. To exit the CBOS, enter:
    quit

For more information on configuring VPI/VCI address mapping, see the Cisco Broadband Operating System User's Guide.

3.8.2 Set ScalaRate for wan0-x

ScalaRate is a technology developed by Cisco that allows dynamic allocation of bandwidth within an ATM-based ADSL connection. This bandwidth allocation is specified and controlled by the end-point devices without affecting the provisioning or status of the underlying ATM transport VC. Bandwidth within the ADSL connection is allocated on a VC basis and provides flexibility in rate structures and deployment models for service providers and network administrators.

The key features of ScalaRate are as follows:


Note Before you change the ScalaRate value, close the wan0-x port.

To set the wan0-x to ScalaRate use the following steps.

    1. To set an upstream ScalaRate for a particular VC, enter:
    cbos# set interface wan0-0 rate 512

    2. To set an upstream ScalaRate to the maximum allowable rate, enter:
    cbos# set interface wan0-0 rate auto

    3. To save your changes, enter:
    cbos# write

    4. To exit the CBOS, enter:
    cbos# quit

3.9 Create Routing Tables

In order to pass data through a network and onto the Internet or wide area network, you may need to add the IP address(es) of gateway(s) to the routing table. Follow the instructions below to build a routing table manually by adding or deleting entries in the table.


Note If your Cisco 676 was provisioned to run in bridging or configurationless mode, you must disable both before attempting to establish routing.

    1. To add a route to IP address 192.9.9.1 without specifying a specific gateway, mask or metric, enter:
    set route add ip 192.9.9.1

    2. To add a route and specify a netmask, gateway, or metric, enter:
    set route add ip 192.10.10.0 mask 255.255.255.0
    gw 208.203.245.228 metric 1

    3. To set a default route, enter:
    set route default 208.203.245.228

    4. To set a destination address for each VC, enter:
    set interface wan0-0 dest 208.203.245.228
    mask 255.255.255.0

    5. To save your changes, enter:
    write

    6. To exit the CBOS, enter:
    quit

For more information on using the set route command, see the Cisco Broadband Operating System User's Guide.

Enable Routing Information Protocol (RIP)

To enable RIP and RIP2 in the CBOS, enter:

set rip enabled 

To disable RIP, enter:

set rip disabled 

For more information on using the set rip commands, see the Cisco Broadband Operating System User's Guide.

3.10 Enable IP Filtering

The Cisco 676 supports up to ten filters for TCP and UDP packets passing through the 676's interfaces. Enabled filters are applied to packets in sequential order according to filter number.

The example below shows how to use filtering:

    1. To block all packets going through the Ethernet interface, enter:
    set filter 0 on deny eth0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0

For more information on using the set filter command, see the Cisco Broadband Operating System User's Guide.

3.11 Configure Applications

The Cisco 676 supports several applications for management and control of the system. These applications include:

3.11.1 DHCP Client

The DHCP Client requests an IP address from the DHCP server. See the instructions below to enable the DHCP client:

    1. Enable the DHCP client:
    set dhcp client enabled

    2. To check whether this feature is enabled, enter the following command:
    show dhcp client

    3. Write the changes to NVRAM:
    write

    4. Reboot the 676:
    reboot

For more information on using DHCP clients, see the set dhcp client commands.

3.11.2 DHCP Server

The DHCP Server application automatically assigns IP addresses to DHCP clients. Follow the steps below to enable the Configurationless Provisioning feature for the 676.

    1. Enable the DHCP server:

set dhcp server enabled
 

    2. To check whether this feature is enabled, enter the following command:

show dhcp server
 

    3. Write the changes to NVRAM:

write
 

    4. Reboot the 676:

reboot

Note The DHCP Server defaults with one IP address configured.

For more information on using DHCP servers, see the set dhcp server series of commands in Cisco's Broadband Operating System User's Manual.

3.11.3 NAT

The NAT application converts IP addresses on a private network (designated as "inside" or "LAN") to global IP addresses that can forward packets to another registered network (designated as "outside" or "WAN"). See the instructions below to enable NAT:

    1. Enable NAT:

set nat enabled
 

    2. To check whether this feature is enabled, enter the following command:

show nat
 

    3. Write the changes to NVRAM:

write
 

    4. Reboot the 676:

reboot
 

For more information on using NAT, see the set nat series of commands in Cisco's Broadband Operating System User's Manual.

3.11.4 RADIUS Client

Remote Authentication Dial-In User Service (RADIUS), authenticates users for access to a network. The RADIUS server uses an authentication scheme, such as PAP, to authenticate incoming messages from RADIUS clients. When a password is present, it is hidden using a method based on the RSA Message Digest Algorithm MD5 [1].

The Cisco 676 has been successfully tested for compatibility with the following RADIUS server providers:

The Cisco 676 Implementation

The Cisco 676 supports a RADIUS client. However, for most environments, the Cisco 676 Radius client is not used. The RADIUS client exists on the service provider's remote access server (for instance, the FireRunner 100 or the Cisco 7200). The Cisco 676 communicates with the RADIUS client via PAP packets.

Configuring RADIUS on the Cisco 676

The following examples assume that the Cisco 676 is connected to a network equipped with a RADIUS server.

set radius enabled
RADIUS is enabled
set ppp wan0-0 radius enabled
set ppp wan0-0 login cisco
set ppp wan0-0 password is_great

Note A RADIUS test command,
set radius test activates the RADIUS debug option. This allows you to test that RADIUS works with current client settings by sending a test message to the RADIUS server.

For more information on RADIUS commands, see the Cisco Broadband Operating System User's Guide.

3.11.5 SYSLOG Client

SYSLOG logs significant system information to a remote SYSLOG server for processing without requiring large amounts of local storage or local processing.

Implementing SYSLOG

Using the CBOS, the Cisco 676 allows you to specify a remote server for logging system messages. Cisco supports the following levels of severity:

The messages are similar to the standard Berkley Software Distribution (BSD)-style severity levels for SYSLOG; however, they do not include None and Mark. To configure your SYSLOG daemon to receive Cisco SYSLOG messages, modify the /etc/syslog.conf configuration file (remember to use tabs, not spaces). Many systems, such as Linux and FreeBSD, have SYSLOG setup by default.


Note A SYSLOG test command,
set syslog test activates the SYSLOG debug option. This allows you to test that SYSLOG works with current client settings by sending a test message to the SYSLOG server.

The following /etc/syslog.conf configuration file entry enables all messages for Info severity levels and above:

*.info	/var/log/messages

To enable only alarm messages and above, enter the following in /etc/syslog.conf:

*.alarm	/var/log/messages
 

Be sure your UNIX syslogd daemon accepts remote reception (network messages). Some processes may need to be killed and restarted with a -r option. Using the man syslog command to view the online UNIX manuals for information about the SYSLOG daemon.

Using SYSLOG From a UNIX Machine

To use SYSLOG, simply enter the following at your CBOS prompt:

set syslog remote <IPaddress of remote server>

Attention Windows NT and Windows 95/98 Users

Windows do not have a SYSLOG client. If you want to utilize SYSLOG on a Windows 95, 98, or NT system, you must install a SYSLOG client from a third-party vendor onto your system. One way to locate a SYSLOG client is to use an Internet search engine to locate a vendor who sells a SYSLOG client. Some SYSLOG clients are provided as share or freeware on the Internet.

Cisco has proven compatibility with the following third-party products:

For more information on SYSLOG commands, see the Cisco Broadband Operating System User's Guide.

3.11.6 Telnet

Telnet provides a command line interface and is used as a means of providing remote login connections between machines on many networks, including the Internet.

Caution
Before closing a Telnet connection, always enter exit or quit at the cbos# prompt.

Using Telnet to Connect to the Cisco 676

Use the telnet daemon to connect to CBOS and configure and operate the Cisco 676.

Connecting from a Windows NT 4.0 or a Windows 95/98 Machine

    1. Click on the Start button.

    2. Select the Run... option.

    3. When the Run box appears, enter telnet in the space provided.

    4. Click the OK button. The Connect menu appears.

    5. Select the Remote System... option from the Connect menu. The following window appears:


Figure 11: Remote System List Box


    6. Enter the IP address of the Cisco 676 in the Host Name box and press Connect. The system then initiates a session with the Cisco 676. Press the Enter key a couple of times to establish a connection.

    7. Provide the exec user password information. Once the system authenticates your password, you have access to the CBOS.


Note If no password has been entered into the system, logon with no password. Press the Enter key at the password prompt. See the Cisco Broadband Operating System User's Guide for more information about how to set and change passwords.
Notice to Windows Users

Windows' Telnet client does not support NVT (Network Virtual Terminal) or any extra form of option negotiation. However, if you are going to use the Windows Telnet client, please read the following steps to set your terminal settings.

    1. When the Telnet window appears, access the Preferences menu in Telnet by selecting Preferences from the Terminal drop down menu.


Figure 12: Telnet Preferences


    2. Set the terminal settings on the Terminal Preferences menu to the following values:


Figure 13: Terminal Preferences


Notice to Linux Users

If you try to run Linux without installing the Term/Termcap database, the message BAD ADDRESS displays during a connection attempt. To install the Term/Termcap database, check the original Linux installation disks.

Connecting from a UNIX Machine

    1. Enter the following at your prompt:

telnet <IP address of Cisco 676>
User Access Verification
Password:

    2. Provide the exec user password. Once the system authenticates the password, you have access to the CBOS.

How to Keep Telnet from Timing Out During Your Session

Telnet sessions time out after a period of inactivity. Enter the following commands keep the Telnet client from timing out.

set telnet timeout off
write
 

For more information on Telnet commands, see the Cisco Broadband Operating System User's Guide.

3.11.7 TFTP Server

The Trivial File Transfer Protocol (TFTP) allows you to transfer files to and from a Cisco 676. The Cisco 676 runs a tftp daemon, which allows users from remote machines who have TFTP client software to remotely transfer files to and from the Cisco 676. The TFTP client can be enabled and disabled from the CBOS or the Web Management Interface.

Caution
For security reasons, Cisco recommends that you disable the TFTP application, except when uploading or downloading a file.
Software Updates

Use TFTP to transfer a new software image from Cisco to your Cisco 676, where the file name format is: c676.x.x.x or c676.x.x.x.ima. The x.x.x represents the image version number.

Archives

Use TFTP to backup a copy of your configuration file before changing it so you can easily recover the old file when necessary. The naming conventions for the configuration file are:

Using TFTP from a UNIX Machine

For information on the UNIX TFTP client, access the online manual by entering:

man tftp 
 

At your command line prompt and the manual page for TFTP appears.

Using TFTP from a Windows NT Machine

Follow these steps:

Follow these steps:

    1. Enable the tftp server on the 676. As an enabled user type the following commmand:

set tftp enabled
 

    2. Start a DOS session and enter:
    C:>tftp -i <IP address of Cisco 676> put <image_filename>

    Where necessary, implement the following options:

    3. Be sure that you reboot the device to activate the new image. When you log back into the Cisco 676 after the reboot, Use the following command to verify the version of the firmware that is active: show version

Attention Windows 95/98 Users

Windows 95/98 does not have a TFTP client. If you want to utilize TFTP on a Windows 95/98 system, you must install a TFTP client from a third-party vendor on your system. One way to locate a TFTP client is to use an Internet search engine to locate a vendor who sells a TFTP client. Some TFTP clients are provided as share or freeware on the Internet. Cisco will provide a TFTP client upon request. TFTP client requests should be directed to Technical Assistance Center.

For more information on TFTP commands, see the Cisco Broadband Operating System User's Guide.

3.11.8 Web Interface

The Cisco 676 supports a web interface, which allows you to perform tasks such as configuring interfaces, displaying statistics, and much more. For a complete description of the web interface, see the Cisco Broadband Operating System User's Guide.

3.12 Configure Timeout Values

The Cisco 676 supports two timeout values: session and idle. The session timeout is based on the total uptime of the session. The setting of the idle timeout facilitates the release of the RADSL physical layer so that the Central Office resource may be released, based on inactivity. The expiration of either timeout will end the ADSL session. However, since authentication is invisible, only the training delay is perceived by the user (approximately 23 - 46 seconds) when the connection is reestablished.

Use the set timeout command to configure the idle or session timeout values in seconds.

    1. To set the session timeout rate to 300 seconds then enter show timeout to verify. Enter:
    set timeout session 300

    2. To set the idle timeout rate to 300 seconds then enter show timeout to verify. Enter:
    set timeout idle 300

    3. To save your changes, enter:
    write

    4. To exit the CBOS, enter:
    quit

3.13 Update the CBOS Prompt

The default CBOS prompt is cbos#. The command prompt is limited to 9 characters. You can change this prompt to a unique subscriber identifier as shown in the following example.

    1. Logon to the CBOS using either the serial or Telnet interfaces. See "Telnet" section for more information on how to use Telnet to logon to the CBOS.

    2. To change the default prompt to 4412883 as the subscriber identifier, enter:
    set prompt 4412883
    The following prompt now appears:
    4412883#

    3. To save your changes, enter:
    write

    4. To exit the CBOS, enter:
    quit

3.14 Setting Passwords

After you have configured your Cisco 676, select and configure new passwords for both the root (enable) and user (exec). Examples of good and bad passwords are:

Use the set password command to change both the enable and exec user passwords as in the following:

    1. To change the enable user password enter:
    set password enable <new password>

    2. To change the exec user password enter:
    set password exec <new password>

    3. To save your changes, enter:
    write

    4. To exit the CBOS, enter:
    quit

3.15 Save Configuration Changes

Use the write command to save any changes you have made during provisioning to the NVRAM configuration file.

write
Caution
If you do not use the write command after changes, all the changes you made during your current session will be lost when you reboot the machine.

3.16 Evaluate System Activity and Performance

The following table describes the Cisco 676 LEDs and their status. The LEDs are located on the front of the unit.


Table 3-3:
LED Label Full Name Description

WAN-LNK

WAN Link

When this light is ON, it indicates that a link has been established on the WAN port. When the light is solid, the 676 is connected and trained. The WAN-LNK light blinks steadily during ADSL line training activities.

WAN-ACT

WAN Activity

When this light blinks ON, indicates that the WAN port is transmitting or receiving data.

LAN-LNK

(Ethernet) LAN Link

When this light is ON, it indicates that a link has been established on the Ethernet port.

LAN-ACT

(Ethernet) LAN Activity

When this light blinks ON, it indicates activity on the Ethernet port.

ALARM

Alarm Light

When the light is Red this indicates a problem or alarm that needs to be resolved. A brief Red light during power up is a normal behavior of the power on self test.

POWER

Power Light

When this light is Green, the Cisco 676 is ON and the unit is receiving power.

Cisco 676 Status LEDs

3.17 Retrieve Cisco 676 Statistics

Use the stats command to display statistics on Cisco 676 activities. The statistics provided by the stats command varies on the application or interface selected. To retrieve Cisco 676 statistics, follow these steps:

    1. To see a list of applications and interfaces that provide status, enter:
    stats ?

    2. To display specific statistics, for example, for the wan0 interface enter:
    stats wan0

    3. To exit the CBOS, enter:
    quit

3.18 Interpret Cisco 676 Statistics

Use the stats command to retrieve certain key statistics regarding ADSL performance of your Cisco 676. These statistics are:


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Jun 9 08:35:11 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.