Page 1 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x First Published: 2018-06-14 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 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: https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.
Page 3: Table Of Contents
Licensing Requirements for PTP Guidelines and Limitations for PTP Default Settings for PTP Configuring PTP Configuring PTP Globally Configuring PTP on an Interface Configuring Multiple PTP Domains Configuring PTP Grandmaster Clock Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 4 C H A P T E R 5 Configuring System Message Logging Information About System Message Logging Syslog Servers Licensing Requirements for System Message Logging Guidelines and Limitations for System Message Logging Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 5 Configuring Contact Information Creating a Destination Profile Modifying a Destination Profile Associating an Alert Group with a Destination Profile Adding Show Commands to an Alert Group Configuring E-Mail Server Details Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 6 Guidelines and Limitations for the Scheduler Default Settings for the Scheduler Configuring the Scheduler Enabling the Scheduler Defining the Scheduler Log File Size Configuring Remote User Authentication Defining a Job Deleting a Job Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 7 Creating SNMP Communities Filtering SNMP Requests Configuring SNMP Notification Receivers Configuring SNMP Notification Receivers with VRFs Filtering SNMP Notifications Based on a VRF Configuring SNMP for Inband Access Enabling SNMP Notifications Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 8 C H A P T E R 1 2 Configuring Embedded Event Manager About Embedded Event Manager Embedded Event Manager Policies Event Statements Action Statements VSH Script Policies Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x viii...
Page 9 Configuring an Ethernet Destination Port Configuring Source Ports Configuring Source Port Channels or VLANs Configuring the Description of a SPAN Session Activating a SPAN Session Suspending a SPAN Session Configuring a SPAN Filter Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 10 Configuration Example for an ERSPAN Source Session Configuration Example for an ERSPAN Destination Session Additional References Related Documents C H A P T E R 1 5 Configuring Warp SPAN Information About Warp SPAN Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 11 Displaying Buffer Histogram Data C H A P T E R 1 9 Performing Software Maintenance Upgrades (SMUs) About SMUs Package Management Prerequisites for SMUs Guidelines and Limitations for SMUs Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 12 Creating Feature Groups Changing User Role Interface Policies Changing User Role VLAN Policies Verifying the User Accounts and RBAC Configuration Configuring User Accounts Default Settings for the User Accounts and RBAC Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 13: Preface
Documentation Feedback, on page xiv • Related Documentation for Cisco Nexus 3000 Series Switches, on page xiv Audience This publication is for network administrators who install, configure, and maintain Cisco Nexus switches. Document Conventions Command descriptions use the following conventions: Convention...
Page 14: Obtaining Documentation And Submitting A Service Request
What's New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html. 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 15: New And Changed Information
Table 1: New and Changed Features Feature Description Added or Where Documented Changed in Release No updates since Cisco NX-OS First 7.x release. Not applicable Not applicable Release 6.x Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 16 New and Changed Information New and Changed Information Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 17: Overview
Session Manager Session Manager allows you to create a configuration and apply it in batch mode after the configuration is reviewed and verified for accuracy and completeness. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 18 SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 19 (sometimes called port mirroring or port monitoring) selects network traffic for analysis by a network analyzer. The network analyzer can be a Cisco SwitchProbe, a Fibre Channel Analyzer, or other Remote Monitoring (RMON) probes. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 20 Overview System Management Features Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 21: Configuring Ptp
PTP operates within a logical scope called a PTP domain. Starting from Cisco NXOS Release 6.0(2)A8(3), PTP supports configuring multiple PTP clocking domains, PTP grandmaster capability, PTP cost on interfaces for slave and passive election, and clock identity.
Page 22: Ptp Device Types
There are two kinds of transparent clocks: End-to-end transparent clock Measures the residence time of a PTP message and accumulates the times in the correction field of the PTP message or an associated follow-up message. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 23: Ptp Process
• The slave uses these timestamps to adjust its clock to the time of its master. High Availability for PTP Stateful restarts are not supported for PTP Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 24: Licensing Requirements For Ptp
Guidelines and Limitations for PTP • In a Cisco Nexus 3500 only environment, PTP clock correction is expected to be in the 1- to 2-digit range, from 1 to 99 nanoseconds. However, in a mixed environment, PTP clock correction is expected to be up to 3 digits, from 100 to 999 nanoseconds.
Page 25: Configuring Ptp
Configures the domain number to use for this clock. PTP domains allow you to use multiple number independent PTP clocking subdomains on a single network. The range for the number is from 0 to 128. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 26 Priority2 : 1 Clock Quality: Class : 248 Accuracy : 254 Offset (log variance) : 65535 Offset From Master : 0 Mean Path Delay : 0 Steps removed : 0 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 27: Configuring Ptp On An Interface
PTP is being enabled. You can only enable PTP on one VLAN on an interface. The range is from 1 to 4094. Step 8 (Optional) switch(config-if) # show ptp brief Displays the PTP status. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 28: Configuring Multiple Ptp Domains
The default value is 255. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config) # [no] feature ptp Enables or disables PTP on the device. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 29 # [no] ptp domain value Specify the values for domain and clock clock-accuracy-threshold value accuracy threshold. The default value is 254. The range for the domain value is from 0 to 127. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 30 GM CAPABILITY : ENABLED PTP DEFAULT DOMAIN : 0 PTP TRANSITION PRIORITY1 : 20 PTP TRANSITION PRIORITY2 : 255 PTP DOMAIN PROPERTY Domain-Number Domain-Priority Clock-Class Clock-Accuracy Ports Eth1/1 switch(config)# Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 31: Configuring Ptp Grandmaster Clock
The range for the domain value is from 0 to 127. The range for the clock-class-threshold value is from 0 to 255. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 32: Configuring Ptp Cost Interface
Configuring PTP Cost Interface You can configure interface cost on each PTP enabled port on a Cisco Nexus 3500 switch. The cost applies to each PTP enabled port if the switch has more than one path to grandmaster clock.
Page 33: Configuring Clock Identity
Eth1/1 switch(config)# Configuring clock Identity You can configure clock identity on a Cisco Nexus 3500 switch. The default clock identity is a unique 8-octet array presented in the form of a character array based on the switch MAC address. Procedure...
Page 34: Verifying The Ptp Configuration
Displays information about the interface to domain association. show ptp cost Displays PTP port to cost association. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 35: Configuring Ntp
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...
Page 36: Ntp As A Time Server
NTP as a Time Server the Cisco NX-OS device can use NTP to distribute time. Other devices can configure it as a time server. You can also configure the device to act as an authoritative NTP server, enabling it to distribute time even when it is not synchronized to an outside time source.
Page 37: Licensing Requirements For Ntp
• If you configure NTP in a VRF, ensure that the NTP server and peers can reach each other through the configured VRFs. • You must manually distribute NTP authentication keys on the NTP server and Cisco NX-OS devices across the network.
Page 38: Default Settings
The range for the max-poll and min-poll arguments is from 4 to 16 seconds, and the default values are 6 and 4, respectively. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 39 Saves the change persistently through reboots running-config startup-config and restarts by copying the running configuration to the startup configuration. Example This example shows how to configure an NTP server and peer: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 40: Configuring Ntp Authentication
This command provides protection against accidentally synchronizing the device to a time source that is not trusted. Step 5 (Optional) switch(config)# show ntp Displays the configured NTP trusted keys. trusted-keys Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 41: Configuring Ntp Access Restrictions
ACL rule in a configured peer, ACL processing stops and does not continue to the next access group option. • The peer keyword enables the device to receive time requests and NTP control Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 42: Configuring The Ntp Source Ip Address
NTP packets are sent. You can configure NTP to use a specific source IP address. To configure the NTP source IP address, use the following command in global configuration mode: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 43: Configuring The Ntp Source Interface
Enters global configuration mode. Step 2 switch(config)# [no] ntp logging Enables or disables system logs to be generated with significant NTP events. NTP logging is disabled by default. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 44: Enabling Cfs Distribution For Ntp
Example This example shows how to enable CFS distribution for NTP: switch# config t Enter configuration commands, one per line. End with CNTL/Z. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 45: Commiting Ntp Configuration Changes
After making the configuration changes, you can choose to discard the changes instead of committing them. If you discard the changes, Cisco NX-OS removes the pending database changes and releases the CFS lock. To discard NTP configuration changes, use the following command in global configuration mode:...
Page 46: Releasing The Cfs Session Lock
Step 7 Displays the temporary CFS database for NTP. show ntp pending Step 8 show ntp pending-diff Displays the difference between the pending CFS database and the current NTP configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 47: Configuration Examples For Ntp
NTP logging enabled. switch(config)# copy running-config startup-config [########################################] 100% switch(config)# This example shows an NTP access group configuration with the following restrictions: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 48: Related Documents For Ntp
This table includes only the updates for those releases that have resulted in additions or changes to the feature. Feature Name Releases Feature Information 5.0(3)A1(1) This feature was introduced. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 49: Configuring System Message Logging
System message logging is based on 3164. For more information about the system message format and the messages that the device generates, see the Cisco NX-OS System Messages Reference. By default, the Cisco Nexus device outputs messages to terminal sessions.
Page 50: Syslog Servers
You can configure the Cisco Nexus Series switch to sends logs to up to eight 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 51: Configuring System Message Logging
(a lower number value indicates a higher severity level). Severity levels range from 0 to 7: • 0 – emergency • 1 – alert • 2 – critical • 3 – error Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 52 (Optional) switch# copy running-config Copies the running configuration to the startup configuration. startup-config Example The following example shows how to configure a logging level of 3 for the console: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 53: Configuring System Message Logging To A File
The default severity level is 5 and the file size is 4194304. Severity levels range from 0 to 7: • 0 – emergency • 1 – alert Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 54 Logging server: disabled Logging logfile: enabled Name - my_log: Severity - informational Size - 4194304 Facility Default Severity Current Session Severity -------- ---------------- ------------------------ altos auth authpriv bootvar callhome capability Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 55: Configuring Module And Facility Messages Logging
• 0 – emergency • 1 – alert • 2 – critical • 3 – error • 4 – warning • 5 – notification • 6 – informational • 7 – debugging Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 56: Configuring Logging Timestamps
3 switch(config)# logging level aaa 2 Configuring Logging Timestamps You can configure the time-stamp units of messages logged by the Cisco Nexus Series switch. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode.
Page 57: Configuring Syslog Servers
Severity levels range from 0 to 7. See Table 5: System Message Severity Levels , on page • The use vrf vrf-name keyword and argument identify the default or Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 58 Saves the change persistently through reboots and restarts by copying the running Example: configuration to the startup configuration. switch(config)# copy running-config startup-config Example The following examples show how to configure a syslog server: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 59: Configuring Syslog On A Unix Or Linux System
$ chmod 666 /var/log/myfile.log Step 3 Make sure that the system message logging daemon reads the new changes by checking myfile.log after entering this command: $ kill -HUP ~cat /etc/syslog.pid~ Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 60: Configuring Syslog Server Configuration Distribution
Configuring syslog Server Configuration Distribution Configuring syslog Server Configuration Distribution You can distribute the syslog server configuration to other switches in the network by using the Cisco Fabric Services (CFS) infrastructure. After you enable syslog server configuration distribution, you can modify the syslog server configuration and view the pending changes before committing the configuration for distribution.
Page 61: Displaying And Clearing Log Files
2007 nov 1 15:10:0 switch# show logging nvram last 10 The following example shows how to clear messages in a log file: switch# clear logging logfile switch# clear logging nvram Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 62: Configuring Dom Logging
Verifying the DOM Logging Configuration Command Purpose show system ethernet dom polling status Displays the transceiver digital optical monitoring periodic polling status. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 63: Verifying The System Message Logging Configuration
Displays the syslog server configuration. show logging session Displays the logging session status. show logging status Displays the logging status. Displays the logging time-stamp units configuration. show logging timestamp Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 64 Configuring System Message Logging Verifying the System Message Logging Configuration Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 65: Configuring Smart Call Home
Technical Assistance Center (TAC). If you have a service contract directly with Cisco, you can register your devices for the Smart Call Home service. Smart Call Home provides fast resolution of system problems by analyzing Smart Call Home messages sent from your devices and providing background information and recommendations.
Page 66: Smart Call Home Overview
Cisco Nexus switches support the following predefined destination profiles: • CiscoTAC-1—Supports the Cisco-TAC alert group in XML message format. • full-text-destination—Supports the full text message format. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 67: Smart Call Home Alert Groups
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 68: Smart Call Home Message Levels
Network-wide catastrophic failure. Disaster Significant network impact. Fatal Emergency (0) System is unusable. Critical Alert (1) Critical conditions that indicate that immediate attention is needed. Major Critical (2) Major conditions. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 69: Call Home Message Formats
Data Item (Plain Text and XML) Description (Plain Text and XML) XML Tag (XML Only) Time stamp Date and time stamp of event in /aml/header/time ISO time notation: YYYY-MM-DD HH:MM:SS GMT+HH:MM Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 70 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 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 71 /aml/body/chassis/partNo chassis. Fields specific to a particular alert group message are inserted here. The following fields may be repeated if multiple CLI commands are executed for this alert group. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 72 Name of the affected FRU that is /aml/body/fru/name generating the event message. FRU s/n Serial number of the FRU. /aml/body/fru/serialNo FRU part number Part number of the FRU. /aml/body/fru/partNo Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 73: Guidelines And Limitations For Smart Call Home
Table 15: Default Call Home Parameters Parameters Default Destination message size for a message sent in full text format 4000000 Destination message size for a message sent in XML format 4000000 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 74: Configuring Smart Call Home
You must configure the e-mail, phone, and street address information for Smart Call Home. You can optionally configure the contract ID, customer ID, site ID, and switch priority information. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 75 The customer-number can be up to 255 alphanumeric characters. Step 9 (Optional) switch(config-callhome)# site-id Configures the site number for this switch. site-number The site-number can be up to 255 alphanumeric characters in free format. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 76: Creating A Destination Profile
Enters Smart Call Home configuration mode. Step 3 switch(config-callhome)# destination-profile Creates a new destination profile and sets the {ciscoTAC-1 {alert-group group | email-addr message format for the profile. The Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 77: Modifying A Destination Profile
• Message size—The allowed length of a Call Home message sent to the e-mail addresses in this destination profile. Note You cannot modify or delete the CiscoTAC-1 destination profile. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 78 5 switch(config-callhome)# destination-profile full-text-destination message-size 10000 switch(config-callhome)# What to do next Associate an alert group with a destination profile. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 79: Associating An Alert Group With A Destination Profile
Adds the show command output to any Call {Configuration | Diagnostic | Environmental Home messages sent for this alert group. Only | Inventory | License | Linecard-Hardware | valid show commands are accepted. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 80: Configuring E-Mail Server Details
Example The following example shows how to add the show ip routing command to the Cisco-TAC alert group: switch# configuration terminal switch(config)# callhome switch(config-callhome)# alert-group Configuration user-def-cmd show ip routing...
Page 81: Configuring Periodic Inventory Notifications
Displays information about Smart Call Home. Step 5 (Optional) switch(config)# copy Saves the change persistently through reboots running-config startup-config and restarts by copying the running configuration to the startup configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 82: Disabling Duplicate Message Throttling
Example The following example shows how to disable duplicate message throttling: switch# configuration terminal switch(config)# callhome switch(config-callhome)# no duplicate-message throttle switch(config-callhome)# What to do next Enable Smart Call Home. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 83: Enabling Or Disabling Smart Call Home
Enters global configuration mode. Step 2 switch(config)# callhome Enters Smart Call Home configuration mode. Step 3 switch(config-callhome) # callhome send Sends the specified Smart Call Home message diagnostic to all configured destinations. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 84: Verifying The Smart Call Home Configuration
Displays the technical support output for Smart Call Home. Sample Syslog Alert Notification in Full-Text Format This sample shows the full-text format for a syslog port alert-group notification: source:MDS9000 Switch Priority:7 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 85: Sample Syslog Alert Notification In Xml Format
<aml-session:Session xmlns:aml-session="http://www.example.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role= "http://www.w3.org/2003/05/soap-envelope/role/next"> <aml-session:To>http://tools.example.com/services/DDCEService</aml-session:To> <aml-session:Path> <aml-session:Via>http://www.example.com/appliance/uri</aml-session:Via> </aml-session:Path> <aml-session:From>http://www.example.com/appliance/uri</aml-session:From> <aml-session:MessageId>M2:69000101:C9D9E20B</aml-session:MessageId> </aml-session:Session> </soap-env:Header> <soap-env:Body> <aml-block:Block xmlns:aml-block="http://www.example.com/2004/01/aml-block"> <aml-block:Header> <aml-block:Type>http://www.example.com/2005/05/callhome/syslog</aml-block:Type> <aml-block:CreationDate>2018-02-25 14:19:55 GMT+00:00</aml-block:CreationDate> <aml-block:Builder> <aml-block:Name>Cat6500</aml-block:Name> <aml-block:Version>2.0</aml-block:Version> </aml-block:Builder> <aml-block:BlockGroup> <aml-block:GroupId>G3:69000101:C9F9E20C</aml-block:GroupId> <aml-block:Number>0</aml-block:Number> <aml-block:IsLast>true</aml-block:IsLast> <aml-block:IsPrimary>true</aml-block:IsPrimary> Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 86 Count and timestamp logging messages: disabled Trap logging: level informational, 72 message lines logged Log Buffer (8192 bytes): 00:00:54: curr is 0x20000 00:00:54: RP: Currently running ROMMON from F2 region Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 87 00:04:56: %DIAG-SP-6-RUN_MINIMUM: Module 4: Running Minimal Diagnostics... 00:00:09: DaughterBoard (Distributed Forwarding Card 3) Firmware compiled 11-Apr-08 03:34 by integ Build [100] slot_id is 8 00:00:31: %FLASHFS_HES-DFC8-3-BADCARD: /bootflash:: The flash card seems to Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 88 00:06:59: %OIR-SP-6-DOWNGRADE_EARL: Module 8 DFC installed is not identical to system PFC and will perform at current system operating mode. 00:07:06: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now online Router#]]> </aml-block:Data> </aml-block:Attachment> </aml-block:Attachments> </aml-block:Block> </soap-env:Body> </soap-env:Envelope> Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 89: Configuring Session Manager
• Configuration session—Creates a list of commands that you want to implement in session manager mode. • Validation—Provides a basic semantic check on your configuration. Cisco NX-OS returns an error if the semantic check fails on any part of the configuration.
Page 90: Configuring Session Manager
Step 5 switch(config-s-if)# ip port access-group name Adds a port access group to the interface. Step 6 (Optional) switch# show configuration session Displays the contents of the session. [name] Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 91: Verifying A Session
Ethernet 1/4 switch(config-s-ip)# ip port access-group acl2 in switch(config-s-ip)# exit switch(config-s)# verify switch(config-s)# exit Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 92: Verifying The Session Manager Configuration
Displays the contents of the configuration session. show configuration session status [name] Displays the status of the configuration session. show configuration session summary Displays a summary of all the configuration sessions. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 93: Configuring The Scheduler
• Periodic mode— A recurring interval that continues until you delete the job. You can configure the following types of intervals: • Daily— Job is completed once a day. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 94: Remote User Authentication
Licensing Requirements for the Scheduler This feature does not require a license. Any feature not included in a license package is bundled with the Cisco NX-OS system images 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.
Page 95: Default Settings For The Scheduler
Example This example shows how to enable the scheduler: switch# configure terminal switch(config)# feature scheduler switch(config)# show scheduler config config terminal feature scheduler scheduler logfile size 16 switch(config)# Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 96: Defining The Scheduler Log File Size
To configure an encrypted password, enter 7. Step 3 switch(config) # scheduler aaa-authentication Configures a clear text password for a remote username name password [0 | 7] password user. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 97: Defining A Job
The name is restricted to 31 characters. Step 5 (Optional) switch(config-job) # copy Saves the change persistently through reboots running-config startup-config and restarts by copying the running configuration to the startup configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 98: Deleting A Job
If you do not specify the time for the time commands, the scheduler assumes the current time. For example, if the current time is March 24, 2008, 22:00 hours,jobs are started as follows: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 99 Step 7 switch(config-schedule) # time start {now Indicates the job starts periodically. repeat repeat-interval | delta-time [repeat The start-time format is repeat-interval]} [[[[yyyy:]mmm:]dd:]HH]:MM. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 100: Clearing The Scheduler Log File
Step 2 switch(config) # clear scheduler logfile Clears the scheduler log file. Example This example shows how to clear the scheduler log file: switch# configure terminal switch(config)# clear scheduler logfile Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 101: Disabling The Scheduler
[name name] Displays the jobs configured. show scheduler logfile Displays the contents of the scheduler log file. show scheduler schedule [name name] Displays the schedules configured. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 102: Configuration Examples For The Scheduler
: back-cfg Job Status: Failed (1) Schedule Name : daily User Name : admin Completion time: Fri Jan 1 1:00:01 2009 --------------------------------- Job Output --------------------------------- `cli var name timestamp 2009-01-01-01.00.00` Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 103: Standards For The Scheduler
TFTP put operation was successful ============================================================================== switch# Standards for the Scheduler No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 104 Configuring the Scheduler Standards for the Scheduler Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 105: Configuring Snmp
• 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 106: Snmp Notifications
The switch cannot determine if the trap was received. An SNMP manager that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the Cisco Nexus device never receives a response, it can send the inform request again.
Page 107: User-Based Security Model
• Message origin authentication—Confirms that the claimed identity of the user who received the data was originated. • Message confidentiality—Ensures that information is not made available or disclosed to unauthorized individuals, entities, or processes. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 108: 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 indicates that this privacy password is for generating a 128-bit AES key #.The...
Page 109: Group-Based Snmp Access
Licensing Requirements for SNMP This feature does not require a license. Any feature not included in a license package is bundled with the Cisco NX-OS system images 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.
Page 110: Configuring Snmp
Configuring SNMP Configuring SNMP Configuring SNMP Configuring SNMP Users Note The commands used to configure SNMP users in Cisco NX-OS are different from those used to configure users in Cisco IOS. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode.
Page 111: Enforcing Snmp Message Encryption
You can configure SNMP to require authentication or encryption for incoming requests. By default, the SNMP agent accepts SNMPv3 messages without authentication and encryption. When you enforce privacy, Cisco NX-OS responds with an authorization error for any SNMPv3 PDU request that uses a security level parameter of either noAuthNoPriv or authNoPriv.
Page 112: Configuring Snmp Notification Receivers
The ACL applies to both IPv4 and IPv6 over UDP and TCP. After creating the ACL, assign the ACL to the SNMP community. For more information about creating ACLs, see the NX-OS security configuration guide for the Cisco Nexus Series software that you are using.
Page 113: Configuring Snmp Notification Receivers With Vrfs
192.0.2.1 informs version 3 auth NMS Configuring SNMP Notification Receivers with VRFs You can configure Cisco NX-OS to use a configured VRF to reach the host receiver. SNMP adds entries into the cExtSnmpTargetVrfTable of the CISCO-SNMP-TARGET-EXT-MIB when you configure the VRF reachability and filtering options for an SNMP notification receiver.
Page 114: Filtering Snmp Notifications Based On A Vrf
192.0.2.1 use-vrf Blue switch(config)# copy running-config startup-config Filtering SNMP Notifications Based on a VRF You can configure Cisco NX-OS filter notifications based on the VRF in which the notification occurred. Procedure Command or Action Purpose...
Page 115: Configuring Snmp For Inband Access
The following SNMPv2 example shows how to configure and inband access to the community comm which is not mapped: switch# config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# snmp-server context def vrf default Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 116: 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 CLI command enables both traps and informs, depending on the configured notification host receivers.
Page 117 [fru] Enables the ENTITY-MIB SNMP notifications. switch(config)# snmp-server enable traps license Enables the license SNMP notification. switch(config)# snmp-server enable traps port-security Enables the port security SNMP notifications. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 118: Configuring Link Notifications
You can disable linkUp and linkDown notifications on an individual interface. You can use these limit notifications on a flapping interface (an interface that transitions between up and down repeatedly). Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 119: Enabling One-Time Authentication For Snmp Over Tcp
You can configure an SNMP context to map to a logical network entity, such as a protocol instance or VRF. Procedure Command or Action Purpose Step 1 switch# configuration terminal Enters global configuration mode. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 120: Disabling Snmp
Verifying the SNMP Configuration To display SNMP configuration information, perform one of the following tasks: Command Purpose show snmp Displays the SNMP status. show snmp community Displays the SNMP community strings. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 121 Displays the SNMP engineID. show snmp group Displays SNMP roles. Displays SNMP sessions. show snmp sessions show snmp trap Displays the SNMP notifications enabled or disabled. show snmp user Displays SNMPv3 users. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 122 Configuring SNMP Verifying the SNMP Configuration Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 123: C H A P T E
You can use alarms with RMON events to generate a log entry or an SNMP notification when the RMON alarm triggers. RMON is disabled by default and no events or alarms are configured in Cisco Nexus devices. You can configure your RMON alarms and events by using the CLI or an SNMP-compatible network management station.
Page 124: Rmon Events
Configuring RMON RMON Events • Rising threshold—The value at which the Cisco Nexus device triggers a rising alarm or resets a falling alarm. • Falling threshold—The value at which theCisco Nexus device triggers a falling alarm or resets a rising alarm.
Page 125 Alarm 1 is active, owned by test Monitors 1.3.6.1.2.1.2.2.1.17.83886080 every 5 second(s) Taking delta samples, last value was 0 Rising threshold is 5, assigned to event 1 Falling threshold is 0, assigned to event 0 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 126: Configuring Rmon Events
Displays information about RMON hcalarms. Displays information about RMON logs. show rmon logs Default RMON Settings The following table lists the default settings for RMON parameters. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 127 Configuring RMON Default RMON Settings Table 21: Default RMON Parameters Parameters Default Alarms None configured. Events None configured. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 128 Configuring RMON Default RMON Settings Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 129: Configuring Online Diagnostics
Online diagnostics provide verification of hardware components during switch bootup or reset, and they monitor the health of the hardware during normal switch operation. Cisco Nexus Series switches support bootup diagnostics and runtime diagnostics. Bootup diagnostics include disruptive tests and nondisruptive tests that run during system bootup and system reset.
Page 130: Health Monitoring Diagnostics
Bootup diagnostics log any failures to the onboard failure logging (OBFL) system. Failures also trigger an LED display to indicate diagnostic test states (on, off, pass, or fail). You can configure Cisco Nexus device to either bypass the bootup diagnostics or run the complete set of bootup diagnostics.
Page 131: Configuring Online Diagnostics
Configures the bootup diagnostic level to trigger [complete | bypass] diagnostics when the device boots, as follows: • complete—Performs all bootup diagnostics. This is the default value. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 132: Verifying The Online Diagnostics Configuration
Displays the results of the diagnostics tests. Default Settings for Online Diagnostics The following table lists the default settings for online diagnostics parameters. Table 27: Default Online Diagnostics Parameters Parameters Default Bootup diagnostics level complete Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 133: C H A P T E
Configuring Syslog as an EEM Publisher, on page 131 About Embedded Event Manager The ability to detect and handle critical events in the Cisco NX-OS system is important for high availability. The Embedded Event Manager (EEM) provides a central, policy-driven framework to detect and handle events in the system by monitoring events that occur on your device and taking action to recover or troubleshoot these events, based on your configuration..
Page 134: Embedded Event Manager Policies
Preconfigured System Policies 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 (__). Some system policies can be overridden. In these cases, you can configure overrides for either the event or the action.
Page 135: Action Statements
When configuring action statements within your user policy or overriding policy, it is important that you confirm that action statements do not negate each other or adversely affect the associated system policy. Supported Actions EEM supports the following actions in action statements: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 136: Vsh Script Policies
Licensing Requirements for Embedded Event Manager This feature does not require a license. Any feature not included in a license package is bundled with the Cisco NX-OS system images 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.
Page 137: Defining A User Policy Using The Cli
Registers the applet with EEM and enters applet configuration mode. Example: The applet-name can be any case-sensitive, switch(config)# event manager applet alphanumeric string up to 29 characters. monitorShutdown switch(config-applet)# Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 138: Configuring Event Statements
Configure event statements and action statements. Configuring Event Statements Use one of the following commands in EEM configuration mode (config-applet) to configure an event statement: Before you begin Define a user policy. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 139 [time Uses the event configured in the system policy. seconds] Use this option for overriding policies. Example: The repeats range is from 1 to 65000. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 140 If you have already configured action statements or choose not to, complete any of the optional tasks: • Define a policy using a VSH script. Then, register and activate a VSH script policy. • Configure memory thresholds Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 141: Configuring Action Statements
The range for number2 is from 0 to 9. The counter can be any case-sensitive, alphanumeric string up to 28 characters. The val can be an integer from 0 to 2147483647 or a substituted parameter. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 142 # action 1.0 syslog priority notifications msg "cpu high" The number can be any number from 1 to 16 digits. The range for number2 is from 0 to 9. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 143: Defining A Policy Using A Vsh Script
Define a policy using a VSH script and copy the file to the system directory. Procedure Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 144: Overriding A System Policy
Use the show event manager system-policy Example: command to find the system policy names. switch(config-applet)# show event manager policy-state __ethpm_link_flap Policy __ethpm_link_flap Cfg count : 5 Cfg time interval : 10.000000 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 145: Configuring Syslog As An Eem Publisher
Configuring Syslog as an EEM Publisher Configuring syslog as an EEM publisher allows you to monitor syslog messages from the switch. Note The maximum number of searchable strings to monitor syslog messages is 10. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 146 Saves the change persistently through reboots and restarts by copying the running Example: configuration to the startup configuration. switch(config)# copy running-config startup-config What to do next Verify your EEM configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 147: Configuring Span
Information About SPAN The Switched Port Analyzer (SPAN) feature (sometimes called port mirroring or port monitoring) selects network traffic for analysis by a network analyzer. The network analyzer can be a Cisco SwitchProbe or other Remote Monitoring (RMON) probes. Guidelines and Limitations for SPAN SPAN have the following guideline and limitation: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 148: Span Sources
SPAN sessions. SPAN Sources SPAN sources refer to the interfaces from which traffic can be monitored. The Cisco Nexus device supports Ethernet, port channels, and VLANs as SPAN sources. With VLANs, all supported interfaces in the specified VLAN are included as SPAN sources.
Page 149: Characteristics Of Destination Ports
SPAN and ERSPAN filtering have the following guidelines and limitations: • Cisco Nexus 3500 Series switches drop the SPAN copies while spanning an interface in the rx direction and another interface in the tx direction when the traffic starts. It happens due to the default SPAN threshold limit being low and it cannot handle the burst traffic for SPAN.
Page 150: Span And Erspan Control-Packet Filtering
ERSPAN session are PTP enabled. SPAN and ERSPAN Control-packet Filtering Cisco NX-OS Release 6.0(2)A8(9) provides the ability to filter out CPU generated packets going out of the SPAN source interface. Control-packet filter is applied in the egress direction, and is therefore effective on source interfaces enabled for Tx mirroring.
Page 151: Guidelines And Limitations For Span And Erspan Sampling
• The supported sampling range is from 2 to 1023. SPAN and ERSPAN Truncation Cisco NX-OS Release 6.0(2)A4(1) introduces truncation of source packets for each SPAN or ERSPAN session based on the size of their MTU. Truncation helps reduce SPAN or ERSPAN bandwidth by reducing the size of packets monitored.
Page 152: Configuring An Ethernet Destination Port
Reverts to global configuration mode. Step 5 switch(config)# monitor session Enters monitor configuration mode for the session-number specified SPAN session. Step 6 switch(config-monitor)# destination interface Configures the Ethernet SPAN destination port. ethernet slot/port Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 153: Configuring Source Ports
Ethernet, Fibre Channel, or virtual Fibre Channel ports. You can specify the traffic direction to duplicate as ingress (Rx), egress (Tx), or both. By default, the direction is both. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 154: Configuring Source Port Channels Or Vlans
2 switch(config-monitor)# source vlan 1 switch(config-monitor)# Configuring the Description of a SPAN Session For ease of reference, you can provide a descriptive name for a SPAN session. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 155: Activating A Span Session
The following example shows how to activate a SPAN session: switch# configure terminal switch(config) # no monitor session 3 shut Suspending a SPAN Session By default, the session state is shut. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 156: Configuring A Span Filter
Enter configuration commands, one per line. End with CNTL/Z. switch(config)# monitor session 1 switch(config-monitor)# source interface Ethernet 1/7 rx switch(config-monitor)# filter ip 10.1.1.1 255.255.255.255 20.1.1.1 255.255.255.255 switch(config-monitor)# destination interface Ethernet 1/48 switch(config-monitor)# no shut Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 157: Configuring Span Sampling
100 switch(config-monitor)# sampling 10 switch(config-monitor)# destination interface ethernet 1/48 switch(config-monitor)# no shut switch(config-monitor)# show monitor session 1 session 1 --------------- type : local state : up Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 158: Configuring Span Truncation
# mtu size Configures the MTU size for truncation. Any SPAN packet that is larger than the configured MTU size is truncated to the configured size with a 4-byte offset. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 159: Displaying Span Information
The following example shows how to display SPAN session information: switch# show monitor SESSION STATE REASON DESCRIPTION ------- ----------- ---------------------- -------------------------------- The session is up down Session suspended down No hardware resource Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 160 The following example shows how to display SPAN session details: switch# show monitor session 2 session 2 --------------- type : local state : up source intf source VLANs destination ports : Eth3/1 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 161: Configuring Erspan
Additional References, on page 165 Information About ERSPAN The Cisco NX-OS system supports the Encapsulated Remote Switching Port Analyzer (ERSPAN) feature on both source and destination ports. ERSPAN transports mirrored traffic over an IP network. ERSPAN consists of an ERSPAN source session, routable ERSPAN generic routing encapsulation (GRE)-encapsulated traffic, and an ERSPAN destination session.
Page 162: Erspan Destinations
Only eight unidirectional, or four bidirectional ERSPAN or SPAN source sessions can run simultaneously across all switches. Only 20 ERSPAN destination sessions can run simultaneously across all switches. The following figure shows an ERSPAN configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 163: Multiple Erspan Sessions
To recover the real value of the ERSPAN timestamp, Cisco NX-OS Release 6.0(2)A4(1) introduces a periodical marker packet to carry the original UTC timestamp information and provide a reference for the ERSPAN timestamp.
Page 164: Prerequisites For Erspan
• ERSPAN is not supported for management ports. • A destination port can be configured in multiple ERSPAN session at a time. • You cannot configure a port as both a source and destination port. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 165 • Replicated multicast packets sent out of the ERSPAN source in the Tx direction are not sent to the ERSPAN destination. • Beginning with Cisco NX-OS Release 6.0(2)A8(6), you can monitor the same source interfaces (physical port or port-channel) in multiple ERSPAN (type 2 or type 3) sessions.
Page 166: Default Settings For Erspan
Example: switch(config)# monitor erspan origin ip-address 10.0.0.1 global Step 3 Configures the granularity of all ERSPAN monitor erspan granularity 100_ns{100_ms|100_ns|ns} sessions. Example: switch(config)# monitor erspan granularity 100_ns Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 167 Step 10 destination ip ip-address Configures the destination IP address in the ERSPAN session. Only one destination IP Example: address is supported per ERSPAN source switch(config-erspan-src)# destination session. ip 10.1.1.1 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 168 Displays the ERSPAN startup configuration. Example: switch(config-erspan-src)# show startup-config monitor Step 19 (Optional) copy running-config Copies the running configuration to the startup startup-config configuration. Example: switch(config-erspan-src)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 169: Configuring An Erspan Destination Session
ERSPAN session. The new session Example: configuration is added to the existing session switch(config-if)# no monitor session configuration. Step 8 monitor session {session-number | all} type Configures an ERSPAN destination session. erspan-destination Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 170 Displays the ERSPAN session configuration. session-number | range session-range} Example: switch(config)# show monitor session 3 Step 15 (Optional) show running-config monitor Displays the running ERSPAN configuration. Example: switch(config-erspan-src)# show running-config monitor Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 171: Shutting Down Or Activating An Erspan Session
If a monitor session is enabled but its operational status is down, then to enable the session, you must first specify the monitor session shut command followed by the no monitor session shut command. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 172: Configuring Erspan Filtering
Configuring ERSPAN Filtering You can configure SPAN filters for local and ERSPAN-source sessions only. SPAN and ERSPAN Filtering, on page 135 provides more information about filters. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 173 Enter configuration commands, one per line. End with CNTL/Z. switch(config)# monitor session 2 type erspan-source switch(config-erspan-src)# filter abcd.ef12.3456 1111.2222.3333 1234.5678.9012 1111.2222.3333 switch(config-erspan-src)# erspan-id 20 switch(config-erspan-src)# vrf default switch(config-erspan-src)# destination ip 200.1.1.1 switch(config-erspan-src)# source interface Ethernet 1/47 rx Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 174: Configuring Erspan Sampling
Step 6 switch(config-erspan-src)# destination ip Configures the destination IP address in the ip-address ERSPAN session. Only one destination IP address is supported per ERSPAN source session. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 175: Configuring Erspan Truncation
: 315 switch(config-erspan-src)# Configuring ERSPAN Truncation You can configure truncation for local and ERSPAN-source sessions only. SPAN and ERSPAN Truncation, on page 137 provides more information about truncation. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 176 Example The following example shows how to configure MTU truncation for an ERSPAN-source session: switch# configure terminal switch(config)# monitor session 6 type erspan-source switch(config-erspan-src)# mtu 1096 switch(config-erspan-src)# erspan-id 40 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 177: Configuring An Erspan Marker Packet
The marker-packet command only enables the marker-packet. switch# configure terminal switch(config)# monitor erspan origin ip-address 172.28.15.250 global switch(config)# monitor session 1 type erspan-source switch(config)# header-type 3 switch(config-erspan-src)# erspan-id 1 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 178: Verifying The Erspan Configuration
1 Note switch(config)# monitor erspan granularity 100_ns and switch(config-erspan-src)# header-type 3 are used only while configuring Type III source sessions. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 179: Configuration Example For An Erspan Destination Session
Related Documents Related Topic Document Title ERSPAN commands: complete command syntax, Cisco Nexus NX-OS System Management Command command modes, command history, defaults, usage Reference for your platform. guidelines, and examples Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 180 Configuring ERSPAN Related Documents Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 181: Configuring Warp Span
12 groups with a total of 47 destination ports (one port—port 1/36—is the fixed source port). See the following table. Table 30: Warp SPAN Groups Group Destination Ports Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 182: Guidelines And Limitations For Warp Span
Warp SPAN logs the following error: ERROR: Cannot configure group with member interfaces in admin DOWN state Configuring Warp SPAN You configure Warp SPAN by enabling it and then configuring its destination groups. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 183: Verifying Warp Span Mode Configuration
1 switch(config-if-range)# copy running-config startup-config Verifying Warp SPAN Mode Configuration You can verify the Warp SPAN mode configuration. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 184 : rx : Eth1/36 tx : both : source VLANs : rx : destination ports : Eth1/1 Eth1/2 Eth1/3 Eth1/4 Legend: f = forwarding enabled, l = learning enabled Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 185: Feature History For Warp Span
Configuring Warp SPAN Feature History for Warp SPAN Feature History for Warp SPAN Feature Name Release Feature Information Warp SPAN 5.0(3)A1(2) This feature was introduced. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 186 Configuring Warp SPAN Feature History for Warp SPAN Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 187: Configuring Dns
A name server may also store information about other parts of the domain tree. To map domain names to IP addresses in Cisco NX-OS, you must first identify the hostnames, then specify a name server, and enable the DNS service.
Page 188: High Availability
High Availability Cisco NX-OS supports stateless restarts for the DNS client. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration. Prerequisites for DNS Clients The DNS client has the following prerequisites: •...
Page 189 Step 7 (Optional) switch(config)# ip domain-lookup Enables DNS-based address translation. This feature is enabled by default. Step 8 (Optional) switch(config)# show hosts Displays information about DNS. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 190 The following example shows how to configure a default domain name and enable DNS lookup: switch# config t switch(config)# vrf context management switch(config)# ip domain-name mycompany.com switch(config)# ip name-server 172.68.0.10 switch(config)# ip domain-lookup Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 191: Configuring Traffic Forwarding Modes
Feature History for Warp Mode, on page 179 Information About Warp Mode The Cisco Nexus device uses a hardware component called the Algorithm Boost Engine (Algo Boost Engine) to support a forwarding mechanism, called warp mode. In warp mode, the access path is shortened by consolidating the forwarding table into single table, resulting in faster processing of frames and packets.
Page 192: Enabling And Disabling Warp Mode
Command or Action Purpose Step 1 switch# show hardware profile Displays information about warp mode and the forwarding-mode host, unicast, multicast, and Layer 2 ternary content addressable memory (TCAM) sizes. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 193: Feature History For Warp Mode
= 4096 multicast size = 8192 size = 8192 switch# Feature History for Warp Mode Feature Name Release Feature Information Warp Mode 5.0(3)A1(1) This feature was introduced. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 194 Configuring Traffic Forwarding Modes Feature History for Warp Mode Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 195: Configuring Active Buffer Monitoring
2 counter (which represents 384 KB to 768 KB) for Ethernet 1/4 is incremented. To avoid a counter overflow, the Cisco NX-OS software collects the histogram data every polling interval and maintains it in the system memory. The software maintains the histogram data in the system memory for the last 60 minutes with 1-second granularity.
Page 196: Buffer Histogram Data Access And Collection
• You can access the buffer histogram data using an XML interface. • You can configure Cisco NX-OS to log a message in the syslog whenever the buffer occupancy exceeds the configured threshold.
Page 197: Displaying Buffer Histogram Data
Step 2 (Optional) switch# clear hardware profile Clears the collected buffer data. buffer monitor Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 198 Class Threshold Limit = 4845 Kbytes ------------------------------------------------------------ Ethernet1/45 Ethernet1/46 Ethernet1/47 Ethernet1/48 Ethernet1/21 Ethernet1/22 Ethernet1/23 Ethernet1/24 Ethernet1/9 Ethernet1/10 Ethernet1/11 Ethernet1/12 Ethernet1/33 Ethernet1/34 Ethernet1/35 Ethernet1/36 ============================================================ Buffer Block 2 Total Shared Buffer Avaliable = 5799 Kbytes Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 199 Class Threshold Limit = 4845 Kbytes Mcast Usage 1 ============================================================ Buffer Block 2 Total Shared Buffer Avaliable = 5799 Kbytes Class Threshold Limit = 5598 Kbytes Mcast Usage 2 ============================================================ Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 200 921 1228 1535 1842 2149 2456 2763 3070 3377 3684 3991 4298 4605 4912 ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- 09/18/2012 07:38:42 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 201 09/18/2012 07:38:25 09/18/2012 07:38:24 09/18/2012 07:38:23 09/18/2012 07:38:22 09/18/2012 07:38:21 09/18/2012 07:38:20 09/18/2012 07:38:19 09/18/2012 07:38:18 09/18/2012 07:38:17 09/18/2012 07:38:16 09/18/2012 07:38:15 09/18/2012 07:38:14 09/18/2012 07:38:13 09/18/2012 07:38:12 09/18/2012 07:38:11 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 202 Configuring Active Buffer Monitoring Displaying Buffer Histogram Data 09/18/2012 07:38:10 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 203: C H A P T E
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 3500 Series NX-OS Software Upgrade and Downgrade Guide.
Page 204: Package Management
Guidelines and Limitations for SMUs SMUs have the following guidelines and limitations: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 205: Performing A Software Maintenance Upgrade For Cisco Nx-Os
• 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 Nexus 3500 software release, the new image will overwrite both the previous Cisco Nexus 3500 release and the SMU package file.
Page 206: Copying The Package File To A Local Storage Device Or Network Server
• Trivial File Transfer Protocol—TFTP allows files to be transferred from one computer to another over a network, usually without the use of client authentication (for example, username and password). It is a simplified version of FTP. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 207: Adding And Activating Packages
Step 3 Required: install activate filename [test] Activates a package that was added to the device. SMU packages remain inactive until Example: Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 208: Committing The Active Package Set
When a package is deactivated, it is no longer active on the device, but the package files remain on the boot disk. The package files can be reactivated later, or they can be removed from the disk. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 209: Displaying Installation Log Information
The installation log provides information on the history of the installation operations. Each time an installation operation is run, a number is assigned to that operation. • Use the show install log command to display information about both successful and failed installation operations. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 210 Install operation 5 completed successfully at Thu Jan 9 01:20:46 2014 ---------------------------------------- Install operation 6 by user 'admin' at Thu Jan 9 01:20:55 2018 Install remove n3500-uk9.6.0.2.U6.0.1.CSCab00001.bin Install operation 6 completed successfully at Thu Jan 9 01:20:57 2018 Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 211: Configuring Rollback
You can create a checkpoint copy of the current running configuration at any time. Cisco NX-OS saves this checkpoint as an ASCII file which you can use to roll back the running configuration to the checkpoint configuration at a future time.
Page 212: Creating A Checkpoint
• Checkpoint names must be unique. You cannot overwrite previously saved checkpoints with the same name. • The Cisco NX-OS commands may differ from the Cisco IOS commands. Creating a Checkpoint You can create up to ten checkpoints of your configuration per switch.
Page 213: Implementing A Rollback
Displays the contents of the checkpoint name. show checkpoint all [user | system] Displays the contents of all checkpoints in the current switch. You can limit the displayed checkpoints to user or system-generated checkpoints. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 214 | startup-config | file dest-file} show rollback log [exec | verify] Displays the contents of the rollback log. Note Use the clear checkpoint database command to delete all checkpoint files. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 215: Configuring User Accounts And Rbac
Configuring User Accounts Default Settings for the User Accounts and RBAC, on page 209 Information About User Accounts and RBAC Cisco Nexus Series switches use role-based access control (RBAC) to define the amount of access that each user has when the user logs into the switch.
Page 216: Rules
A command or group of commands defined in a regular expression. Feature Commands that apply to a function provided by the Cisco Nexus device. Enter the show role feature command to display the feature names available for this parameter. Feature group Default or user-defined group of features.
Page 217: User Account Configuration Restrictions
($) or the percent sign (%), are not allowed. Note Beginning with Cisco NX-OS Release 7.2(0)N1(1), special characters, such as the dollar sign ($) or the percent sign (%), can be used in Cisco Nexus device passwords.
Page 218: Guidelines And Limitations For User Accounts
Guidelines and Limitations for User Accounts If a password is trivial (such as a short, easy-to-decipher password), the Cisco Nexus device rejects the password. Be sure to configure a strong password for each user account. A strong password has the following characteristics: •...
Page 219: Configuring User Accounts
Copies the running configuration to the startup startup-config configuration. Example The following example shows how to configure a user account: switch# configure terminal switch(config)# username NewUser password 4Ty18Rnt switch(config)# exit switch# show user-account Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 220: Configuring Rbac
Repeat this command for as many rules as needed. Step 7 (Optional) switch(config-role)# description Configures the role description. You can text include spaces in the description. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 221: Creating Feature Groups
Example This example shows how to create a feature group: switch# configure terminal switch(config) # role feature-group group1 switch(config) # exit switch# show role feature-group Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 222: Changing User Role Interface Policies
3/1 switch(config-role-interface)# permit interface vfc 30/1 Changing User Role VLAN Policies You can change a user role VLAN policy to limit the VLANs that the user can access. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 223: Verifying The User Accounts And Rbac Configuration
Displays user account information. show user-account Configuring User Accounts Default Settings for the User Accounts and RBAC The following table lists the default settings for user accounts and RBAC parameters. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 224 User account expiry None. date Interface policy All interfaces are accessible. VLAN policy All VLANs are accessible. VFC policy All VFCs are accessible. VETH policy All VETHs are accessible. Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x...
Page 225 164, 165 configuration example disabling 48, 87 164, 165 ERSPAN DOM logging destination scheduler source Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-1...
Page 226 ERSPAN serial IDs Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-2...
Page 227 SNMP 34, 165 related documents 21, 22, 23, 24, 27, 33, 34 ERSPAN access restriction, configuring clock manager configuration examples Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-3...
Page 228 IDs group-based access description guidelines and limitations server IDs inband access description licensing message encryption Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-4...
Page 229 35, 36 registering and activating guidelines and limitations information about licensing system message logging settings 177, 178 warp mode defaults disabling system policies, overriding enabling guidelines and limitations Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-5...
Page 230 INDEX warp mode (continued) warp SPAN overview guidelines and limitations verifying the status of Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x IN-6...

Cisco Nexus 3548 series Configuration Manual

Preface

Audience

C H a P T E

CHAPTER 1 Overview

CHAPTER 3 Configuring PTP

CHAPTER 4 Configuring NTP

CHAPTER 5 Configuring System Message Logging

CHAPTER 6 Configuring Smart Call Home

CHAPTER 7 Configuring Session Manager

CHAPTER 8 Configuring the Scheduler

CHAPTER 9 Configuring SNMP

C H a P T E

Configuring RMON

Configuring Online Diagnostics

C H a P T E

Configuring Embedded Event Manager

CHAPTER 13 Configuring SPAN

C H a P T E

Configuring ERSPAN

C H a P T E

Configuring Warp SPAN

CHAPTER 16 Configuring DNS

CHAPTER 17 Configuring Traffic Forwarding Modes

CHAPTER 18 Configuring Active Buffer Monitoring

C H a P T E

Performing Software Maintenance Upgrades (Smus)

CHAPTER 20 Configuring Rollback

Configuring User Accounts and RBAC

Quick Links

Related Manuals for Cisco Nexus 3548 series

Summary of Contents for Cisco Nexus 3548 series