Managing the Cisco 6400 SCM Element Manager Windows

The Cisco 6400 SCM Element Manager adds custom windows to the standard Cisco Element Manager Framework (EMF) system to improve management of the Cisco 6400 Universal Access Concentrator (UAC). For example, the Cisco 6400 Chassis Management window has four tabbed sections:

Faults
Status
Configuration
Inventory

Each tab displays specific information about the current state of the system or allows you to change various settings on a Cisco 6400 UAC without using Cisco IOS commands. Multiple Element Managers can be installed on a single Cisco EMF server, therefore allowing multidevice management from a single system.

This chapter describes the Element Manager windows that appear in the Cisco 6400 Service Connection Manager (SCM). The Element Manager windows provide:

Fault, Configuration, Accounting, Performance, and Security (FCAPS) information with the capability to be viewed or configured
Capacity Planning, Inventory Management, Network Planning, Software Download, and Service Enabling
Capacity monitoring, to monitor the VPC/VCC allocation and maximize memory allocation for a selected Cisco 6400 Universal Access Concentrator (UAC)
Mass operations (for example, Download to 1000 elements)
Full-time distributed network monitoring
Multiuser support

Each Element Management window consists of one or more tabs that display information or that allows you to configure the Cisco 6400 UAC hardware. A number of the Element Manager windows have a similar layout in terms of management functions. For example, the first tab across a number of the Element Manager windows displays fault information that can be used for troubleshooting problems that arise.

Launching Element Manager Win dows

Table 5-1 displays the Element Manager windows that can be launched from each node or object type. For example, to manage the Cisco 6400 chassis, choose a relevant Manager, Site, Chassis, or NSP object, and right-click Cisco 6400 UAC > Manage > Chassis option.

Note Cisco 6400 SCM also supports the NRP2 module. Unless otherwise noted, the NRP and NRP2 operate similarly. However, the NSP provides the following functions for the NRP2: image and file storage, system logging, console and Telnet access, and SNMPv3Proxy Forwarder. The NRP2 has no local image or file storage. The NSP stores the NRP2 images, system configuration files, ROM state information, and crash information on the PCMCIA disk on the NSP. The PCMCIA disk must be located in the NSP disk slot 0.

Table 5-1: Element Manager Window Access

	Objects (that can be selected) to Open the Window
Cisco 6400 Element Manager Window/Task	Site	Shelf	Chassis	NSP	NRP	NRP ATM Port	Node Line Card (NLC)	Line Card ATM Port	Menu Options to Select to Open Window
Cisco 6400 Chassis Management	Yes	Yes	Yes	No	No	No	No	No	Cisco 6400 UAC, Chassis, Manage, Chassis
Capacity Monitoring	Yes	Yes	Yes	No	No	No	No	No	Cisco 6400 UAC, Chassis, Manage, PVC Usage
SNMP Management	Yes	No	Yes	No	No	No	No	No	Cisco 6400 UAC, Chassis, Manage, SNMP Management
Chassis Configuration	Yes	No	Yes	No	No	No	No	No	Cisco 6400 UAC, Chassis, Manage, Configuration
Module Configuration	Yes	No	Yes	Yes	Yes	No	Yes	No	Cisco 6400 UAC, Module, Manage, Configuration
Interface Configuration	Yes	No	Yes	Yes	Yes	Yes	Yes	Yes	Cisco 6400 UAC, Port, Manage, Configuration
Cisco 6400 NSP Management	Yes	Yes	Yes	Yes	No	No	No	No	Cisco 6400 UAC, Module, Manage, NSP
Cisco 6400 NRP Management	Yes	Yes	Yes	Yes	Yes	No	No	No	Cisco 6400 UAC, Module, Manage, NRP
SSG Configuration	Yes	Yes	Yes	Yes	Yes	No	No	No	Cisco 6400 UAC, Module, Manage, SSG Configuration
Cisco 6400 NRP Capacity Statistics	Yes	Yes	Yes	Yes	Yes	No	No	No	Cisco 6400 UAC, Module, Manage, NRP Capacity Statistics
Cisco 6400 NRP ATM Port Management	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	Cisco 6400 UAC, Port, Manage, NRP ATM Port
	Objects (that can be selected) to Open the Window
Cisco 6400 Element Manager Window/Task	Site	Shelf	Chassis	NSP	NRP	NRP ATM Port	Node Line Card (NLC)	Line Card ATM Port	Menu Options to Select to Open Window
Cisco 6400 Line Card Management	Yes	Yes	Yes	Yes	No	No	Yes	No	Cisco 6400 UAC, Module, Manage, NLC
Cisco 6400 Line Card ATM Port Management	Yes	Yes	Yes	Yes	No	No	Yes	Yes	Cisco 6400 UAC, Port, Manage, NLC ATM Port
OAM Loopback	No	No	Yes	No	No	No	No	Yes	Cisco 6400 UAC, Port, Manage, Cisco OAMLoopback
SONET APS	Yes	Yes	Yes	Yes	No	No	No	Yes	Cisco 6400 UAC, Port, Manage, SONET APS
Module Performance	Yes	No	Yes	Yes	Yes	No	No	Yes	Cisco 6400 UAC, Module, Manage, Performance
Interface Performance	Yes	No	Yes	Yes	Yes	Yes	Yes	Yes	Cisco 6400 UAC, Port, Manage, Performance
Interface Status	Yes	No	Yes	Yes	Yes	Yes	Yes	Yes	Cisco 6400 UAC, Port, Manage, Status
Command Log	Yes	No	Yes	Yes	Yes	No	No	No	Cisco 6400 UAC, Module, View, Command Log
SysLog Message	Yes	No	Yes	Yes	NRP Yes NPR2 throughNSP	No	No	No	Cisco 6400 UAC, Module, View, System Log
Management Information	Yes	Yes	Yes	No	No	No	No	No	Cisco 6400 UAC, Chassis or Module, Admin, Management Information
IOS Image Download	Yes	No	Yes	Yes	NRP Yes NPR2 throughNSP	No	No	No	Cisco 6400 UAC, Module, Admin, IOS Image Download
Configuration Backup/Restore	Yes	No	Yes	Yes	NRP Yes NPR2 throughNSP	No	No	No	Cisco 6400 UAC, Module, Admin, Configuration Backup/Restore
Service Uplink Bandwidth Utilization	Launch from an appropriate Service Uplink object.								Cisco 6400 UAC, Subscriber Bandwidth Utilization
	Objects (that can be selected) to Open the Window
Cisco 6400 Element Manager Window/Task	Site	Shelf	Chassis	NSP	NRP	NRP ATM Port	Node Line Card (NLC)	Line Card ATM Port	Menu Options to Select to Open Window
Service, Subscriber Connection Bandwidth Utilization	Launch from an appropriate Connection object.								Cisco 6400 UAC, Bandwidth Utilization
Telnet Session	No	No	Yes	Yes	NRP Yes NRP2 through NSP	Yes	Yes	Yes	Cisco 6400 UAC, Tools, Initiate Telnet Service
Launch WebConsole	No	No	Yes	Yes	NRP Yes NRP2 through NSP	Yes	Yes	Yes	Cisco 6400 UAC, Tools, Launch Web Console

Using the Element Manager Wind ows

This section identifies the:

Information that appears on the Element Manager windows (for example, Fault, Status, Statistics, Inventory, Backup/Restore, and Download information)
Various configuration and commissioning or decommissioning tasks that you perform (on the Cisco 6400 UAC) using the Cisco 6400 SCM software

This section is divided into a number of topics (for example, Fault Information, Status Information, and Configuration and Commissioning, Decommissioning). Each section provides a table that details the relevant chassis components, the Element Manager window you launch to view the appropriate window, and a pointer to the relevant section in this user guide for further details.

Commissioning, Decommissioning and Configuration Tasks

The Cisco 6400 SCM software allows you to configure and commission or decommission the components within a selected Cisco 6400 chassis. Table 5-2 details each of the Cisco 6400 UAC components that you can configure, the Element Manager window that you should open, and details of the tasks that you can perform. Table 5-1 details how to open each of the Element Manager windows.

Each module (that is, NSP, NRP, NRP2, or NLC) has a module management window where additional module configuration can be carried out either before or after commissioning the selected module. For example, you might want to configure parameters in the Cisco 6400 Line Card Management window before commissioning the NLC module using the Module Configuration window.

Each port interface (that is, NSP, NRP, NRP2, or NLC) has a port management window where you can perform additional port interface configuration either before or after commissioning the selected port interface. For example, you might want to configure parameters in the Cisco 6400 Line Card ATM Port Management window before commissioning the NLC interface port using the Interface Configuration window.

Table 5-2: Configuration and Commissioning, Decommissioning Tasks

Cisco 6400 UAC Component	Element Manager Window	Tasks	For Further Information
Chassis	Cisco 6400 Chassis Management (Configuration tab)	Chassis, clock, alarm, temperature threshold, and power supply configuration.	See the "Cisco 6400 Chassis Management Window" section.
	Chassis Configuration (Configuration tab)	Validation parameters, clock and power supply configuration. Click Commission or Decommission to initiate subchassis discovery. Click Start to begin global performance logging.	See the "Chassis Configuration Window" section.
	Chassis Configuration (Additional Descriptions tab)	Enter additional descriptions for identification purposes (for example, CLLI codes could be entered).	See the "Chassis Configuration Window" section.
	Management Information	Configure system configuration and IOS/command line security information.	See the "Management Information Window" section.
NSP	Cisco 6400 NSP Management (Configuration tab)	System configuration, CLI password.	See the "Cisco 6400 NSP Management Window" section.
NRP and NRP2	Cisco 6400 NRP Management (Configuration tab)	System configuration, CLI password.	See the "Cisco 6400 NRP Management Window" section.
NSP, NRP, and NRP2, or NLC	Module Configuration (Configuration tab)	Enter additional descriptions for the selected NSP, NRP, or NLC module for identification purposes (for example, CLLI codes could be entered). Commission or Decommission the selected NSP, NRP, or NLC module.	See the "Module Configuration Window" section.

Cisco 6400 UAC Component	Element Manager Window	Tasks	For Further Information
SSG	Cisco 6400 SSG Configuration (SSG Configuration tab)	SSG, Layer 3 parameters, and local radius parameters. Configure or deconfigure the selected NRP-SSG parameters.	See the "Interface Configuration Window" section.
	Cisco 6400 SSG Configuration (PPPoA Configuration tab)	PPPoA virtual template and PPPoA IP address pool. Configure or deconfigure the PPPoA parameters.
	Cisco 6400 SSG Configuration (PPPoA Configuration tab)	PPPoE virtual template and PPPoE IP address pool. Configure or deconfigure the PPPoE parameters.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (Configuration tab)	ATM port configuration and ILMI configuration	See the "Cisco 6400 NRP ATM Port Management Window" section.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (More Configuration tab)	Information element transfer.
NLC	Cisco 6400 Line Card Management (Line Card tab)	Configure administration status.	See the "Cisco 6400 Line Card Management Window" section.
NLC ATM Port	Cisco 6400 Line Card ATM Port Management (Configuration tab)	ATM port configuration and ILMI configuration.	See the "Cisco 6400 Line Card ATM Port Management Window" section.
	Cisco 6400 Line Card ATM Port Management (More Configuration tab)	Information element transfer, general physical layer configuration, and DS1/E1/DS3/E3 physical layer configuration.
	Cisco Operation, Administration, and Maintenance Loopback (OAM Configuration tab)	Configure OAM loopback test parameters.	See the "Cisco Operation, Administration, and Maintenance Loopback Window" section.
	Cisco Operation, Administration, and Maintenance Loopback (OAM Status tab)	View the results of an OAM loopback test.

Cisco 6400 UAC Component	Element Manager Window	Tasks	For Further Information
NLC ATM Port (SONET APS)	SONET APS (Configuration tab)	Mode, BER threshold, and Switch command.	See the "SONET APS Management Window" section.
NSP, NRP, and NLC Interface Ports	Interface Configuration (Configuration tab)	Alias, administration status, link up/down trap enable, and supplementary information. Commission or decommission the selected NSP, NRP, or NLC port interface.	See the "Interface Configuration Window" section.

Configuration Backup/Restore

The Cisco 6400 SCM software monitors and displays NSP and NRP system log messages. Table 5-3 details the information displayed on the Configuration Backup/Restore window. Table 5-1 details how to open the Configuration Backup/Restore window.

Table 5-3: Configuration Backup/Restore

Cisco 6400 UAC Component	Element Manager Window	Information Displayed	For Further Information
Chassis, NSP, and NRP	Backup/Restore (Backup/Restore tab)	Configure a backup server. Initiate a backup or restore. Schedule a time for automatic backup/restore.	See the "Configuration Backup/Restore Window" section.

Note NRP2 configuration backup and restore functions are only done from the NSP.

Fault Management

The Cisco 6400 SCM software monitors the Cisco 6400 UAC and specific components connected into the chassis for faults. The fault information obtained from the hardware displays across a number of Element Manager windows.

Table 5-4 details each of the Cisco 6400 UAC components that are monitored, the Element Manager window that you open to view the fault information, and details of the fault information that displays. See Table 5-1 for details of how to open the appropriate Element Manager windows.

Table 5-4: Fault Information

Cisco 6400 UAC Component	Element Manager Window	Information Displayed	For Further Information
Chassis	Cisco 6400 Chassis Management (Faults tab)	The alarm information table displays Alarm Index, Alarm Source, Alarm Severity, Alarm Type, and Alarm Cut Off Status information.	See the "Cisco 6400 Chassis Management Window" section.
NSP	Cisco 6400 NSP Management (Faults tab)	Last restart reason and last authentication failure address.	See the "Cisco 6400 NSP Management Window" section.
NRP and NRP2	Cisco 6400 NRP Management (Faults tab)	Last restart reason and last authentication failure address.	See the "Cisco 6400 NRP Management Window" section.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (Faults tab)	Transmitted message errors, detected message errors, and SSCOP errored PDUs.	See the "Cisco 6400 NRP ATM Port Management Window" section.
Line Card ATM Port Management	Cisco 6400 Line Card ATM Port Management (Faults tab)	Errors (transmitted message errors, detected message errors, and PDU errors received through SSCOP), Sonet frame errors, and DS1/E1/E3 errors.	See the "Cisco 6400 Line Card ATM Port Management Window" section.

The faults displayed in the Cisco 6400 Chassis Management window (Faults tab) also appear as alarms in the Event Browser application.

Capacity Statistics

The Cisco 6400 SCM software monitors capacity statistics for NRP modules. The capacity statistics information that you obtain displays on the Cisco 6400 NRP Capacity Statistics window. Table 5-5 details each of the Cisco 6400 UAC components that are monitored, the Element Manager window that you open to view the capacity information, and details of the fault information that displays. See Table 5-1 for details of how to open the appropriate Element Manager windows.

Table 5-5: Capacity Statistics Information

Cisco 6400 UAC Component	Element Manager Window	Information Displayed	For Further Information
NRP and NRP2	Cisco 6400 NRP Capacity Statistics (NRP Capacity tab)	Subscriber connections, service instance uplinks, multidomain service connections, and over-subscription management.	See the "Cisco 6400 NRP Capacity Statistics Window" section.

Note The capacity statistics for NRP modules are maintained internally by the Cisco 6400 SCM software; they are not derived directly from totals on the Cisco 6400 UAC. When services are provisioned or removed through Cisco IOS, then the Cisco 6400 SCM's information is incorrect.

Status Information

The Cisco 6400 SCM software monitors and displays status information about the Cisco 6400 UAC and specific components connected into the chassis. The information displays across a number of Element Manager windows. Table 5-6 details each of the Cisco 6400 UAC components that are monitored, the Element Manager window that you open to view the status information, and details of the status information displayed. Table 5-1 details how to open the appropriate Element Manager windows.

Table 5-6: Status Information

Cisco 6400 UAC Component	Element Manager Window	Status Information Displayed	For Further Information
Chassis	Cisco 6400 Chassis Management (Status tab)	Chassis, Power Supply 1, Power Supply 2, Temperature Threshold Configuration, and Facility Alarm status information.	See the "Cisco 6400 Chassis Management Window" section.
NSP	Cisco 6400 NSP Management (Status tab)	NSP status, System Configuration File, Host Configuration File, and Network Configuration File.	See the "Cisco 6400 NSP Management Window" section for further details.
NRP and NRP2	Cisco 6400 NRP Management (Status tab)	NRP status, System Configuration File, Host Configuration File, and Network Configuration File.	See the "Cisco 6400 NRP Management Window" section.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (Status tab)	ATM Port Status.	See the "Cisco 6400 NRP ATM Port Management Window" section.
Line Card	Cisco 6400 Line Card Management (Line Card tab)	Operational status.	See the "Cisco 6400 Line Card Management Window" section.
Line Card ATM Port Management	Cisco 6400 Line Card ATM Port Management (Status tab)	ATM port status and physical layer status.	See the "Cisco 6400 Line Card ATM Port Management Window" section.
Interface Status	Interface Status (Status tab)	View interface details, last change details, and transmission details for a selected interface.	See the "Interface Performance Window" section.

Inventory Information

The Cisco 6400 SCM software monitors the Cisco 6400 UAC and specific components connected into the chassis for inventory information. The inventory information obtained from the hardware displays across a number of Element Manager windows. Table 5-7 details the Cisco 6400 UAC components that are monitored, the Element Manager windows that you open to view the inventory information, and details the inventory information displayed. Table 5-1 details how to open each of the Cisco 6400 Chassis Management windows.

Table 5-7: Inventory Information

Cisco 6400 UAC Component	Element Manager Window	Inventory Information Displayed	For Further Information
Chassis	Cisco 6400 Chassis Management (Inventory tab)	Chassis and power supply.	See the "Cisco 6400 Chassis Management Window" section.
NSP	Cisco 6400 NSP Management (Inventory tab)	System inventory.	See the "Cisco 6400 NSP Management Window" section.
NRP and NRP2	Cisco 6400 NRP Management (Inventory tab)	System inventory.	See the "Cisco 6400 NRP Management Window" section.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (Inventory tab)	Admin Address, ATM Address Type, and Physical Port Type.	See the "Cisco 6400 NRP ATM Port Management Window" section.
Line Card	Cisco 6400 Line Card Management (Line Card tab)	Line card inventory information for the selected line card (that is, module type, serial number, max supported ports, module description, hardware and software versions).	See the "Cisco 6400 Line Card Management Window" section.
Line Card ATM Port	Cisco 6400 Line Card ATM Port Management (Inventory tab)	Admin address, ATM address type, and physical port type.	See the "Cisco 6400 Line Card ATM Port Management Window" section.

Performance Information

The Cisco 6400 SCM software monitors and displays performance information on the Cisco 6400 UAC and specific components connected into the chassis. The performance information displays across a number of Element Manager windows. Table 5-8 details the Cisco 6400 UAC components that are monitored, the Element Manager window that you open to view the performance information, and details of the information displayed. Table 5-1 details how to open each of the Element Manager windows.

Table 5-8: Performance Information

Cisco 6400 UAC Component	Element Manager Window	Performance Information Displayed	For Further Information
Chassis	Service Uplink Bandwidth Utilization	Displays the receive and transmit percentage bandwidth utilization.	See the "Service Uplink Bandwidth Utilization" section.
NSP, NRP, and NRP2	Module Performance (Performance tab)	CPU usage. Start or stop performance logging on the selected module.	See the "Module Performance Window" section.
NRP ATM Port	Cisco 6400 NRP ATM Port Management (Performance tab)	Transmitted, connections established or detected, and SSCOP.	See the "Cisco 6400 NRP ATM Port Management Window" section.
Line Card ATM Port	Cisco 6400 Line Card ATM Port Management (Performance tab)	Transmitted, Connections Established, Detected, and SSCOP.	See the "Cisco 6400 Line Card ATM Port Management Window" section.
Interface	Interface Performance (Performance (1) tab)	View general information and packets and octets statistics. Start or stop performance logging for a selected interface.	See the "Interface Performance Window" section.
Interface	Interface Performance (Performance (2) tab)	View error statistics.	See the "Interface Performance Window" section.

Performance Manager (Viewing Historical Trends)

Additional (historical) performance information is available from the Performance Manager application. Performance Manager allows you to view general and performance-specific attributes in one application and in a variety of formats (for example, graphs and tables). You can:

