Configuration

Proper configuration of the cumulative device allows for accurate information by which to manage the device. Certain configuration criteria is essential to enable communication between the EM and the device. The procedures which follow provide the necessary information to create and maintain chassis, module, and interface configuration.

The Configuration chapter details the following:

Chassis Configuration

The Chassis Configuration section covers the following areas:

Management Information

The Management Information window allows you to configure the chassis IP address, system attributes, and set or change chassis user names and passwords.

Caution It is strongly recommended that only a system administrator have access to the Management Information window because access password configuration and modification can occur using this window.

The Management Information section covers the following areas:

System Configuration

To configure the fields within the Configuration tab, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Chassis >) IOS Settings. For information on which objects allow you to launch the Management Information window, see "EM Windows".

The Management Information window appears displaying the Configuration tab.

Figure 5-1 Management Information Window—Configuration Tab

Step 2 Select an IOS Host from the corresponding list box on the left-hand side of the window.

The IP address that the EM uses to contact the device displays in the corresponding field. Although not recommended, this entry is modifiable.

Step 3 Configure the fields on the Configuration tab as follows:

System Name—Enter the name of the device.
System Contact—Enter the name and contact details for the person administering the node.
System Location—Enter the physical location of the system.
Extra Location Information (optional)—Specify additional information describing the location of the system as necessary.

Step 4 Click the Save icon on the toolbar to save your changes.

Step 5 Choose File > Close to close the Management Information window.

Managing Username and Passwords

In order to manage passwords, the chassis password must be identical on the (local) EM and the device. You can manage chassis passwords for both the EM and the device using the Management Information window.

Following initial deployment, you must first enter the chassis password to match that of the device and choose the Save Locally option. The local password on the EM is set to match the password on the device. Once the EM and device chassis passwords match, you may modify the password as you see fit and choose the Save to Device option. Choosing the Save to Device option changes the chassis password locally within the EM and on the device simultaneously.

Similarly, when the chassis password changes on the device you must modify the password to match that of the device and save locally; thereby forcing the (local) EM password to match the device password. Again, when the chassis password is identical on both the EM and the device, you may change the password at your discretion and save to the device in order to update the password in the EM and on the device.

If the chassis password does not match the password of the device, then the actions may fail to complete. Upon failures, an action report may display indicating that the password is not active when operations initiate.

There are two types of passwords supported by the EM used to perform privileged tasks, enable and secret passwords. Each device can be configured using the enable password or the enable and secret passwords. The secret password always takes precedence over the enable password. Choosing the save the password locally to the device changes and enable password, not the secret password.

To enter or change the username or passwords, proceed as follows:

The Management Information window appears displaying the Configuration tab (see the previous figure for an example).

Step 2 Click the IOS/Command Line Security tab.

The IOS/Command Line Security tab displays in the Management Information window.

Figure 5-2 Management Information Window—IOS Command Line Security Tab

Step 3 Enter the appropriate information in the Security Details fields as follows:

User Name (optional)—Enter a unique user name which, combined with the passwords below, provides additional levels of security for accessing the device.
Login Password—Enter the telnet access password to protect the device from access by unauthorized personnel.
Confirm Login Password—Reenter the password entered in the Login Password field.
Exec Password—Depending upon the device configuration, enter either the enable or secret password for the chassis, enabling you to perform privileged operations on the chassis.
Confirm Exec Password—Reenter the password entered in the Exec Password field.

Step 4 If you know the passwords that are set on the device, perform one of the following:

Click Save Locally to save your passwords locally for the selected chassis. This changes the passwords stored within the EM only.
Click Save to Device. This changes passwords both on the device and locally in the EM.

If you want to reconfigure the passwords on the device and passwords have been previously specified, you can click Save to Device. This action will work only if previous valid passwords have been saved locally.

Step 5 Click the Save icon on the toolbar to save your changes.

Step 6 Choose File > Close to close the Management Information window.

Chassis Configuration

The Chassis Configuration window allows you to view and configure parameters, commission or decommission, switch global performance logging on or off for a particular chassis, and write to the running configuration file. The Chassis Configuration window (Additional Descriptions tab) also allows you to specify additional description information for a specific chassis. The Description 1 and Description 2 attributes allow you to enter text descriptions for identification purposes; for example, CLLI codes.

You use the Chassis Configuration window to perform the following tasks:

Configuring the Chassis

To configure the chassis, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Chassis >) Configuration. For information on which objects allow you to launch the Chassis Configuration window, see "EM Windows".

The Chassis Configuration window appears displaying the Configuration tab.

Figure 5-3 Chassis Configuration Window—Configuration Tab

Step 2 Select a Chassis from the Chassis list box on the left-hand side of the window.

Step 3 The Validation Parameters area contains attributes that describe the population characteristics of a chassis and are used to validate module deployment. Optionally, you can modify the values in the Validation Parameters fields as follows:

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

Step 4 Configure the system actions to be taken in the event of a system failure in the Action fields as follows:

Failure—Specify the appropriate system action to be taken when a chassis failure occurs. Options are Nothing, Send Trap, Shutdown, and Send Trap and Shutdown.
Change—Specify whether the previously selected system action will be taken when a chassis failure occurs. The option selected from the Failure button displays to the right of this field. When the Change field is selected, the action that will be taken when a chassis change occurs displays.

Step 5 Configure the parameters in the Clock area as follows:

Source Priority—Specify the highest priority at which the system is configured as the network clock source. Available options are priority levels 1 through 5.
Clocking Mode—When selected, enables you to invoke the clocking mode by toggling on or off the associated button.

Revertive—When not selected, the clock changes to a higher priority clock when one is available.
Non Revertive—When selected, the clock stays at the current priority even if a higher priority clock is available.

Step 6 Configure the power supplies by selecting the appropriate option from the PS1 Admin Status and the PS2 Admin Status option buttons. Options are: enable, disable, or reset.

Step 7 Click the Additional Descriptions tab.

The Chassis Configuration window appears displaying the Additional Descriptions tab.

Figure 5-4 Chassis Configuration Window—Additional Descriptions Tab

Step 8 Enter additional descriptions into the Descriptions 1 and Descriptions 2 areas (optional) as required.

You can enter any information you wish into the Description 1 and Description 2 data entry fields. For example, you might wish to record additional text descriptions for identification purposes, such as CLLI codes.

Step 9 Click the Save icon on the toolbar to save your changes.

Step 10 Choose File > Close to close the Chassis Configuration window.

Commissioning a Chassis

When you commission a chassis, subchassis discovery begins automatically. Subchassis discovery discovers and commissions all objects within the chassis. For additional details regarding subchassis discovery, see the "Chassis Commissioning and Subchassis Discovery" section.

Commissioning automatically starts active management (such as heartbeat polling) on the chassis and all commissioned objects within the chassis.

To commission a chassis, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 5-3).

Step 2 Select the Chassis you want to commission from the Chassis list box on the left-hand side of the window.

Step 3 Ensure the chassis has proper configuration. For information on chassis configuration attributes, see the "Configuring the Chassis" section.

Step 4 Click Commission (in the Management area).

The chassis commissions and all objects contained within commission through subchassis discovery. As subchassis objects discover, they display in the left-hand pane of the Map Viewer window and populate the chassis map in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the chassis commission. Additionally, status information displays in the Commission Status area of the Chassis Configuration window reiterating the outcome of the commissioning action as either Succeeded or Failed.

When viewing the Chassis Configuration window in future instances, the Commission Status area displays the result of the last commission action, either Succeeded or Failed.

Step 5 Click Close to close the Action Report window.

Step 6 Choose File > Close to close the Chassis Configuration window.

The following figure shows a Cisco 10008 chassis map in the Physical view after subchassis discovery. Modules and interfaces are automatically discovered within the chassis and enter the appropriate post-commissioning state. For details about object states, see the "Object States" section.

Figure 5-5 After Subchassis Discovery

After commissioning a chassis you can configure and manage the chassis objects.

