The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter explains how to connect and configure the Connectivity Management Processor (CMP) on a Supervisor Engine 2T-10GE. It also explains how to update the software image for the CMP.
This chapter includes the following sections:
•Verifying the CMP Configuration
•Saving the Configuration File
•Default Settings for CMP Parameters
This section includes the following topics:
•Configuring the CMP-MGMT Interface
•Saving Console Output on the CMP
•Configuring CMPs on a Dual Supervisor Engine
•Verifying the CMP Configuration
You must configure the CMP-MGMT interface before you can connect to the CMP through a SSH or Telnet session. The switch is shipped with the CMP network interface set to a default configuration.
Ensure that you are logged in to the CMP before configuring the default gateway and IP address.
1. configure terminal
2. interface cmpmgmt
3. ip default gateway ipv4-address
4. ip address ipv4-address/length
5. end
6. show running-config
You can log console output on the CMP to help you troubleshoot problems that you might encounter when reloading the RP on a Supervisor Engine 2T-10GE. To manage the log file on the CMP, you can display its logs. The changes that you make to manage the logging of console output are recorded in the running configuration. To activate these changes for future sessions, you must copy the running configuration to the startup configuration after making the changes.
This section includes the following topics:
•Logging Console Output on the CMP
When the log file fills with logs, the system creates another file and begins filling it with logs. The default file size of your CMP log is 100 kilobytes (KB).
To display all of the logs in the log file, enter show loggging route-processor console.
The CMP automatically archives the RP console output log file in its flash-based syslog partition. By default, when the log file reaches its maximum size, the CMP compresses the log file before archiving it. The CMP retains up to four compressed log files per type of log.
The first step in archiving consists of renaming each archived file by incrementing the number in its filename extension. For example, the archived file number four, if present, is deleted, and the slot for archived file number one becomes available. The current log file then is compressed and becomes archived file number one. This process is completed by creating a new uncompressed log file.
Logging CMP messages occurs automatically. The CMP and RP pass information to each other using shared memory.
You can display up to a maximum number of lines according to the type of log that you want to display. The maximum number is 500 for RP logs, 200 for CMP app, 200 for kernel logs, and 50 for epcinfo. The command can retrieve log data from the archived file if the current log file does not have enough lines of data.
To display saved messages, enter one or more of these commands:
The CMP runs in active mode on both supervisor engines, even when only one supervisor engine is active, so you must configure each CMP individually. You can configure a unique IP address for each CMP. To perform all other CMP configuration functions, switch to the CMP that you are configuring to perform those functions.
To display CMP configuration information from the CMP CLI, use the following commands:
There is no version dependency tracking between CMP and RP images. You can load additional CMP images in the CMP bootflash. CMP keeps three kernel images in bootflash: a gold image (master image), F1, and F2. Only F1 and F2 are upgradeable.
When you enter the upgrade command, the system determines which region (F1 or F2) to load the new image file to. The image file is downloaded into memory and stored in the selected region in the boot flash. If the show kernel upgrade command is run after the upgrade command is executed, you will see FIRST_RUN as the status of the region. To complete the upgrade, you must reboot the CMP with the reload command. Once the new image is loaded, the status changes to APPROVED and the upgraded image becomes the running kernel image.
Ensure that you are in CMP mode.
1. show kernel upgrade
2. upgrade kernel file {scp: | sftp: | tftp:} file-path
3. show version
You can reset the admin or root password CMP password to a default password.
Ensure that you are in CMP mode.
1. reload
2. Press any key to put you in to the u-boot CLI when the CMP prompts "Hit any key to stop autoboot:".
3. priv
4. passwd reset
5. boot
6. root:default
You can save the running configuration file into the startup configuration file.
Ensure that you are in CMP mode.
1. write file or write memory
2. show startup-config and show running-config
Note You can view the running configuration file with the write terminal command.
Table 2-1 lists the default settings for CMP parameters.
|
|
---|---|
IP address |
192.168.1.101/24 |
Default gateway |
192.168.1.1 |
SSH server |
Enabled |
Telnet server |
Disabled |