Define the attributes or parameters
Choose the objects that you want to view
Choose the date and time of the view
Set the summary interval

For further information, see "Performance Management and Historical Data Statistics".

Statistics

The Cisco 6400 SCM software monitors and displays statistical information for the Line Card ATM Port (SONET APS). The information displays on a the SONET APS Element Manager window. Table 5-9 details the Element Manager window that you open to view the statistics information and details of the information that displays. Table 5-1 details how to open SONET APS Element Manager window.

Table 5-9: Statistics Information

Cisco 6400 UAC Component	Element Manager Window	Statistics Information Displayed	For Further Information
Line Card ATM Port (SONET APS)	SONET APS (Statistics tab)	Path, line, section, and operational.	See the "SONET APS Management Window" section.

IOS Image Download

The Cisco 6400 SCM software allows you to download IOS configuration information from a specified TFTP server (either manually or automatically at a specified time and date). Table 5-10 details parameters that can be configured in the IOS Image Download window. Table 5-1 details how to open each of the IOS Image Download window.

Table 5-10: IOS Image Download Information

Cisco 6400 UAC Component

Element Manager Window

IOS Image Download Information Displayed

For Further Information

NSP, NRP

(Executed from NSP for NRP2)

IOS Image Download

Configure the TFTP server. Initiate a download. Schedule a time for automatic download.

See the "Interface Configuration Window" section.

SNMP Management

The Cisco 6400 SCM software allows you to configure SNMP management information and enable or disable trap generation for a selected chassis. Table 5-11 details parameters that can be configured in the SNMP Management window. Table 5-1 details how to open each of the IOS Image Download window.

Table 5-11: SNMP Management

Cisco 6400 UAC Component	Element Manager Window	SNMP Management Information Displayed	For Further Information
Chassis	SNMP Management	Configure community names, SNMP version details. configure trap generation. enable or disable trap generation.	See the "SNMP Management Window" section.

Note The NRP2 card has an internal IP address. If a dialog window displays an NSP IP address where an NRP2 object was selected, the NRP2's IP address displays the NSP's IP address.

Command Log

The Cisco 6400 SCM software monitors and displays command log information for the selected NSP and NRP in the Command Log window. The information displays across a number of Element Manager windows. Table 5-12 details the information displayed in the Command Log window. Table 5-1 details how to open the Command Log window.

Table 5-12: Command Log (for NSP, NRP)

Cisco 6400 UAC Component	Element Manager Window	Information Displayed	For Further Information
NSP, NRP	Command Log	Command log details table. Uptime at last save, uptime at last change, maximum table entries, and entries deleted from table.	See the "Command Log Window" section.

Note By default, each command log and system log message created by an NRP2 appears on the NSP as a local message. This message contains the slot number of the NRP2 that created the message.

System Log Messages

The Cisco 6400 SCM software monitors and displays NSP and NRP system log messages. Table 5-13 details the Element Manager windows that you should open to view the SysLog Messages and provides details the information displayed. Table 5-1 details how to open the SysLog Messages windows.

Table 5-13: SysLog Messages (for NSP, NRP)

Cisco 6400 UAC Component	Element Manager Window	Information Displayed	For Further Information
NSP, NRP	SysLog Messages (SysLog Messages tab)	Displays a SysLog Message table. Also displays a SysLog Message Details panel (Messages Not Recorded, Messages Not Processed, Messages Deleted from Table, Notifications Sent, Maximum Table Entries, Maximum SysLog Severity, and Notifications Enabled).	See the "SysLog Messages Window" section.

Cisco 6400 Chassis Management Window

The Cisco 6400 Chassis Management window allows you to view and configure Fault, Status, Configuration, and Inventory information for a selected chassis.

Viewing the Cisco 6400 Chassis Management Window

To view the chassis management window, follow these steps.

Step 1 Place the cursor over a relevant object icon.

Step 2 Right-click Cisco 6400 UAC > Chassis > Manage > Chassis option.

See Table 5-1 for information on which objects allow you to launch the Cisco 6400 Chassis Management window.

The Cisco 6400 Chassis Management window appears with the Faults tab displayed (Figure 5-1).

Figure 5-1: Cisco 6400 Chassis Management Window—Faults Tab

The Cisco 6400 Chassis Management window displays a number of Cisco 6400 SCM EM window aspects. A Cisco 6400 Chassis list displays at the left side of the window. This list is populated with all of the Cisco 6400 chassis available from your launch point.

The Cisco 6400 Chassis Management window is divided into four tabbed sections:

Faults
Status
Configuration
Inventory

Faults Tab

The Faults tab (see Figure 5-1) appears by default when the Cisco 6400 Chassis Management window appears. The Faults tab displays a log of alarms raised against the selected chassis. The following section describes the fields in this window.

Alarm Information Table

The Alarm Information table displays the following information:

Alarm Index—An arbitrary integer value to uniquely identify an alarm information entry.
- Alarm Source—Indicates the source of the alarm. The variable displays a string in one of the following formats:
Chassis—Chassis alarms

Submodule—Submodule alarms

port@slot#/subslot#/port#'—Port alarms
Alarm Severity—Indicates the severity (minor, major, or critical) of the alarm.
Alarm Type—Indicates the type of alarm, which can be one of the following:
- coreTemp—The core temperature limit has been exceeded.
- inletTemp—Inlet temperature limit has been exceeded.
- totalFanFail—Total fan failure.
- partialFanFail—Fan tray failure.
- fanMissing—A fan is missing.
- pem0Fail—Power module 0 failure.
- pem1Fail—Power module 1 failure.
- sonetLineFail—SONET line failure.
- cardOIRAlarm—Card OIR alarm for removal or wrong type of insertion alarm.
- cardFail—Card failure alarm for nonredundant card failure, redundant primary card.
- cardPartialFail—Card partial failure alarm for redundancy or secondary card failure.
Alarm Cut Off Status—Indicates whether the audible or visible local alarm relay is cut off locally for the particular alarm source. When Alarm Cut Off Status is normal, the alarm in the entry has closed the local audible or visible alarm relay contacts. When Alarm Cut Off Status is cut off, the alarm in the entry initially closed the local relay contacts, but was suppressed by a local user pressing the external ACO button on the Cisco 6400 NSP.

Status Tab

To view the Status tab, follow these steps:

Step 1 From the Cisco 6400 Chassis Management window, click the Status tab. The status information for the selected chassis appears (Figure 5-2).

Figure 5-2: Cisco 6400 Chassis Management Window—Status Tab

Chassis Status

The Chassis Status panel (Figure 5-2) displays the following status information:

Core Temperature Status—Chassis temperature status.
Intake Temperature Status—Intake temperature of the chassis.
Fan Status—Status of the chassis fan.
12 Volt Power Supply Status—Status of the chassis 12-volt supply.
CPU Card LED Status—Status of the CPU card.
Ethernet Link LED—Status of the Ethernet link status LED on the CPU card.
Last Chassis Change—Last time the chassis physical content was changed.

Power Supply 1

The Power Supply 1 panel (Figure 5-2) displays the status of power supply 1.

Power Supply 2

The Power Supply 2 panel (Figure 5-2) displays the status of power supply 2.

Temperature Threshold Configuration

The Temperature Threshold Configuration panel displays the Clock Source Status. Notification signifies that the agent detects a change in the system clock source status. Notification is generated when the status value changes.

Facility Alarm Status

The Alarm Status panel displays the following status information:

Critical Alarm—When a green icon appears, no critical alarms are detected. When a red icon appears, at least one critical alarm is detected.
Major Alarm—When a green icon appears, no major alarms are detected. When a red icon appears, at least one major alarm is detected.
Minor Alarm—When a green icon appears, no minor alarms are detected. When a red icon appears, at least one minor alarm is detected.

Configuration Tab

To view the Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 Chassis Management window. See the "Viewing the Cisco 6400 Chassis Management Window" section for further details.

Step 2 Click the Configuration tab. The Cisco 6400 chassis configuration information appears (Figure 5-3).

Figure 5-3: Cisco 6400 Chassis Management Window—Configuration Tab

Step 3 Configure the information using the menus and data entry boxes.

Step 4 Save the changes.

The Configuration panel (Figure 5-3) displays the following information:

Temperature Threshold Configuration
Alarm Configuration

Temperature Threshold Configuration

The Temperature Threshold Configuration panel (Figure 5-3) allows you to view and configure the following information:

Core Major Threshold—Allows you to set and enable or disable the core major temperature alarm threshold.
Core Minor Threshold—Allows you to set and enable or disable the core minor temperature alarm threshold.
Intake Major Threshold—Allows you to set and enable or disable the intake major temperature alarm threshold.
Intake Minor Threshold—Allows you to set and enable or disable the intake minor temperature alarm threshold.

Alarm Configuration

The Alarm Configuration panel (Figure 5-3) allows you to view and configure the Clear Alarms chassis configuration information. Clear Alarms allows you to specify whether to clear all, major, or minor alarm indications and reset the alarm contacts. You can set Clear Alarms to All, Minor, Major, Critical, or Done.

Note When the Clear Alarms option is set, the alarm is still present in the table, but the alarm status displayed in the Alarm Cut Off Status column (displayed in the alarm table in the Faults tab) is set to Cut-Off.

Inventory Tab

To view the Inventory tab, follow these steps:

Step 1 Open the Cisco 6400 Chassis Management window. See the "Viewing the Cisco 6400 Chassis Management Window" section for further details.

Step 2 Click the Inventory tab. The Inventory tab appears (Figure 5-4).

Figure 5-4: Cisco 6400 Chassis Management Window—Inventory Tab

The Inventory tab displays the following information:

Chassis
Power Supply

Chassis

The Chassis panel (Figure 5-4) displays the following inventory information:

Chassis System Type—Displays the chassis system type.
Backplane Type—Displays the chassis backplane type.
Number of Slots—Displays the number of slots in the chassis for plug-in modules.
PCMCIA Slot 0 Type—Displays the type of PCMCIA slot 0 type.
PCMCIA Slot 1 Type—Displays the type of PCMCIA slot 1 type.

Power Supply

The Power Supply panel (Figure 5-4) displays the following inventory information:

PS1 Type—Displays the type of power supply number 1.
PS2 Type—Displays the type of power supply number 2.

Capacity Monitoring Window

The Cisco 6400 Chassis Capacity Monitoring window allows you to monitor the VPC/VCC allocation and maximize memory allocation for a selected Cisco 6400 Universal Access Concentrator (UAC).

Viewing the Cisco 6400 Chassis Capacity Monitoring Window

To view the Monitoring window, follow these steps.

Step 1 Place the cursor on a relevant object icon. See Table 5-1 for information on which objects allow you to launch the Cisco 6400 Chassis Capacity Monitoring window.

Step 2 Right-click Cisco 6400 UAC > Chassis > Manage > PVC Usage option.

The Cisco 6400 Chassis Capacity Monitoring window appears with the Chassis tab displayed (Figure 5-5).

PVC Management and Capacity Monitoring Tool

The Permanent Virtual Connection (PVC) Management and Capacity Monitoring tool allows you to better manage your PVC bandwidth resources by providing the information required to monitor the VPC/VCC allocation and maximize memory allocation for the Cisco 6400 Universal Access Concentrator (UAC).

Note The Management and Capacity Monitoring tool is only compatible with releases of Cisco IOS Release 12.1(4)DB and later that contain the show atm input-xlate-table and show atm input-xlate-table inuse commands for the NSP. Refer to the Cisco 6400 Software Configuration and Command Reference Guide for more information about ITT enhancements.

Cisco IOS Input Translation Table

The Input Translation Table is a hardware data structure used in the Cisco 6400 NSP for handling incoming cells. The ITT table consists of entries that are allocated in contiguous blocks for Virtual Circuit (VC) switching, and each block is dedicated to a Virtual Path Identifier (VPI) on an interface.

The entire NSP consists of a single ITT, which is organized in two banks of 32,000 entries each. This limits the use of large Virtual Channel Identifier (VCI) values and also limits the distribution of VCIs on VPIs as the number of VCs approaches 32,000. When an additional VC is added to a VPI that requires a larger block size than the current block, the current block is copied to a new larger block and the original block is freed. This leaves a series of small unused blocks.

As a result, ITT memory is fragmented. The ITT blocks grow to accommodate higher VCI values for a specific port or VPI, but ITT space is not returned unless the entire ITT is full.

ITT enhancements provide NSP functions to minimize fragmentation and enable the NSP to automatically determine the minimum ITT block size required to support the PVCs configured for each interface and VPI.

Capacity Monitoring Tool

The Capacity Monitoring tool:

Graphically displays memory block allocation by initializing a Telnet session with the NSP. The relevant ITT commands are executed (in Cisco IOS software) to collect information, collate it, and then store the results in the SCM local database. The ITT entry information is then displayed in a tabular format in the SCM database (see Figure 5-5).
Allows you to monitor the VPC/VCC allocation and generate an early alert informing you that the VCC space utilization has reached the threshold that you configured it to be.

At the report phase, you can set a threshold value. If this value is exceeded, an alarm occurs. The alarm is logged to the Event Browser. The default threshold is set to the maximum value.

Using the PVC Usage Feature

The PVC Usage feature is a menu option that allows you to display a window with information invoked from the Input Translation Table from Cisco IOS Release 12.1(4) DB operating software. The Cisco 6400 Chassis Management PVC Usage window displays two tabs:

Chassis
Interface

To access or use the PVC Usage option, follow these steps:

Step 1 Place the cursor on a relevant chassis, site, or shelf icon.

Step 2 Right-click Cisco 6400 UAC > Chassis > Manage > PVC Usage option.

The Cisco 6400 Chassis Capacity Monitoring window appears with the Chassis tab selected (Figure 5-5).

Figure 5-5: Cisco 6400 Chassis Monitoring Window—Chassis Tab

The Cisco 6400 Chassis Management Capacity Monitoring window displays a number of VCI statistics and port statistics (available ports) and a list of memory usage parameters. A Cisco 6400 chassis list box appears at the left side of the window. This list box is populated with all of the Cisco 6400 chassis available from your launch point.

Chassis Tab

To view the Chassis tab in the Capacity Monitoring window, follow these steps:

Step 1 Open the Cisco 6400 Chassis Management Capacity Monitoring window (Figure 5-5).

Step 2 Place the cursor on a relevant chassis, site, or shelf icon.

Step 3 Right-click Cisco 6400 UAC > Chassis > Manage > PVC Usage menu option to display the Chassis tab. The Capacity Monitoring window for the selected chassis appears.

The Chassis tab displays the following information:

A list box of defined chassis
VCC (Virtual Channel Connection) Statistics
- Active VCCs—Total number of active VCCs in this chassis with a status of Up.
- Threshold for Active VCCs—Default threshold is 65536. If this threshold value is exceeded, an alarm is generated when the update action is completed.
- VCC Space Utilization—Percentage of memory blocks populated with VCCs (formula is UTIL = Active VCCs/Space Allocated).
- Threshold for VCC Space Utilization—Default threshold value is set to the maximum value of 100 percent. If this threshold value is exceeded, an alarm is generated when the update action is completed.
Memory
- Space Allocated—Sum of the size of memory blocks currently allocated on this chassis.
- Space Utilization—Percentage of the total device memory that has been allocated (formula is UTIL = Space Allocated/65536).
Port Statistics—Lists the number of ports with a status of Up in the chassis that have no VCCs with VCI numbers greater than 31 and also ports that might have VCC numbers greater than 31 whose status is Down.
Memory Usage—Displays the status of block allocation usage in the Input Translation Table. ITT memory blocks are allocated only to active VCCs.
- Start Address—Identifies the starting address of the memory block.
- Block In-Use—Specifies if the block is in use:
- Yes, this block of memory is currently assigned.
- No, this block of memory is free for allocation.
- Block Size—Specifies the size of the memory block for each VPI on an interface. Values range from 32 to 16384. This value is rounded up to the smallest power of 2 greater than or equal to the entered value. (The blocks allocated must be a power of 2 in size, such as 16, 32, 64, and so on.)
- Interface—Specifies the interface type and port to which the memory blocks are allocated.
- VPI—VPI number to which the memory block is allocated. Values are 0 to 255.
- Largest VCI—Current largest VCI allocated to the VPI that this memory block is assigned.

Interface Tab

The Interface tab displays the interface selection list box and four panels: Port Statistics, Memory, VPI Statistics, and the Threshold for VCC Space Utilization field.

To view the Interface tab, follow these steps:

Step 1 From the Cisco 6400 Chassis Monitoring window, click the Interface tab.

The first interface tab window information for the selected chassis appears (Figure 5-6).

Figure 5-6: Cisco 6400 Chassis Monitoring Window—Interface Tab (1)

Note The Interface tab in the Capacity Monitoring window contains a scroll bar to view the entire VPI Statistics table of parameters. For purposes of viewing the entire VPI Statistics area, the Interface tab information is displayed in Figure 5-6 and Figure 5-7.

The Interface Tab displays the following information:

List of defined chassis.
List of selectable ATM ports (Interface) in the selected chassis.
Port Statistics
- Active VPIs—Number of active VPIs on this port with a status of Up.
- Inactive VPIs—Number of VPIs with a status of Down.
- Active VCCs—Total number of VCCs on this port with a status of Up.
- VCC Limit—Limit of VCCs that you can provision on this port. (Use Cisco IOS or SNMP to configure this parameter.)
- Maximum Available VCCs—Maximum number of VCCs that you can provision onto a new VPI on this port.
- VCC Space Utilization—Percentage of the memory allocated to this port that is populated with active VCCs.
- Threshold for VCC Space Utilization—The default threshold value is the maximum value of 100 percent. The threshold value in the Interface tab applies only to the interface that you choose from the list box and not on the entire chassis. Therefore, choose the interface and then set the threshold value for that interface. If this threshold is exceeded, an alarm is generated when the Update action is completed.
Memory
- VCC Space Utilization—Percentage of the total device memory allocated to this port (formula is UTIL = Space Allocated/65536).
- Threshold for Space Utilization—Default threshold value is set to the maximum value of 100 percent. If this threshold is exceeded, an alarm is generated when the Update action is completed.
- Space Allocated—Sum of the size of all memory blocks currently allocated to this port.
- Status Change Result—Effect on the allocated memory if the port status changes to Up.
VPI Statistics—Lists in tabular format:
- VPI—Number of the VPI.
- Active VCCs—Number of VCCs on this VPI with a status of Up.
- Inactive VCCs—Number of VCCs on this VPI with a status of Down.
- Space Allocated—Size of the memory block currently allocated to this VPI.
- Largest Active VCI—Highest VCI number allocated to this VPI with a status of Up.
- Largest Inactive VCI—Highest VCI number allocated to this VPI with a status of Down.
- Status Change Result—Effect on the allocated memory block if the VCC with the largest inactive VCI changes to a status of Up (for example, No Effect, Port already Up, Increase allocated space, Space not available).
- VCC Space Utilization—Percentage of the memory block allocated to the VPI that is populated with VCCs.
Threshold for VCC Space Utilization field (at the bottom of the window)—If this threshold is exceeded, an alarm is generated when the Update action is completed. The default threshold value is set to the maximum value of 100 percent and applies only to the interface that is selected.

The second interface tab window information for the selected chassis appears (Figure 5-7).

Figure 5-7: Cisco 6400 Chassis PVC Usage Window—Interface Tab (2)

Using the Update Button

The Update button initiates the collection, report, and alert phases of the PVC Usage function. The results of this update appear in tabular format in the Capacity Monitoring windows. If the threshold value is exceeded, an alarm notifies the operator.

To refresh the PVC statistics, you must click the Update button on the Monitoring windows.

Note The update process might vary depending on the size of your configuration.

To display updated parameters on the Capacity Monitoring windows for the entries in the Input Translation Table, follow these steps:

Step 1 From the Cisco 6400 Chassis Monitoring window, click the desired tab and click the Update button.

A dialog box prompts you to update or not (Figure 5-8).

Figure 5-8: Cisco 6400 Chassis Monitoring Window—Update Button

If you click:

Yes, the Action Report window appears (Figure 5-9).
No, the initial Capacity Monitoring window reappears.

Step 2 If you click Yes, an Action Report window appears with a series of status messages. Figure 5-9 shows a sample of a status message that can be appear in the Action Report window.

Figure 5-9: Cisco 6400 Chassis Monitoring Window—Action Report