Decommissioning a Chassis

Decommissioning a chassis decommissions all objects within the chassis and active management (such as polling) stops on the chassis as well as on all objects within the chassis.

Decommissioning a managed chassis object is necessary in order to delete a managed chassis object from the EM. Should you attempt to delete a managed chassis object from the EM without first decommissioning it, an error displays indicating that the action cannot complete successfully.

To decommission a chassis, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 5-3).

Step 2 Select the chassis you want to decommission in the Chassis list box on the left-hand side of the window.

Step 3 Click Decommission (in the Management area).

The chassis and all objects contained within are decommissioned. Decommissioned objects remain in the left-hand pane of the Map Viewer window and appear grayed out in the chassis map which displays in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the chassis decommissioning. Additionally, status information displays in the Commission Status area of the Chassis Configuration window reiterating the outcome of the decommission action as either Succeeded or Failed. If decommissioning is successful, the state of the chassis and subchassis objects change to decommissioned.

Step 4 Click Close to close the Action Report window.

Step 5 Choose File > Close to close the Chassis Configuration window.

Starting Global Performance Logging

Global performance logging collects performance information on interfaces within a specific chassis. Following a minimum fifteen minute increment, performance data is available for viewing through the Cisco EMF Performance Manager.

If you start global performance logging on a chassis, all subchassis objects move into the performance logging on state. Performance data gathering, however, is only applicable to interfaces. Therefore, despite having a state of performance logging on, performance data for chassis and modules is not available in the Performance Manager, with exception only to CPU performance data.

For additional information on the Performance Manager, see the "Performance Manager" section.

Caution Global performance logging can use a lot of resources, so use discretion before enabling this option.

In lieu of starting global performance logging, you can start performance logging on a per module or interface basis. For information on starting performance logging for a specific module, see the "Module Performance" section. For information on starting performance logging for a particular interface, see the "Interface Performance" section.

To start global performance logging for a selected chassis, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 5-3).

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 3 Click Start (in the Global Performance Logging area) to begin performance logging on the selected chassis.

An Action Report window appears indicating whether the performance logging "on" action is successful or fails.

Step 4 Click Close to close the Action Report window.

Step 5 Choose File > Close to close the Chassis Configuration window.

Stopping Global Performance Logging

Stopping global performance logging at the chassis-level stops performance collection at the module and interface level as well.

Rather than stopping performance logging globally, you may stop performance logging on a per module or interface basis. For instructions on stopping performance logging for a selected module, see the "Module Performance" section. For instructions on stopping performance logging for a selected interface (such as ATM, Ethernet, or SONET), see the "Interface Performance" section.

To stop global performance logging for a selected chassis, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 5-3).

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 3 Click Stop (in the Global Performance Logging area) to stop global performance logging for the selected chassis.

The Action Report window appears indicating whether the performance logging "off" action is successful or fails.

Step 4 Click Close to close the Action Report window.

Step 5 Choose File > Close to close the Chassis Configuration window.

Writing a Running Config

Two configurations reside within the EM, a running config and a start up config. As you make changes while working on the system, the running config updates automatically. However, if you should reboot the device, the EM automatically defaults to the current (saved) start up config and a new running config initiates. As such, the changes made to the previous running config are lost. To prevent this from happening, the EM enables you to write changes from the running config to the start up config during the same session.

To write a running config of the selected chassis to the start up config, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 5-3).

Step 2 Click the Device Management tab.

The Chassis Configuration window appears displaying the Device Management tab.

Figure 5-6 Chassis Configuration Window—Device Management Tab

Step 3 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 4 Click writeMem (in the Write Config to Flash area).

Changes to the running config apply to the startup config. In the future, when the startup config is accessed, it will contain the most recent running config written to memory.

Step 5 Click the Save icon on the toolbar to save your changes.

Step 6 Choose File > Close to close the Chassis Configuration window.

SNMP Management

The SNMP Management section covers the following areas:

Configuring SNMP Community Names and Versions

Community names provide a security mechanism for SNMP communications. The device holds its own community names, so the community names set within the EM must match the setting on the device in order to get or set attributes (from the device). If community string settings do not match between the EM and the device, a critical alarm arises on the chassis and the chassis moves into the discovery lost comms state.

Community name configuration is directly related to the SNMP version configuration.

To configure SNMP community names and version information, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Chassis >) SNMP Settings. For information on which objects allow you to launch the SNMP Management window, see "EM Windows".

The SNMP Management window appears displaying the SNMP Management tab.

Figure 5-7 SNMP Management Window—SNMP Management Tab

Step 2 Select an IOS Host from the IOS Host list box on the left-hand side of the window.

Step 3 Enter the appropriate Community Name information as follows:

V1 Read—Enter the community string used when retrieving attributes from a device using the SNMPv1 protocol.
V1 Write—Enter the community string used when setting attributes on a device using the SNMPv1 protocol.
V2 Read—Enter the community string used when retrieving attributes from a device using the SNMPv2c protocol.
V2 Write—Enter the community string used when setting attributes on a device using the SNMPv2c protocol.

SNMP community strings are local only. The data you enter in the fields of the Community Names area have no effect on the device.

Step 4 Select the SNMP version to be used from the SNMP Version option list.

Step 5 Click the Save icon on the toolbar to save your changes.

Step 6 Choose File > Close to close the SNMP Management window.

Enabling or Disabling Trap Generation

Trap generation may be enabled or disabled within the EM through SNMP management. It is, however, necessary to configure the device with the EM server IP address from the CLI in order to receive (SNMP) trap data from the device. This is a critical prerequisite step when enabling trap generation. If the device is not configured with the EM server IP address, trap data will not be received by the EMS.

Note For details on configuring the EM to receive trap information from the device, see the Cisco 10000 Series Manager Installation Guide.

The device sends traps to the EM when trap generation is enabled. When the EM receives a trap, alarms raise on the chassis or the chassis' underlying modules or interfaces. When trap generation is disabled on the device, the EM does not receive any traps and, therefore, does not raise any alarms. As such, it is recommended to enable trap generation at all times.

To enable or disable trap generation on a selected chassis, proceed as follows:

The SNMP Management window appears displaying the SNMP Management tab (see Figure 5-7).

Step 2 Select an IOS Host from the IOS Host list box on the left-hand side of the window.

Step 3 Ensure that the SNMP version and community configuration is appropriate. For additional information, see the preceding section.

Step 4 Click the appropriate Trap Generation button as follows:

Click Enable to enable trap generation for the selected chassis. Traps generate by the selected chassis and are sent to the EM which is configured on the device.
Click Disable to disable trap generation for the selected chassis. No traps will generate by the selected chassis.

Step 5 Click the Save icon on the toolbar to save your changes.

If enabled, traps convert into alarms which display in the Cisco EMF Event Browser. For additional information on the alarms supported by the EM, see "Alarms." Additionally, alarm indicators display on the Map Viewer appropriately.

Note For details regarding the Event Browser and Map Viewer, see the Cisco Element Management Framework User Guide.

Step 6 Choose File > Close to close the SNMP Management window.

IOS Image Download

If you are familiar with other Cisco EMs, the IOS image download feature is typically available through the EM-specific menu initiated by right-clicking a relevant object in the Cisco EMF Map Viewer tool. Currently, Cisco IOS image management capabilities are provided through the Resource Manager Essentials (RME) which is now integrated into Cisco EMF. Using RME, you can upgrade the device with the current version of Cisco IOS image software.

Note For overview information on the RME tool and instructions specific to using RME with Cisco EMF, see the Cisco Element Management Framework Installation and Administration Guide and the Cisco Element Management Framework User Guide.

Note For detailed information on the RME tool, see the User Guide for Resource Manager Essentials.

Configuration Backup/Restore

Configuration backup and restore capabilities are now available through the RME application which is integrated into Cisco EMF. Using the RME application you can archive the network database as necessary.

