|
|
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, interface, an connection configuration.
The Configuration chapter details the following:
The Chassis Configuration section covers the following areas:
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:
To configure the fields within the Configuration tab, proceed as follows:
The Management Information window appears displaying the Configuration tab.
Step 2 Select an IOS Host from the corresponding list box on the left-hand side of the window.
The IP address of the device displays in the corresponding field.
Step 3 Configure the fields on the Configuration tab as follows:
Step 4 Click the Save icon on the toolbar to save your changes.
Step 5 Choose File > Close to close the Management Information window.
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 EM password sets, and the local and device chassis passwords are now the same. Once the EM and device chassis passwords match, you may modify the password as you see fit and choose the Save to Device option; changing the chassis password locally within the EM and to 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.
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.
Step 3 Enter the appropriate information in the Security Details fields as follows:
Step 4 If you know the passwords that are set on the device, perform one of the following:
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.
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:
To configure the chassis, proceed as follows:
The Chassis Configuration window appears displaying the 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:
Step 4 Configure the system actions to be taken in the event of a system failure in the Action fields as follows:
Step 5 Configure the parameters in the Clock area as follows:
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.
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.
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 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 Catalyst 8540 MSR 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.
The Cisco Catalyst 8510 MSR and LS1010 chassis maps do not look the same as the 8540.
After commissioning a chassis you can configure and manage the chassis objects.
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.
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.
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.
|
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 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.
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.
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.
The SNMP Management section covers the following areas:
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:
The SNMP Management window appears displaying the 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 Select the SNMP version to be used from the SNMP Version option list.
Note that the C8500MGR currently does not support SNMP v1.
Step 4 Enter the appropriate Community Name information as follows:
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 5 Click the Save icon on the toolbar to save your changes.
Step 6 Choose File > Close to close the SNMP Management window.
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 Catalyst 8500 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:
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.
The IOS Image Download window allows you to download a current version of the Cisco IOS image software onto your device manually, or automatically (at a pre-scheduled time).
Before attempting an IOS image download, ensure that the Login and Exec Passwords are set and saved (by clicking Save Locally on the IOS/Command Line Security tab in the Management Information window). For details, see the "Managing Username and Passwords" section.
To download the IOS image, proceed as follows:
The IOS Image Download window appears displaying the Download tab.
Step 2 Select the relevant IOS host from the IOS Host list box on the left-hand side of the window.
The current configuration and status data displays. The Status area displays the last download operation, including the date and time of the last download.
Step 3 Configure the fields in the Configuration area as follows:
If you choose to enable the reset device using new image option, you must also configure the register setting to a value between 0x02 and 0x0F for the Cisco Catalyst 8500 router chassis using IOS CLI commands. Only then will the reboot with new image function correctly.
Step 4 Click the Save icon on the toolbar to save your changes.
Step 5 Before initiating an IOS image download, confirm the following:
Step 6 You can manually initiate a download or schedule a download to occur at a specific time. Perform one of the following:
An Action Report window appears detailing the Cisco IOS commands which execute. Invalid Cisco IOS commands result in a failure to commission the service.
a. Check the details in the Action Report window to ensure that the download was successful.
b. Click Save to save the action report when required.
c. Click Close to close the Action Report window and return to the IOS Image Download window.
The Schedule dialog box appears. The Schedule dialog box allows you to specify a date and time when the download is to initiate.
a. Enter a date and time (in mm/dd/yyyy and hh:mm formats respectively) when the download is to take place automatically, then click Ok to save the new date and time.
An Action Report window appears. The Action Report window details the Cisco IOS commands which execute. Invalid Cisco IOS commands result in a failure to download.
b. Check the details in the Action Report window to ensure that the download schedule is setup successfully. You can click Save to save the action report when required.
c. Click Close to close the Action Report window and return to the Cisco IOS Image Download window.
Step 7 Choose File > Close to close the Cisco IOS Image Download window.
The Configuration Backup\Restore window allows you to download the current running configuration from a specific device and save it as a file to any Trivial File Transfer Program (TFTP) server (i.e., backup). You can later download the backup file from the TFTP server to a specific device (i.e., restore).
Backup\Restore is available on a per chassis basis. That is, only the chassis may be selected for backup. When the chassis archives, all underlying objects archive as well). Individual module backup is not available in C8500MGR.
Regular configuration backups allow recovery in the unlikely event of a hardware failure. For example, if a module were to fail, you could insert a replacement module into the chassis and then restore the configuration data. Any changes in configuration data between the last backup and the time of the failure are lost. To minimize data loss, it is recommended that you back up data regularly.
The backup\restore mechanism is not intended as a "configuration download and manipulation" facility permitting configuration of the Cisco hardware (for example, through Cisco IOS, followed by subsequent management by the EM). The EM maintains configuration synchronization between the Cisco EMF database and the device, not between the database and backup configuration.
It is recommended that you check that there is enough memory space available within the TFTP directory before attempting a backup operation. If there is not enough disk space available, the backup creates a 0 byte file.
The Configuration Backup\Restore section covers the following areas:
Before attempting a configuration backup or restore, ensure that the EM and device user names and passwords are identical. If they are not, the action will fail. To modify usernames and passwords, see the "Managing Username and Passwords" section.
Multiple backup files may exist, however, some TFTP servers do not support duplicate file names and will, therefore, fail configuration backups following the initial action (i.e., the TFTP server will not allow overwriting of the existing backup file). To prevent this from happening, ensure that the TFTP server supports duplicate file names.
To backup the running configuration, proceed as follows:
The Configuration Backup\Restore window appears displaying the Backup\Restore tab.
Step 2 Select the relevant IOS host from the IOS Host list box on the left-hand side of the window.
The current configuration and status data displays. The Status area displays the date and time of the last backup and the name of the backup file.
Step 3 Enter the TFTP server IP address in the Back up Server field.
Step 4 Click the Save icon on the toolbar to save your changes.
If you do not save the TFTP server IP address, the previously saved TFTP server IP address is used rather than the TFTP server IP address entered in the Backup Server field in Step 3.
Step 5 Before initiating a backup, confirm the following:
Step 6 You can manually initiate a backup or schedule a backup to occur at a specific time. Perform one of the following:
An Action Report window appears. The Action Report window details the Cisco IOS commands which execute. Invalid Cisco IOS commands result in a failure to complete the backup.
a. Check the details in the Action Report window to ensure that the backup was successful.
b. Click Save to save the action report when required.
c. Click Close to close the Action Report window and return to the Configuration Backup\Restore window.
The Schedule dialog box appears.
a. Enter a date and time (in mm/dd/yyyy and hh:mm formats respectively) when the download is to take place automatically, then click Ok to save the new date and time.
An Action Report window appears. The Action Report window details the Cisco IOS commands which execute. Invalid Cisco IOS commands result in a failure to backup.
b. Check the details in the Action Report window to ensure that the scheduled backup is setup successfully. You can click Save to save the action report when required.
c. Click Close to close the Action Report window and return to the Cisco IOS Image Download window.
Step 7 Choose File > Close to close the Configuration Backup/Restore window.
|
Caution Do not modify the backup file in any way. If there are modifications to the backup file, then you will not be able to restore it as the following section describes. |
When multiple backups have been performed, multiple backup files exist. Restoration of the most recent backup file, based on the date-time stamp, is the file restored.
To restore the running config, proceed as follows:
The Configuration Backup\Restore window appears displaying the Backup\Restore tab (see Figure 5-10).
Step 2 Select the relevant IOS host from the IOS Host list box on the left-hand side of the window.
The current configuration and status data displays. The Status area displays the date and time of the last backup and the name of the backup file.
Step 3 Enter the TFTP server IP address in the Back up Server field.
Step 4 Click the Save icon on the toolbar to save your changes.
If you do not save the TFTP server IP address, the previously saved TFTP server IP address is used rather than the TFTP server IP address entered in the Back up Server field in Step 3.
Step 5 Configure the register setting between 0x02 and 0x0F using the command line interface. This will ensure that the restore operation is successful.
Step 6 Before initiating a restore, confirm the following:
Step 7 Click Restore to begin the restoration.
An Action Report window appears. The Action Report window details the Cisco IOS commands which execute. Invalid Cisco IOS commands result in a failure to complete the restore. Perform the following:
a. Check the details in the Action Report window to ensure that the restore was successful.
Step 8 Choose File > Close to close the Configuration Backup/Restore window.
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.
This EM supports ATM and Ethernet profiles. ATM profiles break down into ATM interface profiles and ATM QoS connection profiles, each with their own configuration windows. Ethernet profiles are HSRP profiles, with its own configuration window.
Profile management involves the following:
Interface configuration profiles allow you to apply a single profile to multiple ATM interfaces, thereby allowing you to reduce interface configuration efforts. However, if the automatic configuration parameter is enabled, the interface type and side, UNI type and signalling version, and maximum active VPI and VCI profile parameters are not applicable to interfaces.
Managing ATM interface profiles involves the following:
To create an ATM interface profile, proceed as follows:
The ATM Interface Configuration Profile window appears displaying the Configuration (1) 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 you new profile.
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, an ATM profile might be called ATM1 or ATMInterface1.
Step 5 Click Ok.
The ATM Interface Configuration Profile window reappears with the new profile name displaying in the ATM Interface list on the left-hand side of the window and default configuration data in the ATM Configuration and ILMI Configuration panels. Note that the first profile you create, the default data will most likely be inappropriate. Therefore you must configure each parameters 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 ATM Configuration area as follows:
Step 7 Configure the parameters in the ILMI Configuration area as follows:
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.
Step 8 Choose the Configuration(2) tab.
The ATM Interface Configuration Profile window displays the Configuration (2) tab.
Step 9 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 area by selecting Enabled or Disabled from the following fields:
Step 10 Configure the parameters in the Physical Layer area as follows:
Step 11 Configure the parameters in the DS1/E1/DS3/E3 area as follows:
Step 12 Click the Save icon on the toolbar to save the parameters you have selected for your profile.
Step 13 Choose File > Close to close the ATM Interface Configuration Profile window.
You may proceed to the "Configuring an Interface" section for details on entering generic interface configuration and applying the ATM profile to an appropriate interface.
To edit an ATM interface profile, proceed as follows:
The ATM Interface Configuration Profile window appears displaying the Configuration (1) tab (see Figure 5-13).
Step 2 Choose the profile you wish to edit from the list of existing profiles which display in the ATM Profile list on the left-hand side of the window.
Step 3 Edit the parameters on the Configuration (1) and Configuration (2) tabs as required. For parameter descriptions, see Steps 6 through 11 of the "Creating and Configuring an ATM 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 ATM Interface Configuration Profile window.
To delete an ATM interface profile, proceed as follows:
The ATM Interface Configuration Profile window appears displaying the Configuration (1) tab (see Figure 5-13).
Step 2 Choose the profile you wish to edit from the list of existing profiles which display in the ATM 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 ATM 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 ATM Interface Configuration Profile window.
ATM QoS profiles, when applied to ATM connections, allow for more efficient configuration of PVCs and SPVCs.
Managing ATM QoS connection profiles involves the following:
To create an ATM QoS connection profile, proceed as follows:
The ATM QoS Profiles Configuration window appears displaying the Profile 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 the name of your new profile.
Step 4 Enter a name for the new profile in the Enter profile name data entry box. Each profile created 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, an ATM QoS profile might be called ATMQoS1 or QoSConnection1.
Step 5 Click Ok.
The QoS Interface Profiles Configuration window reappears and the new profile name displays in the QoS Profiles list on the left-hand side of the window. Default configuration data displays in the Profile Parameters panel. 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 are 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 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 6 Configure the parameters in the Profile Configuration area as follows:
Step 7 Click the RxTx Parameters tab.
The ATM QoS Profiles Configuration window, RxTx Parameters tab displays.
Step 8 Select the appropriate QoS service category for the selected QoS profile. Depending on the service category selection, the fields on the window activate/deactivate. The following table lists the applicable (i.e., active) fields for each service category.
| QoS Service Categories | Applicable Receive/Transmit Parameters |
|---|---|
It is possible to select a service category that is not supported, for example ABR and UBR+. However, this will be detected when an attempt is made to create the connection on the device and the operator informed.
Step 9 Configure the fields in the Receive Parameters and Transmit Parameters areas. Each of these areas contain the same fields, therefore only one description of each field follows:
Step 10 Click the Save icon to save your changes.
Step 11 Choose File > Close to close the ATM QoS Profiles Configuration window.
You may proceed to the "Connection Configuration" section for details on applying the profile and configuring the connection.
An existing profile is available for editing only if it is not currently applied to a connection. Once you have applied a profile to a connection, you cannot edit it (unless you remove it from the connection first). If you want to view the (interface) connections that are using a specific profile, run a Cisco EMF query against the profile name.
|
Note For information on running a Cisco EMF query, refer to the Cisco Element Management Framework User Guide Release 3.2. |
Once you remove a profile from all interfaces, you can proceed to edit its configuration.
To edit an ATM QoS interface profile, proceed as follows:
The ATM QoS Profiles Configuration window appears displaying the Profile tab (see Figure 5-16).
Step 2 Choose the profile you wish to edit from the list of existing profiles displayed in the QoS Profile list on the left-hand side of the window.
Step 3 Edit the parameters in the Profile and RxTx Parameters tabs as required. For parameter descriptions, see Steps 6 through 9 of the "Creating and Configuring an ATM QoS Connection 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 ATM QoS Profiles Configuration window.
Deletion of an existing profile can only occur if it is not currently applied to an interface. Once you have applied a profile to an interface, you cannot delete it (unless you remove it from the interface first). If you want to view the (interface) connections that are using a specific profile, run a Cisco EMF query against the profile name.
|
Note For information on running a Cisco EMF query, refer to the Cisco Element Management Framework User Guide Release 3.2. |
Once you remove a profile from all interfaces, you can proceed to delete it.
To delete an ATM QoS interface profile, follow these steps:
The ATM QoS Profiles Configuration window appears displaying the Profile tab (see Figure 5-16).
Step 2 Choose the profile you wish to edit from the list of existing profiles displayed in the QoS Profile list on the left-hand side of the window.
Step 3 Right click on the profile, then select the Deployment > Delete Objects option.
The Deployment Wizard-Summary window appears.
Step 4 Click Finish to delete the profile.
A Deletion prompt window appears for you to confirm that you wish to delete the selected profile.
Step 5 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 which appear in the ATM Profile list on the left-hand side of the window and an Information window appears.
Step 6 Click OK to close the Information window.
Step 7 Choose File > Close to close the ATM Interface Configuration Profile window.
HSRP profiles are applicable to Ethernet interfaces, reducing the amount of configuration efforts.
Managing HSRP interface profiles involves the following:
To create an HSRP profile, proceed as follows:
The HSRP Profile window appears.
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 you new profile.
Step 4 Enter a name for the new profile in the Enter profile name data entry box. Each profile created 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, an HSRP profile might be called HSRP1.
Step 5 Click Ok.
The QoS Interface Profiles Configuration window reappears displaying the new profile name in the HSRP Profile list on the left-hand side of the window and default configuration data in the HSRP Profile Parameters panel. 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 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. If applicable, select the individual parameter. Choose Edit > Paste to paste to the information. The settings which copy appear in blue. |
Step 6 Configure the parameters in the HSRP Profile Parameters area as follows:
Step 7 Click the Save icon to save your changes.
Step 8 Choose File > Close to close the window.
You may proceed to the "Configuring an Interface" section for details on entering generic interface configuration and applying the HSRP profile to an appropriate interface.
To edit an HSRP profile, proceed as follows:
The HSRP Profile window appears (see Figure 5-20).
Step 2 Choose the profile you wish to edit from the list of existing profiles which display in the HSRP Profile list on the left-hand side of the window.
Step 3 Edit the parameters in the HSRP Profile Parameters panel as required. For parameter descriptions, see Step 6 of the "Creating and Configuring an HSRP 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 HSRP Profiles window.
To delete an HSRP profile, proceed as follows:
The HSRP Profile window appears (see Figure 5-20).
Step 2 Choose the profile you wish to edit from the list of existing profiles which appear in the HSRP 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 which displays.
A Deletion prompt window appears for you to confirm that you wish to delete the selected profile.
Step 4 Click Yes to delete the 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 ATM 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 Click the Save icon on the toolbar to save the parameters you have selected for your profile.
Step 7 Choose File > Close to close the HSRP Profile window.
The EM supports redundancy when there are redundant processors present in the chassis.
In the case of C8500MGR, only the Cisco Catalyst 8540 router is eligible for redundancy activities because it supports:
Specifically, when the Cisco Catalyst 8540 router contains route processors in slots 4 and 8, processor synchronization and failover may take place.
When the Cisco Catalyst 8540 router contains three switch processors in slots 5, 6, and 7, processor switchover may take place. Switch processor synchronization is automated, therefore manual synchronization is not necessary.
The Redundancy section covers the following:
Synchronizing redundant route processor allows you to copy data from the active route processor to the route processor in standby mode. Route processor synchronization is available for data backup purposes or for use prior to forcing a failover. It is recommended that you synchronize the primary and secondary CPUs regularly.
Automatic synchronization is available as well. The automated feature allows for continuous synchronizations where data transfers between the active and standby CPUs when changes are saved to the appropriate configuration file, start up and/or running. You may choose to deactivate automatic synchronizations by selecting the neither option.
To synchronize route processors, proceed as follows:
The Redundancy window appears displaying the Route Processor tab.
Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.
The Status area displays status data for the route processors present in slot 8 of the selected chassis. Status data consists of the slot number where the processor resides, the mode (active or standby), and the current processor module status.
Keep in mind that even though only the processor in slot 8 displays in the Status area, the other processor resides in slot 4. Make a note of the status of the processor in slot 8, active or standby. It can be assumed that the processor in slot 4 holds the other status. For example, in the previous figure the active processor is in slot 8, therefore the standby module must be in slot 4.
The Synchronization area displays recent configuration statistics as follows:
If you want to configure for automatic synchronization upon change, continue to Step 3 and skip Step 4. If you want to initiate a manual synchronization at this time only, skip Step 3 and continue to Step 4.
Step 3 To configure automatic switch processor synchronization, proceed as follows:
a. Select the appropriate option from the Auto-Configuration Sync options list. Options are:
b. Choose File > Save to save the automatic synchronization setting and initiate
An initial synchronization occurs if the running-config, startup-config, or both option was selected. In future instances, data on the active processor writes to the standby processor according to the option selected when a change is made to the configuration(s). The age counter of the most recent synchronization updates in the Synchronization area.
Step 4 To initiate a manual route processor synchronization at this time, proceed as follows:
a. Select the appropriate synchronization configuration parameter from the Synchronize option list in the Actions area. Options are:
b. Click Now to initiate a synchronization, per the established parameter, at the present time.
Data on the active processor writes to the standby processor accordingly. The active and standby processors are synchronized. The age counter of the most recent synchronization updates in the Synchronization area.
Step 5 Choose File > Close to close the Redundancy window.
Forcing a failover essentially forcefully fails the active route processor and moves the standby route processor 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. For information on synchronizing route processors, see the preceding section.
Forcing a failover reversal is not possible until the device reboots.
To force failover, proceed as follows:
The Redundancy window appears displaying the Route Processor tab (see Figure 5-22).
Step 2 Select the relevant chassis from the Chassis list box on the left-hand side of the window.
Step 3 Click Force Failover (in the Actions area).
The active route processor within the selected chassis moves into a failed state and the standby route processor automatically moves into the active role. The Status area updates to display the new active processor and an informational alarm arises on the chassis to the effect that a forced failover has occurred.
Step 4 Choose File > Close to close the Redundancy window.
Forcing a processor switchover moves the standby switch processor into an active role and moves one of the active switch processor into the standby role. Keep in mind that there are two active switch processors and one processor in standby mode.
To force a switchover, proceed as follows:
The Redundancy window appears displaying the Route Processor tab (see Figure 5-22).
Step 2 Click the Switch Processor tab.
The Switch Processor tab appears.
The Status area displays status data for the switch processors present in the selected chassis. Status data consists of the slot number where the processor resides, the mode (active or standby), and the current processor module status.
Step 3 Select the relevant chassis from the Chassis list box on the left-hand side of the window.
Step 4 Select the slots which you want to contain the active switch processor modules from the Preferred Slot #1 and Preferred Slot #2 option buttons (in the Actions area). The options available will consist of 5, 6, or 7, indicating slot numbers.
The preferred slot selections default to one of two possible switchover settings, where the standby processor moves into one of the active processor's slots.
Step 5 Click Force Switchover.
The standby switch processor moves into the active mode, and the switch processor in the slot that was not selected in Step 4 moves into the standby mode. As part of the switchover, the processor which moves into the active role automatically synchronizes with the other processor in the active role.
For example, assuming the data in the previous figure, the preference of slots 5 and 6 indicate that processor in slot 7, which is currently active, will move into the standby role and the processor in slot 6, currently standby, will move into an active role following the switchover. As such, the processor in slot 7 enters the standby mode and the processor in slot 6 moves into the active role. Furthermore, the processors in slot 6 synchronizes with the active processor in slot 5.
Additionally, an informational alarm arises on the chassis to the effect that a forced switchover has occurred and role changes update in the Status area.
Step 6 Choose File > Close to close the Redundancy window.
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:
To configure a module, proceed as follows:
The Module Configuration window appears.
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.
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 4 Click the Save icon on the toolbar to save your changes.
Step 5 Choose File > Close to close the Chassis Configuration window.
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:
Commissioning any supporting module initiates the following activities:
To commission a module, proceed as follows:
The Module Configuration window appears (see Figure 5-24).
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.
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:
Decommissioning any supporting module initiates the following activities:
To decommission a module, proceed as follows:
The Module Configuration window appears (see Figure 5-24).
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 which displays in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the module decommissioning. 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.
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.
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:
To commission an interface, follow these steps:
The Generic Interface Configuration window appears.
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.
To decommission an interface, follow these steps:
The Generic Interface Configuration window appears (see Figure 5-25).
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.
Interfaces require some level of configuration before the EM can manage them effectively. General interface configuration occurs on the Generic Interface Configuration window. Further configuration for the supported technology-specific interfaces, such as ATM, Ethernet, and IP interfaces, uses the appropriate windows. In order to successfully configure an interface, no matter the type, the interface must be in the decommissioned state. To decommission an interface, see the "Decommissioning 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.
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 "Connection Configuration" section.
Step 4 Configure the attributes in the Configurable Parameters area as follows:
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:
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:
The ATM Interface Configuration window appears displaying the 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.
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 "Connection 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 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:
Step 5 Configure the parameters in the ILMI Configuration panel as follows:
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.
Step 6 Choose the Configuration (2) tab.
The ATM Interface Configuration window displays the 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:
Step 8 Configure the parameters in the Physical Layer area as follows:
Step 9 Configure the parameters in the DS1/E1/DS3/E3 area as follows:
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.
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:
The Ethernet Interface Configuration window appears displaying the 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.
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 "Connection 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 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:
If the communication link to the Cisco Catalyst 8500 router is lost, it cannot be switched on again from Cisco EMF. Access to the Cisco Catalyst 8500 router is required before the link can be re-enabled.
Step 5 Click the HSRP Parameters tab.
The Ethernet Interface Configuration window displays the 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:
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.
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:
The IP Configuration window appears.
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 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.
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 "Connection 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, 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:
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.
ATM connections are objects that you can deploy beneath an ATM interface. The EM supports the following types of ATM connections:
A PVC is a permanent logical connection between two ATM interfaces on a network element. The PVC consists of two VCLs which allow for connections to pass (i.e., a cross-connection). PVCs save bandwidth associated with establishing a circuit when a virtual circuit must exist all the time. You can deploy a PVC (which creates the PVC within Cisco EMF), apply a QoS profile to the PVC, then create the connection on the device. Deploying and creating a PVC creates a cross-connection within one device.
An SPVC is a logical connection between two devices. The remote endpoint (interface) can be a non-Cisco EMF endpoint (that is, outside Cisco EMF) or a Cisco EMF endpoint (that is, within Cisco EMF). Non-Cisco EMF endpoint objects, however, do not appear within the EM and require a ATM, or Network Service Access Point (NSAP), address to establish the connection with the destination device. Deploying and creating an SPVC creates a connection between an ATM interface on one device and an ATM interface on another device.
SPVCs are similar to PVCs in setup; however, they function differently. The PVC is always operating and is always up. The SPVC, on the other hand, shuts down when it is not in use. It does not cease to exist, but only goes down until traffic occurs, when it re-establishes itself again. The SPVC saves bandwidth as opposed to the PVC, but is generally slower in operation.
It is important to mention that ATM connection objects only appear within the Component Managed view of the EM.
The Connection Configuration section includes the following:
ATM connections exist within the EM and on the device. In order to manage ATM connections, you must create the connection within the EM, then create the connection on the device using the EM software (actually connecting the PVC or SPVC).
Establishing ATM connections within the EM may occur by either uploading from the device or deploying through the EM templates. As part of manual deployment you may choose to apply an existing configuration profile, allowing for automatic configuration. You may also choose to automatically create the connection on the device following successful deployment. Additional information regarding connection deployment is available in the "Deploying ATM Connections" section. For instructions on uploading connection information from the device, see the "Uploading Existing ATM Connections and ATM QoS Profiles" section.
Should you opt not to automatically configure the connection during deployment, you may manually configure a connection by applying an existing ATM QoS profile or by setting configuration details on a per-connection basis. The "Managing ATM QoS Connection Profiles" section provides instructions for creating, editing, and deleting profiles which you can apply to connections in lieu of manually configuring. For further information on connection configuration, see the "Configuring ATM Connections" section.
Likewise, if you did not select the option to automatically create the connection on the device as part of the deployment process, you may manually initiate the connection on the device and commission the connection within in the EM. The "Connecting or Disconnecting an ATM Connection" section provides further information. Creating the connection on the device automatically commissions the connection within the EM and allows for object management by the EM.
ATM connections and profiles previously configured on a Cisco device can upload into the EM application. Uploading saves time and effort re-configuring ATM connections and profiles that already exist on the device.
Both PVC and SPVC connections are available for uploading.
When you upload PVCs, any corresponding ATM QoS profiles also upload. PVCs discover and move into the normal state, so that management of these connections can begin automatically. Once these connections and/or profiles upload, you can view and adjust them within the EM.
To upload ATM connections and ATM QoS profiles, proceed as follows:
The ATM Connection Upload window appears.
Step 2 Select a chassis from the Chassis list box on the left-hand side of the window.
Upload progress and status data for the selected chassis appears in the Upload panel. If an upload is not currently underway, the results of the last upload display.
Before you can upload any connections or profiles, ensure telnet passwords configuration is correct in the EM. For further details, see the "Managing Username and Passwords" section.
Step 3 Click Upload.
A pop-up dialog appears asking you to confirm that you wish to proceed with the upload.
Step 4 Click Yes to upload.
All ATM connections and ATM QoS profiles currently configured on the selected device upload to the EM. Upload progress and status data display in the Upload panel and update as the upload progresses. ATM connection uploads and ATM QoS profiles automatically name according to the following:
For example, an uploaded ATM connection automatically named PVC_0-1-0_1.35_0-1-1_1.35 indicates that the connection is a PVC with a source endpoint of 0-1-0 (slot-subslot-port) and a destination endpoint of 0-1-1. The VPI/VCI values are 1 and 35 respectively.
Step 5 Choose File > Close to close the ATM Connection Upload window.
Modification of ATM connection uploads is possible using the information in the "Configuring ATM Connections" section. Modifications to ATM profile uploads is possible using the information in the "Profile Management" section.
You can apply the ATM QoS profiles you created earlier to a managed PVC or SPVC.
In order to apply a profile to a connection, the connection must be in the decommissioned state. To decommission (disconnect) a connection, see the "Connecting or Disconnecting an ATM Connection" section. After applying the profile and ensuring the connection configuration, you may re-commission the connection.
To apply an ATM QoS profile to a connection, proceed as follows:
The ATM QoS Profiles Management window appears displaying the Profile 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, select an interface from the Interface list box, then select a connection (PVC or SPVC) from the Connections list box which you want to apply an ATM QoS profile.
If an ATM QoS profile is currently applied to the connection, its data displays.
Step 3 Ensure that the connection is in the decommissioned (disconnected) state by reviewing the connection status in the lower left-hand corner of the window.
If the connection is in the decommissioned state, you may proceed. If the connection is in the normal state or any other post-commissioned state, you must first decommission the connection before applying a profile. To decommission (disconnect) a connection, see the "Connecting or Disconnecting an ATM Connection" section.
Step 4 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 connection. The profile attributes display in the Profile Parameters area as follows:
Step 5 Click the RxTx Parameters tab to view additional profile data.
The ATM QoS Profiles Management window appears displaying the RxTx Parameters tab.
The settings which copy appear in blue.
The Category area displays the QoS service category for the profile. Depending on the service category selection, the fields on the window activate/deactivate and display parameters accordingly. The following table lists the applicable (i.e., active) fields for each service category.
| QoS Service Categories | Applicable Receive/Transmit Parameters |
|---|---|
It is possible to apply a service category that is not supported, for example ABR and UBR+. However, this will be detected when an attempt is made to create the connection on the device and the operator informed.
The fields in the Receive Parameters and Transmit Parameters area display as follows. Each of these areas contain the same fields, therefore only one description of each field follows:
Step 6 Click the Save icon on the toolbar to save your changes.
Step 7 Choose File > Close to close the ATM Connections Management window.
Following the application of the configuration profile to the decommissioned connection, you may connect (and commission) the connection. If the connection is not created on the device and decommissioned, see the "Connecting or Disconnecting an ATM Connection" section.
The Managing ATM Connections section covers the following:
To configure ATM connections, proceed as follows:
The ATM Connection Management window appears.
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, select an interface from the Interface list box, then select a connection from the Connections list box.
Configuration data for the selected connection appears on the Configuration tab. If configuration has not yet taken place, default data populates the attributes where necessary.
The Source area displays the following:
The Destination area displays the following:
Step 3 Enter the subscriber ID in the corresponding field as necessary.
Step 4 Click the Source Port and Source VCL buttons as necessary (optional):
Step 5 Click the Source Port and Source VCL buttons as necessary (optional):
Step 6 Click the Save icon on the toolbar to save the parameter configuration.
Step 7 Choose File > Close to close the ATM Connections Management window.
After configuring a connection, you may connect (and commission) the connection. See the following section for further information.
Connecting a connection creates the PVC or SPVC on the device, which makes it a real, working connection. The connection also commissions within the EM at this time, which allows you to manage configuration and status details.
Disconnecting a PVC or SPVC decommissions the connection and disconnects the connection entirely from the device.
To connect or disconnect an ATM connection, proceed as follows:
The ATM Connection Management window appears (see Figure 5-35).
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, select an interface from the Interface list box, then select a connection from the Connection list box which you want to connect or disconnect.
Configuration data for the selected connection appears on the Configuration tab.
Step 3 Click Connect or Disconnect (in the Actions area).
Messages appear requiring you to confirm the action.
Step 4 Click Yes to continue or No to cancel the operation.
The confirmation window closes. If you elected to continue with the action, an Action Report displays informing you of the outcome.
Step 5 Click Close to close the Action Report.
Step 6 Choose File > Close to close the ATM Connections Management window.
When you create an ATM connection (PVC or SPVC), Virtual Channel Link(s) (VCL) create automatically. Upon creation of PVCs and SPVCs with Cisco EMF end-points, two VCLs create where one VCL represents the source, or incoming, port and the other VCL represents the destination, or outgoing, port. Although the creation of an SPVCs with a non-Cisco EMF end-point results in the creation of two VCLs, the EM can only manage the source end-point.
To configure an ATM VCL, proceed as follows:
The ATM VCL Configuration window appears, displaying the 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, select an interface from the Interface list box, then select a VCL from the Cisco VCL list box which you want to configure.
The VPI/VCI area includes the following fields:
Depending on the state of the VCL, commissioned (normal) or decommissioned, the fields within the VPI/VCI area behave differently. If the VCL is in a managed state, the VPI and VCI fields are not modifiable (i.e., display only). If the VCL is in the decommissioned state (disconnected), the VPI and VCI fields allow for configuration, however; when recommissioned, the VPI and VCI values which display in the VPI/VCI area of the ATM VCL Configuration window are written from the values in the corresponding fields on the ATM Connections Management window.
Step 3 Configure the Traffic Information area as follows:
Step 4 Configure the Encapsulation Parameters area as follows:
The Encapsulation Protocol and Encapsulation Flag fields are not applicable to the current release of C8500MGR.
Step 5 Configure the OAM Information area as follows:
In ATM, when the physical layer detects loss of signal or cell synchronization, RDI cells are used to report a VPC or VCC failure. RDI cells are sent upstream by a VPC or VCC endpoint to notify the VPC or VCC endpoint of the downstream failure.
Step 6 Click the Save icon on the toolbar to save the parameter configuration.
Step 7 Choose File > Close to close the ATM VCL Configuration window.
Well-known VCs facilitate signaling of SVCs or SPVCs on an (ATM) interface. The ATM Interface Configuration window allows you to choose how well-known VCs will create and delete. Manual configuration allows for the creation of non-standard (e.g., non-default) VCIs, while automatic configuration generates VCs based on the interface configuration. VCs are deleted through the interface configuration settings as well.
For specific information regarding the well-known VC settings, see the "Creating and Configuring an ATM Interface Profile" section and "Configuring an ATM Interface" section.
In order to manually create well-known VCs, the manual creation setting must be the established VC setting on the ATM Interface Configuration window. When the manual creation setting is selected, well-known VCs may be created from the command line interface using IOS. The EM, however, does not currently support manual well-known VC creation.
Posted: Wed Feb 26 03:59:33 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