Note If you click the Save button, then the messages (for example, Update for Chassis (NSP) IP Address x.x.xx.xx, Successfully Updated Port Attributes) displayed from the Action Report window are stored in a text file.

SNMP Managemen t Window

The SNMP Management window allows you to:

Enter or modify the SNMP version and read or write names for a selected device.
Enable or disable trap generation on a selected device from this window.

Viewing the SNMP Management Window

To view the SNMP management window, follow these steps.

Step 1 Place the cursor on a relevant object icon or from an object list. See Table 5-1 for information on which objects allow you to launch the SNMP Management window.

Step 2 Right-click Cisco 6400 UAC > Chassis > Manage > SNMP Management option.

The SNMP Management window appears with the SNMP Management tab displayed (Figure 5-10).

Figure 5-10: SNMP Management Window—SNMP Management Tab

The SNMP Management panel (Figure 5-10) displays the following information:

Community Names
SNMP V3 Specific
Version
Trap Generation

Community Names

The Community Names panel provides a security mechanism for SNMP communications. The device holds its own community names, so the correct community names must be used in order to get or set attributes from the device.

V1 Read—Community string used to retrieve attributes from a device using the SNMPv1 protocol.
V1 Write—Community string used to set attributes on a device using the SNMPv1 protocol.
V2 Read—Community string used to retrieve attributes from a device using the SNMPv2c protocol.
V2 Write—Community string used to set attributes on a device using the SNMPv2c protocol.

SNMP V3 Specific

This panel provides the following options:

v3 User Name—The user who is conducting the SNMP operation. Default value is SCM.
v3 Authorization Key—The user's encrypted password key used in message authentication. If authorization is specified in the security level, then you must provide an authorization key (password).
v3 Security Level—A level of security at which SNMP messages can be sent. The three security levels that can be used are:
- noAuthNoPriv—SNMP messages are sent without authentication and without privacy.
- authNoPriv—SNMP messages are sent with authentication but without privacy.
- authPriv—SNMP messages are sent with authentication and with privacy.

Version

Version displays the SNMP Version dropdown list, which allows you to choose the SNMP version.

Trap Generation

Trap Generation displays the following options:

Enable—Click Enable to enable trap generation for the selected chassis. Traps generated by the selected chassis are sent to the IP addresses listed in the Trap Destination and Community table.
Disable—Click Disable to disable trap generation for the selected chassis. No traps generated by the selected chassis are sent to the IP addresses listed in the Trap Destination and Community table.

Enabling and Disabling Trap Generation

When trap generation is enabled on a selected chassis, any traps generate alarms and send them to the IP address of the specified chassis. This means that alarms are visible to the user in the appropriate view of the Cisco 6400 SCM. You can also disable this feature so that no traps are generated and no alarms are sent. This means that no alarms are visible to the user on the selected chassis.

To enable and disable trap generation, follow these steps:

Step 1 Place the cursor on a relevant object icon or from an object list to launch the SNMP Management window.

Step 2 Right-click Cisco 6400 UAC > Chassis > Manage > SNMP Management option.

Step 3 Choose the relevant Chassis from the IOS Host list displayed at the left side of the window.

Step 4 Click Enable to allow trap generation or click Disable to avoid trap generation.

See the "SNMP Management Window" section for further information on the parameters displayed on this tab.

C hassis Configuration Window

The Chassis Configuration window allows you to view and configure parameters relevant to the selected chassis and commission or decommission a selected chassis. The Chassis Configuration—Additional Descriptions tab allows you to specify additional description information for a selected chassis. The Description 1 and Description 2 data entry fields allow you to enter any additional text descriptions for identification purposes (for example, CLLI codes could be entered).

Viewing the Chassis Configuration Window

From a relevant object icon or from an object list right-click Cisco 6400 UAC > Chassis > Manage > Configuration option. (See Table 5-1 for information on which objects allow you to launch the Chassis Configuration window.) The Chassis Configuration window (Figure 5-11) appears with the Configuration tab displayed. The Configuration tab displays four panels.

Figure 5-11: Chassis Configuration Window—Configuration Tab

Configuration Tab

The Configuration tab (Table 5-11) displays four panels: Validation Parameters, Power Supply, Actions, and Commission Status.

Validation Parameters

The Validation Parameters panel contains attributes that describe the population characteristics of a chassis and are used to validate module deployment:

Number of Slots—Displays the number of slots in the chassis for plug-in modules.
Unavailable Slots—Displays a comma-separated list of slots that modules cannot be deployed into.
Max Number of Sub-Modules per Slot—Defines the maximum number of submodules that can be deployed into each slot for the selected chassis.

Action

The Actions panel allows you to take action whenever a failure or change in the chassis is detected:

Failure—Allows you to configure the action to be taken when a chassis failure occurs (that is, a power supply, voltage, temperature, or fan failure). From the Cisco-Rhino-MIB: ciscoLS1010ChassisFailureAction.
Change—Allows you to configure the action to be taken when a chassis change occurs (that is, a power supply, voltage, fan or board, change). From the Cisco-Rhino-MIB: ciscoLS1010ChassisChangeAction.

Clock

The Clock panel allows you to view and change the following information:

Source Priority—Allows you to specify the highest priority at which the "system" is configured as a network clock source. You can set the Source Priority to Priority 1, Priority 2, Priority 3, Priority 4, or Priority 5.
Clocking Mode—Allows you to set the clocking mode of the system to:
- Revertive—Clock changes to a higher priority clock when one is available.
- Non Revertive—Clock sticks to the current priority, even though a higher priority clock is available.

Power Supply

The Power Supply panel allows you to view and change the following information:

PS1 Admin Status—Allows you to enable, disable, or reset power supply 1.
PS2 Admin Status—Allows you to enable, disable, or reset power supply 2.

Actions

The Actions panel displays the Management panel.

Management

The Management panel allows you to commission or decommission the selected chassis. Click Commission to force a discovery of the contents of the selected chassis.

Note A chassis can be commissioned quickly (without opening the Chassis Configuration window) by right-clicking on the chassis map in the Map Viewer window (in the c6400Manager view) and choosing the Cisco 6400 UAC > Chassis > State > Commission option. Selecting the Commission option commissions the chassis and the cards within the chassis. The state of the chassis and the cards within the chassis changes to Normal.

To commission a chassis (from the Chassis Configuration window), follow these steps:

Commission—Click Commission to commission the selected chassis.
Decommission—Click Decommission to decommission the selected chassis.

Global Performance Logging

The Global Performance Logging panel allows you to start or stop global performance logging. Global performance logging is off by default.

Start—Click Start to begin global performance logging.
Stop—Click Stop to stop global performance logging.

Starting Global Performance Logging

Global performance logging allows the Cisco 6400 SCM to collect performance information for the NSP, NRP, and NRP2 modules and for NRP and NLC port interfaces within a selected chassis. This historical information can then be viewed using Performance Manager. "Performance Management and Historical Data Statistics," provides further information on how to use the Performance Manager application.

Note Performance logging can start or stop on a per-module or interface (port) basis. See the "Module Performance Window" section for details on how to start performance logging for a selected module (that is, NSP or NRP modules). See the "Interface Performance Window" section for details on how to start performance logging for a selected interface (that is, for NRP or NLC port interfaces).

To begin global performance logging for a selected chassis, follow these steps:

Step 1 Open the Chassis Configuration window. See the "Viewing the Chassis Configuration Window" section for further details. The Configuration tab appears.

Step 2 Choose the relevant Chassis from the list displayed at the left side of the window.

Step 3 Click Start to begin performance logging on the selected chassis.

Stopping Global Performance Logging

Note Performance logging can also be stopped on a per-module or interface (port) basis. See the "Module Performance Window" section for details on how to stop performance logging for a selected module (that is, NSP or NRP modules). See the "Interface Performance Window" section for details on how to stop performance logging for a selected interface (that is, for NRP or NLC port interfaces).

To stop global performance logging for a selected chassis, follow these steps:

Step 1 Open the Chassis Configuration window. See the "Viewing the Chassis Configuration Window" section for further details. The Configuration tab appears.

Step 2 Choose the relevant Chassis from the list displayed at the left side of the window.

Step 3 Click Stop to stop global performance logging for the selected chassis.

Commission Status

The Commission Status panel gives you the status of the last commission executed.

Additional Descriptions Tab

The Additional Description tab (Figure 5-12) displays the Additional Descriptions panel.

Descriptions 1 and 2 (optional) allow you to specify additional description information for a selected chassis. The Description 1 and Description 2 data entry fields allow you to enter any additional text descriptions for identification purposes (for example, CLLI codes could be entered).

Figure 5-12: Chassis Configuration Window—Additional Description Tab

Cisco 6400 NSP Management Window

The Cisco 6400 NSP Management window allows you to monitor and configure installed NSP modules. The Cisco 6400 NSP Management window displays four tabs: Faults, Status, Configuration, and Inventory.

Note To commission the selected NSP, see the "Commissioning an NSP, NRP, NRP2, or NLC Module" section for further details.

Viewing the Cisco 6400 NSP Management Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > NSP option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 NSP Management window.) The Cisco 6400 NSP Management window appears with the Faults tab displayed. The Fault s tab (Figure 5-13) displays two panels: Faults and Cisco Contact Details.

Figure 5-13: Cisco 6400 NSP Management Window—Faults Tab

Faults Tab

To view the Faults tab, follow these steps:

Step 1 Open the Cisco 6400 NSP Management window. See the "Viewing the Cisco 6400 NSP Management Window" section for further details.

The Faults tab appears (see Figure 5-13).

Step 2 Choose a relevant Chassis from the chassis list.

The fault information for the selected chassis appears.

Faults

The Faults panel (see Figure 5-13) displays the following error information:

Last Restart Reason—Displays the reason why the system was last restarted.
Last Auth Failure Address—Displays the last SNMP authorization failure IP address.

Cisco Contact Details

Displays Cisco contact details.

Status Tab

To view the Status tab, follow these steps:

Step 1 Open the Cisco 6400 NSP Management window. See the "Viewing the Cisco 6400 NSP Management Window" section for further details.

Step 2 Click the Status tab. The Status tab (Figure 5-14) is divided into four panels: Status, System Configuration File, Host Configuration File, and Network Configuration File.

Figure 5-14: Cisco 6400 NSP Management Window—Status Tab

Step 3 Choose a relevant Chassis from the list.

The status information for the selected chassis appears (Figure 5-14).

Status

The Status panel (Figure 5-14) displays the following information:

System Uptime—Displays the time that the system has been active.
Operational Status—Displays the operational status of the system.
Free Memory—Displays the amount of free memory in bytes.

System Configuration File

The System Configuration File panel (Figure 5-14) displays the following information:

Host IP Address—Displays the address of the host that supplied the system boot image.
File Name—Displays the name of the system boot image.
Protocol—Displays the protocol or media that supplied the system boot image.

Host Configuration File

The Host Configuration File panel (Figure 5-14) displays the following information:

Host IP Address—Displays the address of the host that provided the host-configuration file.
File Name—Displays the name of the last configured host-confg file.
Protocol—Displays the protocol that supplied the host- confg file.

Network Configuration File

The Network Configuration File panel (Figure 5-14) displays the following status information:

Host IP Address—Displays the address of the host that supplied the network-confg file.
File Name—Displays the name of the network configuration file.
Protocol—Displays the protocol that supplied the network-confg file.

Configuration Tab

The Configuration tab allows you to configure some of the parameters (System Configuration and CLI Passwords) that can be set on the selected NSP module.

Note To Commission a selected NSP, see the "Commissioning an NSP, NRP, NRP2, or NLC Module" section for further details.

To view the Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 NSP Management window. See the "Viewing the Cisco 6400 NSP Management Window" section for further details.

Step 2 Click the Configuration tab (Figure 5-15).

Figure 5-15: Cisco 6400 NSP Management Window—Configuration Tab

Step 3 Choose a relevant Chassis from the chassis list. The configuration information for the selected NSP appears (Figure 5-15). The Configuration tab displays the system configuration panel.

Step 4 Edit the information in the Configuration tab.

Step 5 Click Save from the Edit menu to save any changes.

System Configuration

The System Configuration panel allows you to configure the following information:

System Name—Allows you to specify a name for the managed node. By convention, the System Name is the node's fully qualified domain name. The field is blank when System Name is unknown.
System Contact—Allows you to specify the contact person for the managed node together with information on how to contact the person. When contact information is unknown, the field is blank.
System Location—Allows you to specify the physical location of the node. The System Contact field is blank when the location is unknown.
IP Address—Allows you to specify the IP address of the selected chassis.
Administration Status—Allows you to enable, disable or reset the module. You can set the Administration Status option to:
- Reset—Reset the module's control logic.
- Enable—Enable the module.
- Disable—Disable the module.

Invento ry Tab

To view the Inventory tab, follow these steps:

Step 1 Open the Cisco 6400 NSP Management window. See the "Viewing the Cisco 6400 NSP Management Window" section for further details.

Step 2 Click the Inventory tab (Figure 5-16).

Figure 5-16: Cisco 6400 NSP Management Window—Inventory Tab

Step 3 Choose a relevant Chassis from the chassis list. The Inventory information for the selected chassis appears.

The Inventory tab displays the System Inventory panel.

System Inventory

The System Inventory panel displays the following information:

Host Name—Represents the name of the host in printable ASCII characters.
Domain Name—Displays the domain portion of the domain name of the host.
Hardware Version—Displays the hardware version of the module.
Module Type—Displays the type of module installed.
ROM ID—Displays the System Bootstrap description and version identification.
Module Description—Displays a descriptive string used by the agent to describe the module.
System Description—Displays a description of the entity. The System Description value should include the full name and version identification of the system's hardware type, software operating system, and networking software.
BootImage Host—Displays the IP address of the host that supplied the current software.
Serial Number—Displays the serial number of the selected module.
Software Version—Displays the software version of the selected module.

M odule Configuration Window

The Module Configuration window allows you to enter a description for a selected NSP, NRP, NRP2, or NLC module and commission or decommission the selected module.

Viewing the Module Configuration Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > Configuration option. (See Table 5-1 for information on which objects allow you to launch the Module Configuration window.) The Configuration tab displays two panels: Additional Descriptions and Actions. The Module Configuration window (Figure 5-17) appears with the Configuration tab displayed.

Figure 5-17: Module Configuration Window—Configuration Tab

The Module list displays half-height modules (OC-3 or DS3 NLCs) with a slot and subslot number (for example, DS3-8-0). Full-height modules (NSPs, NRPs, NRP2s, or OC-12 NLCs) display as a module with a slot number (for example, NRP-5). When selecting a module from the list, you must first identify the module's location in the chassis and then choose the module according to its slot location in the rack.

Additional Descriptions

Actions

The Actions panel allows you to commission or decommission the selected module:

Click Commission to commission the selected module.
Click Decommission to decommission the selected module.

Commissioning an NSP, NRP, NRP2, or NLC Module

Step 1 Open the Module Configuration window. See the "Viewing the Module Configuration Window" section for further details.

Step 2 Choose the relevant Chassis and Module from the lists displayed at the left side of the window. The status of the selected module appears at the bottom left corner of the window.

Step 3 Enter optional Description 1 and Description 2 information. The Description 1 and Description 2 data entry fields allow you to enter any additional text descriptions for identification purposes (for example, CLLI codes could be entered).

Step 4 Click Commission when the status is Decommissioned.

The NSP, NRP, or NLC is now commissioned; its state changes to Commissioning and then Normal. The Commission Status field displays the state of the module.

Decommissioning an NSP, NRP, NRP2, or NLC Module

Step 1 Open the Module Configuration window. See the "Viewing the Module Configuration Window" section for further details.

Step 2 Choose the relevant Chassis and NSP, NRP, or NLC from the lists displayed at the left side of the window. The status of the selected card appears at the bottom left corner of the window.

Step 3 Click Decommission when the status is Normal.

The NRP, NSP, or NLC is now decommissioned; its state changes to Decommissioned. The Commission Status field displays the state of the module.

M odule Performance Window

The Module Performance window displays performance attributes for the selected module. The Module Performance tab displays CPU usage information and allows you to start or stop performance logging for the selected NSP, NRP, or NRP2 modules (see Figure 5-18).

Note Performance logging can also be started or stopped on a global basis for a selected chassis. See the "Chassis Configuration Window" section for details on how to start or stop global performance logging for a selected chassis.

Selecting an NLC module provides performance data for the NSP. The NSP displays the selected NLC's performance data.

Note The values displayed relate to CPU performance, so modules without a CPU display the same value as the CPU card in the chassis.

Viewing the Module Performance Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > Performance option. (See Table 5-1 for information on which objects allow you to launch the Module Performance window.)

The Module Performance window appears with the Performance tab displayed. The Performance tab (Figure 5-18) displays two panels: CPU Usage and Performance Logging. The CPU Usage and Performance Logging panels show "real-time" performance statistics.

Figure 5-18: Module Pe rformance Window—Performance Tab 41578.tif

Choose a Module from the list displayed. The performance information for the selected module appears.

CPU Usage

The CPU Usage panel displays the following performance information:

CPU Busy—Displays the percentage usage of the CPU.
Average (1 min)—Displays the percentage usage of the CPU averaged over a 1-minute period.
Average (5 min)—Displays the percentage usage of the CPU averaged over a 5-minute period.

Performance Logging

The Performance Logging panel allows you to start or stop performance logging for the selected module:

Start—Click Start to begin performance logging.

Stop—Click Stop to stop global performance logging.

Note Performance logging logs data that can be displayed using the Performance Manager application. Figure 5-18 displays "real-time" performance statistics. Historical performance information can be viewed using Performance Manager. "Performance Management and Historical Data Statistics," provides further information on the Performance Manager application.

Starting or Stopping Performance Logging for a Selected Mod ule

Performance logging allows performance information to be collected for a selected module. This historical information can then be viewed using Performance Manager. "Performance Management and Historical Data Statistics," provides further information on how to use the Performance Manager application.

To start or stop performance logging for a selected module, follow these steps:

Step 1 Open the Cisco 6400 NSP Management window. See the "Viewing the Cisco 6400 NSP Management Window" section for further details.

Step 2 Click Start to begin performance logging for the selected module. Click Stop to stop performance logging for the selected module.

Step 3 Launch the Performance Manager application to view the historical performance information for the selected module.

Command Log Window

The Command Log window allows you to view the event commands stored in the Command Log Details table and the system log messages stored in the syslog message table for the selected NSP.

Viewing the Command Log Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > View > Command Log option. (See Table 5-1 for information on which objects allow you to launch the Command Log window). The Command Log window (Figure 5-19) appears with the Command Log Details tab displayed.

Figure 5-19: Command Log Window—Command Log Details Tab

Command Log Details Tab

To view the Command Log Details information, follow these steps:

Step 1 Open the Cisco 6400 NSP Logs window. See the "Viewing the Command Log Window" section for further details. The Command Log Details tab appears (Figure 5-19).

Step 2 Choose a relevant Chassis.

The Command Log Details table for the selected NSP displays the following information:

Index—Arbitrary integer value to uniquely identify the listed events. When it reaches the maximum value, the agent wraps the value back to 1 and might flush existing entries.
Event Time—Value of sysUpTime when the event occurred.
Command Source—Source of the command that instigated the event. You will see either commdLine or SNMP.
Config Source—Configuration data source for the event.
Config Destination—Configuration data destination for the event.
Terminal Type—When Command Source is set to commandLine, the terminal type appears (unknown, console, terminal, virtual, or auxiliary). Otherwise notApplicable appears.
Terminal Number—When Command Source is set to commandLine, the terminal number appears. When the terminal is not available or not applicable, -1 appears.
Terminal User—When Command Source is set to commandLine, the name of the logged-in user appears. When the terminal type is not available or not applicable nothing appears in the field.
Terminal Location—When Command Source is set to commandLine, the hard-wired location of the terminal or the remote host for an incoming connection appears. When the terminal type is not available or not applicable nothing appears in the field.
Command Source Address—When Terminal Type is set to virtual, the internet address of the connected system appears. When Command Source is set to SNMP, the internet address of the requester appears.
Virtual Host Name—When Terminal Type is set to virtual, the host name of the connected system appears. When the terminal type is not available or not applicable nothing appears in the field.
Config Filename—When Config Source or Config Destination is set to networkTftp or networkRcp, the configuration filename at the storage file server appears.
RCP User—When Config Source or Config Destination is set to networkRcp, the remote username appears.