Note For detailed information on the RME tool, see the User Guide for Resource Manager Essentials.

Profile Management

Profiles allow you to apply a set of existing parameters to a number of similar objects, eliminating the need to enter the same data numerous times. Once you create a profile, you can apply that same profile to any number of interfaces or connections as applicable, thus saving time and creating efficiency.

The following figure outlines the interface profile workflow.

Figure 5-8 Interface Profiles Workflow

:56582.bmp

Profile management involves the following:

Managing POS Interface Profiles

Managing POS Interface Profiles

Interface configuration profiles allow you to apply a single profile to multiple POS interfaces, thereby allowing you to reduce interface configuration efforts.

Managing POS interface profiles involves the following:

Creating and Configuring an POS Interface Profile

To create a POS interface profile, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration >
(Chassis >) Profile > POS Profile. For information on which objects allow you to launch the POS Profile Dialog window, see "EM Windows".

The POS Profile Dialog window appears displaying the POS Config tab.

Figure 5-9 POS Profile Dialog Window—POS Config Tab

Step 2 To create a profile based on an existing profile, select the profile you want to model from the profile list box on the left-hand side of the window (optional).

Step 3 Click Create Profile.

A Prompt window appears for you to enter a name for your new profile.

Figure 5-10 Prompt Window

Step 4 Enter a name for the new profile in the Enter profile name data entry box. Each profile must have a unique name. Do not insert spaces into a profile name. When you choose a profile name, it is recommended to use a naming convention that describes the profile type. For example, a POS profile might be called POS1 or POSInterface1.

Step 5 Click Ok.

The POS Profile Dialog window reappears with the new profile name displaying in the POS Interface list on the left-hand side of the window and default configuration data. Note that the first profile you create, the default data will most likely be inappropriate. Therefore you must configure each parameter as the following steps describe. If you chose to create the profile based on an existing profile, custom configuration data from the existing profile displays rather than default data.

TimeSaver In order to save time configuring similar profiles, you can apply an existing profile to a new profile. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles listed. The configuration settings copy from the existing profile to the new profile.

If you prefer to copy and paste individual parameters, or only a single tab of the configuration, you can copy and paste data between profiles as needed. Select the interface from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If copying a single setting, select the individual parameter. Choose Edit > Paste to paste the information.

The settings which copy appear in blue.

Step 6 Configure the parameters in the General area as follows:

POS SPE Scrambling— Allows you to scramble the POS SPE payload which is the payload carrying portion of the STS signal. The SPE is used to transport a tributary signal across the synchronous network. Options are enabled (default) or disabled.
Loopback — Select the desired loopback mode which is used to diagnose equipment malfunctions between the interface and device. Available options are:

Disabled — Disables loopback functionality.
Internal — Configures the loopback tests to be performed internally so that no loopback cable is required.
Line — Causes packets to be looped completely through the channel/digital service unit to configure the digital interface device loop.

Clock Source — Select the desired clock source which measures the speed of the device. Options are Internal (within the device) or Line (the network clock).
Keepalive — Set the keepalive period using a range of 0 to 30 seconds (defaults to 10 seconds). The system sends packets to determine if the interface or the network is up for routing packets.
POS Framing — Specify the type of framing used on the POS interface. Options are:

SDH (Synchronous Digital Hierarchy) — European standard that defines a set of rate and format standards that are transmitted using optical fiber signals.
SONET — Standard format for transporting a wide range of digital telecommunications services over optical fiber.

Encapsulation — Select the desired encapsulation type. Options are HDLC (default), PPP, pr Frame Relay.
Cyclic Redundancy Check — Select whether to use 16 or 32-bit verification code during a cyclic redundancy check. The code must be the same at both the transmitting and receiving ends to ensure that packets sent are received in full without loss of data.

Step 7 Configure the parameters in the SONET Overhead area as follows:

Path Signal Identifier — Set the path signal identifier using a value ranging from 0 to 255.
Section Trace Byte — Set the section trace byte using a value ranging from 0 to 255.
Payload Pointer Byte — Select the desired payload pointer byte. Options range from 0 to 3.

Step 8 Configure the parameters in the Alarm Reporting & Threshold area as follows:

B1 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B1 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
B2 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B2 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
B3 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B3 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
Signal Degrade BER/Threshold — Select whether to set a threshold limit for the system to prompt appropriate Signal Degrade BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
Signal Fail BER/Threshold — Select whether to set a threshold limit for the system to prompt appropriate Signal Fail BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.

Step 9 Configure the parameters in the Alarm Reporting area as follows:

Path Remote Defect Indication Errors — Enable or disable PRDI error alarm messages. A PRDI occurs when a specially allocated bit is "1" for 10 consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of 10 consecutive frames in which all of these types of bits are set to 0, a PRDI error occurs.
Line Remote Defect Indication Errors — Enable or disable LRDI error alarm messages. An LRDI defect occurs when 3 specially allocated bits are "110" for three consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than "110", an LRDI alarm is raised.
Line Alarm Indication Signal Errors — Enable or disable LAIS error alarm messages. A LAIS defect occurs when three specially allocated bits are all "1" for three consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than 1's, the LAIS alarm is reported.
Receive Data Out Of Lock Errors — Enable or disable Receive data out of lock error alarm messages. This type or error is detected when the clock recovery phased lock loop is unable to lock the receive stream.
Path Alarm Indication Signal Errors — Enable or disable PAIS error alarm messages. A PAIS defect occurs when a loss of signal, loss of frame, line alarm indication signal, or loss of pointer is detected on the incoming signal of an upstream network element. The PAIS is signalled to downstream elements.
Section Loss of Signal Errors — Enable or disable panel LOS error alarm messages. An LOS defect occurs when the OC-3 port receives all zeros for approximately 20 microseconds.
LAIS on Interface Shutdown — Enable or disable LAIS on interface shutdown alarm messages. A LAIS on Interface shutdown defect occurs when three specially allocated bits are all "1" for three consecutive frames on an interface shutdown. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than 1's, the LAIS on Interface Shutdown alarm is reported.
Section Loss of Frame Errors — Enable or disable panel LOF error alarm messages. An LOF defect occurs when an out-of-frame (OOF) condition occurs and does not clear for more than 3 microseconds.
Path Loss of Pointer Errors — Enable or disable path LOP error alarm messages. An LOP defect occurs when eight consecutive frames do not contain a valid pointer.

Step 10 Click the Save icon on the toolbar to save the parameters you have selected for your profile.

Step 11 Choose File > Close to close the POS Profile Dialog window.

You may proceed to the "Configuring an Interface" section for details on entering generic interface configuration and applying the POS profile to an appropriate interface.

Editing a POS Interface Profile

To edit a POS interface profile, proceed as follows:

The POS Profile Dialog window appears displaying the POS Config tab (see Figure 5-9).

Step 2 Choose the profile you wish to edit from the list of existing profiles which display in the POS Profile list on the left-hand side of the window.

Step 3 Edit the parameters as required. For parameter descriptions, see Steps 6 through 11 of the "Creating and Configuring an POS Interface Profile" section.

Step 4 Click the Save icon on the toolbar to save the parameters you have selected for your profile.

Step 5 Choose File > Close to close the POS Profile Dialog window.

Deleting a POS Interface Profile

To delete a POS interface profile, proceed as follows:

The POS Profile Dialog window appears displaying the POS Config tab (see Figure 5-9).

Step 2 Choose the profile you wish to delete from the list of existing profiles which display in the POS Profile list on the left-hand side of the window.

Step 3 Choose Edit > Delete Profile, then select the profile you wish to delete from the list.

A Deletion prompt window appears for you to confirm that you wish to delete the selected profile.

Step 4 Click Yes to delete the selected profile or click No to close the window without deleting the profile.

When a profile deletes it disappears from the list of existing profiles in the POS Profile list on the left-hand side of the window and an Information window appears.

Step 5 Click OK to close the Information window.

