Table of Contents

Introduction
Configuration Checklist
Log On to the Cisco Broadband Operating System

Determine the CBOS Version
Operation Modes

Configure Management Virtual Connections

Changing VPI Settings
Changing VCI Settings

Using Telnet

Connecting from a Windows NT or Windows 95 Machine
Connecting from a UNIX Machine
How to Keep Telnet from Timing Out During Your Session

Using a Trivial File Transfer Protocol Server

Using TFTP from a UNIX Machine
Using TFTP from a Windows NT Machine

Upgrade Software through Serial Download
Configure Line Coding

Configure for DMT2
Configure for G.DMT

Update the CBOS Prompt
Set Passwords
Save Configuration Changes
Evaluate System Activity and Performance
Retrieve Statistics
Interpret Statistics

Configuration Procedures for the Cisco 627

Introduction

This chapter provides information about configuring your Cisco 627. Your unit is preconfigured for full operation. However, you might need to configure the Cisco 627 for management virtual connections (VCs).

Configuration Checklist

Table 3-1 identifies the configuration procedures you might need.

Log On to the Cisco Broadband Operating System

After connecting all cables to the Cisco 627 and powering it on, start the terminal emulation program and press the Enter key until the Cisco Broadband Operating System (CBOS) welcome screen appears. When you see the welcome screen, you can log on to CBOS.

Determine the CBOS Version

After you log on to CBOS, you can use the show version command to determine the CBOS version of the Cisco 627:

Operation Modes

CBOS also has two modes of operation: exec and enable. The CBOS defaults to exec mode when you log on. The exec mode grants read-only (command execution) privileges to a user.

To write changes to NVRAM, you must work in enable mode. To invoke enable mode:

---

Step 1   At the command line, enter:

cbos> enable

Step 2   Enter the enable password when CBOS prompts you:

Password:

---

---

Note   If you have not set any passwords, press the Enter key when the system prompts you for a password.

---

Configure Management Virtual Connections

Your system comes preconfigured for full and immediate network operation. However, you might need to manage your Cisco 627 directly over the network. To do this, you must establish and set management virtual connections (VCs).

Note   You must be in the enable mode to perform these procedures.

Each interface is expressed as atmx, where x is either 0 or 1. The atm0 interface is reserved for ATM25. The atm1 interface is used for the ADSL remote interface.

The valid range for VPI is 0 to 255. 0 to 65535 is the valid range for VCI addresses.

Note   The Cisco 627 is configured with atm0 using VPI/VCI 0/34 by default. The atm0 interface is used for management. Cisco recommends that you do not change VPI/VCI values for atm0.

Changing VPI Settings

Step 2   To begin using this connection with the new settings, enter:

Step 3   To verify your setting:

A display similar to the following will appear on your screen:

Step 4   To save the new WAN port configuration, enter:

Step 5   To exit CBOS, enter:

Note   To close an ATM management connection, enter: set interface atmx disable. To set the ATM25 management VPI, repeat the previous steps substituting atm0 for atm1.

Changing VCI Settings

To verify your setting:

A display similar to the following will appear on your screen:

Step 2   To begin using this connection with the new settings, enter:

Step 3   To save the new WAN port configuration, enter:

Step 4   To exit CBOS, enter:

Note   To close an ATM management connection, enter: set interface atmx disable. To set the ADSL ATM VCI, repeat the previous steps substituting atm1 for atm0.

Using Telnet

Telnet provides a command-line interface for remote login connections between machines on many networks, including the Internet. To establish a Telnet connection to the CPE, Telnet must be enabled in CBOS.

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

Connecting from a Windows NT or Windows 95 Machine

Step 2   Select the Run... option.

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

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

Step 5   Select the Remote System... option from the Connect menu. The Remote System List Box appears. (See Figure 3-1.)

Step 6   Enter the atm0 IP address of your modem in the Host Name box and click Connect. The system then initiates a connection session. When connection is initiated, information similar to the following displays:

User Access Verification Password:

---

Note   Press the Enter key several times to establish a connection.

---

Step 7   Provide the logon and password information. After the system authenticates your password, you have access to the CBOS.

---

---

Note   You can log on to the CPE using no password by pressing the Enter key at the password prompt. Refer to the "Set Passwords" section on page 3-19 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, complete the following steps to set your terminal settings.

---