Event History Details

The Event History Details panel (Figure 5-19) displays the following information:

Uptime at Last Save—Displays the amount of time the system had been up, when the running configuration was last saved (written).
Uptime at Last Change—Displays the amount of time the system had been up when the running configuration was last changed.

Note When the value of Uptime at Last Change is greater than Uptime at Last Save, the configuration has been changed but not saved.
Uptime at Last Startup Change—Displays the amount of time the system had been up, when the startup configuration was last written to. In general the Uptime at Last Startup Change is the default configuration used when cold starting the system. It might have been changed by a save of the running configuration or by a copy from elsewhere.
Maximum Table Entries—Maximum number of entries that can be held in the table.
Entries Deleted from Table—Number of times the oldest entry was deleted to make room for a new entry.

Step 3 Scroll through the list of event commands (using the arrow keys) until the relevant event command appears. The down arrow displays the next 10 entries and the up arrow displays the previous 10 entries. Use the horizontal scroll bar to view all the table entries. Drag the scroll bar until the relevant information appears. You can change the width of each column if necessary to view fault strings clearly (see the "Changing Column Width" section).

Changing Column Width

To change the width of a column, follow these steps:

Step 1 Open the relevant window displaying a table.

Step 2 Place the cursor to the left of a column heading and move the cursor until it changes to a double arrow.

Step 3 Click and hold the left mouse button when the cursor changes.

Step 4 Drag the cursor until the column is at the required width.

Step 5 Release the mouse button.

Any text wider than the column is truncated. The column widths return to the default widths when you close this window.

SysLog Messages Window

The SysLog Messages window displays log information for the selected NSP or NRP modules and is useful for diagnosing Cisco 6400 failure conditions.

Viewing the SysLog Messages Window

To view the SysLog Messages window, follow these steps:

Step 1 From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > View > System Log option. (See Table 5-1 for information on which objects allow you to launch the SysLog Messages window.)

The SysLog Messages window (Figure 5-20) appears with the SysLog Messages tab displayed.

Figure 5-20: SysLog Messages Window—SysLog Messages Tab

Step 2 Choose a relevant Chassis. The SysLog Message Table appears for the selected chassis.

Step 3 Scroll through the list of system messages using the arrow keys until you find the information you want. The right arrow displays the next 10 entries and the left arrow displays the previous 10 entries.

You can view all the table entries by using the horizontal scroll bar. Click and drag the scroll bar until you see the information you want. You can change the width of each column if necessary (see the "Changing Column Width" section).

SysLog Messages Table

The SysLog Messages table (Figure 5-20) displays the following information:

Index—Arbitrary integer value to uniquely identify the listed messages. When it reaches the maximum value the agent flushes the table and wraps the value back to 1.
Facility—Name of the facility that generated the Facility message.
Severity—Displays the severity of the message.
Message Name—Textual identification for the message type. A facility name in conjunction with a message name uniquely identifies a message type.
Message Text—Displays the text of the message. When the text of the message exceeds 255 bytes, the message is truncated to 254 bytes and an asterisk (*) character is appended, indicating that the message has been truncated.
Time Stamp—Displays the time that the message was generated.

SysLog Message Details

The SysLog Message Details panel (Figure 5-20) displays the following information:

Messages Not Recorded—Displays the number of syslog messages that were ignored.
Messages Not Processed—Displays the number of messages which could not be processed due to lack of system resources.
Messages Deleted From Table—Number of entries that have been removed to make room for new entries.
Notifications Sent—Displays the number of notifications sent.
Maximum Table Entries—Displays the upper limit on the number of entries that the table can contain.
Maximum SysLog Severity—Any message with a severity less than this one will be ignored by the agent. The Maximum SysLog Severity level can be set to emergency, alert, critical, error, warning, notice, info, or debug.
Notifications Enabled—Displays whether notifications are enabled or not enabled.

Cisco 6400 NRP Management Window

The Cisco 6400 NRP Management window is divided into four tabbed sections: Faults, Status, Configuration, and Inventory.

Note The NRP2 cards appear in the node route processor list in the NRP Management window.

Note To commission the selected NRP, see the "Commissioning an NSP, NRP, NRP2, or NLC Module" section for further details.

Viewing the Cisco 6400 NRP Management Windows

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > NRP option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 NRP Management window.) The Cisco 6400 NRP Management window appears with the Faults tab displayed (Figure 5-21).

Figure 5-21: Cisco 6400 NRP Management Window—Faults Tab

Faults T ab

To view the Faults tab, follow these steps:

Step 1 Open the Cisco 6400 NRP Management window. See the "Viewing the Cisco 6400 NRP Management Windows" section for further details.

Step 2 The Faults tab appears by default. See the "Faults Tab" section for further information.

Step 3 Choose the relevant Chassis and NRP. The fault information for the selected chassis appears.

Faults

The Faults panel displays the following error information:

Last Restart Reason—Displays the reason why the system was last restarted.
Last Auth Failure Address—Displays the last SNMP authorization failure IP address.

Cisco Contact Details

The Cisco Contact Details panel displays Cisco contact information.

Status Tab

To view the Status tab, follow these steps:

Step 1 Open the Cisco 6400 NRP Management window. From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > NRP option. The Cisco 6400 NRP Management window appears (Figure 5-21).

Step 2 From the Cisco 6400 NRP Management window, click the Status tab (Figure 5-22).

Figure 5-22: Cisco 6400 NRP Management Window—Status Tab

Step 3 Choose the relevant chassis and NRP.

The status information for the selected NSP and NRP appears.

Status

The Status panel (Figure 5-22) displays the following information:

System Uptime—Displays the time that the system has been active.
Free Memory—Displays the amount of free memory in bytes.

System Configuration File

The System Configuration File panel displays the following status information:

Host IP Address—Displays the address of the host that supplied the system boot image.
File Name—Displays the name of the system boot image.
Protocol—Displays the protocol or media that supplied the system boot image.

Host Configuration File

The Host Configuration File panel displays the following information:

Host IP Address—Displays the address of the host that provided the host-configuration file.
File Name—Displays the name of the last configured host-confg file.
Protocol—Displays the protocol that supplied the host-confg file.

Network Configuration File

The Network Configuration File panel displays the following information:

Host IP Address—Displays the address of the host that supplied the network-configuration file.
File Name—Displays the name of the network configuration file.
Protocol—Displays the protocol that supplied the network-confg file.

Configuration Tab

Note To commission the selected NRP, see the "Commissioning an NSP, NRP, NRP2, or NLC Module" section for further details.

Note The NRP2's IP address displays the same address as the NSP in the selected chassis.

To view the Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 NRP Management window. See the "Viewing the Cisco 6400 NRP Management Windows" section for further details.

Step 2 Click the Configuration tab (Figure 5-23).

Figure 5-23: Cisco 6400 NRP Management Window—Configuration Tab

Step 3 Choose the relevant Chassis and NRP.

The configuration information for the selected NRP appears (Figure 5-23).

Step 4 Change the information in the dropdown lists and data entry boxes.

Step 5 Save the changes.

The Configuration tab displays the System Configuration panel.

System Configuration

The System Configuration panel allows you to configure the following information:

System Name—Allows you to specify a name for the managed node. By convention, it is the node's fully qualified domain name. When the name is unknown it is left blank.
System Contact—Allows you to specify the contact person for the managed node, together with information on how to contact them. When no contact information is known the field is left blank.
System Location—Allows you to specify the physical location of the node. The field is left blank when the location is unknown.
IP Address—Allows you to specify the IP address of the selected NRP.
Administration Status—This option allows you to enable, disable, or reset the module. You can set the Administration Status option to:
- Reset—Reset the module's control logic.
- Enable—Enable the module.
- Disable—Disable the module.

Inventory Tab

To view the Inventory tab, follow these steps:

Step 1 Open the Cisco 6400 NRP Management window. See the "Viewing the Cisco 6400 NRP Management Windows" section for further details.

Step 2 Click the Inventory tab (Figure 5-24).

Figure 5-24: Cisco 6400 NRP Management Window—Inventory Tab

Step 3 Choose a relevant Chassis and NRP.

The Configuration tab displays the System Inventory panel.

System Inventory

The System Inventory panel (Figure 5-24) displays the following information:

Host Name—Displays the name of the host in printable ASCII characters.
Domain Name—Displays the domain portion of the domain name of the host.
Hardware Version—Displays the hardware version of the module.
Module Type—Displays the type of module installed.
ROM ID—Displays the System Bootstrap description and version identification.
Module Description—Displays a descriptive string used by the agent to describe the module.
System Description—Displays a description of the entity. The System Description should include the full name and version identification of the system's hardware type, software operating-system, and networking software.
BootImage Host—Displays the IP address of the host which supplied the current software.
Serial Number—Displays the serial number of the selected module.
Software Version—Displays the software version number of the selected module.

SSG Configuration Window

The SSG Configuration window is divided into three tabs: SSG Configuration, PPPoA Configuration, and PPPoE Configuration.

Viewing the SSG Configuration Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > SSG Configuration option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 NRP Management window.) The SSG Configuration window (Figure 5-25) appears with the SSG Configuration tab displayed.

Figure 5-25: SSG Configuration Window—SSG Configuration Tab

SSG Configuration Tab

To view the SSG Configuration tab, follow these steps:

Step 1 Open the SSG Configuration window.

Step 2 Choose a relevant Chassis and NRP.

The SSG Configuration tab displays the following panels:

SSG Parameters

The SSG Parameters panel are a prerequisite for setting NRP SSG features. The SSG Parameters panel displays the following information:

Transparent Passthrough—When enabled traffic can transparently pass through the NRP-SSG device.
Cisco Express Forwarding—When enabled will use CEF; if disabled will use fast switching. Cisco Express Forwarding should only be set to Enabled when using Cisco IOS version 12.0(5) and later.
Default Network IP Address—IP address of the default network.
Default Network Subnet Mask—Subnet mask of the default network. A subnet mask is a 32-bit number used to separate the network and host sections of an IP address.
Service Password—This password must be the same as the passwords set in the IP Uplink service configuration window.

Layer 3 Parameters

The Layer 3 Parameters panel allows you to enable service selection dashboard access and layer 3 services. The Layer 3 Parameters panel displays the following information:

SSG Auth-Port—Authentication port for the SSG. Defaults to 1645.
SSG Acct-Port—Port defined for the SSG. Defaults to 1646.
Shared Secret—Shared password between the SSG and SSD.

Local RADIUS Parameters

Note Setting the Local RADIUS Parameters panel values are a prerequisite for setting NRP SSG features.

The Local RADIUS Parameters panel displays the following information:

IP Address—IP address of the local RADIUS server that resides within the SSG's default network.
Auth-Port—Authentication port for the local RADIUS server. Defaults to 1645.
Acct-Port—Port defined for the local RADIUS server. Defaults to 1646.
Secret Key—Password shared between the local RADIUS server and the SSG.

Configure

Click Configure to configure the parameters set in the SSG Configuration Window (SSG Configuration tab) on the NRP-SSG.

Configuring SSG Configuration

SSG configuration should be carried out when the NRP-SSG functionality is required. To set the SSG configuration parameters onto a selected NRP-SSG, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Choose a relevant Chassis and NRP.

Step 3 Configure the parameters displayed in the SSG Parameters, Layer 3 Parameters, and Local RADUIUS Parameters panels.

Step 4 Click Configure to set the parameters on the selected NRP-SSG.

Deconfigure

Click Deconfigure to deconfigure the parameters set on the NRP-SSG.

Deconfiguring SSG Configuration

SSG deconfiguration should be carried out when the NRP-SSG functionality is no longer required. To deconfigure the SSG configuration parameters from a selected NRP-SSG, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Choose a relevant Chassis and NRP.

Step 3 Click Deconfigure to deconfigure the parameters set on the selected NRP-SSG.

PPPoA Configuration Tab

To view the PPPoA Configuration tab, follow these steps:

Step 1 Open the SSG Configuration window.

Step 2 Click the PPPoA Configuration tab. The configuration-related panels (Figure 5-26) appear.

Figure 5-26: SSG Configuration Window—PPPoA Configuration Tab

Step 3 Choose a relevant Chassis and NRP.

The PPPoA Configuration tab (Figure 5-26) displays three panels:

PPPoA Virtual Template
PPPoA Address Pool
PPPoA Configuration

The PPPoA Configuration tab allows parameters to be set on the NRP-SSG that are prerequisites of the PTA-MD service.

Note Before connecting a subscriber to a PTA-MD service using PPPoA, the corresponding parameters on the PPPoA Configuration tab should be configured. For example, the parameters in the PPPoA Virtual Template and PPPoA IP Address Pool should be set and configured to connect a subscriber to a PTA-MD service using PPPoA.

PPPoA Virtual Template

The PPPoA Virtual Template panel displays the following information:

Authentication Type—Authentication type for any subscribers wanting to connect to this service.
IP Unnumbered Interface—Allows the operator to choose which interface IP to target traffic at.
Compression Type—Compression type used within the virtual template.

PPPoA IP Address Pool

The PPPoA IP Address Pool panel displays the following information:

Higher IP Address—Upper limit on the IP address pool.
Lower IP Address—Lower limit on the IP address pool.

No IP address pool is configured when the Higher IP Address and Lower IP Address parameters are left blank.

PPPoA Configuration

Click Configure to configure the parameters set on the NRP-SSG or click Deconfigure to deconfigure the parameters set on the NRP-SSG.

Configuring PPPoA Configuration

PPPoA Configuration must be carried out before a subscriber can be connected to an NRP using PPPoA or before a subscriber can be statically connected to an IP Uplink service. To set the PPPoA configuration parameters onto a selected NRP, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Click the PPPoA Configuration tab.

Step 3 Choose a relevant Chassis and NRP.

Step 4 Configure the parameters displayed in the PPPoA Virtual Template and PPPoA IP Address Pool panels.

Step 5 Click Configure to set the parameters on the selected NRP.

Deconfiguring PPPoA Configuration

To deconfigure PPPoA configuration parameters set on a selected NRP, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Click the PPPoA Configuration tab.

Step 3 Choose a relevant Chassis and NRP.

Step 4 Click Deconfigure to set the parameters on the selected NRP.

PPPoE Configurati on Tab

The PPPoE Configuration tab displays three panels:

PPPoE Virtual Template
PPPoE Address Pool
PPPoE Configuration

The More SSG Configuration tab allows parameters to be set on the NRP-SSG that are prerequisites of the PTA-MD service.

Note Before connecting a subscriber to a PTA-MD service using PPPoE the corresponding parameters on the PPPoE Configuration tab should be configured. For example, the parameters in the PPPoE Virtual Template and PPPoE IP Address Pool panels should be set and configured to connect a subscriber to a PTA-MD service using PPPoE.

To view the PPPoE Configuration tab, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Click the PPPoE Configuration tab. The configuration-related panels (Figure 5-27) appears.

Figure 5-27: SSG Configuration Window—PPPoE Configuration Tab

Step 3 Choose a relevant Chassis and NRP.

The PPPoE Configuration tab displays the following panels.

PPPoE Virtual Template

The PPPoE Virtual Template panel displays the following information:

Authentication Type—Authentication type for any subscribers wanting to connect to this service.
IP Unnumbered Interface—Allows the operator to choose which interface IP to target traffic at.
Compression Type—Compression type used within the virtual template.

PPPoE IP Address Pool

The PPPoE IP Address Pool panel displays the following information:

Higher IP Address—The upper limit on the IP address pool.
Lower IP Address—The lower limit on the IP address pool.

No IP address pool is configured when the Higher IP Address and Lower IP Address parameters are left blank.

PPPoE Configuration

Click Configure to configure the parameters set on the NRP-SSG or click Deconfigure to deconfigure the parameters set on the NRP-SSG.

Configuring PPPoE Configuration

PPPoE Configuration must be carried out before a subscriber can be connected to an NRP using PPPoE. To set the PPPoE configuration parameters onto a selected NRP, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details.

Step 2 Click the PPPoE Configuration tab.

Step 3 Choose a relevant Chassis and NRP.

Step 4 Configure the parameters displayed in the PPPoE Virtual Template and PPPoA IP Address Pool panels.

Step 5 Click Configure to set the parameters on the selected NRP.

Deconfiguring PPPoE Configuration

To deconfigure PPPoE configuration parameters set on a selected NRP, follow these steps:

Step 1 Open the SSG Configuration window. See the "Viewing the SSG Configuration Window" section for further details and click the PPPoE Configuration tab.

Step 2 Choose a relevant Chassis and NRP.

Step 3 Click Deconfigure to set the parameters on the selected NRP.

Cisco 6400 NRP Capacity Statistics Window

The Cisco 6400 NRP Capacity Statistics window displays a single NRP Capacity tab with four panels: Subscriber Connections, Service Instance Uplinks, Multi-Domain Service Connections, and Over-Subscription Management.

Note The Cisco 6400 NRP Capacity Statistics window displays the NRP2 card.

Viewing the Cisco 6400 NRP Capacity Statistics Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > NRP Capacity Statistics option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 NRP Capacity Statistics window.) The Cisco 6400 NRP Capacity Statistics window appears with the NRP Capacity tab displayed (Figure 5-28).

Figure 5-28: Cisco 6400 NRP Capacity Statistics Window—NRP Capacity Tab

NRP Capa city Tab

To view the NRP Capacity tab, follow these steps:

Step 1 Open the Cisco 6400 NRP Management window. See the "Viewing the Cisco 6400 NRP Management Windows" section for further details.

Step 2 The NRP Capacity tab appears by default (see Figure 5-28).

Step 3 Choose the relevant Cisco 6400 Chassis and Cisco 6400 NRP. The NRP capacity information for the selected NRP appears.

The NRP Capacity tab displays the following panels.

Subscriber Connections

The Subscriber Connections panel displays the total number of subscribers connected to the selected NRP or NRP2.

Service Instance Uplinks

The Service Instance Uplinks panel displays the following information:

RFC 1483 Bridging—Displays the number of RFC 1483 Bridging service instance uplinks.
RFC 1483 IRB—Displays the number of RFC 1483 IRB service instance uplinks.
RFC 1483 Routing—Displays the number of RFC 1483 Routing service instance uplinks.
PPPoA-SD—Displays the number of PPPoA-SD service instance uplinks.

Multi-Domain Service Connections

The Multi-Domain Service Connections panel displays the following information:

L2TP—Displays the number of L2TP multidomain service connections.
IP Connection—Displays the number of IP connection multidomain service connections.

Over-Subscription Management

The Over-Subscription Management panel displays the following information:

Total Subscribers PCR—Displays the total peak cell rate for all subscribers whose connections terminate on an NRP.
Total Services PCR—Displays the total peak cell rate for all services deployed on an NRP.
Over-Subscription Factor—Displays the amount by which subscriber PCR exceeds service PCR on an NRP.

Cisco 6400 NRP ATM Port Management Window

The Cisco 6400 NRP ATM Port Management window displays six tabs: Faults, Status, Performance, Configuration, More Configuration, and Inventory.

Note To commission the selected interface port, see the "Commissioning an NRP or NLC Interface Port" section for further details.

Viewing the Cisco 6400 NRP ATM Port Management Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > NRP ATM Port option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 NRP ATM Port Management window.) The Cisco 6400 NRP ATM Port Management window appears with the Faults tab displayed. The Faul ts tab (Figure 5-29) appears by default and has one panel.

Note To Commission the selected NRP ATM Port Interface, see the "Commissioning an NRP or NLC Interface Port" section for further details.

Figure 5-29: Cisco 6400 NRP Window—Faults Tab

Faults Tab

To view the Faults tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. (See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.) The Faults tab appears (see Figure 5-29).

Step 2 Choose a relevant Chassis, NRP, and ATM Port.

The Fault information for the selected ATM port appears.

Errors

The Errors panel (Figure 5-29) displays the following error information:

Transmitted Message Errors—Displays the number of incorrect messages detected on the interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message.
Detected Message Errors—Displays the number of incorrect messages detected on the interface. The incorrect messages counter reflects any sort of incorrect information in a message.
SSCOP Error PDUs—Displays the sum of invalid PDUs plus the PDUs that result in MAA error codes and are discarded.
Invalid PDUs are defined in SSCOP and consist of:
- PDUs with incorrect length (MAA-ERROR code U)
- Undefined PDU type code
- PDUs that are not 32-bit aligned