Step 6 Choose File > Close to close the POS Profile Dialog window.

Redundancy

When redundant PREs are present in the chassis, redundancy configuration and activation must take place. Redundancy functionality through the EM varies depending on the IOS image type running on the device, leased line or broadband. It is the IOS version type running on the device, leased line or broadband, that determines the redundancy data and configuration options available via the EM. IOS version-specific implications are detailed where applicable.

The Redundancy window allows you to perform the following tasks:

To display the Redundancy window, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Chassis) > Redundancy. For information on which objects allow you to launch the Redundancy window, see "EM Windows".

The Redundancy window appears.

Figure 5-11 Redundancy Window (Leased Line IOS Example)

Figure 5-12 Redundancy Window (Broadband IOS Example)

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

The PRE Status area displays status data for the PREs present in slots A and B of the selected chassis. Status data consists of the CPU Mode (active or standby) and the current CPU Status (ok, up or down).

The Redundancy Info area displays detailed information for chassis running leased line IOS. Chassis running broadband IOS display the Redundancy Mode Description, but no other data in this area is displayed. The Redundancy Info area displays the following:

Current Redundancy Mode—Indicates the type of redundancy currently in effect. Possible values are: nonRedundant, staticLoadShareNonRedundant, dynamicLoadShareNonRedundant, staticLoadShareRedundant, dynamicLoadShareRedundant, coldStandbyRedundant, warmStandbyRedundant, and hotStandbyRedundant.
Redundancy Mode Description—Further clarifies or describes the redundancy mode which displays in the Current Redundancy Mode field. Implementation-specific terminology associated with the current redundancy mode may be presented in this field (e.g., SSO, RPR+). Should the chassis not have redundant processors available, Simplex will display indicating that PRE redundancy functions are not currently available.
SysUpTime At Last Failover—Indicates the date and time when the most recent failover occurred. If a failover has never taken place on the system, this field displays as 00:00:00.
Last Failover Reason—Indicates the reason for the most recent failover. Possible values are: unsupported, none, notKnown, userInitiated, userForced, activeUnitFailed, and activeUnitRemoved.
Manual Switch Inhibit—Indicates whether a manual switch of activity is permitted. A switch of activity is the event in which the standby redundant unit becomes active and the previously active unit becomes the standby. If a manual switch of activity is allowed, this field displays the value false. If a manual switch of activity is not allowed, this field displays the value true.

The value in this field does not indicate whether a switch of activity has occurred. The value only indicates if the capability is enabled or not.

For detailed descriptions of the fields in the Auto-Sync area, see the following section, "Configuring Automatic Synchronization of Redundant PREs".

For instructions on the fields and buttons in the Actions area, see the "Configuring the Redundancy Mode of the Chassis" section and/or the "Forcing a Failover" section.

Step 3 Choose File > Close to close the Redundancy window.

Configuring Automatic Synchronization of Redundant PREs

Synchronizing redundant PREs allows you to copy data from the active PRE to the PRE in standby mode. PRE synchronization is available for data backup purposes or for use prior to forcing a failover. Once configured, synchronization occurs automatically to transfer data between the active and standby PREs when changes are saved to the appropriate configuration file. You may choose to deactivate automatic synchronizations by selecting the corresponding configuration option(s).

Automatic synchronization configuration is only applicable for devices running broadband IOS. Configuration file synchronization occurs automatically, by default, for devices running leased line IOS.

To configure automatic synchronization, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > (Chassis) >
Configuration > Redundancy. For information on which objects allow you to launch the Redundancy window, see "EM Windows".

The Redundancy window appears (see Figure 5-11).

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 3 Choose the appropriate option(s) from the Auto-Sync area by selecting yes or no from the appropriate pull-down lists. When yes is selected, continuous synchronization of data between the active and standby processor is enabled. The following options are available:

Standard—When selected, automatically synchronizes the start up and/or running configuration file as appropriate
RunningConfig—When selected, automatically synchronizes the running configuration file
StartupConfig—When selected, automatically synchronizes the startup configuration file
ConfigRegister—When selected, automatically synchronizes the configuration register
BootVar—When selected, automatically synchronizes the Bootvar file

Step 4 Click the Save icon on the toolbar to save your changes.

Following a change to the appropriate configuration file, the active PRE automatically begins to transfer the updated data to the standby PRE. Once the transfer is complete, the PREs are synchronized accordingly.

Choose File > Close to close the Redundancy window.

Configuring the Redundancy Mode of the Chassis

You can configure the redundancy mode as necessary for chassis running broadband IOS. This capability is not available for chassis with leased line IOS.

To configure the redundancy mode of the chassis, proceed as follows:

The Redundancy window appears (see Figure 5-11).

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 3 Choose the appropriate option from the Set Redundancy Mode pull-down list. Options are: SSO and RPR+.

Step 4 Click Change Mode.

The redundancy mode configures accordingly and the standby PRE reboots. The system operates in Simplex mode for several minutes during this time. When the standby PRE completes the boot sequence, the redundancy mode updates accordingly.

Step 5 Choose File > Close to close the Redundancy window.

Forcing a Failover

Manually forcing a failover essentially forcefully fails the active PRE and moves the standby PRE into the active role. Ensuring that the data on the standby processor is current, backing up the active processor to the standby processor before proceeding with the failover allows for a smooth transformation.

Forcing a failover reversal is not possible until the standby PRE becomes active.

To force failover, proceed as follows:

The Redundancy window appears (see Figure 5-11).

Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.

Step 3 Choose the appropriate option from the Synchronize Configuration on Failover pull-down list. Options are yes or no.

It is recommended that you always choose yes to transfer the configuration of the active PRE to the standby PRE before forcing a failover. Choosing yes enables a synchronization of the PREs to take place if needed. Choosing no disables configuration synchronization from occurring prior to a forced failover.

Step 4 Click Force Failover.

The following occurs within the chassis:

a. If you chose to synchronize the PREs before failing over, configuration data transfers from the active PRE to the PRE in standby mode as required.

b. The active PRE within the selected chassis moves into a failed state and the standby PRE automatically moves into the active role. The Status area updates to display the new active processor and, if the chassis is running leased line IOS, an informational alarm arises on the chassis to the effect that the chassis configuration has changed. An alarm does not occur when the selected chassis is running broadband IOS.

c. Ethernet ports on the active PRE prior to the failover are re-parented to the PRE that has assumed the active role and display accordingly on the Map Viewer.

Step 5 Choose File > Close to close the Redundancy window.

Module Configuration

The Configuration window allows you to commission or decommission any module. You can also provide textual descriptions of the specific module, if required.

The Module Configuration section provides the following information:

Configuring a Module

To configure a module, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Module >) Configuration. For information on which objects allow you to launch the Module Configuration window, see "EM Windows".

The Module Configuration window appears.

Figure 5-13 Module Configuration Window

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, then select a module from the Module list box.

Configuration data for the selected module appears in the Additional Descriptions area and the Commission Status area displays the status of the last commission performed on the selected module. Possible values are Succeeded or Failed.

Step 3 Enter additional descriptions into the Descriptions 1 and Descriptions 2 areas (optional) as required.

Step 4 Click the Save icon on the toolbar to save your changes.

Step 5 Choose File > Close to close the Chassis Configuration window.

Commissioning a Module

As previously described, there are several types of modules the EM supports, including line cards and supporting modules (e.g., power supplies and processors). Commissioning modules discovers and commissions the module and all the objects within the module when applicable, and begins heartbeat polling. Overall, successful commissioning places the module in a manageable state (by the EM).

The following lists the activities which occur when commissioning line cards and processor modules.

Commissioning a module initiates the following activities for modules present in the device:

All interfaces on the line card also commission
Heartbeat polling begins on the line card and interfaces
The line card and active interfaces move into the normal state
Status data becomes available on the line card and interfaces

Commissioning any supporting module present in the device initiates the following activities:

Heartbeat polling begins on the object
The state changes to normal
Status data becomes available

