trademarks may be trademarks of their respective owners.
2018 - 07
Rev. A00
Contents
1 About this Guide...........................................................................................................................................36
Related Documents......................................................................................................................................................... 36
Accessing the Command Line........................................................................................................................................ 37
The do Command............................................................................................................................................................ 42
Entering and Editing Commands....................................................................................................................................43
Filtering show Command Outputs.................................................................................................................................44
Example of the grep Keyword..................................................................................................................................44
Multiple Users in Conguration Mode...........................................................................................................................45
Serial Console............................................................................................................................................................. 47
Conguring a Host Name............................................................................................................................................... 48
Accessing the System Remotely....................................................................................................................................48
Accessing the System Remotely..............................................................................................................................49
Congure the Management Port IP Address.........................................................................................................49
Congure a Management Route..............................................................................................................................49
Conguring a Username and Password..................................................................................................................49
Conguring the Enable Password..................................................................................................................................50
Copy Files to and from the System..........................................................................................................................51
Mounting an NFS File System..................................................................................................................................52
Save the Running-Conguration..............................................................................................................................53
Congure the Overload Bit for a Startup Scenario............................................................................................... 54
Managing the File System.............................................................................................................................................. 55
Using HTTP for File Transfers........................................................................................................................................56
Verify Software Images Before Installation...................................................................................................................57
Creating a Custom Privilege Level...........................................................................................................................59
Removing a Command from EXEC Mode..............................................................................................................59
Moving a Command from EXEC Privilege Mode to EXEC Mode........................................................................59
Allowing Access to CONFIGURATION Mode Commands....................................................................................59
Allowing Access to Dierent Modes........................................................................................................................59
Applying a Privilege Level to a Username................................................................................................................61
Applying a Privilege Level to a Terminal Line...........................................................................................................61
Audit and Security Logs............................................................................................................................................62
Conguring Logging Format ...................................................................................................................................63
Setting Up a Secure Connection to a Syslog Server.............................................................................................63
Log Messages in the Internal Buer..............................................................................................................................65
Conguration Task List for System Log Management..........................................................................................65
Disabling System Logging...............................................................................................................................................65
Sending System Messages to a Syslog Server............................................................................................................65
Conguring a UNIX System as a Syslog Server.....................................................................................................65
Changing System Logging Settings...............................................................................................................................70
Display the Logging Buer and the Logging Conguration.........................................................................................71
Conguring a UNIX Logging Facility Level.....................................................................................................................71
Enabling Timestamp on Syslog Messages.................................................................................................................... 73
File Transfer Services.......................................................................................................................................................73
Conguration Task List for File Transfer Services.................................................................................................. 74
Enabling the FTP Server........................................................................................................................................... 74
Conguring FTP Server Parameters........................................................................................................................74
Denying and Permitting Access to a Terminal Line................................................................................................ 75
Conguring Login Authentication for Terminal Lines.............................................................................................76
Setting Timeout for EXEC Privilege Mode....................................................................................................................77
Using Telnet to get to Another Network Device..........................................................................................................78
Viewing the Conguration Lock Status...................................................................................................................78
Restoring the Factory Default Settings.........................................................................................................................79
Important Points to Remember................................................................................................................................79
Viewing the Reason for Last System Reboot............................................................................................................... 81
EAP over RADIUS......................................................................................................................................................84
Related Conguration Tasks..................................................................................................................................... 85
Important Points to Remember......................................................................................................................................85
Conguring a Quiet Period after a Failed Authentication..................................................................................... 88
Forcibly Authorizing or Unauthorizing a Port............................................................................................................... 89
Re-Authenticating a Port................................................................................................................................................89
Conguring Dynamic VLAN Assignment with Port Authentication........................................................................... 91
Guest and Authentication-Fail VLANs.......................................................................................................................... 92
Conguring a Guest VLAN....................................................................................................................................... 93
Conguring an Authentication-Fail VLAN...............................................................................................................93
6 Access Control Lists (ACLs)........................................................................................................................ 95
IP Access Control Lists (ACLs)...................................................................................................................................... 96
Implementing ACLs on Dell EMC Networking OS..................................................................................................97
Important Points to Remember......................................................................................................................................99
Conguration Task List for Route Maps..................................................................................................................99
Conguring Match Routes.......................................................................................................................................101
Conguring Set Conditions..................................................................................................................................... 103
Congure a Route Map for Route Redistribution.................................................................................................104
Congure a Route Map for Route Tagging........................................................................................................... 104
IP Fragment Handling.................................................................................................................................................... 105
IP Fragments ACL Examples...................................................................................................................................105
Congure a Standard IP ACL........................................................................................................................................106
Conguring a Standard IP ACL Filter..................................................................................................................... 107
Congure an Extended IP ACL..................................................................................................................................... 108
Conguring Filters with a Sequence Number.......................................................................................................108
Conguring Filters Without a Sequence Number................................................................................................. 110
Congure Layer 2 and Layer 3 ACLs............................................................................................................................. 111
Assign an IP ACL to an Interface................................................................................................................................... 111
Applying an IP ACL.......................................................................................................................................................... 111
IP Prex Lists...................................................................................................................................................................114
Conguration Task List for Prex Lists...................................................................................................................115
Conguring a Remark...............................................................................................................................................119
Deleting a Remark.....................................................................................................................................................119
Resequencing an ACL or Prex List.......................................................................................................................120
Behavior of Flow-Based Monitoring.......................................................................................................................122
How BFD Works..............................................................................................................................................................127
Session State Changes............................................................................................................................................132
Important Points to Remember.................................................................................................................................... 132
Congure BFD for Physical Ports...........................................................................................................................133
Congure BFD for Static Routes............................................................................................................................134
Congure BFD for IPv6 Static Routes...................................................................................................................138
Congure BFD for OSPF.........................................................................................................................................140
Congure BFD for OSPFv3.....................................................................................................................................146
Congure BFD for IS-IS...........................................................................................................................................149
Congure BFD for BGP............................................................................................................................................151
Congure BFD for VRRP.........................................................................................................................................159
Border Gateway Protocol version 4 (BGPv4).............................................................................................................162
Autonomous Systems (AS)........................................................................................................................................... 162
AS4 Number Representation.................................................................................................................................. 164
Four-Byte AS Numbers........................................................................................................................................... 166
MBGP for IPv4 MulticastBGP Address Family modelIPv4 and IPv6 address family........................................167
Sessions and Peers.........................................................................................................................................................167
Establish a Session................................................................................................................................................... 167
Implementing BGP global and address family.............................................................................................................168
BGP global conguration default values................................................................................................................169
Contents
6
BGP Attributes for selecting Best Path.......................................................................................................................169
Best Path Selection Criteria....................................................................................................................................170
Local Preference.......................................................................................................................................................172
AS Path...................................................................................................................................................................... 174
Next Hop....................................................................................................................................................................174
Implement BGP with Dell EMC Networking OS.........................................................................................................175
Advertise IGP Cost as MED for Redistributed Routes........................................................................................ 175
Ignore Router-ID in Best-Path Calculation............................................................................................................ 176
AS Number Migration...............................................................................................................................................176
BGP4 Management Information Base (MIB)........................................................................................................ 177
Important Points to Remember...............................................................................................................................177
Conguring a BGP peer............................................................................................................................................181
Conguring AS4 Number Representations........................................................................................................... 182
Conguring a BGP VRF address family.................................................................................................................183
Route-refresh and Soft-reconguration................................................................................................................185
Conguring BGP Fast Fall-Over.............................................................................................................................199
Filtering on an AS-Path Attribute.......................................................................................................................... 204
Regular Expressions as Filters................................................................................................................................205
Conguring IP Community Lists.............................................................................................................................207
Conguring an IP Extended Community List.......................................................................................................208
Filtering Routes with Community Lists................................................................................................................. 209
Manipulating the COMMUNITY Attribute.............................................................................................................210
Changing MED Attributes........................................................................................................................................211
Changing the LOCAL_PREFERENCE Attribute...................................................................................................212
Conguring the local System or a Dierent System to be the Next Hop for BGP-Learned Routes............. 212
Changing the WEIGHT Attribute............................................................................................................................213
Setting the extended timer.....................................................................................................................................218
Enabling or disabling BGP neighbors..................................................................................................................... 219
MBGP support for IPv6.................................................................................................................................................221
Conguring IPv6 MBGP between peers..................................................................................................................... 221
Example-Conguring IPv4 and IPv6 neighbors......................................................................................................... 222
Congure IPv6 NH Automatically for IPv6 Prex Advertised over IPv4 Neighbor............................................... 224
Storing Last and Bad PDUs....................................................................................................................................227
Test CAM Usage............................................................................................................................................................ 232
QoS CAM Region Limitation...................................................................................................................................237
Syslog Error When the Table is Full........................................................................................................................237
Syslog Warning Upon 90 Percent Utilization of CAM......................................................................................... 237
Syslog Warning for Discrepancies Between Congured Extended Prexes.................................................... 237
10 Control Plane Policing (CoPP)................................................................................................................. 239
Congure Control Plane Policing................................................................................................................................. 240
Conguring CoPP for Protocols............................................................................................................................. 241
Conguring CoPP for CPU Queues...................................................................................................................... 243
Data Center Bridging Exchange Protocol (DCBx)...............................................................................................249
Contents
8
Data Center Bridging in a Trac Flow.................................................................................................................. 250
Enabling Data Center Bridging.....................................................................................................................................250
DCB Maps and its Attributes.................................................................................................................................. 251
Data Center Bridging: Default Conguration..............................................................................................................252
Conguring PFC in a DCB Map................................................................................................................................... 254
PFC Prerequisites and Restrictions.......................................................................................................................255
Applying a DCB Map on a Port....................................................................................................................................256
Conguring PFC without a DCB Map.........................................................................................................................256
Priority-Based Flow Control Using Dynamic Buer Method....................................................................................258
Pause and Resume of Trac..................................................................................................................................258
Buer Sizes for Lossless or PFC Packets............................................................................................................ 258
Behavior of Tagged Packets.........................................................................................................................................259
Conguration Example for DSCP and PFC Priorities................................................................................................259
SNMP Support for PFC and Buer Statistics Tracking........................................................................................... 260
Performing PFC Using DSCP Bits Instead of 802.1p Bits.........................................................................................260
PFC and ETS Conguration Examples........................................................................................................................ 261
Using PFC to Manage Converged Ethernet Trac................................................................................................... 261
Operations on Untagged Packets.................................................................................................................................261
Generation of PFC for a Priority for Untagged Packets...........................................................................................262
ETS Prerequisites and Restrictions....................................................................................................................... 262
Creating an ETS Priority Group..............................................................................................................................262
ETS Operation with DCBx......................................................................................................................................264
Conguring Bandwidth Allocation for DCBx CIN.................................................................................................264
Conguring ETS in a DCB Map..............................................................................................................................265
Hierarchical Scheduling in ETS Output Policies......................................................................................................... 266
Using ETS to Manage Converged Ethernet Trac................................................................................................... 267
Applying DCB Policies in a Switch Stack.................................................................................................................... 267
Congure a DCBx Operation........................................................................................................................................ 267
DCBx Port Roles......................................................................................................................................................268
Propagation of DCB Information............................................................................................................................270
Auto-Detection and Manual Conguration of the DCBx Version.......................................................................270
DCBx Prerequisites and Restrictions......................................................................................................................271
Verifying the DCB Conguration..................................................................................................................................275
QoS dot1p Trac Classication and Queue Assignment..........................................................................................283
Conguring the Dynamic Buer Method....................................................................................................................284
DHCP Packet Format and Options............................................................................................................................. 288
Assign an IP Address using DHCP...............................................................................................................................290
Congure the System to be a DHCP Server.............................................................................................................. 291
Conguring the Server for Automatic Address Allocation..................................................................................292
Specifying a Default Gateway................................................................................................................................293
Congure a Method of Hostname Resolution..................................................................................................... 293
Using DNS for Address Resolution........................................................................................................................293
Using NetBIOS WINS for Address Resolution..................................................................................................... 294
Debugging the DHCP Server.................................................................................................................................294
Using DHCP Clear Commands.............................................................................................................................. 295
Congure the System to be a DHCP Client...............................................................................................................295
Conguring the DHCP Client System...................................................................................................................295
DHCP Client on a Management Interface............................................................................................................ 297
DHCP Client Operation with Other Features....................................................................................................... 297
DHCP Relay When DHCP Server and Client are in Dierent VRFs........................................................................ 298
Conguring Route Leaking between VRFs on DHCP Relay Agent................................................................... 298
Congure the System for User Port Stacking (Option 230)................................................................................... 300
Enabling IP Source Address Validation..................................................................................................................308
DHCP MAC Source Address Validation................................................................................................................ 309
ECMP for Flow-Based Anity.......................................................................................................................................311
Conguring the Hash Algorithm..............................................................................................................................311
Enabling Deterministic ECMP Next Hop................................................................................................................311
Conguring the Hash Algorithm Seed................................................................................................................... 312
Link Bundle Monitoring.................................................................................................................................................. 312
Managing ECMP Group Paths................................................................................................................................313
Creating an ECMP Group Bundle...........................................................................................................................313
Modifying the ECMP Group Threshold................................................................................................................. 313
Support for /128 IPv6 and /32 IPv4 Prexes in Layer 3 Host Table and LPM Table.......................................314
10
Contents
Support for ECMP in host table.............................................................................................................................315
Support for moving /128 IPv6 Prexes and /32 IPv4 Prexes .........................................................................315
Fibre Channel over Ethernet.........................................................................................................................................316
Ensure Robustness in a Converged Ethernet Network.............................................................................................316
FIP Snooping on Ethernet Bridges...............................................................................................................................318
FIP Snooping in a Switch Stack...................................................................................................................................320
Using FIP Snooping....................................................................................................................................................... 320
Important Points to Remember............................................................................................................................. 320
Enabling the FCoE Transit Feature.........................................................................................................................321
Enable FIP Snooping on VLANs.............................................................................................................................322
Congure the FC-MAP Value................................................................................................................................ 322
Congure a Port for a Bridge-to-Bridge Link....................................................................................................... 322
Congure a Port for a Bridge-to-FCF Link...........................................................................................................322
Impact on Other Software Features..................................................................................................................... 322
Conguring the Flex Hash Mechanism........................................................................................................................331
Conguring Fast Boot and LACP Fast Switchover...................................................................................................332
Optimizing the Boot Time.............................................................................................................................................332
Booting Process When Optimized Boot Time Mechanism is Enabled..............................................................332
Guidelines for Conguring Optimized Booting Mechanism................................................................................333
Interoperation of Applications with Fast Boot and System States..........................................................................334
LACP and IPv4 Routing.......................................................................................................................................... 334
LACP and IPv6 Routing.......................................................................................................................................... 334
Cold Boot Caused by Power Cycling the System................................................................................................335
Unexpected Reload of the System........................................................................................................................335
LACP Fast Switchover............................................................................................................................................335
Changes to BGP Multipath.................................................................................................................................... 336
Delayed Installation of ECMP Routes Into BGP...................................................................................................336
RDMA Over Converged Ethernet (RoCE) Overview............................................................................................... 336
Preserving 802.1Q VLAN Tag Value for Lite Subinterfaces...................................................................................... 337
16 Force10 Resilient Ring Protocol (FRRP)................................................................................................... 338
Ring Status...............................................................................................................................................................339
Important FRRP Points...........................................................................................................................................340
Important FRRP Concepts......................................................................................................................................341
Creating the FRRP Group.......................................................................................................................................342
Conguring the Control VLAN...............................................................................................................................343
Conguring and Adding the Member VLANs.......................................................................................................344
Setting the FRRP Timers........................................................................................................................................345
Clearing the FRRP Counters..................................................................................................................................345
Viewing the FRRP Conguration...........................................................................................................................345
Viewing the FRRP Information.............................................................................................................................. 345
Sample Conguration and Topology............................................................................................................................ 346
FRRP Support on VLT...................................................................................................................................................347
Example Scenario.................................................................................................................................................... 348
Important Points to Remember............................................................................................................................. 349
Important Points to Remember................................................................................................................................... 350
Related Conguration Tasks....................................................................................................................................351
Enabling GVRP on a Layer 2 Interface........................................................................................................................352
Congure a GARP Timer.............................................................................................................................................. 353
18 Internet Group Management Protocol (IGMP)......................................................................................... 354
IGMP Version 2........................................................................................................................................................354
IGMP Version 3........................................................................................................................................................356
Related Conguration Tasks...................................................................................................................................359
Selecting an IGMP Version...........................................................................................................................................360
Adjusting Query and Response Timers..................................................................................................................361
Removing a Group-Port Association.....................................................................................................................364
Specifying a Port as Connected to a Multicast Router...................................................................................... 364
12
Contents
Conguring the Switch as Querier........................................................................................................................365
Fast Convergence after MSTP Topology Changes................................................................................................... 365
Egress Interface Selection (EIS) for HTTP and IGMP Applications........................................................................365
Enabling and Disabling Management Egress Interface Selection...................................................................... 367
Handling of Management Route Conguration................................................................................................... 368
Handling of Switch-Initiated Trac....................................................................................................................... 368
Handling of Switch-Destined Trac......................................................................................................................369
Handling of Transit Trac (Trac Separation).....................................................................................................370
Mapping of Management Applications and Trac Type.....................................................................................370
Behavior of Various Applications for Switch-Initiated Trac ............................................................................. 371
Behavior of Various Applications for Switch-Destined Trac ...........................................................................372
Interworking of EIS With Various Applications..................................................................................................... 372
Designating a Multicast Router Interface................................................................................................................... 373
Resetting an Interface to its Factory Default State................................................................................................... 377
Enabling a Physical Interface........................................................................................................................................378
Conguration Task List for Physical Interfaces.................................................................................................... 378
40G to 1G Breakout Cable Adaptor....................................................................................................................... 378
Overview of Layer Modes.......................................................................................................................................379
Automatic recovery of an Err-disabled interface.......................................................................................................382
Conguring an automatic recovery for an Err-disabled interface......................................................................382
Important Points to Remember............................................................................................................................. 383
Port Channel Interfaces................................................................................................................................................ 387
Port Channel Denition and Standards.................................................................................................................388
Port Channel Benets.............................................................................................................................................388
Port Channel Implementation.................................................................................................................................388
Interfaces in Port Channels.................................................................................................................................... 389
Contents
13
Conguration Tasks for Port Channel Interfaces.................................................................................................389
Creating a Port Channel......................................................................................................................................... 389
Adding a Physical Interface to a Port Channel.....................................................................................................390
Reassigning an Interface to a New Port Channel.................................................................................................391
Conguring the Minimum Oper Up Links in a Port Channel.............................................................................. 392
Adding or Removing a Port Channel from a VLAN............................................................................................. 392
Assigning an IP Address to a Port Channel.......................................................................................................... 394
Deleting or Disabling a Port Channel.....................................................................................................................394
Load Balancing Through Port Channels................................................................................................................394
Changing the Hash Algorithm................................................................................................................................394
Dening Interface Range Macros................................................................................................................................ 398
Dene the Interface Range.................................................................................................................................... 398
Choosing an Interface-Range Macro.................................................................................................................... 398
Monitoring and Maintaining Interfaces....................................................................................................................... 398
Maintenance Using TDR.........................................................................................................................................399
Non Dell-Qualied Transceivers...................................................................................................................................400
Splitting 40G Ports without Reload............................................................................................................................ 400
Splitting QSFP Ports to SFP+ Ports........................................................................................................................... 402
Converting a QSFP or QSFP+ Port to an SFP or SFP+ Port..................................................................................403
Important Points to Remember............................................................................................................................. 403
Example Scenarios.................................................................................................................................................. 404
Link Dampening............................................................................................................................................................. 405
Important Points to Remember............................................................................................................................. 405
Conguration Example of Link Dampening.......................................................................................................... 406
Enabling Link Dampening........................................................................................................................................408
Link Bundle Monitoring................................................................................................................................................. 409
Using Ethernet Pause Frames for Flow Control.........................................................................................................410
Congure the MTU Size on an Interface..................................................................................................................... 411
Auto-Negotiation on Ethernet Interfaces....................................................................................................................412
Setting the Speed of Ethernet Interfaces.............................................................................................................412
Set Auto-Negotiation Options................................................................................................................................ 414
IP Addresses...................................................................................................................................................................425
Conguration Tasks for IP Addresses..........................................................................................................................425
Assigning IP Addresses to an Interface.......................................................................................................................425
Resolution of Host Names............................................................................................................................................429
Enabling Dynamic Resolution of Host Names............................................................................................................430
Specifying the Local System Domain and a List of Domains................................................................................... 430
Conguring DNS with Traceroute................................................................................................................................ 431
Conguration Tasks for ARP........................................................................................................................................ 432
ARP Learning via Gratuitous ARP................................................................................................................................433
Enabling ARP Learning via Gratuitous ARP................................................................................................................ 433
ARP Learning via ARP Request................................................................................................................................... 433
Conguration Tasks for ICMP...................................................................................................................................... 435
Important Points to Remember............................................................................................................................. 436
Congurations Using UDP Helper............................................................................................................................... 436
UDP Helper with Broadcast-All Addresses.................................................................................................................436
UDP Helper with Subnet Broadcast Addresses......................................................................................................... 437
UDP Helper with Congured Broadcast Addresses.................................................................................................. 437
UDP Helper with No Congured Broadcast Addresses............................................................................................438
Path MTU discovery......................................................................................................................................................448
Secure Shell (SSH) Over an IPv6 Transport............................................................................................................... 451
Conguration Tasks for IPv6......................................................................................................................................... 451
Adjusting Your CAM-Prole.....................................................................................................................................451
Assigning an IPv6 Address to an Interface...........................................................................................................452
Assigning a Static IPv6 Route................................................................................................................................453
Conguring Telnet with IPv6..................................................................................................................................453
SNMP over IPv6......................................................................................................................................................454
Conguring IPv6 RA Guard.......................................................................................................................................... 457
Conguring IPv6 RA Guard on an Interface.........................................................................................................459
Monitoring IPv6 RA Guard..................................................................................................................................... 460
Application of Quality of Service to iSCSI Trac Flows..................................................................................... 463
Information Monitored in iSCSI Trac Flows.......................................................................................................463
Detection and Auto-Conguration for Dell EqualLogic Arrays........................................................................... 464
Conguring Detection and Ports for Dell Compellent Arrays............................................................................. 464
Synchronizing iSCSI Sessions Learned on VLT-Lags with VLT-Peer.................................................................465
Enable and Disable iSCSI Optimization.................................................................................................................465
Conguration Tasks for IS-IS.................................................................................................................................. 474
Conguring the Distance of a Route......................................................................................................................481
Changing the IS-Type.............................................................................................................................................. 482
Setting the Overload Bit.........................................................................................................................................486
Maximum Values in the Routing Table.................................................................................................................. 488
Change the IS-IS Metric Style in One Level Only................................................................................................488
Leaks from One Level to Another..........................................................................................................................490
24 Link Aggregation Control Protocol (LACP).............................................................................................. 493
Introduction to Dynamic LAGs and LACP.................................................................................................................. 493
Important Points to Remember............................................................................................................................. 493
Creating a LAG.........................................................................................................................................................495
Conguring the LAG Interfaces as Dynamic........................................................................................................495
Setting the LACP Long Timeout........................................................................................................................... 496
Monitoring and Debugging LACP..........................................................................................................................496
Shared LAG State Tracking...........................................................................................................................................497
Conguring Shared LAG State Tracking............................................................................................................... 497
Important Points about Shared LAG State Tracking...........................................................................................499
Congure a LAG on ALPHA...................................................................................................................................499
Manage the MAC Address Table................................................................................................................................. 508
Clearing the MAC Address Table........................................................................................................................... 508
Setting the Aging Time for Dynamic Entries........................................................................................................508
Conguring a Static MAC Address........................................................................................................................509
Displaying the MAC Address Table........................................................................................................................509
MAC Learning Limit.......................................................................................................................................................509
Setting the MAC Learning Limit............................................................................................................................. 510
mac learning-limit Dynamic..................................................................................................................................... 510
Contents
17
mac learning-limit mac-address-sticky..................................................................................................................510
mac learning-limit station-move..............................................................................................................................511
mac learning-limit no-station-move........................................................................................................................511
Setting Station Move Violation Actions.................................................................................................................512
Recovering from Learning Limit and Station Move Violations............................................................................512
NIC Teaming....................................................................................................................................................................513
FEFD State Changes................................................................................................................................................518
Enabling FEFD on an Interface............................................................................................................................... 519
Protocol Data Units................................................................................................................................................. 522
TIA Organizationally Specic TLVs........................................................................................................................ 525
Related Conguration Tasks...................................................................................................................................529
Important Points to Remember............................................................................................................................. 529
Disabling and Undoing LLDP...................................................................................................................................531
Enabling LLDP on Management Ports.........................................................................................................................531
Disabling and Undoing LLDP on Management Ports...........................................................................................531
Viewing the LLDP Conguration................................................................................................................................. 534
Viewing Information Advertised by Adjacent LLDP Neighbors................................................................................534
Examples of Viewing Information Advertised by Neighbors...............................................................................534
Conguring Transmit and Receive Mode....................................................................................................................537
Conguring the Time to Live Value............................................................................................................................. 538
Limitations of the NLB Feature....................................................................................................................................546
Microsoft Clustering......................................................................................................................................................546
Enable and Disable VLAN Flooding ............................................................................................................................ 546
Conguring a Switch for NLB .....................................................................................................................................546
Enabling a Switch for Multicast NLB.................................................................................................................... 547
Related Conguration Tasks...................................................................................................................................550
Manage the Source-Active Cache..............................................................................................................................555
Viewing the Source-Active Cache........................................................................................................................ 555
Limiting the Source-Active Cache........................................................................................................................ 555
Clearing the Source-Active Cache........................................................................................................................556
Enabling the Rejected Source-Active Cache.......................................................................................................556
Accept Source-Active Messages that Fail the RFP Check..................................................................................... 556
Limiting the Source-Active Messages from a Peer...................................................................................................560
Preventing MSDP from Caching a Local Source.......................................................................................................560
Preventing MSDP from Caching a Remote Source...................................................................................................561
Preventing MSDP from Advertising a Local Source.................................................................................................. 561
Logging Changes in Peership States...........................................................................................................................562
Terminating a Peership..................................................................................................................................................562
MSDP with Anycast RP................................................................................................................................................564
MLD Version 1.................................................................................................................................................................571
Joining a Multicast Group.............................................................................................................................................572
Leaving a Multicast Group............................................................................................................................................ 572
MLD version 2................................................................................................................................................................ 572
Displaying MLD groups table........................................................................................................................................576
Spanning Tree Variations...............................................................................................................................................578
Congure Multiple Spanning Tree Protocol................................................................................................................ 578
Related Conguration Tasks................................................................................................................................... 579
Enable Multiple Spanning Tree Globally.......................................................................................................................579
Adding and Removing Interfaces................................................................................................................................. 579
Creating Multiple Spanning Tree Instances................................................................................................................580
Interoperate with Non-Dell Bridges............................................................................................................................. 582
Changing the Region Name or Revision.....................................................................................................................582
Modifying Global Parameters....................................................................................................................................... 582
Modifying the Interface Parameters........................................................................................................................... 584
Conguring an EdgePort..............................................................................................................................................585
Flush MAC Addresses after a Topology Change....................................................................................................... 585
Enabling IP Multicast.....................................................................................................................................................592
Important Points to Remember.............................................................................................................................. 601
MLD Version 1................................................................................................................................................................609
Joining a Multicast Group..............................................................................................................................................610
Leaving a Multicast Group............................................................................................................................................ 610
MLD version 2.................................................................................................................................................................610
Displaying MLD groups table.........................................................................................................................................614
Congure the switch as a querier.......................................................................................................................... 615
Specify port as connected to multicast router..................................................................................................... 615
Display the MLD Snooping Table............................................................................................................................616
Track IPv4 and IPv6 Routes....................................................................................................................................619
Set Tracking Delays................................................................................................................................................. 620
Tracking a Layer 2 Interface................................................................................................................................... 620
Tracking a Layer 3 Interface....................................................................................................................................621
Track an IPv4/IPv6 Route...................................................................................................................................... 623
Autonomous System (AS) Areas........................................................................................................................... 628
Area Types................................................................................................................................................................ 629
Networks and Neighbors........................................................................................................................................630
Router Priority and Cost.........................................................................................................................................633
OSPF with Dell EMC Networking OS.........................................................................................................................634
Fast Convergence (OSPFv2, IPv4 Only)..............................................................................................................636
Multi-Process OSPFv2 with VRF..........................................................................................................................636
Applying cost for OSPFv3......................................................................................................................................654
Assigning IPv6 Addresses on an Interface........................................................................................................... 654
Assigning Area ID on an Interface..........................................................................................................................654
Assigning OSPFv3 Process ID and Router ID Globally........................................................................................655
Assigning OSPFv3 Process ID and Router ID to a VRF......................................................................................655
Conguring a Default Route................................................................................................................................... 657
OSPFv3 Authentication Using IPsec.....................................................................................................................659
Conguration Task List for Policy-based Routing......................................................................................................668
Create a Redirect List............................................................................................................................................. 669
Create a Rule for a Redirect-list.............................................................................................................................669
Apply a Redirect-list to an Interface using a Redirect-group.............................................................................. 671
Related Conguration Tasks...................................................................................................................................680
Conguring a Designated Router.................................................................................................................................683
Creating Multicast Boundaries and Domains............................................................................................................. 685
Important Points to Remember............................................................................................................................. 686
Related Conguration Tasks................................................................................................................................... 687
Use PIM-SSM with IGMP Version 2 Hosts................................................................................................................ 687
Conguring PIM-SSM with IGMPv2.....................................................................................................................688
Electing an RP using the BSR Mechanism.................................................................................................................689
Enabling RP to Server Specic Multicast Groups...............................................................................................689
38 Port Monitoring........................................................................................................................................691
Important Points to Remember.................................................................................................................................... 691
Port Monitoring..............................................................................................................................................................692
Conguring Port Monitoring........................................................................................................................................ 693
Remote Port Mirroring.................................................................................................................................................. 696
Remote Port Mirroring Example............................................................................................................................ 696
Conguring Remote Port Mirroring.......................................................................................................................697
Conguring the Sample Remote Port Mirroring..................................................................................................699
Encapsulated Remote Port Monitoring.......................................................................................................................702
ERPM Behavior on a typical Dell EMC Networking OS ...........................................................................................704
Decapsulation of ERPM packets at the Destination IP/ Analyzer..................................................................... 704
Port Monitoring on VLT.................................................................................................................................................705
VLT Non-fail over Scenario.....................................................................................................................................705
RPM over VLT Scenarios........................................................................................................................................706
39 Per-VLAN Spanning Tree Plus (PVST+)................................................................................................... 708
Congure Per-VLAN Spanning Tree Plus....................................................................................................................709
Related Conguration Tasks................................................................................................................................... 709
Modifying Global PVST+ Parameters...........................................................................................................................712
Conguring an EdgePort............................................................................................................................................... 714
PVST+ in Multi-Vendor Networks................................................................................................................................ 714
Enabling PVST+ Extend System ID.............................................................................................................................. 714
40 Quality of Service (QoS).......................................................................................................................... 718
Dot1p to Queue Mapping Requirement................................................................................................................. 727
Create a QoS Policy................................................................................................................................................. 727
DSCP Color Maps....................................................................................................................................................730
Queue Classication Requirements for PFC Functionality.......................................................................................736
Support for marking dot1p value in L3 Input Qos Policy...........................................................................................736
Weighted Random Early Detection.............................................................................................................................. 737
Applying a WRED Prole to Trac........................................................................................................................ 738
Displaying Default and Congured WRED Proles.............................................................................................. 739
Displaying WRED Drop Statistics...........................................................................................................................739
Conguring Weights and ECN for WRED ..................................................................................................................742
Global Service Pools With WRED and ECN Settings..........................................................................................742
Conguring WRED and ECN Attributes......................................................................................................................743
Guidelines for Conguring ECN for Classifying and Color-Marking Packets......................................................... 744
Sample conguration to mark non-ecn packets as “yellow” with Multiple trac class.................................. 745
Classifying Incoming Packets Using ECN and Color-Marking............................................................................745
Sample conguration to mark non-ecn packets as “yellow” with single trac class...................................... 747
Applying Layer 2 Match Criteria on a Layer 3 Interface............................................................................................748
Setting the RMON Alarm........................................................................................................................................766
24
Contents
Conguring an RMON Event................................................................................................................................. 766
Related Conguration Tasks................................................................................................................................... 769
Important Points to Remember....................................................................................................................................769
RSTP and VLT.......................................................................................................................................................... 770
Conguring Interfaces for Layer 2 Mode.................................................................................................................... 770
Enabling Rapid Spanning Tree Protocol Globally.........................................................................................................771
Adding and Removing Interfaces................................................................................................................................. 773
Modifying Global Parameters........................................................................................................................................773
Enabling SNMP Traps for Root Elections and Topology Changes..................................................................... 775
Conguring an EdgePort...............................................................................................................................................776
Conguring Fast Hellos for Link State Detection.......................................................................................................777
Conguration Task List for AAA Authentication...................................................................................................782
Obscuring Passwords and Keys...................................................................................................................................785
Conguration Task List for Privilege Levels..........................................................................................................786
Conguration Task List for RADIUS....................................................................................................................... 791
Support for Change of Authorization and Disconnect Messages packets...................................................... 795
Conguration Task List for TACACS+................................................................................................................... 806
Protection from TCP Tiny and Overlapping Fragment Attacks............................................................................... 809
Enabling SCP and SSH................................................................................................................................................. 809
Using SCP with SSH to Copy a Software Image................................................................................................. 810
Removing the RSA Host Keys and Zeroizing Storage .........................................................................................811
Conguring When to Re-generate an SSH Key ...................................................................................................811
Conguring the SSH Server Key Exchange Algorithm........................................................................................812
Contents
25
Conguring the HMAC Algorithm for the SSH Server........................................................................................812
Conguring the SSH Server Cipher List................................................................................................................813
Conguring DNS in the SSH Server...................................................................................................................... 813
VTY Line and Access-Class Conguration.................................................................................................................. 817
VTY Line Local Authentication and Authorization................................................................................................ 817
VTY Line Remote Authentication and Authorization........................................................................................... 818
Overview of RBAC...................................................................................................................................................819
User Roles................................................................................................................................................................. 821
AAA Authentication and Authorization for Roles.................................................................................................824
Role Accounting....................................................................................................................................................... 827
Display Information About User Roles...................................................................................................................828
Two Factor Authentication (2FA)................................................................................................................................ 829
Conguring the root User Password.....................................................................................................................834
Locking Access to GRUB Interface.......................................................................................................................835
Enabling User Lockout for Failed Login Attempts............................................................................................... 836
46 Service Provider Bridging........................................................................................................................ 837
Important Points to Remember............................................................................................................................. 838
Creating Access and Trunk Ports.......................................................................................................................... 839
Enable VLAN-Stacking for a VLAN.......................................................................................................................840
Conguring the Protocol Type Value for the Outer VLAN Tag.......................................................................... 840
Conguring Dell EMC Networking OS Options for Trunk Ports........................................................................ 840
VLAN Stacking in Multi-Vendor Networks........................................................................................................... 842
VLAN Stacking Packet Drop Precedence.................................................................................................................. 845
Enabling Drop Eligibility........................................................................................................................................... 845
Honoring the Incoming DEI Value..........................................................................................................................846
Marking Egress Packets with a DEI Value............................................................................................................ 847
Dynamic Mode CoS for VLAN Stacking..................................................................................................................... 847
Mapping C-Tag to S-Tag dot1p Values...................................................................................................................848
Important Points to Remember............................................................................................................................. 855
Enabling and Disabling sFlow on an Interface............................................................................................................856
sFlow Show Commands............................................................................................................................................... 857
Displaying Show sFlow Global................................................................................................................................857
Displaying Show sFlow on an Interface................................................................................................................ 858
Displaying Show sFlow on a Stack-unit................................................................................................................ 858
Changing the Polling Intervals......................................................................................................................................859
sFlow on LAG ports.......................................................................................................................................................860
Important Points to Remember.............................................................................................................................. 861
SNMPv3 Compliance With FIPS................................................................................................................................. 863
Conguration Task List for SNMP...............................................................................................................................864
Related Conguration Tasks...................................................................................................................................864
Important Points to Remember................................................................................................................................... 865
Set up SNMP.................................................................................................................................................................865
Creating a Community............................................................................................................................................865
Setting Up User-Based Security (SNMPv3)....................................................................................................... 865
Conguring Contact and Location Information using SNMP...................................................................................868
Subscribing to Managed Object Value Updates using SNMP................................................................................. 868
Enabling a Subset of SNMP Traps.............................................................................................................................. 869
Enabling an SNMP Agent to Notify Syslog Server Failure........................................................................................873
Copy Conguration Files Using SNMP........................................................................................................................874
Copying a Conguration File...................................................................................................................................875
Copying Conguration Files via SNMP................................................................................................................. 876
Copying the Startup-Cong Files to the Running-Cong.................................................................................. 876
Copying the Startup-Cong Files to the Server via FTP.................................................................................... 877
Copying the Startup-Cong Files to the Server via TFTP..................................................................................877
Contents
27
Copy a Binary File to the Startup-Conguration..................................................................................................878
Additional MIB Objects to View Copy Statistics.................................................................................................. 878
Obtaining a Value for MIB Objects.........................................................................................................................879
MIB Support to Display Reason for Last System Reboot.........................................................................................879
Viewing the Reason for Last System Reboot Using SNMP...............................................................................880
MIB Support for Power Monitoring.............................................................................................................................880
MIB Support to Display the Available Memory Size on Flash................................................................................... 881
Viewing the Available Flash Memory Size............................................................................................................. 881
MIB Support to Display the Software Core Files Generated by the System.......................................................... 881
Viewing the Software Core Files Generated by the System..............................................................................882
SNMP Support for WRED Green/Yellow/Red Drop Counters................................................................................882
MIB Support to Display the Available Partitions on Flash.........................................................................................883
Viewing the Available Partitions on Flash............................................................................................................. 884
MIB Support to Display Egress Queue Statistics.......................................................................................................885
MIB Support to ECMP Group Count..........................................................................................................................885
Viewing the ECMP Group Count Information......................................................................................................885
MIB Support for entAliasMappingTable ..................................................................................................................... 888
Viewing the entAliasMappingTable MIB................................................................................................................888
MIB Support for LAG.................................................................................................................................................... 888
Viewing the LAG MIB..............................................................................................................................................890
MIB Support to Display Unrecognized LLDP TLVs................................................................................................... 890
MIB Support to Display Reserved Unrecognized LLDP TLVs............................................................................890
MIB Support to Display Organizational Specic Unrecognized LLDP TLVs......................................................891
MIB Support to Display Unrecognized LLDP TLVs....................................................................................................892
Viewing the Details of Reserved Unrecognized LLDP TLVs.............................................................................. 892
MIB Support for LLDP Notication Interval............................................................................................................... 893
Manage VLANs using SNMP....................................................................................................................................... 893
Creating a VLAN......................................................................................................................................................893
Assigning a VLAN Alias........................................................................................................................................... 893
Displaying the Ports in a VLAN..............................................................................................................................894
Add Tagged and Untagged Ports to a VLAN....................................................................................................... 894
Managing Overload on Startup....................................................................................................................................895
Enabling and Disabling a Port using SNMP................................................................................................................895
Fetch Dynamic MAC Entries using SNMP................................................................................................................. 896
Example of Deriving the Interface Index Number......................................................................................................897
MIB Objects for Viewing the System Image on Flash Partitions....................................................................... 897
Monitoring BGP sessions via SNMP........................................................................................................................... 897
MAC Addressing on Stacks....................................................................................................................................905
High Availability on Stacks......................................................................................................................................907
Management Access on Stacks.............................................................................................................................907
Important Points to Remember................................................................................................................................... 908
Create a Stack......................................................................................................................................................... 908
Add Units to an Existing Stack............................................................................................................................... 912
Split a Stack.............................................................................................................................................................. 914
Assigning Unit Numbers to Units in an Stack.......................................................................................................915
Creating a Virtual Stack Unit on a Stack...............................................................................................................915
Displaying Information about a Stack.....................................................................................................................915
Inuencing Management Unit Selection on a Stack............................................................................................ 917
Managing Redundancy on a Stack.........................................................................................................................917
Resetting a Unit on a Stack.................................................................................................................................... 918
Verify a Stack Conguration......................................................................................................................................... 918
Displaying the Status of Stacking Ports................................................................................................................ 918
Remove Units or Front End Ports from a Stack.........................................................................................................919
Removing a Unit from a Stack................................................................................................................................919
Removing Front End Port Stacking....................................................................................................................... 919
Troubleshoot a Stack.....................................................................................................................................................920
Recover from Stack Link Flaps.............................................................................................................................. 920
Recover from a Card Problem State on a Stack..................................................................................................920
Restore Queue Drop State........................................................................................................................................... 923
View Details of Storm Control PFC.............................................................................................................................923
51 Spanning Tree Protocol (STP)..................................................................................................................925
Related Conguration Tasks...................................................................................................................................926
Important Points to Remember................................................................................................................................... 926
Conguring Interfaces for Layer 2 Mode....................................................................................................................927
Enabling Spanning Tree Protocol Globally...................................................................................................................928
Adding an Interface to the Spanning Tree Group...................................................................................................... 930
Modifying Global Parameters.......................................................................................................................................930
Enabling SNMP Traps for Root Elections and Topology Changes...........................................................................936
Conguring Spanning Trees as Hitless........................................................................................................................936
53 System Time and Date.............................................................................................................................948
Network Time Protocol................................................................................................................................................. 948
Congure the Network Time Protocol..................................................................................................................949
Disabling NTP on an Interface................................................................................................................................ 951
Conguring a Source IP Address for NTP Packets..............................................................................................951
Conguring NTP control key password................................................................................................................954
Dell EMC Networking OS Time and Date...................................................................................................................954
Conguration Task List .......................................................................................................................................... 954
Setting the Time and Date for the Switch Software Clock............................................................................... 954
Setting the Timezone..............................................................................................................................................955
Set Daylight Saving Time........................................................................................................................................955
Setting Daylight Saving Time Once.......................................................................................................................955
Conguring a Tunnel..................................................................................................................................................... 958
Conguring a Tunnel Interface.....................................................................................................................................960
How Uplink Failure Detection Works...........................................................................................................................963
UFD and NIC Teaming...................................................................................................................................................964
Important Points to Remember................................................................................................................................... 964
Clearing a UFD-Disabled Interface..............................................................................................................................966
Get Help with Upgrades................................................................................................................................................ 971
VLANs and Port Tagging...............................................................................................................................................974
Creating a Port-Based VLAN..................................................................................................................................974
Assigning Interfaces to a VLAN............................................................................................................................. 975
Assigning an IP Address to a VLAN.......................................................................................................................977
Enabling Null VLAN as the Default VLAN...................................................................................................................978
58 Virtual Link Trunking (VLT)...................................................................................................................... 979
Layer-2 Trac in VLT Domains...............................................................................................................................983
VLT on Core Switches.............................................................................................................................................984
Congure Virtual Link Trunking.................................................................................................................................... 986
Important Points to Remember............................................................................................................................. 986
Primary and Secondary VLT Peers........................................................................................................................990
RSTP and VLT...........................................................................................................................................................991
VLT and Stacking......................................................................................................................................................991
VLT and IGMP Snooping......................................................................................................................................... 991
VLT Port Delayed Restoration................................................................................................................................992
PIM-Sparse Mode Support on VLT.......................................................................................................................992
Verifying a VLT Conguration..................................................................................................................................... 1023
Reconguring Stacked Switches as VLT...................................................................................................................1029
Specifying VLT Nodes in a PVLAN............................................................................................................................ 1029
Association of VLTi as a Member of a PVLAN................................................................................................... 1030
MAC Synchronization for VLT Nodes in a PVLAN.............................................................................................1030
PVLAN Operations When One VLT Peer is Down..............................................................................................1031
PVLAN Operations When a VLT Peer is Restarted............................................................................................ 1031
Interoperation of VLT Nodes in a PVLAN with ARP Requests..........................................................................1031
Scenarios for VLAN Membership and MAC Synchronization With VLT Nodes in PVLAN............................1031
Conguring a VLT VLAN or LAG in a PVLAN...........................................................................................................1033
Creating a VLT LAG or a VLT VLAN.................................................................................................................... 1033
Associating the VLT LAG or VLT VLAN in a PVLAN......................................................................................... 1034
Proxy ARP Capability on VLT Peer Nodes................................................................................................................1035
Working of Proxy ARP for VLT Peer Nodes....................................................................................................... 1035
VLT Nodes as Rendezvous Points for Multicast Resiliency....................................................................................1036
Conguring VLAN-Stack over VLT............................................................................................................................1036
IPv6 Peer Routing in VLT Domains Overview.......................................................................................................... 1040
Synchronization of IPv6 ND Entries in a VLT Domain....................................................................................... 1040
Synchronization of IPv6 ND Entries in a Non-VLT Domain............................................................................... 1041
Tunneling IPv6 ND in a VLT Domain.....................................................................................................................1041
Sample Conguration of IPv6 Peer Routing in a VLT Domain..........................................................................1042
VXLAN on VLT............................................................................................................................................................. 1045
Static VXLAN Conguration in a VLT setup....................................................................................................... 1046
Proxy Gateway in VLT Domains..................................................................................................................................1048
Guidelines for Enabling the VLT Proxy Gateway................................................................................................1049
Components of VXLAN network...............................................................................................................................1059
Components of VXLAN network.........................................................................................................................1059
Functional Overview of VXLAN Gateway.................................................................................................................1060
Components of VXLAN Frame Format................................................................................................................1061
Limitations on VXLAN ................................................................................................................................................ 1062
Conguring and Controlling VXLAN from the NSX Controller GUI.......................................................................1062
Conguring and Controling VXLAN from Nuage Controller GUI........................................................................... 1065
Connecting to an NVP Controller........................................................................................................................ 1066
Advertising VXLAN Access Ports to Controller..................................................................................................1067
VXLAN Service nodes for BFD.................................................................................................................................. 1069
Examples of the show bfd neighbors command................................................................................................1069
Static Virtual Extensible LAN (VXLAN).................................................................................................................... 1069
Preserving 802.1 p value across VXLAN tunnels.......................................................................................................1071
Routing in and out of VXLAN tunnels........................................................................................................................ 1071
Physical Loopback for VXLAN RIOTInternal Loopback for VXLAN RIOT........................................................1071
NSX Controller-based VXLAN for VLT......................................................................................................................1075
Important Points to Remember............................................................................................................................ 1076
Congure NSX Controller-based VxLAN in VLT Setup..................................................................................... 1076
Conguring BFD and UFD for VXLAN.................................................................................................................1077
Conguring NSX-based VxLAN on VLT Peer Devices.......................................................................................1077
Conguring VLT for NSX-based VxLAN..............................................................................................................1078
Conguring and Controlling VXLAN from the NSX Controller GUI.................................................................1083
61 Virtual Routing and Forwarding (VRF).................................................................................................... 1086
Creating a Non-Default VRF Instance.................................................................................................................1089
Assigning an Interface to a VRF...........................................................................................................................1090
Assigning a Front-end Port to a Management VRF.......................................................................................... 1090
Assigning an OSPF Process to a VRF Instance..................................................................................................1091
Conguring VRRP on a VRF Instance..................................................................................................................1091
Conguring a Static Route....................................................................................................................................1093
Conguring Route Leaking without Filtering Criteria.........................................................................................1099
Conguring Route Leaking with Filtering.............................................................................................................1102
VRRP for an IPv4 Conguration............................................................................................................................1117
VRRP in a VRF Conguration................................................................................................................................1120
VRRP for IPv6 Conguration................................................................................................................................ 1125
Proxy Gateway with VRRP..........................................................................................................................................1129
63 Debugging and Diagnostics..................................................................................................................... 1134
Important Points to Remember.............................................................................................................................1134
Auto Save on Crash or Rollover.................................................................................................................................. 1138
Recognize an Overtemperature Condition.......................................................................................................... 1139
Troubleshoot an Over-temperature Condition.....................................................................................................1140
Recognize an Under-Voltage Condition............................................................................................................... 1140
Troubleshoot an Under-Voltage Condition...........................................................................................................1140
Displaying Drop Counters....................................................................................................................................... 1142
Display Stack Port Statistics..................................................................................................................................1146
Display Stack Member Counters...........................................................................................................................1147
Mini Core Dumps.......................................................................................................................................................... 1150
RFC and I-D Compliance..............................................................................................................................................1153
General Internet Protocols.....................................................................................................................................1153
General IPv4 Protocols...........................................................................................................................................1155
General IPv6 Protocols...........................................................................................................................................1156
Open Shortest Path First (OSPF)........................................................................................................................ 1158
Intermediate System to Intermediate System (IS-IS)........................................................................................ 1158
Routing Information Protocol (RIP)......................................................................................................................1159
Introduction to X.509v3 certication..........................................................................................................................1167
How certicates are requested............................................................................................................................. 1167
Advantages of X.509v3 certicates..................................................................................................................... 1168
X.509v3 support in ......................................................................................................................................................1168
Information about installing CA certicates...............................................................................................................1170
Installing CA certicate...........................................................................................................................................1170
Information about Creating Certicate Signing Requests (CSR)........................................................................... 1170
Information about installing trusted certicates........................................................................................................1172
Transport layer security (TLS).....................................................................................................................................1172
Syslog over TLS.......................................................................................................................................................1173
Online Certicate Status Protocol (OSCP)................................................................................................................1173
Conguring OCSP setting on CA..........................................................................................................................1173
Verifying Server certicates.................................................................................................................................. 1175
This guide describes the protocols and features the Dell EMC Networking Operating System (OS) supports and provides conguration
instructions and examples for implementing them. For complete information about all the CLI commands, see the Dell EMC Command Line Reference Guide for your system.
The S6000–ON platform is available with Dell EMC Networking OS version 9.7(0.0) and beyond.
Though this guide contains information about protocols, it is not intended to be a complete reference. This guide is a reference for
conguring protocols on Dell EMC Networking systems. For complete information about protocols, see the related documentation,
including Internet Engineering Task Force (IETF) requests for comments (RFCs). The instructions in this guide cite relevant RFCs. The
Standards Compliance chapter contains a complete list of the supported RFCs and management information base les (MIBs).
Topics:
•Audience
•Conventions
•Related Documents
Audience
This document is intended for system administrators who are responsible for conguring and maintaining networks and assumes knowledge
in Layer 2 (L2) and Layer 3 (L3) networking technologies.
Conventions
This guide uses the following conventions to describe command syntax.
Keyword
parameterParameters are in italics and require a number or word to be entered in the CLI.
{X}Keywords and parameters within braces must be entered in the CLI.
[X]Keywords and parameters within brackets are optional.
x|yKeywords and parameters separated by a bar require you to choose one option.
x||yKeywords and parameters separated by a double bar allows you to choose any or all of the options.
Keywords are in Courier (a monospaced font) and must be entered in the CLI as listed.
Related Documents
For more information about the Dell EMC Networking switches, see the following documents:
•Dell EMC Networking OS Command Line Reference Guide
•Dell EMC Networking OS Installation Guide
•Dell EMC Networking OS Quick Start Guide
•Dell EMC Networking OS Release Notes
36About this Guide
2
Conguration Fundamentals
The Dell EMC Networking Operating System (OS) command line interface (CLI) is a text-based interface you can use to congure
interfaces and protocols.
The CLI is largely the same for each platform except for some commands and command outputs. The CLI is structured in modes for
security and management purposes. Dierent sets of commands are available in each mode, and you can limit user access to modes using
privilege levels.
In the Dell EMC Networking OS, after you enter a command, the command is added to the running conguration le. You can view the
current conguration for the whole system or for a particular CLI mode. To save the current conguration, copy the running conguration
to another location.
NOTE: Due to dierences in hardware architecture and continued system development, features may occasionally dier between
the platforms. Dierences are noted in each CLI description and related documentation.
Topics:
•Accessing the Command Line
•CLI Modes
•The do Command
•Undoing Commands
•Obtaining Help
•Entering and Editing Commands
•Command History
•Filtering show Command Outputs
•Multiple Users in Conguration Mode
Accessing the Command Line
Access the CLI through a serial console port or a Telnet session.
When the system successfully boots, enter the command line in EXEC mode.
: You must have a password congured on a virtual terminal line before you can Telnet into the system. Therefore, you must
NOTE
use a console connection when connecting to the system for the rst time.
telnet 172.31.1.53
Trying 172.31.1.53...
Connected to 172.31.1.53.
Escape character is '^]'.
Login: username
Password:
DellEMC>
CLI Modes
Dierent sets of commands are available in each mode.
A command found in one mode cannot be executed from another mode (except for EXEC mode commands with a preceding do command
(refer to the do Command section).
Conguration Fundamentals37
You can set user access rights to commands and command modes using privilege levels.
The Dell EMC Networking OS CLI is divided into three major mode levels:
•EXEC mode is the default mode and has a privilege level of 1, which is the most restricted level. Only a limited selection of commands is
available, notably the show commands, which allow you to view system information.
•EXEC Privilege mode has commands to view congurations, clear counters, manage conguration les, run diagnostics, and enable or
disable debug operations. The privilege level is 15, which is unrestricted. You can congure a password for this mode; refer to the
Congure the Enable Password section in the Getting Started chapter.
•CONFIGURATION mode allows you to congure security features, time settings, set logging and SNMP functions, congure static ARP
and MAC addresses, and set line cards on the system.
Beneath CONFIGURATION mode are submodes that apply to interfaces, protocols, and features. The following example shows the
submode command structure. Two sub-CONFIGURATION modes are important when conguring the chassis for the rst time:
•INTERFACE submode is the mode in which you congure Layer 2 and Layer 3 protocols and IP services specic to an interface. An
interface can be physical (Management interface, 1 Gigabit Ethernet, 10 Gigabit Ethernet, 25 Gigabit Ethernet, 40 Gigabit Ethernet, 50
Gigabit Ethernet, or 100 Gigabit Ethernet) or logical (Loopback, Null, port channel, or virtual local area network [VLAN]).
•LINE submode is the mode in which you to congure the console and virtual terminal lines.
NOTE: At any time, entering a question mark (?) displays the available command options. For example, when you are in
CONFIGURATION mode, entering the question mark rst lists all available commands, including the possible submodes.
The CLI modes are:
EXEC
EXEC Privilege
CONFIGURATION
AS-PATH ACL
CONTROL-PLANE
CLASS-MAP
DCB POLICY
DHCP
DHCP POOL
ECMP-GROUP
EXTENDED COMMUNITY
FRRP
INTERFACE
GROUP
GIGABIT ETHERNET
10 GIGABIT ETHERNET
40 GIGABIT ETHERNET
INTERFACE RANGE
LOOPBACK
MANAGEMENT ETHERNET
NULL
PORT-CHANNEL
TUNNEL
VLAN
VRRP
IP
IPv6
IP COMMUNITY-LIST
IP ACCESS-LIST
STANDARD ACCESS-LIST
EXTENDED ACCESS-LIST
MAC ACCESS-LIST
LINE
AUXILLIARY
CONSOLE
VIRTUAL TERMINAL
LLDP
LLDP MANAGEMENT INTERFACE
MONITOR SESSION
MULTIPLE SPANNING TREE
OPENFLOW INSTANCE
PVST
The Dell EMC Networking OS prompt changes to indicate the CLI mode.
The following table lists the CLI mode, its prompt, and information about how to access and exit the CLI mode. Move linearly through the
command modes, except for the end command which takes you directly to EXEC Privilege mode and the exit command which moves
you up one command mode level.
NOTE
: Sub-CONFIGURATION modes all have the letters conf in the prompt with more modiers to identify the mode and slot/
port/subport information.
Table 1. Dell EMC Networking OS Command Modes
CLI Command ModePromptAccess Command
EXEC
EXEC Privilege
CONFIGURATION
NOTE: Access all of the following
modes from CONFIGURATION
mode.
AS-PATH ACL
DellEMC>
DellEMC#
DellEMC(conf)#
DellEMC(config-as-path)#ip as-path access-list
Access the router through the console or
terminal line.
•From EXEC mode, enter the enable
command.
•From any other mode, use the end
command.
•From EXEC privilege mode, enter the
configure command.
•From every mode except EXEC and
EXEC Privilege, enter the exit
command.
You can enter an EXEC mode command from any CONFIGURATION mode (CONFIGURATION, INTERFACE, SPANNING TREE, and so
on.) without having to return to EXEC mode by preceding the EXEC mode command with the
The following example shows the output of the do command.
-- Stack Info -Unit UnitType Status ReqTyp CurTyp Version Ports
----------------------------------------------------------------------- 1 Management online S6000-ON S6000-ON 1-0(0-3932) 128
2 Member not present
3 Member not present
4 Member not present
5 Member not present
6 Member not present
-- Power Supplies -Unit Bay Status Type FanStatus FanSpeed(rpm)
----------------------------------------------------------- 1 1 up AC absent 0
1 2 absent absent 0
-- Fan Status -Unit Bay TrayStatus Fan0 Speed Fan1 Speed
---------------------------------------------------------------- 1 1 up up 0 up 0
1 2 up up 0 up 0
1 3 up up 0 up 0
do command.
Speed in RPM
Undoing Commands
When you enter a command, the command line is added to the running conguration le (running-cong).
To disable a command and remove it from the running-cong, enter the no command, then the original command. For example, to delete
an IP address congured on an interface, use the
NOTE
: Use the help or ? command as described in Obtaining Help.
Example of Viewing Disabled Commands
DellEMC(conf)#interface tengigabitethernet 1/17/1
DellEMC(conf-if-te-1/17/1)#ip address 192.168.10.1/24
DellEMC(conf-if-te-1/17/1)#show config
!
interface tenGigabitEthernet 1/17/1
ip address 192.168.10.1/24
no shutdown
DellEMC(conf-if-te-1/17/1)#no ip address
DellEMC(conf-if-te-1/17/1)#show config
!
interface TenGigabitEthernet 1/17/1
no ip address
no shutdown
no ip address ip-address command.
Conguration Fundamentals
42
Layer 2 protocols are disabled by default. To enable Layer 2 protocols, use the no disable command. For example, in PROTOCOL
SPANNING TREE mode, enter no disable to enable Spanning Tree.
Obtaining Help
Obtain a list of keywords and a brief functional description of those keywords at any CLI mode using the ? or help command:
To list the keywords available in the current mode, enter ? at the prompt or after a keyword.
•
•Enter ? after a command prompt to list all of the available keywords. The output of this command is the same as the help command.
DellEMC#?
bmp BMP commands
cd Change current directory
clear Reset functions
clock Manage the system clock
•Enter ? after a partial keyword lists all of the keywords that begin with the specied letters.
•Enter [space]? after a keyword lists all of the keywords that can follow the specied keyword.
DellEMC(conf)#clock ?
summer-time Configure summer (daylight savings) time
timezone Configure time zone
DellEMC(conf)#clock
Entering and Editing Commands
Notes for entering commands.
•The CLI is not case-sensitive.
•You can enter partial CLI keywords.
– Enter the minimum number of letters to uniquely identify a command. For example, you cannot enter cl as a partial keyword
because both the clock and class-map commands begin with the letters “cl.” You can enter clo, however, as a partial keyword
because only one command begins with those three letters.
•The TAB key auto-completes keywords in commands. Enter the minimum number of letters to uniquely identify a command.
•The UP and DOWN arrow keys display previously entered commands (refer to Command History).
•The BACKSPACE and DELETE keys erase the previous letter.
•Key combinations are available to move quickly across the command line. The following table describes these short-cut key
combinations.
Short-Cut Key
Combination
CNTL-AMoves the cursor to the beginning of the command line.
CNTL-BMoves the cursor back one character.
CNTL-DDeletes character at cursor.
CNTL-EMoves the cursor to the end of the line.
CNTL-FMoves the cursor forward one character.
Action
CNTL-ICompletes a keyword.
CNTL-KDeletes all characters from the cursor to the end of the command line.
CNTL-LRe-enters the previous command.
Conguration Fundamentals43
Short-Cut Key
Action
Combination
CNTL-NReturn to more recent commands in the history buer after recalling commands with CTRL-P or the UP arrow key.
CNTL-PRecalls commands, beginning with the last command.
CNTL-RRe-enters the previous command.
CNTL-UDeletes the line.
CNTL-WDeletes the previous word.
CNTL-XDeletes the line.
CNTL-ZEnds continuous scrolling of command outputs.
Esc BMoves the cursor back one word.
Esc FMoves the cursor forward one word.
Esc DDeletes all characters from the cursor to the end of the word.
Command History
The Dell EMC Networking OS maintains a history of previously-entered commands for each mode. For example:
•When you are in EXEC mode, the UP and DOWN arrow keys display the previously-entered EXEC mode commands.
•When you are in CONFIGURATION mode, the UP or DOWN arrows keys recall the previously-entered CONFIGURATION mode
commands.
Filtering show Command Outputs
Filter the output of a show command to display specic information by adding | [except | find | grep | no-more | save] specified_text after the command.
The variable specified_text is the text for which you are ltering and it IS case sensitive unless you use the ignore-case suboption.
Starting with Dell EMC Networking OS version 7.8.1.0, the grep command accepts an ignore-case sub-option that forces the search
to case-insensitive. For example, the commands:
•show run | grep Ethernet returns a search result with instances containing a capitalized “Ethernet,” such as interface
TenGigabitEthernet 1/1/1
•show run | grep ethernet does not return that search result because it only searches for instances containing a noncapitalized “ethernet.”
•show run | grep Ethernet ignore-case returns instances containing both “Ethernet” and “ethernet.”
The grep command displays only the lines containing specied text. The following example shows this command used in combination with
show system brief command.
the
Example of the grep Keyword
DellEMC(conf)#do show system brief | grep 0
0 not present
.
: Dell EMC Networking OS accepts a space or no space before and after the pipe. To lter a phrase with spaces,
NOTE
underscores, or ranges, enclose the phrase with double quotation marks.
44Conguration Fundamentals
The except keyword displays text that does not match the specied text. The following example shows this command used in
combination with the show system brief command.
The find keyword displays the output of the show command beginning from the rst occurrence of specied text. The following example
shows this command used in combination with the show system brief command.
Example of the find Keyword
The display command displays additional conguration information.
The no-more command displays the output all at once rather than one screen at a time. This is similar to the terminal length
command except that the no-more option aects the output of the specied command only.
The save command copies the output to a le for future reference.
NOTE: You can lter a single command output multiple times. The save option must be the last option entered. For example:
Dell EMC Networking OS noties all users when there are multiple users logged in to CONFIGURATION mode.
A warning message indicates the username, type of connection (console or VTY), and in the case of a VTY connection, the IP address of
the terminal on which the connection was established. For example:
•On the system that telnets into the switch, this message appears:
% Warning: The following users are currently configuring the system:
User "<username>" on line console0
•On the system that is connected over the console, this message appears:
% Warning: User "<username>" on line vty0 "10.11.130.2" is in configuration mode
If either of these messages appears, Dell EMC Networking recommends coordinating with the users listed in the message so that you do
not unintentionally overwrite each other’s conguration changes.
Conguration
Fundamentals45
Getting Started
This chapter describes how you start conguring your system.
When you power up the chassis, the system performs a power-on self test (POST) and system then loads the Dell EMC Networking
Operating System. Boot messages scroll up the terminal window during this process. No user interaction is required if the boot process
proceeds without interruption.
When the boot process completes, the system status LEDs remain online (green) and the console monitor displays the EXEC mode
prompt.
For details about using the command line interface (CLI), refer to the Accessing the Command Line section in the Conguration
Fundamentals chapter.
Topics:
•Console Access
•Default Conguration
•Conguring a Host Name
•Accessing the System Remotely
•Conguring the Enable Password
•Conguration File Management
•Managing the File System
•View Command History
•Upgrading Dell EMC Networking OS
•Using HTTP for File Transfers
•Verify Software Images Before Installation
3
46Getting Started
Console Access
The device has one RJ-45/RS-232 console port, an out-of-band (OOB) Ethernet port, and a micro USB-B console port.
Serial Console
The RJ-45/RS-232 console port is labeled on the upper right-hand side, as you face the I/O side of the chassis.
Figure 1. RJ-45 Console Port
1RS-232 console port.
2USB port.
Accessing the Console Port
To access the console port, follow these steps:
For the console port pinout, refer to Accessing the RJ-45 Console Port with a DB-9 Adapter.
1 Install an RJ-45 copper cable into the console port. Use a rollover (crossover) cable to connect the console port to a terminal server.
2 Connect the other end of the cable to the DTE terminal server.
3 Terminal settings on the console port cannot be changed in the software and are set as follows:
•115200 baud rate
•No parity
•8 data bits
•1 stop bit
•No ow control
Getting Started
47
Pin Assignments
You can connect to the console using a RJ-45 to RJ-45 rollover cable and a RJ-45 to DB-9 female DTE adapter to a terminal server (for
example, a PC).
The pin assignments between the console and a DTE terminal server are as follows:
Table 2. Pin Assignments Between the Console and a DTE Terminal Server
Console PortRJ-45 to RJ-45 Rollover
Cable
SignalRJ-45 PinoutRJ-45 PinoutDB-9 PinSignal
RTS188CTS
NC276DSR
TxD362RxD
GND455GND
GND545GND
RxD633TxD
NC724DTR
CTS817RTS
RJ-45 to RJ-45 Rollover
Cable
RJ-45 to DB-9 AdapterTerminal Server Device
Default Conguration
Although a version of Dell EMC Networking OS is pre-loaded onto the system, the system is not congured when you power up the system
rst time (except for the default hostname, which is DellEMC). You must congure the system using the CLI.
Conguring a Host Name
The host name appears in the prompt. The default host name is DellEMC.
•Host names must start with a letter and end with a letter or digit.
•Characters within the string can be letters, digits, and hyphens.
To create a host name, use the hostname name command in Conguration mode.
hostname command example
DellEMC(conf)#hostname R1
R1(conf)#
Accessing the System Remotely
You can congure the system to access it remotely by Telnet or secure shell (SSH).
•The platform has a dedicated management port and a management routing table that is separate from the IP routing table.
•You can manage all Dell EMC Networking products in-band via the front-end data ports through interfaces assigned an IP address as
well.
Getting Started
48
Accessing the System Remotely
Conguring the system for remote access is a three-step process, as described in the following topics:
1Congure an IP address for the management port. Congure the Management Port IP Address
2Congure a management route with a default gateway. Congure a Management Route
3Congure a username and password. Congure a Username and Password
Congure the Management Port IP Address
To access the system remotely, assign IP addresses to the management ports.
1 Enter INTERFACE mode for the Management port.
CONFIGURATION mode
interface ManagementEthernet slot/port
2 Assign an IP address to the interface.
INTERFACE mode
ip address ip-address/mask
•ip-address: an address in dotted-decimal format (A.B.C.D).
•mask: a subnet mask in /prex-length format (/ xx).
3 Enable the interface.
INTERFACE mode
no shutdown
Congure a Management Route
Dene a path from the system to the network from which you are accessing the system remotely. Management routes are separate from
IP routes and are only used to manage the system through the management port.
To congure a management route, use the following command.
•Congure a management route to the network from which you are accessing the system.
CONFIGURATION mode
management route ip-address/mask gateway
– ip-address: the network address in dotted-decimal format (A.B.C.D).
– mask: a subnet mask in /prex-length format (/ xx).
– gateway: the next hop for network trac originating from the management port.
Conguring a Username and Password
To access the system remotely, congure a system username and password.
To congure a system username and password, use the following command.
•Congure a username and password to access the system remotely.
CONFIGURATION mode
– name: Enter a text string upto 63 characters long.
– access-class access-list-name: Enter the name of a congured IP ACL.
nopassword: Allows you to congure an user without the password.
–
– password: Allows you to congure an user with a password.
– secret: Specify a secret string for an user.
– sha256–password: Uses sha256–based encryption method for password.
– encryption-type: Enter the encryption type for securing an user password. There are four encryption types.
◦0 — input the password in clear text.
◦5 — input the password that is already encrypted using MD5 encryption method.
◦7 — input the password that is already encrypted using DES encryption method.
◦8 — input the password that is already encrypted using sha256–based encryption method.
– password: Enter the password string for the user.
– dynamic-salt: Generates an additional random input to password encryption process whenever the password is congured.
– privilege level: Assign a privilege levels to the user. The range is from 0 to 15.
– role role-name: Assign a role name for the user.
Dell EMC Networking OS encrypts type 5 secret and type 7 password based on dynamic-salt option such that the encrypted
password is dierent when an user is congured with the same password.
NOTE
:
dynamic-salt option is shown only with secret and password options.
In dynamic-saltconguration, the length of type 5 secret and type 7 password is 32 and 16 characters more compared to the
secret and password length without dynamic-salt conguration. An error message appears if the
maximum length, which is 256 characters.
The dynamic-salt support for the user conguration is added in REST API. For more information on REST support, see Dell EMC
Networking Open Automation guide
.
username command reaches the
Conguring the Enable Password
Access EXEC Privilege mode using the enable command. EXEC Privilege mode is unrestricted by default. Congure a password as a
basic security measure.
There are three types of enable passwords:
•enable password is stored in the running/startup conguration using a DES encryption method.
•enable secret is stored in the running/startup conguration using MD5 encryption method.
•enable sha256-password is stored in the running/startup conguration using sha256-based encryption method (PBKDF2).
Dell EMC Networking recommends using the enable sha256-password password.
To congure an enable password, use the following command.
•Create a password to access EXEC Privilege mode.
CONFIGURATION mode
– level: is the privilege level, is 15 by default, and is not required.
– encryption-type: species how you input the password, is 0 by default, and is not required.
◦0 is to input the password in clear text.
◦5 is to input a password that is already encrypted using MD5 encryption method. Obtain the encrypted password from the
conguration le of another device.
◦7 is to input a password that is already encrypted using DES encryption method. Obtain the encrypted password from the
conguration le of another device.
◦8 is to input a password that is already encrypted using sha256-based encryption method. Obtain the encrypted password from
the congurationle of another device.
Conguration File Management
Files can be stored on and accessed from various storage media. Rename, delete, and copy les on the system from EXEC Privilege mode.
Copy Files to and from the System
The command syntax for copying les is similar to UNIX. The copy command uses the format copy source-file-url
destination-file-url.
NOTE: For a detailed description of the copy command, refer to the
•To copy a local le to a remote system, combine the le-origin syntax for a local le location with the le-destination syntax for a remote
le location.
•To copy a remote le to Dell EMC Networking system, combine the le-origin syntax for a remote le location with the le-destination
syntax for a local le location.
This feature enables you to quickly access data on an NFS mounted le system. You can perform le operations on an NFS mounted le
system using supported le commands.
This feature allows an NFS mounted device to be recognized as a le system. This le system is visible on the device and you can execute
all le commands that are available on conventional le systems such as a Flash le system.
Before executing any CLI command to perform le operations, you must rst mount the NFS le system to a mount-point on the device.
Since multiple mount-points exist on a device, it is mandatory to specify the mount-point to which you want to load the system.
The /f10/mnt/nfs directory is the root of all mount-points.
To mount an NFS le system, perform the following steps:
Table 4. Mounting an NFS File System
File OperationSyntax
To mount an NFS le system:
mount nfs rhost:path mountpoint username password
The foreign le system remains mounted as long as the device is up and does not reboot. You can run the le system commands without
having to mount or un-mount the le system each time you run a command. When you save the conguration using the write command,
the mount command is saved to the startup conguration. As a result, each time the device re-boots, the NFS le system is mounted
during start up.
Source file name []: test.c
User name to login remote host: username
Example of Logging in to Copy from NFS Mount
DellEMC#copy nfsmount:///test flash:
Destination file name [test]: test2
!
5592 bytes successfully copied
DellEMC#
DellEMC#copy nfsmount:///test.txt ftp://10.16.127.35
Destination file name [test.txt]:
User name to login remote host: username
Password to login remote host:
!
Example of Copying to NFS Mount
DellEMC#copy flash://test.txt nfsmount:///
Destination file name [test.txt]:
!
15 bytes successfully copied
DellEMC#copy flash://test/capture.txt.pcap nfsmount:///
Destination file name [test.txt]:
!
15 bytes successfully copied
DellEMC#copy flash://test/capture.txt.pcap nfsmount:///username/snoop.pcap
!
24 bytes successfully copied
DellEMC#
DellEMC#copy tftp://10.16.127.35/username/dv-maa-test ?
flash: Copy to local file system ([flash://]filepath)
nfsmount: Copy to nfs mount file system (nfsmount:///filepath)
running-config remote host:
Destination file name [test.c]:
!
225 bytes successfully copied
DellEMC#
Save the Running-Conguration
The running-conguration contains the current system conguration. Dell EMC Networking recommends coping your running-conguration
to the startup-conguration.
The commands in this section follow the same format as those commands in the Copy Files to and from the System section but use the lenamesstartup-conguration and running-conguration. These commands assume that current directory is the internal ash, which is
the system default.
•Save the running-conguration to the startup-conguration on the internal ash of the primary RPM.
EXEC Privilege mode
copy running-config startup-config
•Save the running-conguration to an FTP server.
EXEC Privilege mode
NOTE: When copying to a server, a host name can only be used if a DNS server is
congured.
NOTE: When you load the startup conguration or a congurationle from a network server such as TFTP to the running
conguration, the conguration is added to the running conguration. This does not replace the existing running conguration.
Commands in the conguration le has precedence over commands in the running conguration.
Congure the Overload Bit for a Startup Scenario
For information about setting the router overload bit for a specic period of time after a switch reload is implemented, see the Intermediate
System to Intermediate System (IS-IS) section in the Dell Command Line Reference Guide for your system.
Viewing Files
You can only view le information and content on local le systems.
To view a list of les or the contents of a le, use the following commands.
•View a list of les on the internal ash.
EXEC Privilege mode
dir flash:
•View the running-conguration.
EXEC Privilege mode
show running-config
•View the startup-conguration.
EXEC Privilege mode
show startup-config
Example of the dir Command
The output of the dir command also shows the read/write privileges, size (in bytes), and date of modication for each le.
Congurationles have three commented lines at the beginning of the le, as shown in the following example, to help you track the last
time any user made a change to the le, which user made the changes, and when the le was last saved to the startup-conguration.
In the running-congurationle, if there is a dierence between the timestamp on the “Last conguration change” and “Startup-cong last
updated,” you have made changes that have not been saved and are preserved after a system reboot.
Example of the show running-config Command
DellEMC#show running-config
Current Configuration ...
! Version 9.4(0.0)
! Last configuration change at Tue Mar 11 21:33:56 2014 by admin
! Startup-config last updated at Tue Mar 11 12:11:00 2014 by default
!
<output truncated for brevity>
Managing the File System
The Dell EMC Networking system can use the internal Flash, external Flash, or remote devices to store les.
The system stores les on the internal Flash by default but can be congured to store les elsewhere.
To view le system information, use the following command.
•View information about each le system.
EXEC Privilege mode
show file-systems
The output of the show file-systems command in the following example shows the total capacity, amount of free memory, le
structure, media type, read/write privileges for each storage device in use.
You can change the default le system so that le management commands apply to a particular device or memory.
To change the default directory, use the following command.
•Change the default directory.
EXEC Privilege mode
cd directory
View Command History
The command-history trace feature captures all commands entered by all users of the system with a time stamp and writes these
messages to a dedicated trace log buer.
The system generates a trace message for each executed command. No password information is saved to the le.
To view the command-history trace, use the show command-history command.
To upgrade Dell EMC Networking Operating System (OS), refer to the Release Notes for the version you want to load on the system.
You can download the release notes of your platform at http://www.force10networks.com. Use your login ID to log in to the website.
Using HTTP for File Transfers
Stating with Release 9.3(0.1), you can use HTTP to copy les or conguration details to a remote server. To transfer les to an external
server, use the copy source-le-urlhttp://host[:port]/le-path command.
Enter the following source-le-url keywords and information:
•To copy a le from the internal FLASH, enter ash:// followed by the lename.
•To copy the running conguration, enter the keyword running-cong.
•To copy the startup conguration, enter the keyword startup-cong.
•To copy a le on the USB device, enter usbash:// followed by the lename.
In the Dell EMC Networking OS release 9.8(0.0), HTTP services support the VRF-aware functionality. If you want the HTTP server to use a
VRF table that is attached to an interface, congure that HTTP server to use a specic routing table. You can use the ip http vrf
command to inform the HTTP server to use a specic routing table. After you congure this setting, the VRF table is used to look up the
destination address.
: To enable HTTP to be VRF-aware, as a prerequisite you must rstdene the VRF.
NOTE
You can specify either the management VRF or a nondefault VRF to congure the VRF awareness setting.
When you specify the management VRF, the copy operation that is used to transfer les to and from an HTTP server utilizes the VRF table
corresponding to the Management VRF to look up the destination. When you specify a nondefault VRF, the VRF table corresponding to
that nondefault VRF is used to look up the HTTP server.
However, these changes are backward-compatible and do not aect existing behavior; meaning, you can still use the ip http source-
interface
NOTE
To enable an HTTP client to look up the VRF table corresponding to either management VRF or any nondefault VRF, use the ip http
vrf command in CONFIGURATION mode.
•Congure an HTTP client with a VRF that is used to connect to the HTTP server.
CONFIGURATION MODE
command to communicate with a particular interface even if no VRF is congured on that interface
: If the HTTP service is not VRF-aware, then it uses the global routing table to perform the look-up.
Getting Started
56
Verify Software Images Before Installation
To validate the software image on the ash drive, you can use the MD5 message-digest algorithm or SHA256 Secure Hash Algorithm, after
the image is transferred to the system but before the image is installed. The validation calculates a hash value of the downloaded image le
on system’s ash drive, and, optionally, compares it to a Dell EMC Networking published hash for that le.
The MD5 or SHA256 hash provides a method of validating that you have downloaded the original software. Calculating the hash on the
local image le and comparing the result to the hash published for that le on iSupport provides a high level of condence that the local
copy is exactly the same as the published software image. This validation procedure, and the verify {md5 | sha256} command to
support it, prevents the installation of corrupted or modied images.
The verify {md5 | sha256} command calculates and displays the hash of any le on the specied local ash drive. You can
compare the displayed hash against the appropriate hash published on iSupport. Optionally, you can include the published hash in the
verify {md5 | sha256} command, which displays whether it matches the calculated hash of the indicated le.
To validate a software image:
1Download Dell EMC Networking OS software image le from the iSupport page to the local (FTP or TFTP) server. The published hash
for that le displays next to the software image le on the iSupport page.
2Go on to the Dell EMC Networking system and copy the software image to the ash drive, using the copy command.
3Run the verify {md5 | sha256} [ flash://]img-file [hash-value] command. For example, verify sha256
flash://FTOS-SE-9.5.0.0.bin
4Compare the generated hash value to the expected hash value published on the iSupport page.
To validate the software image on the ash drive after the image is transferred to the system, but before you install the image, use the
verify {md5 | sha256} [ flash://]img-file [hash-value] command in EXEC mode.
•md5: MD5 message-digest algorithm
•sha256: SHA256 Secure Hash Algorithm
•flash: (Optional) Species the ash drive. The default uses the ash drive. You can enter the image le name.
•hash-value: (Optional). Specify the relevant hash published on iSupport.
•img-file: Enter the name of the Dell EMC Networking software image le to validate
Examples: Without Entering the Hash Value for Verication
This chapter describes the dierent protocols or services used to manage the Dell EMC Networking system.
Topics:
•Conguring Privilege Levels
•Conguring Logging
•Log Messages in the Internal Buer
•Disabling System Logging
•Sending System Messages to a Syslog Server
•Track Login Activity
•Limit Concurrent Login Sessions
•Enabling Secured CLI Mode
•Changing System Logging Settings
•Display the Logging Buer and the Logging Conguration
•Conguring a UNIX Logging Facility Level
•Synchronizing Log Messages
•Enabling Timestamp on Syslog Messages
•File Transfer Services
•Terminal Lines
•Setting Timeout for EXEC Privilege Mode
•Using Telnet to get to Another Network Device
•Lock CONFIGURATION Mode
•Restoring the Factory Default Settings
•Viewing the Reason for Last System Reboot
4
Conguring Privilege Levels
Privilege levels restrict access to commands based on user or terminal line.
There are 16 privilege levels, of which three are pre-dened. The default privilege level is 1.
Level
Level 0Access to the system begins at EXEC mode, and EXEC mode commands are limited to enable, disable, and
Level 1Access to the system begins at EXEC mode, and all commands are available.
Level 15Access to the system begins at EXEC Privilege mode, and all commands are available.
For information about how access and authorization is controlled based on a user’s role, see Role-Based Access Control.
58Management
Description
exit.
Creating a Custom Privilege Level
Custom privilege levels start with the default EXEC mode command set. You can then customize privilege levels 2-14 by:
•restricting access to an EXEC mode command
•moving commands from EXEC Privilege to EXEC mode
•restricting access
A user can access all commands at his privilege level and below.
Removing a Command from EXEC Mode
To remove a command from the list of available commands in EXEC mode for a specic privilege level, use the privilege exec
command from CONFIGURATION mode.
In the command, specify a level greater than the level given to a user or terminal line, then the rst keyword of each command you wish to
restrict.
Moving a Command from EXEC Privilege Mode to EXEC Mode
To move a command from EXEC Privilege to EXEC mode for a privilege level, use the privilege exec command from
CONFIGURATION mode.
In the command, specify the privilege level of the user or terminal line and specify all keywords in the command to which you want to allow
access.
Allowing Access to CONFIGURATION Mode Commands
To allow access to CONFIGURATION mode, use the privilege exec level level configure command from
CONFIGURATION mode.
A user that enters CONFIGURATION mode remains at his privilege level and has access to only two commands, end and exit. You must
individually specify each CONFIGURATION mode command you want to allow access to using the privilege configure level level command. In the command, specify the privilege level of the user or terminal line and specify all the keywords in the command to
which you want to allow access.
Allowing Access to Dierent Modes
This section describes how to allow access to the INTERFACE, LINE, ROUTE-MAP, and ROUTER modes.
Similar to allowing access to CONFIGURATION mode, to allow access to INTERFACE, LINE, ROUTE-MAP, and ROUTER modes, you must
rst allow access to the command that enters you into the mode. For example, to allow a user to enter INTERFACE mode, use the
privilege configure level level interface tengigabitethernet command.
Next, individually identify the INTERFACE, LINE, ROUTE-MAP or ROUTER commands to which you want to allow access using the
privilege {interface | line | route-map | router} level level command. In the command, specify the privilege
level of the user or terminal line and specify all the keywords in the command to which you want to allow access.
To remove, move or allow access, use the following commands.
The conguration in the following example creates privilege level 3. This level:
Management
59
•removes the resequence command from EXEC mode by requiring a minimum of privilege level 4
•moves the capture bgp-pdu max-buffer-size command from EXEC Privilege to EXEC mode by requiring a minimum privilege
level 3, which is the congured level for VTY 0
•allows access to CONFIGURATION mode with the banner command
•allows access to INTERFACE tengigabitethernet and LINE modes are allowed with no commands
•Remove a command from the list of available commands in EXEC mode.
CONFIGURATION mode
DellEMC#show running-config privilege
!
privilege exec level 3 configure
privilege exec level 4 resequence
privilege configure level 3 line
privilege configure level 3 interface tengigabitethernet
DellEMC#telnet 10.11.80.201
DellEMC#?
configure Configuring from terminal
disable Turn off privileged commands
enable Turn on privileged commands
ethernet Ethernet commands
exit Exit from the EXEC
ip Global IP subcommands
ipv6 Global IPv6 subcommands
monitor Monitoring feature
ping Send echo messages
quit Exit from the EXEC
show Show running system information
DellEMC#config
DellEMC(conf)#do show priv
Current privilege level is 3.
DellEMC(conf)#?
end Exit from configuration mode
exit Exit from configuration mode
interface Select an interface to configure
line Configure a terminal line
DellEMC(conf)#
DellEMC(conf)#interface ?
tengigabitethernet TenGigabit Ethernet interface
DellEMC(conf)#
DellEMC(conf)#interface tengigabitethernet 1/26/1
60
Management
DellEMC(conf-if-te-1/26/1)#?
end Exit from configuration mode
exit Exit from interface configuration mode
DellEMC(conf-if-te-1/26/1)#exit
DellEMC(conf)#
DellEMC(conf)#line ?
console Primary terminal line
vty Virtual terminal
DellEMC(conf)#line vty 0
DellEMC(config-line-vty)#exit
DellEMC(conf)#
Applying a Privilege Level to a Username
To set the user privilege level, use the following command.
•Congure a privilege level for a user.
CONFIGURATION mode
username username privilege level
Applying a Privilege Level to a Terminal Line
To set a privilege level for a terminal line, use the following command.
•Congure a privilege level for a user.
CONFIGURATION mode
username username privilege level
: When you assign a privilege level between 2 and 15, access to the system begins at EXEC mode, but the prompt is
NOTE
hostname#, rather than hostname>.
Conguring Logging
The Dell EMC Networking OS tracks changes in the system using event and error messages.
By default, Dell EMC Networking OS logs these messages on:
•the internal buer
•console and terminal lines
•any congured syslog servers
To disable logging, use the following commands.
•Disable all logging except on the console.
CONFIGURATION mode
no logging on
•Disable logging to the logging buer.
CONFIGURATION mode
no logging buffer
•Disable logging to terminal lines.
CONFIGURATION mode
no logging monitor
Management
61
•Disable console logging.
CONFIGURATION mode
no logging console
Audit and Security Logs
This section describes how to congure, display, and clear audit and security logs.
The following is the conguration task list for audit and security logs:
•Enabling Audit and Security Logs
•Displaying Audit and Security Logs
•Clearing Audit Logs
Enabling Audit and Security Logs
You enable audit and security logs to monitor conguration changes or determine if these changes aect the operation of the system in the
network. You log audit and security events to a system log server, using the logging extended command in CONFIGURATION mode.
Audit Logs
The audit log contains conguration events and information. The types of information in this log consist of the following:
•User logins to the switch.
•System events for network issues or system issues.
•Users making conguration changes. The switch logs who made the conguration changes and the date and time of the
change. However, each specic change on the conguration is not logged. Only that the conguration was modied is logged with the
user ID, date, and time of the change.
•Uncontrolled shutdown.
Security Logs
The security log contains security events and information. RBAC restricts access to audit and security logs based on the CLI sessions’ user
roles. The types of information in this log consist of the following:
•Establishment of secure trac ows, such as SSH.
•Violations on secure ows or certicate issues.
•Adding and deleting of users.
•User access and conguration changes to the security and crypto parameters (not the key information but the crypto conguration)
Important Points to Remember
When you enabled RBAC and extended logging:
•Only the system administrator user role can execute this command.
•The system administrator and system security administrator user roles can view security events and system events.
•The system administrator user roles can view audit, security, and system events.
•Only the system administrator and security administrator user roles can view security logs.
•The network administrator and network operator user roles can view system events.
62
Management
NOTE: If extended logging is disabled, you can only view system events, regardless of RBAC user role.
Example of Enabling Audit and Security Logs
DellEMC(conf)#logging extended
Displaying Audit and Security Logs
To display audit logs, use the show logging auditlog command in Exec mode. To view these logs, you must rst enable the logging
extended command. Only the RBAC system administrator user role can view the audit logs. Only the RBAC security administrator and
system administrator user role can view the security logs. If extended logging is disabled, you can only view system events, regardless of
RBAC user role. To view security logs, use the
Example of the show logging auditlog Command
For information about the logging extended command, see Enabling Audit and Security Logs
DellEMC#show logging auditlog
May 12 12:20:25: DellEMC#: %CLI-6-logging extended by admin from vty0 (10.14.1.98)
May 12 12:20:42: DellEMC#: %CLI-6-configure terminal by admin from vty0 (10.14.1.98)
May 12 12:20:42: DellEMC#: %CLI-6-service timestamps log datetime by admin from vty0
(10.14.1.98)
Example of the show logging Command for Security
For information about the logging extended command, see Enabling Audit and Security Logs
DellEMC#show logging
Jun 10 04:23:40: %STKUNIT0-M:CP %SEC-5-LOGIN_SUCCESS: Login successful for user admin on line
vty0 ( 10.14.1.91 )
show logging command.
Clearing Audit Logs
To clear audit logs, use the clear logging auditlog command in Exec mode. When RBAC is enabled, only the system administrator
user role can issue this command.
Example of the clear logging auditlog Command
DellEMC# clear logging auditlog
Conguring Logging Format
To display syslog messages in a RFC 3164 or RFC 5424 format, use the logging version {0 | 1} command in CONFIGURATION
mode. By default, the system log version is set to 0.
The following describes the two log messages formats:
•0 – Displays syslog messages format as described in RFC 3164, The BSD syslog Protocol
•1 – Displays syslog message format as described in RFC 5424, The SYSLOG Protocol
Example of Conguring the Logging Message Format
DellEMC(conf)#logging version ?
<0-1> Select syslog version (default = 0)
DellEMC(conf)#logging version 1
Setting Up a Secure Connection to a Syslog Server
You can use reverse tunneling with the port forwarding to securely connect to a syslog server.
Management
63
Figure 2. Setting Up a Secure Connection to a Syslog Server
Pre-requisites
To congure a secure connection from the switch to the syslog server:
1On the switch, enable the SSH server
DellEMC(conf)#ip ssh server enable
2On the syslog server, create a reverse SSH tunnel from the syslog server to the Dell OS switch, using following syntax:
ssh -R <remote port>:<syslog server>:<syslog server listen port> user@remote_host -nNf
In the following example the syslog server IP address is 10.156.166.48 and the listening port is 5141. The switch IP address is
3Congure logging to a local host. locahost is “127.0.0.1” or “::1”.
If you do not, the system displays an error when you attempt to enable role-based only AAA authorization.
DellEMC(conf)# logging localhost tcp port
DellEMC(conf)#logging 127.0.0.1 tcp 5140
64
Management
Log Messages in the Internal Buer
All error messages, except those beginning with %BOOTUP (Message), are log in the internal buer.
For example, %BOOTUP:RPM0:CP %PORTPIPE-INIT-SUCCESS: Portpipe 0 enabled
Conguration Task List for System Log Management
There are two conguration tasks for system log management:
•Disable System Logging
•Send System Messages to a Syslog Server
Disabling System Logging
By default, logging is enabled and log messages are sent to the logging buer, all terminal lines, the console, and the syslog servers.
To disable system logging, use the following commands.
•Disable all logging except on the console.
CONFIGURATION mode
no logging on
•Disable logging to the logging buer.
CONFIGURATION mode
no logging buffer
•Disable logging to terminal lines.
CONFIGURATION mode
no logging monitor
•Disable console logging.
CONFIGURATION mode
no logging console
Sending System Messages to a Syslog Server
To send system messages to a specied syslog server, use the following command. The following syslog standards are supported: RFC
5424 The SYSLOG Protocol, R.Gerhards and Adiscon GmbH, March 2009, obsoletes RFC 3164 and RFC 5426 Transmission of Syslog
Messages over UDP.
•Specify the server to which you want to send system messages. You can congure up to eight syslog servers.
CONFIGURATION mode
You can export system logs to an external server that is connected through a dierent VRF.
Conguring a UNIX System as a Syslog Server
To congure a UNIX System as a syslog server, use the following command.
Management
65
•Congure a UNIX system as a syslog server by adding the following lines to /etc/syslog.conf on the UNIX system and assigning write
permissions to the le.
– Add line on a 4.1 BSD UNIX system. local7.debugging /var/log/ftos.log
– Add line on a 5.7 SunOS UNIX system. local7.debugging /var/adm/ftos.log
In the previous lines, local7 is the logging facility level and debugging is the severity level.
Track Login Activity
Dell EMC Networking OS enables you to track the login activity of users and view the successful and unsuccessful login events.
When you log in using the console or VTY line, the system displays the last successful login details of the current user and the number of
unsuccessful login attempts since your last successful login to the system, and whether the current user’s permissions have changed since
the last login. The system stores the number of unsuccessful login attempts that have occurred in the last 30 days by default. You can
change the default value to any number of days from 1 to 30. By default, login activity tracking is disabled. You can enable it using the
login statistics enable command from the conguration mode.
Restrictions for Tracking Login Activity
These restrictions apply for tracking login activity:
•Only the system and security administrators can congure login activity tracking and view the login activity details of other users.
•Login statistics is not applicable for login sessions that do not use user names for authentication. For example, the system does not
report login activity for a telnet session that prompts only a password.
Conguring Login Activity Tracking
To enable and congure login activity tracking, follow these steps:
1 Enable login activity tracking.
CONFIGURATION mode
login statistics enable
After enabling login statistics, the system stores the login activity details for the last 30 days.
2 (Optional) Congure the number of days for which the system stores the user login statistics. The range is from 1 to 30.
CONFIGURATION mode
login statistics time-period days
Example of Conguring Login Activity Tracking
The following example enables login activity tracking. The system stores the login activity details for the last 30 days.
DellEMC(config)#login statistics enable
The following example enables login activity tracking and congures the system to store the login activity details for 12 days.
To view the login statistics, use the show login statistics command.
Example of the show login statistics Command
The show login statistics command displays the successful and failed login details of the current user in the last 30 days or the
custom dened time period.
User: admin
Last login time: 12:52:01 UTC Tue Mar 22 2016
Last login location: Line vty0 ( 10.16.127.143 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 0
Successful login attempt(s) in last 30 day(s): 1
The show login statistics all command displays the successful and failed login details of all users in the last 30 days or the
custom dened time period.
User: admin
Last login time: 08:54:28 UTC Wed Mar 23 2016
Last login location: Line vty0 ( 10.16.127.145 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 3
Successful login attempt(s) in last 30 day(s): 4
User: admin1
Last login time: 12:49:19 UTC Tue Mar 22 2016
Last login location: Line vty0 ( 10.16.127.145 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 3
Successful login attempt(s) in last 30 day(s): 2
User: admin2
Last login time: 12:49:27 UTC Tue Mar 22 2016
Last login location: Line vty0 ( 10.16.127.145 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 3
Successful login attempt(s) in last 30 day(s): 2
User: admin3
Last login time: 13:18:42 UTC Tue Mar 22 2016
Last login location: Line vty0 ( 10.16.127.145 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 3
Successful login attempt(s) in last 30 day(s): 2
Management
67
Example of the show login statistics user user-id command
The show login statistics user user-id command displays the successful and failed login details of a specic user in the last
30 days or the custom dened time period.
User: admin
Last login time: 12:52:01 UTC Tue Mar 22 2016
Last login location: Line vty0 ( 10.16.127.143 )
Unsuccessful login attempt(s) since the last successful login: 0
Unsuccessful login attempt(s) in last 30 day(s): 0
Successful login attempt(s) in last 30 day(s): 1
The following is sample output of the show login statistics unsuccessful-attempts command.
DellEMC# show login statistics unsuccessful-attempts
There were 3 unsuccessful login attempt(s) for user admin in last 30 day(s).
The following is sample output of the show login statistics unsuccessful-attempts time-period days command.
DellEMC# show login statistics unsuccessful-attempts time-period 15
There were 0 unsuccessful login attempt(s) for user admin in last 15 day(s).
The following is sample output of the show login statistics unsuccessful-attempts user login-id command.
DellEMC# show login statistics unsuccessful-attempts user admin
There were 3 unsuccessful login attempt(s) for user admin in last 12 day(s).
The following is sample output of the show login statistics successful-attempts command.
DellEMC#show login statistics successful-attempts
There were 4 successful login attempt(s) for user admin in last 30 day(s).
Limit Concurrent Login Sessions
Dell EMC Networking OS enables you to limit the number of concurrent login sessions of users on VTY, auxiliary, and console lines. You can
also clear any of your existing sessions when you reach the maximum permitted number of concurrent sessions.
By default, you can use all 10 VTY lines, one console line, and one auxiliary line. You can limit the number of available sessions using the
login concurrent-session limit command and so restrict users to that specic number of sessions. You can optionally
congure the system to provide an option to the users to clear any of their existing sessions.
Restrictions for Limiting the Number of Concurrent Sessions
These restrictions apply for limiting the number of concurrent sessions:
•Only the system and security administrators can limit the number of concurrent sessions and enable the clear-line option.
•Users can clear their existing sessions only if the system is congured with the login concurrent-session clear-line enable command.
Conguring Concurrent Session Limit
To congure concurrent session limit, follow this procedure:
•Limit the number of concurrent sessions for all users.
CONFIGURATION mode
Management
68
login concurrent-session limit number-of-sessions
Example of Conguring Concurrent Session Limit
The following example limits the permitted number of concurrent login sessions to 4.
DellEMC(config)#login concurrent-session limit 4
Enabling the System to Clear Existing Sessions
To enable the system to clear existing login sessions, follow this procedure:
•Use the following command.
CONFIGURATION mode
login concurrent-session clear-line enable
Example of Enabling the System to Clear Existing Sessions
The following example enables you to clear your existing login sessions.
When you try to log in, the following message appears with all your existing concurrent sessions, providing an option to close any one of the
existing sessions:
$ telnet 10.11.178.14
Trying 10.11.178.14...
Connected to 10.11.178.14.
Escape character is '^]'.
Login: admin
Password:
Current sessions for user admin:
Line Location
2 vty 0 10.14.1.97
3 vty 1 10.14.1.97
Clear existing session? [line number/Enter to cancel]:
When you try to create more than the permitted number of sessions, the following message appears, prompting you to close one of the
existing sessions. If you close any of the existing sessions, you are allowed to login.
$ telnet 10.11.178.17
Trying 10.11.178.17...
Connected to 10.11.178.17.
Escape character is '^]'.
Login: admin
Password:
Maximum concurrent sessions for the user reached.
Current sessions for user admin:
Line Location
2 vty 0 10.14.1.97
3 vty 1 10.14.1.97
4 vty 2 10.14.1.97
5 vty 3 10.14.1.97
Kill existing session? [line number/Enter to cancel]:
Management
69
Enabling Secured CLI Mode
The secured CLI mode prevents the users from enhancing the permissions or promoting the privilege levels.
•Enter the following command to enable the secured CLI mode:
CONFIGURATION Mode
secure-cli enable
After entering the command, save the running-conguration. Once you save the running-conguration, the secured CLI mode is enabled.
If you do not want to enter the secured mode, do not save the running-conguration. Once saved, to disable the secured CLI mode, you
need to manually edit the startup-congurationle and reboot the system.
Changing System Logging Settings
You can change the default settings of the system logging by changing the severity level and the storage location.
The default is to log all messages up to debug level, that is, all system messages. By changing the severity level in the logging commands,
you control the number of system messages logged.
To specify the system logging settings, use the following commands.
•Specify the minimum severity level for logging to the logging buer.
CONFIGURATION mode
logging buffered level
•Specify the minimum severity level for logging to the console.
CONFIGURATION mode
logging console level
•Specify the minimum severity level for logging to terminal lines.
CONFIGURATION mode
logging monitor level
•Specify the minimum severity level for logging to a syslog server.
CONFIGURATION mode
logging trap level
•Specify the minimum severity level for logging to the syslog history table.
CONFIGURATION mode
logging history level
•Specify the size of the logging buer.
CONFIGURATION mode
logging buffered size
: When you decrease the buer size, Dell EMC Networking OS deletes all messages stored in the buer. Increasing the
NOTE
buer size does not aect messages in the buer.
•Specify the number of messages that Dell EMC Networking OS saves to its logging history table.
CONFIGURATION mode
logging history size size
Management
70
To view the logging buer and conguration, use the show logging command in EXEC privilege mode, as shown in the example for
Display the Logging Buer and the Logging Conguration.
To view the logging conguration, use the show running-config logging command in privilege mode, as shown in the example for
Congure a UNIX Logging Facility Level.
Display the Logging Buer and the Logging
Conguration
To display the current contents of the logging buer and the logging settings for the system, use the show logging command in EXEC
privilege mode. When RBAC is enabled, the security logs are ltered based on the user roles. Only the security administrator and system
administrator can view the security logs.
Example of the show logging Command
DellEMC#show logging
syslog logging: enabled
Console logging: level Debugging
Monitor logging: level Debugging
Buffer logging: level Debugging, 40 Messages Logged, Size (40960 bytes)
Trap logging: level Informational
%IRC-6-IRC_COMMUP: Link to peer RPM is up
%RAM-6-RAM_TASK: RPM1 is transitioning to Primary RPM.
%RPM-2-MSG:CP1 %POLLMGR-2-MMC_STATE: External flash disk missing in 'slot0:'
%CHMGR-5-CARDDETECTED: Line card 0 present
%CHMGR-5-CARDDETECTED: Line card 2 present
%CHMGR-5-CARDDETECTED: Line card 4 present
%CHMGR-5-CARDDETECTED: Line card 5 present
%CHMGR-5-CARDDETECTED: Line card 8 present
%CHMGR-5-CARDDETECTED: Line card 10 present
%CHMGR-5-CARDDETECTED: Line card 12 present
%TSM-6-SFM_DISCOVERY: Found SFM 0
%TSM-6-SFM_DISCOVERY: Found SFM 1
%TSM-6-SFM_DISCOVERY: Found SFM 2
%TSM-6-SFM_DISCOVERY: Found SFM 3
%TSM-6-SFM_DISCOVERY: Found SFM 4
%TSM-6-SFM_DISCOVERY: Found SFM 5
%TSM-6-SFM_DISCOVERY: Found SFM 6
%TSM-6-SFM_DISCOVERY: Found SFM 7
%TSM-6-SFM_SWITCHFAB_STATE: Switch Fabric: UP
%TSM-6-SFM_DISCOVERY: Found SFM 8
%TSM-6-SFM_DISCOVERY: Found 9 SFMs
%CHMGR-5-CHECKIN: Checkin from line card 5 (type EX1YB, 1 ports)
%TSM-6-PORT_CONFIG: Port link status for LC 5 => portpipe 0: OK portpipe 1: N/A
%CHMGR-5-LINECARDUP: Line card 5 is up
%CHMGR-5-CHECKIN: Checkin from line card 12 (type S12YC12, 12 ports)
%TSM-6-PORT_CONFIG: Port link status for LC 12 => portpipe 0: OK portpipe 1: N/A
%CHMGR-5-LINECARDUP: Line card 12 is up
%IFMGR-5-CSTATE_UP: changed interface Physical state to up: So 12/8
%IFMGR-5-CSTATE_DN: changed interface Physical state to down: So 12/8
To view any changes made, use the show running-config logging command in EXEC privilege mode.
Conguring a UNIX Logging Facility Level
You can save system log messages with a UNIX system logging facility.
To congure a UNIX logging facility level, use the following command.
•Specify one of the following parameters.
CONFIGURATION mode
logging facility [facility-type]
Management
71
– auth (for authorization messages)
– cron (for system scheduler messages)
– daemon (for system daemons)
– kern (for kernel messages)
– local0 (for local use)
– local1 (for local use)
– local2 (for local use)
– local3 (for local use)
– local4 (for local use)
– local5 (for local use)
– local6 (for local use)
– local7 (for local use)
– lpr (for line printer system messages)
– mail (for mail system messages)
– news (for USENET news messages)
– sys9 (system use)
– sys10 (system use)
– sys11 (system use)
– sys12 (system use)
– sys13 (system use)
– sys14 (system use)
– syslog (for syslog messages)
– user (for user programs)
– uucp (UNIX to UNIX copy protocol)
Example of the show running-config logging Command
To view nondefault settings, use the show running-config logging command in EXEC mode.
You can congure Dell EMC Networking OS to lter and consolidate the system messages for a specic line by synchronizing the message
output.
Only the messages with a severity at or below the set level appear. This feature works on the terminal and console connections available on
the system.
1 Enter LINE mode.
CONFIGURATION mode
line {console 0 | vty number [end-number] | aux 0}
Congure the following parameters for the virtual terminal lines:
Management
72
•number: the range is from zero (0) to 8.
•end-number: the range is from 1 to 8.
You can congure multiple virtual terminals at one time by entering a number and an end-number.
2 Congure a level and set the maximum number of messages to print.
•level severity-level: the range is from 0 to 7. The default is 2. Use the all keyword to include all messages.
•limit: the range is from 20 to 300. The default is 20.
To view the logging synchronous conguration, use the show config command in LINE mode.
Enabling Timestamp on Syslog Messages
By default, syslog messages include a time/date stamp, taken from the datetime, stating when the error or message was created.
To enable timestamp, use the following command.
•Add timestamp to syslog messages.
CONFIGURATION mode
– localtime: You can add the keyword localtime to include the localtime, msec, and show-timezone. If you do not add
the keyword
– uptime: To view time since last boot.
– datetime: To view the current date and time from the system BIOS.
If you do not specify a parameter, Dell EMC Networking OS conguresdatetime by default.
To view the conguration, use the show running-config logging command in EXEC privilege mode.
To disable time stamping on syslog messages, use the no service timestamps [log | debug] command.
localtime, the time is UTC.
File Transfer Services
With Dell EMC Networking OS, you can congure the system to transfer les over the network using the le transfer protocol (FTP).
One FTP application is copying the system image les over an interface on to the system; however, FTP is not supported on virtual local
area network (VLAN) interfaces.
If you want the FTP or TFTP server to use a VRF table that is attached to an interface, you must congure the FTP or TFTP server to use
a specic routing table. You can use the ip ftp vrf vrf-name or ip tftp vrf vrf-name command to inform the FTP or TFTP
server to use a specic routing table. After you congure this setting, the VRF table is used to look up the destination address. However,
these changes are backward-compatible and do not aect existing behavior; meaning, you can still use the source-interface
command to communicate with a particular interface even if no VRF is congured on that interface.
For more information about FTP, refer to RFC 959, File Transfer Protocol.
NOTE
: To transmit large les, Dell EMC Networking recommends conguring the switch as an FTP server.
Management73
Conguration Task List for File Transfer Services
The conguration tasks for le transfer services are:
•Enable FTP Server (mandatory)
•Congure FTP Server Parameters (optional)
•Congure FTP Client Parameters (optional)
Enabling the FTP Server
To enable the system as an FTP server, use the following command.
To view FTP conguration, use the show running-config ftp command in EXEC privilege mode.
After you enable the FTP server on the system, you can conguredierent parameters.
To specify the system logging settings, use the following commands.
•Specify the directory for users using FTP to reach the system.
CONFIGURATION mode
ftp-server topdir dir
The default is the internal ash directory.
•Specify a user name for all FTP users and congure either a plain text or encrypted password.
CONFIGURATION mode
Congure the following optional and required parameters:
– username: enter a text string.
– encryption-type: enter 0 for plain text or 7 for encrypted text.
– password: enter a text string.
: You cannot use the change directory (cd) command until you have congured ftp-server topdir.
NOTE
To view the FTP conguration, use the show running-config ftp command in EXEC privilege mode.
Management
74
Conguring FTP Client Parameters
To congure FTP client parameters, use the following commands.
•Enter the following keywords and the interface information:
– For a 10-Gigabit Ethernet interface, enter the keyword TenGigabitEthernet then the slot/port/subport information.
– For a 40-Gigabit Ethernet interface, enter the keyword fortyGigE then the slot/port information.
– For a Loopback interface, enter the keyword loopback then a number from 0 to 16383.
– For a port channel interface, enter the keywords port-channel then a number.
– For a VLAN interface, enter the keyword vlan then a number from 1 to 4094.
CONFIGURATION mode
ip ftp source-interface interface
•Congure a password.
CONFIGURATION mode
ip ftp password password
•Enter a username to use on the FTP client.
CONFIGURATION mode
ip ftp username name
To view the FTP conguration, use the show running-config ftp command in EXEC privilege mode, as shown in the example for
Enable FTP Server.
Terminal Lines
You can access the system remotely and restrict access to the system by creating user proles.
Terminal lines on the system provide dierent means of accessing the system. The console line (console) connects you through the console
port in the route processor modules (RPMs). The virtual terminal lines (VTYs) connect you through Telnet to the system. The auxiliary line
(aux) connects secondary devices such as modems.
Denying and Permitting Access to a Terminal Line
Dell EMC Networking recommends applying only standard access control lists (ACLs) to deny and permit access to VTY lines.
•Layer 3 ACLs deny all trac that is not explicitly permitted, but in the case of VTY lines, an ACL with no rules does not deny trac.
•You cannot use the show ip accounting access-list command to display the contents of an ACL that is applied only to a
VTY line.
•When you use the access-class access-list-name command without specifying the ipv4 or ipv6 attribute, both IPv4 as
well as IPv6 rules that are dened in that ACL are applied to the terminal. This method is a generic way of conguring access
restrictions.
•To be able to lter access exclusively using either IPv4 or IPv6 rules, use either the ipv4 or ipv6 attribute along with the access-class access-list-name command. Depending on the attribute that you specify (ipv4 or ipv6), the ACL processes either
IPv4 or IPv6 rules, but not both. Using this conguration, you can set up two dierent types of access classes with each class
processing either IPv4 or IPv6 rules separately.
To apply an IP ACL to a line, Use the following command.
•Apply an ACL to a VTY line.
LINE mode
Management
75
access-class access-list-name [ipv4 | ipv6]
NOTE: If you already have congured generic IP ACL on a terminal line, then you cannot further apply IPv4 or IPv6 specic
ltering on top of this conguration. Similarly, if you have congured either IPv4 or IPv6 specic ltering on a terminal line,
you cannot apply generic IP ACL on top of this conguration. Before applying any of these congurations, you must rst undo
the existing conguration using the no access-class access-list-name [ipv4 | ipv6] command.
Example of an ACL that Permits Terminal Access
Example Conguration
To view the conguration, use the show config command in LINE mode.
DellEMC(config-std-nacl)#show config
!
ip access-list standard myvtyacl
seq 5 permit host 10.11.0.1
DellEMC(config-std-nacl)#line vty 0
DellEMC(config-line-vty)#show config
line vty 0
access-class myvtyacl
DellEMC(conf-ipv6-acl)#do show run acl
!
ip access-list extended testdeny
seq 10 deny ip 30.1.1.0/24 any
seq 15 permit ip any any
!
ip access-list extended testpermit
seq 15 permit ip any any
!
ipv6 access-list testv6deny
seq 10 deny ipv6 3001::/64 any
seq 15 permit ipv6 any any
!
DellEMC(conf)#
DellEMC(conf)#line vty 0 0
DellEMC(config-line-vty)#access-class testv6deny ipv6
DellEMC(config-line-vty)#access-class testvpermit ipv4
DellEMC(config-line-vty)#show c
line vty 0
exec-timeout 0 0
access-class testpermit ipv4
access-class testv6deny ipv6
!
Conguring Login Authentication for Terminal Lines
You can use any combination of up to six authentication methods to authenticate a user on a terminal line.
A combination of authentication methods is called a method list. If the user fails the rst authentication method, Dell EMC Networking OS
prompts the next method until all methods are exhausted, at which point the connection is terminated. The available authentication
methods are:
enable
line
local
none
radius
76Management
Prompt for the enable password.
Prompt for the password you assigned to the terminal line. Congure a password for the terminal line to which you
assign a method list that contains the line authentication method. Congure a password using the password
command from LINE mode.
Prompt for the system username and password.
Do not authenticate the user.
Prompt for a username and password and use a RADIUS server to authenticate.
tacacs+
1 Congure an authentication method list. You may use a mnemonic name or use the keyword default. The default authentication
method for terminal lines is local and the default method list is empty.
CONFIGURATION mode
Prompt for a username and password and use a TACACS+ server to authenticate.
Setting Timeout for EXEC Privilege Mode
EXEC timeout is a basic security feature that returns Dell EMC Networking OS to EXEC mode after a period of inactivity on the terminal
lines.
To set timeout, use the following commands.
•Set the number of minutes and seconds. The default is 10 minutes on the console and 30 minutes on VTY. Disable EXEC time out
by setting the timeout period to 0.
LINE mode
exec-timeout minutes [seconds]
•Return to the default timeout values.
LINE mode
no exec-timeout
Example of Setting the Timeout Period for EXEC Privilege Mode
The following example shows how to set the timeout period and how to view the conguration using the show config command from
LINE mode.
DellEMC(conf)#line con 0
DellEMC(config-line-console)#exec-timeout 0
DellEMC(config-line-console)#show config
Management
77
line console 0
exec-timeout 0 0
DellEMC(config-line-console)#
Using Telnet to get to Another Network Device
To telnet to another device, use the following commands.
NOTE: The device allows 120 Telnet sessions per minute, allowing the login and logout of 10 Telnet sessions, 12 times in a minute.
If the system reaches this non-practical limit, the Telnet service is stopped for 10 minutes. You can use console and SSH service
to access the system during downtime.
•Telnet to a device with an IPv4 or IPv6 address.
EXEC Privilege
telnet [ip-address]
If you do not enter an IP address, Dell EMC Networking OS enters a Telnet dialog that prompts you for one.
Enter an IPv4 address in dotted decimal format (A.B.C.D).
Enter an IPv6 address in the format 0000:0000:0000:0000:0000:0000:0000:0000. Elision of zeros is supported.
Example of the telnet Command for Device Access
DellEMC# telnet 10.11.80.203
Trying 10.11.80.203...
Connected to 10.11.80.203.
Exit character is '^]'.
Login:
Login: admin
Password:
DellEMC>exit
DellEMC#telnet 2200:2200:2200:2200:2200::2201
Trying 2200:2200:2200:2200:2200::2201...
Connected to 2200:2200:2200:2200:2200::2201.
Exit character is '^]'.
FreeBSD/i386 (freebsd2.force10networks.com) (ttyp1)
login: admin
DellEMC#
Lock CONFIGURATION Mode
Dell EMC Networking OS allows multiple users to make congurations at the same time. You can lock CONFIGURATION mode so that only
one user can be in CONFIGURATION mode at any time (Message 2).
You can set two types of lockst: auto and manual.
•Set auto-lock using the configuration mode exclusive auto command from CONFIGURATION mode. When you set autolock, every time a user is in CONFIGURATION mode, all other users are denied access. This means that you can exit to EXEC Privilege
mode, and re-enter CONFIGURATION mode without having to set the lock again.
•Set manual lock using the configure terminal lock command from CONFIGURATION mode. When you congure a manual
lock, which is the default, you must enter this command each time you want to enter CONFIGURATION mode and deny access to
others.
Viewing the Conguration Lock Status
If you attempt to enter CONFIGURATION mode when another user has locked it, you may view which user has control of
CONFIGURATION mode using the show configuration lock command from EXEC Privilege mode.
Management
78
You can then send any user a message using the send command from EXEC Privilege mode. Alternatively, you can clear any line using the
clear command from EXEC Privilege mode. If you clear a console session, the user is returned to EXEC mode.
Example of Locking CONFIGURATION Mode for Single-User Access
DellEMC(conf)#configuration mode exclusive auto
BATMAN(conf)#exit
3d23h35m: %RPM0-P:CP %SYS-5-CONFIG_I: Configured from console by console
If another user attempts to enter CONFIGURATION mode while a lock is in place, the following appears on their terminal (message 1): %
Error: User "" on line console0 is in exclusive configuration mode
If any user is already in CONFIGURATION mode when while a lock is in place, the following appears on their terminal (message 2): %
Error: Can't lock configuration mode exclusively since the following users are currently
configuring the system: User "admin" on line vty1 ( 10.1.1.1 ).
NOTE: The CONFIGURATION mode lock corresponds to a VTY session, not a user. Therefore, if you congure a lock and then
exit CONFIGURATION mode, and another user enters CONFIGURATION mode, when you attempt to re-enter CONFIGURATION
mode, you are denied access even though you are the one that congured the lock.
NOTE: If your session times out and you return to EXEC mode, the CONFIGURATION mode lock is uncongured.
.
Restoring the Factory Default Settings
Restoring the factory-default settings deletes the existing NVRAM settings, startup conguration, and all congured settings such as,
stacking or fanout.
To restore the factory default settings, use the restore factory-defaults stack-unit {stack—unit—number | all}
{clear-all | nvram | bootvar}
CAUTION
: There is no undo for this command.
command in EXEC Privilege mode.
Important Points to Remember
•When you restore all the units in a stack, these units are placed in standalone mode.
•When you restore a single unit in a stack, only that unit is placed in standalone mode. No other units in the stack are aected.
•When you restore the units in standalone mode, the units remain in standalone mode after the restoration.
•After the restore is complete, the units power cycle immediately.
The following example illustrates the restore factory-defaults command to restore the factory default settings.
***********************************************************************
* Warning - Restoring factory defaults will delete the existing *
* persistent settings (stacking, fanout, etc.) *
* After restoration the unit(s) will be powercycled immediately. *
* Proceed with caution ! *
***********************************************************************
Proceed with factory settings? Confirm [yes/no]:yes
-- Restore status --
Unit Nvram Config
------------------------
1 Success
Management
79
Power-cycling the unit(s).
....
Restoring Factory Default Environment Variables
The Boot line determines the location of the image that is used to boot up the chassis after restoring factory default settings. Ideally, these
locations contain valid images, using which the chassis boots up.
When you restore factory-default settings, you can either use a ash boot procedure or a network boot procedure to boot the switch.
When you use the ash boot procedure to boot the device, the boot loader checks if the primary or the secondary partition contains a valid
image. If the primary partition contains a valid image, then the primary boot line is set to A: and the secondary and default boot lines are set
to a Null String. If the secondary partition contains a valid image, then the primary boot line is set to B: and the secondary and default boot
lines are set to a Null String. If both the partitions contain invalid images, then primary, secondary, and default boot line values are set to a
Null string.
When you use the Network boot procedure to boot the device, the boot loader checks if the primary partition contains a valid image. If a
valid image exists on the primary partition and the secondary partition does not contain a valid image, then the primary boot line is set to A:
and the secondary and default boot lines are set to a Null string. If the secondary partition also contains a valid image, then the primary
boot line value is set to the partition that is congured to be used to boot the device in a network failure scenario. The secondary and
default boot line values are set to a Null string.
Important Points to Remember
•The Chassis remains in boot prompt if none of the partitions contain valid images.
•To enable TFTP boot after restoring factory default settings, you must stop the boot process in BLI.
In case the system fails to reload the image from the partition, perform the following steps:
1Power-cycle the chassis (pull the power cord and reinsert it).
2Press esc key to abort the boot process (while the system prompts to)
You enter BLI immediately, as indicated by the BOOT_USER # prompt.
press any key
3Assign the new location of the Dell EMC Networking OS image to be used when the system reloads.
To boot from ash partition A:
BOOT_USER # boot change primary
boot device : flash
file name : systema
BOOT_USER #
To boot from ash partition B:
BOOT_USER # boot change primary
boot device : flash
Management
80
file name : systemb
BOOT_USER #
To boot from network:
BOOT_USER # boot change primary
boot device : tftp
file name : FTOS-S6010-9.10.0.1.bin
Server IP address : 10.16.127.35
BOOT_USER #
4Assign an IP address and netmask to the Management Ethernet interface.
BOOT_USER # interface management ethernet ip address ip_address_with_mask
For example, 10.16.150.106/16.
5Assign an IP address as the default gateway for the system.
default-gateway gateway_ip_address
For example, 10.16.150.254.
6The environment variables are auto saved.
7Reload the system.
BOOT_USER # reload
Viewing the Reason for Last System Reboot
You can view the reason for the last system reboot. To view the reason for the last system reboot, follow this procedure:
•Use the following command to view the reason for the last system reboot:
EXEC or EXEC Privilege mode
show reset-reason [stack-unit {unit-number | all}]
Enter the stack-unit keyword and the stack unit number to view the reason for the last system reboot for that stack unit.
Enter the stack-unit keyword and the keyword all to view the reason for the last system reboot of all stack units in the stack.
DellEMC#show reset-reason
Cause : Reset by User through CLI command
Reset Time: 11/05/2017-08:36
DellEMC# show reset-reason stack-unit 1
Cause : Reset by User through CLI command
Reset Time: 11/05/2017-08:36
Management
81
5
802.1X
802.1X is a port-based Network Access Control (PNAC) that provides an authentication mechanism to devices wishing to attach to a LAN
or WLAN. A device connected to a port that is enabled with 802.1X is disallowed from sending or receiving packets on the network until its
identity is veried (through a username and password, for example).
802.1X employs Extensible Authentication Protocol (EAP) to transfer a device’s credentials to an authentication server (typically RADIUS)
using a mandatory intermediary network access device, in this case, a Dell EMC Networking switch. The network access device mediates
all communication between the end-user device and the authentication server so that the network remains secure. The network access
device uses EAP-over-Ethernet (EAPOL) to communicate with the end-user device and EAP-over-RADIUS to communicate with the
server.
NOTE: The Dell EMC Networking Operating System (OS) supports 802.1X with EAP-MD5, EAP-OTP, EAP-TLS, EAP-TTLS,
PEAPv0, PEAPv1, and MS-CHAPv2 with PEAP.
The following gures show how the EAP frames are encapsulated in Ethernet and RADIUS frames.
Figure 3. EAP Frames Encapsulated in Ethernet and RADUIS
82802.1X
Figure 4. EAP Frames Encapsulated in Ethernet and RADUIS
The authentication process involves three devices:
•The device attempting to access the network is the supplicant. The supplicant is not allowed to communicate on the network until the
authenticator authorizes the port. It can only communicate with the authenticator in response to 802.1X requests.
•The device with which the supplicant communicates is the authenticator. The authenticator is the gate keeper of the network. It
translates and forwards requests and responses between the authentication server and the supplicant. The authenticator also changes
the status of the port based on the results of the authentication process. The Dell EMC Networking switch is the authenticator.
•The authentication-server selects the authentication method, veries the information the supplicant provides, and grants it network
access privileges.
Ports can be in one of two states:
•Ports are in an unauthorized state by default. In this state, non-802.1X trac cannot be forwarded in or out of the port.
•The authenticator changes the port state to authorized if the server can authenticate the supplicant. In this state, network trac can
be forwarded normally.
: The Dell EMC Networking switches place 802.1X-enabled ports in the unauthorized state by default.
NOTE
Topics:
•Port-Authentication Process
•Conguring 802.1X
•Important Points to Remember
•Enabling 802.1X
•Conguring Request Identity Re-Transmissions
•Forcibly Authorizing or Unauthorizing a Port
•Re-Authenticating a Port
•Conguring Timeouts
•Conguring Dynamic VLAN Assignment with Port Authentication
•Guest and Authentication-Fail VLANs
802.1X
83
Port-Authentication Process
The authentication process begins when the authenticator senses that a link status has changed from down to up:
1When the authenticator senses a link state change, it requests that the supplicant identify itself using an EAP Identity Request frame.
2The supplicant responds with its identity in an EAP Response Identity frame.
3The authenticator decapsulates the EAP response from the EAPOL frame, encapsulates it in a RADIUS Access-Request frame and
forwards the frame to the authentication server.
4The authentication server replies with an Access-Challenge frame. The Access-Challenge frame requests the supplicant to prove that
it is who it claims to be, using a specied method (an EAP-Method). The challenge is translated and forwarded to the supplicant by
the authenticator.
5The supplicant can negotiate the authentication method, but if it is acceptable, the supplicant provides the Requested Challenge
information in an EAP response, which is translated and forwarded to the authentication server as another Access-Request frame.
6If the identity information provided by the supplicant is valid, the authentication server sends an Access-Accept frame in which
network privileges are specied. The authenticator changes the port state to authorized and forwards an EAP Success frame. If the
identity information is invalid, the server sends an Access-Reject frame. If the port state remains unauthorized, the authenticator
forwards an EAP Failure frame.
Figure 5. EAP Port-Authentication
EAP over RADIUS
802.1X uses RADIUS to shuttle EAP packets between the authenticator and the authentication server, as dened in RFC 3579.
EAP messages are encapsulated in RADIUS packets as a type of attribute in Type, Length, Value (TLV) format. The Type value for EAP
messages is 79.
802.1X
84
Figure 6. EAP Over RADIUS
RADIUS Attributes for 802.1X Support
Dell EMC Networking systems include the following RADIUS attributes in all 802.1X-triggered Access-Request messages:
Attribute 31Calling-station-id: relays the supplicant MAC address to the authentication server.
Attribute 41NAS-Port-Type: NAS-port physical port type. 15 indicates Ethernet.
Attribute 61NAS-Port: the physical port number by which the authenticator is connected to the supplicant.
Attribute 81Tunnel-Private-Group-ID: associate a tunneled session with a particular group of users.
Conguring 802.1X
Conguring 802.1X on a port is a one-step process.
For more information, refer to Enabling 802.1X.
Related Conguration Tasks
•Conguring Request Identity Re-Transmissions
•Forcibly Authorizing or Unauthorizing a Port
•Re-Authenticating a Port
•Conguring Timeouts
•Conguring a Guest VLAN
•Conguring an Authentication-Fail VLAN
Important Points to Remember
•Dell EMC Networking OS supports 802.1X with EAP-MD5, EAP-OTP, EAP-TLS, EAP-TTLS, PEAPv0, PEAPv1, and MS-CHAPv2 with
PEAP.
•All platforms support only RADIUS as the authentication server.
•If the primary RADIUS server becomes unresponsive, the authenticator begins using a secondary RADIUS server, if congured.
•802.1X is not supported on port-channels or port-channel members.
•The NAS-Port-Type attribute indicates the type of the physical port of the NAS which is authenticating the user. It is used in AccessRequest packets. The value of this attribute is set as Ethernet (15) for both EAP and MAB supplicants.
802.1X
85
Enabling 802.1X
Enable 802.1X globally.
Figure 7. 802.1X Enabled
1 Enable 802.1X globally.
CONFIGURATION mode
dot1x authentication
2 Enter INTERFACE mode on an interface or a range of interfaces.
INTERFACE mode
interface [range]
3 Enable 802.1X on the supplicant interface only.
INTERFACE mode
dot1x authentication
Examples of Verifying that 802.1X is Enabled Globally and on an Interface
Verify that 802.1X is enabled globally and at the interface level using the show running-config | find dot1x command from
EXEC Privilege mode.
802.1X
86
In the following example, the bold lines show that 802.1X is enabled.
DellEMC#show running-config | find dot1x
dot1x authentication
!
[output omitted]
!
interface TenGigabitEthernet 2/1/1
no ip address
dot1x authentication
no shutdown
!
DellEMC#
To view 802.1X conguration information for an interface, use the show dot1x interface command.
In the following example, the bold lines show that 802.1X is enabled on all ports unauthorized by default.
When the authenticator sends a Request Identity frame and the supplicant does not respond, the authenticator waits for 30 seconds and
then re-transmits the frame.
The amount of time that the authenticator waits before re-transmitting and the maximum number of times that the authenticator retransmits can be congured.
: There are several reasons why the supplicant might fail to respond; for example, the supplicant might have been booting
NOTE
when the request arrived or there might be a physical layer problem.
To congure re-transmissions, use the following commands.
•Congure the amount of time that the authenticator waits before re-transmitting an EAP Request Identity frame.
INTERFACE mode
dot1x tx-period number
The range is from 1 to 65535 (1 year)
The default is 30.
802.1X
87
•Congure the maximum number of times the authenticator re-transmits a Request Identity frame.
INTERFACE mode
dot1x max-eap-req number
The range is from 1 to 10.
The default is 2.
The example in Conguring a Quiet Period after a Failed Authentication shows conguration information for a port for which the
authenticator re-transmits an EAP Request Identity frame after 90 seconds and re-transmits for 10 times.
Conguring a Quiet Period after a Failed Authentication
If the supplicant fails the authentication process, the authenticator sends another Request Identity frame after 30 seconds by default. You
can congure this period.
NOTE: The quiet period (dot1x quiet-period) is the transmit interval after a failed authentication; the Request Identity Re-
transmit interval (dot1x tx-period) is for an unresponsive supplicant.
To congure a quiet period, use the following command.
•Congure the amount of time that the authenticator waits to re-transmit a Request Identity frame after a failed authentication.
INTERFACE mode
dot1x quiet-period seconds
The range is from 1 to 65535.
The default is 60 seconds.
Example of Conguring and Verifying Port Authentication
The following example shows conguration information for a port for which the authenticator re-transmits an EAP Request Identity frame:
•after 90 seconds and a maximum of 10 times for an unresponsive supplicant
•re-transmits an EAP Request Identity frame
The bold lines show the new re-transmit interval, new quiet period, and new maximum re-transmissions.
The 802.1X ports can be placed into any of the three states:
•ForceAuthorized — an authorized state. A device connected to this port in this state is never subjected to the authentication process,
but is allowed to communicate on the network. Placing the port in this state is same as disabling 802.1X on the port.
•ForceUnauthorized — an unauthorized state. A device connected to a port in this state is never subjected to the authentication
process and is not allowed to communicate on the network. Placing the port in this state is the same as shutting down the port. Any
attempt by the supplicant to initiate authentication is ignored.
•Auto — an unauthorized state by default. A device connected to this port in this state is subjected to the authentication process. If the
process is successful, the port is authorized and the connected device can communicate on the network. All ports are placed in the
Auto state by default.
To set the port state, use the following command.
•Place a port in the ForceAuthorized, ForceUnauthorized, or Auto state.
INTERFACE mode
You can congure the authenticator for periodic re-authentication.
After the supplicant has been authenticated, and the port has been authorized, you can congure the authenticator to re-authenticate the
supplicant periodically. If you enable re-authentication, the supplicant is required to re-authenticate every 3600 seconds by default, and you
can congure this interval. You can congure the maximum number of re-authentications as well.
To congure re-authentication time settings, use the following commands:
•Congure the authenticator to periodically re-authenticate the supplicant.
INTERFACE mode
802.1X
89
dot1x reauthentication [interval] seconds
The range is from 1 to 31536000.
The default is 3600.
•Congure the maximum number of times the supplicant can be re-authenticated.
INTERFACE mode
dot1x reauth-max number
The range is from 1 to 10.
The default is 2.
Example of Re-Authenticating a Port and Verifying the Conguration
The bold lines show that re-authentication is enabled and the new maximum and re-authentication time period.
If the supplicant or the authentication server is unresponsive, the authenticator terminates the authentication process after 30 seconds by
default. You can congure the amount of time the authenticator waits for a response.
To terminate the authentication process, use the following commands:
•Terminate the authentication process due to an unresponsive supplicant.
INTERFACE mode
dot1x supplicant-timeout seconds
The range is from 1 to 300.
The default is 30.
•Terminate the authentication process due to an unresponsive authentication server.
INTERFACE mode
dot1x server-timeout seconds
The range is from 1 to 300.
802.1X
90
The default is 30.
Example of Viewing Congured Server Timeouts
The example shows conguration information for a port for which the authenticator terminates the authentication process for an
unresponsive supplicant or server after 15 seconds.
The bold lines show the new supplicant and server timeouts.
DellEMC(conf-if-Te-1/1/1)#dot1x port-control force-authorized
DellEMC(conf-if-Te-1/1/1)#do show dot1x interface TenGigabitEthernet 1/1/1
Enter the tasks the user should do after nishing this task (optional).
Conguring Dynamic VLAN Assignment with Port
Authentication
Dell EMC Networking OS supports dynamic VLAN assignment when using 802.1X.
The basis for VLAN assignment is RADIUS attribute 81, Tunnel-Private-Group-ID. Dynamic VLAN assignment uses the standard dot1x
procedure:
1The host sends a dot1x packet to the Dell EMC Networking system
2The system forwards a RADIUS REQEST packet containing the host MAC address and ingress port number
3The RADIUS server authenticates the request and returns a RADIUS ACCEPT message with the VLAN assignment using Tunnel-
Private-Group-ID
The illustration shows the conguration on the Dell EMC Networking system before connecting the end user device in black and blue text,
and after connecting the device in red text. The blue text corresponds to the preceding numbered steps on dynamic VLAN assignment
with 802.1X.
802.1X
91
Figure 8. Dynamic VLAN Assignment
1 Congure 8021.x globally (refer to Enabling 802.1X) along with relevant RADIUS server congurations (refer to the illustration
inDynamic VLAN Assignment with Port Authentication).
2 Make the interface a switchport so that it can be assigned to a VLAN.
3 Create the VLAN to which the interface will be assigned.
4 Connect the supplicant to the port congured for 802.1X.
5 Verify that the port has been authorized and placed in the desired VLAN (refer to the illustration in Dynamic VLAN Assignment with
Port Authentication).
Guest and Authentication-Fail VLANs
Typically, the authenticator (the Dell system) denies the supplicant access to the network until the supplicant is authenticated. If the
supplicant is authenticated, the authenticator enables the port and places it in either the VLAN for which the port is congured or the
VLAN that the authentication server indicates in the authentication data.
NOTE
: Ports cannot be dynamically assigned to the default VLAN.
If the supplicant fails authentication, the authenticator typically does not enable the port. In some cases this behavior is not appropriate.
External users of an enterprise network, for example, might not be able to be authenticated, but still need access to the network. Also,
some dumb-terminals, such as network printers, do not have 802.1X capability and therefore cannot authenticate themselves. To be able to
connect such devices, they must be allowed access the network without compromising network security.
92
802.1X
The Guest VLAN 802.1X extension addresses this limitation with regard to non-802.1X capable devices and the Authentication-fail VLAN
802.1X extension addresses this limitation with regard to external users.
•If the supplicant fails authentication a specied number of times, the authenticator places the port in the Authentication-fail VLAN.
•If a port is already forwarding on the Guest VLAN when 802.1X is enabled, the port is moved out of the Guest VLAN and the
authentication process begins.
Conguring a Guest VLAN
If the supplicant does not respond within a determined amount of time ([reauth-max + 1] * tx-period, the system assumes that the host
does not have 802.1X capability and the port is placed in the Guest VLAN.
NOTE: For more information about conguring timeouts, refer to Conguring Timeouts.
Congure a port to be placed in the Guest VLAN after failing to respond within the timeout period using the dot1x guest-vlan
command from INTERFACE mode. View your conguration using the show config command from INTERFACE mode or using the show dot1x interface command from EXEC Privilege mode.
If the supplicant fails authentication, the authenticator re-attempts to authenticate after a specied amount of time.
NOTE
: For more information about authenticator re-attempts, refer to Conguring a Quiet Period after a Failed Authentication.
You can congure the maximum number of times the authenticator re-attempts authentication after a failure (3 by default), after which the
port is placed in the Authentication-fail VLAN.
Congure a port to be placed in the VLAN after failing the authentication process as specied number of times using the dot1x auth-
fail-vlan
the keyword max-attempts with this command.
Example of Conguring Maximum Authentication Attempts
This chapter describes access control lists (ACLs), prex lists, and route-maps.
At their simplest, access control lists (ACLs), prex lists, and route-maps permit or deny trac based on MAC and/or IP addresses. This
chapter describes implementing IP ACLs, IP prex lists and route-maps. For MAC ACLS, refer to Layer 2.
An ACL is essentially a lter containing some criteria to match (examine IP, transmission control protocol [TCP], or user datagram protocol
[UDP] packets) and an action to take (permit or deny). ACLs are processed in sequence so that if a packet does not match the criterion in
the rstlter, the second lter (if congured) is applied. When a packet matches a lter, the switch drops or forwards the packet based on
the lter’sspecied action. If the packet does not match any of the lters in the ACL, the packet is dropped (implicit deny).
The number of ACLs supported on a system depends on your content addressable memory (CAM) size. For more information, refer to User
Congurable CAM Allocation and CAM Optimization. For complete CAM proling information, refer to Content Addressable Memory
(CAM).
You can congure ACLs on VRF instances. In addition to the existing qualifying parameters, Layer 3 ACLs also incorporate VRF ID as one of
the parameters. Using this new capability, you can also congure VRF based ACLs on interfaces.
: You can apply Layer 3 VRF-aware ACLs only at the ingress level.
NOTE
You can apply VRF-aware ACLs on:
•VRF Instances
•Interfaces
In order to congure VRF-aware ACLs on VRF instances, you must carve out a separate CAM region. You can use the cam-acl command
for allocating CAM regions. As part of the enhancements to support VRF-aware ACLs, the cam-acl command now includes the following
new parameter that enables you to allocate a CAM region:
The order of priority for conguringuser-dened ACL CAM regions is as follows:
•V4 ACL CAM
•VRF V4 ACL CAM
•L2 ACL CAM
With the inclusion of VRF based ACLs, the order of precedence of Layer 3 ACL rules is as follows:
•Port/VLAN based PERMIT/DENY Rules
•Port/VLAN based IMPLICIT DENY Rules
•VRF based PERMIT/DENY Rules
•VRF based IMPLICIT DENY Rules
NOTE
: In order for the VRF ACLs to take eect, ACLs congured in the Layer 3 CAM region must have an implicit-permit option.
You can use the ip access-group command to congure VRF-aware ACLs on interfaces. Using the ip access-group command, in
addition to a range of VLANs, you can also specify a range of VRFs as input for conguring ACLs on interfaces. The VRF range is from 1 to
63. These ACLs use the existing V4 ACL CAM region to populate the entries in the hardware and do not require you to carve out a separate
CAM region.
vrfv4acl.
NOTE
: You can congure VRF-aware ACLs on interfaces either using a range of VLANs or a range of VRFs but not both.
Access Control Lists (ACLs)95
Topics:
•IP Access Control Lists (ACLs)
•Important Points to Remember
•IP Fragment Handling
•Congure a Standard IP ACL
•Congure an Extended IP ACL
•Congure Layer 2 and Layer 3 ACLs
•Assign an IP ACL to an Interface
•Applying an IP ACL
•Congure Ingress ACLs
•Congure Egress ACLs
•IP Prex Lists
•ACL Remarks
•ACL Resequencing
•Route Maps
•Flow-Based Monitoring
•Conguring IP Mirror Access Group
IP Access Control Lists (ACLs)
In Dell EMC Networking switch/routers, you can create two dierent types of IP ACLs: standard or extended.
A standard ACL lters packets based on the source IP packet. An extended ACL lters trac based on the following criteria:
•IP protocol number
•Source IP address
•Destination IP address
•Source TCP port number
•Destination TCP port number
•Source UDP port number
•Destination UDP port number
For more information about ACL options, refer to the Dell EMC Networking OS Command Reference Guide.
For extended ACL, TCP, and UDP lters, you can match criteria on specic or ranges of TCP or UDP ports. For extended ACL TCP lters,
you can also match criteria on established TCP sessions.
When creating an access list, the sequence of the lters is important. You have a choice of assigning sequence numbers to the lters as
you enter them, or the Dell EMC Networking Operating System (OS) assigns numbers in the order the lters are created. The sequence
numbers are listed in the display output of the show config and show ip accounting access-list commands.
Ingress and egress Hot Lock ACLs allow you to append or delete new rules into an existing ACL (already written into CAM) without
disrupting tracow. Existing entries in the CAM are shued to accommodate the new entries. Hot lock ACLs are enabled by default and
support both standard and extended ACLs and on all platforms.
NOTE
: Hot lock ACLs are supported for Ingress ACLs only.
96Access Control Lists (ACLs)
CAM Usage
The following section describes CAM allocation and CAM optimization.
•User Congurable CAM Allocation
•CAM Optimization
User Congurable CAM Allocation
Allocate space for IPV6 ACLs by using the cam-acl command in CONFIGURATION mode.
The CAM space is allotted in lter processor (FP) blocks. The total space allocated must equal 13 FP blocks. (There are 16 FP blocks, but
System Flow requires three blocks that cannot be reallocated.)
Enter the ipv6acl allocation as a factor of 2 (2, 4, 6, 8, 10). All other prole allocations can use either even or odd numbered ranges.
If you want to congure ACL's on VRF instances, you must allocate a CAM region using the vrfv4acl option in the cam-acl command.
Save the new CAM settings to the startup-cong (use write-mem or copy run start) then reload the system for the new settings
to take eect.
CAM Optimization
When you enable this command, if a policy map containing classication rules (ACL and/or dscp/ ip-precedence rules) is applied to more
than one physical interface on the same port-pipe, only a single copy of the policy is written (only one FP entry is used). When you disable
this command, the system behaves as described in this chapter.
Test CAM Usage
This command applies to both IPv4 and IPv6 CAM proles, but is best used when verifying QoS optimization for IPv6 ACLs.
To determine whether sucient ACL CAM space is available to enable a service-policy, use this command. To verify the actual CAM space
required, create a class map with all the required ACL rules, then execute the test cam-usage command in Privilege mode. The
following example shows the output when executing this command. The status column indicates whether you can enable the policy.
You can assign one IP ACL per interface. If you do not assign an IP ACL to an interface, it is not used by the software.
The number of entries allowed per ACL is hardware-dependent.
Access Control Lists (ACLs)
97
If counters are enabled on ACL rules that are already congured, those counters are reset when a new rule which is inserted or prepended
or appended requires a hardware shift in the ow table. Resetting the counters to 0 is transient as the proginal counter values are retained
after a few seconds. If there is no need to shift the ow in the hardware, the counters are not aected. This is applicable to the following
features:
•L2 Ingress Access list
•L2 Egress Access list
In the Dell EMC Networking OS versions prior to 9.13(0.0), the system does not install any of your ACL rules if the available CAM space is
lesser than what is required for your set of ACL rules. Eective with the Dell EMC Networking OS version 9.13(0.0), the system installs your
ACL rules until all the allocated CAM memory is used. If there is no implicit permit in your rule, the Dell EMC Networking OS ensures that an
implicit deny is installed at the end of your rule. This behavior is applicable for IPv4 and IPv6 ingress and egress ACLs.
NOTE: System access lists (system-ow entries) are pre-programmed in the system for lifting the control-plane packets
destined for the local device which the CPU needs to process. The system access lists always override the user congured
access lists. Even if you congure ACL to block certain hosts, control plane protocols such as, ARP, BGP, LACP, VLT, VRRP and
so on, associated with such hosts cannot be blocked.
Assigning ACLs to VLANs
When you apply an ACL to a VLAN using single port-pipe, a copy of the ACL entries gets installed in the ACL CAM on the port-pipe. The
entry looks for the incoming VLAN in the packet. When you apply an ACL on individual ports of a VLAN, separate copies of the ACL entries
are installed for each port belonging to a port-pipe.
You can use the log keyword to log the details about the packets that match. The control processor becomes busy based on the number
of packets that match the log entry and the rate at which the details are logged in. However, the route processor (RP) is unaected. You
can use this option for debugging issues related to control trac.
ACL Optimization
If an access list contains duplicate entries, Dell EMC Networking OS deletes one entry to conserve CAM space.
Standard and extended ACLs take up the same amount of CAM space. A single ACL rule uses two CAM entries to identify whether the
access list is a standard or extended ACL.
Determine the Order in which ACLs are Used to Classify Trac
When you link class-maps to queues using the service-queue command, Dell EMC Networking OS matches the class-maps according
to queue priority (queue numbers closer to 0 have lower priorities).
As shown in the following example, class-map cmap2 is matched against ingress packets before cmap1.
ACLs acl1 and acl2 have overlapping rules because the address range 20.1.1.0/24 is within 20.0.0.0/8. Therefore (without the keyword
order), packets within the range 20.1.1.0/24 match positive against cmap1 and are buered in queue 7, though you intended for these
packets to match positive against
In cases where class-maps with overlapping ACL rules are applied to dierent queues, use the order keyword to specify the order in
which you want to apply ACL rules. The order can range from 0 to 254. Dell EMC Networking OS writes to the CAM ACL rules with lowerorder numbers (order numbers closer to 0) before rules with higher-order numbers so that packets are matched as you intended. By
default, all ACL rules have an order of
Example of the order Keyword to Determine ACL Sequence
DellEMC(conf)#ip access-list standard acl1
DellEMC(config-std-nacl)#permit 20.0.0.0/8
DellEMC(config-std-nacl)#exit
DellEMC(conf)#ip access-list standard acl2
DellEMC(config-std-nacl)#permit 20.1.1.0/24 order 0
– Two or more match clauses within the same route-map sequence have the same match commands (though the values are
dierent), matching a packet against these clauses is a logical OR operation.
– Two or more match clauses within the same route-map sequence have dierent match commands, matching a packet against
these clauses is a logical AND operation.
•If no match is found in a route-map sequence, the process moves to the next route-map sequence until a match is found, or there are
no more sequences.
•When a match is found, the packet is forwarded and no more route-map sequences are processed.
– If a continue clause is included in the route-map sequence, the next or a specied route-map sequence is processed after a match
is found.
Conguration Task List for Route Maps
Congure route maps in ROUTE-MAP mode and apply the maps in various commands in ROUTER RIP and ROUTER OSPF modes.
The following list includes the conguration tasks for route maps, as described in the following sections.
•Create a route map (mandatory)
•Congure route map lters (optional)
•Congure a route map for route redistribution (optional)
•Congure a route map for route tagging (optional)
Creating a Route Map
Route maps, ACLs, and prex lists are similar in composition because all three contain lters, but route map lters do not contain the permit
and deny actions found in ACLs and prex lists.
Route map lters match certain routes and set or specic values.
To create a route map, use the following command.
•Create a route map and assign it a unique name. The optional permit and deny keywords are the actions of the route map.
The optional seq keyword allows you to assign a sequence number to the route map instance.
Access Control Lists (ACLs)
99
Congured Route Map Examples
The default action is permit and the default sequence number starts at 10. When you use the keyword deny in conguring a route map,
routes that meet the match lters are not redistributed.
To view the conguration, use the show config command in ROUTE-MAP mode.
You can create multiple instances of this route map by using the sequence number option to place the route maps in the correct order.
Dell EMC Networking OS processes the route maps with the lowest sequence number rst. When a congured route map is applied to a
command, such as redistribute, trac passes through all instances of that route map until a match is found. The following is an
example with two instances of a route map.
The following example shows matching instances of a route-map.
DellEMC#show route-map
route-map zakho, permit, sequence 10
Match clauses:
Set clauses:
route-map zakho, permit, sequence 20
Match clauses:
interface TenGigabitEthernet 1/1/1
Set clauses:
tag 35
level stub-area
DellEMC#
To delete all instances of that route map, use the no route-map map-name command. To delete just one instance, add the sequence
number to the command syntax.
DellEMC(conf)#no route-map zakho 10
DellEMC(conf)#end
DellEMC#show route-map
route-map zakho, permit, sequence 20
Match clauses:
interface TenGigabitEthernet 1/1/1
Set clauses:
tag 35
level stub-area
DellEMC#
The following example shows a route map with multiple instances. The show config command displays only the conguration of the
current route map instance. To view all instances of a specic route map, use the
DellEMC#show route-map dilling
route-map dilling, permit, sequence 10
Match clauses:
Set clauses:
route-map dilling, permit, sequence 15
Match clauses:
interface Loopback 23
Set clauses:
tag 3444
DellEMC#
To delete a route map, use the no route-map map-name command in CONFIGURATION mode.
show route-map command.
Access Control Lists (ACLs)
100
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.