Status Tab

The status information for the selected ATM Port appears. To view the Status tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.

Step 2 Click the Status tab (Figure 5-30).

Figure 5-30: Cisco 6400 NRP ATM Port Management Window—Status Tab

Step 3 Choose a relevant Chassis, NRP, and ATM Port.

The Status tab displays the following panels:

ATM Port Status

The ATM Port Status panel displays the following information:

Receive LED Status—Displays the receive LED color of the port. It can be one of the following: off, steadyGreen, steadyYellow, steadyRed, flashGreen, flashYellow, or flashRed.
Transmit LED Status—Displays the transmit LED color of the port. It can be one of the following: off, steadyGreen, steadyYellow, steadyRed, flashGreen, flashYellow, or flashRed.
Soft VC Destination Address—Displays the 20-byte ATM address of the destination ATM interface for soft ATM PVC/PVP.

Capacity Status

The Capacity Status panel displays the following information:

Total Connections—Displays the total number of existing connections at the interface.
Configured VP Interfaces—Displays the number of configured VP interfaces at the physical interface.
Number of VPCs—Displays the number of VPCs (PVCs and SVCs) configured for use at the ATM interface. At the ATM UNI, the configured number of VPCs (PVCs and SVCs) can range from 0 to 256 only.
Active SVPs—Displays the number of active switched virtual paths at the interface.
Number of PVPs—Displays the number of permanent virtual paths at the interface.
SVC Minimum VCI—Displays the minimum of the range of values from which VCIs are assigned to new SVC connections. When the value is larger, more VCIs are reserved for setting up PVCs. It applies to every VPI of the physical interface and every logical port.
Number of VCCs—Displays the number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
Active SVCs—Displays the number of active switched virtual channels at the interface.
Number of PVCs—Displays the number of permanent virtual channels at the interface.

Performance Tab

The Performance tab is divided into four panels: Transmitted, Connections Established, Detected, and SSCOP.

To view the Performance tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.

Step 2 Click the Performance tab (Figure 5-31).

Figure 5-31: Cisco 6400 NRP ATM Port Management Window—Performance Tab

Step 3 Choose a relevant Chassis, NRP, and ATM Port.

The Performance tab displays the following panels:

Transmitted

The Transmitted panel displays the following information:

Restarts—Displays the number of restart activity errors transmitted from the interface. The restart activity counter provides a count of host, switch, or network restart activity. The counter is incremented when transmitting a RESTART message.
Unavailable Routes—Displays the number of route unavailability messages transmitted from the interface. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is transmitted. (Cause values apply to both UNI 3.0 and UNI 3.1). Table 5-14 lists the codes.

Table 5-14: Unavailable Routes Cause Code Values

Cause Value	Meaning
1	Unallocated (unassigned) number
1	No route to specified transit network
3	No route to destination

Note RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value are redundant (for counting purposes) and should not be counted for the counter.

Unavailable Resources—Displays the number of Resource Unavailability conditions transmitted from the interface. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-15 lists the codes.

Table 5-15: Unavailable Resources Cause Code Values

Cause Value	Meaning
17	User busy
18	No user responding
21	Call rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Calling Party Events—Displays the number of Calling Party Events conditions transmitted from the interface. The counter monitors error events that occur due to the originating user doing something wrong. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is transmitted. Table 5-16 lists the codes.

Table 5-16: Calling Parity Events Cause Code Values

Cause Value	Meaning
28	Invalid number format (address incomplete)
43	Access information discarded
57	Bearer capability not authorized
65	Bearer capability not implemented
73	Unsupported combination of traffic parameters
78	AAL parameters cannot be supported (UNI 3.1 only)
91	Invalid transit network selection
93	AAL parameters cannot be supported (UNI 3.0 only)

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Called Party Events—Displays the number of Called Party Responsible For Unsuccessful Call conditions transmitted from the interface. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is transmitted. Table 5-17 lists the codes.

Table 5-17: Called Party Events Cause Code Values

Cause Value	Meaning
17	User busy
18	No user responding
21	All rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Timer Expires—Displays the number of Timer Expires conditions transmitted from the interface. The Timer Expires counter provides a count of network timer expirations and some switch timer expires counts. The conditions for incrementing the Timer Expires counter are:
- Expiration of any network timer
- Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, "recovery on timer expires."
Setup attempts—Displays the number of call setup attempts (both successful and unsuccessful) transmitted on the interface.
Number of Cells—Displays the number of cells transmitted on the interface, including p2p and p2mp cells.

Bandwidth Utilization—Displays the utilized bandwidth as a percentage of the maximum bandwidth supported by the port.

Note Receive and Transmit Utilization gauges are displayed from a subscriber's point of view; that is, the Transmit Utilization value shows the number of cells per second the subscriber is transmitting and the Receive Utilization value shows the number of cells per second the subscriber is receiving.

Connection Established

The Connections Established panel displays the following performance information:

Incoming—Displays the number of SVC VCCs established at the signaling entity for incoming connections.
Outgoing—Displays the number of SVC VCCs established at the signaling entity for outgoing connections.

Detected

The Detected panel displays the following performance information:

Restarts—Displays the number of Restart Activity errors detected on the interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. The counter is incremented when receiving a RESTART message.
Unavailable Routes—Displays the number of Route Unavailability conditions detected on the interface. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-18 lists the codes.

Table 5-18: Unavailable Routes Cause Codes

Cause Value	Meaning
1	Unallocated (unassigned) number
1	No route to specified transit network
3	No route to destination
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Unavailable Resources—Displays the number of Resource Unavailability conditions detected on the interface. The Unavailable Resources counter incremented is when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-19 lists the codes.

Table 5-19: Unavailable Resources Cause Codes

Cause Value	Meaning
35	Requested VPCI/VCI not available
37	User cell rate not available (UNI 3.1 only)
38	Network out of order
41	Temporary failure
45	No VPCI/VCI available
47	Resource unavailable, unspecified
49	Quality of Service unavailable
51	User cell rate not available (UNI 3.0 only)
58	Bearer capability not presently available
63	Service or option not available, unspecified
92	Too many pending add party requests

Note Cause values apply to both UNI 3.0 and UNI 3.1 unless otherwise stated.

Calling Party Events—Number of Calling Party Events conditions detected on the interface. The counter monitors error events that occur due to the originating user doing something wrong. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-20 lists the codes.

Table 5-20: Calling Party Events Cause Codes

Cause Value	Meaning
28	Invalid number format (address incomplete)
43	Access information discarded
57	Bearer capability not authorized
65	Bearer capability not implemented
73	Unsupported combination of traffic parameters
78	AAL parameters cannot be supported (UNI 3.1 only)
91	Invalid transit network selection
93	AAL parameters cannot be supported (UNI 3.0 only)

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Called Party Events—Displays the number of Called Party Responsible For Unsuccessful Call conditions detected on the interface. The counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received:

Table 5-21: Called Party Events Cause Codes

Cause Value	Meaning
17	User busy
18	No user responding
21	All rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Timer Expires—Displays the number of Timer Expires conditions detected on the interface. The Timer Expires counter provides a count of network timer expirations and some host or switch timer expires counts. The conditions for incrementing the counter are:
- Expiration of any network timer
- Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, "recovery on timer expires."
Setup Attempts—Displays the number of call setup attempts (both successful and unsuccessful) detected on the interface.
Number of Cells—Number of cells received on the interface, including p2p and p2mp cells.

SSCOP

The SSCOP section of the Performance tab allows you to view the following performance information:

Connection Event—Displays the SSCOP Connection Events Counter. The counter counts the sum of the following errors:
- SSCOP Connection Disconnect Counter—The abnormal occurrence of the event is characterized by the expiration counts of Timer_NO_RESPONSE. (The event is communicated to the layer management with MAA-ERROR code P. Refer to ITU-T Q.2110 [13].)
- SSCOP Connection Initiation Failure—Indicates the inability to establish an SSCOP connection. The event occurs whenever the number of connection control timer expires count (Timer_CC) exceeds MaxCC or upon receipt of a connection reject message, BGREJ PDU. (The event is communicated to layer management with MAA-ERROR code O. Refer to ITU-T Q.2110.)
- SSCOP Connection Re-Establ or Resynch—Occurs upon receipt of a BGN PDU or RESYNC PDU message.

Configuration Tab

The Configuration tab is divided into two panels: ATM Port Configuration and ILMI Configuration. To view the Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.

Step 2 Click the Configuration tab (Figure 5-32).

Figure 5-32: Cisco 6400 NRP ATM Port Management Window—Configuration Tab

Step 3 Choose a relevant Chassis, NRP, and ATM Port. The configuration information for the selected ATM port appears.

Step 4 Configure the information displayed.

Step 5 Save the changes.

ATM Port Configuration

The ATM Port Configuration panel allows you to configure the following information:

Neighbor IP Address—Allows you to specify the IP address of the neighbor system connected to the far end of the interface, to which a Network Management Station can send SNMP messages as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system.
Neighbor Interface Name—Allows you to specify the textual name of the interface on the neighbor system on the far end of the interface, and to which the interface connects. When the neighbor system is manageable through SNMP and supports the object ifName, the value of the object must be identical with that of ifName for the ifEntry of the lowest level physical interface for the port. When the interface does not have a textual name, the value of the object is a zero length string. Note that the value of the object might be obtained in different ways, for example, by manual configuration or through ILMI interaction with the neighbor system.
Maximum VCCs—Allows you to specify the maximum number of VCCs (PVCs and SVCs) supported at the ATM interface.
Maximum VPCs—Allows you to specify the maximum number of VPCs (PVCs and SVCs) supported at the ATM interface. At the ATM UNI, the maximum number of VPCs (PVCs and SVCs) ranges from 0 to 256 only.
Max Active VPI Bits—Allows you to specify the maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum number of active VPI bits configured for use ranges from 0 to 8 only.
Max Active VCI Bits—Allows you to specify the maximum number of active VCI bits configured for use at the ATM interface.
UNI Signaling Version—Allows you to specify the version of UNI signaling that is currently being used on the interface. You can set the UNI Signaling Version to:
- ATMF UNI 3.0, ATM FUNI 3.1 or ATMF UNI 4.0—Used when the interface is an UNI or IISP interface.
Not Applicable—Used when the interface is a PNNI interface or when signaling is disabled. It might reflect a manually configured value for the signaling version, or might be determined by other means such as auto-configuration.
UNI Type—Allows you to specify the type of User to Network Interface (UNI). You can set the UNI Type to public or private.
Well-known VC Mode—Allows you to specify whether well-known VCs should be automatically or manually created for the interface. You can set the Well-known VC Mode to:
- Automatic—In automatic mode, well-known VCs are created with default VPI/VCI values upon startup or upon entry to the automatic mode. In Automatic mode, well-known VCs are not allowed to be deleted or modified by user commands. Automatic mode is the default mode at startup for equipment which supports automatic well-known VC creation.
- Manual—In manual mode, well-known VCs won't be automatically created. Instead you can delete and create PVCs with the reserved encapsulation types aalQsAal, aal5Ilmi, and aal5Pnni as applicable. PVCs are allowed to have VCI values in the range 5 to 16383, instead of 32 to 16383.
Manual Delete Upon Entry—The Manual Delete Upon Entry action causes any existing VCs with reserved encapsulation types (aalQsAal, aal5Ilmi or aal5Pnni) to be deleted for the interface as it enters the manual state.
ATM Interface Side—Allows you to specify the side of ATM interface. You can set the ATM Interface Side to either a User or Network side or Not Applicable. A Not Applicable value implies that Interface Type is other than uni or iisp.
Signaling Admin Status—Allows you to Enable or Disable signaling or sscop on the interface. You can set the Signaling Admin Status option to:
- Enabled—Signaling or sscop on the interface is enabled.
- Disabled—Signaling or sscop on the interface is disabled.

SVC UPC Intent—Allows you to specify the policing (Usage Parameter Control or UPC) action to take for SVCs established through the interface. You can set the SVC UPC Intent option to Passing, Tagging or Dropping.

Note Values other than passing are allowed only when policing is supported on the interface. The SVC UPC Intent also serves to determine which UPC to use on the terminating (destination) half-leg of Soft PVCs. For the CPU interface or logical ports on the LS1010, only the "passing" value is supported.

Interface Type—Allows you to specify the type of ATM interface. You can set the Interface Type to Other, UNI (User to Network), PNNI, IISP, or NNI PVC Only.

ILMI Configuration

The ILMI Configuration panel allows you to configure the following information:

ILIM VCI Value—Allows you to specify the VCI value of the VCC supporting the ILMI at the ATM interface. When the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at the ATM interface.
ILMI VPI Value—Allows you to specify the VPI value of the VCC supporting the ILMI at the ATM interface. When the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at the ATM interface.
ILMI Keepalive Time—Allows you to specify the amount of time that should elapse between successive ILMI See messages sent on the interface. A value of 0 disables ILMI keepalive messages on the interface.
ILMI Auto-Configuration—Allows you to Enable or Disable the ILMI link and interface type determination. You can set the ILMI Auto-Configuration option to:
- Enabled—ILMI link and interface type determination on the interface is enabled.
- Disabled—ILMI link and interface type determination on the interface is disabled.

ILMI Configuration—Allows you to Enable or Disable ILMI configuration on the interface.

Enabled—ILMI configuration on the interface is enabled.

Disabled—ILMI configuration on the interface is disabled.

Note The configuration takes effect only on the next interface restart. Disabling the ILMI Configuration will also disable atmIfIlmiAddressRegistration and atmIfIlmiAutoConfiguration and atmIfIlmiKeepAlive.

ILMI Address Registration—Allows you to Enable or Disable the ILMI Address Registration on the interface.
- Enabled—ILMI Address Registration on the interface is enabled.
- Disabled—ILMI Address Registration on the interface is disabled.

More Configuration Tab

The More Configuration tab (Figure 5-33) is divided into two panels: Information Element Transfer, and Actions.

Note To commission the selected interface port, see the "Commissioning an NRP or NLC Interface Port" section for further details.

To view the More Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.

Step 2 Click the More Configuration tab (Figure 5-33).

Figure 5-33: Cisco 6400 NRP ATM Port Management Window

Step 3 Choose a relevant Chassis, NRP, and ATM Port. The configuration information for the selected ATM port appears (Figure 5-33).

Step 4 Change the information as required.

Step 5 Save the changes.

Information Element Transfer

The Information Element Transfer panel allows you to configure the following information:

Broadband High Layer—Allows you to specify whether to accept, transfer, and deliver the Broadband High Layer Information Element from the calling party to the called party. You can set the Broadband High Layer to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Called Party Subnet Address—This parameter is required for ATM systems that support only a value of "disabled" (that is, the ATM systems does not support the feature associated with the parameter).
Calling Party Number—Allows you to specify whether the Calling Party Number Information Element is transferred to the called party address. You can set the Calling Party Number to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Unknown—Allows you to specify whether to accept, transfer, and deliver the unknown Information Element from the calling party to the called party, when the IE instruction field flag is set to zero. You can set the Unknown option to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element is not transferred to the called party.
Broadband Repeat Indicator—The Broadband Repeat Indicator is required for ATM systems that support only a value of "disabled" (that is, the ATM systems does not support the feature associated with the parameter).
Calling Party Subnet Address—Allows you to specify whether to accept and transfer the Calling Party Subaddress Information Element from the calling party to the called party. You can set the Calling Party Subnet Address to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
ATM Adaption Layer Parameters—Allows you to specify whether to accept, transfer, and deliver the ATM Adaptation Layer Parameters Information Element from the calling party to the called party. You can set the ATM Adaption Layer Parameters option to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Broadband Low Layer—This parameter is required for ATM systems that support only a value of "disabled" (that is, the ATM systems does not support the feature associated with the parameter).

Inventory Tab

The Inventory tab displays a single panel. To view the Inventory tab, follow these steps:

Step 1 Open the Cisco 6400 NRP ATM Port Management window. See the "Viewing the Cisco 6400 NRP ATM Port Management Window" section for further details.

Step 2 Click the Inventory tab. The Cisco 6400 NRP ATM Port Management window (Figure 5-34) appears.

Figure 5-34: Cisco 6400 NRP ATM Port Management Window—Inventory Tab

Step 3 Choose a relevant Chassis, NRP, and ATM Port.

The Inventory information displays for the selected ATM Port.

Inventory

The Inventory panel displays the following information:

Admin Address—Displays the address assigned for administrative purposes, for example, an address associated with the service provider side of a public network UNI. When the interface has no assigned administrative address, or when the address used for administrative purposes is the same as that used for ifPhysAddress, then the Admin Address is an octet string of zero length.
ATM Address Type—Displays the type of primary ATM address configured for use at the ATM interface.
Physical Port Type—Displays the type of physical layer medium on the port.

Cisco 6400 Line Card Management Window

The Cisco 6400 Line Card Management window displays a single Line Card tab. The Cisco 6400 SCM supports OC-3, OC-12, and DS3 line modules.

Note To commission a selected NLC, see the "Commissioning an NSP, NRP, NRP2, or NLC Module" section for further details.

Viewing the Cisco 6400 Line Card Management Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Manage > NLC option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 Line Card Management window.) The Cisco 6400 Line Card Management window (Figure 5-35) appears with the Line Card tab displayed. The Line Card tab is divided into four panels: Status, Configuration, Inventory, and Actions.

Figure 5-35: Cisco 6400 Line Card Management Window—Line Card Tab

Line Card Tab

To view the Line Card tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card Management window. See the "Viewing the Cisco 6400 Line Card Management Window" section for further details.

Step 2 Choose a relevant Chassis and Line Card. Status information for the selected NLC appears.

The Line Card tab displays the Status, Configuration, and Inventory panels.

Status

The Status panel displays the operational status of the NLC.

Configuration

The Configuration panel allows you to configure administration information.

The Administration Status option allows you to enable, disable, or reset the module. You can set the Administration Status option to:

Reset—Reset the module's control logic.
Enable—Enable the module.
Disable—Disable the module.

Inventory

The Inventory panel displays the following information:

Module Type—Displays the module type of the selected NLC.
Serial Number—Displays the serial number of the submodule.
Max Supported Ports—Displays the maximum number of ports supported by the submodule.
Hardware Version (major)—Displays the major hardware version of the submodule. Together with ciscoLS1010SubModuleHwVersionMinor, this completely specifies the hardware version of the submodule.
Hardware Version (minor)—Displays the minor hardware version of the submodule. Together with ciscoLS1010SubModuleHwVersion, this completely specifies the hardware version of the submodule.
Software Version—Displays the current software version number.

Cisco 6400 Line Card ATM Port Management Window

The Cisco 6400 Line Card ATM Port Management window displays six tabs: Faults, Status, Performance, Configuration, More Configuration, and Inventory.

Note To commission the selected NLC ATM Port Interface, see the "Commissioning an NRP or NLC Interface Port" section for further details.

Viewing the Cisco 6400 Line Card ATM Port Management Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > NLC ATM Port option. (See Table 5-1 for information on which objects allow you to launch the Cisco 6400 Line Card ATM Port Management window.) The Cisco 6400 Line Card ATM Port Management window (Figure 5-36) appears with the Faults tab displayed.

Note To commission the selected NLC ATM Port Interface, see the "Commissioning an NRP or NLC Interface Port" section for further details.

Figure 5-36: Cisco 6400 Line Card ATM Port Management Window—Faults Tab

Faults Tab

To view the Faults tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window. (See the "Viewing the Cisco 6400 Line Card ATM Port Management Window" section for further details.) The Faults tab appears.

Step 2 Choose a relevant Chassis, Line Card, and ATM Port. The fault information for the selected ATM port appears (Figure 5-36).

The Faults tab displays the following panels:

Errors
SONET Frame Errors
DS1/E1?ds3/E3 Errors

Errors

The Errors panel displays the following error information:

Transmitted Message Errors—Displays the number of Incorrect Messages detected on the interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message.
Detected Message Errors—Displays the number of Incorrect Messages detected on the interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message.
SSCOP Error PDUs—Displays the sum of invalid PDUs plus the PDUs that result in MAA error codes and are discarded.
Invalid PDUs are defined in SSCOP and consist of:
- PDUs with incorrect length (MAA-ERROR code U)
- Undefined PDU type code
- PDUs that are not 32-bit aligned