Module commissioning also preprovisions manually deployed modules which are not yet present in the device and are in a given state (normal, performance logging on, or synchronizing.) Module preprovisioning creates a place holder for the specific card within the device through the commissioning process. Preprovisioning allows for configuration to occur in advance of the module being physically present via the EM and/or IOS commands. Following the commissioning process, predeployed modules which are not yet present in the device enter the preprovisioned state.

Once preprovisioned modules are present within the device, all configuration parameters entered through the EM or via IOS commands are applied to the card during discovery.

To commission and preprovision a module, proceed as follows:

The Module Configuration window appears (see Figure 5-13).

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, then select a module from the Module list box.

Step 3 Ensure the module has proper configuration. For information on module configuration attributes, see the "Module Configuration" section.

Step 4 Click Commission (located in the Actions area).

The module and all objects it contains commission through discovery. An Action Report window appears displaying the outcome of the module commission. Additionally, status information displays in the Commission Status area of the Module Configuration window reiterating the outcome of the commissioning action as either Succeeded or Failed.

When viewing the Module Configuration window in future instances, the Commission Status area displays the result of the last commission action, either Succeeded or Failed.

Step 5 Click Close to close the Action Report window.

Step 6 Choose File > Close to close the Module Configuration window.

Unprovisioning a Module

Preprovisioned modules may be unprovisioned as required.

To unprovision a module, right-click on the relevant module object and choose
Cisco 10000 Series Manager > Configuration > Unprovision.

The module state changes from preprovisioned to decommissioned. While the module object remains in the EM views, the device no longer regards the module for the specified slot. Upon completion, an Action Results window displays indicating the unprovisioning of the module.

Decommissioning a Module

Decommissioning modules also decommissions all objects beneath the card. As a part of decommissioning, heartbeat polling, status gathering, and performance monitoring terminates. These activities put the module in a state that is unmanageable from the EM.

The following lists the activities which occur when decommissioning line cards and supporting modules.

Decommissioning a module initiates the following activities:

All interfaces and ATM connections on the line card are also decommissioned
Heartbeat polling stops on the line card and interfaces
The line card, interfaces, and ATM connections are placed in the decommissioned state
Status data is no longer available on the line card and interfaces
Performance polling stops on the line card and interfaces (if enabled)

Decommissioning any supporting module initiates the following activities:

Heartbeat polling stops on the object
The state changes to decommissioned
Status data is no longer available
Performance polling stops on the module (if enabled)

It is recommended that you decommission a module prior to physically removing it from a managed chassis. Decommissioning a module before physically removing it prevents alarms.

To decommission a module, proceed as follows:

The Module Configuration window appears (see Figure 5-13).

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, then select a module from the Module list box.

Step 3 Click Decommission to decommission the selected module.

The module and all objects contained within are decommissioned. Decommissioned objects remain in the left-hand pane of the Map Viewer window and appear grayed out in the chassis map in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome. If decommissioning is successful, the state of the module and objects contained within change to decommissioned.

Step 4 Choose Close to close the Action Report window.

Step 5 Choose File > Close to close the Module Configuration window.

Interface Configuration

Interfaces on modules can support multiple technologies. Configuration windows are technology-specific. You can configure or set up any interface through the Interface Configuration windows associated with each line card. The following table outlines which technology-specific configuration windows support each interface type.

Table 5-1 Interfaces and Configuration Windows

Interfaces	Technology-Specific Configuration Windows
Generic	Generic, ATM, SONET, Ethernet, IP, DS1, DS3, POS
ATM	Generic, ATM
Ethernet	Ethernet, IP
IP	IP, Ethernet, ATM, SONET, DS1, DS3, POS

To properly configure an interface, configuration data for each of the applicable windows should be entered.

In lieu of performing redundant configurations on similar objects, you may alternatively apply pre-defined interface configuration profiles to the appropriate interface type. ATM profiles support ATM interface configuration and HSRP profiles support Ethernet and IP interface configurations. The corresponding configuration procedures indicate how to apply these profiles at the appropriate time. To pre-define interface profiles, see the "Profile Management" section.

The Interface Configuration section covers the following:

Commissioning an Interface

To commission an interface, follow these steps:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration >
(Interface >) Configuration. For information on which objects allow you to launch the Generic Interface Configuration window, see "EM Windows".

The Generic Interface Configuration window appears.

Figure 5-14 Generic Interface Configuration Window—Configuration Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the Interface list box.

Configuration data for the selected interface appears in the Configurable Parameters panel.

Step 3 Ensure the interface has proper configuration. For information on interface configuration attributes, see the "Configuring an Interface" section.

Step 4 Click Commission (in the Actions area).

The status of the selected interface appears at the bottom left-hand corner of the window, and a Confirmation window appears.

Step 5 Click Yes to commission the interface or click No on the Confirmation window to cancel the operation at this time.

The interface discovers and commissions, and the interface's state changes accordingly. A status report appears displaying whether the commission action successful or fails.

Step 6 Click Close to close the Action Report window.

Step 7 Choose File > Close to close the Generic Interface Configuration window.

Decommissioning an Interface

To decommission an interface, follow these steps:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Interface >) Configuration. For information on which objects allow you to launch the Generic Interface Configuration window, see "EM Windows".

The Generic Interface Configuration window appears (see Figure 5-14).

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the Interface list box.

Configuration data for the selected interface appears in the Configurable Parameters panel.

Step 3 Click Decommission (in the Actions area).

The status of the selected interface appears at the bottom left-hand corner of the window, and a Confirmation window appears.

Step 4 Click Yes to decommission the interface or click No on the Confirmation window to cancel the operation at this time.

The interface is decommissioned and the interface's state changes accordingly. A status report appears displaying whether the commission action is successful or fails.

Step 5 Click Close to close the Action Report window.

Step 6 Choose File > Close to close the Generic Interface Configuration window.

Configuring an Interface

Interfaces require some level of configuration before the EM can manage them effectively. In order to successfully configure an interface, no matter the type, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

When interface configuration is complete, the interface may be commissioned to enable the EM to manage it.

To configure general interface criteria, proceed as follows:

The Generic Interface Configuration window appears.

Figure 5-15 Generic Interface Configuration Window—Configuration Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the Interface list box.

Configuration data for the selected interface appears in the Configurable Parameters area. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

If the interface is in the normal state or any other post-commissioned state, you may proceed. If the interface is in the decommissioned state, you must first commission the interface before continuing with the interface configuration. To commission an interface, see the "Commissioning an Interface" section.

Step 4 Configure the attributes in the Configurable Parameters area as follows:

Alias—Enter the name for the interface as the network manager specifies.
Administration Status—Select the administration status for the interface. Options are: up, down, or testing.
Link Up/Down Trap Status—Enable or disable link up/down trap generation for the selected interface by selecting the corresponding option.
Supplementary Information—Enter additional information about the interface as desired.

Step 5 Click the Save icon on the toolbar to save your changes.

Step 6 Choose File > Close to close the Generic Interface Configuration window.

If the EM supports the technology-specific configuration of the interface for which you have set general configuration parameters, you may further configure the interface. Proceed to one of the following sections:

Configuring an ATM Interface

In order to successfully configure an interface, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

To configure an ATM interface, proceed as follows these steps:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Interface >) ATM. For information on which objects allow you to launch the ATM Interface Configuration window, see "EM Windows".

The ATM Interface Configuration window appears displaying the Configuration (1) tab.

Figure 5-16 ATM Interface Configuration Window—Configuration (1) Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the ATM Interface list box.

Configuration data for the selected interface appears on the Configuration (1) and Configuration (2) tabs. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

TimeSaver In order to save time configuring interfaces, you can apply an existing profile to populate the configuration parameters. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles listed. The configuration settings copy from the profile to the configuration of the interface.

If you prefer to copy and paste individual parameters, or only a single tab of the configuration, you can copy and paste data between profiles as needed. Select the interface from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information.