Step 1   When the Telnet window appears, go to the Terminal drop-down menu, and click Preferences. (See

Step 2   Set the terminal settings on the Terminal Preferences menu to the values shown in Figure 3-3.

Connecting from a UNIX Machine

The following procedure describes how to log on to your modem from a UNIX system:

After you have connected, information similar to the following appears on your display:

Step 2   Provide the login and password information. After the system authenticates your password, you have access to CBOS.

How to Keep Telnet from Timing Out During Your Session

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

The set telnet timeout off setting is not saved in NVRAM after a reboot. You must explicitly set it for every session.

Using a Trivial File Transfer Protocol Server

The Trivial File Transfer Protocol (TFTP) enables you to transfer files to and from your modem. Your system runs a tftp daemon that enables remote users who have TFTP client software, to transfer files to and from the system. The TFTP client is 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 the TFTP utility to transfer a new software image from Cisco to your system, where the filename equals nsrouter.c627.x.ima, where x is the release number.

Versions of CBOS 2.3 or higher use the filename format c627.x.bin, where x is the release number.

Archives

Use the TFTP utility to back up a copy of your configuration file before changing it,

so you can easily recover the old file if necessary. The naming conventions for the configuration file are:

• When using the put option of the tftp command, you must name the file nscfg.cfg.

• When using the get option of the tftp command, name the file any name that a standard text editor can view and edit.

Using TFTP from a UNIX Machine

For information on the UNIX TFTP client, access the online manual on your UNIX system. At the command-line prompt, enter:

The manual page for TFTP appears. The TFTP UNIX man page contains all the information you need to establish and invoke a remote TFTP session.

Using TFTP from a Windows NT Machine

Before attempting to use TFTP, make sure of the following:

• On the Cisco 627, TFTP is enabled and the IP address of the ATMx port is the same IP address used in Step 2 of the following procedure.

• The ATMx port is enabled, and the VCI/VPI is set correctly on it.

• The remote host computer must be configured for RFC 1483 Logical Link Control (LLC)/Subnetwork Access Protocol (SNAP) encapsulation if the PC is directly connected to the CPE through the atm0 interface, or verify the IP connectivity between the PC and the CPE.

To use TFTP:

Step 2   Enter one of the following commands:

where IP address is the IP address of the ATMx port.

Where necessary, implement the following options:

-i - Sets the transfer mode to binary mode.

put - Uploads a file to that IP address.

---

Note   The CPE might take up to 2 minutes to upgrade the firmware. Wait until the management console reappears before rebooting the CPE.

---

Step 3   Be sure that you reboot the device to activate the new image. When you log back on to your system after the reboot, use the following command to verify the version of the firmware that is active:

Notice to Windows 95 Users

Windows 95 does not have a TFTP client. If you want to utilize TFTP on a Windows 95 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. By request, Cisco will provide a TFTP client.

Upgrade Software through Serial Download

You can upgrade software on your CPE using the serial interface:

Step 2   To turn debug monitor on, enter:

Step 3   To save your changes, enter:

Step 4   To reboot the device, enter:

After the modem reboots, press Enter twice. The prompt should change to =>.

Step 5   To erase sector 0, enter:

Repeat this step for sectors 1 through 5.

Step 6   To start serial download, enter:

Step 7   Use a terminal emulation application, such as Hyperterminal, to start an Xmodem download of a new Cisco 67x image.

Step 8   When the download is complete, the following message appears:

Record the number of bytes transferred.

Step 9   To program the area of memory to Flash, enter:

where xxxxxxxx is the value recorded in Step 6.

Step 10   To turn debug monitor off, enter:

Step 11   To reboot, enter:

Configure Line Coding

The Cisco 627 allows you to choose transmission protocols to match your network configuration by changing the CPE's configuration file and operating system. You will use the TFTP to transfer files to and from the CPE. This section describes procedures to configure the Cisco 627 for G.Lite and G.DMT protocols.

Note   Changes to your CPE must be coordinated with the central office equipment.

Configure for DMT2

Step 2   Enable TFTP by entering:

Step 3   Set the remote address for the TFTP host computer by entering:

This command tells the CPE to accept TFTP transfers from a specific IP address. An example remote IP address would be 192.168.35.4. This address is an example only; do not use it to configure the router.

---

Note   If you do not have the CPE address, consult your network administrator. For more information about TFTP, see " Using a Trivial File Transfer Protocol Server" section on page 3-10.

---

Step 4   To start the file transfer from a PC, start a DOS session and enter the following command:

To start the file transfer from a UNIX machine, enter the following commands:

Where necessary, implement the following values:

Substitute the filename for the software image update. See the latest Release Notes for the Cisco Broadband Operating System available on CCO for the appropriate filenames to use.

Caution   Do not turn off the power to the router until after the file transfer is completed.

Step 5   Be sure to reboot the CPE to activate the new image. When you log back in to the CPE after the reboot, use the show version command to verify the version of the firmware that is active. Note the DMT firmware version.

Sample Output of Configuration Session for DMT2

Configure for G.DMT

Before the CPE can be configured for G.DMT, the .full image must be loaded. See the latest Release Notes for the Cisco Broadband Operating Sytsem for the appropriate filenames to use. The central office hardware must be correctly configured to accept a G.DMT service user.

Step 2   Be sure to retrain the CPE to activate the new line code. When the CPE is retrained, use the show interface atm1 command to verify the G.DMT standard is active. Note that the standard configuration for the .full image is DMT2.

---

Note   Changes made to the running configuration must be written to NVRAM for changes to be seen on reboot.

---

Sample Output of Configuration Session for G.DMT

Update the CBOS Prompt

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

Step 2   To change the default prompt to 4412883 as the subscriber identifier, enter:

Step 3   To save your changes, enter:

Step 4   To exit the CBOS, enter:

Set Passwords

After you have configured your system, you should pick new passwords for both the enable and exec modes. Keep in mind that the enable mode provides all the functionality of a system administrator for the CPE. Examples of good and bad passwords are:

• Good Password—77ta99y (Do not use the sample password.)

• Bad Passwords—Passwords such as your name; or your street address, or home telephone number are too predictable.

Save Configuration Changes

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

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 Cisco 627.

Evaluate System Activity and Performance

Table 3-2 describes the LEDs and their status.

Retrieve Statistics

The stats command shows information about the number of packets transmitted and received and activity information about general applications.

To retrieve statistics:

Step 2   To display specific statistics, enter:

Step 3   To exit the CBOS, enter:

Interpret Statistics

Use the stats atm0 and show interface atm1 commands to retrieve key statistics regarding ADSL performance. These statistics are:

• CRC Errors—Number of CRC errors. CRC errors might occur when the ATM traffic rate is faster than the ADSL rate, causing ATM cells to be dropped. This corrupts the AAL5 logical packets. CRC errors might also be an indication of excessive noise on the DSL line.

• Errored Seconds—Number of Superframe CRC errors. If this field is incremented, the user data path is encountering uncorrected errors.

• Rx'ed Blocks—Number of blocks received by the unit. A block is 250 milliseconds. This statistic is reset whenever the modem trains.

• Tx'ed Blocks—Number of blocks transmitted by the unit. A block is 250 milliseconds. This statistic is reset whenever the modem trains.

• Corrected/Uncorrected Blocks—The modem can correct a block containing errors. If the block correction fails, the block is counted as an uncorrected block and discarded.

• Attenuation—Difference in decibels (dB) between the power level received at the near end versus the power level transmitted from the far end. The attenuation range is 0 to 63 dB in 1 db increments. Attenuation is calculated every 10 seconds.

• Signal-to-Noise (SNR) Margin—Amount of increased received signal noise (in decibels) relative to the signal noise power level the unit is designed to tolerate without disconnecting from the network. The SNR Margin range is -64.0 to +63 dB in 1 dB increments. SNR Margin is calculated every 10 seconds. The previous value is moved to the Previous SNR Margin field.

• Previous SNR Margin—Last SNR Margin measurement, which occurs approximately every 10 seconds.

• Operation, Administration, Maintenance (OAM) Loopback Cells—The Cisco 627 supports the Operation, Administration, and Maintenance (OAM) F5 loopback cell to verify end-to-end ATM network connectivity. The OAM-F5 loopback cell is generated by a network-side system. The cell is injected into a specific virtual circuit along with the normal user traffic flow. The cell is carried unmodified by each intermediate ATM switching node until it arrives at the circuit's other endpoint such as the Cisco 627. The receiving endpoint modifies the cell payload to indicate that the cell has been looped back and transmits this new cell back into the ATM circuit. It is relayed by each intermediate node until it arrives at the original transmitting endpoint. The receipt of this cell indicates a valid end-to-end connection between the two endpoints over the intervening ATM network.

Posted: Fri May 4 14:36:45 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.