SONET Frame Errors

The SONET Frame Errors panel displays the following error information:

Path FEBE Errors—Displays the number of G1 (Path FEBE) errors on the physical interface. This object is only present for SONET interfaces.
Line FEBE Errors—Displays the number of Z2 (Line FEBE) errors on the physical interface. This object is only present for SONET interfaces.
Path Parity Errors—Displays the number of B3 (BIP) errors on the physical interface. This object is only present for SONET interfaces.
Line Parity Errors—Displays the number of B2 (BIP) errors on the physical interface. This object is only present for SONET interfaces.
Section Parity Errors—Displays the number of B1 (BIP) errors on the physical interface. This object is only present for SONET interfaces.

DS1/E1/DS3/E3 Errors

The DS1/E1/DS3/E3 Errors panel displays the following error information:

LCV Errors—Displays the number of CRC errors (in CRC-4 mode) on the physical interface. This object is only present for E1 interfaces.
C-Bit Parity Errors—Displays the number of C-bit parity violations on the physical interface. This object is only present for DS3 interfaces.
P-bit Parity Errors—Displays the number of P-bit parity violations or E3 G.832 BIP-8 errors on the physical interface. This object is present only for DS3/E3 interfaces.
PLCP BIP Violations—Displays the number of PLCP BIP violations on the physical interface. This object is only present for DS3/E3/DS1/E1 interfaces.
E1 CRC Errors—Displays the number of bit errors (CRC-6 error in ESF mode and framing bit error in SF mode) on the physical interface. This object is only present for DS1 interfaces.
DS1 Bit Errors—Displays the number of Line Code Violation errors on the physical interface. This object is only present for DS3/E3/DS1/E1 interfaces.

Status Tab

The Status tab is divided into three panels: ATM Port Status, Capacity Status, and Physical Layer Status. To view the Status tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window.

Step 2 Click the Status tab. The Status panels (Figure 5-37) appear.

Figure 5-37: Cisco 6400 Line Card ATM Port Management Window—Status Tab

Step 3 Choose a relevant Chassis, Line Card, and ATM Port. The status information for the selected ATM port appears.

ATM Port Status

The ATM Port Status section displays the following status information:

Receive LED Status—Displays the receive LED color of the port. It can be off, steadyGreen, steadyYellow, steadyRed, flashGreen, flashYellow, or flashRed.
Soft VC Destination Address—Displays the 20-byte ATM address of the destination ATM interface for soft ATM PVC/PVP.
Transmit LED Status—Displays the transmit LED color of the port. It can be off, steadyGreen, steadyYellow, steadyRed, flashGreen, flashYellow, or flashRed.

Capacity Status

The Capacity Status section displays the following information:

Total Connections—Displays the total number of existing connections at the interface.
Configured VP Interfaces—Displays the number of configured VP interfaces at the physical interface.
Number of VPCs—Displays the number of VPCs (PVCs and SVCs) configured for use at the ATM interface. At the ATM UNI, the configured number of VPCs (PVCs and SVCs) can range from 0 to 256 only.
Active SVPs—Displays the number of active switched virtual paths at the interface.
Number of PVPs—Displays the number of permanent virtual paths at the interface.
SVC Minimum VCI—Displays the minimum of the range of values from which VCIs are assigned to new SVC connections. When the SVC Minimum VCI value is larger, more VCIs are reserved for setting up PVCs. The SVC Minimum VCI value applies to every VPI of the physical interface and every logical port.
Number of VCCs—Displays the number of VCCs (PVCs and SVCs) configured for use at the ATM interface.
Active SVCs—Displays the number of active switched virtual channels at the interface.
Number of PVCs—Displays the number of permanent virtual channels at the interface.

Physical Layer

The Physical Layer Status panel displays the following status information:

Physical Interface Status—Displays the status of the physical interface. The value of the object is only valid when the interface's ifAdminStatus has the value "up'". Note that some of the enumerated values are specific to a particular physical layer. You will see: normal, los, lof, loc, ais, yellowLine, yellowPath, lop, idle, yellowAlarm, plcpLOF, plcpYellow, maFERF, pathAis or ocd.
Clock Source Status—Displays the network clock source status of the interface:
- notSelected—Not selected as the network clock source.
- selected—Selected as the network clock source.

Performance Tab

The Performance tab (Figure 5-38) is divided into four panels: Transmitted, Connections Established, Detected, and SSCOP. To view the Performance tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window.

Step 2 Click the Performance tab. The performance-related panels (Figure 5-38) appear.

Figure 5-38: Cisco 6400 Line Card ATM Port Management Window—Performance Tab

Step 3 Choose a relevant Chassis, Line Card, and ATM Port. The performance information for the selected ATM port appears.

Transmitted

The Transmitted panel displays the following performance information:

Restarts—Displays the number of Restart Activity errors transmitted from the interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. The Restarts counter is incremented when transmitting a RESTART message.
Unavailable Routes—Displays the number of Restart Activity errors transmitted from the interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. The Unavailable Routes counter is incremented when transmitting a RESTART message.
Unavailable Resources—Displays the number of Resource Unavailability transmitted from the interface. The Unavailable Resources counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-22 lists the codes.

Table 5-22: Unavailable Resources Cause Codes

Cause Value	Meaning
17	User busy
18	No user responding
21	Call rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Called Party Events—Displays the number of Called Party Responsible For Unsuccessful Call transmitted from the interface. The Called Party Events counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is transmitted. Table 5-23 lists the codes.

Table 5-23: Called Party Events Cause Codes

Cause Value	Meaning
17	User busy
18	No user responding
21	All rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Calling Party Events—Displays the number of Calling Party Events transmitted from the interface. The Calling Party Events counter monitors error events that occur due to the originating user doing something wrong. The Calling Party Events counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is transmitted. Table 5-24 lists the codes.

Table 5-24: Calling Party Events Cause Codes

Cause Value	Meaning
28	Invalid number format (address incomplete)
43	Access information discarded
57	Bearer capability not authorized
65	Bearer capability not implemented
73	Unsupported combination of traffic parameters
78	AAL parameters cannot be supported (UNI 3.1 only)
91	Invalid transit network selection
93	AAL parameters cannot be supported (UNI 3.0 only)

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Timer Expires—Displays the number of Timer Expires conditions transmitted from the interface. The Timer Expires counter provides a count of network timer expirations and some host or switch timer expires counts. The conditions for incrementing the Timer Expires counter are:

Expiration of any network timer—Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, "recovery on timer expires."
Setup attempts—Displays the number of call setup attempts (both successful and unsuccessful) transmitted on this interface.
Number of Cells—Displays the number of cells transmitted on the interface, including p2p and p2mp cells.

Bandwidth Utilization—Displays the utilized bandwidth as a percentage of the maximum bandwidth supported by the port.

Connection Established

The Connections Established panel displays the following performance information:

Incoming—Displays the number of SVC VCCs established at the signaling entity for incoming connections.
Outgoing—Displays the number of SVC VCCs established at the signaling entity for outgoing connections.

Detected

The Detected panel displays the following performance information:

Restarts—Displays the number of Restart Activity errors detected on the interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. The Restarts counter is incremented when receiving a RESTART message.
Unavailable Routes—Displays the number of Route Unavailability conditions detected on the interface. The Unavailable Routes counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-25 lists the codes.

Table 5-25: Unavailable Routes Cause Codes

Cause Value	Meaning
1	Unallocated (unassigned) number
1	No route to specified transit network
3	No route to destination
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Unavailable Resources—Displays the number of Resource Unavailability conditions detected on the interface. The Unavailable Resources counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-26 lists the codes.

Table 5-26: Unavailable Resources Cause Codes

Cause Value	Meaning
35	Requested VPCI/VCI not available
37	User cell rate not available (UNI 3.1 only)
38	Network out of order
41	Temporary failure
45	No VPCI/VCI available
47	Resource unavailable, unspecified
49	Quality of service unavailable
51	User cell rate not available (UNI 3.0 only)
58	Bearer capability not currently available
63	Service or option not available, unspecified
92	Too many pending add party requests

Note Cause values apply to both UNI 3.0 and UNI 3.1 unless otherwise stated.

Called Party Events—Displays the number of Called Party Responsible For Unsuccessful Call conditions detected on the interface. The Called Party Events counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-27 lists the codes.
Table 5-27: Called Party Events Cause Codes

Cause Value	Meaning
17	User busy
18	No user responding
21	All rejected
22	Number changed
23	User rejects all calls with calling line ID restriction (CLIR)
27	Destination out of order
31	Normal, unspecified
88	Incompatible destination

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Calling Party Events—Number of Calling Party Events conditions detected on the interface. The Calling Party Events counter monitors error events that occur due to the originating user making an error. The Calling Party Events counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains a cause code value is received. Table 5-28 lists the codes.

Table 5-28: Calling Parity Events Cause Codes

Cause Value	Meaning
28	Invalid number format (address incomplete)
43	Access information discarded
57	Bearer capability not authorized
65	Bearer capability not implemented
73	Unsupported combination of traffic parameters
78	AAL parameters cannot be supported (UNI 3.1 only)
91	Invalid transit network selection
93	AAL parameters cannot be supported (UNI 3.0 only)

Note Cause values apply to both UNI 3.0 and UNI 3.1.

Timer Expires—Displays the number of Timer Expires conditions detected on the interface. The Timer Expires Counter provides a count of network timer expirations and some host or switch timer expires counts. The conditions for incrementing the Timer Expires counter are:
- Expiration of any network timer.
- Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, "recovery on timer expires."
Setup attempts—Displays the number of call setup attempts (both successful and unsuccessful) detected on the interface.
Number of Cells—Number of cells received of the interface, including p2p and p2mp cells.

Bandwidth Utilization—Displays the utilized bandwidth as a percentage of the maximum bandwidth supported by the port.

Note Receive or Transmit Utilization gauges are displayed from a subscriber's point of view; that is, the Transmit Utilization value shows the number of cells per second that the subscriber is transmitting and the Receive Utilization value shows the number of cells per second that the subscriber is receiving.

SSCOP

The SSCOP panel displays the following performance information:

Connection Event—SSCOP Connection Events Counter. The Connection Event counter counts the sum of the following errors:
- SSCOP Connection Disconnect Counter—The abnormal occurrence of the event is characterized by the expiration of Timer_NO_RESPONSE. (The event is communicated to the layer management with MAA-ERROR code P. Refer to ITU-T Q.2110 [13].)
- SSCOP Connection Initiation Failure—Condition indicates the inability to establish an SSCOP connection. The event occurs whenever the number of the connection control timer expires count (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message, BGREJ PDU. (The event is communicated to layer management with MAA-ERROR code O. Refer to ITU-T Q.2110.)
- SSCOP Connection Re-Establ or Resynch—The SSCOP Connection Re-Establ or Resynch event occurs upon receipt of a BGN PDU or RESYNC PDU message.

Configuration Tab

The Configuration tab (Figure 5-39) is divided into two panels: ATM Port Configuration and ILMI Configuration.

Note To Commission the selected NRP ATM Port Interface, see the "Commissioning an NRP or NLC Interface Port" section for further details.

To view the Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window.

Step 2 Click the Configuration tab. The configuration-related panels (Figure 5-39) appear.

Figure 5-39: Cisco 6400 Line Card ATM Port Management Window—Configuration Tab

Step 3 Choose a relevant Chassis, Line Card, and ATM Port. The configuration information for the selected ATM port appears.

Step 4 Change the information using the dropdown lists. See the following sections for more information.

ATM Port Configuration

The ATM Port Configuration panel allows you to configure the following information:

Neighbor IP Address—Allows you to specify the IP address of the neighbor system connected to the far end of the interface, to which a Network Management Station can send SNMP messages as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system.
Neighbor Interface Name—Allows you to specify the textual name of the interface on the neighbor system on the far end of the interface to which the interface connects. When the neighbor system is manageable through SNMP and supports the object ifName, the value of the object must be identical with that of ifName for the ifEntry of the lowest-level physical interface for the port. When the interface does not have a textual name, the value of the object is a zero-length string. Note that the value of the object can be obtained in different ways; for example, by manual configuration or through ILMI interaction with the neighbor system.
Maximum VCCs—Allows you to specify the maximum number of VCCs (PVCs and SVCs) supported at the ATM interface.
Maximum VPCs—Allows you to specify the maximum number of VPCs (PVCs and SVCs) supported at the ATM interface. At the ATM UNI, the maximum number of VPCs (PVCs and SVCs) ranges from 0 to 256 only.
Max Active VPI Bits—Allows you to specify the maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum number of active VPI bits configured for use ranges from 0 to 8 only.
Max Active VCI Bits—Allows you to specify the maximum number of active VCI bits configured for use at the ATM interface.

UNI Signaling Version—Allows you to specify the version of UNI signaling that is currently being used on the interface. You can set the UNI signaling Version to:

ATMF UNI 3.0, ATMF UNI 3.1, or ATM UNI 4.0—Used when the interface is a UNI or IISP interface.

Not Applicable—Used when the interface is a PNNI interface or when signaling is disabled. Not Applicable can reflect a manually configured value for the signaling version, or can be determined by other means such as auto-configuration.

Note Setting UNI Signaling Version to a value of Not Applicable is not allowed. To modify the ciscoAtmIfUniSignalingVersion, ifAdminStatus has to be down and atmIfIlmiAutoConfiguration disabled.

UNI Type—Allows you to specify the type of User to Network interface. You can set the UNI Type to public or private.
Well-known VC Mode—Allows you to specify whether well-known VCs should be automatically or manually created for the interface. You can set the UNI Type to:
- Automatic—In automatic mode, well-known VCs are created with default VPI/VCI values upon startup or upon entry to the automatic mode. While in this mode, well-known VCs are not allowed to be deleted or modified by user commands. This is the default mode at startup for equipment which supports automatic well-known VC creation.
- Manual—In manual mode, well-known VCs are not created automatically. Instead you can delete and create PVCs with the reserved encapsulation types aalQsAal, aal5Ilmi, and aal5Pnni as applicable. PVCs are allowed to have VCI values in the range 5 to 16383, instead of 32 to 16383.
Manual Delete Upon Entry—The Manual DeleteUponEntry action causes any existing VCs with reserved encapsulation types (aalQsAal, aal5Ilmi, or aal5Pnni) to be deleted for this interface as it enters the manual state.
ATM Interface Side—Allows you to specify the side of ATM interface. You can set the ATM Interface Side to either a user or network side or Not Applicable. A Not Applicable value implies that the Interface Type is other than uni or iisp.
Signaling Admin Status—Allows you to enable or disable signaling or SSCOP on this interface. You can set Signaling Admin Status to:
- Enabled—Signaling or SSCOP on this interface is enabled.
- Disabled—Signaling or SSCOP on this interface is disabled.

SVC UPC Intent—Allows you to specify the policing (Usage Parameter Control or UPC) action to take for SVCs established through this interface. You can set this option to Passing, Tagging, or Dropping.

Note Values other than Passing are allowed only when policing is supported on the interface. This also serves to determine which UPC to use on the terminating (destination) half-leg of Soft PVCs. For the CPU interface or logical ports on the LS1010, only the Passing value is supported.

Interface Type—Allows you to specify the type of ATM interface. You can set the Interface Type to UNI (User to Network), PNNI, IISP, or NNI PVC only.

ILMI Configuration

The ILMI Configuration panel allows you to configure the following information:

ILIM VCI Value—Allows you to specify the VCI value of the VCC supporting the ILMI at this ATM interface. When the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero, then the ILMI is not supported at this ATM interface.
ILMI VPI Value—Allows you to specify the VPI value of the VCC supporting the ILMI at this ATM interface. When the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero, then the ILMI is not supported at this ATM interface.
ILMI Keepalive Time—Allows you to specify the amount of time that should elapse between successive ILMI keepalive messages sent on this interface. A value of 0 disables ILMI keepalive messages on this interface.
ILMI Auto-Configuration—Allows you to enable or disable the ILMI link and interface type determination. You can set ILMI Auto-Configuration to:
- Enabled—ILMI link and interface type determination on this interface is enabled.
- Disabled—ILMI link and interface type determination on this interface is disabled.

ILMI Configuration—Allows you to enable or disable ILMI configuration on this interface.

Enabled—ILMI configuration on this interface is enabled.

Disabled—ILMI configuration on this interface is disabled.

Note The configuration takes effect only on the next interface restart. Disabling this object also disables atmIfIlmiAddressRegistration and atmIfIlmiAutoConfiguration and atmIfIlmiKeepAlive.

ILMI Address Registration—Allows you to enable or disable ILMI Address Registration on this interface.
- Enabled—ILMI Address Registration on this interface is enabled.
- Disabled—ILMI Address Registration on this interface is disabled.

Step 5 Save the changes.

More Configuration Tab

The More Configuration tab (Figure 5-40) is divided into four panels: Information Element Transfer, Actions, General Physical Layer Configuration, and DS1/E1/DS3/E3 Physical Layer Configuration.

Note To commission the selected NRP ATM Port Interface, see the "Commissioning an NRP or NLC Interface Port" section for further details.

To view the More Configuration tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window.

Step 2 Click the More Configuration tab. The configuration-related panels (Figure 5-40) appear.

Figure 5-40: Cisco 6400 Line Card ATM Port Management Window—More Configuration Tab

Step 3 Choose a relevant Chassis, Line Card, and ATM Port. The configuration information for the selected ATM port appears.

Information Element Transfer

The Information Element Transfer panel allows you to configure the following information:

Broadband High Layer—Allows you to specify whether to accept, transfer, and deliver the Broadband High Layer Information Element from the calling party to the called party. You can set the Broadband High Layer option to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Called Party Subnet Address—Required for ATM systems that support only a value of "disabled" (that is, the ATM system does not support the feature associated with the parameter).
Calling Party Number—Allows you to specify whether the Calling Party Number Information Element is transferred to the called party address. You can set the Calling Party Number to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Unknown—Allows you to specify whether to accept, transfer and deliver the unknown Information Element from the calling party to the called party, when the IE instruction field flag is set to zero. You can set the Unknown option to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Broadband Repeat Indicator—Required for ATM systems that support only a value of "disabled" (that is, the ATM system does not support the feature associated with the parameter).
Calling Party Subnet Address—Allows you to specify whether to accept and transfer the Calling Party Subaddress Information Element from the calling party to the called party. You can set the Calling Party Subnet Address to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
ATM Adaptation Layer Parameters—Allows you to specify whether to accept, transfer, and deliver the ATM Adaptation Layer Parameters Information Element from the calling party to the called party. You can set the ATM Adaptation Layer Parameters to:
- Enabled—Information element is transferred to the called party.
- Disabled—Information element will not be transferred to the called party.
Broadband Low Layer—Required for ATM systems that support only a value of 'disabled' (that is, the ATM system does not support the feature associated with the parameter).

General Physical Layer Configuration

The General Physical Layer Configuration panel allows you to configure the following information:

Cell Payload Scrambling—Allows you to specify whether cell payload scrambling is enabled or disabled on the physical interface. You can set the ATM Adaptation Layer Parameters to:
- On—Cell payload scrambling is enabled on the physical interface.
- Off—Cell payload scrambling is disabled on the physical interface.
Clock Source Priority—Allows you to specify the priority of this interface when configured as a network clock source. You can set the Clock Source Priority option to: notConfigured, priority1, priority2, priority3, or priority4.
Framing Mode—Allows you to specify the framing format present on the physical interface. You can set Framing Mode to the following options:
- SONET—Displays sts-3c or sts-12c format and applies only to OC-3 and OC-12 type interfaces, respectively.
- SDH—Displays stm1 or stm4 format and applies only to OC-3 and OC-12 type interfaces, respectively.
- DS3 M23 ADM—Displays M23 ADM mode and applies to DS3 type interfaces only.
- DS3 M23 PLCP—Displays M23 PLCP mode and applies to DS3 type interfaces only.
- DS3 C-bit ADM—Displays C-BIT ADM mode and applies to DS3 type interfaces only.
- DS3 C-bit PLCP—Indicates C-BIT PLCP mode and applies to DS3 type interfaces only.
- E3 G832 ADM—Displays G.832 ADM mode and applies to E3 type interfaces only.
- E3 G751 ADM—Displays G.751 ADM mode and applies to E3 type interfaces only.
- E3 G751 PLCP— Displays G.751 PLCP mode and applies to E3 type interfaces only.
- DS1 SF ADM—Displays DS1 SF ADM mode and applies to DS1 type interfaces only.
- DS1 ESF ADM—Displays DS1 ESF ADM mode and applies to DS1 type interfaces only.
- DS1 SF PLCP—Displays DS1 SF PLCP mode and applies to DS1 type interfaces only.
- DS1 ESF PLCP—Displays DS1 ESF PLCP mode and applies to DS1 type interfaces only.
- E1 ADM—Displays E1 ADM mode and applies to E1 type interfaces only.
- E1 PLCP—Displays E1 PLCP mode and applies to E1 type interfaces only.
- E1 CRC ADM—Displays E1 CRC-4 ADM mode and applies to E1 type interfaces only.
- E1 CRC PLCP—Displays E1 CRC-4 PLCP mode and applies to E1 type interfaces only.
STS-Stream Scrambling—Allows you to specify whether STS-stream scrambling is enabled or disabled on the physical interface.You can set the STS-Stream Scrambling option to:
- on—STS-stream scrambling is enabled.
- off—STS-stream scrambling is disabled.
Transmit Clock Source—Allows you to specify the source of the transmit clock.
Loop Timing—Displays that the recovered receive clock is used as the transmit clock. You can set Loop Timing to:
- Free Running—Displays that a local clock source is used.
- Network Derived—Displays that the recovered receive clock from another interface is used as the transmit clock source.
Loopback Configuration—Allows you to specify the loopback configured on the physical interface. You can set Loopback Configuration to:
No Loop—Displays no loopback is present.
Diagnostic Loop—Displays transmit data stream is looped to the receive direction.
Line Loop—Displays receive data stream is looped to the transmit direction.
Other Loop—Displays loopbacks that are not defined here.

DS1/E1/DS3/E3 Physical Layer Configuration

The DS1/E1/DS3/E3 Physical Layer Configuration section allows you to configure the following information:

Line Buildout—Allows you to specify the line buildout configured on the transmit signal. You can set the Line Buildout option to:
- E3 All Cables—Applies to all cables of E3 physical interfaces.
- DS3 Cables Under 225—Applies to cables under 225 feet of DS3 physical interfaces.
- DS3 Cables Over 225—Applies to cables over 225 feet of DS3 physical interfaces.
- DS1 Cables 0 To 110—Applies to cables 0 to 110 feet of DS1 physical interfaces.
- DS1 Cables 110 To 220—Applies to cables 110 to 220 feet of DS1 physical interfaces.
- DS1 Cables 220 To 330—Applies to cables 220 to 330 feet of DS1 physical interfaces.
- DS1 Cables 330 To 440—Applies to cables 330 to 440 feet of DS1 physical interfaces.
- DS1 Cables 440 To 550—Applies to cables 440 to 550 feet of DS1 physical interfaces.
- DS1 Cables 550 To 660—Applies to cables 550 to 660 feet of DS1 physical interfaces.
- DS1 Cables Over 600—Applies to cables over 600 feet of DS1 physical interfaces.
- E1 All Cables—Applies to all cables of E1 physical interfaces.
Line Coding—Allows you to specify the line coding present on the physical interface. You can set Line Coding to:
- AMI—Displays alternate mark inversion (AMI) line code on the DS1/E1 interface.
- B8ZS—Displays B8ZS line code on the physical interface and applies only to DS1 interfaces.
- HDB3—Displays HDB3 line code on the physical interface and applies only to E1 interfaces.

Step 4 Change the information.

Step 5 Save the changes.

Inventory Tab

To view the Inventory tab, follow these steps:

Step 1 Open the Cisco 6400 Line Card ATM Port Management window.

Step 2 Click the Inventory tab. The Inventory panel (Figure 5-41) appears.

Figure 5-41: Cisco 6400 Line Card ATM Port Management Window—Inventory Tab

Step 3 Choose a relevant Chassis, Line Card, and ATM Port. The Inventory information appears for the selected ATM port.

Inventory

The Inventory panel displays the following information:

Admin Address—Displays the address assigned for administrative purposes; for example, an address associated with the service provider side of a public network UNI. When the interface has no assigned administrative address, or when the address used for administrative purposes is the same as that used for ifPhysAddress, then the Admin Address is an octet string of zero length.
ATM Address Type—Displays the type of primary ATM address configured for use at the ATM interface.
Physical Port Type—Displays the type of physical layer medium on the port.

Cisco Operation, Administration, and Maintenance Loopback Window

The Operations, Administration, and Maintenance (OA&M) loopback feature is used to verify connectivity between devices in the network, or connectivity through the entire network. The loopback feature enables you to find faults by looping a signal at various points in the network.

Two types of loopback tests are provided so you can test connectivity between a subscriber connection on the Cisco 64000 UAC and a neighboring switch, or a device at the other end of the network:

Segment—Tests connectivity to the neighboring switch

End-to-end—Tests connectivity through the entire network

Note Multiple services ordered by a subscriber are delivered over a single dedicated line (the subscriber connection). When you run the loopback test, the test checks the connectivity for all of the services delivered to the subscriber.

During the loopback test, SCM sends a specified number of OA&M cells from the local end (the subscriber connection) to the far end (a neighboring switch or a device at the other end of the network). At the far end, the cells are looped back, which means they are sent back to the local end.

If the cells loop back successfully, the network path between the local end and the far end is assumed to be good. If the cells do not loop back successfully, there is a problem. The loopback test also determines how long it took the cells to reach the far end and return, and the number of cells that were successfully looped back.

Running a Loopback Test

To run an SCM OA&M loopback test, follow these steps:

Step 1 Determine the VPI/VCI values of the subscriber connection you want to test.

a. Right click on the ATM module that the subscriber connection uses and select Cisco 6400 UAC > Subscriber > Configure Subscriber option. The Subscriber Configuration window appears (see Figure 8-92).

b. In the left column, select the subscriber.

c. Under Connection Details, select the subscriber connection you want to test.

d. Write down the values in the Subscriber VPI and Subscriber VCI fields. You need to know these values to set up the loopback test.

Step 2 In Map Viewer, locate the chassis that supports the subscriber connection you want to test.

Step 3 Right-click on the chassis and select Cisco 6400 UAC > Port > Manage > Cisco OAM Loopback option. The Cisco Operation Administration and Maintenance Loopback window appears (Figure 5-42).

Figure 5-42: Cisco Operation, Administration, and Maintenance Loopback Window

Step 4 Select the module and ATM port supporting the subscriber connection you want to test.

Step 5 Set up the loopback-test parameters (see the "OAM Configuration Tab" section for detailed field descriptions).

a. For Loopback Level, specify whether to test the virtual path (VP) or the virtual connection (VC).

b. For Loopback Type, select the type of loopback test to run: segment or end-to-end.

c. For Ping VPI and Ping VCI, specify the VPI and VCI values for the subscriber connection you are testing:

For VP level (F4) loopback tests, specify a VPI only.
For VC level (F5) loopback tests, specify both VPI and VCI.

d. For Trap Configuration, specify whether to send notification when the loopback test is finished.

e. For end-to-end loopback tests, use the Location Type and Loopback Location fields to identify the remote end for the loopback test. For segment loopback tests, this is not necessary.

f. Use the Loopback Cell Configuration fields to specify how many OA&M cells to send during the test, and to define the time intervals for sending the cells or considering a cell to have failed.

Step 6 Click Ping Start to initiate the loopback test. The test runs until the specified number of OA&M test cells have been sent, or until you click Ping Stop.

Step 7 Click the OAM Status tab to view the test results (see the "OAM Status Tab" section).

Step 8 To stop the loopback test before it completes, click Ping Stop.

OAM Configuration Tab

Use the OAM Configuration tab (see Figure 5-43) of the Cisco Operation, Administration, and Maintenance Loopback window to define the OA&M loopback test configuration and endpoints. To display the Cisco Operation, Administration, and Maintenance Loopback window, right-click on the ATM module that supports the subscriber connection you want to test and select Cisco 6400 UAC > Port > Manage > Cisco OAM Loopback option.

Figure 5-43: Cisco Operation Administration and Maintenance Loopback Window— OAM Configuration Tab

Loopback Configuration

The Loopback Configuration fields define the type of loopback test to run.

Loopback Level—Specifies whether to run the loopback test on the virtual path (VP) or the virtual connection (VC):
- VP Level (F4)—Test the virtual path specified in Ping VPI. This type of test checks connectivity between the network elements used in virtual paths, and is useful for finding an unavailable path or a path that cannot be guaranteed.
- VC Level (F5)—Test the virtual connection specified by Ping VPI and Ping VCI. This type of test checks the data flow between the network elements used in virtual connections, and is useful for checking for degraded VC performance, such as late arriving cells, lost cells, and cell-insertion problems.
Loopback Type—Type of
loopback test to run from the selected subscriber connection:
- Segment—Tests connectivity to the neighboring switch.
End2end—(End-to-end) Tests connectivity through the network to the remote device whose address is specified in Loopback Location.

Connection Details

These fields identify the subscriber connection to test.

Ping VPI—Virtual path identifier (VPI) of the virtual path used by the subscriber connection you are testing. Use the Subscriber VPI value from the Subscriber Configuration window.
Ping VCI—Virtual channel identifier (VCI) of the virtual connection used for the subscriber connection you are testing. Fill in this field only if you selected F5 Loopback. Use the Subscriber VCI value from the Subscriber Configuration window.

Trap Configuration

This field specifies what SCM should do when the loopback test is over.

Trap on Completion—Send an SNMP trap when the loopback test is finished (Enable), or not (Disable).

Remote End Details

These fields identify the remote endpoint for an end-to-end loopback test. The fields are not valid for segment loopback tests.

Location Type—Type of address in the Loopback Location field. This field applies only when Loopback Type is End-to-End.
- IP address—Use an IP address for Loopback Location.
- nsapPrefix—Use a Network Service Access Point (NSAP) address prefix for Loopback Location.
- 16ByteFixedValue—Use a 16-byte (128-bit value) address for Loopback Location.
Loopback Location—IP, ATM, or fixed 16-byte address (as specified by Location Type) that identifies the remote endpoint for the loopback test. This value, which is placed in the Loopback Location ID field of OA&M cells, causes the device at this location to loop back the cells to the local endpoint.

Loopback Cell Configuration

Ping Timeout—The amount of time to wait (measured in .001 seconds) before considering an OA&M cell to have failed. If the cell is not received back from the remote end within this time period, it is considered to have been dropped. Valid values are 0 through 3600000; the default is 1000, or 1 second.
Ping Count—The number of OA&M cells to send (1 through 2147483647) during the loopback test. The loopback test runs until all of the cells have been sent or you click Ping Stop.
Ping Delay—The amount of time (measured in .001 seconds) to wait before sending the next OA&M cell. After receiving a response for an OA&M cell, or after the cell times out, SCM waits the specified amount of time before sending the next cell. Valid values are 0 through 3600000 (60 minutes). Note that the actual delay may be greater than the specified value because of internal task scheduling.

Actions

Ping Start—Click this button to initiate the loopback test.
Ping Stop—Click this button to stop the loopback test.

OAM Status Tab

Use the OAM Status tab (Figure 5-44) of the Cisco Operation, Administration, and Maintenance Loopback window to view the loopback test results. To display the Cisco Operation, Administration, and Maintenance Loopback window, right-click on the ATM module that supports the subscriber connection being tested and select Cisco 6400 UAC > Port > Manage > Cisco OAM Loopback option.

Figure 5-44: Cisco Operation Administration and Maintenance Loopback Window—OAM Status Tab

Ping Status

Note The Rtt fields describe round-trip time, which is the length of time it takes a cell to travel to the far end and return.

Ping Max Rtt—The maximum round-trip time (in .001 seconds) for any OA&M cells sent during the loopback test. This is the longest that it took for any cell to reach the far end and return (for example, a value of 25000 means it took 25 seconds).
Ping Min Rtt—The minimum round-trip time (measured in .001 seconds) for any OA&M cells sent during the loopback test. This is the least amount of time it took for any cell to reach the far end and return (for example, a value of 5000 means it took 5 seconds).
Ping Avg Rtt—The average round-trip time (measured in .001 seconds) of OA&M cells sent during the loopback test (for example, 7000 is 7 seconds).
Ping Completed—Indicates whether the loopback test has completed (True), or is still running (False).
Ping Sent Cells—Total number of OA&M cells sent during the loopback test.
Ping Received Cells—Total number of OA&M cells received back from the remote end.
Ping Success Rate—Percentage of ping cells that made it to the remote end and were received back at the local end (Ping Received Cells divided by Ping Sent Cells).

SONET APS Management Window

The SONET APS window is divided into two tabbed sections: Statistics and Configuration. These tabs allow you to view the statistics for SONET devices and configure the SONET automatic protection switching between SONET devices.

Viewing the SONET APS Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > SONET APS option. (See Table 5-1 for information on which objects allow you to launch the SONET APS window.) The SONET APS window appears with the Statistics tab displayed (Figure 5-45).

Note The SONET APS window (Statistics tab) only populates when redundancy is configured on the device. Redundancy must be configured manually using Cisco IOS. See "Configuring Redundancy in a Cisco 6400 Chassis" section for further information on configuring redundancy.

Figure 5-45: SONET APS Window—Statistics Tab

Statistics Tab

The Statistics tab (Figure 5-45) displays four panels: Path, Line, Section, and Operational. To view the SONET APS statistics for a specified port, follow these steps:

Step 1 Open the SONET APS window. See the "Viewing the SONET APS Window" section for further details.

Step 2 Choose a relevant NSP, Line Card, and ATM Port.

The statistics for the selected ATM port appear in the Path, Line, Section, and Operational panels (Figure 5-45).

Path

The Path panel displays the following information:

Work Path Status—Indicates the path-level status of the working channel in APS. The c64SONETAPSWorkPathStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetPathNoDefect bit should be set when and only when no other flag is set. Table 5-29 lists the possible bit positions.

Table 5-29: Work Path Status Bit Positions

1	sonetPathNoDefect
2	sonetPathSTSAIS
3	sonetPathSTSRDI
4	sonetPathSTSLOP
5	sonetBIPE(BIP-8)
6	sonetFEBE
7	sonetPathUnequipped
8	sonetPathSignalLabelMismatch

Work Path BIPE—Displays the number of path BIP-8 errors in the working channel.

Work Path FEBE—Displays the number of path far-end-block-errors in the working channel.

Protected Path Status—Indicates the path-level status of the protection channel in APS. The c64SONETAPSProtectPathStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetPathNoDefect bit should be set only when no other flag is set. Table 5-30 lists the possible bit positions.

Table 5-30: Protected Path Status Bit Positions

1	sonetPathNoDefect
2	sonetPathSTSLOP
4	sonetPathSTSAIS
8	sonetBIPE(BIP-8)
16	sonetFEBE
32	sonetPathSTSRDI
64	sonetPathUnequipped
128	sonetPathSignalLabelMismatch

Protected Path BIPE—Displays the number of path BIP-8 errors in the protection channel.
Protected Path FEBE—Displays the number of path far-end-block-errors in the protection channel.

Line

The Line panel displays the following information:

Work Line Status—Indicates the line-level status of the working channel in APS. The c64SONETAPSWorkLineStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetLineNoDefectbit should be set only when no other flag is set. Table 5-31 lists the possible bit positions.

Table 5-31: Work Line Status Bit Positions

1	sonetLineNoDefect
2	sonetLineAIS
3	sonetLineRDI
4	sonetBIPE(BIP-8/24)
5	sonetFEBE

Work Line BIPE—Displays the number of line BIP-8/24 errors in the working channel.

Work Line FEBE—Displays the number of line far-end-block-errors in the working channel.

Protected Line Status—Indicates the line-level status of the protection channel in APS. The c64SONETAPSProtectLineStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetLineNoDefect bit should be set only when no other flag is set. Table 5-32 lists the possible bit positions.

Table 5-32: Protected Line Status Bit Positions

1	sonetLineNoDefect
2	sonetLineAIS
4	sonetLineRDI
8	sonetBIPE(BIP-8/24)
16	sonetFEBE

Protected Line BIPE—Displays the number of line BIP-8/24 errors in the protection channel.
Protected Line FEBE—Displays the number of line far-end-block-errors in the protection channel.

Section

The Section panel displays the following information:

Work Section Status—Indicates the section-level status of the working channel in APS. The c64SONETAPSWorkSectionStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetSectionNoDefect bit should be set only when no other flag is set. Table 5-33 lists the possible bit positions.

Table 5-33: Work Section Status Bit Positions

1	sonetSectionNoDefect
2	sonetSectionLOS
3	sonetSectionLOF
4	sonetBIPE(BIp-8)

Work Section BIPE—Displays the number of section BIP-8 errors in the working channel.

Protected Section Status—Indicates the section-level status of the protection channel in APS. The c64SONETAPSProtectSectionStatus is a bitmap represented as a sum of multiple alarms simultaneously. The sonetSectionNoDefect bit should be set only when no other flag is set. Table 5-34 lists the possible bit positions.

Table 5-34: Protected Section Status Bit Positions

1	sonetSectionNoDefect
2	sonetSectionLOS
4	sonetSectionLOF
8	sonetBIPE(BIp-8)

Protected Section BIPE—Displays the number of section BIP-8 errors in the protection channel.

Operational

The Operational panel displays the following information:

Work Operational Status—Displays the last condition detected in the working channel.
Protected Operational Status—Indicates the last condition detected in the protection channel.

C onfiguration Tab

To change SONET APS configuration information for a specified port, follow these steps:

Step 1 Open the SONET APS window (Figure 5-46). See the "Viewing the SONET APS Window" section for further details.

Figure 5-46: SONET APS Window—Configuration Tab

Step 2 Click the Configuration tab.

Step 3 Choose a relevant NSP, Line Card, or ATM Port. The configuration information for the selected ATM port appears (Figure 5-46) in the configuration panel.

Step 4 Configure the information displayed.

Step 5 Save any changes made.

Configuration

The Configuration panel allows you to view and configure the following parameters:

Mode—Allows you to set the APS mode on the corresponding interface referenced by ifIndex object. You can set the Mode option to:
- Linear—The APS mode of linear 1+1 nonreverting and unidirectional. This is the only true APS mode supported in cisco6400 at FCS.
- yCable—Provides the port hardware redundancy but not transmission line redundancy and is not strictly an APS mode.
- Disable—Disables the Mode option.
BER Threshold—Allows you to set the Bit-Error-Rate threshold at which an APS request of priority Signal Degrade is posted.
Switch Command—Used to post an APS priority request. This request succeeds when no higher priority request is posted. You can set the Switch Command option to:
- LockOut—Locks out the protection channel corresponding to this entry.
- Force Working—Posts a request to switch away from the working channel to the protection channel of this entry.
- Force Protect—Posts a request to switch away from the protection channel to the working channel of this entry.
- Manual Working—Posts a request to switch away from the working channel to the protection channel of this entry.
- Manual Protect—Posts a request to switch away from the protection channel to the working channel of this entry.
- Clear—Clears all posted APS priority requests in this channel.

C onfiguring Redundancy in a Cisco 6400 Chassis

Redundancy configuration allows you to specify the redundancy pairings for CPUs (NSPs), slots (NRPs and OC-12 NLC), and subslots (OC-3 and DS-3 NLCs). Redundancy configuration is not supported in the current release of the Cisco 6400 SCM application. Redundancy can be set up manually, however, using Cisco IOS commands.

Note The SONET APS window (see Figure 5-45) will only populate when redundancy is configured on the device.

To configure any of the redundancy parameters on the NSP, follow these steps:

Step 1 From a relevant object icon or from an object list, right-click Technology Specific Tools > Initiate Telnet Session option. (See Table 5-1 for information on which objects allow you to launch a Telnet window.)

Step 2 Release the mouse button. A Telnet window appears (Figure 5-47).

Figure 5-47: Telnet Window

Step 3 Enter a password at the prompt:
<yourpassword>

The NSP prompt appears.

Step 4 Enter enable mode:
enable

Step 5 Enter the enable password at the prompt:
<enablepassword>

Step 6 Enter configuration mode:
NSPprompt# configure terminal

Step 7 Enter redundancy mode:
NSPprompt(config)#redundancy

The next step is to configure the main CPU parameters on the NSP.

Step 8 Enter main-cpu mode:
NSPprompt(config-r)#main-cpu

Step 9 To configure the autosync elements:
NSPprompt(config-r-mc)#auto-sync <startup-config> <config-register> <bootvar> <standard>

Note Adding on to the command any of the optional (<>) parameters will set this parameter on the NSP.

Step 10 Enter the slot numbers to configure slot redundancy:
NSPprompt(config-r)#associate slot x y

Note When entering the slots to be associated, the slot numbers (x and y) must be adjacent and the first slot must be an odd-numbered slot; for example, slot 1 + 2 is valid, but slot 2 + 3 is invalid. The x and y must be integer values between 1 and 8.

Step 11 Enter the subslot numbers (adhering to the same numbering restrictions as for slot numbers) to configure subslot redundancy:
NSPprompt(config-r)#associate subslot <slot>/<card> <slot>/<card>

Note To deconfigure any of the settings described earlier, prefix the command with "no"; for example, NSPprompt(config-r)#no associate subslot <slot>/<card> <slot>/<card>

Interface Configuration Window

The Interface Configuration window allows you to carry out part of the configuration for the NRP and NLC interface ports in a selected chassis. You can then commission or decommission the selected interface port.

Each port interface (that is, NRP, NRP2, or NLC) has a port management window where additional port interface configuration can be carried out (either before or after commissioning the selected port interface). For example, you might want to configure parameters in the Cisco 6400 Line Card ATM Port Management window before commissioning the NLC interface port using the Interface Configuration window.

Viewing the Interface Configuration Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > Configuration option. (See Table 5-1 for information on which objects allow you to launch the Interface Configuration window.) The Interface Configuration window appears with the Configuration tab displayed (Figure 5-48).

Figure 5-48: Interface Configuration Window—Configuration Tab

The Module list displays half-height modules (OC-3 or DS3 NLCs) with a slot and subslot number displayed (for example, OC-3-8-0). Full-height modules (NSPs, NRPs, NRP2s, or OC-12 NLCs) are displayed as a module with a slot number (for example, NRP-5). When selecting a module from the list, you must first identify the module's location in the chassis and then choose the module according to its slot location in the rack.

The Interface list displays a list of the interfaces for the selected chassis and module (that is, NSP, NRP, NRP2, or NLC). The Interface list displays half-height modules (OC-3 or DS3 NLCs) with a slot, subslot and port number (for example, ATM-8-0-0). Full-height modules (NSPs, NRPs, NRP2s, or OC-12 NLCs) are displayed as a module with a slot number, subslot number, and port number (for example, ATM-1-0-0).

Configurable Parameters

The Configurable Parameters panel displays the following information:

Alias—Displays the name for the interface, as specified by the network manager.
Administration Status—Administration Status option allows you to enable, disable or reset the module.
Link Up or Down Trap Enable—Allows you to choose whether link up or down traps should be generated for this interface.
Supplementary Information—Displays supplementary information.

Actions

The Actions panel allows you to commission or decommission the selected interface:

Commission—Click Commission to commission the selected interface.
Decommission—Click Decommission to decommission the selected interface.

C ommissioning an NRP or NLC In terface Port

Step 1 Open the Interface Configuration window. See the "Viewing the Interface Configuration Window" section for further details.

Step 2 Choose the relevant Chassis, Module, and Interface from the lists displayed at the left side of the window. The Status of the selected module appears at the bottom left corner of the window.

Note The NSP module resides in Slot 0 in the chassis. Do not attempt to commission an NSP module.

Step 3 Configure the parameters displayed in the Configurable Parameters panel.

Step 4 Click Commission when the status is Decommissioned.

The NRP, NSP, or NLC interface is now commissioned. Its state changes to Commissioning and then Normal.

Decommissioning an NRP or NLC Interface Port

Step 1 Open the Interface Configuration window. See the "Viewing the Interface Configuration Window" section for further details.

Step 2 Choose the relevant Chassis, Module, and Interface from the lists displayed at the left side of the window. The status of the selected module appears at the bottom left corner of the window.

Step 3 Click Decommission when the status is Normal. The NRP, NSP or NLC is now decommissioned. Its state changes to Decommissioned.

Interface Performance Window

The Interface Performance window displays performance attributes for the selected interface and allows you to Start or Stop performance logging for the selected interface.

Note Performance logging can start or stop on a module or global basis for a selected chassis. See the "Chassis Configuration Window" section for details on how to start or stop global performance logging for a selected chassis. See the "Module Configuration Window" section for details on how to start or stop global performance logging on a per-module basis.

Viewing the Interface Performance Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > Performance option. (See Table 5-1 for information on which objects allow you to launch the Interface Performance window.) The Interface Performance window appears with the Performance (1) tab displayed (Figure 5-49).

Note The NRP2 displays in the Module list on the Interface Performance window.

Figure 5-49: Interface Performance Window—Performance (1) Tab

Starting Performance Loggi ng for a Selected Interface

To begin performance logging for a selected interface, follow these steps:

Step 1 Open the Interface Performance window. (See the "Viewing the Interface Performance Window" section for further details.) The Performance (1) tab appears (Figure 5-49).

Step 2 Choose the relevant Chassis, Module, and Interface from the lists displayed at the left side of the window.

Step 3 Click Start to begin performance logging for the selected interface. A window appears for you to confirm that you want to start performance logging.

Step 4 Click Yes to begin performance logging for the selected interface.

Note Click the Performance (2) tab to view Error Statistics information for the selected interface.

Stopping Performance Logging for an Interface

To stop performance logging for a selected interface, follow these steps:

Step 1 Open the Interface Performance window. See the "Viewing the Interface Performance Window" section for further details. The Performance (1) tab appears.

Step 2 Choose the relevant Chassis, Module, and Interface from the lists displayed at the left side of the window.

Step 3 Click Stop to stop performance logging for the selected interface. A window appears for you to confirm that you want to stop performance logging.

Step 4 Click Yes to stop performance logging for the selected interface.

Interface Status Window

The Interface Status window displays status information for the selected interface.

Viewing the Interface Status Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Port > Manage > Status option. (See Table 5-1 for information on which objects allow you to launch the Interface Status window.) The Interface Status window appears with the Status tab displayed (Figure 5-50). The Status tab displays three panels: Interface Details, Last Change Details, and Transmission Details.

Figure 5-50: Interface Status Window—Status Tab

Status T ab

To view the Status tab, follow these steps:

Step 1 Open the Interface Status window. See the "Viewing the Interface Status Window" section for further details.

The Status tab appears.

Step 2 Choose the relevant Chassis, Module, and Interface from the lists displayed at the left side of the window.

The Status tab displays the following panels.

Interface Details

The Interface Details panel displays the following information:

Type—Displays the interface type.
Description—Displays a text-string description of the interface.
Operational Status—Displays the current operational status of the interface.
Physical Address—Displays the address of the interface at its protocol sublayer.
Keep Alive—Displays whether keepalives are enabled or not on this interface.
Line Protocol—Displays whether the line interface protocol is up or not.
Connector Present—Displays whether or not the interface has a physical connector. "True" means a physical connector is present and "False" means a physical connector is not present.

Last Change Details

The Last Change Details panel displays the following information:

Interface Last Change—Displays the value of the system uptime at the time the interface entered its current operational state.
Reason for Last Change—Reason for the last status change in the interface.

Transmission Details

The Transmission Details panel displays the following information:

Speed—Displays an estimate of the interface's current bandwidth in bits per second (bps).
High Speed—Displays an estimate of the interface's current bandwidth in units of 1,000,000 bits per second (bps).
Maximum Transmission Unit—Size of the largest packet which can be sent or received on the interface, specified in octets.

M anagement Information Window

The Management Information window allows you to set system configuration information for a selected chassis and IOS command line security information. The Management Information window (Figure 5-51) displays two tabs: Configuration and IOS/Command Line Security

Viewing the Management Information Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Chassis > Admin > Management Information option. (See Table 5-1 for information on which objects allow you to launch the Management Information window) The Management Information window (Figure 5-51) appears with the Configuration tab displayed.

Figure 5-51: Management Information Window—Configuration Tab

The Configuration tab displays the System Configuration panel.

System Configuration

The System Configuration panel allows you to configure the following parameters:

IP Address—Allows you to set the IP address for the system.
System Name—Allows you to enter a system name.
System Contact—Allows you to enter a contact name string.
System Location—Allows you to enter a system location string.
Extra Location Information—Allows you to enter additional location information.

Configuring System Configuration and IOS/Command Line Security Information

To configure system configuration and IOS/command line security information, follow these steps:

Step 1 Open the Management Information window. The Configuration tab appears.

Step 2 Choose the relevant Chassis from the lists displayed at the left side of the window.

Step 3 Configure the parameters displayed in the Configuration tab.

Step 4 Click the IOS/Command Line Security tab.

Step 5 Configure the parameters displayed in the Security Details panel.

The Security Details panel allows you to view and configure the following parameters:

User Name—Displays the username.
Login Password—Allows you to enter a login password for the device.
Exec Password—Allows you to enter an Exec password for the device.
Save Locally—Click Save Locally to save the management information to a local device.
Save to Device—Click Save to Device to save the management information to a selected device.

Step 6 Click Save Locally to save the configuration information.

IOS Image Download Window

The IOS Image Download window displays a single Download tab. The Download tab allows you to configure download parameters and initiate a Cisco 6400 firmware or Cisco IOS release download to one or more user-selected NSPs and NRPs at a user-specified time.

Caution IOS image download is available on a chassis and modules. Care is required when selecting a chassis or NRP from the IOS Host list. When a chassis or NLC is selected (in the IOS Host list) the IOS image is downloaded to the NSP, and when an NRP is selected (in the IOS Host list) the image is downloaded to the NRP.

Note The NSP controls and manages the NRP2 image download process. It is recommended that you store all NRP2 images on the NSP PCMCIA disk.

Viewing the IOS Image Download Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Admin > IOS Image Download option. (See Table 5-1 for information on which objects allow you to launch the IOS Image Download window.)

The IOS Image Download window appears with the Download tab displayed. The Download tab (Figure 5-52) displays three panels: Configuration, Status, and Actions.

Figure 5-52: IOS Image Download Window—Download Tab

The Configuration panel allows you to view and configure the following parameters:

TFTP Server IP Address—Allows you to set the TFTP IP address.
Destination File System—Allows you to specify any file system name supported by the Cisco 6400 UAC. Supported file system names are, Boot Flash, Flash, Disk 0, and Disk 1.
Source File Name—Allows you to specify the source file name (Cisco IOS image name).
Destination File Name—Allows you to specify the name for the file as it is stored in the file system of the Cisco 6400 SCM.
Format the destination device before copying?—Allows you to format the destination device before copying. You can set the Format the destination device before copying? option to:
- Yes—Enables formatting of the destination device.
- No—Disables formatting of the destination device.
Reboot device using new image?—Allows you to reboot the device after a successful download. You can set the Reboot device using new image? option to:
- Yes—Enables rebooting of the device.
- No—Disables rebooting of the device.

Status

The Status panel displays the Last download operation (this displays the date and time of the last download).

Actions

The Actions panel allows you to initiate the following actions:

Download—Click Download to download the Cisco IOS image (specified by the Source File Name in the Configuration panel) from the specified TFTP server to the Cisco 6400 file system (specified in the Destination File Name in the Configuration panel).
Scheduled Download—Click Scheduled Download to open the ScheduleDialog window. The ScheduleDialog window allows you to enter a Date (in <mm><dd><yyyy> format) and time (hh:mm) for the download to be performed.

Initiating a Dow n load

To initiate a download, follow these steps:

Step 1 Open the IOS Image Download window. See the "Viewing the IOS Image Download Window" section for further details.

Step 2 Choose an IOS Host (that is, an NSP). The download information appears.

Caution IOS image download is available on a chassis and modules. Care is required when you choose a chassis or NRP from the IOS Host list. When a chassis or NLC is selected (in the IOS Host list) the IOS image is downloaded to the NSP, and when an NRP is selected (in the IOS Host list) the image is downloaded to the NRP.

Step 3 Configure the parameters displayed in the Configuration panel.

Step 4 Click Download to download the Cisco IOS image (specified by the Source File Name in the Configuration panel) from the specified TFTP server to the file system of the Cisco 6400 (specified in the Destination File Name in the Configuration panel).

Scheduling a Download

To schedule a Cisco IOS image download, follow these steps:

Step 1 Open the IOS Image Download window. See the "Viewing the IOS Image Download Window" section for further details.

Step 2 Choose an IOS Host. The download information appears.

Step 3 Configure the parameters displayed in the Configuration panel.

Step 4 Click Scheduled Download. The Schedule Dialog window appears (Figure 5-53). The Schedule Dialog window allows you to enter a Date (in <mm><dd><yyyy> format) and time (hh:mm) for the download to be performed.

Figure 5-53: Schedule Dialog Window

Step 5 Enter a Date (mm/dd/yyyy) and time (hh:mm) for the download to take place automatically. Click Ok to save the new date and time. An Action Report window appears. The Action Report window details the Cisco IOS commands executed. Invalid Cisco IOS commands result in a failure to download.

Step 6 Check the details in the Action Report window to ensure that the scheduled download was set up successfully.

Step 7 Click Save to save the Action Report, if required.

Step 8 Click Close to close the Action Report window and return to the Cisco IOS Image Download window.

Step 9 Click Close from the File menu to close the Cisco IOS Image Download window.

Configuration Backup/Restore Window

Caution The User Name, Login Password, and Exec Password parameters (set in the Management Information window in the IOS Command Line Security tab) must be identical to the CLI Passwords set in the Cisco 6400 NSP Management window (Configuration tab). See the "Cisco 6400 NSP Management Window" section and the "Management Information Window" section for further details on setting the User Name, Login Password, and Exec Password parameters. IOS Image Download and Backup/Restore fail when the username and passwords are not identical.

The Configuration Backup/Restore window allows you to upload the current Cisco 6400 SCM running configuration from a specified Cisco 6400 UAC and save it as a file to any Trivial File Transfer Program (TFTP) server. Later you can download this file from the specified TFTP server to a user specified Cisco 6400 UAC.

Regular configuration backups allow recovery if hardware fails. For example, if an NRP were to fail, a replacement NRP could be inserted into the chassis and the configuration data would be restored. Changes in configuration data between the last backup and the time of the failure would be lost.

Note The backup/restore mechanism is not intended as a "configuration upload and manipulation" facility permitting configuration of the Cisco 6400 UAC (for example, through Cisco IOS, followed by subsequent management by the Cisco 6400 SCM).

Note Refer to the "Setting Up a Workstation As a TPTP Server" section in the Cisco 6400 Service Connection Manager Installation Guide.

Note Backup and Restore is on a per-chassis basis. When all NRP and NSP configurations are backed up when the Restore button is pressed the configuration is copied onto the Cisco 6400 UAC. Selecting the Restore button initiates the action of restoring the running configuration to a Cisco 6400 UAC.

Viewing the Configuration Backup/Restore Window

From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Module > Admin > Configuration Backup/Restore option. (See Table 5-1 for information on which objects allow you to launch the Configuration Backup and Restore window.) The Configuration Backup/Restore window appears with the Backup/Restore tab displayed (Figure 5-54).

Figure 5-54: Configuration Backup/Restore Window

Initiating a Backup

To initiate a backup, follow these steps:

Step 1 Open the Configuration Backup/Restore window (Figure 5-54).

Step 2 Choose a relevant Chassis. The Backup information for the Cisco 6400 SCM appears in the Configuration and Actions panels.

Step 3 Click Backup to begin the backup. The Action Report window appears (Figure 5-55).

Figure 5-55: Action Report Window

The Action Report window details the Cisco IOS commands executed when the service is commissioned. Invalid Cisco IOS commands result in a failure to commission the service.

Step 4 Check the details in the Action Report window to ensure that the backup was successful.

Step 5 Click Save to save the Action Report, if required.

Step 6 Click Close to close the Action Report window and return to the Configuration Backup/Restore window.

Step 7 Click Close from the File menu to close the Configuration Backup/Restore window.

Configuration

The Configuration panel allows you to view and configure the following parameters:

Backup Server—Allows you to set the TFTP IP address.

Backup after every Action—Allows you to take a backup after every Telnet action (for example, service (de)commission or service (dis)connection). You can set the Backup after every Action option to:

Enable—Enables automatic backup after every configuration change.

Disable—Configuration changes are not automatically saved after every configuration change.

Note This option (when enabled) automatically backs up the Cisco 6400 after every: Service Instance "Commission" operation, and connect or disconnect operation. The default setting for Backup after every Action is "disable."

Status

The Status panel displays the following parameters:

Time Stamp of Last Backup—The time of the last backup.
Backup File Name—The name of the backup file.

Actions

The Actions panel allows you to:

Backup—Click Backup to initiate the action of backing up the running configuration of the selected Cisco 6400 UAC.
Restore—Click Restore to initiate the action of restoring the running configuration to the selected Cisco 6400 UAC.
Schedule Backup—Click Schedule Backup to schedule a date and time for the backup to take place.

Initiating a Resto re

To initiate a restore, follow these steps:

Step 1 Open the Configuration Backup/Restore window. See the "Viewing the Configuration Backup/Restore Window" section for further details.

Step 2 Choose a relevant Chassis. The backup/restore information for the Cisco 6400 SCM appears.

Step 3 Click Restore to begin the backup. An Action Report window appears. The Action Report window details the Cisco IOS commands executed when the service is commissioned. Invalid Cisco IOS commands result in a failure to commission the service.

Step 4 Check the details in the Action Report window to ensure that the restore was successful.

Step 5 Click Save to save the Action Report, if required.

Step 6 Click Close to close the Action Report window and return to the Configuration Backup/Restore window.

Step 7 Click Close from the File menu to close the Configuration Backup/Restore window.

Scheduling a Backup

To schedule a backup, follow these steps:

Step 1 Open the Configuration Backup/Restore window. See the "Viewing the Configuration Backup/Restore Window" section for further details.

Step 2 Choose a relevant IOS Host. The backup/restore information for the Cisco 6400 SCM appears.

Step 3 Click Schedule Backup to schedule a date and time for the backup to take place. The Schedule window appears (Figure 5-56).

Figure 5-56: Schedule Window

Step 4 Enter a Date (mm/dd/yyyy) and time (hh:mm) for the scheduled backup to take place automatically. Click Ok to save the new date and time. An Action Report window appears. The Action Report window details the Cisco IOS commands executed when the service is commissioned. Invalid Cisco IOS commands result in a failure to commission the service.

Step 5 Check the details in the Action Report window to ensure that the scheduled backup was set up successfully.

Step 6 Click Save to save the Action Report, if required.

Step 7 Click Close to close the Action Report window and return to the Configuration Backup/Restore window.

Step 8 Click Close from the File menu to close the Configuration Backup/Restore window.

Launching Telnet on NSPs and NRPs

You can launch a Telnet session from an icon representing a Chassis, NSP, or NRP in the MapViewer application.

Note From an NRP2 object, the menu option Cisco 6400 UAC > Tools > Initiate Telnet Service does not initiate a Telnet session to the NRP2. Instead, a Telnet session is launched to the NSP. To Telnet to an NRP2, launch a Telnet session from the NSP.

To launch a Telnet session, follow these steps:

Step 1 From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Tools > Initiate Telnet Session option. (See Table 5-1 for information on which objects allow you to launch a Telnet window.)

Step 2 Release the mouse button. A Telnet window appears.

Step 3 Enter the required password. Refer to the Cisco 6400 UAC Software Configuration Guide for further Telnet information.

Launching the NSP WebConsole Application

You can launch Netscape and open the URL representing the home page of the embedded NSP or NRP HTTP server application (known as the WebConsole) from an icon representing an NSP or NRP in the MapViewer application.

To launch the WebConsole application, follow these steps:

Step 1 From a relevant object icon or from an object list, right-click Cisco 6400 UAC > Tools > Launch WebConsole option. (See Table 5-1 for information on which objects allow you to launch a WebConsole application window)

Step 2 Release the mouse button. A password window appears. Enter the required user ID and password.

A window appears providing access to the Cisco WebConsole product. Refer to the Cisco 6400 UAC Software Configuration Guide for further information on WebConsole.

Table of Contents

Managing the Cisco 6400 SCM Element Manager Windows

Management

Starting Global Performance Logging

Configuring PPPoE Configuration