The settings which copy appear in blue.

Step 4 Configure the parameters in the ATM Configuration panel as follows:

Neighbor IP Address—Displays the IP address of the device at the remote end of the link
Interface Type—Select the interface type. The following options are available: other, uni, pnni, iisp, and nniPvcOnly.
ATM Interface Side—Select the appropriate ATM interface side option, including: user, network, and notApplicable.
SVC UPC Intent—Select the usage parameter control action to take for SVCs established through the network. Options are: passing, tagging or dropping.
Loopback—Select the loopback mode. The following options are available: noLoopback, diagnostic, and line.
Maximum VPCs—Enter the maximum number of Virtual Path Connections permitted.
Maximum VCCs—Enter the maximum number of Virtual Channel Connections (PVCs and SVCs) supported at this interface.
Number of VCs per VP—Enter the number of virtual channel per virtual path.
Clock Source—Select the source of the clock. Choose internal if the local clock is to be used, or none if no clock source is to be used.
NSAP Address—Enter the Network Service Access Point (NSAP) address for the interface. The NSAP address is used for establishing SPVCs.
Neighbor Interface Name—Displays the interface name of the device at the remote end of this link.
UNI Type—Select the appropriate UNI type, public or private.
UNI Signalling Version—Select the version of UNI signalling that is currently being used on the interface. The appropriate value, either atmfUni3Dot0, atmfUni3Dot1, or atmfUni4Dot0, is used when the interface is an UNI or IISP interface. The value not applicable is used when the interface is a PNNI interface or when signalling is disabled. Setting this variable to a value of not applicable is not allowed if the interface type is UNI or IISP. To modify this field, the interface Ilmi auto configuration parameter must be set to disabled.
Signalling Admin Status—Select the appropriate option to enable or disable the signaling/SSCOP on the interface.
Well-known VC Mode—Select whether well-known VCs are automatically or manually created for the interface. Descriptions of the available options follow:

automatic—Well-known VCs created with default VPI/VCI values upon startup or upon entry to the automatic mode. While in this mode, you may not delete or modify well-known VCs. This is the default value.
manual—Well-known VCs are not automatically created. Instead, you may create and delete PVCs with the reserved encapsulation types aalQsAal, aal5Ilmi, and aal5Pnni as applicable. These PVCs have VCI values of 5, 16, and 18 for QSAAL, ILMI, and PNNI functions, respectively.
manualDeleteUponEnabled—Causes any existing VCs with reserved encapsulation types (e.g., allQsAal, aal5Ilmi, or aal5Pnni) to be deleted from the interface as it enters the manual state.

Transmit Queue Limit—Enter the maximum of the transmit queue length.
Maximum Active VPI Bits—Enter the maximum allowable active VPI bits for use at this interface.
Maximum Active VCI Bits—Enter the maximum allowable active VCI bits for use at this interface.

Step 5 Configure the parameters in the ILMI Configuration panel as follows:

Keepalive Time—Enter the amount of time (in seconds) that should elapse between successive ILMI keepalive messages sent on this interface. A value of 0 disables ILMI keepalive messages on this interface.
Auto-Configuration—Determines the interface type when the interface initiates. When enabled, the local and remote devices negotiate the following parameters: Interface Type, Interface Side, UNI Type, UNI Signalling Version, Maximum Active VPI Bits, and Maximum Active VCI Bits. If the devices are unable to negotiate these parameters, you must disable the Auto-Configuration setting in order to configure the fields mentioned manually. After configuring the field to disabled, save this setting before making additional configuration selections.

Attempting to save configuration parameters after setting the Auto-Configuration field to disable results in error if the Auto-Configuration field disabled setting was not saved first.

Address Registration—You can enable or disable ILMI Address Registration on this interface. The configuration takes effect only on the next interface restart.
Trap—Allows you to enable or disable the ILMI traps.
Configuration—Enable or disable ILMI configuration on this interface. The configuration takes effect only on the next interface restart. Disabling this object will also disable address registration, auto-configuration, and keepalive time.

Step 6 Choose the Configuration (2) tab.

The ATM Interface Configuration window displays the Configuration (2) tab.

Figure 5-17 ATM Interface Configuration Window—Configuration (2) Tab

Step 7 The Information Element Transfer area allows you to enable or disable the following attributes. For all fields, Enabled allows for the element to be transferred to the called party; Disabled does not allow for the transfer to take place. Configure the parameters in the Information Element Transfer panel by selecting Enabled or Disabled from the following fields:

Broadband High Layer—Indicates whether to accept, transfer, and deliver the broadband high layer information element from the calling party to the called party.
Broadband Low Layer—Indicates whether to accept, transfer, and deliver the broadband low layer information element from the calling party to the called party.
Broadband Repeat Indicator—Indicates whether to accept, transfer, and deliver the broadband repeat indicator information element from the calling party to the called party.
Calling Party Subnet Address—Indicates whether to accept, transfer, and deliver the calling party subnet address information.
Calling Party Number—Indicates whether the calling party number information element is transferred to the called party.
Called Party Subnet Address—Indicates whether to accept, transfer, and deliver the called party subnet address information.
ATM Adaption Layer Parameters—Indicates whether to accept, transfer, and deliver the ATM adaptation layer parameters.
Unknown Information Element—Indicates whether to accept, transfer, and deliver the unknown information element from the calling party to the called party.

Step 8 Configure the parameters in the Physical Layer area as follows:

Transmit Clock Source—Select the source of the clock transmission. Options are:

loopTiming—Recovered received clock is used as the transmit clock
freeRunning—Local clock source is used
networkDerived—Recovered clock source from another interface is used as the transmit clock source

Clock Source Priority—Select the clock source priority. Priorities 1 through 4 are available options, as well as notConfigured. The notConfigured option indicates that there is not a network clock source configured.
Line Coding—Select the appropriate line coding option; ami, b8zs or hdb3. Descriptions of each option follow.

ami—Alternative mark inversion line code on a DS1/E1 interface
8zs—B8ZS line code on the physical interface; applies only to DS1 interfaces
hdb3—HDB3 line code on the physical interface; applies only to E1 interfaces

Loopback Configuration—Select the appropriate loopback configuration option:

noLoop—Loopback configuration does not exist
diagnosticLoop—Transmit data stream is looped to the receive direction
lineLoop—Receive data stream is looped to the transmit direction
otherLoop—Loopback configuration exists, but it is neither diagnostic nor line

Cell Payload Scrambling—Turn cell payload scrambling on or off by choosing the corresponding option.
STS-Stream Scrambling—Turn STS-stream scrambling on or off by choosing the corresponding option. The STS-Stream Scrambling parameter is only applicable to SONET.

Step 9 Configure the parameters in the DS1/E1/DS3/E3 area as follows:

Line Buildout—Select the appropriate line buildout configuration value. Available values are:

e3AllCables—E3 physical interfaces cables
ds3CablesUnder225—Cables under 225 feet of DS3 physical interfaces
ds3CablesOver225—Cables over 225 feet of DS3 physical interfaces
ds1Cables0To110—Cables 0 to 110 feet of DS1 physical interfaces
ds1Cables110To220—Cables 110 to 220 feet of DS1 physical interfaces
ds1Cables220To330—Cables 220 to 330 feet of DS1 physical interfaces
ds1Cables330To440—Cables 330 to 440 feet of DS1 physical interfaces
ds1Cables440To550—Cables 440 to 550 feet of DS1 physical interfaces
ds1Cables550To660—Cables 550 to 660 feet of DS1 physical interfaces
ds1CablesOver600—Cables over 600 feet of DS1 physical interfaces
e1AllCables—E1 physical interfaces cable

Framing Mode—Select the appropriate framing mode option. Available framing modes are:

