- Connecting to the CMP MGMT Ethernet Port
- Configuring the CMP
- Accessing the CMP from the CP
- Logging Out of a CMP Session
- Configuring the CMP-MGMT Interface
- Configuring an IPv4 Access Control List on the CMP
- Configuring the Cisco Discovery Protocol for the CMP
- Saving Console Output on the CMP
- Logging CMP Messages
- Changing the Communication Settings
- Configuring Flow Control
- Configuring CMPs on a Dual Supervisor System
- Verifying the CMP Configuration
- Upgrading the CMP Image
- Default Settings for CMP Parameters
Connecting, Configuring, and Upgrading the CMP
This chapter explains how to connect and configure the Connectivity Management Processor (CMP) on a Cisco Nexus 7000 Series switch. It also explains how to update the software image for the CMP.
This chapter includes the following sections:
•
Connecting to the CMP MGMT Ethernet Port
•
Verifying the CMP Configuration
•
Default Settings for CMP Parameters
Connecting to the CMP MGMT Ethernet Port
To connect the CMP to the network, follow these steps for each installed supervisor:
Step 1
Connect a modular, RJ-45, UTP cable to the CMP MGMT ETH port on the Supervisor 1 module.
Step 2
Route the cable through the central slot in the cable management system on the Cisco Nexus 7000 Series chassis.
Step 3
Connect the other end of the cable to the networking device.
You configure the cmp-mgmt interface during the initial setup script on the CP when you first configure your switch. See the Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 5.x for details on the setup script.
Configuring the CMP
This section includes the following topics:
•
Accessing the CMP from the CP
•
Configuring the CMP-MGMT Interface
•
Configuring an IPv4 Access Control List on the CMP
•
Configuring the Cisco Discovery Protocol for the CMP
•
Saving Console Output on the CMP
•
Changing the Communication Settings
•
Configuring CMPs on a Dual Supervisor System
Accessing the CMP from the CP
You can access the CMP through a console, SSH, or Telnet session with the CP.
Note
To access the CMP by SSH or Telnet, you must enable those sessions on the CMP (by default, the SSH server session is enabled). To enable or disable SSH or Telnet sessions, see Table 1-2.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
DETAILED STEPS
|
|
|
|
|---|---|---|
Step 1 |
attach cmp
Example: switch# attach cmp
Connected Escape character is '~,' switch-cmp# |
Accesses the CMP on the active supervisor module. |
Logging Out of a CMP Session
When you log out of a CMP session, you must end the session then exit the mode.
BEFORE YOU BEGIN
You must be accessing the CMP.
SUMMARY STEPS
1.
end
2.
exit
DETAILED STEPS
|
|
|
|
|---|---|---|
Step 1 |
end
Example: switch-cmp# end
switch-cmp# |
Ends the configuration session. |
Step 2 |
exit
Example: switch-cmp# exit switch# |
Exits from the CMP configuration mode. |
Note
If you are in an attached console session, use the ~, command to exit the CMP.
Configuring the CMP-MGMT Interface
You must configure the CMP-MGMT interface before you can connect to the CMP through a SSH or Telnet session.
Note
Unlike when you configure the CP, you do not need to use the copy running-config startup-config command configuring the CMP-MGMT interface. Each time that you enter a command when configuring the CMP-MGMT interface, the Cisco NX-OS operating system saves the configuration changes on the CMP flash drive.
The following sections explain each of the different ways that you can configure the CMP-MGMT interface:
•
Using a Setup Script on the CP to Configure the CMP-MGMT Interface
•
Configuring an IPv4 IP Address for the CMP From the CP
•
Configuring an IPv4 IP Address for the CMP From the CMP
•
Configuring an IPv6 IP Address for the CMP From the CP
•
Configuring an IPv6 IP Address for the CMP From the CMP
Using a Setup Script on the CP to Configure the CMP-MGMT Interface
The Cisco NX-OS setup script guides you through configuring the CMP-MGMT interface. To use this script, see the Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 5.x.
Configuring an IPv4 IP Address for the CMP From the CP
You can use the Cisco NX-OS CLI on the CP to configure an IP address (IPv4 format) for the CMP-MGMT interface.
BEFORE YOU BEGIN
Ensure that you are in the default virtual device context (VDC) (or use the switchback command).
SUMMARY STEPS
1.
configure terminal
2.
interface cmp-mgmt module slot
3.
ip address ipv4-address/length
4.
ip default-gateway ipv4-address
5.
(optional) show running-config cmp
DETAILED STEPS
Configuring an IPv4 IP Address for the CMP From the CMP
You can use the Cisco NX-OS CLI on the CP to configure an IP address (IPv4 format) for the CMP-MGMT interface.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
ip default-gateway ipv4-address
4.
interface cmp-mgmt
5.
ip address ipv4-address/length
6.
(optional) show running-config
7.
(optional) ~,
DETAILED STEPS
Configuring an IPv6 IP Address for the CMP From the CP
You can configure an IPv6 address for the CMP-MGMT interface from the CP.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
configure terminal
2.
interface cmp-mgmt module slot
3.
ipv6 address ipv6-address/length
4.
ipv6 default-gateway ipv6-address
5.
(optional) show running-config cmp
DETAILED STEPS
To remove the IP address for the cmp-mgmt interface, use the no ipv6 address command.
To remove the IP address for the default gateway, use the no ipv6 default-gateway command.
Configuring an IPv6 IP Address for the CMP From the CMP
You can use the Cisco NX-OS CLI on the CP to configure an IPv6 IP address for the CMP-MGMT interface.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
ipv6 default-gateway ipv6-address
4.
interface cmp-mgmt
5.
ipv6 address ipv6-address/length
6.
(optional) show running-config
7.
(optional) ~,
DETAILED STEPS
Configuring an IPv4 Access Control List on the CMP
You can create an IPv4 access control list (ACL) and apply it to the cmp-mgmt interface. For more information on ACLs, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x.
Note
You can only configure an ACL on the CMP directly. You cannot configure an ACL from Cisco NX-OS software on the supervisor module CP.
BEFORE YOU BEGIN
You are connected to the CMP (see the "Configuring an IPv4 IP Address for the CMP From the CMP" section).
SUMMARY STEPS
1.
configure terminal
2.
ip access-list name
3.
{permit | deny} protocol source destination
4.
exit
5.
interface cmp-mgmt
6.
ip access-group access-list in
7.
(optional) show running-config
DETAILED STEPS
Configuring the Cisco Discovery Protocol for the CMP
The Cisco Discovery Protocol (CDP) is a media- and protocol-independent protocol that runs on all Cisco-manufactured equipment including routers, bridges, access and communication servers, and switches. You can use CDP to discover and view information about all the Cisco devices that are directly attached to the switch.
CDP gathers protocol addresses of neighboring devices and discovers the platform of those devices.
Each switch that you configure for CDP sends periodic advertisements to a multicast address. The advertisements also contain hold-time information, which indicates the length of time that a receiving device should hold CDP information before removing it. You can configure the advertisement or refresh timer and the hold timer.
This section includes the following topics:
•
Enabling and Disabling the CDP
•
Configuring Optional CDP Parameters
Enabling and Disabling the CDP
CDP is enabled by default. You can disable CDP and then reenable it at a later time.
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
cdp enable
DETAILED STEPS
To disable the CDP feature on the switch, use the no cdp enable command.
Configuring Optional CDP Parameters
You can use the following optional commands in global configuration mode to modify CDP:
Default Settings
Table 2-1 lists the CDP default settings.
|
|
|
|---|---|
CDP |
Enabled globally and on all interfaces |
CDP version |
Version 2 |
CDP device ID |
Serial number |
CDP timer |
60 seconds |
CDP hold time |
180 seconds |
Additional References
For additional information related to implementing CDP, see Table 2-2.
Saving Console Output on the CMP
Beginning with Cisco NX-OS Release 5.0, you can log console output on the CMP to help you troubleshoot problems that you might encounter when reloading the CP on your Cisco Nexus 7000 Series switch. To manage the log file on the CMP, you can specify the size of the file, display its logs, archive the file on the CP log flash drive, and clear logs from the file. 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
•
Specifying the Size of the Logging File
Logging Console Output on the CMP
When you enable the logging of console output on the CMP, you can either use the default file size (50 kilobytes [KB]) for the logs or specify another file size between 10 KB and 100 KB. You can enable or disable this logging function while working in the CP or in the CMP.
Note
When the log file fills with logs, the system creates another file and begins filling it with logs.
BEFORE YOU BEGIN
If you are operating in an attach CMP or detach CMP mode, your configuration change to enable or disable the logging is recorded in the running configuration but the switch does not change this function for the current session.
SUMMARY STEPS
1.
configure terminal
2.
capture cp console [file_size]
3.
(optional) copy running-config startup-config
DETAILED STEPS
Note
To disable the logging of console output, use the no capture cp console command. When you use this command on the CP, it applies the CMP configuration to both the active and standby supervisor modules.
Specifying the Size of the Logging File
You can specify the size of the console output logging file separately from enabling or disabling the logging function. You can do this action while working in the CP or in the CMP.
BEFORE YOU BEGIN
If you are configuring the CMP from the CP, you must not be in an attach CMP mode.
If you are configuring the CMP from the CMP, you must not be in a monitor CP mode.
Note
If you are operating in an attach CMP or detach CMP mode, your configuration change to enable or disable the logging is recorded in the running configuration but the switch does not change this function for the current session.
SUMMARY STEPS
1.
configure terminal
2.
capture cp size [file_size]
3.
(optional) copy running-config startup-config
DETAILED STEPS
Showing Logged Output
You can display the contents of a console output log file or the last number of logs that you specify.
PROCEDURE
Archiving a Log File
You can archive the console output log file on the CP while working in the CP or in the CMP. By default, the switch archives the log file.
BEFORE YOU BEGIN
If you are configuring the CMP from the CP, you must not be in an attach CMP mode.
If you are configuring the CMP from the CMP, you must not be in a monitor CP mode.
Note
If you are operating in an attach CMP or detach CMP mode, your configuration change to enable or disable the logging is recorded in the running configuration but the switch does not change this function for the current session.
SUMMARY STEPS
1.
configure terminal
2.
capture cp archive enable
3.
(optional) copy running-config startup-config
DETAILED STEPS
Note
To stop the archiving of the console output to the CP, use the no capture cp archive enable command.
Clearing the Log File
You can clear the contents of a log file while configuring in the CMP.
SUMMARY STEPS
1.
configure terminal
2.
clear capture cp
3.
(optional) copy running-config startup-config
DETAILED STEPS
Logging CMP Messages
You can save up to 256 CMP messages in a log file, and you can specify a severity threshold for the messages saved. When the file has 256 messages, the CMP automatically removes the oldest message whenever it saves a new message. Table 2-3 describes the message levels and types of messages that the CMP saves. When you specify a severity level, the CMP saves messages for that level and all levels below it in the log file.
This section includes the following topics:
•
Configuring the Logging Level
Displaying Saved Messages
You can display all of the messages saved in the CMP log file.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
show logging logfile
3.
(optional) ~,
DETAILED STEPS
Configuring the Logging Level
By default, the CMP saves level 2 messages and below for each CMP process in the log file. You can specify a different level for the CMP to save for a process by using the logging level command.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
(optional) show logging level process
4.
logging level process [1 | 2 | 3 | 4 | 5 | 6 | 7]
5.
(optional) show logging level process
6.
(optional) ~,
DETAILED STEPS
Clearing the Log File
You can clear the contents of the log file.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
clear logging logfile
4.
(optional) ~,
DETAILED STEPS
Directing Syslog Messages Externally
You can direct the CMP syslog messages to a maximum of five external devices (consoles and terminals), and you can specify the maximum level of the messages directed to each external device.
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
logging server ip_address|ipv6_address {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7} facility {auth | daemon | kernel | user}
logging console {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}
logging monitor {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}
logging level logging_facility {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}
4.
(Optional) show logging
(Optional) show logging server
(Optional) show logging console
(Optional) show logging monitor
(Optional) show logging level
5.
(Optional) -,
DETAILED STEPS
Changing the Communication Settings
You can change the communication speed, number of bits in a byte, terminal parity, asynchronous line stop bits, and flow control settings so that the CMP can communicate with its CP.
This section includes the following topics:
•
Changing the Number of Bits in a Transmitted Character
•
Changing the Asynchronous Stop Bits
Changing the Speed
The CP and CMP must use the same speed (baud rate). If the CP and CMP use different speeds, you must change the speed used by the CMP so that it matches the CP speed.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
line com1
4.
(Optional) show line
5.
speed number
6.
(Optional) ~,
DETAILED STEPS
Changing the Number of Bits in a Transmitted Character
The CP and CMP must use the same number of data bits in the characters that they transmit. If the CP and CMP use different numbers of data bits, you can change the number used by the CMP so that it matches the CP usage.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
line com1
4.
(Optional) show line
5.
databits number
6.
(Optional) ~,
DETAILED STEPS
Changing the Parity Checking
The CP and CMP must use the same type of parity checking. If the CP and CMP use different types, you must change the type used by the CMP so that it matches the CP type.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
line com1
4.
(Optional) show line
5.
parity {even | odd | none}
6.
(Optional) ~,
DETAILED STEPS
Changing the Asynchronous Stop Bits
The CP and CMP must use the same number of stop bits. If the CP and CMP use different numbers of stop bits, you must change the number used by the CMP so that it matches the CP number.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
line com1
4.
stopbits {1 | 2}
5.
exit
6.
(Optional) show line
7.
(Optional) ~,
DETAILED STEPS
Configuring Flow Control
You can use a hardware version of flow control to regulate the flow of data traffic over the internal serial connection between the CMP and CP. When enabled for both the CMP and CP, flow control delays the flow of frames until earlier frames are processed by the receiving processor.
This section includes the following topics:
•
Enabling or Disabling Flow Control for the CMP
•
Enabling or Disabling Flow Control for the CP
Enabling or Disabling Flow Control for the CMP
You can enable or disable the CMP to use a hardware version of flow control with the CP.
BEFORE YOU BEGIN
You must enable flow control on the CP (see the "Enabling or Disabling Flow Control for the CP" section).
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
attach cmp
2.
configure terminal
3.
line com1
4.
{flowcontrol hardware} | {no flowcontrol hardware}
5.
(Optional) show line com1
6.
exit
7.
(Optional) ~,
DETAILED STEPS
Enabling or Disabling Flow Control for the CP
You can enable or disable the CP to use a hardware version of flow-control with the CMP.
BEFORE YOU BEGIN
You must enable flow control on the CMP (see the "Enabling or Disabling Flow Control for the CMP" section).
SUMMARY STEPS
1.
configure terminal
2.
line console
3.
{flowcontrol hardware} | {no flowcontrol hardware}
4.
(Optional) show line console
5.
exit
6.
exit
DETAILED STEPS
Configuring CMPs on a Dual Supervisor System
The CMP runs in active mode on both supervisor modules, even when only one supervisor module is active, so you must configure each CMP individually. You can configure the unique IP address for each CMP from the active CP by using Cisco NX-OS commands through either the CLI or scripts. To perform all other CMP configuration functions, connect directly to the CMP that you are configuring to perform those functions.
Verifying the CMP Configuration
To display CMP configuration information from the Cisco NX-OS CLI on the CP, use the following commands:
To display CMP configuration information from the CMP CLI, use the following commands:
Upgrading the CMP Image
You can upgrade the CMP image, which is part of the Cisco NX-OS system image and contains a subset of commands to support the CMP features.
Note
The CMP image is independent of the CP image, so the version of the CMP image might not match the version of the CP image. To make sure that the CMP is running the latest compatible image, use the install all command from the Cisco NX-OS CLI on the CP.
To upgrade the Cisco NX-OS kickstart image, system image, and CMP image at the same time, use the install all command from the Cisco NX-OS CLI on the CP. This command automatically upgrades the software on both CMPs. After the software is upgraded, you must manually reload the CMP on each supervisor. For more information on software images, see the Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 5.x.
Use the following procedure if you want to update only the CMP image.
BEFORE YOU BEGIN
Ensure that you are in the default VDC (or use the switchback command).
SUMMARY STEPS
1.
copy {ftp | tftp} remote-location local-location
2.
(Optional) show module
3.
install module active-slot cmp system local-location
4.
install module standby-slot cmp system local-location
5.
reload cmp module active-slot
6.
reload cmp module standby-slot
7.
(Optional) show version
DETAILED STEPS
Default Settings for CMP Parameters
Table 2-4 lists the default settings for CMP parameters.
|
|
|
|---|---|
Logging level |
2 (critical level) |
SSH server |
Enabled |
Telnet server |
Disabled |
Feedback