Page 1 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x First Published: 2013-11-20 Last Modified: 2014-10-10 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883...
Page 2 This product includes software written by Tim Hudson (tjh@cryptsoft.com). http:// Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks .
Page 3: Table Of Contents
Configuring with Cisco DCNM Network Time Protocol Cisco Discovery Protocol System Messages Smart Call Home Rollback Session Manager Scheduler SNMP RMON Online Diagnostics Embedded Event Manager Onboard Failure Logging Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 4 Configuring the NTP Source Interface Configuring NTP Logging Verifying the NTP Configuration Configuration Examples for NTP Additional References Related Documents MIBs Configuring CDP C H A P T E R 4 About CDP Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 5 Verifying the System Message Logging Configuration Configuration Example for System Message Logging Additional References Related Documents Configuring Smart Call Home C H A P T E R 6 About Smart Call Home Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 6 Short Text Message Format Common Event Message Fields Alert Group Message Fields Fields for Reactive and Proactive Event Messages Fields for Inventory Event Messages Fields for User-Generated Test Messages Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 7 Guidelines and Limitations for Session Manager Configuring Session Manager Creating a Session Configuring ACLs in a Session Verifying a Session Committing a Session Saving a Session Discarding a Session Verifying the Session Manager Configuration Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 8 C H A P T E R 1 0 About SNMP SNMP Functional Overview SNMP Notifications SNMPv3 Security Models and Levels for SNMPv1, v2, v3 User-Based Security Model Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x viii...
Page 9 Assigning SNMP Device Contact and Location Information Configuring the Context to Network Entity Mapping Disabling SNMP Modifying the AAA Synchronization Time Verifying SNMP Configuration Configuration Examples for SNMP Additional References Related Documents RFCs MIBs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 10 Configuring Online Diagnostics Setting the Bootup Diagnostic Level Activating a Diagnostic Test Starting or Stopping an On-Demand Diagnostic Test Simulating Diagnostic Results Clearing Diagnostic Results Verifying the Online Diagnostics Configuration Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 11 Configuring Onboard Failure Logging C H A P T E R 1 4 About OBFL Licensing Requirements for OBFL Prerequisites for OBFL Guidelines and Limitations for OBFL Default Settings for OBFL Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 12 Configuration Example for a Unidirectional SPAN Session Configuration Example for a SPAN ACL Additional References Related Documents Configuring ERSPAN C H A P T E R 1 6 About ERSPAN ERSPAN Types ERSPAN Sources Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 13 Verifying the LLDP Configuration Configuration Example for LLDP Performing Software Maintenance Upgrades C H A P T E R 1 8 About SMUs Package Management Impact of Package Activation and Deactivation Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x xiii...
Page 14 Overriding (Disabling) an Entire Module Overriding (Disabling) Multiple Modules and Sensors Enabling One Sensor While Disabling All Remaining Sensors of All Modules Enabling Multiple Sensors While Disabling All Remaining Sensors of All Modules Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 15 Configuration Example for Port Tracking Configuration Example to Register an EEM Policy with the EEM Configuration Limits for Cisco NX-OS System Management A P P E N D I X C Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 16 Contents Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 17: Document Conventions
• Documentation Feedback, page xviii • Obtaining Documentation and Submitting a Service Request, page xix Audience This publication is for network administrators who install, configure, and maintain Cisco Nexus switches. Document Conventions Command descriptions use the following conventions: Convention Description...
Page 18: Documentation Feedback
An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. Related Documentation for Cisco Nexus 9000 Series Switches The entire Cisco Nexus 9000 Series switch documentation set is available at the following URL: http://www.cisco.com/en/US/products/ps13386/tsd_products_support_series_home.html Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com.
Page 19: Obtaining Documentation And Submitting A Service Request
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
Page 20 Preface Obtaining Documentation and Submitting a Service Request Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 21: New And Changed Information
New and Changed Information, page 1 New and Changed Information This table summarizes the new and changed features for the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x and tells you where they are documented. Table 1: New and Changed Features for Cisco NX-OS Release 6.x...
Page 22 (SMUs) Maintenance Upgrades, on page 217 SPAN Added support for source VLANs 6.1(2)I2(1) Configuring SPAN, on and support for SPAN destination page 185 ports in access or trunk mode. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 23: Chapter
C H A P T E R Overview This chapter describes the system management features that you can use to monitor and manage Cisco NX-OS devices. This chapter contains the following sections: • Software Image, page 4 • Cisco NX-OS Device Configuration Methods, page 4 •...
Page 24: Software Image
This image runs on all Cisco Nexus 9000 Series switches. Cisco NX-OS Device Configuration Methods You can configure devices using direct network configuration methods or web services hosted on a Cisco Data Center Network Management (DCNM) server. This figure shows the device configuration methods available to a network user.
Page 25: Configuring With Cli Or Xml Management Interface
Configuring with Cisco DCNM You can configure Cisco NX-OS devices using the Cisco DCNM client, which runs on your local PC and uses web services on the Cisco DCNM server. The Cisco DCNM server configures the device over the XML management interface.
Page 26: Smart Call Home
XML-based automated parsing applications. You can use this feature to page a network support engineer, e-mail a Network Operations Center, or use Cisco Smart Call Home services to automatically generate a case with the Technical Assistance Center.
Page 27: Span
Online Diagnostics Online Diagnostics Cisco Generic Online Diagnostics (GOLD) define a common framework for diagnostic operations across Cisco platforms. The online diagnostic framework specifies the platform-independent fault-detection architecture for centralized and distributed systems, including the common diagnostics CLI and the platform-independent fault-detection procedures for boot-up and run-time diagnostics.
Page 28: Smus
Virtual Device Contexts Cisco NX-OS can segment operating system and hardware resources into virtual device contexts (VDCs) that emulate virtual devices. The Cisco Nexus 9000 Series switches currently do not support multiple VDCs. All switch resources are managed in the default VDC.
Page 29: Configuring Ntp
C H A P T E R Configuring NTP This chapter describes how to configure the Network Time Protocol (NTP) on Cisco NX-OS devices. This chapter includes the following sections: • About NTP, page 9 • Licensing Requirements for NTP, page 11 •...
Page 30: Ntp Associations
Before synchronizing, NTP compares the time reported by several network devices and does not synchronize with one that is significantly different, even if it is a stratum 1. Because Cisco NX-OS cannot connect to a radio or atomic clock and act as a stratum 1 server, we recommend that you use the public NTP servers available on the Internet.
Page 31: Virtualization Support
• You must manually distribute NTP authentication keys on the NTP server and Cisco NX-OS devices across the network. • If you are using the switch as an edge device and want to use NTP, Cisco recommends using the ntp access-group command and filtering NTP only to the required edge devices.
Page 32: Default Settings For Ntp
Disabled NTP logging Disabled Configuring NTP Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Enabling or Disabling NTP You can enable or disable NTP. NTP is enabled by default.
Page 33: Configuring The Device As An Authoritative Ntp Server
Make sure you know the IP address or Domain Name System (DNS) names of your NTP server and its peers. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 34 A domain name is resolved only when you have a DNS switch(config)# show ntp peers server configured. Step 5 (Optional) copy running-config startup-config Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 35: Configuring Ntp Authentication
This command provides protection against accidentally synchronizing the device to a time source that is not trusted. Step 5 show ntp trusted-keys (Optional) Displays the configured NTP trusted keys. Example: switch(config)# show ntp trusted-keys Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 36: Configuring Ntp Access Restrictions
• The serve keyword enables the device to receive time requests and NTP control queries from the servers specified in the access list but not to synchronize itself to the specified servers. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 37: Configuring The Ntp Source Ip Address
The ip-address can be in IPv4 or IPv6 format. Example: switch(config)# ntp source 192.0.2.1 Step 3 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 38: Configuring The Ntp Source Interface
NTP events. NTP logging is disabled by default. Example: switch(config)# ntp logging Step 3 show ntp logging-status (Optional) Displays the NTP logging configuration status. Example: switch(config)# show ntp logging-status Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 39: Verifying The Ntp Configuration
Enter configuration commands, one per line. End with CNTL/Z. switch(config)# ntp server 192.0.2.105 key 42 switch(config)# ntp peer 2001:0db8::4101 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 40 10 permit ip host 10.6.6.6 any switch(config-acl)# 20 permit ip host 10.7.7.7 any switch(config)# ip access-list query-only-acl switch(config-acl)# 10 permit ip host 10.2.2.2 any switch(config-acl)# 20 permit ip host 10.3.3.3 any Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 41: Additional References
Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide MIBs MIBs MIBs Link MIBs related to NTP To locate and download supported MIBs, go to the following URL: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 42 Configuring NTP MIBs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 43: Configuring Cdp
The Cisco Discovery Protocol (CDP) is a media-independent 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 device.
Page 44: Vtp Feature Support
CDP packets sent from that trunk port include the lowest configured VLAN ID allowed on that trunk port. The trunk port can receive CDP packets that include any VLAN ID in the allowed VLAN list for that trunk port. For more information on VLANs, see the Cisco Nexus 9000 Series NX-OS Layer 2 Switching Configuration Guide.
Page 45: Virtualization Support
60 seconds CDP hold timer 180 seconds Configuring CDP Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 46: Enabling Or Disabling Cdp Globally
Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Step 2 interface interface slot/port Enters interface configuration mode. Example: switch(config)# interface ethernet 1/2 switch(config-if)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 47: Configuring Optional Cdp Parameters
• mac-address—The MAC address of the chassis. Example: switch(config)# cdp format • serial-number—The chassis serial device-id mac-address number/Organizationally Unique Identifier (OUI). • system-name—The system name or fully qualified domain name. The default is system-name. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 48: Verifying The Cdp Configuration
Configuration Example for CDP This example shows how to enable the CDP feature and configure the refresh and hold timers: configure terminal cdp enable cdp timer 50 cdp holdtime 100 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 49: Additional References
Configuring CDP Additional References Additional References MIBs MIBs MIBs Link MIBs related to CDP To locate and download supported MIBs, go to the following URL: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 50 Configuring CDP MIBs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 51: Configuring System Message Logging
C H A P T E R Configuring System Message Logging This chapter describes how to configure system message logging on Cisco NX-OS devices. This chapter contains the following sections: • About System Message Logging, page 31 • Licensing Requirements for System Message Logging, page 32 •...
Page 52: Syslog Servers
The syslog servers run on remote systems that log system messages based on the syslog protocol. You can configure up to eight IPv4 or IPv6 syslog servers. To support the same configuration of syslog servers on all switches in a fabric, you can use Cisco Fabric Services (CFS) to distribute the syslog server configuration.
Page 53: Guidelines And Limitations For System Message Logging
Disabled Configuring System Message Logging Note Be aware that the Cisco NX-OS commands for this feature might differ from those commands used in Cisco IOS. Configuring System Message Logging to Terminal Sessions You can configure the device to log messages by their severity level to console, Telnet, and SSH sessions.
Page 54 A lower number indicates a higher severity level. Severity levels range from Example: 0 to 7: switch(config)# logging monitor • 0 – emergency Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 55: Logging System Messages To A File
Logging System Messages to a File You can configure the device to log system messages to a file. By default, system messages are logged to the file log:messages. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 56 • default—Specifies that the default logging configuration is used by interfaces not explicitly configured. Step 4 show logging info (Optional) Displays the logging configuration. Example: switch(config)# show logging info Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 57: Configuring Module And Facility Messages Logging
• 2 – critical • 3 – error • 4 – warning • 5 – notification • 6 – informational • 7 – debugging If the severity level is not Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 58 To apply the same severity level to all facilities, use the all facility. For defaults, see the show logging level command. The no option resets the logging severity level for Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 59 (config)# logging level ethpm link-down notif ? <CR> switch(config)#logging level ethpm link-up ? error ERRORS notif NOTICE (config)# logging level ethpm link-up error ? <CR> (config)# logging level ethpm link-up notif ? <CR> Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 60: Configuring Syslog Servers
Cisco recommends that you configure the syslog server to use the management virtual routing and Note forwarding (VRF) instance. For more information on VRFs, see the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 61 Displays the syslog server configuration. Example: switch(config)# show logging server Step 5 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 62: Configuring Syslog Servers On A Unix Or Linux System
Log debug messages with the local7 facility in the file /var/log/myfile.log by adding the following line to the /etc/syslog.conf file: Example: debug.local7 var/log/myfile.log Step 2 Create the log file by entering these commands at the shell prompt: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 63: Displaying And Clearing Log Files
Clears the contents of the log file. Example: switch# clear logging logfile Step 5 Clears the logged messages in NVRAM. clear logging nvram Example: switch# clear logging nvram Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 64: Verifying The System Message Logging Configuration
3 logging logfile my_log 6 logging module 3 logging level aaa 2 logging timestamp milliseconds logging server 172.28.254.253 logging server 172.28.254.254 5 facility local3 copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 65: Additional References
Configuring System Message Logging Additional References Additional References Related Documents Related Topic Document Title System messages Cisco NX-OS System Messages Reference Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 66 Configuring System Message Logging Related Documents Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 67: Configuring Smart Call Home
You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to automatically generate a case with the Technical Assistance Center. Smart Call Home offers the following features: •...
Page 68: Destination Profiles
Smart Call Home Alert Groups An alert group is a predefined subset of Smart Call Home alerts that are supported in all Cisco Nexus devices. Alert groups allow you to select the set of Smart Call Home alerts that you want to send to a predefined or custom destination profile.
Page 69 FRUs are inserted or removed. This alert is show sprom all considered a noncritical show system uptime event, and the information is used for status and show version entitlement. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 70 Syslog port Events generated by the show license usage group syslog PORT facility. show logging last 200 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 71: Smart Call Home Message Levels
The following table lists each Smart Call Home message level keyword and the corresponding syslog level for the syslog port alert group. Table 7: Severity and Syslog Level Mapping Smart Call Home Level Keyword Syslog Level Description Catastrophic Network-wide catastrophic failure. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 72: Obtaining Smart Call Home
Debugging messages. Obtaining Smart Call Home If you have a service contract directly with Cisco, you can register for the Smart Call Home service. Smart Call Home analyzes Smart Call Home messages and provides background information and recommendations. For known issues, particularly online diagnostics failures, Automatic Service Requests are generated with the Cisco TAC.
Page 73: Database Merge Guidelines
For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 74: Prerequisites For Smart Call Home
Smart Call Home has the following prerequisites: • To send messages to an email address, you must first configure an email server. To send messages using HTTP, you must have access to an HTTPS server and have a valid certificate installed on the Cisco Nexus device.
Page 75: Configuring Smart Call Home
Disabled and no proxy server configured Configuring Smart Call Home Be aware that the Cisco NX-OS commands may differ from the Cisco IOS commands. Note We recommend that you complete the Smart Call Home configuration procedures in the following sequence:...
Page 76 Configures the switch priority for this device. Example: The range is from 0 to 7, with 0 being the highest switch(config-callhome)# priority and 7 the lowest. The default is 7. switch-priority 3 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 77: Creating A Destination Profile
Enters Smart Call Home configuration mode. Example: switch(config)# callhome switch(config-callhome)# Step 3 destination-profile name Creates a new destination profile. The name can be any alphanumeric string up to 31 characters. Example: switch(config-callhome)# destination-profile Noc101 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 78: Modifying A Destination Profile
• Message level—The Smart Call Home message severity level for this destination profile. • Message size—The allowed length of a Smart Call Home message sent to the email addresses in this destination profile. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 79 Smart Call Home severity level to destinations in this profile. The range is from Example: 0 to 9, where 9 is the highest severity level. switch(config-callhome)# destination-profile full-txt-destination message-level 5 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 80: Associating An Alert Group With A Destination Profile
Enters Smart Call Home configuration mode. Example: switch(config)# callhome switch(config-callhome)# Step 3 destination-profile {name | CiscoTAC-1 | Associates an alert group with this full-txt-destination | short-txt-destination} destination profile. Use the All keyword Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 81: Adding Show Commands To An Alert Group
You cannot add user-defined CLI show commands to the CiscoTAC-1 destination profile. Note Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 82: Configuring The Email Server
The highest priority server is tried first. If the message fails to be sent, the next server in the list is tried until the limit is exhausted. If two servers have equal priority, the one that was configured earlier is tried first. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 83 Commits the Smart Call Home configuration commands. Example: switch(config-callhome)# commit Step 7 (Optional) show callhome transport Displays the transport-related configuration for Smart Call Home. Example: switch(config-callhome)# show callhome transport Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 84: Configuring Vrfs To Send Messages Using Http
Blue Step 4 commit Commits the Smart Call Home configuration commands. Example: switch(config-callhome)# commit Step 5 (Optional) show callhome Displays information about Smart Call Home. Example: switch(config-callhome)# show callhome Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 85: Configuring An Http Proxy Server
Step 5 commit Commits the Smart Call Home configuration commands. Example: switch(config-callhome)# commit Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 86: Configuring Periodic Inventory Notifications
X days an update is sent (where X is switch(config-callhome)# periodic-inventory notification the update interval). interval 20 Step 4 commit Commits the Smart Call Home configuration commands. Example: switch(config-callhome)# commit Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 87: Disabling Duplicate Message Throttling
Disables duplicate message throttling for Smart Call Home. Example: Duplicate message throttling is enabled by switch(config-callhome)# no default. duplicate-message throttle Step 4 Commits the Smart Call Home configuration commit commands. Example: switch(config-callhome)# commit Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 88: Enabling Or Disabling Smart Call Home
Step 5 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config What to Do Next Optionally generate a test message. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 89: Testing The Smart Call Home Configuration
Displays the Smart Call Home configuration. show callhome show callhome destination-profile name Displays one or more Smart Call Home destination profiles. Displays the transport-related configuration for Smart show callhome transport Call Home. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 90: Configuration Examples For Smart Call Home
Based on the configuration above, the SMTP servers would be tried in this order: 10.1.1.174 (priority 0) 192.0.2.10 (priority 4) 172.21.34.193 (priority 50, which is the default) 64.72.101.213 (priority 60) Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 91: Additional References
Power supply has shut down. TEMPERATURE_ALARM Thermal sensor going bad. TEMPERA TURE_MAJOR_ALARM Thermal sensor indicates temperature has reached operating major threshold. TEMPERA TURE_MINOR_ALARM Thermal sensor indicates temperature has reached operating minor threshold. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 92: Message Formats
SW_SYSTEM_INCONSISTENT Inconsistency has been detected in software or file system. Test and TEST User generated test has occurred. CISCO_TAC Message Formats Smart Call Home supports the following message formats: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 93: Short Text Message Format
Name of alert group, such as /aml/header/group syslog. Severity level Severity level of message. /aml/header/level Source ID Product type for routing, such as /aml/header/source the Cisco Nexus 9000 Series switch. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 94 ID by any support service. Site ID Optional user-configurable field /aml/ header/siteId used for Cisco-supplied site ID or other data meaningful to alternate support service. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 95 /aml/body/chassis/name specific model as part of a product family name). Serial number Chassis serial number of the unit. /aml/body/chassis/serialNo Chassis part number Top assembly number of the /aml/body/chassis/partNo chassis. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 96: Alert Group Message Fields
Software version(s) that is running /aml/body/fru/swVersion on the affected FRU. Fields for Inventory Event Messages The following table describes the inventory event message format for full text or XML messages. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 97: Fields For User-Generated Test Messages
Contact Email:contact@example.com Contact Phone:+91-80-1234-5678 Street Address:#1 Any Street Event Description:SYSLOG_ALERT 2013 May 17 16:31:33 dc3-test %ETHPORT-2-IF_SEQ_ERROR: Error (0x20) while communicating with component MTS_SAP_ELTM opcode:MTS_OPC_ETHPM_PORT_PHY_CLEANUP (for:RID_PORT: Ethernet3/1) syslog_facility:ETHPORT start chassis information: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 98 2013 May 17 16:29:34 dc3-test %DAEMON-3-SYSTEM_MSG: ssh disabled, removing - dcos-xinetd[19105] 2013 May 17 16:29:34 dc3-test %DAEMON-3-SYSTEM_MSG: Telnet disabled, removing - dcos-xinetd[19105] 2013 May 17 16:29:35 dc3-test %PLATFORM-2-PS_AC_IN_MISSING: Power supply 2 present but Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 99 Feature Ins Lic Status Expiry Date Comments Count -------------------------------------------------------------------------------- LAN_ENTERPRISE_SERVICES_PKG Yes - Unused Never - -------------------------------------------------------------------------------- Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 100: Sample Syslog Alert Notification In Xml Format
</rme:Chassis> </ch:Device> </ch:CallHome> </aml-block:Content> <aml-block:Attachments> <aml-block:Attachment type="inline"> <aml-block:Name>show logging logfile | tail -n 200</aml-block:Name> <aml-block:Data encoding="plain"> <![CDATA[2013 May 17 10:57:51 dc3-test %SYSLOG-1-SYSTEM_MSG : Logging logfile (messages) cleared by user Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 101 <more> return code <14> 2013 May 17 16:30:24 dc3-test vsh[23803]: CLIC-3-FAILED_EXEC: Can not exec command <more> return code <14> 2013 May 17 16:30:24 dc3-test vsh[23818]: CLIC-3-FAILED_EXEC: Can not exec command Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 102 </aml-block:Attachment> <aml-block:Attachment type="inline"> <aml-block:Name>show license usage</aml-block:Name> <aml-block:Data encoding="plain"> <![CDATA[Feature Ins Lic Status Expiry Date Comments Count -------------------------------------------------------------------------------- LAN_ENTERPRISE_SERVICES_PKG Yes - Unused Never - -------------------------------------------------------------------------------- ]]> </aml-block:Data> </aml-block:Attachment> </aml-block:Attachments> </aml-block:Block> </soap-env:Body> </soap-env:Envelope> Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 103: Mibs
Configuring Smart Call Home MIBs MIBs MIBs MIBs Link MIBs related to Smart Call Home To locate and download supported MIBs, go to the following URL: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 104 Configuring Smart Call Home MIBs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 105: Configuring Rollback
Additional References, page 90 About Rollbacks A rollback allows you to take a snapshot, or user checkpoint, of the Cisco NX-OS configuration and then reapply that configuration to your device at any point without having to reload the device. A rollback allows any authorized administrator to apply this checkpoint configuration without requiring expert knowledge of the features configured in the checkpoint.
Page 106: Automatically Generated System Checkpoints
If you cancel the operation, Cisco NX-OS provides a list of changes already applied before the error occurred. You need to clean up these changes manually.
Page 107: Licensing Requirements For Rollbacks
NX-OS bundled with the nx-os image and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Rollbacks To configure rollback, you must have network-admin user privileges.
Page 108: Default Settings For Rollbacks
This table lists the default settings for rollback parameters. Parameters Default Rollback type Atomic Configuring Rollbacks Be aware that the Cisco NX-OS commands may differ from the Cisco IOS commands. Note Creating a Checkpoint You can create up to ten checkpoints of your configuration. Procedure Command or Action...
Page 109: Implementing A Rollback
Verifying the Rollback Configuration To display the rollback configuration information, perform one of the following tasks: Command Purpose show checkpoint name [all] Displays the contents of the checkpoint name. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 110: Configuration Example For Rollback
This example shows how to create a checkpoint file and then implements a best-effort rollback to a user checkpoint name: checkpoint stable rollback running-config checkpoint stable best-effort Additional References Related Documents Related Topic Document Title Configuration files Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 111: Configuring Session Manager
Cisco NX-OS returns an error if the configuration does not pass this verification phase. • Commit—Cisco NX-OS verifies the complete configuration and applies the changes to the device. If a failure occurs, Cisco NX-OS reverts to the original configuration.
Page 112: High Availability
Configuring Session Manager Be aware that the Cisco NX-OS commands might differ from Cisco IOS commands. Note Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 113: Creating A Session
ACL. Example: switch(config-s)# ip access-list acl1 switch(config-s-acl)# Step 3 permit protocol source destination (Optional) Adds a permit statement to the ACL. Example: switch(config-s-acl)# permit tcp any any Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 114: Verifying A Session
If the validation fails, Cisco NX-OS reverts switch(config-s)# commit to the original configuration. Saving a Session Use the following command in session mode to save a session: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 115: Discarding A Session
ACL_tcp_in Config Session started, Session ID is 1 Enter configuration commands, one per line. End with CNTL/Z. switch(config-s)# verify Verification Successful switch(config-s)# commit Commit Successful Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 116: Additional References
Configuring Session Manager Additional References switch# Additional References Related Documents Related Topic Document Title Configuration files Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 117: Configuring The Scheduler
C H A P T E R Configuring the Scheduler This chapter describes how to configure the scheduler on Cisco NX-OS devices. This chapter includes the following sections: • About the Scheduler, page 97 • Licensing Requirements for the Scheduler, page 98 •...
Page 118: Remote User Authentication
NX-OS with the nx-os image and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for the Scheduler The scheduler has the following prerequisites: •...
Page 119: Guidelines And Limitations For The Scheduler
Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Step 2 [no] feature scheduler Enables or disables the scheduler. Example: switch(config)# feature scheduler Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 120: Defining The Scheduler Log File Size
Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Configuring Remote User Authentication You can configure the scheduler to use remote authentication for users who want to configure and schedule jobs. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 121: Defining A Job
Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Defining a Job You can define a job including the job name and the command sequence. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 122: Deleting A Job
Step 5 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Deleting a Job You can delete a job from the scheduler. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 123: Defining A Timetable
22:00; but the job requires two minutes to complete. The scheduler starts the first job at 22:00, completes it at 22:02, and then observes a one-minute interval before starting the next job at 22:03. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 124 • delta-time—Specifies the amount of time to wait switch(config-schedule)# time start now repeat 48:00 after the schedule is configured before starting a job. • now—Specifies that the job starts now. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 125: Clearing The Scheduler Log File
Verifying the Scheduler Configuration To display the scheduler configuration information, perform one of the following tasks: Command Purpose show scheduler config Displays the scheduler configuration. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 126: Configuration Examples For The Scheduler
Last Execution Time : Fri Jan 2 1:00:00 2013 Last Completion Time: Fri Jan 2 1:00:01 2013 Execution count : 2 ----------------------------------------------- Job Name Last Execution Status ----------------------------------------------- back-cfg Success (0) switch# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 127: Displaying The Results Of Running Scheduler Jobs
`copy running-config bootflash:/switch-cfg.2013-01-02-01.00.00` `copy bootflash:/switch-cfg.2013--01-02-01.00.00 tftp://1.2.3.4/ vrf management ` Connection to Server Established. [ ] 0.50KBTrying to connect to tftp server..[###### ] 24.50KB TFTP put operation was successful ============================================================================== switch# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 128 Configuring the Scheduler Displaying the Results of Running Scheduler Jobs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 129: C H A P T E
• An SNMP agent—The software component within the managed device that maintains the data for the device and reports these data, as needed, to managing systems. The Cisco Nexus device supports the agent and MIB. To enable the SNMP agent, you must define the relationship between the manager and the agent.
Page 130: Snmp Notifications
Cisco NX-OS generates SNMP notifications as either traps or informs. A trap is an asynchronous, unacknowledged message sent from the agent to the SNMP managers listed in the host receiver table. Informs are asynchronous messages sent from the SNMP agent to the SNMP manager which the manager must acknowledge receipt of.
Page 131: Snmpv3
The various security levels that exist within a security model are as follows: • noAuthNoPriv—Security level that does not provide authentication or encryption. This level is not supported for SNMPv3. • authNoPriv—Security level that provides authentication but does not provide encryption. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 132: User-Based Security Model
Cipher Block Chaining (CBC) DES (DES-56) standard. User-Based Security Model The SNMPv3 User-Based Security Model (USM) refers to SNMP message-level security and offers the following services: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 133: Cli And Snmp User Synchronization
• HMAC-MD5-96 authentication protocol • HMAC-SHA-96 authentication protocol Cisco NX-OS uses Advanced Encryption Standard (AES) as one of the privacy protocols for SNMPv3 message encryption and conforms with RFC 3826. The priv option offers a choice of DES or 128-bit AES encryption for SNMP security encryption. The priv option and the aes-128 token indicate that this privacy password is for generating a 128-bit AES key.
Page 134: Group-Based Snmp Access
Configuring SNMP SNMP and Embedded Event Manager When you configure a passphrase/password in localized key/encrypted format, Cisco NX-OS does not Note synchronize the user information (passwords, roles, and so on). Cisco NX-OS holds the synchronized user configuration for 60 minutes by default.
Page 135: High Availability For Snmp
SNMPv3 users stored on Authentication, Authorization, and Accounting (AAA) servers. • Cisco NX-OS supports read-only access to some SNMP MIBs. See the Cisco NX-OS MIB support list at the following URL for more information: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html...
Page 136: Configuring Snmp
Configuring SNMP Configuring SNMP Configuring SNMP Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Configuring SNMP Users You can configure a user for SNMP. Procedure Command or Action...
Page 137: Assigning Snmpv3 Users To Multiple Roles
Enters global configuration mode. Example: switch# configure terminal switch(config)# Step 2 snmp-server user name group Associates this SNMP user with the configured user role. Example: switch(config)# snmp-server user Admin superuser Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 138: Creating Snmp Communities
If the ACL denies the request, SNMP drops the request and sends a system message. Create the ACL with the following parameters: • Source IP address • Destination IP address • Source port Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 139: Configuring Snmp Notification Receivers
Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Configuring SNMP Notification Receivers You can configure Cisco NX-OS to generate SNMP notifications to multiple host receivers. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode.
Page 140: Configuring A Source Interface For Snmp Notifications
SNMP trap, and the connection is opened with the address of the egress interface as source. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 141: Configuring The Notification Target User
You must configure a notification target user on the device to send SNMPv3 inform notifications to a notification host receiver. Cisco NX-OS uses the credentials of the notification target user to encrypt the SNMPv3 inform notification messages to the configured notification host receiver.
Page 142: Configuring Snmp Notification Receivers With Vrfs
You must configure the host before configuring the VRF reachability or filtering options. Note You can configure Cisco NX-OS to use a configured VRF to reach the host receiver or to filter notifications based on the VRF in which the notification occurred.
Page 143: Configuring Snmp To Send Traps Using An Inband Port
To configure a source interface at the host level, Note use the snmp-server host ip-address source-interface if-type if-number command. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 144: Enabling Snmp Notifications
Enabling SNMP Notifications You can enable or disable notifications. If you do not specify a notification name, Cisco NX-OS enables all notifications. Note The snmp-server enable traps command enables both traps and informs, depending on the configured notification host receivers.
Page 145 CISCO-FEATURE-CONTROL-MIB snmp-server enable traps feature-control snmp-server enable traps feature-control FeatureOpStatusChange CISCO-HSRP-MIB snmp-server enable traps hsrp snmp-server enable traps hsrp state-change Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 146 SNMPv2-MIB snmp-server enable traps snmp snmp-server enable traps snmp authentication Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 147: Snmp-Server Enable Traps Aaa Server-State-Change
• server-state-change—Enables AAA server state-change notifications. Enables Border Gateway Protocol (BGP) SNMP snmp-server enable traps bgp Example: notifications. switch(config)# snmp-server enable traps bgp Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 148: Snmp-Server Enable Traps Bridge Newroot
SNMP notifications for configuration changes config in the running or startup configuration. snmp-server enable traps eigrp [tag] Enables CISCO-EIGRP-MIB SNMP notifications. Example: switch(config)# snmp-server enable traps eigrp Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 149: Snmp-Server Enable Traps Entity
[state-change] Enables CISCO-HSRP-MIB SNMP notifications. Example: Optionally, enables the following specific notifications: switch(config)# snmp-server enable traps hsrp • state-change—Enables HSRP state-change notifications. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 150 Enables redundancy framework (RF) SNMP [redundancy-framework] notifications. Optionally, enables the following specific notifications: Example: switch(config)# snmp-server enable traps rf • redundancy-framework—Enables RF supervisor switchover MIB notifications. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 151 Enables upgrade notifications. Optionally, enables [UpgradeJobStatusNotify] the following specific notifications: [UpgradeOpNotifyOnCompletion] • UpgradeJobStatusNotify—Enables upgrade Example: job status notifications. switch(config)# snmp-server enable traps upgrade • UpgradeOpNotifyOnCompletion—Enables upgrade global status notifications. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 152: Disabling Link Notifications On An Interface
This command is enabled by default. Example: switch(config-if)# no snmp trap link-status Step 4 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config-if)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 153: Displaying Snmp Ifindex For An Interface
Assigning SNMP Device Contact and Location Information You can assign the device contact information, which is limited to 32 characters (without spaces) and the device location. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 154: Configuring The Context To Network Entity Mapping
Before You Begin Determine the logical network entity instance. For more information on VRFs and protocol instances, see the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide or the Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide. Procedure...
Page 155: Disabling Snmp
Enters global configuration mode. Example: switch# configure terminal switch(config)# Step 2 no snmp-server protocol enable Disables SNMP. SNMP is enabled by default. Example: switch(config)# no snmp-server protocol enable Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 156: Modifying The Aaa Synchronization Time
Configuring SNMP Modifying the AAA Synchronization Time Modifying the AAA Synchronization Time You can modify how long Cisco NX-OS holds the synchronized user configuration. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal...
Page 157: Configuration Examples For Snmp
Displays SNMPv3 users. Configuration Examples for SNMP This example shows how to configure Cisco NX-OS to send the Cisco linkUp or Down notifications to one notification host receiver using the Blue VRF and defines two SNMP users, Admin and NMS: configure terminal snmp-server contact Admin@company.com...
Page 158 Enter configuration commands, one per line. End with CNTL/Z. switch(config)# feature ospf switch(config)# router ospf Enterprise switch(config-router)# exit switch(config)# snmp-server context public1 instance Enterprise switch(config)# snmp-server mib community-map public context public1 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 159: Additional References
View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) MIBs MIBs MIBs Link MIBs related to SNMP To locate and download supported MIBs, go to the following URL: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 160: Cisco Nexus 9000 Series Nx-Os System Management Configuration Guide, Release
Configuring SNMP MIBs Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 161: Configuring Rmon
You can use alarms with RMON events to generate a log entry or an SNMP notification when the RMON alarm triggers. RMON is enabled by default, but no alarms are configured in Cisco NX-OS. You can configure RMON alarms by using the CLI or an SNMP-compatible network management station.
Page 162: Rmon Alarms
You may choose to use the default RMON events template configuration or you can delete these entries Note and create new RMON events. Until you create RMON alarm configurations, no alarms will be triggered by these configurations. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 163: High Availability For Rmon
Configuring RMON High Availability for RMON High Availability for RMON Cisco NX-OS supports stateless restarts for RMON. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration. Virtualization Support for RMON Cisco NX-OS supports one instance of RMON.
Page 164: Configuring Rmon
Configuring RMON Configuring RMON Configuring RMON Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Configuring RMON Alarms You can configure RMON alarms on any integer-based SNMP MIB object.
Page 165: Configuring Rmon Events
Displays information about RMON events. Example: switch(config)# show rmon events Step 4 copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 166: Verifying The Rmon Configuration
0 owner test rmon event 1 trap trap1 Additional References MIBs MIBs MIBs Link MIBs related to RMON To locate and download supported MIBs, go to the following URL: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/ Nexus9000MIBSupportList.html Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 167: About Online Diagnostics
C H A P T E R Configuring Online Diagnostics This chapter describes how to configure the generic online diagnostics (GOLD) feature on Cisco NX-OS devices. This chapter contains the following sections: • About Online Diagnostics, page 147 • Licensing Requirements for Online Diagnostics, page 151 •...
Page 168: Chapter 1 2 Configuring Online Diagnostics
Bootup Diagnostics Bootup Diagnostics Bootup diagnostics run during bootup and detect faulty hardware before Cisco NX-OS brings a module online. For example, if you insert a faulty module in the device, bootup diagnostics test the module and take it offline before the device uses the module to forward traffic.
Page 169 SecondaryBootROM 30 minutes active Verifies the integrity of the secondary boot device on the supervisor. BootFlash 30 minutes active Verifies access to the bootflash devices. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 170: On-Demand Diagnostics
Online diagnostics in high availability detect hardware failures and provide feedback to high availability software components to make switchover decisions. Cisco NX-OS supports stateless restarts for online diagnostics. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration.
Page 171: Virtualization Support
NX-OS with the nx-os image and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Guidelines and Limitations for Online Diagnostics Online diagnostics has the following configuration guidelines and limitations: •...
Page 172: Configuring Online Diagnostics
Configuring Online Diagnostics Configuring Online Diagnostics Configuring Online Diagnostics Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Setting the Bootup Diagnostic Level You can configure the bootup diagnostics to run the complete set of tests, or you can bypass all bootup diagnostic tests for a faster module bootup time.
Page 173: Activating A Diagnostic Test
Step 4 show diagnostic content module {slot (Optional) | all} Displays information about the diagnostics and their attributes. Example: switch(config)# show diagnostic content module 6 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 174: Starting Or Stopping An On-Demand Diagnostic Test
(Optional) Verifies that the diagnostic has been scheduled. Example: switch# show diagnostic status module Simulating Diagnostic Results You can simulate a diagnostic test result. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 175: Clearing Diagnostic Results
To display online diagnostics configuration information, perform one of the following tasks: Command Purpose Displays information about bootup diagnostics. show diagnostic bootup level show diagnostic content module {slot | all} Displays information about diagnostic test content for a module. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 176: Configuration Examples For Online Diagnostics
This example shows how to activate test 2 and set the test interval on module 6: configure terminal diagnostic monitor module 6 test 2 diagnostic monitor interval module 6 test 2 hour 3 min 30 sec 0 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 177: Configuring The Embedded Event Manager
EEM consists of three major components: • Event statements—Events to monitor from another Cisco NX-OS component that may require some action, workaround, or notification. • Action statements—An action that EEM can take, such as sending an e-mail, or disabling an interface, to recover from an event.
Page 178: Policies
(the default option). EEM maintains event logs on the supervisor. Cisco NX-OS has a number of preconfigured system policies. These system policies define many common events and actions for the device. System policy names begin with two underscore characters (__).
Page 179: Event Statements
If you want to allow the triggered event to process any default actions, you must configure the EEM policy Note to allow the event default action statement. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 180: Action Statements
For example, you can create an environment variable for the IP address of an external e-mail server. You can use an environment variable in action statements by using the parameter substitution format. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 181: Eem Event Correlation
High Availability Cisco NX-OS supports stateless restarts for EEM. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration.
Page 182: Default Settings For Eem
• EEM event correlation does not override the system default policies. • Default action execution is not supported for policies that are configured with tagged events. • You can invoke EEM from Python. For more information about Python, see the Cisco Nexus 9000 Series NX-OS Programmability Guide.
Page 183: Defining A User Policy Using The Cli
Registers the applet with EEM and enters applet configuration mode. The applet-name can be any case-sensitive, alphanumeric string up to 29 Example: characters. switch(config)# event manager applet monitorShutdown switch(config-applet)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 184: Configuring Event Statements
Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Configuring Event Statements Use one of the following commands in EEM configuration mode to configure an event statement: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 185 Triggers an event if a fan fails for more than the Example: configured time, in seconds. The number range is module dependent. The seconds range is from 10 to switch(config-applet)# event fanbad time 64000. 3000 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 186 {all | module-num} selected status. Example: The tag tag keyword-argument pair identifies this switch(config-applet)# event module status specific event when multiple events are included in offline module all the policy. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 187 0 to 4294967295, where 0 indicates no time limit. Triggers an event if the power budget exceeds the event poweroverbudget Example: capacity of the configured power supplies. switch(config-applet)# event poweroverbudget Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 188 Triggers an event if the temperature sensor exceeds threshold {any | major | minor} the configured threshold. The sensor range is from 1 to 18. Example: switch(config-applet)# event temperature module 2 threshold any Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 189: Configuring Action Statements
The action label is in the format Example: number1.number2. switch(config-applet)# action 1.0 cli “show interface e 3/1“ number can be any number up to 16 digits. The range for number2 is from 0 to 9. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 190 Forces one or more modules or the entire system to reload. Example: switch(config-applet)# action 1.0 reload number can be any number up to 16 digits. The range module 3-5 for number2 is from 0 to 9. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 191: Defining A Policy Using A Vsh Script
Step 3 Copy the file to the following system directory: bootflash://eem/user_script_policies. Registering and Activating a VSH Script Policy You can register and activate a policy defined in a VSH script. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 192: Overriding A Policy
Hash default, Count 0 Step 3 event manager applet applet-name override Overrides a system policy and enters applet system-policy configuration mode. The applet-name can be any case-sensitive alphanumeric string up to 29 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 193: Configuring Memory Thresholds
You can set the memory thresholds used to trigger events and set whether the operating system should kill processes if it cannot allocate memory. Before You Begin Ensure that you are logged in with administrator privileges. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 194 The default value is to allow the system to kill processes, starting with the one that consumes the Example: most memory. switch(config)# system memory-thresholds threshold critical no-process-kill Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 195: Configuring Syslog As Eem Publisher
| period seconds | pattern the search string in the policy. msg-text | priority priority} • The tag tag keyword-argument pair identifies this specific event when multiple events are included in the policy. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 196: Verifying The Eem Configuration
| moderate | severe}] show event manager policy-state policy-name Displays information about the policy state, including thresholds. show event manager script system [policy-name | Displays information about the script policies. all] Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 197: Configuration Examples For Eem
“copy run start” event syslog tag three pattern “hello” tag one or two or three happens 1 in 120 action 1.0 reload module 1 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 198 Configuring the Embedded Event Manager Configuration Examples for EEM For additional EEM configuration examples, see Embedded Event Manager System Events and Note Configuration Examples, on page 237. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 199: Configuring Onboard Failure Logging
Additional References, page 184 About OBFL Cisco NX-OS provides the ability to log failure data to persistent storage, which you can retrieve and display for analysis at a later time. This onboard failure logging (OBFL) feature stores failure and environmental information in nonvolatile memory on the module.
Page 200: Licensing Requirements For Obfl
• OBFL flash supports a limited number of writes and erases. The more logging you enable, the faster you use up this number of writes and erases. Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS.
Page 201: Configuring Obfl
Enables the OBFL hw-module logging onboard environmental-history environmental history. Example: switch(config)# hw-module logging onboard environmental-history Module: 7 Enabling environmental-history ... was successful. Module: 10 Enabling environmental-history ... was successful. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 202: Verifying The Obfl Configuration
Verifying the OBFL Configuration To display OBFL information stored in flash on a module, perform one of the following tasks: Command Purpose show logging onboard boot-uptime Displays the boot and uptime information. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 203 Enabled stack-trace Enabled Module: 22 OBFL Log: Enabled cpu-hog Enabled credit-loss Enabled environmental-history Enabled error-stats Enabled exception-log Enabled interrupt-stats Enabled mem-leak Enabled miscellaneous-error Enabled obfl-log (boot-uptime/device-version/obfl-history) Enabled register-log Enabled Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 204: Configuration Example For Obfl
This example shows how to enable OBFL on module 2 for environmental information: switch# configure terminal switch(config)# hw-module logging onboard module 2 environmental-history Additional References Related Documents Related Topic Document Title Configuration files Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 205: Chapter 1 5 Configuring Span
SPAN sources include the following: • Ethernet ports (but not subinterfaces) • Port channels • The inband interface to the control plane CPU Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 206: Characteristics Of Source Ports
VLANs can be SPAN sources only in the ingress direction. Note • Satellite ports and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender (FEX) These interfaces are supported in Layer 2 access mode and Layer 2 trunk mode. They Note are not supported in Layer 3 mode, and Layer 3 subinterfaces are not supported.
Page 207: Characteristics Of Destination Ports
SPAN Sessions You can create SPAN sessions to designate sources and destinations to monitor. See the Cisco Nexus 9000 Series NX-OS Verified Scalability Guide for information on the number of supported SPAN sessions. This figure shows a SPAN configuration. Packets on three Ethernet ports are copied to destination port Ethernet 2/5.
Page 208: Acl Tcam Regions
High Availability The SPAN feature supports stateless and stateful restarts. After a reboot or supervisor switchover, the running configuration is applied. For more information on high availability, see the Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide. Licensing Requirements for SPAN...
Page 209 • VLAN ACL redirects to SPAN destination ports are not supported. • VLAN and ACL filters are not supported for FEX ports. • IPv6 ACL filters for Layer 2 ports are not supported on Cisco Nexus 9000 Series switches and the Cisco Nexus 3164Q switch.
Page 210: Default Settings For Span
• SPAN is supported in Layer 3 mode; however, SPAN is not supported on Layer 3 subinterfaces or Layer 3 port-channel subinterfaces. • Cisco NX-OS does not span Link Layer Discovery Protocol (LLDP) or Link Aggregation Control Protocol (LACP) packets when the source interface is not a host interface port channel.
Page 211 Configuring SPAN Configuring a SPAN Session Before You Begin You must configure the destination ports in access or trunk mode. For more information, see the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide. Procedure Command or Action Purpose Step 1 Enters global configuration mode.
Page 212 The SPAN destination port must be either Note Example: an access port or a trunk port. You must enable monitor mode on the Note switch(config-monitor)# destination interface ethernet 2/5 destination port. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 213: Shutting Down Or Resuming A Span Session
The no form of the command resumes (enables) the Example: specified SPAN sessions. By default, sessions are created switch(config)# monitor session in the shut state. 3 shut Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 214: Verifying The Span Configuration
{all | session-number | range Displays the SPAN session configuration. session-range} [brief] Configuration Examples for SPAN Configuration Example for a SPAN Session To configure a SPAN session, follow these steps: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 215: Configuration Example For A Unidirectional Span Session
2/5 switch(config-if)# switchport switch(config-if)# switchport monitor switch(config-if)# no shut switch(config-if)# exit switch(config)# Step 2 Configure a SPAN session. Example: switch(config)# no monitor session 3 switch(config)# monitor session 3 rx Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 216: Configuration Example For A Span Acl
1 switch(config-erspan-src)# filter access_group span_filter Additional References Related Documents Related Topic Document Title Cisco Nexus 2000 Series NX-OS Fabric Extender Software Configuration Guide for Cisco Nexus 9000 Series Switches Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 217: Configuring Erspan
The packet is decapsulated at the destination router and then sent to the destination interface. ERSPAN Types Cisco Nexus 9300 Series switches support ERSPAN Type II, and Cisco Nexus 9500 Series switches support only ERSPAN. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 218: Erspan Sources
VLANs can be ERSPAN sources only in the ingress direction. Note • Satellite ports and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender (FEX) Note These interfaces are supported in Layer 2 access mode and Layer 2 trunk mode. They are not supported in Layer 3 mode, and Layer 3 subinterfaces are not supported.
Page 219: High Availability
The ERSPAN feature supports stateless and stateful restarts. After a reboot or supervisor switchover, the running configuration is applied. For more information on high availability, see the Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide. Licensing Requirements for ERSPAN...
Page 220: Default Settings
• ERSPAN and ERSPAN ACL sessions are terminated identically at the destination router only when the ERSPAN destination IP address is resolved through Cisco Nexus 9300 Series switch uplink ports. • VLAN and ACL filters are not supported for FEX ports.
Page 221: Configuring Erspan
Configuring ERSPAN Configuring ERSPAN Configuring ERSPAN Be aware that the Cisco NX-OS commands for this feature may differ from those commands used in Cisco Note IOS. Configuring an ERSPAN Source Session You can configure an ERSPAN session on the local device only. By default, ERSPAN sessions are created in the shut state.
Page 222 Step 11 destination ip ip-address Configures the destination IP address in the ERSPAN session. Only one destination IP address is supported per ERSPAN source session. Example: switch(config-erspan-src)# destination ip 10.1.1.1 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 223 (Optional) Displays the running ERSPAN configuration. Example: switch(config)# show running-config monitor Step 20 (Optional) show startup-config monitor Displays the ERSPAN startup configuration. Example: switch(config)# show startup-config monitor Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 224: Shutting Down Or Activating An Erspan Session
Enters the monitor configuration mode for the ERSPAN source type. The new session erspan-source configuration is added to the existing session configuration. Example: switch(config)# monitor session 3 type erspan-source switch(config-erspan-src)# Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 225: Verifying The Erspan Configuration
To display the ERSPAN configuration, perform one of the following tasks: Command Purpose show monitor session {all | session-number | range Displays the ERSPAN session configuration. session-range} [brief] show running-config monitor Displays the running ERSPAN configuration. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 226: Configuration Examples For Erspan
10 switch(config-access-map)# match ip address match_12_pkts switch(config-access-map)# action forward switch(config-access-map)# exit switch(config)# monitor session 1 type erspan-source switch(config-erspan-src)# filter access_group erspan_filter Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 227: Additional References
Configuring ERSPAN Additional References Additional References Related Documents Related Topic Document Title Cisco Nexus 2000 Series NX-OS Fabric Extender Software Configuration Guide for Cisco Nexus 9000 Series Switches Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 228 Configuring ERSPAN Related Documents Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 229: Configuring Lldp
The Cisco Discovery Protocol (CDP) is a device discovery protocol that allows network management applications to automatically discover and learn about other Cisco devices that are connected to the network. To permit the discovery of non-Cisco devices, the switch also supports the Link Layer Discovery Protocol (LLDP), a vendor-neutral device discovery protocol that is defined in the IEEE 802.1ab standard.
Page 230: High Availability
High Availability The LLDP feature supports stateless and stateful restarts. After a reboot or supervisor switchover, the running configuration is applied. For more information on high availability, see the Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide. Virtualization Support One instance of LLDP is supported.
Page 231: Default Settings For Lldp
LLDP transmit Enabled, after LLDP is enabled globally Configuring LLDP Cisco NX-OS commands for this feature may differ from Cisco IOS commands for a similar feature. Note Enabling or Disabling LLDP Globally You can enable or disable LLDP globally on a device. You must enable LLDP globally to allow a device to send and receive LLDP packets.
Page 232: Enabling Or Disabling Lldp On An Interface
Enables or disables the reception of LLDP packets on an interface. After you globally enable LLDP, it is enabled on all supported interfaces by default. Example: switch(config-if)# lldp receive Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 233: Configuring Optional Lldp Parameters
[no] lldp timer seconds (Optional) Specifies the transmission frequency of LLDP updates in seconds. Example: switch(config)# lldp timer 50 The range is 5 to 254 seconds; the default is 30 seconds. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 234: Verifying The Lldp Configuration
LLDP packets sent and received by the device, the number of discarded packets, and the number of unrecognized TLVs. show lldp traffic interface interface slot/port Displays the number of LLDP packets sent and received on the interface. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 235: Configuration Example For Lldp
200 switch(config)# lldp reinit 5 switch(config)# lldp timer 50 switch(config)# no lldp tlv-select port-vlan switch(config)# no lldp tlv-select system-name Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 236 Configuring LLDP Configuration Example for LLDP Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 237: About Smus
SMUs are not an alternative to maintenance releases. They provide a quick resolution of immediate issues. All defects fixed by SMUs are integrated into the maintenance releases. For information on upgrading your device to a new feature or maintenance release, see the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide.
Page 238: Performing Software Maintenance Upgrades
• All processes in the line cards might be restarted. Restarting processes in the line cards is equivalent to a soft reset. • The line cards might reload. • No processes in the line cards might be affected. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 239: Prerequisites For Smus
• Each CLI install request is assigned a request ID, which can be used later to review the events. • If you perform a software maintenance upgrade and later upgrade your device to a new Cisco NX-OS software release, the new image will overwrite both the previous Cisco NX-OS release and the SMU package file.
Page 240: Performing A Software Maintenance Upgrade For Cisco Nx-Os
Active Packages: Active Packages on Module #3: Active Packages on Module #6: Active Packages on Module #7: Active Packages on Module #22: Active Packages on Module #30: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 241: Downloading The Smu Package File From Cisco.com
Go to the Download Software page at this URL: http://software.cisco.com/download/navigator.html Step 3 In the Select a Product list, choose Switches > Data Center Switches > Cisco Nexus 9000 Series Switches > model. Step 4 Choose the appropriate SMU file for your device and click Download.
Page 242 Copying the Package File to a Local Storage Device or Network Server • SSH File Transfer Protocol—SFTP is part of the SSHv2 feature in the security package and provides for secure file transfers. For more information, see the Cisco Nexus 9000 Series NX-OS Security Configuration Guide.
Page 243 If you want to specify an absolute path for the directory, you must add a “/” following the server address. • filename—The name of the package file that you want to add. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 244: Adding And Activating Packages
Copying the Package File to a Local Storage Device or Network Server, on page 221. Procedure Command or Action Purpose Step 1 Connect to the console port and log in. Establishes a CLI management session to the console port. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 245 (Optional) Displays the inactive packages on the device. Verify that the package added in the previous step appears in the Example: display. switch# show install inactive Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 246: Committing The Active Package Set
Before you commit a package set, verify that the device is operating correctly and is forwarding packets as expected. Complete the procedure described in Adding and Activating Packages, on page 224. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 247: Deactivating And Removing Packages
The package files can be reactivated later, or they can be removed from the disk. The Cisco NX-OS software also provides the flexibility to roll back the selected package set to a previously saved package set. If you find that you prefer a previous package set over the currently active package set, you can use the install deactivate and install commit commands to make a previously active package set active again.
Page 248 Proceed with removing? (y/n)? [n] y with the filename argument. • To remove all inactive packages from all nodes in the system, use the install remove command with the inactive keyword. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 249: Displaying Installation Log Information
Install operation 7 completed successfully at Thu Jan 9 01:21:10 201 This example shows how to display additional information, including any impact to nodes and processes: switch# show install log detail Thu Jan 9 01:24:03 2014 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 250 The software will be activated with system reload Install operation 18 !!WARNING!! This patch will get activated only after a reload of the switch. at Sun Mar 9 00:42:12 2014 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 251: Performing A Software Maintenance Upgrade For Guest Shell Bash
Access to the guest shell will be temporarily you will need to repeat this procedure after disabled while it synchronizes contents to a supervisor switchover. standby. Are you sure you want to continue? (y/n) [n] Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 252: Additional References
Guest Shell Bash SMU for Bash vulnerabilities CVE-2014-6277, CVE-2014-6278, CVE-2014-7186, and CVE-2014-7187 n9000-dk9.6.1.2.I3.1.CSCur02700.bin 6.1(2)I3(1) and all Cisco NX-OS SMU for CSCur02700 6.1(2)I2(x) releases (Bash vulnerabilities CVE-2014-6277, CVE-2014-6278, CVE-2014-7186, and CVE-2014-7187) Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 253 Performing Software Maintenance Upgrades SMU History SMU Package File Releases Description n9000-dk9.6.1.2.I2.1.CSCup81353.bin 6.1(2)I2(1), 6.1(2)I2(2), Cisco NX-OS SMU for CSCup81353 6.1(2)I2(2a), and 6.1(2)I2(3) Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 254 Performing Software Maintenance Upgrades SMU History Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 255: Ietf Rfcs Supported By Cisco Nx-Os System Management
A P P E N D I X IETF RFCs supported by Cisco NX-OS System Management This appendix lists the IETF RFCs for system management supported in Cisco NX-OS. • IETF RFCs Supported by Cisco NX-OS System Management, page 235 IETF RFCs Supported by Cisco NX-OS System Management This appendix lists the IETF RFCs for system management supported in Cisco NX-OS.
Page 256 IETF RFCs supported by Cisco NX-OS System Management IETF RFCs Supported by Cisco NX-OS System Management Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 257: Appendix B Embedded Event Manager System Events And Configuration Examples
10 consecutive failures of GOLD "RewriteEngine" test __asic_register_check Do CallHome, log error, and disable further HM testing for that ASIC device/instance after 20 consecutive failures of GOLD "ASICRegisterCheck" test Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 258 Syslog when fan goes bad __pfm_fanbad_any_singlefan Syslog when fan goes bad __pfm_power_over_budget Syslog warning for insufficient power overbudget __pfm_tempev_major TempSensor Major Threshold. Action: Shutdown __pfm_tempev_minor TempSensor Minor Threshold. Action: Syslog Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 259: Eem Events
The following table describes the EEM events you can use on the device. EEM Event Description application Publishes an application-specific event. CLI command is entered that matches a pattern with a wildcard. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 260 System manager generates an event. temperature Temperature level in the system exceeds a threshold. timer Specified time is reached. track Tracked object changes state. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 261: Configuration Examples For Eem Policies
Enter configuration commands, one per line. End with CNTL/Z. switch(config)# switch(config)# event manager applet rollbackTrigger switch(config-applet)# switch(config-applet)# description “Rollback trigger.” switch(config-applet)# event cli match “rollback *” switch(config-applet)# action 1.0 cli copy running-config bootflash:last_config switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 262: Configuration Examples To Override (Disable) Major Thresholds
2 sensor 7 threshold major switch(config-applet)# end This example shows how to revert to the default configuration: switch# configure terminal switch(config)# no event manager applet myappletname override __pfm_tempev_major switch(config)# end Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 263: Overriding (Disabling) An Entire Module
__pfm_tempev_major switch(config-applet)# end switch# configure terminal switch(config)# event manager applet myapplet2 override __pfm_tempev_major switch(config-applet)# event temperature module 9 sensor 4 threshold major switch(config-applet)# action 2 policy-default switch(config-applet)# end Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 264: Modules
2 sensor 7 threshold major switch(config-applet)# action 4 policy-default switch(config-applet)# end switch# configure terminal switch(config)# event manager applet myapplet5 override __pfm_tempev_major switch(config-applet)# event temperature module 3 threshold major Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 265: Configuration Examples To Override (Disable) Shutdown For Fan Tray Removal
4 time 60 switch(config-applet)# end This example shows how to revert to the default configuration: switch# configure terminal switch(config)# no event manager applet myappletname override __pfm_fanabsent_any_singlefan switch(config)# end Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 266: Overriding (Disabling) A Shutdown For Removal Of All Fan Trays Except One
Configuration Examples to Create a Supplemental Policy Creating a Supplemental Policy for the Fan Tray Absent Event This example shows how to create a supplemental policy using the event fanabsent command: Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 267: Creating A Supplemental Policy For The Temperature Threshold Event
You can specify a list of modules that the power over-budget action uses to shut down modules until the power recovers from the red (negative) zone. Empty slots and slots that contain a supervisor, standby supervisor, spine, or crossbar are skipped. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 268: Configuration Examples To Select Modules To Shut Down
The device-type can be fan, module, or powersupply. The event-type can be insert, remove, or anyoir (insert or remove). The optional device-number specifies a single device. If omitted, all devices are selected. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 269: Configuration Example To Generate A User Syslog
CPU utilization of the switch: cseSysCPUUtilization OBJECT-TYPE SYNTAX Gauge32 (0..100 ) UNITS "%" MAX-ACCESS read-only STATUS current DESCRIPTION "The average utilization of CPU on the active supervisor." ::= { ciscoSysInfoGroup 1 } Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 270: Sending An Snmp Notification In Response To An Event In The Event Policy
Configure an EEM event to bring up Ethernet interface 1/2 when Ethernet interface 3/23 comes up. Example: switch# configure terminal switch(config)# event manager applet track_3_23_up switch(config-applet)# event track 1 state up switch(config-applet)# action 1 syslog msg EEM applet track_3_23_down bringing up port Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 271: Configuration Example To Register An Eem Policy With The Eem
• These five files need to be created and loaded into the above directory: ◦ load_schedules ◦ remove_vpc_if_peer_failed ◦ clean_up ◦ unload_schedules ◦ restore_vpc Configuration for the load_schedules file: feature scheduler configure terminal scheduler job name vpc_check configure terminal Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 272 Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 273 2.0 syslog msg severity alert "##### VPC PEER DETECTED. VPC CONFIG RESTORED #####" action 3.0 cli configure terminal action 4.0 cli copy bootflash:eem/user_script_policies/unload_schedules running-config action 5.0 cli no event manager applet restore_vpc action 6.0 cli end Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 274 Embedded Event Manager System Events and Configuration Examples Configuration Example to Register an EEM Policy with the EEM Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 275: Appendix C Configuration Limits For Cisco Nx-Os System Management
A P P E N D I X Configuration Limits for Cisco NX-OS System Management The configuration limits are documented in the Cisco Nexus 9000 Series NX-OS Verified Scalability Guide. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...
Page 276 Configuration Limits for Cisco NX-OS System Management Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x...

Cisco Nexus 9000 Series Configuration Manual

CHAPTER 2 Overview 3

Configuring NTP

Configuring CDP

Configuring System Message Logging

Configuring Smart Call Home

Configuring Rollback

Configuring Session Manager

Configuring the Scheduler

C H a P T E

Configuring SNMP

Snmp-Server Enable Traps Aaa Server-State-Change

Snmp-Server Enable Traps Bgp

Snmp-Server Enable Traps Bridge Newroot

Snmp-Server Enable Traps Callhome Event-Notify

Snmp-Server Enable Traps Config

Snmp-Server Enable Traps Eigrp [Tag]

Snmp-Server Enable Traps Entity

Snmp-Server Enable Traps Feature-Control Featureopstatuschange

Snmp-Server Enable Traps Hsrp State-Change

Rfcs

Mibs

Configuring RMON

Chapter 1 2 Configuring Online Diagnostics

Configuring the Embedded Event Manager

Configuring Onboard Failure Logging

Chapter 1 5 Configuring SPAN

Quick Links

Related Manuals for Cisco Nexus 9000 Series

Summary of Contents for Cisco Nexus 9000 Series