sonet—sts-3c or sts-12c format and applies only to OC-3 and OC-12 type interface, respectively
sdh—stm1 or stm4 format and applies only to OC-3 and OC-12 type interface, respectively
ds3m23adm—M23 ADM mode and applies only to DS3 type interface
ds3m23plcp—M23 PLCP mode and applies only to DS3 type interface
ds3cbitadm—C-BIT ADM mode and applies only to DS3 type interface
e3g832adm—G.832 ADM mode and applies only to E3 type interface
e3g751adm—G.751 ADM mode and applies only to E3 type interface
e3g751plcp—G.751 PLCP mode and applies only to E3 type interface
ds1sfadm—DS1 SF ADM mode and applies only to DS1 type interface
ds1esfadm—DS1 ESF ADM mode and applies only to DS1 type interface
ds1sfplcp—DS1 SF PLCP mode and applies only to DS1 type interface
ds1esplcp—DS1 ESF PLCP mode and applies only to DS1 type interface
e1adm—E1 ADM mode and applies only to E1 type interface
e1plcp—E1 PLCP mode and applies only to E1 type interface
e1crcadm—E1 CRC-4 ADM mode and applies only to E1 type interface
e1crcplcp—E1 CRC-4 PLCP mode and applies only to E1 type interface

Step 10 Click the Save icon on the toolbar to save the parameter configuration.

Step 11 Choose File > Close to close the ATM Interface Configuration window.

Configuring an Ethernet Interface

The Ethernet Interface Configuration window allows you to configure Ethernet fields, such as loopback, keepalive period, and MAC address.

In order to successfully configure an interface, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

To configure an Ethernet interface, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Interface >) Ethernet. For information on which objects allow you to launch the Ethernet Interface Configuration window, see "EM Windows".

The Ethernet Interface Configuration window appears displaying the Configuration tab.

Figure 5-18 Ethernet Interface Configuration Window—Configuration Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the Ethernet Interface list box.

Configuration data for the selected interface appears on the Configuration and HSRP Parameters tabs. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

TimeSaver In order to save time configuring interfaces, you can apply an existing profile to populate the configuration parameters. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles listed. The configuration settings copy from the profile to the configuration of the interface.

If you prefer to copy and paste individual parameters, or only a single tab of the configuration, you can copy and paste data between profiles as needed. Select the profile from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information.

The settings which copy appear in blue.

Step 4 Configure the parameters in the General area as follows:

Loopback—Select one of the following options:

Internal—No cable is needed to connect the input and output ports. The data is looped back within the device itself. Applicable only for Gigabit and Fast Ethernet interfaces.
External—Input and output ports are physically connected by a cable to simulate a loopback. When data is transmitted, it travels through the output port and enters the device through the input port. Applicable only for Gigabit and Fast Ethernet interfaces.
Enabled—Packets are transmitted back to the source to test the interface functionality and ensure that packets transmitted through the interface reach the destination.

If the communication link to the Cisco router is lost, it cannot be switched on again from Cisco EMF. Access to the Cisco router is required before the link can be re-enabled.

Disabled—Disables switches loopback off for Fast and Gigabit Ethernet interfaces.

Keepalive Period—Displays set the keepalive period. The system sends packets to know if the interface or the network is up for routing packets. By default it is 10 seconds.

Step 5 Click the HSRP Parameters tab.

The Ethernet Interface Configuration window displays the HSRP Parameters tab.

Figure 5-19 Ethernet Interface Configuration Window—HSRP Parameters Tab

The Configured Group Numbers attribute lists the number of configured HSRP groups.

Step 6 Configure the fields in the HSRP Parameters area as follows:

Group Number—Enter the group number on the interface for which HSRP is being activated. The default is zero.
Standby Priority—Enable or disable the priority for the HSRP interface. Select one of the possible values:

Enabled—When the current interface fails, it automatically switches to the standby interface.
Disabled—When the current interface fails, it does not switch to a standby interface.

Standby Authentication—Enable or disable the standby authentication string. Select on of the following options:

Enabled—Checks for an authentication string set and allows you to configure the interface on presence of the set string.
Disabled—Does not check for an authentication string.

Standby Hello Time—Enter and integer (in seconds) between 1 and 255. The default is 3 seconds.
Standby Preempt—Select either enabled or disabled. When enabled, the standby router waits for the set time and takes over as active router if the current router fails or does not respond to the packets sent. When disabled, no action automatically takes place in the described situation.
IP Address—Enter the IP address of the hot standby router interface.
Priority—Enter the priority value that prioritizes a potential hot standby router. The range is 0 to 255; the default is 100.
Authentication String—Enter a valid authentication string up to eight characters in length to serve as a check to avoid any damage to the interface. The default string is "cisco."
Standby Hold Time—Enter the time, in seconds, before the active or standby router is declared to be down. This entry must be an integer of 1 to 255. The default is 10 seconds.

Step 7 Click the Save icon on the toolbar to save the parameter configuration.

Step 8 Choose File > Close to close the Ethernet Interface Configuration window.

Configuring an IP Interface

In order to successfully configure an interface, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

To configure an IP interface, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Interface >) IP. For information on which objects allow you to launch the IP Configuration window, see "EM Windows".

The IP Configuration window appears.

Figure 5-20 IP Configuration Window—Generic Parameters Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the IP Interface list box.

Configuration data for the selected interface appears in the Generic Parameters panel. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

TimeSaver In order to save time configuring interfaces, you can apply an existing profile to populate the configuration parameters. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles which appear. The configuration settings are copied from the profile to the configuration of the interface.

If you prefer to copy and paste individual parameters, or only a single tab of the configuration, you can copy and paste data between profiles as needed. Select the profile from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information.

The settings which copy appear in blue.

Step 4 Configure the parameters in the Generic Parameters panel as follows:

IP Address—Enter the IP address for the selected chassis.
Subnet Mask—Enter the address mask for the selected chassis.
Maximum Transmission Unit—Enter the maximum packet size, in bytes, that the selected interface can handle.
IP Maximum Transmission Unit — Enter the maximum IP packet size (in bytes) that the selected interface can handle. This value should be less than the configured MTU.
Interface State—Select the interface state to be used, enabled or disabled, from the drop down list.
Cisco Discovery Protocol (CDP)—Enable or disable CDP on the chassis by selecting the appropriate option. CDP allows a device to advertise its existence to other devices and receive information about other devices on the same LAN or on the remote side of a WAN.
IP Multicast Fast Switching—Enable or disable IP Multicast Fast Switching on the chassis by selecting the appropriate option.

Step 5 Click the Save icon on the toolbar to save the parameter configuration.

Step 6 Choose File > Close to close the IP Configuration window.

Configuring a DS3/E3 Interface

In order to successfully configure an interface, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

To configure a DS3/E3 interface, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration >
(Interface >) DS3. For information on which objects allow you to launch the Manage DS3/E3 Interface Configuration window, see "EM Windows".

The Manage DS3/E3 Interface Configuration window appears.

Figure 5-21 Manage DS3/E3 Interface Configuration Window—Configuration Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the DS3/E3 Interface list box.

Configuration data for the selected interface appears in the Configuration panel. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

If the interface is in the normal state or any other post-commissioned state, you may proceed. If the interface is in the decommissioned state, you must first commission the interface before continuing. To commission an interface, see the "Interface Configuration" section.

TimeSaver In order to save time configuring interfaces, you can apply an existing profile to populate the configuration parameters. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles which appear. The configuration settings are copied from the profile to the configuration of the interface.

If you prefer to copy and paste individual parameters, you can copy and paste data between profiles as needed. Select the profile from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information.

The settings which copy appear in blue.

Step 4 Configure the parameters in the Configuration panel as follows:

Circuit Identifier — Displays the transmission vendor's circuit identifier for the purpose of facilitating troubleshooting.
Transmit Clock Source — Displays the source of the transmit clock which is derived from the recovered receive clock of another DS3 interface.
Loopback Config — Displays the loopback configuration of the DS3/E3 interface. Possible values are:

dsx3NoLoop — Not in the loopback state. A device that is not capable of performing a loopback on the interface always returns this value.
dsx3PayloadLoop — The received signal at this interface is looped through the device. Typically, the received signal is looped back for retransmission after it has passed through the device's framing function.
dsx3LineLoop — The received signal at this interface does not go through the device (minimum penetration) but is looped back out.
dsx3OtherLoop — Loopbacks that are not defined here.

Line Type — Indicates the variety of DS3 C-bit or E3 application implementing this interface. The type of interface affects the interpretation of the usage and error statistics. The rate of DS3 is 44.736 Mbps and E3 is 34.368 Mbps.

Step 5 Click the Save icon on the toolbar to save the parameter configuration.

Step 6 Choose File > Close to close the Manage DS3/E3 Interface Configuration window.

Configuring a POS Interface

In order to successfully configure an interface, the interface must be in a commissioned state. To commission an interface, see the "Commissioning an Interface" section.

To configure an POS interface, proceed as follows:

Step 1 Right-click on a relevant object and choose Cisco 10000 Series Manager > Configuration > (Interface >) POS. For information on which objects allow you to launch the POS Interface Configuration window, see "EM Windows".

The POS Interface Configuration window appears.

Figure 5-22 POS Interface Configuration Window—POS Config Tab

Step 2 Select a chassis from the Chassis list box on the left-hand side of the window, select a module from the Module list box, then select an interface from the POS Interface list box.

Configuration data for the selected interface appears in each panel in the window. If configuration has not yet taken place from the EM, configuration data populates the attributes according to the information available on the device.

Step 3 Ensure that the interface is in a post-commissioning state by reviewing the interface status in the lower left-hand corner of the window.

TimeSaver In order to save time configuring interfaces, you can apply an existing profile to populate the configuration parameters. Choose Edit > Apply Profile, then choose the existing profile you wish to apply from the profiles which appear. The configuration settings are copied from the profile to the configuration of the interface.

If you prefer to copy and paste individual parameters, or only a single tab of the configuration, you can copy and paste data between profiles as needed. Select the profile from which you want to copy data, then click the tab where the data you want to copy exists. To copy a specific setting, select the item you want to copy, then choose the Edit > Copy. To copy all settings on a specific tab, choose Edit > Copy Page Configuration. Select the profile to which you want to add the information, click the appropriate tab as necessary. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information.

The settings which copy appear in blue.

Step 4 Configure the parameters in the General area as follows:

POS SPE Scrambling— Allows you to scramble the POS SPE payload which is the payload carrying portion of the STS signal. The SPE is used to transport a tributary signal across the synchronous network. Options are enabled (default) or disabled.
Loopback — Select the desired loopback mode which is used to diagnose equipment malfunctions between the interface and device. Available options are:

Disabled — Disables loopback functionality.
Internal — Configures the loopback tests to be performed internally so that no loopback cable is required.
Line — Causes packets to be looped completely through the channel/digital service unit to configure the digital interface device loop.

Clock Source — Select the desired clock source which measures the speed of the device. Options are Internal (within the device) or Line (the network clock).
Keepalive — Set the keepalive period using a range of 0 to 30 seconds (defaults to 10 seconds). The system sends packets to determine if the interface or the network is up for routing packets.
POS Framing — Specify the type of framing used on the POS interface. Options are:

SDH (Synchronous Digital Hierarchy) — European standard that defines a set of rate and format standards that are transmitted using optical fiber signals.
SONET — Standard format for transporting a wide range of digital telecommunications services over optical fiber.

Encapsulation — Select the desired encapsulation type. Options are HDLC (default), PPP, pr Frame Relay.
Cyclic Redundancy Check — Select whether to use 16 or 32-bit verification code during a cyclic redundancy check. The code must be the same at both the transmitting and receiving ends to ensure that packets sent are received in full without loss of data.

Step 5 Configure the parameters in the SONET Overhead area as follows:

Path Signal Identifier — Set the path signal identifier using a value ranging from 0 to 255.
Section Trace Byte — Set the section trace byte using a value ranging from 0 to 255.
Payload Pointer Byte — Select the desired payload pointer byte. Options range from 0 to 3.

Step 6 Configure the parameters in the Alarm Reporting & Threshold area as follows:

B1 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B1 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
B2 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B2 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
B3 BER Threshold Crossing Alarm/Threshold — Select whether to set a threshold limit for the system to prompt appropriate B3 BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
Signal Degrade BER/Threshold — Select whether to set a threshold limit for the system to prompt appropriate Signal Degrade BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.
Signal Fail BER/Threshold — Select whether to set a threshold limit for the system to prompt appropriate Signal Fail BER Threshold alarm messages. If selected, enter the corresponding Threshold value (in 10e-) using a range from 3 to 9.

Step 7 Configure the parameters in the Alarm Reporting area as follows:

Path Remote Defect Indication Errors — Enable or disable PRDI error alarm messages. A PRDI occurs when a specially allocated bit is "1" for 10 consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of 10 consecutive frames in which all of these types of bits are set to 0, a PRDI error occurs.
Line Remote Defect Indication Errors — Enable or disable LRDI error alarm messages. An LRDI defect occurs when 3 specially allocated bits are "110" for three consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than "110", an LRDI alarm is raised.
Line Alarm Indication Signal Errors — Enable or disable LAIS error alarm messages. A LAIS defect occurs when three specially allocated bits are all "1" for three consecutive frames. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than 1's, the LAIS alarm is reported.
Receive Data Out Of Lock Errors — Enable or disable Receive data out of lock error alarm messages. This type or error is detected when the clock recovery phased lock loop is unable to lock the receive stream.
Path Alarm Indication Signal Errors — Enable or disable PAIS error alarm messages. A PAIS defect occurs when a loss of signal, loss of frame, line alarm indication signal, or loss of pointer is detected on the incoming signal of an upstream network element. The PAIS is signalled to downstream elements.
Section Loss of Signal Errors — Enable or disable panel LOS error alarm messages. An LOS defect occurs when the OC-3 port receives all zeros for approximately 20 microseconds.
LAIS on Interface Shutdown — Enable or disable LAIS on interface shutdown alarm messages. A LAIS on Interface shutdown defect occurs when three specially allocated bits are all "1" for three consecutive frames on an interface shutdown. This occurrence begins the alarm integration period. If this period elapses without the detection of three consecutive frames in which these bits show any pattern other than 1's, the LAIS on Interface Shutdown alarm is reported.
Section Loss of Frame Errors — Enable or disable panel LOF error alarm messages. An LOF defect occurs when an out-of-frame (OOF) condition occurs and does not clear for more than 3 microseconds.
Path Loss of Pointer Errors — Enable or disable path LOP error alarm messages. An LOP defect occurs when eight consecutive frames do not contain a valid pointer.

Step 8 Click the Save icon on the toolbar to save the parameter configuration.

Step 9 Choose File > Close to close the POS Interface Configuration window.

Table of Contents

Configuration

Chassis Configuration

Management Information

System Configuration

Managing Username and Passwords

Chassis Configuration

Configuring the Chassis

Commissioning a Chassis

Decommissioning a Chassis

Starting Global Performance Logging

Stopping Global Performance Logging

Writing a Running Config

SNMP Management

Configuring SNMP Community Names and Versions

Enabling or Disabling Trap Generation

IOS Image Download

Configuration Backup/Restore

Profile Management

Managing POS Interface Profiles

Creating and Configuring an POS Interface Profile

Editing a POS Interface Profile

Deleting a POS Interface Profile

Redundancy

Configuring Automatic Synchronization of Redundant PREs

Configuring the Redundancy Mode of the Chassis

Forcing a Failover

Module Configuration

Configuring a Module

Commissioning a Module

Unprovisioning a Module

Decommissioning a Module

Interface Configuration

Commissioning an Interface

Decommissioning an Interface

Configuring an Interface

Configuring an ATM Interface

Configuring an Ethernet Interface

Configuring an IP Interface

Configuring a DS3/E3 Interface

Configuring a POS Interface