Lenovo RackSwitch G8272 · 10/10/2010 · RackSwitch G8272: Application Guide

Lenovo RackSwitch G8272

Application GuideFor Networking OS 8.2

Note: Before using this information and the product it supports, read the general information in the Safety information and Environmental Notices and User Guide documents on the Lenovo Documentation CD and the Warranty Information document that comes with the product.

First Edition (April 2015)

© Copyright Lenovo 2015Portions © Copyright IBM Corporation 2014.

LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant a General Services Administration “GSA” contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-05925.

Lenovo and the Lenovo logo are trademarks of Lenovo in the United States, other countries, or both.

© Copyright Lenovo 2015 3

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . .20What You’ll Find in This Guide . . . . . . . . . . . . . . . . . . . . . .21Additional References . . . . . . . . . . . . . . . . . . . . . . . . . .25Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . .26

Part 1:. Getting Started. . . . . . . . . . . . . . . . . . . . . . 27

Chapter 1. Switch Administration . . . . . . . . . . . . . . . . . 29Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . .30

Browser-Based Interface . . . . . . . . . . . . . . . . . . . . . . .30Establishing a Connection . . . . . . . . . . . . . . . . . . . . . . . .31

Using the Switch Management Ports. . . . . . . . . . . . . . . . . .31Using the Switch Data Ports . . . . . . . . . . . . . . . . . . . . .32Using Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Using Secure Shell. . . . . . . . . . . . . . . . . . . . . . . . . .33

Using SSH with Password Authentication . . . . . . . . . . . . .34Using SSH with Public Key Authentication . . . . . . . . . . . . .34

Using a Web Browser . . . . . . . . . . . . . . . . . . . . . . . .35Using Simple Network Management Protocol. . . . . . . . . . . . . .38

BOOTP/DHCP Client IP Address Services . . . . . . . . . . . . . . . . .39DHCP Host Name Configuration . . . . . . . . . . . . . . . . . . .39DHCP SYSLOG Server. . . . . . . . . . . . . . . . . . . . . . . .40Global BOOTP Relay Agent Configuration . . . . . . . . . . . . . . .40Domain-Specific BOOTP Relay Agent Configuration. . . . . . . . . . .41DHCP Option 82 . . . . . . . . . . . . . . . . . . . . . . . . . .41

Switch Login Levels . . . . . . . . . . . . . . . . . . . . . . . . . . .42Setup vs. the Command Line . . . . . . . . . . . . . . . . . . . . . . .44Idle Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Boot Strict Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Acceptable Cipher Suites . . . . . . . . . . . . . . . . . . . . . . .47Configuring Strict Mode . . . . . . . . . . . . . . . . . . . . . . .48SSL/TLS Version Limitation . . . . . . . . . . . . . . . . . . . . .49Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Chapter 2. Initial Setup. . . . . . . . . . . . . . . . . . . . . . 51Information Needed for Setup . . . . . . . . . . . . . . . . . . . . . .52Default Setup Options . . . . . . . . . . . . . . . . . . . . . . . . . .52Stopping and Restarting Setup Manually . . . . . . . . . . . . . . . . .53Setup Part 1: Basic System Configuration . . . . . . . . . . . . . . . . .54Setup Part 2: Port Configuration . . . . . . . . . . . . . . . . . . . . .56Setup Part 3: VLANs . . . . . . . . . . . . . . . . . . . . . . . . . .58Setup Part 4: IP Configuration . . . . . . . . . . . . . . . . . . . . . .59

IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Loopback Interfaces . . . . . . . . . . . . . . . . . . . . . . . . .60Default Gateways . . . . . . . . . . . . . . . . . . . . . . . . . .61IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

4 RackSwitch G8272: Application Guide

Setup Part 5: Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . 63Optional Setup for Telnet Support . . . . . . . . . . . . . . . . . . . . 64

Chapter 3. Switch Software Management . . . . . . . . . . . . . . 65Loading New Software to Your Switch . . . . . . . . . . . . . . . . . . 66

Loading Software via the ISCLI . . . . . . . . . . . . . . . . . . . . 66Loading Software via BBI . . . . . . . . . . . . . . . . . . . . . . 67USB Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

USB Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . 68USB Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

The Boot Management Menu . . . . . . . . . . . . . . . . . . . . . . 70Recovering from a Failed Upgrade . . . . . . . . . . . . . . . . 70

Part 2:. Securing the Switch . . . . . . . . . . . . . . . . . . . 73

Chapter 4. Securing Administration . . . . . . . . . . . . . . . . 75Secure Shell and Secure Copy . . . . . . . . . . . . . . . . . . . . . . 76

Configuring SSH/SCP Features on the Switch. . . . . . . . . . . . . . 76Configuring the SCP Administrator Password . . . . . . . . . . . . . 77Using SSH and SCP Client Commands . . . . . . . . . . . . . . . . 77SSH and SCP Encryption of Management Messages . . . . . . . . . . . 79Generating RSA Host Key for SSH Access . . . . . . . . . . . . . . . 79SSH/SCP Integration with Radius Authentication . . . . . . . . . . . . 79SSH/SCP Integration with TACACS+ Authentication . . . . . . . . . . 79

End User Access Control . . . . . . . . . . . . . . . . . . . . . . . . 80Considerations for Configuring End User Accounts . . . . . . . . . . . 80Strong Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 80User Access Control . . . . . . . . . . . . . . . . . . . . . . . . . 81Listing Current Users . . . . . . . . . . . . . . . . . . . . . . . . 82Logging into an End User Account . . . . . . . . . . . . . . . . . . 82Password Fix-Up Mode . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 5. Authentication & Authorization Protocols . . . . . . . . . 83RADIUS Authentication and Authorization . . . . . . . . . . . . . . . . 84

How RADIUS Authentication Works . . . . . . . . . . . . . . . . . 84Configuring RADIUS on the Switch . . . . . . . . . . . . . . . . . . 84RADIUS Authentication Features in Lenovo N/OS . . . . . . . . . . . 85Switch User Accounts . . . . . . . . . . . . . . . . . . . . . . . . 86RADIUS Attributes for Lenovo N/OS User Privileges . . . . . . . . . . 86

TACACS+ Authentication . . . . . . . . . . . . . . . . . . . . . . . . 88How TACACS+ Authentication Works . . . . . . . . . . . . . . . . 88TACACS+ Authentication Features in Lenovo N/OS . . . . . . . . . . . 88Command Authorization and Logging . . . . . . . . . . . . . . . . 90Configuring TACACS+ Authentication on the Switch . . . . . . . . . . 90

LDAP Authentication and Authorization . . . . . . . . . . . . . . . . . 92

Chapter 6. 802.1X Port-Based Network Access Control . . . . . . . . 95Extensible Authentication Protocol over LAN . . . . . . . . . . . . . . . 96EAPoL Authentication Process . . . . . . . . . . . . . . . . . . . . . . 97EAPoL Message Exchange . . . . . . . . . . . . . . . . . . . . . . . . 98

© Copyright Lenovo 2015 Contents 5

EAPoL Port States . . . . . . . . . . . . . . . . . . . . . . . . . . .99Guest VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Supported RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . 100EAPoL Configuration Guidelines . . . . . . . . . . . . . . . . . . . . 102

Chapter 7. Access Control Lists . . . . . . . . . . . . . . . . . . 103Summary of Packet Classifiers . . . . . . . . . . . . . . . . . . . . . 104Summary of ACL Actions . . . . . . . . . . . . . . . . . . . . . . . 106Assigning Individual ACLs to a Port . . . . . . . . . . . . . . . . . . 106ACL Order of Precedence . . . . . . . . . . . . . . . . . . . . . . . 107ACL Metering and Re-Marking . . . . . . . . . . . . . . . . . . . . . 107ACL Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . 108Viewing ACL Statistics . . . . . . . . . . . . . . . . . . . . . . . . 109ACL Configuration Examples . . . . . . . . . . . . . . . . . . . . . 110VLAN Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Using Storm Control Filters . . . . . . . . . . . . . . . . . . . . . . 114

Part 3:. Switch Basics . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 8. VLANs . . . . . . . . . . . . . . . . . . . . . . . .117VLANs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 118VLANs and Port VLAN ID Numbers . . . . . . . . . . . . . . . . . . 118

VLAN Numbers . . . . . . . . . . . . . . . . . . . . . . . . . 118PVID/Native VLAN Numbers . . . . . . . . . . . . . . . . . . . 119

VLAN Tagging/Trunk Mode . . . . . . . . . . . . . . . . . . . . . . 120VLAN Topologies and Design Considerations . . . . . . . . . . . . . . 124

Multiple VLANs with Tagging/Trunk Mode Adapters . . . . . . . . . 124VLAN Configuration Example . . . . . . . . . . . . . . . . . . . 126

Private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Private VLAN Ports . . . . . . . . . . . . . . . . . . . . . . . . 127Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . 127Configuration Example . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 9. Ports and Trunking . . . . . . . . . . . . . . . . . . 129Configuring QSFP+ Ports . . . . . . . . . . . . . . . . . . . . . . . 130Trunking Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 132Static Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Static Trunk Requirements . . . . . . . . . . . . . . . . . . . . . 133Static Trunk Group Configuration Rules . . . . . . . . . . . . . . . 133Configuring a Static Port Trunk . . . . . . . . . . . . . . . . . . . 134

Link Aggregation Control Protocol . . . . . . . . . . . . . . . . . . . 136LACP Overview . . . . . . . . . . . . . . . . . . . . . . . . . 136

Static LACP Trunks . . . . . . . . . . . . . . . . . . . . . . 137LACP Port Modes . . . . . . . . . . . . . . . . . . . . . . . . . 137

LACP Individual . . . . . . . . . . . . . . . . . . . . . . . 138LACP Minimum Links Option . . . . . . . . . . . . . . . . . . . 139Configuring LACP . . . . . . . . . . . . . . . . . . . . . . . . 139

Configurable Trunk Hash Algorithm . . . . . . . . . . . . . . . . . . 140


Chapter 10. Spanning Tree Protocols . . . . . . . . . . . . . . . 143Spanning Tree Protocol Modes . . . . . . . . . . . . . . . . . . . . . 144Global STP Control . . . . . . . . . . . . . . . . . . . . . . . . . . 145PVRST Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Port States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Bridge Protocol Data Units . . . . . . . . . . . . . . . . . . . . . 146

Bridge Protocol Data Units Overview . . . . . . . . . . . . . . 146Determining the Path for Forwarding BPDUs . . . . . . . . . . . 146

Simple STP Configuration . . . . . . . . . . . . . . . . . . . . . 149Per-VLAN Spanning Tree Groups. . . . . . . . . . . . . . . . . . 151

Using Multiple STGs to Eliminate False Loops . . . . . . . . . . 151VLANs and STG Assignment . . . . . . . . . . . . . . . . . . 151Manually Assigning STGs . . . . . . . . . . . . . . . . . . . 152Guidelines for Creating VLANs . . . . . . . . . . . . . . . . . 153Rules for VLAN Tagged/Trunk Mode Ports. . . . . . . . . . . . 153Adding and Removing Ports from STGs . . . . . . . . . . . . . 154The Switch-Centric Model . . . . . . . . . . . . . . . . . . . 155

Configuring Multiple STGs . . . . . . . . . . . . . . . . . . . . 156Rapid Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . 158

Port States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158RSTP Configuration Guidelines. . . . . . . . . . . . . . . . . . . 158RSTP Configuration Example. . . . . . . . . . . . . . . . . . . . 158

Multiple Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . 160MSTP Region. . . . . . . . . . . . . . . . . . . . . . . . . . . 160Common Internal Spanning Tree . . . . . . . . . . . . . . . . . . 160MSTP Configuration Guidelines . . . . . . . . . . . . . . . . . . 160MSTP Configuration Examples . . . . . . . . . . . . . . . . . . . 161

Port Type and Link Type . . . . . . . . . . . . . . . . . . . . . . . 163Edge/Portfast Port . . . . . . . . . . . . . . . . . . . . . . . . 163Link Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 11. Virtual Link Aggregation Groups . . . . . . . . . . . . 165VLAG Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . 168VLAGs versus Port Trunks . . . . . . . . . . . . . . . . . . . . . . 168Configuring VLAGs . . . . . . . . . . . . . . . . . . . . . . . . . 170

Basic VLAG Configuration . . . . . . . . . . . . . . . . . . . . . 171VLAG Configuration - VLANs Mapped to MSTI . . . . . . . . . 173Configuring Health Check . . . . . . . . . . . . . . . . . . . 175

VLAGs with VRRP . . . . . . . . . . . . . . . . . . . . . . . . 176Configuring VLAGs in Multiple Layers . . . . . . . . . . . . . . . 182

VLAG with PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Traffic Forwarding . . . . . . . . . . . . . . . . . . . . . . . . 185Health Check. . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Chapter 12. Quality of Service . . . . . . . . . . . . . . . . . . 187QoS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Using ACL Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Summary of ACL Actions . . . . . . . . . . . . . . . . . . . . . 189ACL Metering and Re-Marking . . . . . . . . . . . . . . . . . . . 190


Using DSCP Values to Provide QoS . . . . . . . . . . . . . . . . . . . 191Differentiated Services Concepts . . . . . . . . . . . . . . . . . . 191Per Hop Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 192QoS Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193DSCP Re-Marking and Mapping . . . . . . . . . . . . . . . . . . 194DSCP Re-Marking Configuration Examples . . . . . . . . . . . . . 194

Using 802.1p Priority to Provide QoS . . . . . . . . . . . . . . . . . . 197Queuing and Scheduling . . . . . . . . . . . . . . . . . . . . . . . 198Control Plane Protection . . . . . . . . . . . . . . . . . . . . . . . . 198WRED with ECN . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

How WRED/ECN work together . . . . . . . . . . . . . . . . . . 199Configuring WRED/ECN. . . . . . . . . . . . . . . . . . . . . . 200WRED/ECN Configuration Example. . . . . . . . . . . . . . . . . 201

Chapter 13. Precision Time Protocol . . . . . . . . . . . . . . . . 205Ordinary Clock Mode . . . . . . . . . . . . . . . . . . . . . . . 206Transparent Clock Mode . . . . . . . . . . . . . . . . . . . . . . 206Tracing PTP Packets . . . . . . . . . . . . . . . . . . . . . . . . 207Viewing PTP Information . . . . . . . . . . . . . . . . . . . . . 207

Part 4:. Advanced Switching Features . . . . . . . . . . . . . . . 209

Chapter 14. OpenFlow . . . . . . . . . . . . . . . . . . . . . . 211OpenFlow Overview . . . . . . . . . . . . . . . . . . . . . . . . . 212

Switch Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 212OpenFlow Versions . . . . . . . . . . . . . . . . . . . . . . . . 212OpenFlow Instance . . . . . . . . . . . . . . . . . . . . . . . . 213Flow Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Static Flows . . . . . . . . . . . . . . . . . . . . . . . . . . 215Table-Miss . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Fail Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . 221Emergency Mode . . . . . . . . . . . . . . . . . . . . . . . . . 221OpenFlow Ports. . . . . . . . . . . . . . . . . . . . . . . . . . 222

Data Path ID . . . . . . . . . . . . . . . . . . . . . . . . . 224sFlow Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 224OpenFlow Groups . . . . . . . . . . . . . . . . . . . . . . . . 224

Configuring OpenFlow . . . . . . . . . . . . . . . . . . . . . . . . 226Configuration Example 1 - OpenFlow Boot Profile . . . . . . . . . . . 226Configuration Example 2 - Default Boot Profile . . . . . . . . . . . . 229Feature Limitations . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 15. Deployment Profiles . . . . . . . . . . . . . . . . . 233Available Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Selecting Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Automatic Configuration Changes . . . . . . . . . . . . . . . . . . . 236

Chapter 16. Virtualization. . . . . . . . . . . . . . . . . . . . . 237

Chapter 17. VMready . . . . . . . . . . . . . . . . . . . . . . 239VE Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240


Defining Server Ports . . . . . . . . . . . . . . . . . . . . . . . . . 240VM Group Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Local VM Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 241Distributed VM Groups . . . . . . . . . . . . . . . . . . . . . . . . 243

VM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Initializing a Distributed VM Group. . . . . . . . . . . . . . . . . 243Assigning Members . . . . . . . . . . . . . . . . . . . . . . . . 244Synchronizing the Configuration . . . . . . . . . . . . . . . . . . 244Removing Member VEs . . . . . . . . . . . . . . . . . . . . . . 245

VMcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Virtual Distributed Switch . . . . . . . . . . . . . . . . . . . . . . . 248

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Migrating to vDS . . . . . . . . . . . . . . . . . . . . . . . . . 249

Virtualization Management Servers . . . . . . . . . . . . . . . . . . . 250Assigning a vCenter. . . . . . . . . . . . . . . . . . . . . . . . 250vCenter Scans . . . . . . . . . . . . . . . . . . . . . . . . . . 250Deleting the vCenter . . . . . . . . . . . . . . . . . . . . . . . 251Exporting Profiles. . . . . . . . . . . . . . . . . . . . . . . . . 252VMware Operational Commands . . . . . . . . . . . . . . . . . . 252

Pre-Provisioning VEs . . . . . . . . . . . . . . . . . . . . . . . . . 253VLAN Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254VM Policy Bandwidth Control . . . . . . . . . . . . . . . . . . . . . 255

VM Policy Bandwidth Control Commands . . . . . . . . . . . . . . 255Bandwidth Policies vs. Bandwidth Shaping . . . . . . . . . . . . . 255

VMready Information Displays . . . . . . . . . . . . . . . . . . . . 257VMready Configuration Example. . . . . . . . . . . . . . . . . . . . 261

Chapter 18. FCoE and CEE . . . . . . . . . . . . . . . . . . . . 263Fibre Channel over Ethernet . . . . . . . . . . . . . . . . . . . . . . 265

The FCoE Topology . . . . . . . . . . . . . . . . . . . . . . . . 265FIP Snooping Requirements . . . . . . . . . . . . . . . . . . . . 266

Converged Enhanced Ethernet . . . . . . . . . . . . . . . . . . . . . 267Turning CEE On or Off . . . . . . . . . . . . . . . . . . . . . . 267Effects on Link Layer Discovery Protocol. . . . . . . . . . . . . . . 267Effects on 802.1p Quality of Service . . . . . . . . . . . . . . . . . 268Effects on Flow Control . . . . . . . . . . . . . . . . . . . . . . 269

FCoE Initialization Protocol Snooping . . . . . . . . . . . . . . . . . . 270Global FIP Snooping Settings . . . . . . . . . . . . . . . . . . . . 270FIP Snooping for Specific Ports . . . . . . . . . . . . . . . . . . . 270Port FCF and ENode Detection . . . . . . . . . . . . . . . . . . . 271FCoE Connection Timeout . . . . . . . . . . . . . . . . . . . . . 271FCoE ACL Rules . . . . . . . . . . . . . . . . . . . . . . . . . 271FCoE VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . 272Viewing FIP Snooping Information . . . . . . . . . . . . . . . . . 272Operational Commands . . . . . . . . . . . . . . . . . . . . . . 273FIP Snooping Configuration . . . . . . . . . . . . . . . . . . . . 273


FCoE Forwarder . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Configuring FCF . . . . . . . . . . . . . . . . . . . . . . . . . 275Fibre Channel Services . . . . . . . . . . . . . . . . . . . . . . . 275FCF VLAN Configuration . . . . . . . . . . . . . . . . . . . . . 276Full Fabric Zoning. . . . . . . . . . . . . . . . . . . . . . . . . 276Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Zonesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Defining and Activating Zoning. . . . . . . . . . . . . . . . . . . 278Changing the Active Zoneset . . . . . . . . . . . . . . . . . . . . 279FCF Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Priority-Based Flow Control . . . . . . . . . . . . . . . . . . . . . . 281Global Configuration . . . . . . . . . . . . . . . . . . . . . . . 282PFC Configuration Example . . . . . . . . . . . . . . . . . . . . 282

Enhanced Transmission Selection . . . . . . . . . . . . . . . . . . . . 284802.1p Priority Values . . . . . . . . . . . . . . . . . . . . . . . 284Priority Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 285

PGID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Assigning Priority Values to a Priority Group . . . . . . . . . . . 286Deleting a Priority Group. . . . . . . . . . . . . . . . . . . . 286Allocating Bandwidth . . . . . . . . . . . . . . . . . . . . . 286

Configuring ETS . . . . . . . . . . . . . . . . . . . . . . . . . 287Data Center Bridging Capability Exchange . . . . . . . . . . . . . . . . 290

DCBX Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 290Configuring DCBX . . . . . . . . . . . . . . . . . . . . . . . . 292

Chapter 19. Edge Virtual Bridging . . . . . . . . . . . . . . . . . 295EVB Operations Overview . . . . . . . . . . . . . . . . . . . . . . . 296

VSIDB Synchronization . . . . . . . . . . . . . . . . . . . . . . 296VLAN Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . 297Manual Reflective Relay . . . . . . . . . . . . . . . . . . . . . . 297VSIDB - IPv6 Support . . . . . . . . . . . . . . . . . . . . . . . 298

EVB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 299Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . 301

Chapter 20. Static Multicast ARP . . . . . . . . . . . . . . . . . 303Configuring Static Multicast ARP . . . . . . . . . . . . . . . . . . . . 304

Configuration Example . . . . . . . . . . . . . . . . . . . . . . 304Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Chapter 21. Unified Fabric Port . . . . . . . . . . . . . . . . . . 307UFP Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Virtual Ports Modes. . . . . . . . . . . . . . . . . . . . . . . . . . 309

vPort-S-Tag Mapping . . . . . . . . . . . . . . . . . . . . . 309vPort-VLAN Mapping . . . . . . . . . . . . . . . . . . . . . 309UFP vPort Mode . . . . . . . . . . . . . . . . . . . . . . . 309

UFP Bandwidth Provisioning . . . . . . . . . . . . . . . . . . . . . 312UFP Strict Bandwidth Provisioning Mode . . . . . . . . . . . . . . 312


Using UFP with Other RackSwitch G8272 Features . . . . . . . . . . . . 313Layer 2 Failover . . . . . . . . . . . . . . . . . . . . . . . . . 313Increased VLAN Limits . . . . . . . . . . . . . . . . . . . . . . 313VMReady . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313802.1Qbg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

UFP Configuration Examples . . . . . . . . . . . . . . . . . . . . . 314Example 1: Access Mode . . . . . . . . . . . . . . . . . . . . . . 314Example 2: Trunk Mode . . . . . . . . . . . . . . . . . . . . . . 315Example 3: Auto-VLAN Mode . . . . . . . . . . . . . . . . . . . 317Example 4: Tunnel Mode . . . . . . . . . . . . . . . . . . . . . 318Example 5: FCoE Mode . . . . . . . . . . . . . . . . . . . . . . 319Example 6: Layer 2 Failover Configuration . . . . . . . . . . . . . . 320

Part 5:. IP Routing . . . . . . . . . . . . . . . . . . . . . . . 323

Chapter 22. Basic IP Routing . . . . . . . . . . . . . . . . . . . 325IP Routing Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 326Routing Between IP Subnets . . . . . . . . . . . . . . . . . . . . . . 326Example of Subnet Routing . . . . . . . . . . . . . . . . . . . . . . 327

Using VLANs to Segregate Broadcast Domains . . . . . . . . . . . . 328Configuration Example . . . . . . . . . . . . . . . . . . . . . . 328

ARP - Local Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . 331Network Address Translation . . . . . . . . . . . . . . . . . . . . . 332

Static NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Unidirectional NAT Translation. . . . . . . . . . . . . . . . . 334Network Address Port Translation . . . . . . . . . . . . . . . 334

Dynamic NAT . . . . . . . . . . . . . . . . . . . . . . . . . . 334NAT Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . 335Global NAT Settings . . . . . . . . . . . . . . . . . . . . . . . 335Scaling and Limitations . . . . . . . . . . . . . . . . . . . . . . 336

ECMP Static Routes. . . . . . . . . . . . . . . . . . . . . . . . . . 337ECMP Route Hashing . . . . . . . . . . . . . . . . . . . . . . . 337Configuring ECMP Static Routes . . . . . . . . . . . . . . . . . . 338

Dynamic Host Configuration Protocol. . . . . . . . . . . . . . . . . . 339

Chapter 23. Policy-Based Routing . . . . . . . . . . . . . . . . . 341PBR Policies and ACLs . . . . . . . . . . . . . . . . . . . . . . . . 341Applying PBR ACLs . . . . . . . . . . . . . . . . . . . . . . . . . 341Configuring Route Maps . . . . . . . . . . . . . . . . . . . . . . . 342

Match Clauses . . . . . . . . . . . . . . . . . . . . . . . . . . 342Set Clauses. . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Configuring Health Check . . . . . . . . . . . . . . . . . . . . . 343

Example PBR Configuration . . . . . . . . . . . . . . . . . . . . . . 345Configuring PBR with other Features . . . . . . . . . . . . . . . . . . 346Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . 346Dynamic PBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Features and Limitations. . . . . . . . . . . . . . . . . . . . . . 347Example Configuration . . . . . . . . . . . . . . . . . . . . . . 347


Chapter 24. Routed Ports. . . . . . . . . . . . . . . . . . . . . 349Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Configuring a Routed Port . . . . . . . . . . . . . . . . . . . . . . . 351

Configuring OSPF on Routed Ports . . . . . . . . . . . . . . . . . 351OSPF Configuration Example . . . . . . . . . . . . . . . . . . 352

Configuring RIP on Routed Ports . . . . . . . . . . . . . . . . . . 352RIP Configuration Example . . . . . . . . . . . . . . . . . . . 352

Configuring PIM on Routed Ports . . . . . . . . . . . . . . . . . . 353PIM Configuration Example . . . . . . . . . . . . . . . . . . 353

Configuring BGP on Routed Ports . . . . . . . . . . . . . . . . . . 354Configuring IGMP on Routed Ports . . . . . . . . . . . . . . . . . 354

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Chapter 25. Internet Protocol Version 6 . . . . . . . . . . . . . . . 357IPv6 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 358IPv6 Address Format . . . . . . . . . . . . . . . . . . . . . . . . . 359IPv6 Address Types . . . . . . . . . . . . . . . . . . . . . . . . . . 360IPv6 Address Autoconfiguration . . . . . . . . . . . . . . . . . . . . 362IPv6 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Neighbor Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . 364Supported Applications . . . . . . . . . . . . . . . . . . . . . . . . 366Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . 367IPv6 Configuration Examples . . . . . . . . . . . . . . . . . . . . . 368

Chapter 26. IPsec with IPv6 . . . . . . . . . . . . . . . . . . . . 371IPsec Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Using IPsec with the RackSwitch G8272 . . . . . . . . . . . . . . . . . 373

Setting up Authentication . . . . . . . . . . . . . . . . . . . . . 373Creating an IKEv2 Proposal . . . . . . . . . . . . . . . . . . . 374Importing an IKEv2 Digital Certificate . . . . . . . . . . . . . . 374Generating an IKEv2 Digital Certificate. . . . . . . . . . . . . . 375Enabling IKEv2 Preshared Key Authentication . . . . . . . . . . 375

Setting Up a Key Policy . . . . . . . . . . . . . . . . . . . . . . 375Using a Manual Key Policy . . . . . . . . . . . . . . . . . . . . . 377Using a Dynamic Key Policy . . . . . . . . . . . . . . . . . . . . 379

Chapter 27. Routing Information Protocol . . . . . . . . . . . . . . 381Distance Vector Protocol . . . . . . . . . . . . . . . . . . . . . . . . 382Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Routing Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 382RIPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383RIPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383RIPv2 in RIPv1 Compatibility Mode. . . . . . . . . . . . . . . . . . . 383RIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384RIP Configuration Example . . . . . . . . . . . . . . . . . . . . . . 385

Chapter 28. Internet Group Management Protocol . . . . . . . . . . 387IGMP Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388How IGMP Works . . . . . . . . . . . . . . . . . . . . . . . . . . 389IGMP Capacity and Default Values . . . . . . . . . . . . . . . . . . . 390


IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . 391IGMP Querier . . . . . . . . . . . . . . . . . . . . . . . . . . 391IGMP Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 392IGMPv3 Snooping . . . . . . . . . . . . . . . . . . . . . . . . 392IGMP Snooping Configuration Guidelines . . . . . . . . . . . . . . 394IGMP Snooping Configuration Example . . . . . . . . . . . . . . . 395Advanced Configuration Example: IGMP Snooping . . . . . . . . . . 396

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . 397Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 397

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 401IGMP Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . 404Configure IGMP Relay . . . . . . . . . . . . . . . . . . . . . . 405Advanced Configuration Example: IGMP Relay . . . . . . . . . . . 406

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . 406Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 407

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 410Additional IGMP Features . . . . . . . . . . . . . . . . . . . . . . . 413

FastLeave . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413IGMP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . 413Static Multicast Router. . . . . . . . . . . . . . . . . . . . . . . 414

Chapter 29. Multicast Listener Discovery . . . . . . . . . . . . . . 415MLD Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416How MLD Works . . . . . . . . . . . . . . . . . . . . . . . . . . 417

MLD Querier. . . . . . . . . . . . . . . . . . . . . . . . . . . 418Dynamic Mrouters . . . . . . . . . . . . . . . . . . . . . . . . 419

MLD Capacity and Default Values . . . . . . . . . . . . . . . . . . . 420Configuring MLD . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Chapter 30. Border Gateway Protocol . . . . . . . . . . . . . . . 423Internal Routing Versus External Routing . . . . . . . . . . . . . . . . 424

Route Reflector . . . . . . . . . . . . . . . . . . . . . . . . . . 425Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . 427

Forming BGP Peer Routers . . . . . . . . . . . . . . . . . . . . . . 428Static Peers. . . . . . . . . . . . . . . . . . . . . . . . . . . . 428Dynamic Peers . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Loopback Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 430What is a Route Map? . . . . . . . . . . . . . . . . . . . . . . . . . 430

Next Hop Peer IP Address . . . . . . . . . . . . . . . . . . . 431Incoming and Outgoing Route Maps . . . . . . . . . . . . . . . . 431Precedence. . . . . . . . . . . . . . . . . . . . . . . . . . . . 432Configuration Overview . . . . . . . . . . . . . . . . . . . . . . 432

Aggregating Routes. . . . . . . . . . . . . . . . . . . . . . . . . . 434Redistributing Routes . . . . . . . . . . . . . . . . . . . . . . . . . 434BGP Communities . . . . . . . . . . . . . . . . . . . . . . . . . . 435BGP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436Selecting Route Paths in BGP. . . . . . . . . . . . . . . . . . . . . . 438

Equal Cost Multi-Path . . . . . . . . . . . . . . . . . . . . . . . 438Multipath Relax . . . . . . . . . . . . . . . . . . . . . . . . . 438


BGP Failover Configuration . . . . . . . . . . . . . . . . . . . . . . 439Default Redistribution and Route Aggregation Example . . . . . . . . . . 441

Chapter 31. OSPF . . . . . . . . . . . . . . . . . . . . . . . .443OSPFv2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Types of OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . 444Types of OSPF Routing Devices . . . . . . . . . . . . . . . . . . . 445Neighbors and Adjacencies . . . . . . . . . . . . . . . . . . . . . 446The Link-State Database . . . . . . . . . . . . . . . . . . . . . . 446The Shortest Path First Tree . . . . . . . . . . . . . . . . . . . . 448Internal Versus External Routing . . . . . . . . . . . . . . . . . . 448

OSPFv2 Implementation in Lenovo N/OS . . . . . . . . . . . . . . . . 449Configurable Parameters . . . . . . . . . . . . . . . . . . . . . . 449Defining Areas . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Assigning the Area Index . . . . . . . . . . . . . . . . . . . . 450Using the Area ID to Assign the OSPF Area Number . . . . . . . . 451Attaching an Area to a Network . . . . . . . . . . . . . . . . . 451

Interface Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . 452Electing the Designated Router and Backup . . . . . . . . . . . . . 452Summarizing Routes . . . . . . . . . . . . . . . . . . . . . . . 452Default Routes . . . . . . . . . . . . . . . . . . . . . . . . . . 453Virtual Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 454Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 455

Configuring Plain Text OSPF Passwords . . . . . . . . . . . . . 456Configuring MD5 Authentication . . . . . . . . . . . . . . . . 456

Host Routes for Load Balancing . . . . . . . . . . . . . . . . . . . 457Loopback Interfaces in OSPF . . . . . . . . . . . . . . . . . . . . 458OSPF Features Not Supported in This Release. . . . . . . . . . . . . 458

OSPFv2 Configuration Examples . . . . . . . . . . . . . . . . . . . . 459Example 1: Simple OSPF Domain . . . . . . . . . . . . . . . . . . 460Example 2: Virtual Links . . . . . . . . . . . . . . . . . . . . . . 462Example 3: Summarizing Routes . . . . . . . . . . . . . . . . . . 466Verifying OSPF Configuration . . . . . . . . . . . . . . . . . . . 467

OSPFv3 Implementation in Lenovo N/OS . . . . . . . . . . . . . . . . 468OSPFv3 Differences from OSPFv2 . . . . . . . . . . . . . . . . . . 468

OSPFv3 Requires IPv6 Interfaces . . . . . . . . . . . . . . . . 468OSPFv3 Uses Independent Command Paths . . . . . . . . . . . 468OSPFv3 Identifies Neighbors by Router ID . . . . . . . . . . . . 469Other Internal Improvements . . . . . . . . . . . . . . . . . . 469

OSPFv3 Limitations . . . . . . . . . . . . . . . . . . . . . . . . 469OSPFv3 Configuration Example. . . . . . . . . . . . . . . . . . . 469

Neighbor Configuration Example . . . . . . . . . . . . . . . . 472

Chapter 32. Service Location Protocol . . . . . . . . . . . . . . . 473Active DA Discovery. . . . . . . . . . . . . . . . . . . . . . 473SLP Configuration . . . . . . . . . . . . . . . . . . . . . . . 474

Chapter 33. Protocol Independent Multicast . . . . . . . . . . . . . 475PIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476


Supported PIM Modes and Features . . . . . . . . . . . . . . . . . . 477Basic PIM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 478

Globally Enabling or Disabling the PIM Feature. . . . . . . . . . . . 478Defining a PIM Network Component . . . . . . . . . . . . . . . . 478Defining an IP Interface for PIM Use . . . . . . . . . . . . . . . . 478PIM Neighbor Filters . . . . . . . . . . . . . . . . . . . . . . . 479

Additional Sparse Mode Settings . . . . . . . . . . . . . . . . . . . . 481Specifying the Rendezvous Point . . . . . . . . . . . . . . . . . . 481Influencing the Designated Router Selection . . . . . . . . . . . . . 481Specifying a Bootstrap Router . . . . . . . . . . . . . . . . . . . 482Configuring a Loopback Interface . . . . . . . . . . . . . . . . . . 482

Using PIM with Other Features. . . . . . . . . . . . . . . . . . . . . 484PIM Configuration Examples . . . . . . . . . . . . . . . . . . . . . 485

Part 6:. High Availability Fundamentals . . . . . . . . . . . . . . 489

Chapter 34. Basic Redundancy . . . . . . . . . . . . . . . . . . 491Trunking for Link Redundancy. . . . . . . . . . . . . . . . . . . . . 492Virtual Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . 492Hot Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

Forward Delay . . . . . . . . . . . . . . . . . . . . . . . . . . 493Preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . 493FDB Update . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . 493Configuring Hot Links . . . . . . . . . . . . . . . . . . . . . . 494

Chapter 35. Layer 2 Failover . . . . . . . . . . . . . . . . . . . 495Monitoring Trunk Links . . . . . . . . . . . . . . . . . . . . . . . . 495Setting the Failover Limit . . . . . . . . . . . . . . . . . . . . . . . 496Manually Monitoring Port Links . . . . . . . . . . . . . . . . . . . . 497L2 Failover with Other Features . . . . . . . . . . . . . . . . . . . . 498

Static Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . 498LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . 498

Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . 499Configuring Layer 2 Failover. . . . . . . . . . . . . . . . . . . . . . 499

Chapter 36. Virtual Router Redundancy Protocol . . . . . . . . . . 501VRRP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

VRRP Components . . . . . . . . . . . . . . . . . . . . . . . . 502VRRP Operation . . . . . . . . . . . . . . . . . . . . . . . . . 503Selecting the Master VRRP Router . . . . . . . . . . . . . . . . . 504

Failover Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . 505Active-Active Redundancy. . . . . . . . . . . . . . . . . . . . . 505Virtual Router Group . . . . . . . . . . . . . . . . . . . . . . . 505

Lenovo N/OS Extensions to VRRP . . . . . . . . . . . . . . . . . . . 506Virtual Router Deployment Considerations . . . . . . . . . . . . . . . 507High Availability Configurations . . . . . . . . . . . . . . . . . . . . 509

VRRP High-Availability Using Multiple VIRs . . . . . . . . . . . . 509VRRP High-Availability Using VLAGs . . . . . . . . . . . . . . . 513


Part 7:. Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . 515

Chapter 37. Link Layer Discovery Protocol . . . . . . . . . . . . . 517LLDP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 518Enabling or Disabling LLDP . . . . . . . . . . . . . . . . . . . . . . 519

Global LLDP Setting. . . . . . . . . . . . . . . . . . . . . . . . 519Transmit and Receive Control . . . . . . . . . . . . . . . . . . . 519

LLDP Transmit Features . . . . . . . . . . . . . . . . . . . . . . . . 520Scheduled Interval . . . . . . . . . . . . . . . . . . . . . . . . 520Minimum Interval. . . . . . . . . . . . . . . . . . . . . . . . . 520Time-to-Live for Transmitted Information . . . . . . . . . . . . . . 520Trap Notifications . . . . . . . . . . . . . . . . . . . . . . . . . 521Changing the LLDP Transmit State . . . . . . . . . . . . . . . . . 521Types of Information Transmitted . . . . . . . . . . . . . . . . . . 522

LLDP Receive Features . . . . . . . . . . . . . . . . . . . . . . . . 524Types of Information Received . . . . . . . . . . . . . . . . . . . 524Viewing Remote Device Information . . . . . . . . . . . . . . . . 524Time-to-Live for Received Information . . . . . . . . . . . . . . . . 526

LLDP Example Configuration . . . . . . . . . . . . . . . . . . . . . 528

Chapter 38. Simple Network Management Protocol . . . . . . . . . . 529SNMP Version 1 & Version 2 . . . . . . . . . . . . . . . . . . . . . . 530SNMP Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 531Configuring SNMP Trap Hosts . . . . . . . . . . . . . . . . . . . . . 533SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536Switch Images and Configuration Files . . . . . . . . . . . . . . . . . 543

Loading a New Switch Image . . . . . . . . . . . . . . . . . . . . 544Loading a Saved Switch Configuration. . . . . . . . . . . . . . . . 544Saving the Switch Configuration . . . . . . . . . . . . . . . . . . 545Saving a Switch Dump. . . . . . . . . . . . . . . . . . . . . . . 545

Chapter 39. NETCONF . . . . . . . . . . . . . . . . . . . . . . 547NETCONF Overview . . . . . . . . . . . . . . . . . . . . . . . . . 548XML Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 549Installing the NETCONF Client . . . . . . . . . . . . . . . . . . . . . 550Using Juniper Perl Client . . . . . . . . . . . . . . . . . . . . . . . 552Establishing a NETCONF Session . . . . . . . . . . . . . . . . . . . . 553NETCONF Operations . . . . . . . . . . . . . . . . . . . . . . . . 555


Protocol Operations Examples . . . . . . . . . . . . . . . . . . . . . 556<get-config> . . . . . . . . . . . . . . . . . . . . . . . . . . . 556<edit-config> . . . . . . . . . . . . . . . . . . . . . . . . . . . 557<copy-config> . . . . . . . . . . . . . . . . . . . . . . . . . . 559<delete-config> . . . . . . . . . . . . . . . . . . . . . . . . . . 560<lock> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560<unlock>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561<get> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562<close-session> . . . . . . . . . . . . . . . . . . . . . . . . . . 563<kill-session> . . . . . . . . . . . . . . . . . . . . . . . . . . . 563<get-configuration> . . . . . . . . . . . . . . . . . . . . . . . . 564<get-interface-information> . . . . . . . . . . . . . . . . . . . . 565

Part 8:. Monitoring . . . . . . . . . . . . . . . . . . . . . . . 569

Chapter 40. Remote Monitoring . . . . . . . . . . . . . . . . . . 571RMON Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 571RMON Group 1—Statistics . . . . . . . . . . . . . . . . . . . . . . 572RMON Group 2—History . . . . . . . . . . . . . . . . . . . . . . . 573

History MIB Object ID . . . . . . . . . . . . . . . . . . . . . . . 573Configuring RMON History . . . . . . . . . . . . . . . . . . . . 573

RMON Group 3—Alarms . . . . . . . . . . . . . . . . . . . . . . . 574Alarm MIB objects . . . . . . . . . . . . . . . . . . . . . . . . 574Configuring RMON Alarms . . . . . . . . . . . . . . . . . . . . 574

RMON Group 9—Events . . . . . . . . . . . . . . . . . . . . . . . 576

Chapter 41. sFlow . . . . . . . . . . . . . . . . . . . . . . . 577sFlow Statistical Counters . . . . . . . . . . . . . . . . . . . . . . . 577sFlow Network Sampling . . . . . . . . . . . . . . . . . . . . . . . 577sFlow Example Configuration . . . . . . . . . . . . . . . . . . . . . 578

Chapter 42. Port Mirroring . . . . . . . . . . . . . . . . . . . . 579

Part 9:. Appendices . . . . . . . . . . . . . . . . . . . . . . . 581

Appendix A. Glossary . . . . . . . . . . . . . . . . . . . . . . 583

Appendix B. Getting help and technical assistance. . . . . . . . . . 585

Appendix C. Notices . . . . . . . . . . . . . . . . . . . . . . 587Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 590Recycling Information. . . . . . . . . . . . . . . . . . . . . . . . . 591Particulate Contamination . . . . . . . . . . . . . . . . . . . . . . . 592Telecommunication Regulatory Statement . . . . . . . . . . . . . . . . 593


Electronic Emission Notices . . . . . . . . . . . . . . . . . . . . . . 594Federal Communications Commission (FCC) Statement . . . . . . . . 594Industry Canada Class A Emission Compliance Statement . . . . . . . 594Avis de Conformité à la Réglementation d'Industrie Canada . . . . . . 594Australia and New Zealand Class A Statement . . . . . . . . . . . . 594European Union EMC Directive Conformance Statement . . . . . . . . 594Germany Class A Statement . . . . . . . . . . . . . . . . . . . . 595Japan VCCI Class A Statement . . . . . . . . . . . . . . . . . . . 596Japan Electronics and Information Technology Industries Association (JEITA) Statement . . . . . . . . . . . . . . . . . . . . . . . . . 597Korea Communications Commission (KCC) Statement . . . . . . . . . 597

Russia Electromagnetic Interference (EMI) Class A statement . . . . . . . . 598People’s Republic of China Class A electronic emission statement . . . . . . 599Taiwan Class A compliance statement . . . . . . . . . . . . . . . . . . 600

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601



PrefaceThe Lenovo RackSwitch G8272 Application Guide for Lenovo N/OS 8.2 describes how to configure and use the Lenovo Networking OS 8.2 software on the RackSwitch G8272 (referred to as G8272 throughout this document). For documentation on installing the switch physically, see the Installation Guide for your G8272.


Who Should Use This GuideThis guide is intended for network installers and system administrators engaged in configuring and maintaining a network. The administrator should be familiar with Ethernet concepts, IP addressing, Spanning Tree Protocol, and SNMP configuration parameters.

© Copyright Lenovo 2015 Preface 21

What You’ll Find in This GuideThis guide will help you plan, implement, and administer Lenovo N/OS software. Where possible, each section provides feature overviews, usage examples, and configuration instructions. The following material is included:

Part 1: Getting Started

This material is intended to help those new to N/OS products with the basics of switch management. This part includes the following chapters:

Chapter 1, “Switch Administration,” describes how to access the G8272 to configure the switch and view switch information and statistics. This chapter discusses a variety of manual administration interfaces, including local management via the switch console, and remote administration via Telnet, a web browser, or via SNMP.

Chapter 2, “Initial Setup,” describes how to use the built-in Setup utility to perform first-time configuration of the switch.

Chapter 32, “Service Location Protocol,” describes the Service Location Protocol (SLP) that allows the switch to provide dynamic directory services.

Chapter 3, “Switch Software Management,” describes how to update the N/OS software operating on the switch.

Part 2: Securing the Switch

Chapter 4, “Securing Administration,” describes methods for using Secure Shell for administration connections, and configuring end-user access control.

Chapter 5, “Authentication & Authorization Protocols,” describes different secure administration for remote administrators. This includes using Remote Authentication Dial-in User Service (RADIUS), as well as TACACS+ and LDAP.

Chapter 6, “802.1X Port-Based Network Access Control,” describes how to authenticate devices attached to a LAN port that has point-to-point connection characteristics. This feature prevents access to ports that fail authentication and authorization and provides security to ports of the G8272 that connect to blade servers.

Chapter 7, “Access Control Lists,” describes how to use filters to permit or deny specific types of traffic, based on a variety of source, destination, and packet attributes.

Part 3: Switch Basics

Chapter 8, “VLANs,” describes how to configure Virtual Local Area Networks (VLANs) for creating separate network segments, including how to use VLAN tagging for devices that use multiple VLANs. This chapter also describes Protocol-based VLANs, and Private VLANs.

Chapter 9, “Ports and Trunking,” describes how to group multiple physical ports together to aggregate the bandwidth between large-scale network devices.


Chapter 10, “Spanning Tree Protocols,” discusses how Spanning Tree Protocol (STP) configures the network so that the switch selects the most efficient path when multiple paths exist. Covers Rapid Spanning Tree Protocol (RSTP), Per-VLAN Rapid Spanning Tree (PVRST), and Multiple Spanning Tree Protocol (MSTP).

Chapter 11, “Virtual Link Aggregation Groups,” describes using Virtual Link Aggregation Groups (VLAG) to form trunks spanning multiple VLAG-capable aggregator switches.

Chapter 12, “Quality of Service,” discusses Quality of Service (QoS) features, including IP filtering using Access Control Lists (ACLs), Differentiated Services, and IEEE 802.1p priority values.

Chapter 13, “Precision Time Protocol,” describes the configuration of PTP for clock synchronization.

Part 4: Advanced Switching Features

Chapter 14, “OpenFlow,” describes how to create an OpenFlow Switch instance on the RackSwitch G8272.

Chapter 15, “Deployment Profiles,” describes how the G8272 can operate in different modes for different deployment scenarios, adjusting switch capacity levels to optimize performance for different types of networks.

Chapter 16, “Virtualization,” provides an overview of allocating resources based on the logical needs of the data center, rather than on the strict, physical nature of components.

Chapter 14, “Virtual NICs,” discusses using virtual NIC (vNIC) technology to divide NICs into multiple logical, independent instances.

Chapter 17, “VMready,” discusses virtual machine (VM) support on the G8272.

Chapter 18, “FCoE and CEE,” discusses using various Converged Enhanced Ethernet (CEE) features such as Priority-based Flow Control (PFC), Enhanced Transmission Selection (ETS), and FIP Snooping for solutions such as Fibre Channel over Ethernet (FCoE).

Chapter 19, “Edge Virtual Bridging (EVB) discusses the IEEE 802.1Qbg—a standards-based protocol that defines how virtual Ethernet bridges exchange configuration information. EVB bridges the gap between physical and virtual network resources, thus simplifying network management.

Chapter 20, “Static Multicast ARP discusses the configuration of a static ARP entry with multicast MAC address for Microsoft’s Network Load Balancing (NLB) feature to function efficiently.

Chapter 21, “Unified Fabric Port describes how UFP logically subdivides a high-speed physical link connecting to a server NIC. UFP provides a switch fabric component to control the NIC.

Part 5: IP Routing

Chapter 22, “Basic IP Routing,” describes how to configure the G8272 for IP routing using IP subnets, BOOTP, and DHCP Relay.

Chapter 23, “Policy-Based Routing describes how to configure the G8272 to forward traffic based on defined policies rather than entries in the routing table.


Chapter 24, “Routed Ports describes how to configure a switch port to forward Layer 3 traffic.

Chapter 25, “Internet Protocol Version 6,” describes how to configure the G8272 for IPv6 host management.

Chapter 26, “IPsec with IPv6,” describes how to configure Internet Protocol Security (IPsec) for securing IP communications by authenticating and encrypting IP packets, with emphasis on Internet Key Exchange version 2, and authentication/confidentiality for OSPFv3.

Chapter 27, “Routing Information Protocol,” describes how the N/OS software implements standard Routing Information Protocol (RIP) for exchanging TCP/IP route information with other routers.

Chapter 28, “Internet Group Management Protocol,” describes how the N/OS software implements IGMP Snooping or IGMP Relay to conserve bandwidth in a multicast-switching environment.

Chapter 29, “Multicast Listener Discovery,” describes how Multicast Listener Discovery (MLD) is used with IPv6 to support host users requests for multicast data for a multicast group.

Chapter 30, “Border Gateway Protocol,” describes Border Gateway Protocol (BGP) concepts and features supported in N/OS.

Chapter 31, “OSPF,” describes key Open Shortest Path First (OSPF) concepts and their implemented in N/OS, and provides examples of how to configure your switch for OSPF support.

Chapter 33, “Protocol Independent Multicast,” describes how multicast routing can be efficiently accomplished using the Protocol Independent Multicast (PIM) feature.

Part 6: High Availability Fundamentals

Chapter 34, “Basic Redundancy,” describes how the G8272 supports redundancy through trunking, and hotlinks.

Chapter 35, “Layer 2 Failover,” describes how the G8272 supports high-availability network topologies using Layer 2 Failover.

Chapter 36, “Virtual Router Redundancy Protocol,” describes how the G8272 supports high-availability network topologies using Virtual Router Redundancy Protocol (VRRP).

Part 7: Network Management

Chapter 37, “Link Layer Discovery Protocol,” describes how Link Layer Discovery Protocol helps neighboring network devices learn about each others’ ports and capabilities.

Chapter 38, “Simple Network Management Protocol,” describes how to configure the switch for management through an SNMP client.

Chapter 39, “NETCONF,” describes how to manage the G8272 using the Network Configuration Protocol (NETCONF), a mechanism based on the Extensible Markup Language (XML).


Part 8: Monitoring

Chapter 40, “Remote Monitoring,” describes how to configure the RMON agent on the switch, so that the switch can exchange network monitoring data.

Chapter 41, “sFlow, described how to use the embedded sFlow agent for sampling network traffic and providing continuous monitoring information to a central sFlow analyzer.

Chapter 42, “Port Mirroring,” discusses tools how copy selected port traffic to a monitor port for network analysis.

Part 9: Appendices

Appendix A, “Glossary,” describes common terms and concepts used throughout this guide.

Appendix B, “Getting help and technical assistance,” provides details on where to go for additional information about Lenovo and Lenovo products.

Appendix C, “Notices,” contains copyright and trademark notices.


Additional ReferencesAdditional information about installing and configuring the G8272 is available in the following guides:

Lenovo RackSwitch G8272 Installation Guide

Lenovo RackSwitch G8272 Industry-Standard CLI Reference Guide for Lenovo N/OS 8.2


Typographic ConventionsThe following table describes the typographic styles used in this book.

Table 1. Typographic Conventions

Typeface or Symbol

Meaning Example

ABC123 This type is used for names of commands, files, and directories used within the text.

View the readme.txt file.

It also depicts on-screen computer output and prompts.

Main#

ABC123 This bold type appears in command examples. It shows text that must be typed in exactly as shown.

Main# sys

<ABC123> This italicized type appears in command examples as a parameter placeholder. Replace the indicated text with the appropriate real name or value when using the command. Do not type the brackets.

To establish a Telnet session, enter:host# telnet <IP address>

This also shows book titles, special terms, or words to be emphasized.

Read your User’s Guide thoroughly.

[ ] Command items shown inside brackets are optional and can be used or excluded as the situation demands. Do not type the brackets.

host# ls [a]

| The vertical bar ( | ) is used in command examples to separate choices where multiple options exist. Select only one of the listed options. Do not type the vertical bar.

host# set left|right

AaBbCc123 This block type depicts menus, buttons, and other controls that appear in Web browsers and other graphical interfaces.

Click the Save button.


Part 1: Getting Started



Chapter 1. Switch Administration

Your RackSwitch G8272 (G8272) is ready to perform basic switching functions right out of the box. Some of the more advanced features, however, require some administrative configuration before they can be used effectively.

The extensive Lenovo Networking OS switching software included in the G8272 provides a variety of options for accessing the switch to perform configuration, and to view switch information and statistics.

This chapter discusses the various methods that can be used to administer the switch.


Administration InterfacesLenovo N/OS provides a variety of user-interfaces for administration. These interfaces vary in character and in the methods used to access them: some are text-based, and some are graphical; some are available by default, and some require configuration; some can be accessed by local connection to the switch, and others are accessed remotely using various client applications. For example, administration can be performed using any of the following:

A built-in, text-based command-line interface and menu system for access via serial-port connection or an optional Telnet or SSH session

The built-in Browser-Based Interface (BBI) available using a standard web-browser

SNMP support for access through network management software such as IBM Director or HP OpenView

The specific interface chosen for an administrative session depends on user preferences, as well as the switch configuration and the available client tools.

In all cases, administration requires that the switch hardware is properly installed and turned on. (see the RackSwitch G8272 Installation Guide).

Browser-Based Interface

The Browser-based Interface (BBI) provides access to the common configuration, management and operation features of the G8272 through your Web browser.

For more information, refer to the BBI Quick Guide.

© Copyright Lenovo 2015 Chapter 1: Switch Administration 31

Establishing a ConnectionThe factory default settings permit initial switch administration through only the built-in serial port. All other forms of access require additional switch configuration before they can be used.

Remote access using the network requires the accessing terminal to have a valid, routable connection to the switch interface. The client IP address may be configured manually, or an IPv4 address can be provided automatically through the switch using a service such as DHCP or BOOTP relay (see “BOOTP/DHCP Client IP Address Services” on page 39), or an IPv6 address can be obtained using IPv6 stateless address configuration.Note: Throughout this manual, IP address is used in places where either an IPv4 or IPv6 address is allowed. IPv4 addresses are entered in dotted-decimal notation (for example, 10.10.10.1), while IPv6 addresses are entered in hexadecimal notation (for example, 2001:db8:85a3::8a2e:370:7334). In places where only one type of address is allowed, IPv4 address or IPv6 address is specified.

Using the Switch Management Ports

To manage the switch through the management ports, you must configure an IP interface for each management interface. Configure the following IPv4 parameters:

IP address/mask

Default gateway address

1. Log on to the switch.

2. Enter Global Configuration mode.

3. Configure a management IP address and mask:

4. Configure the appropriate default gateway.

IP gateway 4 is required for IF 128.

Once you configure a management IP address for your switch, you can connect to a management port and use the Telnet program from an external management station to access and control the switch. The management port provides out-of-band management.

RS 8272> enableRS 8272# configure terminal

RS 8272(config)# interface ip 128RS 8272(configipif)# ip address <management interface IPv4 address>RS 8272(configipif)# ip netmask <IPv4 subnet mask>RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway 4 address <default gateway IPv4 address>RS 8272(config)# ip gateway 4 enable


Using the Switch Data Ports

You also can configure in-band management through any of the switch data ports. To allow in-band management, use the following procedure:

1. Log on to the switch.

2. Enter IP interface mode.

Note: Interface 128 is reserved for out-of-band management (see “Using the Switch Management Ports” on page 31).

3. Configure the management IP interface/mask.

Using IPv4:

Using IPv6:

4. Configure the VLAN, and enable the interface.

5. Configure the default gateway.

If using IPv4:

If using IPv6:

Note: Gateway 1, 2, and 3 are used for in-band data networks. Gateway 4 is reserved for the out-of-band management port (see “Using the Switch Management Ports” on page 31).

Once you configure the IP address and have a network connection, you can use the Telnet program from an external management station to access and control the switch. Once the default gateway is enabled, the management station and your switch do not need to be on the same IP subnet.

RS 8272> enableRS 8272# configure terminalRS 8272(config)# interface ip <IP interface number>

RS 8272(configipif)# ip address <management interface IPv4 address>RS 8272(configipif)# ip netmask <IPv4 subnet mask>

RS 8272(configipif)# ipv6 address <management interface IPv6 address>RS 8272(configipif)# ipv6 prefixlen <IPv6 prefix length>

RS 8272(configipif)# vlan 1RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway <gateway number> address <IPv4 address>RS 8272(config)# ip gateway <gateway number> enable

RS 8272(config)# ip gateway6 <gateway number> address <IPv6 address>RS 8272(config)# ip gateway6 <gateway number> enable


The G8272 supports an industry standard command-line interface (ISCLI) that you can use to configure and control the switch over the network using the Telnet program. You can use the ISCLI to perform many basic network management functions. In addition, you can configure the switch for management using an SNMP-based network management system or a Web browser.

For more information, see the documents listed in “Additional References” on page 25.

Using Telnet

A Telnet connection offers the convenience of accessing the switch from a workstation connected to the network. Telnet access provides the same options for user and administrator access as those available through the console port.

By default, Telnet access is enabled. Use the following commands to disable or re-enable Telnet access:

Once the switch is configured with an IP address and gateway, you can use Telnet to access switch administration from any workstation connected to the management network.

To establish a Telnet connection with the switch, run the Telnet program on your workstation and issue the following Telnet command:

You will then be prompted to enter a password as explained “Switch Login Levels” on page 42.

Two attempts are allowed to log in to the switch. After the second unsuccessful attempt, the Telnet client is disconnected via TCP session closure.

Using Secure Shell

Although a remote network administrator can manage the configuration of a G8272 via Telnet, this method does not provide a secure connection. The Secure Shell (SSH) protocol enables you to securely log into another device over a network to execute commands remotely. As a secure alternative to using Telnet to manage switch configuration, SSH ensures that all data sent over the network is encrypted and secure.

The switch can do only one session of key/cipher generation at a time. Thus, a SSH/SCP client will not be able to login if the switch is doing key generation at that time. Similarly, the system will fail to do the key generation if a SSH/SCP client is logging in at that time.

The supported SSH encryption and authentication methods are:

Server Host Authentication: Client RSA-authenticates the switch when starting each connection

RS 8272(config)# [no] access telnet enable

telnet <switch IPv4 or IPv6 address>


Key Exchange: ecdh-sha2-nistp521, ecdh-sha2-nistp384, ecdh-sha2-nistp256, ecdh-sha2-nistp224, ecdh-sha2-nistp192, rsa2048-sha256, rsa1024-sha1, diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group1-sha1

Encryption: aes128-ctr, aes128-cbc, rijndael128-cbc, blowfish-cbc,3des-cbc, arcfour256, arcfour128, arcfour

MAC: hmac-sha1, hmac-sha1-96, hmac-md5, hmac-md5-96

User Authentication: Local password authentication, public key authentication, RADIUS, TACACS+

Lenovo Networking OS implements the SSH version 2.0 standard and is confirmed to work with SSH version 2.0-compliant clients such as the following:

OpenSSH_5.4p1 for Linux

Secure CRT Version 5.0.2 (build 1021)

Putty SSH release 0.60

Using SSH with Password AuthenticationBy default, the SSH feature is disabled. Once the IP parameters are configured and the SSH service is enabled, you can access the command line interface using an SSH connection.

To establish an SSH connection with the switch, run the SSH program on your workstation by issuing the SSH command, followed by the switch IPv4 or IPv6 address:

You will then be prompted to enter a password as explained “Switch Login Levels” on page 42.

Using SSH with Public Key AuthenticationSSH can also be used for switch authentication based on asymmetric cryptography. Public encryption keys can be uploaded on the switch and used to authenticate incoming login attempts based on the clients’ private encryption key pairs. After a predefined number of failed public key login attempts, the switch reverts to password-based authentication.

To set up public key authentication:

1. Enable SSH:

2. Import the public key file using SFTP or TFTP for the admin user account::

# ssh <switch IP address>

RS 8272(config)# ssh enable

RS 8272(config)# copy sftp|tftp publickeyPort type ["DATA"/"MGT"]: mgtAddress or name of remote host: 9.43.101.151Source file name: 11.keyUsername of the public key: adminConfirm download operation (y/n) ? y


Notes:

When prompted to input a username, a valid user account name must be entered. If no username is entered, the key is stored on the switch, and can be assigned to a user account later.

A user account can have up to 100 public keys set up on the switch.

3. Configure a maximum number of 3 failed public key authentication attempts before the system reverts to password-based authentication:

Once the public key is configured on the switch, the client can use SSH to login from a system where the private key pair is set up:

Using a Web Browser

The switch provides a Browser-Based Interface (BBI) for accessing the common configuration, management and operation features of the G8272 through your Web browser.

By default, BBI access via HTTP is enabled on the switch.

You can also access the BBI directly from an open Web browser window. Enter the URL using the IP address of the switch interface (for example, http://<IPv4 or IPv6 address>).

Configuring HTTP Access to the BBI

By default, BBI access via HTTP is enabled on the switch.

To disable or re-enable HTTP access to the switch BBI, use the following commands:

The default HTTP web server port to access the BBI is port 80. However, you can change the default Web server port with the following command:

To access the BBI from a workstation, open a Web browser window and type in the URL using the IP address of the switch interface (for example, http://<IPv4 or IPv6 address>).

Configuring HTTPS Access to the BBI

The BBI can also be accessed via a secure HTTPS connection over management and data ports.

RS 8272(config)# ssh maxauthattempts 3

# ssh <switch IP address>

RS 8272(config)# access http enable (Enable HTTP access)-or-

RS 8272(config)# no access http enable (Disable HTTP access)

RS 8272(config)# access http port <TCP port number>


1. Enable HTTPS.

By default, BBI access via HTTPS is disabled on the switch. To enable BBI Access via HTTPS, use the following command:

2. Set the HTTPS server port number (optional).

To change the HTTPS Web server port number from the default port 443, use the following command:

3. Generate the HTTPS certificate.

Accessing the BBI via HTTPS requires that you generate a certificate to be used during the key exchange. A default certificate is created the first time HTTPS is enabled, but you can create a new certificate defining the information you want to be used in the various fields.

4. Save the HTTPS certificate.

The certificate is valid only until the switch is rebooted. To save the certificate so it is retained beyond reboot or power cycles, use the following command:

When a client (such as a web browser) connects to the switch, the client is asked to accept the certificate and verify that the fields match what is expected. Once BBI access is granted to the client, the BBI can be used as described in the Lenovo Networking OS 8.2 BBI Quick Guide.

RS 8272(config)# access https enable

RS 8272(config)# access https port <x>

RS 8272(config)# access https generatecertificateCountry Name (2 letter code) []: <country code>State or Province Name (full name) []: <state>Locality Name (eg, city) []: <city>Organization Name (eg, company) []: <company>Organizational Unit Name (eg, section) []: <org. unit>Common Name (eg, YOUR name) []: <name>Email (eg, email address) []: <email address>Confirm generating certificate? [y/n]: yGenerating certificate. Please wait (approx 30 seconds)restarting SSL agent

RS 8272(config)# access https savecertificate


Browser-Based Interface Summary

The BBI is organized at a high level as follows:

Context buttons—These buttons allow you to select the type of action you wish to perform. The Configuration button provides access to the configuration elements for the entire switch. The Statistics button provides access to the switch statistics and state information. The Dashboard button allows you to display the settings and operating status of a variety of switch features.

Navigation Window—This window provides a menu list of switch features and functions: System—this folder provides access to the configuration elements for the entire

switch.

Switch Ports—Configure each of the physical ports on the switch.

Port-Based Port Mirroring—Configure port mirroring behavior.

Layer 2—Configure Layer 2 features for the switch.

RMON Menu—Configure Remote Monitoring features for the switch.

Layer 3—Configure Layer 3 features for the switch.

QoS—Configure Quality of Service features for the switch.

Access Control—Configure Access Control Lists to filter IP packets. CEE – Configure Converged Enhanced Ethernet (CEE). FCoE – Configure FibreChannel over Ethernet (FCoE). Virtualization – Configure vNICs and VMready for virtual machine (VM) sup-

port.


Using Simple Network Management Protocol

N/OS provides Simple Network Management Protocol (SNMP) version 1, version 2, and version 3 support for access through any network management software, such as IBM Director or HP-OpenView.Note: SNMP read and write functions are enabled by default. For best security practices, if SNMP is not needed for your network, it is recommended that you disable these functions prior to connecting the switch to the network.

To access the SNMP agent on the G8272, the read and write community strings on the SNMP manager must be configured to match those on the switch. The default read community string on the switch is public and the default write community string is private.

The read and write community strings on the switch can be configured using the following commands:

The SNMP manager must be able to reach any one of the IP interfaces on the switch.

For the SNMP manager to receive the SNMPv1 traps sent out by the SNMP agent on the switch, configure the trap host on the switch with the following commands:

To restrict SNMP access to specific IPv4 subnets, use the following commands:

For IPv6 networks, use:

Note: Subnets allowed for SNMP read-only access must not overlap with subnets allowed for SNMP read-write access.

For more information on SNMP usage and configuration, see “Simple Network Management Protocol” on page 529.

RS 8272(config)# snmpserver readcommunity <1-32 characters>

-and-RS 8272(config)# snmpserver writecommunity <1-32 characters>

RS 8272(config)# snmpserver trapsource <trap source IP interface>RS 8272(config)# snmpserver host <IPv4 address> <trap host community string>

RS 8272(config)# access managementnetwork <IPv4 address> <subnet mask> snmpro

-and-RS 8272(config)# access managementnetwork <IPv4 address> <subnet mask> snmprw

RS 8272(config)# access managementnetwork6 <IPv6 address> <IPv6 prefix length> snmpro

-and-RS 8272(config)# access managementnetwork6 <IPv6 address> <IPv6 prefix length> snmprw


BOOTP/DHCP Client IP Address ServicesFor remote switch administration, the client terminal device must have a valid IP address on the same network as a switch interface. The IP address on the client device may be configured manually, or obtained automatically using IPv6 stateless address configuration, or an IPv4 address may obtained automatically via BOOTP or DHCP relay as discussed in the next section.

The G8272 can function as a relay agent for Bootstrap Protocol (BOOTP) or DHCP. This allows clients to be assigned an IPv4 address for a finite lease period, reassigning freed addresses later to other clients.

Acting as a relay agent, the switch can forward a client’s IPv4 address request to up to five BOOTP/DHCP servers. In addition to the five global BOOTP/DHCP servers, up to five domain-specific BOOTP/DHCP servers can be configured for each of up to 10 VLANs.

When a switch receives a BOOTP/DHCP request from a client seeking an IPv4 address, the switch acts as a proxy for the client. The request is forwarded as a UDP Unicast MAC layer message to the BOOTP/DHCP servers configured for the client’s VLAN, or to the global BOOTP/DHCP servers if no domain-specific BOOTP/DHCP servers are configured for the client’s VLAN. The servers respond to the switch with a Unicast reply that contains the IPv4 default gateway and the IPv4 address for the client. The switch then forwards this reply back to the client.

DHCP is described in RFC 2131, and the DHCP relay agent supported on the G8272 is described in RFC 1542. DHCP uses UDP as its transport protocol. The client sends messages to the server on port 67 and the server sends messages to the client on port 68.

BOOTP and DHCP relay are collectively configured using the BOOTP commands and menus on the G8272.

DHCP Host Name Configuration

The G8272 supports DHCP host name configuration as described in RFC 2132, option 12. DHCP host name configuration is enabled by default.

Host name can be manually configured using the following command:

If the host name is manually configured, the switch does not replace it with the host name received from the DHCP server.

After the host name is configured on the switch, if DHCP or DHCP host name configuration is disabled, the switch retains the host name.

The switch prompt displays the host name.

Host name configuration can be enabled/disabled using the following command:

RS 8272(config)# hostname <name>

RS 8272(config)# [no] system dhcp hostname


DHCP SYSLOG Server

During switch startup, if the switch fails to get the configuration file, a message can be recorded in the SYSLOG server.

The G8272 supports requesting of a SYSLOG server IP address from the DHCP server as described in RFC 2132, option 7. DHCP SYSLOG server request option is enabled by default.

Manually configured SYSLOG server takes priority over DHCP SYSLOG server.

Up to two SYSLOG server addresses received from the DHCP server can be used. The SYSLOG server can be learnt over a management port or a data port.

Use the RS 8272# show logging command to view the SYSLOG server address.

DHCP SYSLOG server address option can be enabled/disabled using the following command:

Global BOOTP Relay Agent Configuration

To enable the G8272 to be a BOOTP (or DHCP) forwarder, enable the BOOTP relay feature, configure up to four global BOOTP server IPv4 addresses on the switch, and enable BOOTP relay on the interface(s) on which the client requests are expected.

Generally, it is best to configure BOOTP for the switch IP interface that is closest to the client, so that the BOOTP server knows from which IPv4 subnet the newly allocated IPv4 address will come.

In the G8272 implementation, there are no primary or secondary BOOTP servers. The client request is forwarded to all the global BOOTP servers configured on the switch (if no domain-specific servers are configured). The use of multiple servers provides failover redundancy. However, no health checking is supported.

1. Use the following commands to configure global BOOTP relay servers:

2. Enable BOOTP relay on the appropriate IP interfaces.

BOOTP/DHCP Relay functionality may be assigned on a per-interface basis using the following commands:

RS 8272(config)# [no] system dhcp syslog

RS 8272(config)# ip bootprelay enableRS 8272(config)# ip bootprelay server <1-5> address <IPv4 address>

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# relayRS 8272(configipif)# exit


Domain-Specific BOOTP Relay Agent Configuration

Use the following commands to configure up to five domain-specific BOOTP relay agents for each of up to 10 VLANs:

As with global relay agent servers, domain-specific BOOTP/DHCP functionality may be assigned on a per-interface basis (see Step 2 in page 40).

DHCP Option 82

DHCP Option 82 provides a mechanism for generating IP addresses based on the client device’s location in the network. When you enable the DHCP relay agent option on the switch, it inserts the relay agent information option 82 in the packet, and sends a unicast BOOTP request packet to the DHCP server. The DHCP server uses the option 82 field to assign an IP address, and sends the packet, with the original option 82 field included, back to the relay agent. DHCP relay agent strips off the option 82 field in the packet and sends the packet to the DHCP client.

Configuration of this feature is optional. The feature helps resolve several issues where untrusted hosts access the network. See RFC 3046 for details.

Use the following commands to configure DHCP Option 82:

RS 8272(config)# ip bootprelay bcastdomain <1-10> vlan <VLAN number>RS 8272(config)# ip bootprelay bcastdomain <1-10> server <1-5> address

<IPv4 address>RS 8272(config)# ip bootprelay bcastdomain <1-10> enable

RS 8272(config)# ip bootprelay information enable (Enable Option 82)RS 8272(config)# ip bootprelay enable (Enable DHCP relay)RS 8272(config)# ip bootprelay server <1-5> address <IP address>


Switch Login LevelsTo enable better switch management and user accountability, three levels or classes of user access have been implemented on the G8272. Levels of access to CLI, Web management functions, and screens increase as needed to perform various switch management tasks. Conceptually, access classes are defined as follows:

User interaction with the switch is completely passive—nothing can be changed on the G8272. Users may display information that has no security or privacy implications, such as switch statistics and current operational state information.

Operators can only effect temporary changes on the G8272. These changes will be lost when the switch is rebooted/reset. Operators have access to the switch management features used for daily switch operations. Because any changes an operator makes are undone by a reset of the switch, operators cannot severely impact switch operation.

Administrators are the only ones that may make permanent changes to the switch configuration—changes that are persistent across a reboot/reset of the switch. Administrators can access switch functions to configure and troubleshoot problems on the G8272. Because administrators can also make temporary (operator-level) changes as well, they must be aware of the interactions between temporary and permanent changes.

Access to switch functions is controlled through the use of unique user names and passwords. Once you are connected to the switch via console, remote Telnet, or SSH, you are prompted to enter a password. The default user names/password for each access level are listed in the following table.Note: It is recommended that you change default switch passwords after initial configuration and as regularly as required under your network security policies. Table 2. User Access Levels - Default Settings

User Account

Password Description and Tasks Performed Status

user user The User has no direct responsibility for switch management. He or she can view all switch status information and statistics, but cannot make any configuration changes to the switch.

Disabled

oper oper The Operator manages all functions of the switch. The Operator can reset ports, except the management ports.

Disabled

admin admin The superuser Administrator has complete access to all menus, information, and configuration commands on the G8272, including the ability to change both the user and administrator passwords.

Enabled


Note: Access to each user level (except admin account) can be disabled by setting the password to an empty value. To disable admin account, use the command: RS 8272(config)# no access user administratorenable. Admin account can be disabled only if there is at least one user account enabled and configured with administrator privilege.


Setup vs. the Command LineOnce the administrator password is verified, you are given complete access to the switch. If the switch is still set to its factory default configuration, the system will ask whether you wish to run Setup (see “Initial Setup” on page 51”), a utility designed to help you through the first-time configuration process. If the switch has already been configured, the command line is displayed instead.

Idle DisconnectBy default, the switch will disconnect your Telnet session after 10 minutes of inactivity. This function is controlled by the idle timeout parameter, which can be set from 0 to 60 minutes, where 0 means the session will never timeout.

Use the following command to set the idle timeout value:

RS 8272(config)# system idle <0-60>


Boot Strict ModeThe implementations specified in this section are compliant with National Institute of Standards and Technology (NIST) Special Publication (SP) 800-131A.

The RackSwitch G8272 can operate in two boot modes:

Compatibility mode (default): This is the default switch boot mode. This mode may use algorithms and key lengths that may not be allowed/acceptable by NIST SP 800-131A specification. This mode is useful in maintaining compatibility with previous releases and in environments that have lesser data security requirements.

Strict mode: Encryption algorithms, protocols, and key lengths in strict mode are compliant with NIST SP 800-131A specification.

When in boot strict mode, the switch uses Secure Sockets Layer (SSL)/Transport Layer Security (TLS) 1.2 protocols to ensure confidentiality of the data to and from the switch.

Before enabling strict mode, ensure the following:

The software version on all connected switches is Lenovo N/OS 8.2.

The supported protocol versions and cryptographic cipher suites between clients and servers are compatible. For example: if using SSH to connect to the switch, ensure that the SSH client supports SSHv2 and a strong cipher suite that is compliant with the NIST standard.

Compliant Web server certificate is installed on the switch, if using BBI.

A new self-signed certificate is generated for the switch (RS 8272(config)# access https generatecertificate). The new certificate is generated using 2048-bit RSA key and SHA-256 digest.

Protocols that are not NIST SP 800-131A compliant must be disabled or not used.

Only SSHv2 or higher is used.

The current configuration, if any, is saved in a location external to the switch. When the switch reboots, both the startup and running configuration are lost.

Only protocols/algorithms compliant with NIST SP 800-131A specification are used/enabled on the switch. Please see the NIST SP 800-131A publication for details. The following table lists the acceptable protocols and algorithms:

Table 3. Acceptable Protocols and Algorithms

Protocol/Function Strict Mode Algorithm Compatibility Mode Algorithm

BGP BGP does not comply with NIST SP 800-131A specification. When in strict mode, BGP is disabled. How-ever, it can be enabled, if required.

Acceptable

CertificateGeneration

RSA-2048SHA-256

RSA 2048SHA 256

CertificateAcceptance

RSA 2048 or higherSHA 224 or higher

RSASHA, SHA2


HTTPS TLS 1.2 onlySee “Acceptable Cipher Suites” on page 47;

TLS 1.0, 1.1, 1.2See “Acceptable Cipher Suites” on page 47;

IKEKey Exchange DH Group 24 DH group 1, 2, 5, 14, 24Encryption 3DES, AES-128-CBC 3DES, AES-128-CBCIntegrity HMAC-SHA1 HMAC-SHA1, HMAC-MD5IPSecAH HMAC-SHA1 HMAC-SHA1, HMAC-MD5ESP 3DES, AES-128-CBC, HMAC-SHA1 3DES, AES-128-CBC,

HMAC-SHA1, HMAC-MD5LDAP LDAP does not comply with NIST

SP 800-131A specification. When in strict mode, LDAP is disabled. However, it can be enabled, if required.

Acceptable

OSPF OSPF does not comply with NIST SP 800-131A specification. When in strict mode, OSPF is disabled. How-ever, it can be enabled, if required.

Acceptable

RADIUS RADIUS does not comply with NIST SP 800-131A specification. When in strict mode, RADIUS is disabled. However, it can be enabled, if required.

Acceptable

Random Number Generator

NIST SP 800-90A AES CTR DRBG NIST SP 800-90A AES CTR DRBG

Secure NTP Secure NTP does not comply with NIST SP 800-131A specification. When in strict mode, secure NTP is disabled. However, it can be enabled, if required.

Acceptable

SLP SHA-256 or higherRSA/DSA 2048 or higher

SNMP SNMPv3 onlyAES-128-CFB-128/SHA1

Note: Following algorithms are acceptable if you choose to support old SNMPv3 factory default users:AES-128-CFB/SHA1DES/MD5AES-128-CFB-128/SHA1

SNMPv1, SNMPv2, SNMPv3DES/MD5, AES-128-CFB-128/SHA1




Acceptable Cipher Suites

The following cipher suites are acceptable (listed in the order of preference) when the RackSwitch G8272 is in compatibility mode:

SSH/SFTP Host Key SSH-RSA SSH-RSAKey Exchange ECDH-SHA2-NISTP521

ECDH-SHA2-NISTP384ECDH-SHA2-NISTP256ECDH-SHA2-NISTP224RSA2048-SHA256DIFFIE-HELL-MAN-GROUP-EXCHANGE-SHA256DIFFIE-HELL-MAN-GROUP-EXCHANGE-SHA1

ECDH-SHA2-NISTP521ECDH-SHA2-NISTP384ECDH-SHA2-NISTP256ECDH-SHA2-NISTP224ECDH-SHA2-NISTP192RSA2048-SHA256RSA1024-SHA1DIFFIE-HELL-MAN-GROUP-EXCHANGE-SHA256DIFFIE-HELL-MAN-GROUP-EXCHANGE-SHA1DIFFIE-HELL-MAN-GROUP14-SHA1DIFFIE-HELL-MAN-GROUP1-SHA1

Encryption AES128-CTRAES128-CBC3DES-CBC

AES128-CTRAES128-CBCRIJNDAEL128-CBCBLOWFISH-CBC3DES-CBC

MAC HMAC-SHA1HMAC-SHA1-96

HMAC-SHA1HMAC-SHA1-96HMAC-MD5HMAC-MD5-96

TACACS+ TACACS+ does not comply with NIST SP 800-131A specification. When in strict mode, TACACS+ is disabled. However, it can be enabled, if required.

Acceptable



Table 4. List of Acceptable Cipher Suites in Compatibility Mode

Cipher

ID

Key Exchange

Authentication

Encryption

MAC Cipher Name

0xC027 ECDHE RSA AES_128_CBC

SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256


SHA1 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

0xC012 ECDHE RSA 3DES SHA1 SSL_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA

0xC011 ECDHE RSA SHA1 SSL_ECDHE_RSA_WITH_RC4_128_SHA

0x002F RSA RSA AES_128_CBC

SHA1 TLS_RSA_WITH_AES_128_CBC_SHA

0x003C RSA RSA AES_128_CBC

SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256

0x0005 RSA RSA SHA1 SSL_RSA_WITH_RC4_128_SHA


The following cipher suites are acceptable (listed in the order of preference) when the RackSwitch G8272 is in strict mode:

Configuring Strict Mode

To change the switch mode to boot strict mode, use the following command:

When strict mode is enabled, you will see the following message:

For SNMPv3 default users, see “SNMP Version 3” on page 531.

When strict mode is disabled, the following message is displayed:

0x000A RSA RSA 3DES SHA1 SSL_RSA_WITH_3DES_EDE_CBC_SHA

0x0033 DHE RSA AES128_CBC

SHA1 TLS_DHE_RSA_WITH_AES_128_CBC_SHA

0x0067 DHE RSA AES_128_CBC

SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

0x0016 DHE RSA 3DES SHA1 SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA

Table 5. List of Acceptable Cipher Suites in Strict ModeCipher ID Key

Exchange

Authentication

Encryption MAC Cipher Name


SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256


SHA1 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

0xC012 ECDHE RSA 3DES SHA1 SSL_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA

0x0033 DHE RSA AES128_CBC

SHA1 TLS_DHE_RSA_WITH_AES_128_CBC_SHA

0x0067 DHE RSA AES_128_CBC

SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

0x0016 DHE RSA 3DES SHA1 SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA

0x002F RSA RSA AES_128_CBC

SHA1 TLS_RSA_WITH_AES_128_CBC_SHA

0x003C RSA RSA AES_128_CBC

SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256

0x000A RSA RSA 3DES SHA1 SSL_RSA_WITH_3DES_EDE_CBC_SHA

Table 4. List of Acceptable Cipher Suites in Compatibility Mode (continued)

Cipher

ID

Key Exchange

Authentication

Encryption

MAC Cipher Name

RS 8272(config)# [no] boot strict enable

Warning, security strict mode limits the cryptographic algorithms used by secure protocols on this switch. Please see the documentation for full details, and verify that peer devices support acceptable algorithms before enabling this mode. The mode change will take effect after reloading the switch and the configuration will be wiped during the reload. System will enter security strict mode with default factory configuration at next boot up.

Do you want SNMPV3 support old default users in strict mode (y/n)?

Warning, disabling security strict mode. The mode change will take effect after reloading the switch.


You must reboot the switch for the boot strict mode enable/disable to take effect.

SSL/TLS Version Limitation

Each of the following successive encryption protocol versions provide more security and less compatibility: SSLv3, TLS1.0, TLS1.1, TLS1.2. When negotiating the encryption protocol during the SSL handshake, the switch will accept, by default, the latest (and most secure) protocol version supported by the client equipment. To enforce a minimal level of security acceptable for the connections, use the following command:

Limitations

In Lenovo N/OS 8.2, consider the following limitation/restrictions if you need to operate the switch in boot strict mode:

Power ITEs and High-Availability features do not comply with NIST SP 800-131A specification.

The G8272 will not discover Platform agents/Common agents that are not in strict mode.

Web browsers that do not use TLS 1.2 cannot be used.

Limited functions of the switch managing Windows will be available.

RS 8272(config)# ssl minimumversion tls10|tls11|tls12



Chapter 2. Initial Setup

To help with the initial process of configuring your switch, the Lenovo Networking OS software includes a Setup utility. The Setup utility prompts you step-by-step to enter all the necessary information for basic configuration of the switch.

Setup can be activated manually from the command line interface any time after login.


Information Needed for SetupSetup requests the following information: Basic system information

Date & time Whether to use Spanning Tree Group or not

Optional configuration for each port Speed, duplex, flow control, and negotiation mode (as appropriate) Whether to use VLAN trunk mode/tagging or not (as appropriate)

Optional configuration for each VLAN Name of VLAN Which ports are included in the VLAN

Optional configuration of IP parameters IP address/mask and VLAN for each IP interface IP addresses for default gateway Whether IP forwarding is enabled or not

Default Setup OptionsThe Setup prompt appears automatically whenever you login as the system administrator under the factory default settings.

1. Connect to the switch. After connecting, the login prompt appears.

2. Enter admin as the default administrator password.Note: If the default admin login is unsuccessful, or if the administrator Main Menu appears instead, the system configuration has probably been changed from the factory default settings. If desired, return the switch to its factory default configuration.

3. Enter y to begin the initial configuration of the switch, or n to bypass the Setup facility.

Enter Password:

© Copyright Lenovo 2015 Chapter 2: Initial Setup 53

Stopping and Restarting Setup ManuallyStopping Setup

To abort the Setup utility, press <Ctrl-C> during any Setup question. When you abort Setup, the system will prompt:

Enter n to abort Setup, or y to restart the Setup program at the beginning.

Restarting Setup

You can restart the Setup utility manually at any time by entering the following command at the configuration prompt:

Would you like to run from top again? [y/n]

RS 8272(config)# setup


Setup Part 1: Basic System ConfigurationWhen Setup is started, the system prompts:

1. Enter y if you will be configuring VLANs. Otherwise enter n.If you decide not to configure VLANs during this session, you can configure them later using the configuration menus, or by restarting the Setup facility. For more information on configuring VLANs, see the Lenovo Networking OS Application Guide. Next, the Setup utility prompts you to input basic system information.

2. Enter the year of the current date at the prompt:

Enter the four-digits that represent the year. To keep the current year, press <Enter>.

3. Enter the month of the current system date at the prompt:

Enter the month as a number from 1 to 12. To keep the current month, press <Enter>.

4. Enter the day of the current date at the prompt:

Enter the date as a number from 1 to 31. To keep the current day, press <Enter>.

The system displays the date and time settings:

5. Enter the hour of the current system time at the prompt:

Enter the hour as a number from 00 to 23. To keep the current hour, press <Enter>.

6. Enter the minute of the current time at the prompt:

Enter the minute as a number from 00 to 59. To keep the current minute, press <Enter>.

"Set Up" will walk you through the configuration of System Date and Time, Spanning Tree, Port Speed/Mode, VLANs, and IP interfaces. [type CtrlC to abort "Set Up"]

System Date:Enter year [2009]:

System Date:Enter month [1]:

Enter day [3]:

System clock set to 18:55:36 Wed Jan 28, 2009.

System Time:Enter hour in 24hour format [18]:

Enter minutes [55]:


7. Enter the seconds of the current time at the prompt:

Enter the seconds as a number from 00 to 59. To keep the current second, press <Enter>. The system then displays the date and time settings:

8. Turn Spanning Tree Protocol on or off at the prompt:

Enter y to turn off Spanning Tree, or enter n to leave Spanning Tree on.

Enter seconds [37]:

System clock set to 8:55:36 Wed Jan 28, 2009.

Spanning Tree:Current Spanning Tree Group 1 setting: ONTurn Spanning Tree Group 1 OFF? [y/n]


Setup Part 2: Port ConfigurationNote: When configuring port options for your switch, some prompts and options may be different.

1. Select whether you will configure VLANs and VLAN trunk mode/tagging for ports:

If you wish to change settings for VLANs, enter y, or enter n to skip VLAN configuration. Note: The sample screens that appear in this document might differ slightly from the screens displayed by your system. Screen content varies based on the firmware versions and options that are installed.

2. Select the port to configure, or skip port configuration at the prompt:

If you wish to change settings for individual ports, enter the number of the port you wish to configure. To skip port configuration, press <Enter> without specifying any port and go to “Setup Part 3: VLANs” on page 58.

3. Configure Gigabit Ethernet port flow parameters.

The system prompts:

Enter rx to enable receive flow control, tx for transmit flow control, both to enable both, or none to turn flow control off for the port. To keep the current setting, press <Enter>.

4. Configure Gigabit Ethernet port autonegotiation mode.

If you selected a port that has a Gigabit Ethernet connector, the system prompts:

Enter on to enable port autonegotiation, off to disable it, or press <Enter> to keep the current setting.

5. If configuring VLANs, enable or disable VLAN trunk mode/tagging for the port.

If you have selected to configure VLANs back in Part 1, the system prompts:

Port Config:Will you configure VLANs and VLAN Tagging/TrunkMode for ports? [y/n]

Gig Link Configuration:Port Flow Control:Current Port EXT1 flow control setting: bothEnter new value ["rx"/"tx"/"both"/"none"]:

Port Auto Negotiation:Current Port EXT1 autonegotiation: onEnter new value ["on"/"off"]:

Port VLAN tagging/trunk mode config (tagged/trunk mode port can be a member of multiple VLANs)Current VLAN tagging/trunk mode support: disabledEnter new VLAN tagging/trunk mode support [d/e]:


Enter d to disable VLAN trunk mode/tagging for the port or enter e to enable VLAN tagging for the port. To keep the current setting, press <Enter>.

6. The system prompts you to configure the next port:

When you are through configuring ports, press <Enter> without specifying any port. Otherwise, repeat the steps in this section.

Enter port (164):


Setup Part 3: VLANsIf you chose to skip VLANs configuration back in Part 2, skip to “Setup Part 4: IP Configuration” on page 59.

1. Select the VLAN to configure, or skip VLAN configuration at the prompt:

If you wish to change settings for individual VLANs, enter the number of the VLAN you wish to configure. To skip VLAN configuration, press <Enter> without typing a VLAN number and go to “Setup Part 4: IP Configuration” on page 59.

2. Enter the new VLAN name at the prompt:

Entering a new VLAN name is optional. To use the pending new VLAN name, press <Enter>.

3. Enter the VLAN port numbers:

Enter each port, by port number or port alias, and confirm placement of the port into this VLAN. When you are finished adding ports to this VLAN, press <Enter> without specifying any port.

4. Configure Spanning Tree Group membership for the VLAN:

5. The system prompts you to configure the next VLAN:

Repeat the steps in this section until all VLANs have been configured. When all VLANs have been configured, press <Enter> without specifying any VLAN.

VLAN Config:Enter VLAN number from 2 to 4094, NULL at end:

Current VLAN name: VLAN 2Enter new VLAN name:

Define Ports in VLAN:Current VLAN 2: emptyEnter ports one per line, NULL at end:

Spanning Tree Group membership:Enter new Spanning Tree Group index [1127]:

VLAN Config:Enter VLAN number from 2 to 4094, NULL at end:


Setup Part 4: IP ConfigurationThe system prompts for IPv4 parameters.

Although the switch supports both IPv4 and IPv6 networks, the Setup utility permits only IPv4 configuration. For IPv6 configuration, see “Internet Protocol Version 6” on page 357|.

IP Interfaces

IP interfaces are used for defining the networks to which the switch belongs.

Up to 126 IP interfaces can be configured on the RackSwitch G8272 (G8272). The IP address assigned to each IP interface provides the switch with an IP presence on your network. No two IP interfaces can be on the same IP network. The interfaces can be used for connecting to the switch for remote configuration, and for routing between subnets and VLANs (if used).

1. Select the IP interface to configure, or skip interface configuration at the prompt:

If you wish to configure individual IP interfaces, enter the number of the IP interface you wish to configure. To skip IP interface configuration, press <Enter> without typing an interface number and go to “Default Gateways” on page 61.

2. For the specified IP interface, enter the IP address in IPv4 dotted decimal notation:

To keep the current setting, press <Enter>.

3. At the prompt, enter the IPv4 subnet mask in dotted decimal notation:

To keep the current setting, press <Enter>.If configuring VLANs, specify a VLAN for the interface.

This prompt appears if you selected to configure VLANs back in Part 1:

Enter the number for the VLAN to which the interface belongs, or press <Enter> without specifying a VLAN number to accept the current setting.

IP Config:

IP interfaces:Enter interface number: (1126)

Current IP address: 0.0.0.0Enter new IP address:

Current subnet mask: 0.0.0.0Enter new subnet mask:

Current VLAN: 1Enter new VLAN [14094]:


4. At the prompt, enter y to enable the IP interface, or n to leave it disabled:

5. The system prompts you to configure another interface:

Repeat the steps in this section until all IP interfaces have been configured. When all interfaces have been configured, press <Enter> without specifying any interface number.

Loopback Interfaces

A loopback interface provides an IP address, but is not otherwise associated with a physical port or network entity. Essentially, it is a virtual interface that is perceived as being “always available” for higher-layer protocols to use and advertise to the network, regardless of other connectivity.

Loopback interfaces improve switch access, increase reliability, security, and provide greater flexibility in Layer 3 network designs. They can be used for many different purposes, but are most commonly for management IP addresses, router IDs for various protocols, and persistent peer IDs for neighbor relationships.

In Lenovo N/OS 8.2, loopback interfaces have been expanded for use with routing protocols such as OSPF and BGP. Loopback interfaces can also be specified as the source IP address for syslog, SNMP, RADIUS, TACACS+, NTP, and router IDs.

Loopback interfaces must be configured before they can be used in other features. Up to five loopback interfaces are currently supported. They can be configured using the following commands:

Using Loopback Interfaces for Source IP Addresses

The switch can use loopback interfaces to set the source IP addresses for a variety of protocols. This assists in server security, as the server for each protocol can be configured to accept protocol packets only from the expected loopback address block. It may also make is easier to locate or process protocol information, since packets have the source IP address of the loopback interface, rather than numerous egress interfaces.

Configured loopback interfaces can be applied to the following protocols:

Syslogs

SNMP traps

Enable IP interface? [y/n]

Enter interface number: (1126)

RS 8272(config)# interface loopback <1-5>RS 8272(configiploopback)# [no] ip address <IPv4 address> <mask> enableRS 8272(configiploopback)# exit

RS 8272(config)# logging sourceinterface loopback <1-5>

RS 8272(config)# snmpserver trapsource loopback <1-5>


RADIUS

TACACS+

NTP

Loopback Interface Limitation ARP is not supported. Loopback interfaces will ignore ARP requests. Loopback interfaces cannot be assigned to a VLAN.

Default Gateways

To set up a default gateway:

1. At the prompt, select an IP default gateway for configuration, or skip default gateway configuration:

Enter the number for the IP default gateway to be configured. To skip default gateway configuration, press <Enter> without typing a gateway number and go to “IP Routing” on page 61.

2. At the prompt, enter the IPv4 address for the selected default gateway:

Enter the IPv4 address in dotted decimal notation, or press <Enter> without specifying an address to accept the current setting.

3. At the prompt, enter y to enable the default gateway, or n to leave it disabled:

4. The system prompts you to configure another default gateway:

Repeat the steps in this section until all default gateways have been configured. When all default gateways have been configured, press <Enter> without specifying any number.

IP Routing

When IP interfaces are configured for the various IP subnets attached to your switch, IP routing between them can be performed entirely within the switch. This eliminates the need to send inter-subnet communication to an external router

RS 8272(config)# ip radius sourceinterface loopback <1-5>

RS 8272(config)# ip tacacs sourceinterface loopback <1-5>

RS 8272(config)# ntp source loopback <1-5>

IP default gateways:Enter default gateway number: (14)

Current IP address: 0.0.0.0Enter new IP address:

Enable default gateway? [y/n]

Enter default gateway number: (14)


device. Routing on more complex networks, where subnets may not have a direct presence on the G8272, can be accomplished through configuring static routes or by letting the switch learn routes dynamically.

This part of the Setup program prompts you to configure the various routing parameters.

At the prompt, enable or disable forwarding for IP Routing:

Enter y to enable IP forwarding. To disable IP forwarding, enter n. To keep the current setting, press <Enter>.

Enable IP forwarding? [y/n]


Setup Part 5: Final Steps1. When prompted, decide whether to restart Setup or continue:

Enter y to restart the Setup utility from the beginning, or n to continue.

2. When prompted, decide whether you wish to review the configuration changes:

Enter y to review the changes made during this session of the Setup utility. Enter n to continue without reviewing the changes. We recommend that you review the changes.

3. Next, decide whether to apply the changes at the prompt:

Enter y to apply the changes, or n to continue without applying. Changes are normally applied.

4. At the prompt, decide whether to make the changes permanent:

Enter y to save the changes to flash. Enter n to continue without saving the changes. Changes are normally saved at this point.

5. If you do not apply or save the changes, the system prompts whether to abort them:

Enter y to discard the changes. Enter n to return to the “Apply the changes?” prompt.Note: After initial configuration is complete, it is recommended that you change the default passwords.

Would you like to run from top again? [y/n]

Review the changes made? [y/n]

Apply the changes? [y/n]

Save changes to flash? [y/n]

Abort all changes? [y/n]


Optional Setup for Telnet SupportNote: This step is optional. Perform this procedure only if you are planning on connecting to the G8272 through a remote Telnet connection.

Telnet is enabled by default. To change the setting, use the following command:

RS 8272(config)# no access telnet


Chapter 3. Switch Software Management

The switch software image is the executable code running on the G8272. A version of the image comes pre-installed on the device. As new versions of the image are released, you can upgrade the software running on your switch. To get the latest version of software supported for your G8272, go to the following website:

http://www.lenovo.com/support/

To determine the software version currently used on the switch, use the following switch command:

The typical upgrade process for the software image consists of the following steps:

Load a new software image and boot image onto an FTP or TFTP server on your network.

Transfer the new images to your switch.

Specify the new software image as the one which will be loaded into switch memory the next time a switch reset occurs.

Reset the switch.

For instructions on the typical upgrade process, see “Loading New Software to Your Switch” on page 66.

CAUTION:Although the typical upgrade process is all that is necessary in most cases, upgrading from (or reverting to) some versions of Lenovo Networking OS requires special steps prior to or after the software installation process. Please be sure to follow all applicable instructions in the release notes document for the specific software release to ensure that your switch continues to operate as expected after installing new software.

RS 8272# show boot

http://www.lenovo.com/support/


Loading New Software to Your SwitchThe G8272 can store up to two different switch software images (called image1 and image2) as well as special boot software (called boot). When you load new software, you must specify where it is placed: either into image1, image2, or boot.

For example, if your active image is currently loaded into image1, you would probably load the new image software into image2. This lets you test the new software and reload the original active image (stored in image1), if needed.

CAUTION:When you upgrade the switch software image, always load the new boot image and the new software image before you reset the switch. If you do not load a new boot image, your switch might not boot properly (To recover, see “Recovering from a Failed Upgrade” on page 70).

To load a new software image to your switch, you will need the following: The image and boot software loaded on an FTP or TFTP server on your network.

Note: Be sure to download both the new boot file and the new image file.

The hostname or IP address of the FTP or TFTP server

Note: The DNS parameters must be configured if specifying hostnames.

The name of the new software image or boot file

When the software requirements are met, use one of the following procedures to download the new software to your switch. You can use the ISCLI, USB, or the BBI to download and activate new software.

Loading Software via the ISCLI

1. In Privileged EXEC mode, enter the following command:

2. Enter the hostname or IP address of the FTP or TFTP server.

3. Enter the name of the new software file on the server.

The exact form of the name will vary by server. However, the file location is normally relative to the FTP or TFTP directory (for example, tftpboot).

4. If required by the FTP or TFTP server, enter the appropriate username and password.

Router# copy tftp|ftp image1|image2|bootimage

Address or name of remote host: <name or IP address>

Source file name: <filename>

© Copyright Lenovo 2015 Chapter 3: Switch Software Management 67

5. The switch will prompt you to confirm your request.

Once confirmed, the software will begin loading into the switch.

6. When loading is complete, use the following commands to enter Global Configuration mode to select which software image (image1 or image2) you want to run in switch memory for the next reboot:

The system will then verify which image is set to be loaded at the next reset:

7. Reboot the switch to run the new software:

The system prompts you to confirm your request. Once confirmed, the switch will reboot to use the new software.

Loading Software via BBI

You can use the Browser-Based Interface to load software onto the G8272. The software image to load can reside in one of the following locations:

FTP server

TFTP server

Local computer

After you log onto the BBI, perform the following steps to load a software image:

1. Click the Configure context tab in the toolbar.

2. In the Navigation Window, select System > Config/Image Control.

The Switch Image and Configuration Management page appears.

3. If you are loading software from your computer (HTTP client), skip this step and go to the next. Otherwise, if you are loading software from a FTP/TFTP server, enter the server’s information in the FTP/TFTP Settings section.

4. In the Image Settings section, select the image version you want to replace (Image for Transfer).

If you are loading software from a FTP/TFTP server, enter the file name and click Get Image.

If you are loading software from your computer, click Browse.

In the File Upload Dialog, select the file and click OK. Then click Download via Browser.

Once the image has loaded, the page refreshes to show the new software.

Router# configure terminalRouter(config)# boot image image1|image2

Next boot will use switch software image1 instead of image2.

Router(config)# reload


USB Options

You can insert a USB drive into the USB port on the G8272 and use it to work with switch image and configuration files. You can boot the switch using files located on the USB drive, or copy files to and from the USB drive.

To safely remove the USB drive, first use the following command to un-mount the USB file system: system usbeject

Command mode: Global configuration

USB BootUSB Boot allows you to boot the switch with a software image file, boot file, or configuration file that resides on a USB drive inserted into the USB port. Use the following command to enable or disable USB Boot: [no] boot usbboot enable

Command mode: Global configuration

When enabled, when the switch is reset/reloaded, it checks the USB port. If a USB drive is inserted into the port, the switch checks the root directory on the USB drive for software and image files. If a valid file is present, the switch loads the file and boots using the file. Note: The following file types are supported: FAT32, NTFS (read-only), EXT2, and EXT3.

The following list describes the valid file names, and describes the switch behavior when it recognizes them. The file names must be exactly as shown, or the switch will not recognize them.

RS8272_Boot.imgThe switch replaces the current boot image with the new image, and boots with the new image.

RS8272_OS.imgThe switch boots with the new software image. The existing images are not affected.

RS8272_replace1_OS.imgThe switch replaces the current software image1 with the new image, and boots with the new image. RS8272_replace1_OS.img takes precedence over RS8272_OS.img

RS8272_replace2_OS.img takes precedence over RS8272_OS.img

RSG8272.cfgThe switch boots with the new configuration file. The existing configuration files (active and backup) are not affected.

RSG8272_replace.cfgThe switch replaces the active configuration file with the new file, and boots with the new file. This file takes precedence over any other configuration files that may be present on the USB drive.


If more than one valid file is present, the switch loads all valid files and boots with them. For example, you may simultaneously load a new boot file, image file, and configuration file from the USB drive.

The switch ignores any files that do not match the valid file names or that have the wrong format.

USB CopyIf a USB drive is inserted into the USB port, you can copy files from the switch to the USB drive, or from the USB drive to the switch. USB Copy is available only for software image 1 and the active configuration.

Copy to USB

Use the following command to copy a file from the switch to the USB drive (Privileged EXEC mode):

In this example, the active configuration file is copied to a directory on the USB drive:

Copy from USB

Use the following command to copy a file from the USB drive to the switch:

In this example, the active configuration file is copied from a directory on the USB drive:

The new file replaces the current file. Note: Do not use two consecutive dot characters ( .. ). Do not use a slash character ( / ) to begin a filename.

usbcopy tousb <filename> boot|image1|active|syslog|crashdump

G8272(config)# usbcopy tousb a_folder/myconfig.cfg active

usbcopy fromusb <filename> boot|image1|active

G8272(config)# usbcopy fromusb a_folder/myconfig.cfg active


The Boot Management MenuThe Boot Management menu allows you to switch the software image, reset the switch to factory defaults, or to recover from a failed software download.

You can interrupt the boot process and enter the Boot Management menu from the serial console port. When the system displays Memory Test, press <Shift B>. The Boot Management menu appears.

The Boot Management menu allows you to perform the following actions:

To change the booting image, press I and follow the screen prompts.

To change the configuration block, press C and follow the screen prompts.

To reboot the switch, press Q. The booting process restarts.

To boot in recovery mode, press R and follow the screen prompts.

To exit the Boot Management menu, press E. The booting process continues.

Recovering from a Failed UpgradeUse the following procedure to recover from a failed software upgrade.

1. Connect a PC to the serial port of the switch.

2. Open a terminal emulator program that supports XModem Download (such as HyperTerminal or PuTTY) and select the following serial port characteristics:

Speed: 9600 bps

Data Bits: 8

Stop Bits: 1

Parity: None

Flow Control: None

Resetting the System ...Memory Test ................................

Boot Menu mode

FLASH: 16 MBL2: 512 KB enabledPCIe1: Root Complex of PCIe, x2, regs @ 0xffe0a000PCIe1: Bus 00 01MMC: FSL_ESDHC: 0Net: eTSEC1, eTSEC2 [PRIME]

Boot Management Menu I Change booting image C Change configuration block R Boot in recovery mode (tftp and xmodem download of images to recover switch) Q Reboot E ExitPlease choose your menu option: ICurrent boot image is 1. Enter image to boot: 1 or 2: 2Booting from image 2


3. Boot the switch and access the Boot Management menu by pressing <Shift B> while the Memory Test is in progress and the dots are being displayed.

4. Select R for Recovery mode, then select one of the following options:

T – Configure networking and tftp download an image

X – Use xmodem 1K to serial download an image

P – Physical presence (low security mode)

F – Filesystem check

R – Reboot

E – Exit

5. Select X for Xmodem download. When you see the following message, change the Serial Port characteristics to 115200 bps:

6. Press <Enter> to set the system into download accept mode. When the readiness meter displays (a series of “C” characters), start XModem on your terminal emulator.

## Switch baudrate to 115200 bps and press ENTER ...



Part 2: Securing the Switch



Chapter 4. Securing Administration

Secure switch management is needed for environments that perform significant management functions across the Internet. Common functions for secured management are described in the following sections:

“Secure Shell and Secure Copy” on page 76

“End User Access Control” on page 80Note: SNMP read and write functions are enabled by default. For best security practices, if SNMP is not needed for your network, it is recommended that you disable these functions prior to connecting the switch to the network (see “Using Simple Network Management Protocol” on page 38).


Secure Shell and Secure CopyBecause using Telnet does not provide a secure connection for managing a G8272, Secure Shell (SSH) and Secure Copy (SCP) features have been included for G8272 management. SSH and SCP use secure tunnels to encrypt and secure messages between a remote administrator and the switch.

SSH is a protocol that enables remote administrators to log securely into the G8272 over a network to execute management commands.

SCP is typically used to copy files securely from one machine to another. SCP uses SSH for encryption of data on the network. On a G8272, SCP is used to download and upload the switch configuration via secure channels.

Although SSH and SCP are disabled by default, enabling and using these features provides the following benefits: Identifying the administrator using Name/Password Authentication of remote administrators Authorization of remote administrators Determining the permitted actions and customizing service for individual

administrators Encryption of management messages Encrypting messages between the remote administrator and switch Secure copy support

Lenovo Networking OS implements the SSH version 2.0 standard and is confirmed to work with SSH version 2.0-compliant clients such as the following:

OpenSSH_5.4p1 for Linux

Secure CRT Version 5.0.2 (build 1021)

Putty SSH release 0.60

Configuring SSH/SCP Features on the Switch

SSH and SCP features are disabled by default. To change the SSH/SCP settings, using the following procedures.Note: To use SCP, you must first enable SSH.

To Enable or Disable the SSH Feature

Connect to the console port and enter the following command:

To Enable or Disable SCP Apply and Save

Enter the following command from the switch CLI to enable the SCP putcfg_apply and putcfg_apply_save commands:

RS 8272(config)# [no] ssh enable

RS 8272(config)# [no] ssh scpenable

© Copyright Lenovo 2015 Chapter 4: Securing Administration 77

Configuring the SCP Administrator Password

To configure the SCP-only administrator password, enter the following command (the default password is admin):

Using SSH and SCP Client Commands

This section shows the format for using some client commands. The following examples use 205.178.15.157 as the IP address of a sample switch.

To Log In to the Switch

Syntax:

Note: The 4 option (the default) specifies that an IPv4 switch address will be used. The 6 option specifies IPv6.

Example:

To Copy the Switch Configuration File to the SCP Host

Syntax:

Example:

To Load a Switch Configuration File from the SCP Host

Syntax:

Example:

RS 8272(config)# [no] ssh scppasswordChanging SCPonly Administrator password; validation required...Enter current administrator password: <password>Enter new SCPonly administrator password: <new password>Reenter new SCPonly administrator password: <new password>New SCPonly administrator password accepted.

>> ssh [4|6] <switch IP address>

-or->> ssh [4|6] <login name>@<switch IP address>

>> ssh [email protected]

>> scp [4|6] <username>@<switch IP address>:getcfg <local filename>

>> scp [email protected]:getcfg ad4.cfg

>> scp [4|6] <local filename> <username>@<switch IP address>:putcfg

>> scp ad4.cfg [email protected]:putcfg


To Apply and Save the Configuration

When loading a configuration file to the switch, the apply and save commands are still required for the configuration commands to take effect. The apply and save commands may be entered manually on the switch, or by using SCP commands.

Syntax:

Example:

The CLI diff command is automatically executed at the end of putcfg to notify the remote client of the difference between the new and the current configurations.

putcfg_apply runs the apply command after the putcfg is done.

putcfg_apply_save saves the new configuration to the flash after putcfg_apply is done.

The putcfg_apply and putcfg_apply_save commands are provided because extra apply and save commands are usually required after a putcfg; however, an SCP session is not in an interactive mode.

To Copy the Switch Image and Boot Files to the SCP Host

Syntax:

Example:

To Load Switch Configuration Files from the SCP Host

Syntax:

Example:

>> scp [4|6] <local filename> <username>@<switch IP address>:putcfg_apply>> scp [4|6] <local filename> <username>@<switch IP address>:putcfg_apply_save

>> scp ad4.cfg [email protected]:putcfg_apply>> scp ad4.cfg [email protected]:putcfg_apply_save

>> scp [4|6] <username>@<switch IP address>:getimg1 <local filename> >> scp [4|6] <username>@<switch IP address>:getimg2 <local filename> >> scp [4|6] <username>@<switch IP address>:getboot <local filename>

>> scp [email protected]:getimg1 6.1.0_os.img

>> scp [4|6] <local filename> <username>@<switch IP address>:putimg1>> scp [4|6] <local filename> <username>@<switch IP address>:putimg2>> scp [4|6] <local filename> <username>@<switch IP address>:putboot

>> scp 6.1.0_os.img [email protected]:putimg1


SSH and SCP Encryption of Management Messages

The following encryption and authentication methods are supported for SSH and SCP:

Server Host Authentication: Client RSA authenticates the switch at the beginning of every connection

Key Exchange: RSA

Encryption: 3DES-CBC

User Authentication: Local password authentication, RADIUS

Generating RSA Host Key for SSH Access

To support the SSH host feature, an RSA host key is required. The host key is 2048 bits and is used to identify the G8272.

To configure RSA host key, first connect to the G8272 through the console port (commands are not available via external Telnet connection), and enter the following command to generate it manually.

When the switch reboots, it will retrieve the host key from the FLASH memory.Note: The switch will perform only one session of key/cipher generation at a time. Thus, an SSH/SCP client will not be able to log in if the switch is performing key generation at that time. Also, key generation will fail if an SSH/SCP client is logging in at that time.

SSH/SCP Integration with Radius Authentication

SSH/SCP is integrated with RADIUS authentication. After the RADIUS server is enabled on the switch, all subsequent SSH authentication requests will be redirected to the specified RADIUS servers for authentication. The redirection is transparent to the SSH clients.

SSH/SCP Integration with TACACS+ Authentication

SSH/SCP is integrated with TACACS+ authentication. After the TACACS+ server is enabled on the switch, all subsequent SSH authentication requests will be redirected to the specified TACACS+ servers for authentication. The redirection is transparent to the SSH clients.

RS 8272(config)# ssh generatehostkey


End User Access ControlLenovo N/OS allows an administrator to define end user accounts that permit end users to perform operation tasks via the switch CLI commands. Once end user accounts are configured and enabled, the switch requires username/password authentication.

For example, an administrator can assign a user, who can then log into the switch and perform operational commands (effective only until the next switch reboot).

Considerations for Configuring End User Accounts

Note the following considerations when you configure end user accounts:

A maximum of 20 user IDs are supported on the switch.

N/OS supports end user support for console, Telnet, BBI, and SSHv2 access to the switch.

If RADIUS authentication is used, the user password on the Radius server will override the user password on the G8272. Also note that the password change command only modifies only the user password on the switch and has no effect on the user password on the Radius server. Radius authentication and user password cannot be used concurrently to access the switch.

Passwords for end users can be up to 128 characters in length for TACACS, RADIUS, Telnet, SSH, Console, and Web access.

Strong Passwords

The administrator can require use of Strong Passwords for users to access the G8272. Strong Passwords enhance security because they make password guessing more difficult.

The following rules apply when Strong Passwords are enabled:

Minimum length: 8 characters; maximum length: 64 characters.

Must contain at least one uppercase alphabet.

Must contain at least one lowercase alphabet.

Must contain at least one number.

Must contain at least one special character. Supported special characters: ! “ # % & ‘ ( ) ; < = >> ? [\] * + , - . / : ^ _ | ~

Cannot be same as the username.

No consecutive four characters can be the same as in the old password.

When strong password is enabled, users can still access the switch using the old password but will be advised to change to a strong password while attempting to log in.

Strong password requirement can be enabled using the following command:

RS 8272(config)# access user strongpassword enable


The administrator can choose the number of days allowed before each password expires. When a strong password expires, the user is allowed to log in one last time to change the password. A warning provides advance notice for users to change the password.

User Access Control

The end-user access control commands allow you to configure end-user accounts.

Setting up User IDs

Up to 20 user IDs can be configured. Use the following commands to define any user name and set the user password at the resulting prompts:

Defining a User’s Access Level

The end user is by default assigned to the user access level (also known as class of service, or COS). COS for all user accounts have global access to all resources except for User COS, which has access to view only resources that the user owns. For more information, see Table 6 on page 86.

To change the user’s level, select one of the following options:

Validating a User’s Configuration

Enabling or Disabling a User

An end user account must be enabled before the switch recognizes and permits login under the account. Once enabled, the switch requires any user to enter both username and password.

Locking Accounts

To protect the switch from unauthorized access, the account lockout feature can be enabled. By default, account lockout is disabled. To enable this feature, ensure the strong password feature is enabled (See “Strong Passwords” on page 80). Then use the following command:

RS 8272(config)# access user 1 name <1-8 characters>RS 8272(config)# access user 1 password

Changing user1 password; validation required:Enter current admin password: <current administrator password>Enter new user1 password: <new user password>Reenter new user1 password: <new user password>New user1 password accepted.

RS 8272(config)# access user 1 level user|operator|administrator

RS 8272# show access user uid 1

RS 8272(config)# [no] access user 1 enable

RS 8272(config)# access user strongpassword lockout


After multiple failed login attempts, the switch locks the user account if lockout has been enabled on the switch.

Re-enabling Locked Accounts

The administrator can re-enable a locked account by reloading the switch or by using the following command:

However, the above command cannot be used to re-enable an account disabled by the administrator.

To re-enable all locked accounts, use the following command:

Listing Current Users

The following command displays defined user accounts and whether or not each user is currently logged into the switch.

Logging into an End User Account

Once an end user account is configured and enabled, the user can login to the switch using the username/password combination. The level of switch access is determined by the COS established for the end user account.

Password Fix-Up Mode

Password Fix-Up Mode enables admin user account recovery if administrator access is lost. You must connect to the switch over the serial console and log in using the password “forgetME!”. This enables the admin account if disabled and a new administrator password can be entered.

To disable the Password Fix-Up functionality, use the following command:

RS 8272(config)# access user strongpassword clear local user lockout username <user name>

RS 8272(config)# access user strongpassword clear local user lockout all

RS 8272# show access user

Usernames:user Enabled offlineoper Disabled offlineadmin Always Enabled online 1 session

Current User ID table:1: name jane , ena, cos user , password valid, online 1 session2: name john , ena, cos user , password valid, online 2 sessions

RS 8272(config)# no access user passwordrecovery


Chapter 5. Authentication & Authorization Protocols

Secure switch management is needed for environments that perform significant management functions across the Internet. The following are some of the functions for secured IPv4 management and device access:

“RADIUS Authentication and Authorization” on page 84

“TACACS+ Authentication” on page 88

“LDAP Authentication and Authorization” on page 92Note: Lenovo Networking OS 8.2 does not support IPv6 for RADIUS, TACACS+, or LDAP.


RADIUS Authentication and AuthorizationLenovo N/OS supports the RADIUS (Remote Authentication Dial-in User Service) method to authenticate and authorize remote administrators for managing the switch. This method is based on a client/server model. The Remote Access Server (RAS)—the switch—is a client to the back-end database server. A remote user (the remote administrator) interacts only with the RAS, not the back-end server and database.

RADIUS authentication consists of the following components: A protocol with a frame format that utilizes UDP over IP (based on RFC 2138 and

2866) A centralized server that stores all the user authorization information A client: in this case, the switch

The G8272—acting as the RADIUS client—communicates to the RADIUS server to authenticate and authorize a remote administrator using the protocol definitions specified in RFC 2138 and 2866. Transactions between the client and the RADIUS server are authenticated using a shared key that is not sent over the network. In addition, the remote administrator passwords are sent encrypted between the RADIUS client (the switch) and the back-end RADIUS server.

How RADIUS Authentication Works

The RADIUS authentication process follows these steps:

1. A remote administrator connects to the switch and provides a user name and password.

2. Using Authentication/Authorization protocol, the switch sends request to authentication server.

3. The authentication server checks the request against the user ID database.

4. Using RADIUS protocol, the authentication server instructs the switch to grant or deny administrative access.

Configuring RADIUS on the Switch

Use the following procedure to configure Radius authentication on your switch.

1. Configure the IPv4 addresses of the Primary and Secondary RADIUS servers, and enable RADIUS authentication.

Note: You can use a configured loopback address as the source address so the RADIUS server accepts requests only from the expected loopback address block. Use the following command to specify the loopback interface:RS 8272(config)# ip radius sourceinterface loopback <1-5>

RS 8272(config)# radiusserver primaryhost 10.10.1.1RS 8272(config)# radiusserver secondaryhost 10.10.1.2RS 8272(config)# radiusserver enable

© Copyright Lenovo 2015 Chapter 5: Authentication & Authorization Protocols 85

2. Configure the RADIUS secret.

3. If desired, you may change the default UDP port number used to listen to RADIUS.

The well-known port for RADIUS is 1812.

4. Configure the number retry attempts for contacting the RADIUS server, and the timeout period.

RADIUS Authentication Features in Lenovo N/OS

N/OS supports the following RADIUS authentication features:

Supports RADIUS client on the switch, based on the protocol definitions in RFC 2138 and RFC 2866.

Allows RADIUS secret password up to 32 bytes and less than 16 octets.

Supports secondary authentication server so that when the primary authentication server is unreachable, the switch can send client authentication requests to the secondary authentication server. Use the following command to show the currently active RADIUS authentication server:

Supports user-configurable RADIUS server retry and time-out values: Time-out value = 1-10 seconds Retries = 1-3The switch will time out if it does not receive a response from the RADIUS server in 1-3 retries. The switch will also automatically retry connecting to the RADIUS server before it declares the server down.

Supports user-configurable RADIUS application port. The default is 1645/UDP-based on RFC 2138. Port 1812 is also supported.

Allows network administrator to define privileges for one or more specific users to access the switch at the RADIUS user database.

RS 8272(config)# radiusserver primaryhost 10.10.1.1 key <1-32 character secret>

RS 8272(config)# radiusserver secondaryhost 10.10.1.2 key <1-32 character secret>

RS 8272(config)# radiusserver port <UDP port number>

RS 8272(config)# radiusserver retransmit 3RS 8272(config)# radiusserver timeout 5

RS 8272# show radiusserver


Switch User Accounts

The user accounts listed in Table 6 can be defined in the RADIUS server dictionary file.

RADIUS Attributes for Lenovo N/OS User Privileges

When the user logs in, the switch authenticates his/her level of access by sending the RADIUS access request, that is, the client authentication request, to the RADIUS authentication server.

If the remote user is successfully authenticated by the authentication server, the switch will verify the privileges of the remote user and authorize the appropriate access. The administrator has two options: to allow backdoor access via Telnet, SSH, HTTP, or HTTPS; to allow secure backdoor access via Telnet, SSH, or BBI. Backdoor and secure backdoor provides access to the switch when the RADIUS servers cannot be reached.

The default G8272 setting for backdoor and secure backdoor access is disabled. Backdoor and secure backdoor access is always enabled on the console port.

Irrespective of backdoor/secure backdoor being enabled or not, you can always access the switch via the console port by using noradius as radius username. You can then enter the username and password configured on the switch. If you are trying to connect via SSH/Telnet/HTTP/HTTPS (not console port), there are two possibilities:

Backdoor is enabled: The switch acts like it is connecting via console.

Secure backdoor is enabled: You must enter the username: noradius. The switch checks if RADIUS server is reachable. If it is reachable, then you must authenticate via remote authentication server. Only if RADIUS server is not reachable, you will be prompted for local user/password to be authenticated against these local credentials.

Table 6. User Access Levels

User Account Description and Tasks Performed Password

User The User has no direct responsibility for switch management. They can view all switch status information and statistics but cannot make any configuration changes to the switch.

user

Operator The Operator manages all functions of the switch. The Operator can reset ports, except the management port.

oper

Administrator The super-user Administrator has complete access to all commands, information, and configuration commands on the switch, including the ability to change both the user and administrator passwords.

admin


All user privileges, other than those assigned to the Administrator, have to be defined in the RADIUS dictionary. RADIUS attribute 6 which is built into all RADIUS servers defines the administrator. The file name of the dictionary is RADIUS vendor-dependent. The following RADIUS attributes are defined for G8272 user privileges levels:

Table 7. Lenovo N/OS-proprietary Attributes for RADIUS

User Name/Access User-Service-Type Value

User Vendor-supplied 255

Operator Vendor-supplied 252

Admin Vendor-supplied 6


TACACS+ AuthenticationN/OS supports authentication and authorization with networks using the Cisco Systems TACACS+ protocol. The G8272 functions as the Network Access Server (NAS) by interacting with the remote client and initiating authentication and authorization sessions with the TACACS+ access server. The remote user is defined as someone requiring management access to the G8272 through a data port.

TACACS+ offers the following advantages over RADIUS:

TACACS+ uses TCP-based connection-oriented transport; whereas RADIUS is UDP-based. TCP offers a connection-oriented transport, while UDP offers best-effort delivery. RADIUS requires additional programmable variables such as re-transmit attempts and time-outs to compensate for best-effort transport, but it lacks the level of built-in support that a TCP transport offers.

TACACS+ offers full packet encryption whereas RADIUS offers password-only encryption in authentication requests.

TACACS+ separates authentication, authorization and accounting.

How TACACS+ Authentication Works

TACACS+ works much in the same way as RADIUS authentication as described on page 84.

1. Remote administrator connects to the switch and provides user name and password.

2. Using Authentication/Authorization protocol, the switch sends request to authentication server.

3. Authentication server checks the request against the user ID database.

4. Using TACACS+ protocol, the authentication server instructs the switch to grant or deny administrative access.

During a session, if additional authorization checking is needed, the switch checks with a TACACS+ server to determine if the user is granted permission to use a particular command.

TACACS+ Authentication Features in Lenovo N/OS

Authentication is the action of determining the identity of a user, and is generally done when the user first attempts to log in to a device or gain access to its services. N/OS supports ASCII inbound login to the device. PAP, CHAP and ARAP login methods, TACACS+ change password requests, and one-time password authentication are not supported.

Authorization

Authorization is the action of determining a user’s privileges on the device, and usually takes place after authentication.


The default mapping between TACACS+ authorization levels and N/OS management access levels is shown in Table 8. The authorization levels must be defined on the TACACS+ server.

Alternate mapping between TACACS+ authorization levels and N/OS management access levels is shown in Table 9. Use the following command to set the alternate TACACS+ authorization levels.

If the remote user is successfully authenticated by the authentication server, the switch verifies the privileges of the remote user and authorizes the appropriate access. The administrator has an option to allow secure backdoor access via Telnet/SSH. Secure backdoor provides switch access when the TACACS+ servers cannot be reached. You always can access the switch via the console port, by using notacacs and the administrator password, whether secure backdoor is enabled or not. Note: To obtain the TACACS+ backdoor password for your G8272, contact Technical Support.

Accounting

Accounting is the action of recording a user's activities on the device for the purposes of billing and/or security. It follows the authentication and authorization actions. If the authentication and authorization is not performed via TACACS+, there are no TACACS+ accounting messages sent out.

You can use TACACS+ to record and track software login access, configuration changes, and interactive commands.

The G8272 supports the following TACACS+ accounting attributes:

protocol (console/Telnet/SSH/HTTP/HTTPS)

start_time

stop_time

elapsed_time

Table 8. Default TACACS+ Authorization Levels

N/OS User Access Level TACACS+ level

user 0

oper 3

admin 6

RS 8272(config)# tacacsserver privilegemapping

Table 9. Alternate TACACS+ Authorization Levels

N/OS User Access Level TACACS+ level

user 0 - 1

oper 6 - 8

admin 14 - 15


disc_causeNote: When using the Browser-Based Interface, the TACACS+ Accounting Stop records are sent only if the Logout button on the browser is clicked.

Command Authorization and Logging

When TACACS+ Command Authorization is enabled, N/OS configuration commands are sent to the TACACS+ server for authorization. Use the following command to enable TACACS+ Command Authorization:

When TACACS+ Command Logging is enabled, N/OS configuration commands are logged on the TACACS+ server. Use the following command to enable TACACS+ Command Logging:

The following examples illustrate the format of N/OS commands sent to the TACACS+ server:

Configuring TACACS+ Authentication on the Switch

1. Configure the IPv4 addresses of the Primary and Secondary TACACS+ servers, and enable TACACS authentication.

Note: You can use a configured loopback address as the source address so the TACACS+ server accepts requests only from the expected loopback address block. Use the following command to specify the loopback interface:RS 8272(config)# ip tacacs sourceinterface loopback <1-5>

2. Configure the TACACS+ secret and second secret.

3. If desired, you may change the default TCP port number used to listen to TACACS+.

The well-known port for TACACS+ is 49.

RS 8272(config)# tacacsserver commandauthorization

RS 8272(config)# tacacsserver commandlogging

authorization request, cmd=shell, cmdarg=interface ipaccounting request, cmd=shell, cmdarg=interface ipauthorization request, cmd=shell, cmdarg=enableaccounting request, cmd=shell, cmdarg=enable

RS 8272(config)# tacacsserver primaryhost 10.10.1.1RS 8272(config)# tacacsserver primaryhost mgtportRS 8272(config)# tacacsserver secondaryhost 10.10.1.2RS 8272(config)# tacacsserver secondaryhost dataportRS 8272(config)# tacacsserver enable

RS 8272(config)# tacacsserver primaryhost 10.10.1.1 key <1-32 character secret>RS 8272(config)# tacacsserver secondaryhost 10.10.1.2 key

<1-32 character secret>

RS 8272(config)# tacacsserver port <TCP port number>


4. Configure the number of retry attempts, and the timeout period.

RS 8272(config)# tacacsserver retransmit 3RS 8272(config)# tacacsserver timeout 5


LDAP Authentication and AuthorizationN/OS supports the LDAP (Lightweight Directory Access Protocol) method to authenticate and authorize remote administrators to manage the switch. LDAP is based on a client/server model. The switch acts as a client to the LDAP server. A remote user (the remote administrator) interacts only with the switch, not the back-end server and database.

LDAP authentication consists of the following components: A protocol with a frame format that utilizes TCP over IP A centralized server that stores all the user authorization information A client: in this case, the switch

Each entry in the LDAP server is referenced by its Distinguished Name (DN). The DN consists of the user-account name concatenated with the LDAP domain name. If the user-account name is John, the following is an example DN:uid=John,ou=people,dc=domain,dc=com

Configuring the LDAP Server

G8272 user groups and user accounts must reside within the same domain. On the LDAP server, configure the domain to include G8272 user groups and user accounts, as follows:

User Accounts:Use the uid attribute to define each individual user account.

User Groups:Use the members attribute in the groupOfNames object class to create the user groups. The first word of the common name for each user group must be equal to the user group names defined in the G8272, as follows: admin

oper

user

Configuring LDAP Authentication on the Switch

1. Turn LDAP authentication on, then configure the IPv4 addresses of the Primary and Secondary LDAP servers.

2. Configure the domain name.

3. You may change the default TCP port number used to listen to LDAP (optional).

>> # ldapserver enable>> # ldapserver primaryhost 10.10.1.1 mgtport>> # ldapserver secondaryhost 10.10.1.2 dataport

>> # ldapserver domain <ou=people,dc=my-domain,dc=com>


The well-known port for LDAP is 389.

4. Configure the number of retry attempts for contacting the LDAP server, and the timeout period.

>> # ldapserver port <1-65000>

>> # ldapserver retransmit 3>> # ldapserver timeout 10



Chapter 6. 802.1X Port-Based Network Access Control

Port-Based Network Access control provides a means of authenticating and authorizing devices attached to a LAN port that has point-to-point connection characteristics. It prevents access to ports that fail authentication and authorization. This feature provides security to ports of the RackSwitch G8272 (G8272) that connect to blade servers.

The following topics are discussed in this section:

“Extensible Authentication Protocol over LAN” on page 96

“EAPoL Authentication Process” on page 97

“EAPoL Port States” on page 99

“Guest VLAN” on page 99

“Supported RADIUS Attributes” on page 100

“EAPoL Configuration Guidelines” on page 102


Extensible Authentication Protocol over LAN

Lenovo Networking OS can provide user-level security for its ports using the IEEE 802.1X protocol, which is a more secure alternative to other methods of port-based network access control. Any device attached to an 802.1X-enabled port that fails authentication is prevented access to the network and denied services offered through that port.

The 802.1X standard describes port-based network access control using Extensible Authentication Protocol over LAN (EAPoL). EAPoL provides a means of authenticating and authorizing devices attached to a LAN port that has point-to-point connection characteristics and of preventing access to that port in cases of authentication and authorization failures.

EAPoL is a client-server protocol that has the following components:

Supplicant or Client The Supplicant is a device that requests network access and provides the required credentials (user name and password) to the Authenticator and the Authenticator Server.

Authenticator The Authenticator enforces authentication and controls access to the network. The Authenticator grants network access based on the information provided by the Supplicant and the response from the Authentication Server. The Authenticator acts as an intermediary between the Supplicant and the Authentication Server: requesting identity information from the client, forwarding that information to the Authentication Server for validation, relaying the server’s responses to the client, and authorizing network access based on the results of the authentication exchange. The G8272 acts as an Authenticator.

Authentication ServerThe Authentication Server validates the credentials provided by the Supplicant to determine if the Authenticator ought to grant access to the network. The Authentication Server may be co-located with the Authenticator. The G8272 relies on external RADIUS servers for authentication.

Upon a successful authentication of the client by the server, the 802.1X-controlled port transitions from unauthorized to authorized state, and the client is allowed full access to services through the port. When the client sends an EAP-Logoff message to the authenticator, the port will transition from authorized to unauthorized state.

© Copyright Lenovo 2015 Chapter 6: 802.1X Port-Based Network Access Control 97

EAPoL Authentication ProcessThe clients and authenticators communicate using Extensible Authentication Protocol (EAP), which was originally designed to run over PPP, and for which the IEEE 802.1X Standard has defined an encapsulation method over Ethernet frames, called EAP over LAN (EAPOL). Figure 1 shows a typical message exchange initiated by the client.

Figure 1. Authenticating a Port Using EAPoL

802.1x ClientRADIUS

Server

Radius-Access-Request

Radius-Access-Challenge

Radius-Access-Request

Radius-Access-Accept

EAP-Request (Credentials)

EAP-Response (Credentials)

EAP-Success

EAP-Request (Credentials)

EAP-Response (Credentials)

EAPOL-Start

Port Authorized

Port Unauthorized

Lenovo Switch

Authenticator

(RADIUS Client)

EAPOL

Ethernet

RADIUS-EAP

UDP/IP


EAPoL Message ExchangeDuring authentication, EAPOL messages are exchanged between the client and the G8272 authenticator, while RADIUS-EAP messages are exchanged between the G8272 authenticator and the RADIUS server.

Authentication is initiated by one of the following methods:

The G8272 authenticator sends an EAP-Request/Identity packet to the client

The client sends an EAPOL-Start frame to the G8272 authenticator, which responds with an EAP-Request/Identity frame.

The client confirms its identity by sending an EAP-Response/Identity frame to the G8272 authenticator, which forwards the frame encapsulated in a RADIUS packet to the server.

The RADIUS authentication server chooses an EAP-supported authentication algorithm to verify the client’s identity, and sends an EAP-Request packet to the client via the G8272 authenticator. The client then replies to the RADIUS server with an EAP-Response containing its credentials.

Upon a successful authentication of the client by the server, the 802.1X-controlled port transitions from unauthorized to authorized state, and the client is allowed full access to services through the controlled port. When the client later sends an EAPOL-Logoff message to the G8272 authenticator, the port transitions from authorized to unauthorized state.

If a client that does not support 802.1X connects to an 802.1X-controlled port, the G8272 authenticator requests the client's identity when it detects a change in the operational state of the port. The client does not respond to the request, and the port remains in the unauthorized state.Note: When an 802.1X-enabled client connects to a port that is not 802.1X-controlled, the client initiates the authentication process by sending an EAPOL-Start frame. When no response is received, the client retransmits the request for a fixed number of times. If no response is received, the client assumes the port is in authorized state, and begins sending frames, even if the port is unauthorized.


EAPoL Port StatesThe state of the port determines whether the client is granted access to the network, as follows:

UnauthorizedWhile in this state the port discards all ingress and egress traffic except EAP packets.

AuthorizedWhen the client is successfully authenticated, the port transitions to the authorized state allowing all traffic to and from the client to flow normally.

Force UnauthorizedYou can configure this state that denies all access to the port.

Force AuthorizedYou can configure this state that allows full access to the port.

Use the 802.1X global configuration commands (dot1x) to configure 802.1X authentication for all ports in the switch. Use the 802.1X port commands to configure a single port.

Guest VLANThe guest VLAN provides limited access to unauthenticated ports. The guest VLAN can be configured using the following commands:

Client ports that have not received an EAPOL response are placed into the Guest VLAN, if one is configured on the switch. Once the port is authenticated, it is moved from the Guest VLAN to its configured VLAN.

When Guest VLAN enabled, the following considerations apply while a port is in the unauthenticated state:

The port is placed in the guest VLAN.

The Port VLAN ID (PVID) is changed to the Guest VLAN ID.

Port tagging is disabled on the port.

RS 8272(config)# dot1x guestvlan ?


Supported RADIUS AttributesThe 802.1X Authenticator relies on external RADIUS servers for authentication with EAP. Table 10 lists the RADIUS attributes that are supported as part of RADIUS-EAP authentication based on the guidelines specified in Annex D of the 802.1X standard and RFC 3580.

Table 10. Support for RADIUS Attributes

# Attribute Attribute Value A-R A-A A-C A-R

1 User-Name The value of the Type-Data field from the supplicant’s EAP-Response/ Identity message. If the Identity is unknown (for example, Type-Data field is zero bytes in length), this attribute will have the same value as the Calling-Station-Id.

1 0-1 0 0

4 NAS-IP-Address IPv4 address of the authenticator used for Radius communication.

1 0 0 0

5 NAS-Port Port number of the authenticator port to which the supplicant is attached.

1 0 0 0

24 State Server-specific value. This is sent unmodified back to the server in an Access-Request that is in response to an Access-Challenge.

0-1 0-1 0-1 0

30 Called-Station-ID

The MAC address of the authenticator encoded as an ASCII string in canonical format, such as 000D5622E3 9F.

1 0 0 0

31 Calling-Station-ID

The MAC address of the supplicant encoded as an ASCII string in canonical format, such as 00034B436206.

1 0 0 0

64 Tunnel-Type Only VLAN (type 13) is currently supported (for 802.1X RADIUS VLAN assignment). The attribute must be untagged (the Tag field must be 0).

0 0-1 0 0

65 Tunnel-Medium-Type

Only 802 (type 6) is currently supported (for 802.1X RADIUS VLAN assignment). The attribute must be untagged (the Tag field must be 0).

0 0-1 0 0


81 Tunnel-Private-Group-ID

VLAN ID (1-4094). When 802.1X RADIUS VLAN assignment is enabled on a port, if the RADIUS server includes the tunnel attributes defined in RFC 2868 in the Access-Accept packet, the switch will automatically place the authenticated port in the specified VLAN. Reserved VLANs (such as for management) may not be specified. The attribute must be untagged (the Tag field must be 0).

0 0-1 0 0

79 EAP-Message Encapsulated EAP packets from the supplicant to the authentication server (Radius) and vice-versa. The authenticator relays the decoded packet to both devices.

1+ 1+ 1+ 1+

80 Message-Authenticator

Always present whenever an EAP-Message attribute is also included. Used to integrity-protect a packet.

1 1 1 1

87 NAS-Port-ID Name assigned to the authenticator port, e.g. Server1_Port3

1 0 0 0

Legend: RADIUS Packet Types: A-R (Access-Request), A-A (Access-Accept), A-C (Access-Challenge), A-R (Access-Reject)

RADIUS Attribute Support: 0 This attribute MUST NOT be present in a packet. 0+ Zero or more instances of this attribute MAY be present in a packet. 0-1 Zero or one instance of this attribute MAY be present in a packet. 1 Exactly one instance of this attribute MUST be present in a packet. 1+ One or more of these attributes MUST be present.

Table 10. Support for RADIUS Attributes (continued)

# Attribute Attribute Value A-R A-A A-C A-R


EAPoL Configuration GuidelinesWhen configuring EAPoL, consider the following guidelines:

The 802.1X port-based authentication is currently supported only in point-to-point configurations, that is, with a single supplicant connected to an 802.1X-enabled switch port.

When 802.1X is enabled, a port has to be in the authorized state before any other Layer 2 feature can be operationally enabled. For example, the STG state of a port is operationally disabled while the port is in the unauthorized state.

The 802.1X supplicant capability is not supported. Therefore, none of its ports can successfully connect to an 802.1X-enabled port of another device, such as another switch, that acts as an authenticator, unless access control on the remote port is disabled or is configured in forced-authorized mode. For example, if a G8272 is connected to another G8272, and if 802.1X is enabled on both switches, the two connected ports must be configured in force-authorized mode.

Unsupported 802.1X attributes include Service-Type, Session-Timeout, and Termination-Action.

RADIUS accounting service for 802.1X-authenticated devices or users is not currently supported.

Configuration changes performed using SNMP and the standard 802.1X MIB will take effect immediately.


Chapter 7. Access Control Lists

Access Control Lists (ACLs) are filters that permit or deny traffic for security purposes. They can also be used with QoS to classify and segment traffic to provide different levels of service to different traffic types. Each filter defines the conditions that must match for inclusion in the filter, and also the actions that are performed when a match is made.

Lenovo Networking OS 8.2 supports the following ACLs:

IPv4 ACLsUp to 256 ACLs are supported for networks that use IPv4 addressing. IPv4 ACLs are configured using the following ISCLI command path:

IPv6 ACLsUp to 128 ACLs are supported for networks that use IPv6 addressing. IPv6 ACLs are configured using the following ISCLI command path:

VLAN Maps (VMaps)Up to 128 VLAN Maps are supported for attaching filters to VLANs rather than ports. See “VLAN Maps” on page 112 for details.

Management ACLs (MACLs)Up to 256 MACLs are supported for filtering traffic toward CPU. MACLs are configured using the following ISCLI command path:

RS 8272(config)# accesscontrol list <IPv4 ACL number> ?

RS 8272(config)# accesscontrol list6 <IPv6 ACL number> ?

RS 8272(config)# accesscontrol macl <MACL number> ?


Summary of Packet ClassifiersACLs allow you to classify packets according to a variety of content in the packet header (such as the source address, destination address, source port number, destination port number, and others). Once classified, packet flows can be identified for more processing.

IPv4 ACLs, IPv6 ACLs, and VMaps allow you to classify packets based on the following packet attributes:

Ethernet header options (for IPv4 ACLs and VMaps only) Source MAC address Destination MAC address VLAN number and mask Ethernet type (ARP, IP, IPv6, MPLS, RARP, etc.) Ethernet Priority (the IEEE 802.1p Priority)

IPv4 header options (for IPv4 ACLs and VMaps only) Source IPv4 address and subnet mask Destination IPv4 address and subnet mask Type of Service value IP protocol number or name as shown in Table 11:

IPv6 header options (for IPv6 ACLs only) Source IPv6 address and prefix length Destination IPv6 address and prefix length Next Header value Flow Label value Traffic Class value

Table 11. Well-Known Protocol Types

Number Protocol Name

1261789112

icmpigmptcpudpospfvrrp

© Copyright Lenovo 2015 Chapter 7: Access Control Lists 105

TCP/UDP header options (for all ACLs) TCP/UDP application source port and mask as shown in Table 12 TCP/UDP application destination port as shown in Table 12

TCP/UDP flag value as shown in Table 13

Packet format (for IPv4 ACLs and VMaps only) Ethernet format (eth2, SNAP, LLC) Ethernet tagging format IP format (IPv4, IPv6)

Table 12. Well-Known Application Ports

PortTCP/UDPApplication Port

TCP/UDPApplication Port

TCP/UDPApplication

2021222325374243536970

ftp-dataftpsshtelnetsmtptimenamewhoisdomaintftpgopher

7980

109110111119123143144161162

fingerhttppop2pop3sunrpcnntpntpimapnewssnmpsnmptrap

179194220389443520554

1645/181218131985

bgpircimap3ldaphttpsriprtspRadiusRadius Accountinghsrp

Table 13. Well-Known TCP flag values

Flag Value

URGACKPSHRSTSYNFIN

0x00200x00100x00080x00040x00020x0001


Summary of ACL ActionsOnce classified using ACLs, the identified packet flows can be processed differently. For each ACL, an action can be assigned. The action determines how the switch treats packets that match the classifiers assigned to the ACL. G8272 ACL actions include the following: Pass or Drop the packet Re-mark the packet with a new DiffServ Code Point (DSCP) Re-mark the 802.1p field Set the COS queue

Assigning Individual ACLs to a Port

Once you configure an ACL, you must assign the ACL to the appropriate ports. Each port can accept multiple ACLs, and each ACL can be applied for multiple ports. ACLs can be assigned individually.

To assign an individual ACLs to a port, use the following IP Interface Mode commands:

When multiple ACLs are assigned to a port, higher-priority ACLs are considered first, and their action takes precedence over lower-priority ACLs. ACL order of precedence is discussed in the next section.

RS 8272(config)# interface port <port>RS 8272(configif)# accesscontrol list <IPv4 ACL number>RS 8272(configif)# accesscontrol list6 <IPv6 ACL number>


ACL Order of PrecedenceIf no assigned ACL matches the port traffic, no ACL action is applied.

ACL Metering and Re-MarkingYou can define a profile for the aggregate traffic flowing through the G8272 by configuring a QoS meter (if desired) and assigning ACLs to ports.Note: When you add ACLs to a port, make sure they are ordered correctly in terms of precedence (see “ACL Order of Precedence” on page 107).

Actions taken by an ACL are called In-Profile actions. You can configure additional In-Profile and Out-of-Profile actions on a port. Data traffic can be metered, and re-marked to ensure that the traffic flow provides certain levels of service in terms of bandwidth for different types of network traffic.

Metering

QoS metering provides different levels of service to data streams through user-configurable parameters. A meter is used to measure the traffic stream against a traffic profile which you create. Thus, creating meters yields In-Profile and Out-of-Profile traffic for each ACL, as follows:

In-ProfileIf there is no meter configured or if the packet conforms to the meter, the packet is classified as In-Profile.

Out-of-ProfileIf a meter is configured and the packet does not conform to the meter (exceeds the committed rate or maximum burst rate of the meter), the packet is classified as Out-of-Profile.

Using meters, you set a Committed Rate in Kbps . All traffic within this Committed Rate is In-Profile. Additionally, you can set a Maximum Burst Size that specifies an allowed data burst larger than the Committed Rate for a brief period. These parameters define the In-Profile traffic.

Meters keep the sorted packets within certain parameters. You can configure a meter on an ACL, and perform actions on metered traffic, such as packet re-marking.

Re-Marking

Re-marking allows for the treatment of packets to be reset based on new network specifications or desired levels of service. You can configure the ACL to re-mark a packet as follows:

Change the DSCP value of a packet, used to specify the service level that traffic receives.

Change the 802.1p priority of a packet.


ACL Port MirroringFor IPv4 ACLs and VMaps, packets that match the filter can be mirrored to another switch port for network diagnosis and monitoring.

The source port for the mirrored packets cannot be a portchannel, but may be a member of a portchannel.

The destination port to which packets are mirrored must be a physical port.

The action (permit, drop, etc.) of the ACL or VMap must be configured before assigning it to a port.

Use the following commands to add mirroring to an ACL:

For IPv4 ACLs:

The ACL must be also assigned to it target ports as usual (see “Assigning Individual ACLs to a Port” on page 106).

For VMaps (see “VLAN Maps” on page 112):

See the configuration example on page 113.

RS 8272(config)# accesscontrol list <ACL number> mirror port <destination port>

RS 8272(config)# accesscontrol vmap <VMap number> mirror port <monitor destination port>


Viewing ACL StatisticsACL statistics display how many packets have “hit” (matched) each ACL. Use ACL statistics to check filter performance or to debug the ACL filter configuration.

You must enable statistics for each ACL that you wish to monitor:

RS 8272(config)# accesscontrol list <ACL number> statistics


ACL Configuration Examples

ACL Example 1

Use this configuration to block traffic to a specific host. All traffic that ingresses on port 1 is denied if it is destined for the host at IP address 100.10.1.1

1. Configure an Access Control List.

2. Add ACL 1 to port 1.

ACL Example 2

Use this configuration to block traffic from a network destined for a specific host address. All traffic that ingresses in port 2 with source IP from class 100.10.1.0/24 and destination IP 200.20.2.2 is denied.



RS 8272(config)# accesscontrol list 1 ipv4 destinationipaddress 100.10.1.1

RS 8272(config)# accesscontrol list 1 action deny

RS 8272(config)# interface port 1RS 8272(configif)# accesscontrol list 1RS 8272(configif)# exit

RS 8272(config)# accesscontrol list 2 ipv4 sourceipaddress 100.10.1.0 255.255.255.0

RS 8272(config)# accesscontrol list 2 ipv4 destinationipaddress 200.20.2.2 255.255.255.255

RS 8272(config)# accesscontrol list 2 action deny



ACL Example 3

Use this configuration to block traffic from a specific IPv6 source address. All traffic that ingresses in port 2 with source IP from class 2001:0:0:5:0:0:0:2/128 is denied.



ACL Example 4

Use this configuration to deny all ARP packets that ingress a port.


2. Add ACL 2 to port EXT2.

ACL Example 5

Use the following configuration to permit access to hosts with destination MAC address that matches 11:05:00:10:00:00 FF:F5:FF:FF:FF:FF and deny access to all other hosts.

1. Configure Access Control Lists.

2. Add ACLs to a port.

RS 8272(config)# accesscontrol list6 3 ipv6 sourceaddress 2001:0:0:5:0:0:0:2 128

RS 8272(config)# accesscontrol list6 3 action deny

RS 8272(config)# interface port 2RS 8272(configif)# accesscontrol list6 3RS 8272(configif)# exit

RS 8272(config)# accesscontrol list 2 ethernet ethernettype arpRS 8272(config)# accesscontrol list 2 action deny


RS 8272(config)# accesscontrol list 30 ethernet destinationmacaddress 11:05:00:10:00:00 FF:F5:FF:FF:FF:FF

RS 8272(config)# accesscontrol list 30 action permitRS 8272(config)# accesscontrol list 100 ethernet destinationmacaddress

00:00:00:00:00:00 00:00:00:00:00:00RS 8272(config)# accesscontrol list 100 action deny

RS 8272(config)# interface port 2RS 8272(configif)# accesscontrol list 30RS 8272(configif)# accesscontrol list 100RS 8272(configif)# exit


VLAN MapsA VLAN map (VMap) is an ACL that can be assigned to a VLAN or VM group rather than to a switch port as with IPv4 ACLs. This is particularly useful in a virtualized environment where traffic filtering and metering policies must follow virtual machines (VMs) as they migrate between hypervisors.

The G8272 supports up to 128 VMaps.

Individual VMap filters are configured in the same fashion as IPv4 ACLs, except that VLANs cannot be specified as a filtering criteria (unnecessary, since the VMap are assigned to a specific VLAN or associated with a VM group VLAN).

VMaps are configured using the following ISCLI configuration command path:

Once a VMap filter is created, it can be assigned or removed using the following configuration commands:

For regular VLAN, use config-vlan mode:

For a VM group (see “VM Group Types” on page 240), use the global configuration mode:

Note: Each VMap can be assigned to only one VLAN or VM group. However, each VLAN or VM group may have multiple VMaps assigned to it.

When the optional serverports or nonserverports parameter is specified, the action to add or remove the VMap is applied for either the switch server ports (serverports) or uplink ports (nonserverports). If omitted, the operation will be applied to all ports in the associated VLAN or VM group.

RS 8272(config)# accesscontrol vmap <VMap ID> ? action Set filter action egressport Set to filter for packets egressing this port ethernet Ethernet header options ipv4 IP version 4 header options meter ACL metering configuration mirror Mirror options packetformat Set to filter specific packet format types remark ACL remark configuration statistics Enable access control list statistics tcpudp TCP and UDP filtering options

RS 8272(config)# vlan <VLAN ID>RS 8272(configvlan)# [no] vmap <VMap ID> [serverports|

nonserverports]

RS 8272(config)# [no] virt vmgroup <ID> vmap <VMap ID> [serverports|nonserverports]


VMap Example

In this example, EtherType 2 traffic from VLAN 3 server ports is mirrored to a network monitor on port 4.

RS 8272(config)# accesscontrol vmap 21 packetformat ethernet ethernettype2RS 8272(config)# accesscontrol vmap 21 mirror port 4RS 8272(config)# accesscontrol vmap 21 action permitRS 8272(config)# vlan 3RS 8272(configvlan)# vmap 21 serverports


Using Storm Control FiltersExcessive transmission of broadcast or multicast traffic can result in a network storm. A network storm can overwhelm your network with constant broadcast or multicast traffic, and degrade network performance. Common symptoms of a network storm are denial-of-service (DoS) attacks, slow network response times, and network operations timing out.

The G8272 provides filters that can limit the number of the following packet types transmitted by switch ports: Broadcast packets Multicast packets Unknown unicast packets (destination lookup failure)

Unicast packets whose destination MAC address is not in the Forwarding Database are unknown unicasts. When an unknown unicast is encountered, the switch handles it like a broadcast packet and floods it to all other ports in the VLAN (broadcast domain). A high rate of unknown unicast traffic can have the same negative effects as a broadcast storm.

Configuring Storm Control

Configure broadcast filters on each port that requires broadcast storm control. Set a threshold that defines the total number of broadcast packets transmitted (0-2097151), in packets per second. When the threshold is reached, no more packets of the specified type are transmitted.

To filter broadcast packets on a port, use the following commands:

To filter multicast packets on a port, use the following commands:

To filter unknown unicast packets on a port, use the following commands:

RS 8272(config)# interface port 1RS 8272(configif)# stormcontrol broadcast level rate <packets per second>

RS 8272(configif)# stormcontrol multicast level rate <packets per second>

RS 8272(configif)# stormcontrol unicast level rate <packets per second>RS 8272(configif)# exit


Part 3: Switch BasicsThis section discusses basic switching functions:

VLANs

Port Trunking

Spanning Tree Protocols (Spanning Tree Groups, Rapid Spanning Tree Protocol, and Multiple Spanning Tree Protocol)

Virtual Link Aggregation Groups

Quality of Service



Chapter 8. VLANs

This chapter describes network design and topology considerations for using Virtual Local Area Networks (VLANs). VLANs commonly are used to split up groups of network users into manageable broadcast domains, to create logical segmentation of workgroups, and to enforce security policies among logical segments. The following topics are discussed in this chapter:

“VLANs and Port VLAN ID Numbers” on page 118

“VLAN Tagging/Trunk Mode” on page 120

“VLAN Topologies and Design Considerations” on page 124This section discusses how you can connect users and segments to a host that supports many logical segments or subnets by using the flexibility of the multiple VLAN system.

“Private VLANs” on page 127Note: VLANs can be configured from the Command Line Interface (see “VLAN Configuration” as well as “Port Configuration” in the Command Reference).


VLANs OverviewSetting up virtual LANs (VLANs) is a way to segment networks to increase network flexibility without changing the physical network topology. With network segmentation, each switch port connects to a segment that is a single broadcast domain. When a switch port is configured to be a member of a VLAN, it is added to a group of ports (workgroup) that belong to one broadcast domain.

Ports are grouped into broadcast domains by assigning them to the same VLAN. Frames received in one VLAN can only be forwarded within that VLAN, and multicast, broadcast, and unknown unicast frames are flooded only to ports in the same VLAN.

The RackSwitch G8272 (G8272) supports jumbo frames with a Maximum Transmission Unit (MTU) of bytes. Within each frame, 18 bytes are reserved for the Ethernet header and CRC trailer. The remaining space in the frame comprise the packet, which includes the payload and any additional overhead, such as 802.1q or VLAN tags. Jumbo frame support is automatic: it is enabled by default, requires no manual configuration, and cannot be manually disabled.

VLANs and Port VLAN ID Numbers

VLAN Numbers

The G8272 supports up to 4095 VLANs per switch. Each can be identified with any number between 1 and 4094. VLAN 1 is the default VLAN for the data ports. VLAN 4095 is used by the management network, which includes the management ports.

Use the following command to view VLAN information:

© Copyright Lenovo 2015 Chapter 8: VLANs 119

PVID/Native VLAN Numbers

Each port in the switch has a configurable default VLAN number, known as its PVID. By default, the PVID for all non-management ports is set to 1, which correlates to the default VLAN ID. The PVID for each port can be configured to any VLAN number between 1 and 4094.

Use the following command to view PVIDs:

Use the following command to set the port PVID/Native VLAN:

Each port on the switch can belong to one or more VLANs, and each VLAN can have any number of switch ports in its membership. Any port that belongs to multiple VLANs, however, must have VLAN tagging/trunk mode enabled (see “VLAN Tagging/Trunk Mode” on page 120).

Access Mode Port

RS 8272(config)# interface port <port number>RS 8272(configif)# switchport access vlan <VLAN ID>

For Trunk Mode Port

RS 8272(config)# interface port <port number>RS 8272(configif)# switchport trunk native vlan <VLAN ID>


VLAN Tagging/Trunk ModeLenovo Networking OS software supports 802.1Q VLAN tagging, providing standards-based VLAN support for Ethernet systems.

Tagging places the VLAN identifier in the frame header of a packet, allowing each port to belong to multiple VLANs. When you add a port to multiple VLANs, you also must enable tagging on that port.

Since tagging fundamentally changes the format of frames transmitted on a tagged port, you must carefully plan network designs to prevent tagged frames from being transmitted to devices that do not support 802.1Q VLAN tags, or devices where tagging is not enabled.

Important terms used with the 802.1Q tagging feature are:

VLAN identifier (VID)—the 12-bit portion of the VLAN tag in the frame header that identifies an explicit VLAN.

Port VLAN identifier (PVID)—a classification mechanism that associates a port with a specific VLAN. For example, a port with a PVID of 3 (PVID =3) assigns all untagged frames received on this port to VLAN 3. Any untagged frames received by the switch are classified with the PVID of the receiving port.

Tagged frame—a frame that carries VLAN tagging information in the header. This VLAN tagging information is a 32-bit field (VLAN tag) in the frame header that identifies the frame as belonging to a specific VLAN. Untagged frames are marked (tagged) with this classification as they leave the switch through a port that is configured as a tagged port.

Untagged frame— a frame that does not carry any VLAN tagging information in the frame header.

Untagged member—a port that has been configured as an untagged member of a specific VLAN. When an untagged frame exits the switch through an untagged member port, the frame header remains unchanged. When a tagged frame exits the switch through an untagged member port, the tag is stripped and the tagged frame is changed to an untagged frame.

Tagged member—a port that has been configured as a tagged member of a specific VLAN. When an untagged frame exits the switch through a tagged member port, the frame header is modified to include the 32-bit tag associated with the PVID. When a tagged frame exits the switch through a tagged member port, the frame header remains unchanged (original VID remains).

Note: If a 802.1Q tagged frame is received by a port that has VLAN-tagging disabled and the port VLAN ID (PVID) is different than the VLAN ID of the packet, then the frame is dropped at the ingress port.


Figure 2. Default VLAN settings

Note: The port numbers specified in these illustrations may not directly correspond to the physical port configuration of your switch model.

When a VLAN is configured, ports are added as members of the VLAN, and the ports are defined as either tagged or untagged (see Figure 3 through Figure 6).

The default configuration settings for the G8272 has all ports set as untagged members of VLAN 1 with all ports configured as PVID = 1. In the default configuration example shown in Figure 2, all incoming packets are assigned to VLAN 1 by the default port VLAN identifier (PVID =1).

Figure 3 through Figure 6 illustrate generic examples of VLAN tagging. In Figure 3, untagged incoming packets are assigned directly to VLAN 2 (PVID = 2). Port 5 is configured as a tagged member of VLAN 2, and port 7 is configured as an untagged member of VLAN 2. Note: The port assignments in the following figures are not meant to match the G8272.

Figure 3. Port-based VLAN assignment

Port 1

DA

SA

Data

CRC

Incominguntagged

packet

BS45010A

Port 2 Port 3 Port 4 Port 5

VLAN 1

802.1Q Switch

By default:

Key

All ports are assigned PVID = 1All ports are untagged members of VLAN 1

PVID = 1

Port 6 ...

DA

SA

Data

CRC

Outgoinguntagged packet

(unchanged)

Port 7

Port 6

DASADataCRC

BS45011A

Port 7 Port 8

Port 1

Port

4

Port

5

Port 2 Port 3

802.1Q Switch

PVID = 2

Untagged packet

Untagged memberof VLAN 2

Tagged memberof VLAN 2

Before


As shown in Figure 4, the untagged packet is marked (tagged) as it leaves the switch through port 5, which is configured as a tagged member of VLAN 2. The untagged packet remains unchanged as it leaves the switch through port 7, which is configured as an untagged member of VLAN 2.

Figure 4. 802.1Q tagging (after port-based VLAN assignment)

In Figure 5, tagged incoming packets are assigned directly to VLAN 2 because of the tag assignment in the packet. Port 5 is configured as a tagged member of VLAN 2, and port 7 is configured as an untagged member of VLAN 2.

Figure 5. 802.1Q tag assignment

As shown in Figure 6, the tagged packet remains unchanged as it leaves the switch through port 5, which is configured as a tagged member of VLAN 2. However, the tagged packet is stripped (untagged) as it leaves the switch through port 7, which is configured as an untagged member of VLAN 2.

BS45012A

Port 6 Port 7 Port 8

Port 1

Port

4

Port

5

Port 2 Port 3

802.1Q Switch

Key

Priority

CFI

VID

- User_priority

- Canonical format indicator

- VLAN identifier

PVID = 2 Tagged memberof VLAN 2

Untagged memeberof VLAN 2

After

DA

SA

Data

CRC

(*Recalculated)

Outgoinguntagged packet

(unchanged)

DASADataCRC* Tag

VID = 2Priority

16 bits 3 bits 1 bits 12 bits

8100 CFI

Port 6

DASATagDataCRC

Tagged packet

BS45013A

Port 7 Port 8

Port 1

Port

4

Port

5

Port 2 Port 3

802.1Q Switch

PVID = 2


Tagged memberof VLAN 2

Before


Figure 6. 802.1Q tagging (after 802.1Q tag assignment)

BS45014A

Port 6 Port 7 Port 8

Port 1

Por

t 4

Por

t 5

Port 2 Port 3

802.1Q Switch

Key

PriorityCFI VID

- User_priority- Canonical format indicator- VLAN identifier

PVID = 2 Tagged memberof VLAN 2


After

DA

SA

Data

CRC* (*Recalculated)

Outgoinguntagged packetchanged(tag removed)

DASADataCRC Tag

VID = 2Priority

16 bits 3 bits 1 bit 12 bits

8100 CFI


VLAN Topologies and Design ConsiderationsNote the following when working with VLAN topologies:

By default, the G8272 software is configured so that tagging/trunk mode is disabled on all ports.

By default, the G8272 software is configured so that all data ports are members of VLAN 1.

When using Spanning Tree, STG 2-128 may contain only one VLAN unless Multiple Spanning-Tree Protocol (MSTP) mode is used. With MSTP mode, STG 1 to 32 can include multiple VLANs.

All ports involved in both trunking and port mirroring must have the same VLAN configuration. If a port is on a trunk with a mirroring port, the VLAN configuration cannot be changed. For more information trunk groups, see “Ports and Trunking” on page 129 and “Port Mirroring” on page 579.

Multiple VLANs with Tagging/Trunk Mode Adapters

Figure 7 illustrates a network topology described in Note: on page 125 and the configuration example on page 126.

Figure 7. Multiple VLANs with VLAN-Tagged Gigabit Adapters

Server 1VLAN 1

Server 2VLAN 1

Server 3VLAN 2

Server 4VLAN 3

Server 5VLAN 1, 2

EnterpriseRouting Switch



The features of this VLAN are described in the following table.

Note: VLAN tagging/trunk mode is required only on ports that are connected to other switches or on ports that connect to tag-capable end-stations, such as servers with VLAN-tagging/trunk mode adapters.

To configure a specific VLAN on a trunk port, the following conditions must be met:

The port must be in trunk mode.

The VLAN must be in the trunk’s allowed VLAN range. By default, the range includes all VLANs.

The VLAN must be un-reserved.

The VLAN must be created.

The order in which the conditions above are met is not relevant. However, all conditions must be met collectively. When the final condition is met, the VLAN is enabled on the port. When the first condition is broken, the VLAN is disabled.

Table 14. Multiple VLANs Example

Component Description

G8272 switch This switch is configured with three VLANs that represent three different IP subnets. Five ports are connected downstream to servers. Two ports are connected upstream to routing switches. Uplink ports are members of all three VLANs, with VLAN tagging/trunk mode enabled.

Server 1 This server is a member of VLAN 1 and has presence in only one IP subnet. The associated switch port is only a member of VLAN 1, so tagging/trunk mode is disabled.

Server 2 This server is a member of VLAN 1 and has presence in only one IP subnet. The associated switch port is only a member of VLAN 1, so tagging/trunk mode is disabled.

Server 3 This server belongs to VLAN 2, and it is logically in the same IP subnet as Server 5. The associated switch port has tagging/trunk mode disabled.

Server 4 A member of VLAN 3, this server can communicate only with other servers via a router. The associated switch port has tagging/trunk mode disabled.

Server 5 A member of VLAN 1 and VLAN 2, this server can communicate only with Server 1, Server 2, and Server 3. The associated switch port has tagging/trunk mode enabled.

Enterprise Routing switches

These switches must have all three VLANs (VLAN 1, 2, 3) configured. They can communicate with Server 1, Server 2, and Server 5 via VLAN 1. They can communicate with Server 3 and Server 5 via VLAN 2. They can communicate with Server 4 via VLAN 3. Tagging/trunk mode on switch ports is enabled.


VLAN Configuration Example

Use the following procedure to configure the example network shown in Figure 7 on page 124.

1. Enable VLAN tagging/trunk mode on server ports that support multiple VLANs.

2. Enable tagging/trunk mode on uplink ports that support multiple VLANs.

3. Configure server ports that belong to a single VLAN.

By default, all ports are members of VLAN 1, so configure only those ports that belong to other VLANs.

RS 8272(config)# interface port 5RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit

RS 8272(config)# interface port 19RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2,3RS 8272(configif)# exitRS 8272(config)# interface port 20RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2,3RS 8272(configif)# exit

RS 8272(config)# interface port 4RS 8272(configif)# switchport mode accessRS 8272(configif)# switchport access vlan 2RS 8272(configif)# exit


Private VLANsPrivate VLANs provide Layer 2 isolation between the ports within the same broadcast domain. Private VLANs can control traffic within a VLAN domain, and provide port-based security for host servers.

Lenovo N/OS supports Private VLAN configuration as described in RFC 5517.

Use Private VLANs to partition a VLAN domain into sub-domains. Each sub-domain is comprised of one primary VLAN and one or more secondary VLANs, as follows: Primary VLAN—carries unidirectional traffic downstream from promiscuous

ports. Each Private VLAN configuration has only one primary VLAN. All ports in the Private VLAN are members of the primary VLAN.

Secondary VLAN—Secondary VLANs are internal to a private VLAN domain, and are defined as follows: Isolated VLAN—carries unidirectional traffic upstream from the host servers

toward ports in the primary VLAN and the gateway. Each Private VLAN configuration can contain only one isolated VLAN.

Community VLAN—carries upstream traffic from ports in the community VLAN to other ports in the same community, and to ports in the primary VLAN and the gateway. Each Private VLAN configuration can contain multiple community VLANs.

After you define the primary VLAN and one or more secondary VLANs, you map the secondary VLAN(s) to the primary VLAN.

Private VLAN Ports

Private VLAN ports are defined as follows: Promiscuous—A promiscuous port is a port that belongs to the primary VLAN.

The promiscuous port can communicate with all the interfaces, including ports in the secondary VLANs (Isolated VLAN and Community VLANs).

Isolated—An isolated port is a host port that belongs to an isolated VLAN. Each isolated port has complete layer 2 separation from other ports within the same private VLAN (including other isolated ports), except for the promiscuous ports. Traffic sent to an isolated port is blocked by the Private VLAN, except the

traffic from promiscuous ports. Traffic received from an isolated port is forwarded only to promiscuous ports.

Community—A community port is a host port that belongs to a community VLAN. Community ports can communicate with other ports in the same com-munity VLAN, and with promiscuous ports. These interfaces are isolated at layer 2 from all other interfaces in other communities and from isolated ports within the Private VLAN.

Configuration Guidelines

The following guidelines apply when configuring Private VLANs: The default VLAN 1 cannot be a Private VLAN. IGMP Snooping must be disabled on Private VLANs. All VLANs that comprise the Private VLAN must belong to the same Spanning

Tree Group.


Configuration Example

Follow this procedure to configure a Private VLAN.

1. Select a VLAN and define the Private VLAN type as primary.

2. Configure a promiscuous port for VLAN 700.

3. Configure two secondary VLANs: isolated VLAN and community VLAN.

4. Map secondary VLANs to primary VLAN.

5. Configure host ports for secondary VLANs.

6. Verify the configuration.

RS 8272(config)# vlan 700RS 8272(configvlan)# privatevlan primaryRS 8272(configvlan)# exit

RS 8272(config)# interface port 1RS 8272(configif)# switchport mode privatevlanRS 8272(configif)# switchport privatevlan mapping 700RS 8272(configif)# exit

RS 8272(config)# vlan 701RS 8272(configvlan)# privatevlan isolatedRS 8272(configvlan)# exitRS 8272(config)# vlan 702RS 8272(configvlan)# privatevlan communityRS 8272(configvlan)# exit

RS 8272(config)# vlan 700702RS 8272(configvlan)# stg 1RS 8272(configvlan)# exitRS 8272(config)# vlan 700RS 8272(configvlan)# privatevlan association 701,702RS 8272(configvlan)# exit

RS 8272(config)# interface port 2RS 8272(configif)# switchport mode privatevlanRS 8272(configif)# switchport privatevlan hostassociation 700 701RS 8272(configif)# exit

RS 8272(config)# interface port 3RS 8272(configif)# switchport mode privatevlanRS 8272(configif)# switchport privatevlan hostassociation 700 702RS 8272(configif)# exit

RS 8272(config)# show vlan privatevlan

Primary Secondary Type Ports vPorts 700 701 isolated 1 2 empty700 702 community 1 3 empty


Chapter 9. Ports and Trunking

Trunk groups can provide super-bandwidth, multi-link connections between the RackSwitch G8272 (G8272) and other trunk-capable devices. A trunk group is a group of ports that act together, combining their bandwidth to create a single, larger virtual link. This chapter provides configuration background and examples for trunking multiple ports together:

“Configuring QSFP+ Ports” on page 130

“Trunking Overview” on page 132”

“Configuring a Static Port Trunk” on page 134

“Configurable Trunk Hash Algorithm” on page 140

“Link Aggregation Control Protocol” on page 136


Configuring QSFP+ PortsQSFP+ ports support both 10GbE and 40GbE, as shown in Table 15.

Use the following procedure to change the QSFP+ port mode.

1. Display the current port mode for the QSFP+ ports.

2. Change the port mode to 40GbE. Select the physical port number.

Table 15. QSFP+ Port Numbering

Physical Port Number 40GbE mode 10GbE mode

Port 49 Port 49 Ports 49/1-49/4

Port 50 Port 50 Ports 50/1-50/4

Port 51 Port 51 Port 51/1-51/4



#show boot qsfpportmodes

QSFP ports booted configuration: Port 49/1, 49/2, 49/3, 49/4 10G Mode Port 50/1, 50/2, 50/3, 50/4 10G Mode Port 51/1, 51/2, 51/3, 51/4 10G Mode Port 52/1, 52/2, 52/3, 52/4 10G Mode Port 53/1, 53/2, 53/3, 53/4 10G Mode Port 54/1, 54/2, 54/3, 54/4 10G Mode

QSFP ports saved configuration: Port 49/1, 49/2, 49/3, 49/4 10G Mode Port 50/1, 50/2, 50/3, 50/4 10G Mode Port 51/1, 51/2, 51/3, 51/4 10G Mode Port 52/1, 52/2, 52/3, 52/4 10G Mode Port 53/1, 53/2, 53/3, 53/4 10G Mode Port 54/1, 54/2, 54/3, 54/4 10G Mode

RS 8272(config)#boot qsfp40Gports 50/1

© Copyright Lenovo 2015 Chapter 9: Ports and Trunking 131

3. Verify the change.

4. Reset the switch.

Use the ‘no’ form of the command to reset a port to 10GbE mode.

# show boot qsfpportmodes

QSFP ports booted configuration: Port 49/1, 49/2, 49/3, 49/4 10G Mode Port 50/1, 50/2, 50/3, 50/4 10G Mode Port 51/1, 51/2, 51/3, 51/4 10G Mode Port 52/1, 52/2, 52/3, 52/4 10G Mode Port 53/1, 53/2, 53/3, 53/4 10G Mode Port 54/1, 54/2, 54/3, 54/4 10G Mode

QSFP ports saved configuration: Port 49/1, 49/2, 49/3, 49/4 10G Mode Port 50 40G Mode Port 51/1, 51/2, 51/3, 51/4 10G Mode Port 52/1, 52/2, 52/3, 52/4 10G Mode Port 53/1, 53/2, 53/3, 53/4 10G Mode Port 54/1, 54/2, 54/3, 54/4 10G Mode

RS 8272(config)# reload

RS 8272(config)# no boot qsfp40Gports <port number or a range of ports>


Trunking OverviewWhen using port trunk groups between two switches, as shown in Figure 8, you can create a virtual link between the switches, operating with combined throughput levels that depends on how many physical ports are included.

Each G8272 supports up to 72 trunk groups. Two trunk types are available: static trunk groups (portchannel), and dynamic LACP trunk groups. Each type can contain up to 32 member ports, depending on the port type and availability.

Figure 8. Port Trunk Group

Trunk groups are also useful for connecting a G8272 to third-party devices that support link aggregation, such as Cisco routers and switches with EtherChannel technology (not ISL trunking technology) and Sun's Quad Fast Ethernet Adapter. Trunk Group technology is compatible with these devices when they are configured manually.

Trunk traffic is statistically distributed among the ports in a trunk group, based on a variety of configurable options.

Also, since each trunk group is comprised of multiple physical links, the trunk group is inherently fault tolerant. As long as one connection between the switches is available, the trunk remains active and statistical load balancing is maintained whenever a port in a trunk group is lost or returned to service.

Switch 2

AggregatePort Trunk

Switch 1


Static Trunks

Static Trunk Requirements

When you create and enable a static trunk, the trunk members (switch ports) take on certain settings necessary for correct operation of the trunking feature.

Before you configure your trunk, you must consider these settings, along with specific configuration rules, as follows:

1. Read the configuration rules provided in the section, “Static Trunk Group Configuration Rules” on page 133.

2. Determine which switch ports (up to 32) are to become trunk members (the specific ports making up the trunk).

3. Ensure that the chosen switch ports are set to enabled. Trunk member ports must have the same VLAN and Spanning Tree configuration.

4. Consider how the existing Spanning Tree will react to the new trunk configuration. See Chapter 10, “Spanning Tree Protocols,” for Spanning Tree Group configuration guidelines.

5. Consider how existing VLANs will be affected by the addition of a trunk.

Static Trunk Group Configuration Rules

The trunking feature operates according to specific configuration rules. When creating trunks, consider the following rules that determine how a trunk group reacts in any network topology:

All trunks must originate from one logical device, and lead to one logical destination device. Usually, a trunk connects two physical devices together with multiple links. However, in some networks, a single logical device may include multiple physical devices or when using VLAGs (see “Virtual Link Aggregation Groups” on page 165). In such cases, links in a trunk are allowed to connect to multiple physical devices because they act as one logical device.

Any physical switch port can belong to only one trunk group.

Trunking from third-party devices must comply with Cisco® EtherChannel® technology.

All ports in a trunk must have the same link configuration (speed, duplex, flow control), the same VLAN properties, and the same Spanning Tree, storm control, and ACL configuration. It is recommended that the ports in a trunk be members of the same VLAN.

Each trunk inherits its port configuration (speed, flow control, tagging) from the first member port. As additional ports are added to the trunk, their settings must be changed to match the trunk configuration.

When a port leaves a trunk, its configuration parameters are retained.

You cannot configure a trunk member as a monitor port in a port-mirroring configuration.


Trunks cannot be monitored by a monitor port; however, trunk members can be monitored.

Configuring a Static Port Trunk

In the following example, three ports are trunked between two switches.

Figure 9. Port Trunk Group Configuration Example

Prior to configuring each switch in this example, you must connect to the appropriate switches as the administrator.Note: For details about accessing and using any of the commands described in this example, see the RackSwitch G8272 ISCLI Reference.

1. Follow these steps on the G8272: a. Define a trunk group.

b. Verify the configuration.

Examine the resulting information. If any settings are incorrect, make appropriate changes.

2. Repeat the process on the other switch.

3. Connect the switch ports that will be members in the trunk group.

Trunk group 3 (on the G8272) is now connected to trunk group 1 (on the other switch). Note: In this example, two G8272 switches are used. If a third-party device support-ing link aggregation is used (such as Cisco routers and switches with EtherChannel technology or Sun's Quad Fast Ethernet Adapter), trunk groups on the third-party device must be configured manually. Connection problems could arise when using automatic trunk group negotiation on the third-party device.

2 9 16

1 11 18

Trunk Group 3 combinesPorts 2, 9, and 16

Trunk Group 1 combinesPorts 1, 11, and 18Trunk 1

Trunk 3

RS 8272(config)# portchannel 3 port 2,9,16RS 8272(config)# portchannel 3 enable

# show portchannel information

RS 8272(config)# portchannel 1 port 1,11,18RS 8272(config)# portchannel 1 enable


4. Examine the trunking information on each switch.

Information about each port in each configured trunk group is displayed. Make sure that trunk groups consist of the expected ports and that each port is in the expected state.

The following restrictions apply:

Any physical switch port can belong to only one trunk group.

Up to 32 ports can belong to the same trunk group.

All ports in static trunks must be have the same link configuration (speed, duplex, flow control).

Trunking from third-party devices must comply with Cisco® EtherChannel® technology.

# show portchannel informationPortChannel 3: EnabledProtocol—Staticport state: 2: STG 1 forwarding 9: STG 1 forwarding 16: STG 1 forwarding


Link Aggregation Control Protocol

LACP Overview

Link Aggregation Control Protocol (LACP) is an IEEE 802.3ad standard for grouping several physical ports into one logical port (known as a dynamic trunk group or Link Aggregation group) with any device that supports the standard. Please refer to IEEE 802.3ad-2002 for a full description of the standard.

The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link Aggregation Control Protocol (LACP). Link aggregation is a method of grouping physical link segments of the same media type and speed in full duplex, and treating them as if they were part of a single, logical link segment. If a link in a LACP trunk group fails, traffic is reassigned dynamically to the remaining link(s) of the dynamic trunk group. Note: LACP implementation in the Lenovo Networking OS does not support the Churn machine, an option used to detect if the port is operable within a bounded time period between the actor and the partner. Only the Marker Responder is implemented, and there is no marker protocol generator.

A port’s Link Aggregation Identifier (LAG ID) determines how the port can be aggregated. The Link Aggregation ID (LAG ID) is constructed mainly from the partner switch’s system ID and the port’s admin key, as follows:

System ID: an integer value based on the partner switch’s MAC address and the system priority assigned in the CLI.

Admin key: a port’s Admin key is an integer value (1-65535) that you can configure in the CLI. Each switch port that participates in the same LACP trunk group must have the same admin key value. The Admin key is local significant, which means the partner switch does not need to use the same Admin key value.

For example, consider two switches, an Actor (the G8272) and a Partner (another switch), as shown in Table 16.

In the configuration shown in Table 16, Actor switch ports 7 and 8 aggregate to form an LACP trunk group with Partner switch ports 1 and 2. Only ports with the same LAG ID are aggregated in the trunk group. Actor switch ports 9 and 10 are not aggregated in the same trunk group, because although they have the same admin key on the Actor switch, their LAG IDs are different (due to a different Partner switch admin key configuration). Instead, they form a secondary trunk group with Partner switch ports 3 and 4.

Table 16. Actor vs. Partner LACP configuration

Actor Switch Partner Switch

Port 7 (admin key = 100) Port 1 (admin key = 50) Primary trunk group

Port 8 (admin key = 100) Port 2 (admin key = 50) Primary trunk group

Port 9 (admin key = 100) Port 3 (admin key = 70) Secondary trunk group

Port 10 (admin key = 100) Port 4 (admin key = 70) Secondary trunk group


LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the controlled addition and removal of physical links for the link aggregation.

Static LACP TrunksTo prevent switch ports with the same admin key from forming multiple trunk groups, you can configure the LACP trunk as static. In a static LACP trunk, ports with the same admin key, but with different LAG IDs, compete to get aggregated in a trunk group. The LAG ID for the trunk group is decided based on the first port that is aggregated in the group. Ports with this LAG ID get aggregated and the other ports are placed in suspended mode. As per the configuration shown in Table 16, if port 7 gets aggregated first, then the LAG ID of port 7 would be the LAG ID of the trunk. Port 8 will join the trunk while ports 9 and 10 would be placed in suspended mode. When in suspended mode, a port transmits only LACP data units (LACPDUs) and discards all other traffic.

A port may also be placed in suspended mode for the following reasons:

When LACP is configured on the port but it stops receiving LACPDUs from the partner switch.

When the port has a different LAG ID because of the partner switch MAC or port LACP key being different. For example: when a switch is connected to two partners.

Static LACP trunks are configured by associating the LACP admin key to a portchannel ID within a dedicated LACP portchannel group range:

LACP Port Modes

Up to 64 ports can be assigned to a single LAG, but only 32 ports can actively participate in the LAG at a given time.

Each port on the switch can have one of the following LACP modes.

off (default)The user can configure this port in to a regular static trunk group.

activeThe port is capable of forming an LACP trunk. This port sends LACPDU packets to partner system ports.

passiveThe port is capable of forming an LACP trunk. This port only responds to the LACPDU packets sent from an LACP active port.

Each active LACP port transmits LACP data units (LACPDUs), while each passive LACP port listens for LACPDUs. During LACP negotiation, the admin key is exchanged. The LACP trunk group is enabled as long as the information matches at both ends of the link. If the admin key value changes for a port at either end of the link, that port’s association with the LACP trunk group is lost.

RS 8272(config)# portchannel <73-144> lacp key <adminkey of the LAG>


When the system is initialized, all ports by default are in LACP off mode and are assigned unique admin keys. To make a group of ports aggregatable, you assign them all the same admin key. You must set the port’s LACP mode to active to activate LACP negotiation. You can set other port’s LACP mode to passive, to reduce the amount of LACPDU traffic at the initial trunk-forming stage.

Use the following command to check whether the ports are trunked:

Note: If you configure LACP on ports with 802.1X network access control, make sure the ports on both sides of the connection are properly configured for both LACP and 802.1X.

LACP IndividualPorts assigned with an LACP admin key are prevented by default from forming individual links if they cannot join an LACP trunk group. To override this behavior, use the following commands:

This allows the selected ports to be treated as normal link-up ports, which may forward data traffic according to STP, Hot Links or other applications, if they do not receive any LACPDUs.

To configure the LACP individual setting for all the ports in a static LACP trunk, use the following commands:

or:

RS 8272 # show lacp information

RS 8272(config) # interface port <port no.>RS 8272(configif) # no lacp suspendindividual

RS 8272(config)# interface portchannel lacp <adminkey of the LAG> RS 8272(configPortChannel)# [no] lacp suspendindividual

RS 8272(config)# interface portchannel <static trunk ID of the LAG> RS 8272(configPortChannel)# [no] lacp suspendindividual


LACP Minimum Links Option

For dynamic trunks that require a guaranteed amount of bandwidth to be considered useful, you can specify the minimum number of links for the trunk. If the specified minimum number of ports are not available, the trunk link will not be established. If an active LACP trunk loses one or more component links, the trunk will be placed in the down state if the number of links falls to less than the specified minimum. By default, the minimum number of links is 1, meaning that LACP trunks will remain operational as long as at least one link is available.

The LACP minimum links setting can be configured as follows:

Via interface configuration mode:

Or via portchannel configuration mode:

Configuring LACP

Use the following procedure to configure LACP for ports 7, 8, 9 and 10 to participate in link aggregation.

1. Configure port parameters. All ports that participate in the LACP trunk group must have the same settings, including VLAN membership.

2. Select the port range and define the admin key. Only ports with the same admin key can form an LACP trunk group.

3. Set the LACP mode.

4. Allow member ports to individually participate in normal data traffic if no LACPDUs are received.

5. Set the link aggregation as static, by associating it with trunk ID 65:

RS 8272(config)# interface port <port number or range>RS 8272(configif)# portchannel minlinks <minimum links>RS 8272(configif)# exit

RS 8272(config)# interface portchannel lacp <LACP key>RS 8272(configPortChannel)# portchannel minlinks <minimum links>RS 8272(configif)# exit

RS 8272(config)# interface port 710RS 8272(configif)# lacp key 100

RS 8272(configif)# lacp mode active

RS 8272(configif)# no lacp suspendindividualRS 8272(configif)# exit

RS 8272(config)# portchannel 65 lacp key 100


Configurable Trunk Hash Algorithm

Traffic in a trunk group is statistically distributed among member ports using a hash process where various address and attribute bits from each transmitted frame are recombined to specify the particular trunk port the frame will use.

The switch can be configured to use a variety of hashing options. To achieve the most even traffic distribution, select options that exhibit a wide range of values for your particular network. Avoid hashing on information that is not usually present in the expected traffic, or which does not vary.

The G8272 supports the following hashing options: Layer 2 source MAC address

Layer 2 destination MAC address

Layer 2 source and destination MAC address

Layer 3 IPv4/IPv6 source IP address

Layer 3 IPv4/IPv6 destination IP address

Layer 3 source and destination IPv4/IPv6 address (the default)

Layer 2 hash configuration

Layer 4 port hash

Ingress port hash

RS 8272(config)# portchannel thash l2thash l2sourcemacaddress

RS 8272(config)# portchannel thash l2thash l2destinationmacaddress

RS 8272(config)# portchannel thash l2thash l2sourcedestinationmac

RS 8272(config)# portchannel thash l3thash l3sourceipaddress

RS 8272(config)# portchannel thash l3thash l3destinationipaddress

RS 8272(config)# portchannel thash l3thash l3sourcedestinationip

RS 8272(config)# portchannel thash l3thash l3usel2hash

RS 8272(config)# portchannel thash l4port

RS 8272(config)# portchannel thash ingress


The G8272 supports the following FCoE hashing options:

RS 8272(config)# portchannel thash fcoe cntagidRS 8272(config)# portchannel thash fcoe destinationidRS 8272(config)# portchannel thash fcoe fabricidRS 8272(config)# portchannel thash fcoe originatoridRS 8272(config)# portchannel thash fcoe responderidRS 8272(config)# portchannel thash fcoe sourceid



Chapter 10. Spanning Tree Protocols

When multiple paths exist between two points on a network, Spanning Tree Protocol (STP), or one of its enhanced variants, can prevent broadcast loops and ensure that the RackSwitch G8272 (G8272) uses only the most efficient network path.

This chapter covers the following topics:

“Spanning Tree Protocol Modes” on page 144

“Global STP Control” on page 145

“PVRST Mode” on page 145

“Rapid Spanning Tree Protocol” on page 158

“Multiple Spanning Tree Protocol” on page 160

“Port Type and Link Type” on page 163


Spanning Tree Protocol ModesLenovo Networking OS 8.2 supports the following STP modes:

Rapid Spanning Tree Protocol (RSTP)IEEE 802.1D (2004) RSTP allows devices to detect and eliminate logical loops in a bridged or switched network. When multiple paths exist, STP configures the network so that only the most efficient path is used. If that path fails, STP automatically configures the best alternative active path on the network to sustain network operations. RSTP is an enhanced version of IEEE 802.1D (1998) STP, providing more rapid convergence of the Spanning Tree network path states on STG 1.See “Rapid Spanning Tree Protocol” on page 158 for details.

Per-VLAN Rapid Spanning Tree (PVRST)PVRST mode is based on RSTP to provide rapid Spanning Tree convergence, but supports instances of Spanning Tree, allowing one STG per VLAN. PVRST mode is compatible with Cisco R-PVST/R-PVST+ mode.PVRST is the default Spanning Tree mode on the G8272. See “PVRST Mode” on page 145 for details.

Multiple Spanning Tree Protocol (MSTP)IEEE 802.1Q (2003) MSTP provides both rapid convergence and load balancing in a VLAN environment. MSTP allows multiple STGs, with multiple VLANs in each.See “Multiple Spanning Tree Protocol” on page 160 for details.

© Copyright Lenovo 2015 Chapter 10: Spanning Tree Protocols 145

Global STP ControlBy default, the Spanning Tree feature is globally enabled on the switch, and is set for PVRST mode. Spanning Tree (and thus any currently configured STP mode) can be globally disabled using the following command:

Spanning Tree can be re-enabled by specifying the STP mode:

where the command options represent the following modes: rstp: RSTP mode pvrst: PVRST mode mst: MSTP mode

PVRST ModeNote: Per-VLAN Rapid Spanning Tree (PVRST) is enabled by default on the G8272.

Using STP, network devices detect and eliminate logical loops in a bridged or switched network. When multiple paths exist, Spanning Tree configures the network so that a switch uses only the most efficient path. If that path fails, Spanning Tree automatically sets up another active path on the network to sustain network operations.

N/OS PVRST mode is based on IEEE 802.1w RSTP. Like RSTP, PVRST mode provides rapid Spanning Tree convergence. However, PVRST mode is enhanced for multiple instances of Spanning Tree. In PVRST mode, each VLAN may be automatically or manually assigned to one of 127 available STGs. Each STG acts as an independent, simultaneous instance of STP. PVRST uses IEEE 802.1Q tagging to differentiate STP BPDUs and is compatible with Cisco R-PVST/R-PVST+ modes.

The relationship between ports, trunk groups, VLANs, and Spanning Trees is shown in Table 17.

RS 8272(config)# spanningtree mode disable

RS 8272(config)# spanningtree mode pvrst|rstp|mst

Table 17. Ports, Trunk Groups, and VLANs

Switch Element Belongs To

Port Trunk group or one or more VLANs

Trunk group One or more VLANs

VLAN (non-default) PVRST: One VLAN per STG RSTP: All VLANs are in STG 1 MSTP: Multiple VLANs per STG


Port States

The port state controls the forwarding and learning processes of Spanning Tree. In PVRST, the port state has been consolidated to the following: discarding, learning, and forwarding.

Due to the sequence involved in these STP states, considerable delays may occur while paths are being resolved. To mitigate delays, ports defined as edge ports (“Port Type and Link Type” on page 163) may bypass the discarding and learning states, and enter directly into the forwarding state.

Bridge Protocol Data Units

Bridge Protocol Data Units OverviewTo create a Spanning Tree, the switch generates a configuration Bridge Protocol Data Unit (BPDU), which it then forwards out of its ports. All switches in the Layer 2 network participating in the Spanning Tree gather information about other switches in the network through an exchange of BPDUs.

A bridge sends BPDU packets at a configurable regular interval (2 seconds by default). The BPDU is used to establish a path, much like a hello packet in IP routing. BPDUs contain information about the transmitting bridge and its ports, including bridge MAC addresses, bridge priority, port priority, and path cost. If the ports are in trunk mode/tagged, each port sends out a special BPDU containing the tagged information.

The generic action of a switch on receiving a BPDU is to compare the received BPDU to its own BPDU that it will transmit. If the priority of the received BPDU is better than its own priority, it will replace its BPDU with the received BPDU. Then, the switch adds its own bridge ID number and increments the path cost of the BPDU. The switch uses this information to block any necessary ports.Note: If STP is globally disabled, BPDUs from external devices will transit the switch transparently. If STP is globally enabled, for ports where STP is turned off, inbound BPDUs will instead be discarded.

Determining the Path for Forwarding BPDUsWhen determining which port to use for forwarding and which port to block, the G8272 uses information in the BPDU, including each bridge ID. A technique based on the “lowest root cost” is then computed to determine the most efficient path for forwarding.

Bridge Priority

The bridge priority parameter controls which bridge on the network is the STG root bridge. To make one switch become the root bridge, configure the bridge priority lower than all other switches and bridges on your network. The lower the value, the higher the bridge priority. Use the following command to configure the bridge priority:

RS 8272(config)# spanningtree stp <STG> bridge priority <0-65535>


Port Priority

The port priority helps determine which bridge port becomes the root port or the designated port. The case for the root port is when two switches are connected using a minimum of two links with the same path-cost. The case for the designated port is in a network topology that has multiple bridge ports with the same path-cost connected to a single segment, the port with the lowest port priority becomes the designated port for the segment. Use the following command to configure the port priority:

where priority value is a number from 0 to 240, in increments of 16 (such as 0, 16, 32, and so on). If the specified priority value is not evenly divisible by 16, the value will be automatically rounded down to the nearest valid increment whenever manually changed in the configuration, or whenever a configuration file from a release prior to N/OS 6.5 is loaded.

Root Guard

The root guard feature provides a way to enforce the root bridge placement in the network. It keeps a new device from becoming root and thereby forcing STP re-convergence. If a root-guard enabled port detects a root device, that port will be placed in a blocked state.

You can configure the root guard at the port level using the following commands:

The default state is “none”, i.e. disabled.

Loop Guard

In general, STP resolves redundant network topologies into loop-free topologies. The loop guard feature performs additional checking to detect loops that might not be found using Spanning Tree. STP loop guard ensures that a non-designated port does not become a designated port.

To globally enable loop guard, enter the following command:

Note: The global loop guard command will be effective on a port only if the port-level loop guard command is set to default as shown below:RS 8272(config)# interface port <port number>RS 8272(configif)# no spanningtree guard

To enable loop guard at the port level, enter the following command:

The default state is “none”, meaning disabled.

RS 8272(configif)# spanningtree stp <STG> priority <port priority>

RS 8272(config)# interface port <port number>RS 8272(configif)# spanningtree guard root

RS 8272(config)# spanningtree loopguard

RS 8272(config)# interface port <port number>RS 8272(configif)# spanningtree guard loop


Port Path Cost

The port path cost assigns lower values to high-bandwidth ports, such as 10 Gigabit Ethernet, to encourage their use. The objective is to use the fastest links so that the route with the lowest cost is chosen. A value of 0 (the default) indicates that the default cost will be computed for an auto-negotiated link or trunk speed.

Use the following command to modify the port path cost:

The port path cost can be a value from 1 to 200000000. Specify 0 for automatic path cost.

RS 8272(config)# interface port <port number>RS 8272(configif)# spanningtree stp <STG> pathcost <path cost value> RS 8272(configif)# exit


Simple STP Configuration

Figure 10 depicts a simple topology using a switch-to-switch link between two G8272 1 and 2.

Figure 10. Spanning Tree Blocking a Switch-to-Switch Link

To prevent a network loop among the switches, STP must block one of the links between them. In this case, it is desired that STP block the link between the Lenovo switches, and not one of the G8272 uplinks or the Enterprise switch trunk.

During operation, if one G8272 experiences an uplink failure, STP will activate the Lenovo switch-to-switch link so that server traffic on the affected G8272 may pass through to the active uplink on the other G8272, as shown in Figure 11.

EnterpriseRoutingSwitches

x

Server Server Server Server

Switch 1 Switch 2STP

Blocks Link


Figure 11. Spanning Tree Restoring the Switch-to-Switch Link

In this example, port 10 on each G8272 is used for the switch-to-switch link. To ensure that the G8272 switch-to-switch link is blocked during normal operation, the port path cost is set to a higher value than other paths in the network. To configure the port path cost on the switch-to-switch links in this example, use the following commands on each G8272.

EnterpriseRoutingSwitches

Server Server Server Server

Switch 1 Switch 2STPRestores Link

UplinkFailure

RS 8272(config)# interface port 10RS 8272(configif)# spanningtree stp 1 pathcost 60000RS 8272(configif)# exit


Per-VLAN Spanning Tree Groups

PVRST mode supports a maximum of 128 STGs, with each STG acting as an independent, simultaneous instance of STP.

Multiple STGs provide multiple data paths which can be used for load-balancing and redundancy. To enable load balancing between two G8272s using multiple STGs, configure each path with a different VLAN and then assign each VLAN to a separate STG. Since each STG is independent, they each send their own IEEE 802.1Q tagged Bridge Protocol Data Units (BPDUs).

Each STG behaves as a bridge group and forms a loop-free topology. The default STG 1 may contain multiple VLANs (typically until they can be assigned to another STG). STGs 2-127 may contain only one VLAN each.

Using Multiple STGs to Eliminate False LoopsFigure 12 shows a simple example of why multiple STGs are needed. In the figure, two ports on a G8272 are connected to two ports on an application switch. Each of the links is configured for a different VLAN, preventing a network loop. However, in the first network, since a single instance of Spanning Tree is running on all the ports of the G8272, a physical loop is assumed to exist, and one of the VLANs is blocked, impacting connectivity even though no actual loop exists.

Figure 12. Using Multiple Instances of Spanning Tree Group

In the second network, the problem of improper link blocking is resolved when the VLANs are placed into different Spanning Tree Groups (STGs). Since each STG has its own independent instance of Spanning Tree, each STG is responsible only for the loops within its own VLAN. This eliminates the false loop, and allows both VLANs to forward packets between the switches at the same time.

VLANs and STG AssignmentIn PVRST mode, up to 128 STGs are supported. Ports cannot be added directly to an STG. Instead, ports must be added as members of a VLAN, and the VLAN must then be assigned to the STG.

VL

AN

1

VL

AN

30

Application Switch

Switch 1

FalseLoop

Application Switch

Switch 2

VLAN 1is active

STG 1VLAN 30is active

STG 2x

With a single Spanning Tree,one link becomes blocked.

Using multiple STGs,both links may be active.


STG 1 is the default STG. Although VLANs can be added to or deleted from default STG 1, the STG itself cannot be deleted from the system. By default, STG 1 is enabled and includes VLAN 1, which by default includes all switch ports (except for management VLANs and management ports).

STG 128 is reserved for switch management. By default, STG 128 is disabled, but includes management VLAN 4095 and the management ports (MGMT-A and MGMT-B).

By default, all other STGs (STG 2 through 127) are enabled, though they initially include no member VLANs. VLANs must be assigned to STGs. By default, this is done automatically using VLAN Automatic STG Assignment (VASA), though it can also be done manually (see “Manually Assigning STGs” on page 152.

When VASA is enabled (as by default), each time a new VLAN is configured, the switch will automatically assign that new VLAN to its own STG. Conversely, when a VLAN is deleted, if its STG is not associated with any other VLAN, the STG is returned to the available pool.

The specific STG number to which the VLAN is assigned is based on the VLAN number itself. For low VLAN numbers (1 through 127), the switch will attempt to assign the VLAN to its matching STG number. For higher numbered VLANs, the STG assignment is based on a simple modulus calculation; the attempted STG number will “wrap around,” starting back at the top of STG list each time the end of the list is reached. However, if the attempted STG is already in use, the switch will select the next available STG. If an empty STG is not available when creating a new VLAN, the VLAN is automatically assigned to default STG 1.

If ports are tagged, each tagged port sends out a special BPDU containing the tagged information. Also, when a tagged port belongs to more than one STG, the egress BPDUs are tagged to distinguish the BPDUs of one STG from those of another STG.

VASA is enabled by default, but can be disabled or re-enabled using the following commands:

If VASA is disabled, when you create a new VLAN, that VLAN automatically belongs to default STG 1. To place the VLAN in a different STG, assign it manually.

VASA applies only to PVRST mode and is ignored in RSTP and MSTP modes.

Manually Assigning STGsThe administrator may manually assign VLANs to specific STGs, whether or not VASA is enabled.

1. If no VLANs exist (other than default VLAN 1), see “Guidelines for Creating VLANs” on page 153 for information about creating VLANs and assigning ports to them.

RS 8272(config)# [no] spanningtree stgauto


2. Assign the VLAN to an STG using one of the following methods:

From the global configuration mode:

Or from within the VLAN configuration mode:

When a VLAN is assigned to a new STG, the VLAN is automatically removed from its prior STG.Note: For proper operation with switches that use Cisco PVST+, it is recommended that you create a separate STG for each VLAN.

Guidelines for Creating VLANsFollow these guidelines when creating VLANs:

When you create a new VLAN, if VASA is enabled (the default), that VLAN is automatically assigned its own STG. If VASA is disabled, the VLAN automatically belongs to STG 1, the default STG. To place the VLAN in a different STG, see “Manually Assigning STGs” on page 152. The VLAN is automatically removed from its old STG before being placed into the new STG.

Each VLANs must be contained within a single STG; a VLAN cannot span multiple STGs. By confining VLANs within a single STG, you avoid problems with Spanning Tree blocking ports and causing a loss of connectivity within the VLAN. When a VLAN spans multiple switches, it is recommended that the VLAN remain within the same STG (be assigned the same STG ID) across all the switches.

If ports are tagged, all trunked ports can belong to multiple STGs.

A port cannot be directly added to an STG. The port must first be added to a VLAN, and that VLAN added to the desired STG.

Rules for VLAN Tagged/Trunk Mode PortsThe following rules apply to VLAN tagged ports:

Tagged/trunk mode ports can belong to more than one STG, but untagged/access mode ports can belong to only one STG.

When a tagged/trunk mode port belongs to more than one STG, the egress BPDUs are tagged to distinguish the BPDUs of one STG from those of another STG.

RS 8272(config)# spanningtree stp <STG number> vlan <VLAN>

RS 8272(config)# vlan <VLAN numbers>RS 8272(configvlan)# stg <STG number>RS 8272(configvlan)# exit


Adding and Removing Ports from STGsThe following rules apply when you add ports to or remove ports from STGs:

When you add a port to a VLAN that belongs to an STG, the port is also added to that STG. However, if the port you are adding is an untagged port and is already a member of another STG, that port will be removed from its current STG and added to the new STG. An untagged port cannot belong to more than one STG.For example: Assume that VLAN 1 belongs to STG 1, and that port 1 is untagged and does not belong to any STG. When you add port 1 to VLAN 1, port 1 will automatically become part of STG 1.However, if port 5 is untagged and is a member of VLAN 3 in STG 2, then adding port 5 to VLAN 1 in STG 1 will change the port PVID from 3 to 1:

When you remove a port from VLAN that belongs to an STG, that port will also be removed from the STG. However, if that port belongs to another VLAN in the same STG, the port remains in the STG.As an example, assume that port 2 belongs to only VLAN 2, and that VLAN 2 belongs to STG 2. When you remove port 2 from VLAN 2, the port is moved to default VLAN 1 and is removed from STG 2.However, if port 2 belongs to both VLAN 1 and VLAN 2, and both VLANs belong to STG 2, removing port 2 from VLAN 2 does not remove port 2 from STG 2, because the port is still a member of VLAN 1, which is still a member of STG 1.

An STG cannot be deleted, only disabled. If you disable the STG while it still contains VLAN members, Spanning Tree will be off on all ports belonging to that VLAN.

The relationship between port, trunk groups, VLANs, and Spanning Trees is shown in Table 17 on page 145.

"Port 5 is an UNTAGGED/Access Mode port and its PVID/NativeVLAN changed from 3 to 1.


The Switch-Centric ModelPVRST is switch-centric: STGs are enforced only on the switch where they are configured. PVRST allows only one VLAN per STG, except for the default STG 1 to which multiple VLANs can be assigned. The STG ID is not transmitted in the Spanning Tree BPDU. Each Spanning Tree decision is based entirely on the configuration of the particular switch.

For example, in Figure 13, each switch is responsible for the proper configuration of its own ports, VLANs, and STGs. Switch A identifies its own port 17 as part of VLAN 2 on STG 2, and the Switch B identifies its own port 8 as part of VLAN 2 on STG 2.

Figure 13. Implementing Multiple Spanning Tree Groups

The VLAN participation for each Spanning Tree Group in Figure 13 on page 155 is as follows: VLAN 1 Participation

Assuming Switch B to be the root bridge, Switch B transmits the BPDU for STG 1 on ports 1 and 2. Switch C receives the BPDU on port 2, and Switch D receives the BPDU on port 1. Because there is a network loop between the switches in VLAN 1, either Switch D will block port 8 or Switch C will block port 1, depending on the information provided in the BPDU.

VLAN 2 ParticipationSwitch B, the root bridge, generates a BPDU for STG 2 from port 8. Switch A receives this BPDU on port 17, which is assigned to VLAN 2, STG 2. Because switch B has no additional ports participating in STG 2, this BPDU is not forwarded to any additional ports and Switch B remains the designated root.

VLAN 3 ParticipationFor VLAN 3, Switch A or Switch C may be the root bridge. If Switch A is the root bridge for VLAN 3, STG 3, then Switch A transmits the BPDU from port 18. Switch C receives this BPDU on port 8 and is identified as participating in VLAN 3, STG 3. Since Switch C has no additional ports participating in STG 3, this BPDU is not forwarded to any additional ports and Switch A remains the designated root.

ApplicationSwitch B

ChassisSwitch A

ApplicationSwitch D

ApplicationSwitch C

VLAN 2STG 2

STG 3VLAN 3 STG 1

VLAN 1

1

1

1

2

2

817

18

8

8


Configuring Multiple STGs

This configuration shows how to configure the three instances of STGs on the switches A, B, C, and D illustrated in Figure 13 on page 155.

Because VASA is enabled by default, each new VLAN is automatically assigned its own STG.

1. Set the Spanning Tree mode on each switch to PVRST.

Note: PVRST is the default mode on the G8272. This step is not required unless the STP mode has been previously changed, and is shown here merely as an example of manual configuration.

2. Configure the following on Switch A:

Enable VLAN 2 and VLAN 3.

Add port 17 to VLAN 2, port 18 to VLAN 3.

VLAN 2 and VLAN 3 are removed from STG 1.Note: In PVRST mode, each instance of STG is enabled by default.

3. Configure the following on Switch B:

Add port 8 to VLAN 2. Ports 1 and 2 are by default in VLAN 1 assigned to STG 1.

RS 8272(config)# spanningtree mode pvrst

RS 8272(config)# vlan 2RS 8272(configvlan)# exitRS 8272(config)# vlan 3RS 8272(configvlan)# exit

If VASA is disabled, enter the following commands:RS 8272(config)# spanningtree stp 2 vlan 2RS 8272(config)# spanningtree stp 3 vlan 3



RS 8272(config)# vlan 2RS 8272(configvlan)# stg 2RS 8272(configvlan)# exitRS 8272(config)# interface port 8RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit

If VASA is disabled, enter the following command:RS 8272(config)# spanningtree stp 2 vlan 2


VLAN 2 is automatically removed from STG 1. By default VLAN 1 remains in STG 1.

4. Configure the following on application switch C:

Add port 8 to VLAN 3. Ports 1 and 2 are by default in VLAN 1 assigned to STG 1.

VLAN 3 is automatically removed from STG 1. By default VLAN 1 remains in STG 1.

5. Switch D does not require any special configuration for multiple Spanning Trees. Switch D uses default STG 1 only.

RS 8272(config)# vlan 3RS 8272(configvlan)# stg 3RS 8272(configvlan)# exitRS 8272(config)# interface port 8RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 3RS 8272(configif)# exit

If VASA is disabled, enter the following command:RS 8272(config)# spanningtree stp 3 vlan 3


Rapid Spanning Tree ProtocolRSTP provides rapid convergence of the Spanning Tree and provides the fast re-configuration critical for networks carrying delay-sensitive traffic such as voice and video. RSTP significantly reduces the time to reconfigure the active topology of the network when changes occur to the physical topology or its configuration parameters. RSTP reduces the bridged-LAN topology to a single Spanning Tree.

RSTP was originally defined in IEEE 802.1w (2001) and was later incorporated into IEEE 802.1D (2004), superseding the original STP standard.

RSTP parameters apply only to Spanning Tree Group (STG) 1. The PVRST mode STGs 2-128 are not used when the switch is placed in RSTP mode.

RSTP is compatible with devices that run IEEE 802.1D (1998) Spanning Tree Protocol. If the switch detects IEEE 802.1D (1998) BPDUs, it responds with IEEE 802.1D (1998)-compatible data units. RSTP is not compatible with Per-VLAN Rapid Spanning Tree (PVRST) protocol.

Port States

RSTP port state controls are the same as for PVRST: discarding, learning, and forwarding.

Due to the sequence involved in these STP states, considerable delays may occur while paths are being resolved. To mitigate delays, ports defined as edge/portfast ports (“Port Type and Link Type” on page 163) may bypass the discarding and learning states, and enter directly into the forwarding state.

RSTP Configuration Guidelines

This section provides important information about configuring RSTP. When RSTP is turned on, the following occurs:

STP parameters apply only to STG 1.

Only STG 1 is available. All other STGs are turned off.

All VLANs, including management VLANs, are moved to STG 1.

RSTP Configuration Example

This section provides steps to configure RSTP.

1. Configure port and VLAN membership on the switch.

2. Set the Spanning Tree mode to Rapid Spanning Tree.

3. Configure RSTP parameters.

RS 8272(config)# spanningtree mode rstp

RS 8272(config)# spanning-tree stp 1 bridge priority 8192RS 8272(config)# spanning-tree stp 1 bridge hello-time 5RS 8272(config)# spanning-tree stp 1 bridge forward-delay 20RS 8272(config)# spanning-tree stp 1 bridge maximum-age 30RS 8272(config)# no spanning-tree stp 1 enable


4. Configure port parameters: RS 8272(config)# interface port 3RS 8272(config-if)# spanning-tree stp 1 priority 240RS 8272(config-if)# spanning-tree stp 1 path-cost 500RS 8272(config-if)# no spanning-tree stp 1 enableRS 8272(config-if)# exit


Multiple Spanning Tree ProtocolMultiple Spanning Tree Protocol (MSTP) extends Rapid Spanning Tree Protocol (RSTP), allowing multiple Spanning Tree Groups (STGs) which may each include multiple VLANs. MSTP was originally defined in IEEE 802.1s (2002) and was later included in IEEE 802.1Q (2003).

In MSTP mode, the G8272 supports up to 32 instances of Spanning Tree, corresponding to STGs 1-32, with each STG acting as an independent, simultaneous instance of RSTP.

MSTP allows frames assigned to different VLANs to follow separate paths, with each path based on an independent Spanning Tree instance. This approach provides multiple forwarding paths for data traffic, thereby enabling load-balancing, and reducing the number of Spanning Tree instances required to support a large number of VLANs.

Due to Spanning Tree’s sequence of discarding, learning, and forwarding, lengthy delays may occur while paths are being resolved. Ports defined as edge/portfast ports (“Port Type and Link Type” on page 163) bypass the Discarding and Learning states, and enter directly into the Forwarding state.Note: In MSTP mode, Spanning Tree for the management ports is turned off by default.

MSTP Region

A group of interconnected bridges that share the same attributes is called an MST region. Each bridge within the region must share the following attributes:

Alphanumeric name

Revision number

VLAN-to STG mapping scheme

MSTP provides rapid re-configuration, scalability and control due to the support of regions, and multiple Spanning-Tree instances support within each region.

Common Internal Spanning Tree

The Common Internal Spanning Tree (CIST) or MST0 provides a common form of Spanning Tree Protocol, with one Spanning-Tree instance that can be used throughout the MSTP region. CIST allows the switch to interoperate with legacy equipment, including devices that run IEEE 802.1D (1998) STP.

CIST allows the MSTP region to act as a virtual bridge to other bridges outside of the region, and provides a single Spanning-Tree instance to interact with them.

CIST port configuration includes Hello time, path-cost, and interface priority. These parameters do not affect Spanning Tree Groups 1-32. They apply only when the CIST is used.

MSTP Configuration Guidelines

This section provides important information about configuring Multiple Spanning Tree Groups:


When MSTP is turned on, the switch moves VLAN 1 and VLANs 33-128 to the CIST. When MSTP is turned off, the switch moves VLAN 1 and VLANs 33-128 from the CIST to STG 1.

When you enable MSTP, you must configure the Region Name. A default version number of 1 is configured automatically.

Each bridge in the region must have the same name, revision number, and VLAN mapping.

MSTP Configuration Examples

Example 1

This section provides steps to configure MSTP on the G8272.


2. Configure Multiple Spanning Tree region parameters, and set the mode to MSTP.

3. Map VLANs to MSTP instances:

Example 2

This configuration shows how to configure MSTP Groups on the switch, as shown in Figure 13.

Figure 14. Implementing Multiple Spanning Tree Groups

RS 8272(config)# spanningtree mst configuration( Enter MST configuration mode)RS 8272(configmst)# instance <instance ID> vlan <vlan number or range>

EnterpriseRouting SwitchMSTP Group 1

Root

EnterpriseRouting SwitchMSTP Group 2Root

Server 1VLAN 1

Server 2VLAN 1

Server 3VLAN 2

Server 4VLAN 2

Blocking VLAN 1Passing VLAN 2

Passing VLAN 1Blocking VLAN 2


This example shows how multiple Spanning Trees can provide redundancy without wasting any uplink ports. In this example, the server ports are split between two separate VLANs. Both VLANs belong to two different MSTP groups. The Spanning Tree priority values are configured so that each routing switch is the root for a different MSTP instance. All of the uplinks are active, with each uplink port backing up the other.

1. Configure port membership and define the STGs for VLAN 1. Enable tagging on uplink ports that share VLANs. Port 19 and port 20 connect to the Enterprise Routing switches.

2. Configure MSTP: Spanning Tree mode, region name, and version.

3. Map VLANs to MSTP instances:

4. Add server ports 1 and 2 to VLAN 1. Add uplink ports 19 and port 20 to VLAN 1.

5. Configure port membership and define the STGs for VLAN 2. Add server ports 3, 4, and 5 to VLAN 2. Add uplink ports 19 and 20 to VLAN 2. Assign VLAN 2 to STG 2.

Note: Each STG is enabled by default.

RS 8272(config)# interface port 19, 20RS 8272(configif)# switchport mode trunkRS 8272(configif)# exit

RS 8272(config)# spanningtree mst configuration

RS 8272(configmst)# name MyRegion (Define the Region name)RS 8272(configmst)# revision 100 (Define the Revision level)RS 8272(configmst)# exit

RS 8272(config)# spanningtree mode mst(Set mode to Multiple Spanning Trees)

RS 8272(config)# spanningtree mst configurationRS 8272(configmst)# instance 1 vlan 1RS 8272(configmst)# instance 2 vlan 2

RS 8272(config)# interface port 1,2,19,20RS 8272(configif)# switchport trunk allowed vlan add 1RS 8272(configif)# exit

RS 8272(config)# interface port 3,4,5,19,20RS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit


Port Type and Link Type

Edge/Portfast Port

A port that does not connect to a bridge is called an edge port. Since edge ports are assumed to be connected to non-STP devices (such as directly to hosts or servers), they are placed in the forwarding state as soon as the link is up.

Edge ports send BPDUs to upstream STP devices like normal STP ports, but do not receive BPDUs. If a port with edge enabled does receive a BPDU, it immediately begins working as a normal (non-edge) port, and participates fully in Spanning Tree.

Use the following commands to define or clear a port as an edge port:

Link Type

The link type determines how the port behaves in regard to Rapid Spanning Tree. Use the following commands to define the link type for the port:

where type corresponds to the duplex mode of the port, as follows:

p2p A full-duplex link to another device (point-to-point)

shared A half-duplex link is a shared segment and can contain more than one device.

auto The switch dynamically configures the link type.

Note: Any STP port in full-duplex mode can be manually configured as a shared port when connected to a non-STP-aware shared device (such as a typical Layer 2 switch) used to interconnect multiple STP-aware devices.

RS 8272(config)# interface port <port>RS 8272(configif)# [no] spanningtree portfastRS 8272(configif)# exit

RS 8272(config)# interface port <port>RS 8272(configif)# [no] spanningtree linktype <type>RS 8272(configif)# exit



Chapter 11. Virtual Link Aggregation Groups

In many data center environments, downstream servers or switches connect to upstream devices which consolidate traffic. For example, see Figure 15.

Figure 15. Typical Data Center Switching Layers with STP vs. VLAG

As shown in the example, a switch in the access layer may be connected to more than one switch in the aggregation layer to provide for network redundancy. Typically, Spanning Tree Protocol (RSTP, PVRST, or MSTP—see “Spanning Tree Protocols” on page 143) is used to prevent broadcast loops, blocking redundant uplink paths. This has the unwanted consequence of reducing the available bandwidth between the layers by as much as 50%. In addition, STP may be slow to resolve topology changes that occur during a link failure, and can result in considerable MAC address flooding.

Using Virtual Link Aggregation Groups (VLAGs), the redundant uplinks remain active, utilizing all available bandwidth.

Two switches are paired into VLAG peers, and act as a single virtual entity for the purpose of establishing a multi-port trunk. Ports from both peers can be grouped into a VLAG and connected to the same LAG-capable target device. From the perspective of the target device, the ports connected to the VLAG peers appear to be a single trunk connecting to a single logical device. The target device uses the configured Tier ID to identify the VLAG peers as this single logical device. It is important that you use a unique Tier ID for each VLAG pair you configure. The VLAG-capable switches synchronize their logical view of the access layer port structure and internally prevent implicit loops. The VLAG topology also responds more quickly to link failure and does not result in unnecessary MAC flooding.

VLAGs are also useful in multi-layer environments for both uplink and downlink redundancy to any regular LAG-capable device. For example:

STP blocksimplicit loops

Links remainactive

AccessLayer

Servers

AggregationLayer

VLAGPeers

VLAGs

ISL


Figure 16. VLAG Application with Multiple Layers

Wherever ports from both peered switches are trunked to another device, the trunked ports must be configured as a VLAG. For example, VLAGs 1 and 3 must be configured for both VLAG Peer A switches. VLAGs 2 and 4 must be configured for both VLAG Peer B switches.VLAGs 3, 5, and 6 must be configured on both VLAG Peer C switches. Other devices connecting to the VLAG peers are configured using regular static or dynamic trunks.Note: Do not configure a VLAG for connecting only one switch in the peer set to another device or peer set. For instance, in VLAG Peer C, a regular trunk is employed for the downlink connection to VLAG Peer B because only one of the VLAG Peer C switches is involved.

ISL

VLAG 3

VLAG 3

VLAG 5 VLAG 6

TrunkTrunk

VLAG 2

Trunk

ISL

ISL

Layer 2/3 Border

Layer 2 Regionwith multiple levels

Servers

VLAGPeers C

VLAGPeers B

VLAGPeers A

VLAG 1

Trunk

Trunk

VLAG 4

LACP-capableServer

LACP-capableSwitch

LACP-capableRouters

© Copyright Lenovo 2015 Chapter 11: Virtual Link Aggregation Groups 167

In addition, when used with VRRP, VLAGs can provide seamless active-active failover for network links. For example

Figure 17. VLAG Application with VRRP:

ISL

VLAG

Server

VRRPMaster

VRRPBackup

VLAGPeers

ActiveTraffic Flows


VLAG CapacitiesServers or switches that connect to the VLAG peers using a multi-port VLAG are considered VLAG clients. VLAG clients are not required to be VLAG-capable. The ports participating in the VLAG are configured as regular port trunks on the VLAG client end.

On the VLAG peers, the VLAGs are configured similarly to regular port trunks, using many of the same features and rules. See “Ports and Trunking” on page 129 for general information concerning all port trunks.

Each VLAG begins as a regular port trunk on each VLAG-peer switch. The VLAG may be either a static trunk group (portchannel) or dynamic LACP trunk group, and consumes one slot from the overall port trunk capacity pool. The trunk type must match that used on VLAG client devices. Additional configuration is then required to implement the VLAG on both VLAG peer switches.

You may configure up to 64 trunk groups on the switch, with all types (regular or VLAG, static or LACP) sharing the same pool.

The maximum number of configurable VLAG instances is as follows:

With STP off: Maximum of 52 VLAG instances

With STP on: PVRST/MSTP with one VLAG instance per VLAN/STG: Maximum of 52

VLAG instances PVRST/MSTP with one VLAG instance belonging to multiple

VLANs/STGs: Maximum of 20 VLAG instances

Each trunk type can contain up to 32 member ports, depending on the port type and availability.

VLAGs versus Port TrunksThough similar to regular port trunks in many regards, VLAGs differ from regular port trunks in a number of important ways:

A VLAG can consist of multiple ports on two VLAG peers, which are connected to one logical client device such as a server, switch, or another VLAG device.

The participating ports on the client device are configured as a regular port trunk.

The VLAG peers must be the same model, and run the same software version.

VLAG peers require a dedicated inter-switch link (ISL) for synchronization. The ports used to create the ISL must have the following properties: ISL ports must have VLAN tagging turned on. ISL ports must be configured for all VLAG VLANs. ISL ports must be placed into a regular port trunk group (dynamic or static). A minimum of two ports on each switch are recommended for ISL use.

Dynamic routing protocols, such as OSPF, cannot terminate on VLAGs.


Routing over VLAGs is not supported. However, IP forwarding between subnets served by VLAGs can be accomplished using VRRP.

VLAGs are configured using additional commands.

It is recommended that end-devices connected to VLAG switches use NICs with dual-homing. This increases traffic efficiency, reduces ISL load, and provides faster link failover.


Configuring VLAGsWhen configuring VLAG or making changes to your VLAG configuration, consider the following VLAG behavior:

When adding a static Mrouter on VLAG links, ensure that you also add it on the ISL link to avoid VLAG link failure. If the VLAG link fails, traffic cannot be recovered through the ISL.

When you enable VLAG on the switch, if a MSTP region mismatch is detected with the VLAG peer, the ISL will shut down. In such a scenario, correct the region on the VLAG peer and manually enable the ISL.

If you have enabled VLAG on the switch, and you need to change the STP mode, ensure that you first disable VLAG and then change the STP mode.

When VLAG is enabled, you may see two root ports on the secondary VLAG switch. One of these will be the actual root port for the secondary VLAG switch and the other will be a root port synced with the primary VLAG switch.

The LACP key used must be unique for each VLAG in the entire topology.

The STG to VLAN mapping on both VLAG peers must be identical.

The following parameters must be identically configured on the VLAG ports of both the VLAG peers:

VLANs

Native VLAN tagging

STP mode

BPDU Guard setting

STP port setting

MAC aging timers

Static MAC entries

ACL configuration parameters

QoS configuration parameters


Basic VLAG Configuration

Figure 18 shows an example configuration where two VLAG peers are used for aggregating traffic from downstream devices.

Figure 18. Basic VLAGs

In this example, each client switch is connected to both VLAG peers. On each client switch, the ports connecting to the VLAG peers are configured as a dynamic LACP port trunk. The VLAG peer switches share a dedicated ISL for synchronizing VLAG information. On the individual VLAG peers, each port leading to a specific client switch (and part of the client switch’s port trunk) is configured as a VLAG.

In the following example configuration, only the configuration for VLAG 1 on VLAG Peer 1 is shown. VLAG Peer 2 and all other VLAGs are configured in a similar fashion.

Configure the ISL

The ISL connecting the VLAG peers is shared by all their VLAGs. The ISL needs to be configured only once on each VLAG peer.

1. Configure STP if required. Use PVRST or MSTP mode only:

2. Configure the ISL ports and place them into a port trunk group:

Note: In this case, a dynamic trunk group is shown. A static trunk (portchannel) could be configured instead.

VLAG Peer 1Mgmt IP: 10.10.10.1/24

VLAG Peer 2Mgmt IP: 10.10.10.2/24

VLAG 1LACP 1000VLAN 100

VLAG 2LACP 2000VLAN 100

ISL

LACP 200

1

8 9 7 8

223

Client SwitchClient Switch

RS 8272(config)# spanningtree mode pvrst

RS 8272(config)# interface port 12RS 8272(configif)# switchport mode trunkRS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 200RS 8272(configif)# exitRS 8272(config)# vlag isl adminkey 200


3. Configure VLAG Tier ID and enable VLAG globally. This is used to identify the VLAG switch in a multi-tier environment.

4. Configure the ISL for the VLAG peer.

Make sure you configure the VLAG peer (VLAG Peer 2) using the same ISL trunk type (dynamic or static), the same VLAN, and the same STP mode and tier ID used on VLAG Peer 1.

Configure the VLAG

1. Configure the VLAN for VLAG 1. Make sure members include the ISL and VLAG 1 ports.

Note: In MSTP mode, VLANs are automatically mapped to CIST.

2. Place the VLAG 1 port(s) in a port trunk group:

3. Assign the trunk to the VLAG:

4. Continue by configuring all required VLAGs on VLAG Peer 1, and then repeat the configuration for VLAG Peer 2.

For each corresponding VLAG on the peer, the port trunk type (dynamic or static), VLAN, and STP mode and ID must be the same as on VLAG Peer 1.

5. Verify the completed configuration:

RS 8272(config)# vlag tierid 10RS 8272(config)# vlag enable

RS 8272(config)# vlan 100RS 8272(configvlan)# exitRS 8272(config)# interface port 12,8RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 100RS 8272(configif)# exit

RS 8272(config)# interface port 8RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1000RS 8272(configif)# exit

RS 8272(config)# vlag adminkey 1000 enable

# show vlag


VLAG Configuration - VLANs Mapped to MSTIFollow the steps below to configure VLAG in environments where the VLANs are mapped to Multiple Spanning Tree Instance (MSTI).

Configure the ISL

The ISL connecting the VLAG peers is shared by all their VLAGs. The ISL needs to be configured only once on each VLAG peer.

1. Configure STP:



3. Configure VLAG Tier ID and enable VLAG globally. This is used to identify the VLAG switch in a multi-tier environment.

4. Configure the ISL for the VLAG peer.

Make sure you configure the VLAG peer (VLAG Peer 2) using the same ISL trunk type (dynamic or static), the same VLAN, and the same STP mode and tier ID used on VLAG Peer 1.

Configure the VLAG

1. Configure the VLAN for VLAG 1.

Note: The VLAN is automatically mapped to CIST.

2. Shut down ISL ports and VLAG ports. This ensures that traffic passes through to other switches.

RS 8272(config)# spanningtree mode mst

RS 8272(config)# interface port 12RS 8272(configif)# switchport mode trunkRS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 200RS 8272(configif)# exitRS 8272(config)# vlag isl adminkey 200


RS 8272(config)# vlan 100RS 8272(configvlan)# exit

RS 8272(config)# interface port 12,8RS 8272(configif)# shutdown


3. Map the VLAN to an MSTI.

4. Disable VLAG.

5. Add VLAG ports to the VLAN.

6. Enable VLAG.



9. Continue by configuring all required VLAGs on VLAG Peer 1, then follow the steps for configuring VLAG Peer 2.

10. Configure the VLAN for VLAG 2.

Note: The VLAN is automatically mapped to CIST.

11. Map the VLAN to an MSTI.

Note: At this point, traffic may be momentarily disrupted due to STP recalculation.

12. Disable VLAG.


RS 8272(config)# spanningtree mst 1 vlan 100

RS 8272(config)# no vlag enable

RS 8272(config)# interface port 12,8RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan 100RS 8272(configif)# exit

RS 8272(config)# vlag enable




RS 8272(config)# spanningtree mst 1 vlan 100

RS 8272(config)# no vlag enable


13. Add VLAG ports to the VLAN.

14. Enable VLAG.


On VLAG Peer 1:

15. Enable ISL ports and VLAG ports:

On VLAG Peer2:




Configuring Health CheckWe strongly recommend that you configure the G8272 to check the health status of its VLAG peer. Although the operational status of the VLAG peer is generally determined via the ISL connection, configuring a network health check provides an alternate means to check peer status in case the ISL links fail. Use an independent link between the VLAG switches to configure health check. Note: Configuring health check on an ISL VLAN interface or on a VLAG data port may impact the accuracy of the health check status.

RS 8272(config)# interface port 12,8RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan 100RS 8272(configif)# exit

RS 8272(config)# vlag enable

RS 8272(config)# interface port 12,8RS 8272(configif)# no shutdown



RS 8272# show vlag


1. Configure a management interface for the switch. Note: If the switch does not have a dedicated management interface, configure a VLAN for the health check interface. The health check interface can be configured with an IPv4 or IPv6 address:

Note: Configure a similar interface on VLAG Peer 2. For example, use IP address 10.10.10.2.

2. Specify the IPv4 or IPv6 address of the VLAG Peer:

Note: For VLAG Peer 2, the management interface would be configured as 10.10.10.2, and the health check would be configured for 10.10.10.1, pointing back to VLAG Peer 1.

VLAGs with VRRPNote: In a multi-layer environment, configure VRRP separately for each layer. We recommend that you configure VRRP only on the tier with uplinks. See “Configuring VLAGs in Multiple Layers” on page 182.

VRRP (see “Virtual Router Redundancy Protocol” on page 501) can be used in conjunction with VLAGs and LACP-capable devices to provide seamless redundancy.

Figure 19. Active-Active Configuration using VRRP and VLAGs

Task 1: Configure VLAG Peer 1

Note: Before enabling VLAG, you must configure the VLAG tier ID and ISL portchannel.

RS 8272(config)# interface ip 128RS 8272(configipif)# ip address 10.10.10.1 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# vlag hlthchk peerip 10.10.10.2

Internet

10.0.1.1

10.0.1.2

10.0.1.3Layer 3

Router

Layer 3

Router1

2

4 5

4 5

1

2

Server 1

Server 2

Server 3

VLAG Peer 1

ISL

VLAG 1

VLAG 2

VLAG 3

VRRP Master

VRRP Backup

Network 10.0.1.0/24

VIR: 10.0.1.100

VLAG Peer 2

VIR: 10.0.1.100

10

11

12

10

11

12


1. Configure VLAG tier ID and enable VLAG globally.

2. Configure appropriate routing.

Although OSPF is used in this example, static routing could also be deployed. For more information, see “OSPF” on page 443 or “Basic IP Routing” on page 325.

3. Configure a server-facing interface.

4. Turn on VRRP and configure the Virtual Interface Router.

5. Set the priority of Virtual Router 1 to 101, so that it becomes the Master.



7. Configure the upstream ports.


RS 8272(config)# router ospfRS 8272(configrouterospf)# area 1 areaid 0.0.0.1RS 8272(configrouterospf)# enableRS 8272(configrouterospf)# exit

RS 8272(config)# interface ip 3RS 8272(configipif)# ip address 10.0.1.10 255.255.255.0RS 8272(configipif)# vlan 100RS 8272(configipif)# exit

RS 8272(config)# router vrrpRS 8272(configvrrp)# enableRS 8272(configvrrp)# virtualrouter 1 virtualrouterid 1RS 8272(configvrrp)# virtualrouter 1 interface 3RS 8272(configvrrp)# virtualrouter 1 address 10.0.1.100RS 8272(configvrrp)# virtualrouter 1 enable

RS 8272(configvrrp)# virtualrouter 1 priority 101RS 8272(configvrrp)# exit

RS 8272(config)# interface port 45RS 8272(configif)# switchport mode trunkRS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 2000RS 8272(configif)# exit

RS 8272(config)# interface port 1RS 8272(configif)# switchport access vlan 10RS 8272(configif)# exitRS 8272(config)# interface port 2RS 8272(configif)# switchport access vlan 20RS 8272(configif)# exit


8. Configure the server ports.

9. Configure all VLANs including VLANs for the VLAGs.

10. Configure Internet-facing interfaces.

RS 8272(config)# interface port 10RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exitRS 8272(config)# interface port 11RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exitRS 8272(config)# interface port 12RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exit

RS 8272(config)# vlan 10RS 8272(configvlan)# exitRS 8272(config)# interface port 1RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 10RS 8272(configif)# exit


RS 8272(config)# vlan 100RS 8272(configvlan)# exitRS 8272(config)# interface port 45, 1012RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 100RS 8272(configif)# exit

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 172.1.1.10 255.255.255.0RS 8272(configipif)# vlan 10RS 8272(configipif)# enableRS 8272(configipif)# ip ospf area 1RS 8272(configipif)# ip ospf enableRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip address 172.1.3.10 255.255.255.0RS 8272(configipif)# vlan 20RS 8272(configipif)# enableRS 8272(configipif)# ip ospf area 1RS 8272(configipif)# ip ospf enableRS 8272(configipif)# exit


11. Place the VLAG port(s) in their port trunk groups.

12. Assign the trunks to the VLAGs:


Task 2: Configure VLAG Peer 2

The VLAG peer (VLAG Peer 2) must be configured using the same ISL trunk type (dynamic or static), the same VLAN, and the same STP mode and Tier ID used on VLAG Switch 1.

For each corresponding VLAG on the peer, the port trunk type (dynamic or static), VLAN, and STP mode and ID must be the same as on VLAG Switch 1.


2. Configure appropriate routing.

Although OSPF is used in this example, static routing could also be deployed.

3. Configure a server-facing interface.

RS 8272(config)# interface port 10RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1000RS 8272(configif)# exitRS 8272(config)# interface port 11RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1100RS 8272(configif)# exitRS 8272(config)# interface port 12RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1200RS 8272(configif)# exit

RS 8272(config)# vlag adminkey 1000 enableRS 8272(config)# vlag adminkey 1100 enableRS 8272(config)# vlag adminkey 1200 enable

# show vlag


RS 8272(config)# router ospfRS 8272(configrouterospf)# area 1 areaid 0.0.0.1RS 8272(configrouterospf)# enableRS 8272(configrouterospf)# exit

RS 8272(config)# interface ip 3RS 8272(configipif)# ip address 10.0.1.11 255.255.255.0RS 8272(configipif)# vlan 100RS 8272(configipif)# exit


4. Turn on VRRP and configure the Virtual Interface Router.


6. Configure the upstream ports.

7. Configure the server ports.

RS 8272(config)# router vrrpRS 8272(configvrrp)# enableRS 8272(configvrrp)# virtualrouter 1 virtualrouterid 1RS 8272(configvrrp)# virtualrouter 1 interface 3RS 8272(configvrrp)# virtualrouter 1 address 10.0.1.100RS 8272(configvrrp)# virtualrouter 1 enable

RS 8272(config)# interface port 45RS 8272(configif)# switchport mode trunkRS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 2000RS 8272(configif)# exit

RS 8272(config)# interface port 1RS 8272(configif)# switchport access vlan 30RS 8272(configif)# exitRS 8272(config)# interface port 2RS 8272(configif)# switchport access vlan 40RS 8272(configif)# exit

RS 8272(config)# interface port 10RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exitRS 8272(config)# interface port 11RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exitRS 8272(config)# interface port 12RS 8272(configif)# switchport access vlan 100RS 8272(configif)# exit


8. Configure all VLANs including VLANs for the VLAGs.

9. Configure Internet-facing interfaces.

10. Place the VLAG port(s) in their port trunk groups.



RS 8272(config)# vlan 100RS 8272(configvlan)# exitRS 8272(config)# interface port 45,1012RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 100RS 8272(configif)# exit

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 172.1.2.11 255.255.255.0RS 8272(configipif)# vlan 30RS 8272(configipif)# enableRS 8272(configipif)# ip ospf area 1RS 8272(configipif)# ip ospf enableRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip address 172.1.4.12 255.255.255.0RS 8272(configipif)# vlan 40RS 8272(configipif)# enableRS 8272(configipif)# ip ospf area 1RS 8272(configipif)# ip ospf enableRS 8272(configipif)# exit

RS 8272(config)# interface port 10RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1000RS 8272(configif)# exitRS 8272(config)# interface port 11RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1100RS 8272(configif)# exitRS 8272(config)# interface port 12RS 8272(configif)# lacp mode activeRS 8272(configif)# lacp key 1200RS 8272(configif)# exit


11. Assign the trunks to the VLAGs:


Configuring VLAGs in Multiple Layers

Figure 20. VLAG in Multiple Layers

Figure 20 shows an example of VLAG being used in a multi-layer environment. Following are the configuration steps for the topology.

Task 1: Configure Layer 2/3 border switches.

Configure ports on border switch as follows:

Repeat these commands for the second border switch.

RS 8272(config)# vlag adminkey 1000 enableRS 8272(config)# vlag adminkey 1100 enableRS 8272(config)# vlag adminkey 1200 enable

# show vlag

ISL

VLAG 3

VLAG 5 VLAG 6

TrunkTrunk

VLAG 2

Trunk

ISL

ISL

Layer 2/3 Border

Layer 2 Regionwith multiple levels

Servers

VLAGPeers C

VLAGPeers B

VLAGPeers A

VLAG 1

Trunk

Trunk

VLAG 4

LACP-capableServer

LACP-capableSwitch

LACP-capableRouters

Switch A Switch B

Switch C Switch D Switch E Switch F

Switch G

VLAG 3

RS 8272(config)# interface port 1,2RS 8272(configif)# lacp key 100RS 8272(configif)# lacp mode activeRS 8272(configif)# exit


Task 2: Configure switches in the Layer 2 region.

Consider the following:

ISL ports on switches A and B - ports 1, 2

Ports connecting to Layer 2/3 - ports 5, 6

Ports on switches A and B connecting to switches C and D: ports 10, 11

Ports on switch B connecting to switch E: ports 15, 16

Ports on switch B connecting to switch F: ports 17, 18


2. Configure ISL ports on Switch A.

3. Configure port on Switch A connecting to Layer 2/3 router 1.

Repeat these steps on Switch B for ports connecting to Layer 2/3 router 1.


RS 8272(config)# interface port 1,2RS 8272(configif)# switchport mode trunkRS 8272(configif)# lacp key 200RS 8272(configif)# lacp mode activeRS 8272(configif)# exit

RS 8272(config)# vlag isl adminkey 200RS 8272(configvlan)# exit

RS 8272(config)# vlan 10 VLAN number 10 with name “VLAN 10” created VLAN 10 was assigned to STG 10RS 8272(configvlan)# exitRS 8272(config)# interface port 1,2,5RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 10RS 8272(configif)# exit

RS 8272(config)# interface port 5RS 8272(configif)# lacp key 400RS 8272(configif)# lacp mode activeRS 8272(configif)# exit



4. Configure port on Switch A connecting to Layer 2/3 router 2.

Repeat these commands on Switch B for ports connecting to Layer 2/3 router 2.

5. Configure ports on Switch A connecting to downstream VLAG switches C and D.

Repeat these commands on Switch B for ports connecting to downstream VLAG switch C and D.

6. Configure ports on Switch B connecting to downstream switches E and F.

7. Configure ISL between switches C and D, and between E and F as shown in Step 1.

8. Configure the Switch G as shown in Step 2.

RS 8272(config)# vlan 20 VLAN number 20 with name “VLAN 20” created VLAN 20 was assigned to STG 20RS 8272(configvlan)# exitRS 8272(config)# interface port 1,2,6RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 20RS 8272(configif)# exit



RS 8272(config)# vlan 20RS 8272(configvlan)# exitRS 8272(config)# interface port 10,11RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 20RS 8272(configif)# lacp key 600RS 8272(configif)# lacp mode activeRS 8272(configif)# exit


RS 8272(config)# vlan 30RS 8272(configvlan)# exitRS 8272(config)# interface port 1518RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 30RS 8272(configif)# lacp key 700RS 8272(configif)# lacp mode activeRS 8272(configif)# exit


VLAG with PIMProtocol Independent Multicast (PIM) is designed for efficiently routing multicast traffic across one or more IPv4 domains. PIM is used by multicast source stations, client receivers, and intermediary routers and switches, to build and maintain efficient multicast routing trees. PIM is protocol independent; It collects routing information using the existing unicast routing functions underlying the IPv4 network, but does not rely on any particular unicast protocol. For PIM to function, a Layer 3 routing protocol (such as BGP, OSPF, RIP, or static routes) must first be configured on the switch.

Lenovo Networking OS supports PIM in Sparse Mode (PIM-SM) and Dense Mode (PIM-DM). For more details on PIM, see Chapter 33, “Protocol Independent Multicast” on page 475.

PIM, when configured in a VLAG topology, provides efficient multicast routing along with redundancy and failover. Only the primary VLAG switch forwards multicast data packets to avoid duplicate packets reaching the access layer switch. The secondary VLAG switch is available as backup and forwards packets only when the primary VLAG switch is not available and during failover.

See Figure 18 on page 171 for a basic VLAG topology. For PIM to function in a VLAG topology, the following are required:

IGMP (v1 or v2) must be configured on the VLAG switches.

A Layer 3 routing protocol (such as BGP, OSPF, RIP, or static routes) must be globally enabled and on VLAG-associated IP interfaces for multicast routing.

The VLAG switches must be connected to upstream multicast routers.

The Rendezvous Point (RP) and/or the Bootstrap router (BSR) must be configured on the upstream router.

Flooding must be disabled on the VLAG switches or in the VLAN associated with the VLAG ports.

ISL ports must be members of VLANs that have VLAG ports as members.

For PIM configuration steps and commands, see “PIM Configuration Examples” on page 485.

Traffic Forwarding

In a VLAG with PIM topology, traffic forwarded by the upstream router is managed as follows:

If the primary and secondary VLAG ports are up, the primary switch forwards traffic to the receiver. The secondary switch blocks the traffic. Multicast entries are created on both the VLAG switches: primary VLAG switch with forward state; secondary VLAG switch with pruned state.

If the primary VLAG port fails, the secondary VLAG switch forwards traffic to the receiver. Multicast entries are created on both the VLAG switches: primary VLAG switch with forward state; secondary VLAG switch with VLAG pruned state.


If the secondary VLAG port fails, the primary VLAG switch forwards traffic to the receiver. Multicast entries are created on both the VLAG switches: primary VLAG switch with forward state; secondary VLAG switch with pruned state.

If the primary VLAG switch is down, the secondary VLAG switch forwards traffic to the receiver. When the primary VLAG switch boots up again, it becomes the secondary VLAG switch and blocks traffic to the receiver. The VLAG switch that was secondary initially becomes the primary and continues forwarding traffic to the receiver.

If the secondary VLAG switch is down, the primary VLAG switch forwards traffic to the receiver. When the secondary VLAG switch is up, it blocks traffic. The primary switch forwards traffic to the receiver.

If the uplink to the primary VLAG switch is down, the secondary VLAG switch forwards traffic to the receiver and to the primary VLAG switch over the ISL. The primary VLAG switch blocks traffic to the receiver so the receiver does not get double traffic. Both the VLAG switches will have multicast entries in forward state.

If the uplink to the secondary VLAG switch is down, the primary VLAG switch forwards traffic to the receiver and to the secondary VLAG switch over the ISL. The secondary VLAG switch blocks traffic to the receiver so the receiver does not get double traffic. Both the VLAG switches will have multicast entries in the forward state.

Health Check

In a VLAG with PIM topology, you must configure health check. See “Configuring Health Check” on page 175.

When health check is configured, and the ISL is down, the primary VLAG switch forwards traffic to the receiver. The secondary VLAG switch ports will be errdisable state and will block traffic to the receiver.


Chapter 12. Quality of Service

Quality of Service features allow you to allocate network resources to mission-critical applications at the expense of applications that are less sensitive to such factors as time delays or network congestion. You can configure your network to prioritize specific types of traffic, ensuring that each type receives the appropriate Quality of Service (QoS) level.


“QoS Overview” on page 188

“Using ACL Filters” on page 189

“Using DSCP Values to Provide QoS” on page 191

“Using 802.1p Priority to Provide QoS” on page 197

“Queuing and Scheduling” on page 198

“Control Plane Protection” on page 198

“WRED with ECN” on page 199


QoS Overview QoS helps you allocate guaranteed bandwidth to the critical applications, and limit bandwidth for less critical applications. Applications such as video and voice must have a certain amount of bandwidth to work correctly; using QoS, you can provide that bandwidth when necessary. Also, you can put a high priority on applications that are sensitive to timing out or that cannot tolerate delay, by assigning their traffic to a high-priority queue.

By assigning QoS levels to traffic flows on your network, you can ensure that network resources are allocated where they are needed most. QoS features allow you to prioritize network traffic, thereby providing better service for selected applications.

Figure 21 shows the basic QoS model used by the switch.

Figure 21. QoS Model

The basic QoS model works as follows:

Classify traffic: Read DSCP value. Read 802.1p priority value. Match ACL filter parameters.

Perform actions: Define bandwidth and burst parameters Select actions to perform on in-profile and out-of-profile traffic Deny packets Permit packets Mark DSCP or 802.1p Priority Set COS queue (with or without re-marking)

Queue and schedule traffic: Place packets in one of the COS queues. Schedule transmission based on the COS queue.

Ports

ACLFilter

Permit/Deny

ClassifyPackets

PerformActions

EgressIngress

COSQueue

Queue andSchedule

© Copyright Lenovo 2015 Chapter 12: Quality of Service 189

Using ACL FiltersAccess Control Lists (ACLs) are filters that allow you to classify and segment traffic, so you can provide different levels of service to different traffic types. Each filter defines the conditions that must match for inclusion in the filter, and also the actions that are performed when a match is made.

Lenovo Networking OS 8.2 supports up to 256 ACLs.

The G8272 allows you to classify packets based on various parameters. For example: Ethernet: source MAC, destination MAC, VLAN number/mask, Ethernet type,

priority. IPv4: Source IP address/mask, destination address/mask, type of service, IP pro-

tocol number. TCP/UPD: Source port, destination port, TCP flag. Packet format

For ACL details, see “Access Control Lists” on page 103.

Summary of ACL Actions

Actions determine how the traffic is treated. The G8272 QoS actions include the following: Pass or Drop Re-mark a new DiffServ Code Point (DSCP) Re-mark the 802.1p field Set the COS queue


ACL Metering and Re-Marking

You can define a profile for the aggregate traffic flowing through the G8272 by configuring a QoS meter (if desired) and assigning ACLs to ports. When you add ACLs to a port, make sure they are ordered correctly in terms of precedence.

Actions taken by an ACL are called In-Profile actions. You can configure additional In-Profile and Out-of-Profile actions on a port. Data traffic can be metered, and re-marked to ensure that the traffic flow provides certain levels of service in terms of bandwidth for different types of network traffic.

Metering

QoS metering provides different levels of service to data streams through user-configurable parameters. A meter is used to measure the traffic stream against a traffic profile, which you create. Thus, creating meters yields In-Profile and Out-of-Profile traffic for each ACL, as follows:

In-Profile–If there is no meter configured or if the packet conforms to the meter, the packet is classified as In-Profile.

Out-of-Profile–If a meter is configured and the packet does not conform to the meter (exceeds the committed rate or maximum burst rate of the meter), the packet is classified as Out-of-Profile.

Using meters, you set a Committed Rate in Kbps (multiples of 64 Mbps). All traffic within this Committed Rate is In-Profile. Additionally, you set a Maximum Burst Size that specifies an allowed data burst larger than the Committed Rate for a brief period. These parameters define the In-Profile traffic.

Meters keep the sorted packets within certain parameters. You can configure a meter on an ACL, and perform actions on metered traffic, such as packet re-marking.

Re-Marking

Re-marking allows for the treatment of packets to be reset based on new network specifications or desired levels of service. You can configure the ACL to re-mark a packet as follows:

Change the DSCP value of a packet, used to specify the service level traffic receives.

Change the 802.1p priority of a packet.


Using DSCP Values to Provide QoSThe switch uses the Differentiated Services (DiffServ) architecture to provide QoS functions. DiffServ is described in IETF RFCs 2474 and 2475.

The six most significant bits in the TOS byte of the IP header are defined as DiffServ Code Points (DSCP). Packets are marked with a certain value depending on the type of treatment the packet must receive in the network device. DSCP is a measure of the Quality of Service (QoS) level of the packet.

The switch can classify traffic by reading the DiffServ Code Point (DSCP) or IEEE 802.1p priority value, or by using filters to match specific criteria. When network traffic attributes match those specified in a traffic pattern, the policy instructs the switch to perform specified actions on each packet that passes through it. The packets are assigned to different Class of Service (COS) queues and scheduled for transmission.

Differentiated Services Concepts

To differentiate between traffic flows, packets can be classified by their DSCP value. The Differentiated Services (DS) field in the IP header is an octet, and the first six bits, called the DS Code Point (DSCP), can provide QoS functions. Each packet carries its own QoS state in the DSCP. There are 64 possible DSCP values (0-63).

Figure 22. Layer 3 IPv4 packet

The switch can perform the following actions to the DSCP: Read the DSCP value of ingress packets. Re-mark the DSCP value to a new value Map the DSCP value to a Class of Service queue (COSq).

The switch can use the DSCP value to direct traffic prioritization.

With DiffServ, you can establish policies to direct traffic. A policy is a traffic-controlling mechanism that monitors the characteristics of the traffic, (for example, its source, destination, and protocol) and performs a controlling action on the traffic when certain characteristics are matched.

7 6 5 4 3 2 1 0

Differentiated Services Code Point (DSCP) unused

VersionLength ToS Length ID Offset TTL Proto FCS DIPSIP Data


Trusted/Untrusted Ports

By default, all ports on the G8272 are trusted. To configure untrusted ports, re-mark the DSCP value of the incoming packet to a lower DSCP value using the following commands:

Per Hop Behavior

The DSCP value determines the Per Hop Behavior (PHB) of each packet. The PHB is the forwarding treatment given to packets at each hop. QoS policies are built by applying a set of rules to packets, based on the DSCP value, as they hop through the network.

The default settings are based on the following standard PHBs, as defined in the IEEE standards:

Expedited Forwarding (EF)—This PHB has the highest egress priority and lowest drop precedence level. EF traffic is forwarded ahead of all other traffic. EF PHB is described in RFC 2598.

Assured Forwarding (AF)—This PHB contains four service levels, each with a different drop precedence, as shown in the following table. Routers use drop precedence to determine which packets to discard last when the network becomes congested. AF PHB is described in RFC 2597.

RS 8272(config)# interface port 1RS 8272(configif)# dscpmarkingRS 8272(configif)# exitRS 8272(config)# qos dscp dscpmapping <DSCP value (0-63)> <new value>RS 8272(config)# qos dscp remarking

DropPrecedence

Class 1 Class 2 Class 3 Class 4

Low AF11 (DSCP 10) AF21 (DSCP 18) AF31 (DSCP 26) AF41 (DSCP 34)

Medium AF12 (DSCP 12) AF22 (DSCP 20) AF32 (DSCP 28) AF42 (DSCP 36)

High AF13 (DSCP 14) AF23 (DSCP 22) AF33 (DSCP 30) AF43 (DSCP 38)


Class Selector (CS)—This PHB has eight priority classes, with CS7 representing the highest priority, and CS0 representing the lowest priority, as shown in the following table. CS PHB is described in RFC 2474.

QoS Levels

Table 18 shows the default service levels provided by the switch, listed from highest to lowest importance:

Priority Class Selector DSCP

Highest CS7 56

CS6 48

CS5 40

CS4 32

CS3 24

CS2 16

CS1 8

Lowest CS0 0

Table 18. Default QoS Service Levels

Service Level Default PHB 802.1p Priority

Critical CS7 7

Network Control CS6 6

Premium EF, CS5 5

Platinum AF41, AF42, AF43, CS4 4

Gold AF31, AF32, AF33, CS3 3

Silver AF21, AF22, AF23, CS2 2

Bronze AF11, AF12, AF13, CS1 1

Standard DF, CS0 0


DSCP Re-Marking and Mapping

The switch can use the DSCP value of ingress packets to re-mark the DSCP to a new value, and to set an 802.1p priority value. Use the following command to view the default settings.

Use the following command to turn on DSCP re-marking globally:

Then you must enable DSCP re-marking on any port that you wish to perform this function (Interface Port mode). Note: If an ACL meter is configured for DSCP re-marking, the meter function takes precedence over QoS re-marking.

DSCP Re-Marking Configuration Examples

Example 1

The following example includes the basic steps for re-marking DSCP value and mapping DSCP value to 802.1p.

RS 8272# show qos dscpCurrent DSCP Remarking Configuration: OFF

DSCP New DSCP New 802.1p Prio 0 0 0 1 1 0 2 2 0 3 3 0 4 4 0 5 5 0 6 6 0 7 7 0 8 8 1 9 9 0 10 10 1... 54 54 0 55 55 0 56 56 7 57 57 0 58 58 0 59 59 0 60 60 0 61 61 0 62 62 0 63 63 0

RS 8272(config)# qos dscp remarking


1. Turn DSCP re-marking on globally, and define the DSCP-DSCP-802.1p mapping. You can use the default mapping.

2. Enable DSCP re-marking on a port.

Example 2

The following example assigns strict priority to VoIP traffic and a lower priority to all other traffic.

1. Create an ACL to re-mark DSCP value and COS queue for all VoIP packets.

2. Create an ACL to set a low priority to all other traffic.

3. Apply the ACLs to a port and enable DSCP marking.

4. Enable DSCP re-marking globally.

5. Assign the DSCP re-mark value.

6. Assign strict priority to VoIP COS queue.

RS 8272(config)# qos dscp remarkingRS 8272(config)# qos dscp dscpmapping <DSCP value (0-63)> <new value>RS 8272(config)# qos dscp dot1pmapping <DSCP value (0-63)> <802.1p value>

RS 8272(config)# interface port 1RS 8272(configif)# qos dscp remarkingRS 8272(configif)# exit

RS 8272(config)# accesscontrol list 2 tcpudp sourceport 5060 0xffffRS 8272(config)# accesscontrol list 2 meter committedrate 10000000RS 8272(config)# accesscontrol list 2 meter enableRS 8272(config)# accesscontrol list 2 remark inprofile dscp 56RS 8272(config)# accesscontrol list 2 remark dot1p 7RS 8272(config)# accesscontrol list 2 action permit

RS 8272(config)# accesscontrol list 3 action setpriority 1RS 8272(config)# accesscontrol list 3 action permit

RS 8272(config)# interface port 5RS 8272(configif)# accesscontrol list 2RS 8272(configif)# accesscontrol list 3 ethernet sourcemacaddress 00:00:00:00:00:00 00:00:00:00:00:00RS 8272(configif)# dscpmarkingRS 8272(configif)# exit

RS 8272(config)# qos dscp remarking

RS 8272(config)# qos dscp dscpmapping 40 9RS 8272(config)# qos dscp dscpmapping 46 9

RS 8272(config)# qos transmitqueue weightcos 7 0


7. Map priority value to COS queue for non-VoIP traffic.

8. Assign weight to the non-VoIP COS queue.

RS 8272(config)# qos transmitqueue mapping 1 1

RS 8272(config)# qos transmitqueue weightcos 1 2


Using 802.1p Priority to Provide QoSThe G8272 provides Quality of Service functions based on the priority bits in a packet’s VLAN header. (The priority bits are defined by the 802.1p standard within the IEEE 802.1Q VLAN header.) The 802.1p bits, if present in the packet, specify the priority to be given to packets during forwarding. Packets with a numerically higher (non-zero) priority are given forwarding preference over packets with lower priority value.

The IEEE 802.1p standard uses eight levels of priority (0-7). Priority 7 is assigned to highest priority network traffic, such as OSPF or RIP routing table updates, priorities 5-6 are assigned to delay-sensitive applications such as voice and video, and lower priorities are assigned to standard applications. A value of 0 (zero) indicates a “best effort” traffic prioritization, and this is the default when traffic priority has not been configured on your network. The switch can filter packets based on the 802.1p values.

Figure 23. Layer 2 802.1q/802.1p VLAN tagged packet

Ingress packets receive a priority value, as follows:

Tagged packets—switch reads the 802.1p priority in the VLAN tag.

Untagged packets—switch tags the packet and assigns an 802.1p priority value, based on the port’s default 802.1p priority.

Egress packets are placed in a COS queue based on the priority value, and scheduled for transmission based on the COS queue number. Higher COS queue numbers provide forwarding precedence.

To configure a port’s default 802.1p priority value, use the following commands.

RS 8272(config)# interface port 1RS 8272(configif)# dot1p <802.1p value (0-7)>RS 8272(configif)# exit

7 6 5 4 3 2 1 0

Priority

7 6 5 4 3 2 1 0

VLAN Identifier (VID)

SFD DMAC SMAC Tag E Type Data FCSPreamble


Queuing and SchedulingThe G8272 can be configured to have 8 output Class of Service (COS) queues per port, into which each packet is placed. Each packet’s 802.1p priority determines its COS queue, except when an ACL action sets the COS queue of the packet.

You can configure the following attributes for COS queues:

Map 802.1p priority value to a COS queue

Define the scheduling weight of each COS queue

You can map 802.1p priority value to a COS queue, as follows:

To set the COS queue scheduling weight, use the following command.

Control Plane ProtectionControl plane receives packets that are required for the internal protocol state machines. This type of traffic is usually received at low rate. However, in some situations such as DOS attacks, the switch may receive this traffic at a high rate. If the control plane protocols are unable to process the high rate of traffic, the switch may become unstable.

The control plane receives packets that are channeled through protocol-specific packet queues. Multiple protocols can be channeled through a common packet queue. However, one protocol cannot be channeled through multiple packet queues. These packet queues are applicable only to the packets received by the software and does not impact the regular switching or routing traffic. Packet queue with a higher number has higher priority.

You can configure the bandwidth for each packet queue. Protocols that share a packet queue will also share the bandwidth.

The following commands configure the control plane protection (CoPP) feature:

RS 8272(config)# qos transmitqueue mapping <802.1p priority value (0-7)> <COS queue (0-7)>

RS 8272(config)# qos transmitqueue weightcos <COSq number> <COSq weight (0-15)>

RS 8272(config)# qos protocolpacketcontrol packetqueuemap <0-43><protocol> (Configure a queue for a protocol)

RS 8272(config)# qos protocolpacketcontrol ratelimitpacketqueue<0-43> <1-10000> (Set the bandwidth for the queue, in packets per second)


WRED with ECNWeighted Random Early Detection (WRED) is a congestion avoidance algorithm that helps prevent a TCP collapse, where a congested port indiscriminately drops packets from all sessions. The transmitting hosts wait to retransmit resulting in a dramatic drop in throughput. Often times, this TCP collapse repeats in a cycle, which results in a saw-tooth pattern of throughput. WRED selectively drops packets before the queue gets full, allowing majority of the traffic to flow smoothly.

WRED discards packets based on the CoS queues. Packets marked with lower priorities are discarded first.

Explicit Congestion Notification (ECN) is an extension to WRED. For packets that are ECN-aware, the ECN bit is marked to signal impending congestion instead of dropping packets. The transmitting hosts then slow down sending packets.

How WRED/ECN work together

For implementing WRED, you must define a profile with minimum threshold, maximum threshold, and a maximum drop probability. The profiles can be defined on a port or a CoS.

For implementing ECN, you require ECN-specific field that has two bits—the ECN-capable Transport (ECT) bit and the CE (Congestion Experienced) bit—in the IP header. ECN is identified and defined by the values in these bits in the Differentiated Services field of IP Header. Table 19 shows the combination values of the ECN bits.

Table 19. ECN Bit Setting

ECT Bit CE Bit Description

0 0 Not ECN-capable

0 1 Endpoints of the transport protocol are ECN-capable

1 0 Endpoints of the transport protocol are ECN-capable

1 1 Congestion experienced


WRED and ECN work together as follows:

If the number of packets in the queue is less than the minimum threshold, packets are transmitted. This happens irrespective of the ECN bit setting, and on networks where only WRED (without ECN) is enabled.

If the number of packets in the queue is between the minimum threshold and the maximum threshold, one of the following occurs: If the ECN field on the packet indicates that the endpoints are ECN-capable

and the WRED algorithm determines that the packet has likely been dropped based on the drop probability, the ECT and CE bits for the packet are changed to 1, and the packet is transmitted.

If the ECN field on the packet indicates that neither endpoint is ECN-capable, the packet may be dropped based on the WRED drop probability. This is true even in cases where only WRED (without ECN) is enabled.

If the ECN field on the packet indicates that the network is experiencing congestion, the packet is transmitted. No further marking is required.

If the number of packets in the queue is greater than the maximum threshold, packets are dropped based on the drop probability. This is the identical treatment a packet receives when only WRED (without ECN) is enabled.

Configuring WRED/ECN

For configuring WRED, you must define a TCP profile and a non-TCP profile. WRED prioritizes TCP traffic over non-TCP traffic.

For configuring ECN, you must define a TCP profile. You don’t need a non-TCP profile as ECN can be enabled only for TCP traffic.

If you do not configure the profiles, the profile thresholds are set to maximum value of 0xFFFF to avoid drops.Note: WRED/ECN can be configured only on physical ports and not on trunks. WRED and ECN are applicable only to unicast traffic.

Consider the following guidelines for configuring WRED/ECN:

Profiles can be configured globally or per port. Global profiles are applicable to all ports.

Always enable the global profile before applying the port-level profile.Note: You can enable the global profile and disable the port-level profile. However, you must not enable the port-level profile if the global profile is disabled.

WRED settings are dependent on Memory Management Unit (MMU) Settings. If you change the MMU setting, it could impact WRED functionality.

You cannot enable WRED if you have QoS buffer settings such as Converged Enhanced Ethernet (CEE), Priority-based Flow Control (PFC), or Enhanced Transmission Selection (ETS).

The number of WRED profiles per-port must match the total number of COS Queues configured in the system.

If you have configured a TCP profile and enabled ECN, ECN remarking happens only if all traffic experiencing congestion is TCP traffic.

Configure a TCP profile only after enabling ECN on the interface.


You can apply TCP and non-TCP profile configurations irrespective of ECN status (enabled/disabled).

WRED/ECN Configuration Example

Follow these steps to enable WRED/ECN and configure a global and/or port-level profile. If you configure global and port-level profile, WRED/ECN uses the port-level profile to make transmit/drop decisions when experiencing traffic congestion.

Configure Global Profile for WRED

1. Enable WRED globally.

2. Enable a transmit queue.

3. Configure WRED thresholds (minimum, maximum, and drop rate) for TCP traffic.

Note: Percentages are of Average Queue available in hardware and not percentages of traffic.

4. Configure WRED thresholds (minimum, maximum, and drop rate) for non-TCP traffic.

5. Select the port.

6. Enable WRED for the port.

Configure Port-level Profile for WRED

1. Enable WRED globally.

2. Select the port.

RS 8272(config)# qos randomdetect enable

RS 8272(config)# qos randomdetect transmitqueue 0 enable

RS 8272(config)# qos randomdetect transmitqueue 0 tcp minthreshold 1 maxthreshold 2 droprate 3

RS 8272(config)# qos randomdetect transmitqueue 0 nontcp minthreshold 4 maxthreshold 5 droprate 6

RS 8272(config)# interface port 1

RS 8272(configif)# randomdetect enableRS 8272(configif)# exit

RS 8272(config)# qos randomdetect enable



3. Enable WRED for the port .


5. Configure WRED thresholds (minimum, maximum, and drop rate) for TCP traffic.


6. Configure WRED thresholds (minimum, maximum, and drop rate) for non-TCP traffic.

Configure Global Profile for ECN

1. Enable ECN globally.


3. Configure ECN thresholds (minimum, maximum, and drop rate) for TCP traffic.


4. Select the port.

5. Enable ECN for the port.

RS 8272(configif)# randomdetect enable

RS 8272(configif)# randomdetect transmitqueue 0 enable

RS 8272(configif)# randomdetect transmitqueue 0 tcp minthreshold 11 maxthreshold 22 droprate 33

RS 8272(configif)# randomdetect transmitqueue 0 nontcp minthreshold 44 maxthreshold 55 droprate 66

RS 8272(configif)# exit

RS 8272(config)# qos randomdetect ecn enable

RS 8272(config)# qos randomdetect transmitqueue 0 enable

RS 8272(config)# qos randomdetect transmitqueue 0 tcp minthreshold 1 maxthreshold 2 droprate 3


RS 8272(configif)# randomdetect ecn enableRS 8272(configif)# exit


Configure Port-level Profile for ECN

1. Enable ECN globally.

2. Select the port.

3. Enable ECN for the port.


5. Configure ECN thresholds (minimum, maximum, and drop rate) for TCP traffic.


Verifying WRED/ECN

Use the following command to view global WRED/ECN information.

RS 8272(config)# qos randomdetect ecn enable


RS 8272(configif)# randomdetect ecn enable

RS 8272(configif)# randomdetect transmitqueue 0 enable

RS 8272(configif)# randomdetect transmitqueue 0 tcp minthreshold 11 maxthreshold 22 droprate 33

RS 8272(configif)# exit

RS 8272(config)# show qos randomdetectCurrent wred and ecn configuration:Global ECN: EnableGlobal WRED: EnableTQ0:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Ena 10 20 30 10 20 30TQ1:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ2:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ3:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ4:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ5:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ6:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ7:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0


Use the following command to view port-level WRED/ECN information.

RS 8272(config)# show interface port 1 randomdetectPort: 1 ECN: Enable WRED: EnableTQ0:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ1:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Ena 4 5 6 1 2 3TQ2:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ3:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ4:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ5:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ6:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0TQ7:WREDTcpMinThrTcpMaxThrTcpDrateNonTcpMinThrNonTcpMaxThrNonTcpDrate Dis 0 0 0 0 0 0

© Copyright Lenovo 2015 Chapter 13: Precision Time Protocol 205

Chapter 13. Precision Time Protocol

As defined in the IEEE 1588-2008 standard, Precision Time Protocol (PTP) is a precision clock synchronization protocol for networked measurement and control systems. PTP provides system-wide synchronization accuracy and precision in the sub-microsecond range with minimal network and local clock computing resources. The synchronization is achieved through the exchange of messages: General messages that carry data but need not be time stamped; Event messages that are time stamped and are critical for clock synchronization accuracy.

A PTP network consists of PTP-enabled devices such as switches or routers. These devices consist of the following types of clocks:

Master clock: In a PTP domain, the clock with the most precise time is considered the master clock. A best master clock algorithm determines the highest quality clock in a network.

Ordinary clock: An ordinary clock synchronizes its time with the Master clock. The ordinary clock has a bidirectional communication with the master clock. By receiving synchronization/delay response and sending delay request packets, the ordinary clock adjusts its time with the master clock.

Boundary clock: A boundary clock connects to multiple networks. It synchronizes with the attached master clock and in turn acts as a master clock to all attached ordinary clocks. Boundary clocks help to reduce the effect of jitter in Ethernet-based networks.

Transparent clock: A transparent clock listens for PTP packets and adjusts the correction field in the PTP event packets as they pass the PTP device.

RackSwitch G8272 supports the configuration of ordinary clock and transparent clock. It cannot be a master clock as the switch does not participate in the master clock selection process. Note: Lenovo Networking OS does not support IPv6 for PTP.

By default, PTP version 2 is installed on the switch but is globally disabled. Use the following command to globally enable PTP:

PTP is configured on switch ports. In case of trunk ports, the PTP configuration must be the same on all ports participating in the same trunk. The switch uses only one port from a trunk (typically the one used by a multicast protocol) to forward PTP packets.

By default, PTP is enabled on all the switch ports. To disable PTP on a port, use the following commands:

Note: PTP cannot be enabled on management ports.

RS 8272(config)# ptp ordinary|transparent enable

RS 8272(config)# interface port <port number>RS 8272(configif)# no ptp


PTP packets have a Control Plane Protection (CoPP) queue of 36. You can change this CoPP priority using the following command:

You can modify the PTP queue rate using the following command:

Ordinary Clock Mode

When the RackSwitch G8272 is configured as an ordinary clock, it synchronizes its clock with the master clock. If the G8272 does not detect a master clock, it will not synchronize its clock with any other device. In this mode, the G8272’s clock cannot be modified manually or using another time protocol such as Network Time Protocol (NTP).

As an ordinary clock, the G8272 synchronizes with a single PTP domain. The switch uses a delay-request mechanism to synchronize with the master clock. The switch uses a source IP address for the packets it generates. You can create a loopback interface for this purpose. By default, the switch uses the lowest interface in the VLAN from which the sync messages are received. To assign a loopback interface, use the following command:

Note: If there are no interfaces on the switch that belong to the VLAN from which the sync messages are received, then the ordinary clock will not function. An error message will be generated. You can view this message using the RS 8272# show ptp command.

Transparent Clock Mode

When the G8272 is configured as a transparent clock, its time can be set manually or using any time protocol. You must configure PTPv2 for the transparent clock to function. The switch does not modify PTPv1 packets as they pass through the switch.

As a transparent clock, the G8272 supports syntonization (synchronization of clock frequency but not time) and synchronization with multiple domains.

Event packets received on all ports on the switch that have PTP enabled will be adjusted with the residence time. The switch sends all PTP packets to the multicast group address: 224.0.1.129. You can use Protocol Independent Multicast (PIM), Internet Group Management Protocol (IGMP), or any other multicast protocol to route the PTP packets.

RS 8272(config)# qos protocolpacketcontrol packetqueuemap <0-47> <protocol>

RS 8272(config)# qos protocolpacketcontrol ratelimitpacketqueue <0-47> <1-10000>

RS 8272(config)# ip ptp sourceinterface loopback <interface number>

© Copyright Lenovo 2015 Chapter 13: Precision Time Protocol 207

Tracing PTP Packets

PTP packets can be traced on the PTP ports. These packets can be identified by their destination IP address and UDP ports. The following table includes the IEEE standard specification:

Viewing PTP Information

The following table includes commands for viewing PTP information:

Table 20. IEEE Standard PTP Messages

Message IP Address/UDP Port

PTP-primary: All PTP messages except peer delay mechanism messages

224.0.1.129

PTP-pdelay: Peer delay mechanism messages

224.0.0.107

Event Messages: Sync, delay request, peer delay request, peer delay response

319

General Messages: Announce, follow-up, delay response, peer delay response follow-up, management

320

Table 21. PTP Information Commands

Command Description

RS 8272(config)# show ptp Displays global PTP information

RS 8272(config)# show interface port <port number>

Displays port information including port-specific PTP information

RS 8272(config)# show ptp counters

Displays ingress and egress PTP counters



Part 4: Advanced Switch-ing Features



Chapter 14. OpenFlow

This document describes how you can create an OpenFlow Switch instance on the RackSwitch G8272.

The following topics are discussed in this document:

“OpenFlow Overview” on page 212

“Configuring OpenFlow” on page 226


OpenFlow OverviewOpenFlow architecture consists of a control plane residing outside of the switch (typically on a server) and a data plane residing in the switch. The control plane is called OpenFlow controller. The data plane which resides in the switch consists of a set of flows which determine the forwarding of data packets.

The OpenFlow protocol is described in the OpenFlow Switch Specification 1.0.0 and OpenFlow Switch Specification 1.3.1.

An OpenFlow network consists of simple flow-based switches in the data path, with a remote controller to manage all switches in the OpenFlow network.

OpenFlow maintains a TCP channel for communication of flow management between the controller and the switch. All controller-switch communication takes place over the switch's management network.

Switch Profiles

The RackSwitch G8272 can be used for configuring OpenFlow and legacy switching features simultaneously. However, Layer 2 and Layer 3 switching features can be configured only on the ports that are not OpenFlow ports. Legacy switching ports and OpenFlow ports do not communicate with each other.

Alternately, the switch can be configured as an OpenFlow-only switch if you do not need to configure legacy switching features.

Based on your requirement, select the switch boot profile using the following commands:

OpenFlow-only: RS 8272(config)# boot profile openflow

The switch will operate only in OpenFlow environment. None of the legacy switching features will be supported.

OpenFlow and Legacy Switching:RS 8272(config)# boot profile default

Legacy switching features can be configured on the non-OpenFlow ports. By default, the switch boots in this profile.

Reload the switch to apply boot profile changes.

OpenFlow Versions

The RackSwitch G8272 can be configured to run either version 1.0 or version 1.3 of the OpenFlow standard. By default, the switch uses OpenFlow 1.0. To shift between versions, use the following commands:

RS 8272(config)# boot openflow v1

The switch will run OpenFlow 1.0 after reboot. This version does not support MPLS-based flows (See “Flow Tables” on page 213), groups, and static portchannels.

© Copyright Lenovo 2015 Chapter 14: OpenFlow 213

RS 8272(config)# boot openflow v13

The switch will run OpenFlow 1.3 after reboot. This version does not support emergency flow tables (See “Emergency Mode” on page 221).

OpenFlow 1.3 includes (but not limited to) the following key features:

Layer 3 MPLS

Static LAG

MAC address/IP address masking

Flexible Table Miss and Fail Secure

40Gb support

Static CLI for Flow Programming

OpenFlow 1.0 backward compatibility

OpenFlow Groups

OpenFlow Instance

The G8272 supports up to two instances of the OpenFlow protocol. Each instance appears as a switch to the controller. Instances on the same switch can be connected to different virtual networks. Each instance maintains a separate TCP channel for communication of flow management between controller and switch. Each instance supports up to four controllers. However, only one controller per instance is active at any point in time.

Global OpenFlow configuration applies to all instances. OpenFlow parameters for an instance can be configured using the command:

RS 8272(config)# openflow instance <instance ID>.

OpenFlow ports cannot be shared between instances.

Flow Tables

A set of a flow identification condition and an action towards a flow is called flow entry, and the database that stores the entries is called the flow table. A flow is defined as all the packets matching a flow entry in an OpenFlow flow table. Each flow entry includes:

Qualifiers - These are header fields that are matched with a packet.

Actions to be performed when a packet matches the qualifiers.

The controller decides which flows to admit and the path their packets will follow.

The switch classifies the flows as ACL-based, FDB-based, or MPLS-based. MPLS-based flows are supported only in version 1.3 of the OpenFlow standard. When the switch operates in OpenFlow boot profile (See “Switch Profiles” on page 212), a maximum of 2000 ACL-based flows, 4096 FDB multicast flows, 123904 FDB unicast flows, 1000 MPLS label pop flows, and 2000 MPLS label push flows are available. When the switch operates in default boot profile, a maximum of 1500 ACL-based flows, 4096 FDB multicast flows, 123904 FDB unicast flows, 1000 MPLS


label pop flows, and 2000 MPLS label push flows are available. The instances share these flows dynamically. To guarantee a specific number of flows to an instance, use the following commands:

OpenFlow boot profile:

Default boot profile:

Note: When the switch operates in default boot profile, the number of FDB and MPLS flows in an instance cannot be guaranteed.

In version 1.0 of the OpenFlow standard, the G8272 supports two flow tables per switch instance; basic flow table and emergency flow table. Actions are applied to packets that match the flow entry. This is done in the data path.

This system identifies packets as a flow by matching parameters in the following fields:

Ingress port

Source MAC (SMAC)

Destination MAC (DMAC)

Ether Type

VLAN TAG – Single VLAN tag – VLAN ID and Priority

IP address (source IP and destination IP)

IP Protocol

MPLS label

DSCP bits

Layer 4 Port (TCP, UDP)

ICMP code and type

If EtherType is ARP, then the specified ARP type (request/reply) or SIP in the ARP payload can be used a to match a packet.

Once a packet arrives, the switch searches the flow table. When a flow entry is hit in the search, the packet is processed according to the action specified in the flow entry.

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# maxflowacl <0-2000> RS 8272(configopenflowinstance)# maxflowmcastfdb <0-4096>RS 8272(configopenflowinstance)# maxflowucastfdb <0-123904>RS 8272(configopenflowinstance)# maxflowmplspop <0-1000>RS 8272(configopenflowinstance)# maxflowmplspush <0-2000>

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# maxflowacl <0-1500>


Static FlowsYou can configure static flow entries for OpenFlow instances. The switch forwards traffic based on these entries even if it is not connected to a controller. Up to 1000 static ACL entries across all instances can be configured. An OpenFlow controller cannot modify or delete these entries. Static flow entries can replace entries installed by a controller. Static flow entries are not lost when the switch is reloaded.

Static flow entries are based on the following qualifiers, actions, and options:

Table 22. Static Flow Entry Qualifiers in OpenFlow 1.0

Qualifier Description

ingress-port port of the instance

src-mac source MAC address

dst-mac destination MAC address

vlan-id VLAN identifier (tagged, untagged, or 0-4094)

vlan-priority 802.1p (0-7)

src-ip source IP address

dst-ip destination IP address

src-port Layer 4 source port (0-65535)

dst-port Layer 4 destination port (0-65535)

ether-type "arp"/"0806" or "ip"/"0800" or (hex-value <= 65535)

protocol "tcp" or "udp" or 0-255

tos IP TOS (0-255)

type "request" or "reply" (can be set only if ether type is ARP)

all all qualifiers or any qualifier

Table 23. Static Flow Entry Qualifiers in OpenFlow 1.3


in-port switch input port

in-portchannel switch input portchannel (only static trunk supported)

in-phy-port switch physical input port, valid only when in-port is pecified

eth-src source MAC address and mask

eth-dst destination MAC address and mask

vlan-vid VLAN identifier (0-4095 + 65535 (untagged))


vlan-pcp 802.1p(0-7)

ipv4-src source IPv4 address and mask

ipv4-dst destination IPv4 address and mask

tcp-src TCP source port (0-65535)

tcp-dst TCP destination port (0-65535)

udp-src UDP source port (0-65535)

udp-dst UDP destination port (0-65535)

icmpv4-type ICMPv4 type

icmpv4-code ICMPv4 code

eth-type "arp"/"0806" or "ip"/"0800" or (hex-value < =65535)

ip-proto "tcp" or "udp" or 0-255

ip-dscp IP DSCP (6 bits in ToS field)

arp-op "request" or "reply" (can be set only if eth-type is ARP)

mpls-label MPLS label

all all qualifiers or any qualifier

Table 24. Static Flow Entry Actions in OpenFlow 1.0

Action Description

out-put "all","in-port","flood","controller" or a valid port

set-src-mac change source MAC address

set-dst-mac change destination MAC address

strip-vlan-id strip VLAN

set-vlan-id set VLAN ID

set-vlan-priority set 802.1p priority (0-7)

set-nw-tos set IP TOS (0-255)

drop drop the packet

Table 23. Static Flow Entry Qualifiers in OpenFlow 1.3 (continued)



Port Membership

When static flow entries are configured, port membership changes are handled as follows:

If a port is the “in-port” or “out-port” in a static flow entry, the port membership cannot be changed.

When a port membership changes, the ingress bitmap of static entries with in-port ANY will be updated.

Table 25. Static Flow Entry Actions in OpenFlow 1.3

Action Description

output physical portsreserved ports: all, controller, in_port

output-portchannel Logical ports (only support static LAG)

set-eth-src change source MAC address

set-eth-dst change destination MAC address

push-vlan push a new VLAN tag, 0x8100

pop-vlan pop the VLAN tag

push-mpls push a new MPLS tag, 0x8847

pop-mpls pop MPLS tag, 0x0800 or 0x800 (IP Ethertype)

set-vlan-vid set VLAN ID, <0-4094>

set-vlan-pcp set 802.1p priority (0-7)

set-ip-dscp Set IP DSCP (0-63), 6 highest bits in TOS

set-mpls-ttl set MPLS TTL

set-mpls-label Set MPLS label, <1-0xFFFFF>

copy-ttl-out copy TTL outward - from next-to-outermost to outermost

copy-ttl-in copy TTL inward - from outermost to next-to-outermost

drop drop the packet

Note: Actions for static flows must be specified in the following order: set-mpls-ttl, copy-ttl-in, pop-mpls, pop-vlan, push-mpls, push-vlan, copy-ttl-out, set-field, output. The actions output, output-portchannel, set-eth-src, set-eth-dst, set-vlan-vid, set-vlan-pcp, set-ip-dscp, and set-mpls-label may be used in any order.

Table 26. Static Flow Entry Options

Option Description

max-len maximum length of flow to send to controller


When a port membership changes, the egress bitmap of static entries with redirect output FlOOD/ANY will be updated.

Static Flow Examples

Following are example static flow entries for Openflow 1.0:

Basic ACL flow:

Flow with multiple qualifiers and actions:

Flow with action: output to controller:

Static ACL flow entries can be deleted using the command:

Following are example static flow entries for OpenFlow 1.3:

Basic ACL flow:

Flow with multiple qualifiers and actions:

Static ACL flow entries for OpenFlow 1.3 can also be deleted using the command:

RS 8272(configopenflowinstance)# statictable add index 1 match ingressport=1 actions output=10 priority 12345

RS 8272(configopenflowinstance)# statictable add index 2 match vlanid=1,dstmac=00:00:00:00:00:01 actions setvlanpriority=3,output=20 priority 1000

RS 8272(configopenflowinstance)# statictable add index 3 match all actions output=controller options maxlen=65534 priority 1000

RS 8272(configopenflowinstance)# statictable remove index <index number>

RS 8272(configopenflowinstance)# statictable add index 1 match inport=41 actions output=50 priority 12345

RS 8272(configopenflowinstance)# statictable add index 2 match vlanid=1,ethdst=00:00:00:00:00:01 actions setvlanpcp=3,output=50 priority 1000

RS 8272(configopenflowinstance)# statictable remove index <index number>


In OpenFlow version 1.0:

RS 8272(configopenflowinstance)# show openflow table

Openflow instance 1 is currently disabled

Openflow Instance Id: 2

BASIC FLOW TABLE

CONTROLLER ADDED FLOWS

Flow:1 Filter Based, priority: 0, hardtimeout: 0, idletimeout: 0 cookie: 0x0 QUALIFIERS: ACTION: drop STATS: packets=0, bytes=0

Flow:2 Filter Based, priority:65535, hardtimeout: 0, idletimeout: 0 cookie: 0x0 QUALIFIERS: ethertype:0x88cc protocol: 0, tos: 0 srcip:0.0.0.0/32, dstip:0.0.0.0/32 srcport: 0, dstport: 0 ACTION: output:CONTROLLER [Max Len: 65535 / bytes (C/S)] STATS: packets=0, bytes=0

Flow:3 Filter Based, priority: 2, hardtimeout: 0, idletimeout: 0 cookie: 0x0 QUALIFIERS: ACTION: output:CONTROLLER [Max Len: 65535 / bytes (C/S)] STATS: packets=0, bytes=0


In OpenFlow version 1.3:

Table-MissIn OpenFlow 1.3, if a match is not found for an arriving packet, the packet is either dropped or sent to the controller. If sent to the controller, the controller decides which action(s) to perform on all packets from the same flow. The decision is then sent to the switch and cached as an entry in the switch instance’s flow table. If the controller decides to add the flow, it sends a flow add message to the switch. The switch then adds the flow in its flow table. The next arriving packet that belongs to the same flow is then forwarded at line-rate through the switch without consulting the controller.

By default, packets that don’t match any of the existing flow entries are dropped. To set up an OpenFlow instance to send non-matching packets to the controller instead of dropping them, use the following commands:

RS 8272(configopenflowinstance)# show openflow table

Openflow instance 1 is currently disabled


CONTROLLER added FLOWs

Flow 1, Filter Based, priority:1000, hardtimeout:0, idletimeout:0cookie:0x0QUALIFIERS: inport:PCH1ethdst:01:00:08:00:00:03vlanvid:1Instruction: apply_actionACTION: output:18, PCH1, PCH66STATS: packets=0, bytes=0

Flow 2, Filter Based, priority:2, hardtimeout:0, idletimeout:0 cookie:0x0 QUALIFIERS: Instruction: write_action ACTION: output:CONTROLLER [Max Len: 65535 / bytes (C/S)] STATS: packets=0, bytes=0

Flow 3, Filter Based, priority:65535, hardtimeout:0, idletimeout:0 cookie:0x0 QUALIFIERS: ethtype:0x88cc Instruction: write_action ACTION: output:CONTROLLER [Max Len: 65535 / bytes (C/S)] STATS: packets=0, bytes=0

Flow 4, Filter Based, priority:0, hardtimeout:0, idletimeout:0 cookie:0x0 QUALIFIERS: Instruction: empty ACTION: drop STATS: packets=0, bytes=0

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# tablemiss controller


Fail Secure Mode

In OpenFlow 1.3, if contact with all controllers is lost, the switch automatically enters a fail secure mode. In this mode, the switch continues to operate based on the existing flow entries until they expire (according to the configured flow timeout value), while packets and messages destined to the controllers are dropped. When a connection to a controller is reestablished, the controller has the option to either delete or keep any remaining flow entries.

Emergency ModeNote: Emergency Mode is supported only in version 1.0 of the OpenFlow standard.

By default, Emergency mode is disabled. In this state, if the connection to the controller fails, the switch enters Fail Secure mode.

To enable Emergency mode, use the following command:

In Emergency mode enabled state, if the connection to the controller fails, the switch tries to establish connection with any of the other configured controllers. If it is unable to connect with any controller, it enters Emergency mode. It replaces the flow entries with the entries from the emergency flow table.

The switch stays in the Emergency mode for the time configured as the Emergency timeout interval (default value is 30 seconds), after which the switch tries to establish connection with any configured controller.

If connection with a controller is established, the switch exits Emergency mode. Entries in the Emergency flow table are retained. If desired, the controller may delete all the emergency flow entries.

If connection with a controller is not established, the switch stays in Emergency mode and continues to forward packets based on the Emergency flows. It retries to establish a connection with a controller every time the Emergency timeout interval expires.

Emergency mode can be activated or deactivated per instance. To activate Emergency mode on an instance, use the following command:

To deactivate Emergency mode on an instance, use the following command:

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# emergency

RS 8272# openflow instance <instance ID> enteremergency

RS 8272# no openflow instance <instance ID> enteremergency


Table 27 displays an example of emergency flows created:

OpenFlow Ports

When OpenFlow is enabled, all OpenFlow instance member ports become OpenFlow ports. OpenFlow ports have the following characteristics:

Learning is turned off.

Flood blocking is turned on.

Spanning Tree Protocol (STP) is disabled.

Table 27. Emergency Flows

RS 8272(config)# show openflow table


BASIC FLOW TABLE

Flow:1 FDB Based, priority: 1000, hardtimeout: 0 QUALIFIERS: dstmac:010203050600, vlanid: 100 ACTION: outport:21

Flow:2 Filter Based, priority:32768, hardtimeout: 0, idletimeout: 0 QUALIFIERS: vlanid: 100 dstmac:010203667600 ACTION: output:22 STATS: packets=0, bytes=0

EMERGENCY FLOW TABLE


Flow:2 Filter Based, priority:32768, hardtimeout: 0, idletimeout: 0 QUALIFIERS: vlanid: 100 dstmac:010203660600 ACTION: output:22


BASIC FLOW TABLE


EMERGENCY FLOW TABLE



The switch communicates with OpenFlow controllers through controller management ports or through dedicated out-of-band management ports on the switch. All OpenFlow ports, except controller management ports, must be members of VLAN 1. Controller management ports can be members of any VLAN except VLAN 1.Note: When the switch operates in the default boot profile, we recommend that you use a non-OpenFlow port to connect the switch with the controller. Use the following command to view port information:

For each OpenFlow instance, when you configure the controller IP address and port, the switch establishes a TCP connection with the controller for flow control and management. See Step 3 on page 226. The switch supports up to four controllers per instance. The default controller port is 6633 and is reachable via out-of-band management port (port MGT) or in-band port. The controller management ports must not be members of an OpenFlow instance. You can use a controller to manage and control multiple instances.

Use the following command to configure a data port as a controller management port:

Note: In default boot profile, when you disable OpenFlow, the OpenFlow ports become legacy switch ports and are added to the default VLAN 1.

OpenFlow Edge Ports

You can configure a port as an OpenFlow edge port. Edge ports are connected to either non-OpenFlow switches or servers. OpenFlow edge ports have the following characteristics:

Flood blocking is turned on.

MAC learning is turned on.

Use the following commands to configure a port as an edge port:

Note: Edge ports are not OpenFlow standard ports. You must configure edge ports only if the controller supports it.

Link Aggregation

In OpenFlow 1.3, logical ports can be used to aggregate links. You can add a logical port to an OpenFlow instance using the following command:

RS 8272(config)# show interface information

RS 8272(config)# openflow mgmtport <port number>

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# edgeport <port number>

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# member portchannel <Trunk ID>


Once added, the logical port inherits the OpenFlow data properties such as MAC learning turned off, flood blocking turned on, and STP disabled. The switch derives the logical port ID based on the configured trunk ID.

The trunk link stays active as long as at least one member port is up. The trunk link speed is an aggregation of the speed of individual member ports. If a port goes down, the trunk link speed lowers.

A portchannel can be added to the OpenFlow instance using the command:

To add a portchannel to the edge ports list, use the following command:

Data Path IDThe data path ID—automatically computed—is a combination of two bytes of the instance ID and six bytes of the switch MAC address. Alternately, the data path ID can be manually configured using the following command. Each instance on the switch must have a unique data path ID:

Note: If the data path ID is changed, the switch instance closes the active connection and reconnects with the modified data path ID.

sFlow Compatibility

OpenFlow ports that are set for sFlow sampling will send incoming sample packets to both the sFlow server or analyzer and the OpenFlow controller as “packet-in”. All sFlow servers must be configured as reachable over a management port or a non-OpenFlow data port.

Unicast FDB flows support both ingress and egress sampling. ACL-based flows, MPLS-based flows, multicast FDB-based flows, packet-in, send-to-controller, and mirror-to-controller flows only support ingress sampling.

OpenFlow Groups

In OpenFlow 1.3, the RackSwitch G8272 supports OpenFlow groups based on the OpenFlow 1.3.1 specification. The following OpenFlow group features are supported:

Group types: ALL and INDIRECT

Up to 256 groups per instance

Group operations: ADD, MODIFY and DELETE

Support for group multipart messages: group counter statistics, group description and group features

RS 8272(configopenflowinstance)# member portchannel <Trunk ID>

RS 8272(configopenflowinstance)# edgeport portchannel <Trunk ID>

RS 8272(config)# openflow instance <instance ID>RS 8272(configopenflowinstance)# dpid <Data path ID>

(Hex string starting with 0x)


Flows: ACL, FDB and MPLS

Port types: physical port, logical port (static portchannel)


Configuring OpenFlowThe RackSwitch G8272 is capable of operating both in normal switching environment (default boot profile) and in OpenFlow switch environment (OpenFlow boot profile). Note: If you disable OpenFlow, you must reboot the switch in order to resume normal switch environment operations.

Perform the following steps to configure an OpenFlow switch instance.

1. Enable OpenFlow:

2. Create an OpenFlow switch instance and add data ports:

In version 1.3 of the OpenFlow standard, you can also add static portchannels to the instance:

3. Configure a controller for the OpenFlow switch instance:

4. Enable the OpenFlow switch instance:

The switch is ready to perform switching functions in an OpenFlow environment.

5. Verify OpenFlow configuration:

Configuration Example 1 - OpenFlow Boot Profile

The following example includes steps to configure an OpenFlow switch instance when the switch operates in OpenFlow boot profile.

Configure OpenFlow instance 1, which connects with one controller via in-band management port and another controller via out-of-band management port; and OpenFlow instance 2, which connects with two controllers via in-band management ports.

RS 8272(config)# openflow enable

RS 8272(config)# openflow instance <1-2>RS 8272(configopenflowinstance)# member <port number or range>

RS 8272(configopenflowinstance)# member portchannel <1-72>

RS 8272(configopenflowinstance)# controller <1-4> address <IP address> [mgtport|dataport]RS 8272(configopenflowinstance)# controller <1-4> port <1-65535>

RS 8272(configopenflowinstance)# enable

RS 8272(config)# show openflow <instance ID> information


1. Configure IP interface 128 for out-of-band connection:

2. Configure IP interface 1 for in-band connection:


4. Enable OpenFlow globally:

5. Configure OpenFlow in-band management ports:

Note: Step 5 is not required when the switch operates in default boot profile.

6. Create OpenFlow switch instance 1 and add data ports:

RS 8272(config)# interface ip 128RS 8272(configipif)# ip address 172.20.100.1 255.255.0.0 enableRS 8272(configipif)# exit


RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 172.21.100.1 255.255.0.0 enableRS 8272(configipif)# vlan 3000RS 8272(configipif)# exit




RS 8272(config)# openflow mgmtport 5,6 (Switch can connect with the controllers via dataport 5 and 6, which are connected to the controller networks)

RS 8272(config)# openflow instance 1 (Create OpenFlow instance 1)RS 8272(configopenflowinstance)# member 17,18,1925

(Add data ports 17,18, and data port range 19 through 25 as members of OpenFlow instance 1)


7. Configure controller 1 IP address using out-of-band management port:

8. Configure controller 2 IP address using in-band management port:

9. Enable OpenFlow instance 1:





14. View OpenFlow Configuration:

RS 8272(configopenflowinstance)# controller 1 address 172.20.100.73 mgtport

(Switch connects with controller 1 via the out-of-band management port; default controller port is used in this example)

RS 8272(configopenflowinstance)# controller 2 address 172.21.100.73 dataport(Switch connects with controller 2 via the in-band management port configured in Step 5 on page 227; default controller port is used in this example)

RS 8272(configopenflowinstance)# enableRS 8272(configopenflowinstance)# exit

RS 8272(config)# openflow instance 2 (Create OpenFlow instance 2)RS 8272(configopenflowinstance)# member 26,27,2834

(Add data ports 26,27, and data port range 28 through 34 as members of OpenFlow instance 2)

RS 8272(configopenflowinstance)# controller 1 address 172.21.100.73 dataport(Switch connects with controller 1 via the in-band management port configured in Step 5; default controller port is used in this example)

RS 8272(configopenflowinstance)# controller 2 address 172.22.100.73 dataportSwitch connects with controller 2 via in-band management port configured in Step 5 on page 227; default controller port is used in this example)

RS 8272(configopenflowinstance)# enable

RS 8272(config)# show runningconfig


Configuration Example 2 - Default Boot Profile

The following example includes steps to configure an OpenFlow switch instance when the switch operates in Default boot profile.

1. Configure IP interface 128 for out-of-band connection:



4. Enable OpenFlow globally:


6. Configure controller 1 IP addresses using out-of-band management port:

RS 8272(config)# interface ip 128RS 8272(configipif)# ip address 172.20.100.1 255.255.0.0 enableRS 8272(configipif)# exit






RS 8272(config)# openflow instance 1 (Create OpenFlow instance 1)RS 8272(configopenflowinstance)# member 17,18,1925(Add data ports 17,18, and

data port range 19 through 25 as members of OpenFlow instance 1)

RS 8272(configopenflowinstance)# controller 1 address 172.20.100.73 mgtport

(Switch connects with controller 1 via the out-of-band management port; default controller port is used in this example)








13. View OpenFlow Configuration:

RS 8272(configopenflowinstance)# controller 2 address 172.21.100.73 dataport(Switch connects with controller 2 via the in-band management port; default controller port is used in this example)


RS 8272(config)# openflow instance 2 (Create OpenFlow instance 2)RS 8272(configopenflowinstance)# member 26,27,2834(

Add data ports 26,27, and data port range 28 through 34 as members of OpenFlow instance 2)

RS 8272(configopenflowinstance)# controller 1 address 172.21.100.73 dataport(Switch connects with controller 1 via the in-band management port; default controller port is used in this example)

RS 8272(configopenflowinstance)# controller 2 address 172.22.100.73 dataportSwitch connects with controller 2 via in-band management port; default controller port is used in this example)


RS 8272(config)# show runningconfig


Feature Limitations

When the switch is booted in the OpenFlow profile, it operates only in OpenFlow switch environment. None of the normal switching environment features are supported.

If the switch is booted in default profile, normal switching environment features can be configured on the non-OpenFlow ports. However, the following features are not supported:

ACLs

ECN

FCoE

IPMC

IPv6

MACL

vNIC

VMready



Chapter 15. Deployment Profiles

The Lenovo N/OS software for the RackSwitch G8272 can be configured to operate in different modes for different deployment scenarios. Each deployment profile sets different capacity levels for basic switch resources, such as the number of IP Multicast (IPMC) entries and ACL entries, to optimize the switch for different types of networks.

This chapter covers the following topics

“Available Profiles” on page 234

“Selecting Profiles” on page 235

“Automatic Configuration Changes” on page 236


Available ProfilesThe following deployment profiles are currently available on the G8272:

Default Profile: This profile is recommended for general network usage. Switch resources are allocated to support a wide range of features such as IPv6, ACLs, and FCoE/CEE.

ACL Profile: This profile enables you to configure the maximum number of ACLs. The IPv6, FCoE/CEE, and VMready features will not be supported. This profile also does not support the forwarding of IPMC packets with IP options.

The properties of each mode are compared in the following table.

Note: Throughout this guide, where feature capacities are listed, values reflect those of the Default profile only, unless otherwise noted.

Table 28. Deployment Mode Comparison

Switch Feature

Capacity, by Mode

Default Openflow ACL

ACLs 256 256 896

IPv6 Supported Not Supported Not Supported

VMready Supported Not Supported Not Supported

VMap Supported Not Supported Not Supported

FCoE/CEE Supported Not Supported Not Supported

© Copyright Lenovo 2015 Chapter 15: Deployment Profiles 235

Selecting ProfilesTo change the deployment profile, you must first select the new profile and then reboot the switch.Note: Before changing profiles, it is recommended that you save the active switch configuration to a backup file so that it may be restored later if desired.

When you select a profile, you will see a warning message. For example, if you select the ACL profile, you will see the following message:

To view the current deployment profile, use the following command:

Use the following commands to change the deployment profile:

When using a specialized profile, menus and commands are unavailable for features that are not supported under the profile. Such menus and commands will be available again only when a supporting profile is used.Note: Only use deployment profiles other than those listed in this section when under the direction of your support personnel.

Warning: Setting boot profile to "ACL" will cause FIPS, IPv6 and VM ACL configuration to be lost in next boot and error messages will be displayed when above configurations are restored.

Next boot will use "ACL" profile.

RS 8272# show boot

RS 8272(config)# boot profile default|openflow|acl||ipmcopt acls128|acls256|acls384|aclsnone

(Select deployment profile)RS 8272(config)# exit (To privileged EXEC mode)RS 8272# reload (Reboot the switch)


Automatic Configuration ChangesWhen a new profile is loaded, configuration settings for any unsupported features will be ignored. However, these settings are retained in memory until you change or save the current configuration under the new profile. Until then, you can return to the old profile with all prior configuration settings intact.

Once you change or save the configuration under a new profile, any configuration settings related to unsupported features will be reset to their default values. At that point, you will have to reconfigure these settings or use a backup configuration if you reapply the old profile.

For example, when using the ACL profile, because IPv6 is not supported in that mode, IPv6 settings will be excluded when the configuration is saved. Then, if returning to the Default profile, it will be necessary to reconfigure the IPv6 settings, or to use the backup configuration.


Chapter 16. Virtualization

Virtualization allows resources to be allocated in a fluid manner based on the logical needs of the data center, rather than on the strict, physical nature of components. The following virtualization features are included in Lenovo Networking OS 8.2 on the RackSwitch G8272 (G8272):

Virtual Local Area Networks (VLANs)VLANs are commonly used to split groups of networks into manageable broadcast domains, create logical segmentation of workgroups, and to enforce security policies among logical network segments.For details on this feature, see “VLANs” on page 117.

Port trunkingA port trunk pools multiple physical switch ports into a single, high-bandwidth logical link to other devices. In addition to aggregating capacity, trunks provides link redundancy.For details on this feature, see “Ports and Trunking” on page 129.

Virtual Link Aggregation (VLAGs)With VLAGs, two switches can act as a single logical device for the purpose of establishing port trunking. Active trunk links from one device can lead to both VLAG peer switches, providing enhanced redundancy, including active-active VRRP configuration.For details on this feature, see “Virtual Link Aggregation Groups” on page 165

VMreadyThe switch’s VMready software makes it virtualization aware. Servers that run hypervisor software with multiple instances of one or more operating systems can present each as an independent virtual machine (VM). With VMready, the switch automatically discovers virtual machines (VMs) connected to switch.For details on this feature, see “VMready” on page 239.

Unified Fabric Port (UFP)An architecture that logically subdivides a high-speed physical link connecting to a server NIC. UFP provides a switch fabric component to control the NIC.For details on this feature, see “Unified Fabric Port” on page 307.

N/OS virtualization features provide a highly-flexible framework for allocating and managing switch resources.



Chapter 17. VMready

Virtualization is used to allocate server resources based on logical needs, rather than on strict physical structure. With appropriate hardware and software support, servers can be virtualized to host multiple instances of operating systems, known as virtual machines (VMs). Each VM has its own presence on the network and runs its own service applications.

Software known as a hypervisor manages the various virtual entities (VEs) that reside on the host server: VMs, virtual switches, and so on. Depending on the virtualization solution, a virtualization management server may be used to configure and manage multiple hypervisors across the network. With some solutions, VMs can even migrate between host hypervisors, moving to different physical hosts while maintaining their virtual identity and services.

The Lenovo Networking OS 8.2 VMready feature supports up to 4096 VEs in a virtualized data center environment. The switch automatically discovers the VEs attached to switch ports, and distinguishes between regular VMs, Service Console Interfaces, and Kernel/Management Interfaces in a VMware® environment.

VEs may be placed into VM groups on the switch to define communication boundaries: VEs in the same VM group may communicate with each other, while VEs in different groups may not. VM groups also allow for configuring group-level settings such as virtualization policies and ACLs.

The administrator can also pre-provision VEs by adding their MAC addresses (or their IPv4 address or VM name in a VMware environment) to a VM group. When a VE with a pre-provisioned MAC address becomes connected to the switch, the switch will automatically apply the appropriate group membership configuration.

The G8272 with VMready also detects the migration of VEs across different hypervisors. As VEs move, the G8272 NMotion™ feature automatically moves the appropriate network configuration as well. NMotion gives the switch the ability to maintain assigned group membership and associated policies, even when a VE moves to a different port on the switch.

VMready also works with VMware Virtual Center (vCenter) management software. Connecting with a vCenter allows the G8272 to collect information about more distant VEs, synchronize switch and VE configuration, and extend migration properties.


VE CapacityWhen VMready is enabled, the switch will automatically discover VEs that reside in hypervisors directly connected on the switch ports. Networking OS 8.2 supports up to 4096 VEs. Once this limit is reached, the switch will reject additional VEs.Note: In rare situations, the switch may reject new VEs prior to reaching the supported limit. This can occur when the internal hash corresponding to the new VE is already in use. If this occurs, change the MAC address of the VE and retry the operation. The MAC address can usually be changed from the virtualization management server console (such as the VMware Virtual Center).

Defining Server PortsBefore you configure VMready features, you must first define whether ports are connected to servers or are used as uplink ports. Use the following ISCLI configuration command to define a port as a server port:

Ports that are not defined as server ports are automatically considered uplink ports.

VM Group TypesVEs, as well as switch server ports, switch uplink ports, static trunks, and LACP trunks, can be placed into VM groups on the switch to define virtual communication boundaries. Elements in a given VM group are permitted to communicate with each other, while those in different groups are not. The elements within a VM group automatically share certain group-level settings.

N/OS 8.2 supports up to 4093 VM groups. There are two different types: Local VM groups are maintained locally on the switch. Their configuration is not

synchronized with hypervisors. Distributed VM groups are automatically synchronized with a virtualization

management server (see “Assigning a vCenter” on page 250).

Each VM group type is covered in detail in the following sections.

RS 8272(config)# system serverports port <port alias or number>

© Copyright Lenovo 2015 Chapter 17: VMready 241

Local VM GroupsThe configuration for local VM groups is maintained on the switch (locally) and is not directly synchronized with hypervisors. Local VM groups may include only local elements: local switch ports and trunks, and only those VEs connected to one of the switch ports or pre-provisioned on the switch.

Local VM groups support limited VE migration: as VMs and other VEs move to different hypervisors connected to different ports on the switch, the configuration of their group identity and features moves with them. However, VE migration to and from more distant hypervisors (those not connected to the G8272, may require manual configuration when using local VM groups.

Configuring a Local VM Group

Use the following ISCLI configuration commands to assign group properties and membership:

RS 8272(config)# virt vmgroup <VM group number> ?

cpu (Enable sending unregistered IPMC to CPU)flood (Enable flooding unregistered IPMC)key <LACP trunk key> (Add LACP trunk to group)optflood (Enable optimized flooding)port <port alias or number> (Add port member to group)portchannel <trunk group number> (Add static trunk to group)profile <profile name> (Not used for local groups)stg <Spanning Tree group> (Add STG to group)tag (Set VLAN tagging on ports)validate <advanced|basic> (Validate mode for the group)vlan <VLAN number> (Specify the group VLAN)vm <MAC>|<index>|<UUID>|<IPv4 address>|<name>(Add VM member to group)vmap <VMAP number> [intports|extports](Specify VMAP number)

vport (Add a virtual port to the group)


The following rules apply to the local VM group configuration commands:

cpu: Enable sending unregistered IPMC to CPU.

flood: Enable flooding unregistered IPMC. key: Add LACP trunks to the group.

optflood: Enable optimized flooding to allow sending unregistered IPMC to the Mrouter ports without having any packet loss during the learning period; This option is disabled by default; When optflood is enabled, the flood and cpu settings are ignored.

port: Add switch server ports or switch uplink ports to the group. portchannel: Add static port trunks to the group. profile: The profile options are not applicable to local VM groups. Only

distributed VM groups may use VM profiles (see “VM Profiles” on page 243). stg: The group may be assigned to a Spanning-Tree group for broadcast loop

control (see “Spanning Tree Protocols” on page 143). tag: Enable VLAN tagging for the VM group. If the VM group contains ports

which also exist in other VM groups, enable tagging in both VM groups.

validate: Set validation mode for the group. vlan: Each VM group must have a unique VLAN number. This is required for

local VM groups. If one is not explicitly configured, the switch will automatically assign the next unconfigured VLAN when a VE or port is added to the VM group.

vmap: Each VM group may optionally be assigned a VLAN-based ACL (see “VLAN Maps” on page 254).

vm: Add VMs.VMs and other VEs are primarily specified by MAC address. They can also be specified by UUID, IP address, or by the index number as shown in various VMready information output (see “VMready Information Displays” on page 257).

vport: Add a virtual port to the group.If VMware Tools software is installed in the guest operating system (see VMware documentation for information on installing recommended tools), VEs may also be specified by IPv4 address or VE name. However, if there is more than one possible VE for the input, the switch will display a list of candidates and prompt for a specific MAC address.Only VEs currently connected to the switch port (local) or pending connection (pre-provisioned) are permitted in local VM groups.

Use the no variant of the commands to remove or disable VM group configuration settings:

RS 8272(config)# no virt vmgroup <VM group number> [?]


Distributed VM GroupsDistributed VM groups allow configuration profiles to be synchronized between the G8272 and associated hypervisors and VEs. This allows VE configuration to be centralized, and provides for more reliable VE migration across hypervisors.

Using distributed VM groups requires a virtualization management server. The management server acts as a central point of access to configure and maintain multiple hypervisors and their VEs (VMs, virtual switches, and so on).

The G8272 must connect to a virtualization management server before distributed VM groups can be used. The switch uses this connection to collect configuration information about associated VEs, and can also automatically push configuration profiles to the virtualization management server, which in turn configures the hypervisors and VEs. See “Virtualization Management Servers” on page 250 for more information.

VM Profiles

VM profiles are required for configuring distributed VM groups. They are not used with local VM groups. A VM profile defines the VLAN and virtual switch bandwidth shaping characteristics for the distributed VM group. The switch distributes these settings to the virtualization management server, which in turn distributes them to the appropriate hypervisors for VE members associated with the group.

Creating VM profiles is a two part process. First, the VM profile is created as shown in the following command on the switch:

Next, the profile must be edited and configured using the following configuration commands:

For virtual switch bandwidth shaping parameters, average and peak bandwidth are specified in kilobits per second (a value of 1000 represents 1 Mbps). Burst size is specified in kilobytes (a value of 1000 represents 1 MB). Eshaping (egress shaping) is used for distributed virtual switch.Note: The bandwidth shaping parameters in the VM profile are used by the hypervisor virtual switch software. To set bandwidth policies for individual VEs, see “VM Policy Bandwidth Control” on page 255.

Once configured, the VM profile may be assigned to a distributed VM group as shown in the following section.

Initializing a Distributed VM Group

Note: A VM profile is required before a distributed VM group may be configured. See “VM Profiles” on page 243 for details.

RS 8272(config)# virt vmprofile <profile name>

RS 8272(config)# virt vmprofile edit <profile name> ?eshaping <average bandwidth> <burst size> <peak>shaping <average bandwidth> <burst size> <peak>vlan <VLAN number>


Once a VM profile is available, a distributed VM group may be initialized using the following configuration command:

Only one VM profile can be assigned to a given distributed VM group. To change the VM profile, the old one must first be removed using the following ISCLI configuration command:

Note: The VM profile can be added only to an empty VM group (one that has no VLAN, VMs, or port members). Any VM group number currently configured for a local VM group (see “Local VM Groups” on page 241) cannot be converted and must be deleted before it can be used for a distributed VM group.

Assigning Members

VMs, ports, and trunks may be added to the distributed VM group only after the VM profile is assigned. Group members are added, pre-provisioned, or removed from distributed VM groups in the same manner as with local VM groups (“Local VM Groups” on page 241), with the following exceptions:

VMs: VMs and other VEs are not required to be local. Any VE known by the virtualization management server can be part of a distributed VM group.

The VM group vlan option (see page 242) cannot be used with distributed VM groups. For distributed VM groups, the VLAN is assigned in the VM profile.

Synchronizing the Configuration

When the configuration for a distributed VM group is modified, the switch updates the assigned virtualization management server. The management server then distributes changes to the appropriate hypervisors.

For VM membership changes, hypervisors modify their internal virtual switch port groups, adding or removing server port memberships to enforce the boundaries defined by the distributed VM groups. Virtual switch port groups created in this fashion can be identified in the virtual management server by the name of the VM profile, formatted as follows: Lenovo_<VM profile name>(or)Lenovo_<VM profile name> <index number> (for vDS)

Adding a server host interface to a distributed VM group does not create a new port group on the virtual switch or move the host. Instead, because the host interface already has its own virtual switch port group on the hypervisor, the VM profile settings are applied to its existing port group.Note: When applying the distributed VM group configuration, the virtualization management server and associated hypervisors must take appropriate actions. If a hypervisor is unable to make requested changes, an error message will be displayed on the switch. Be sure to evaluate all error message and take the appropriate actions for the expected changes to apply.

RS 8272(config)# virt vmgroup <VM group number> profile <VM profile name>

RS 8272(config)# no virt vmgroup <VM group number> profile


Removing Member VEs

Removing a VE from a distributed VM group on the switch will have the following effects on the hypervisor:

The VE will be moved to the Lenovo_Default port group in VLAN 0 (zero).

Traffic shaping will be disabled for the VE.

All other properties will be reset to default values inherited from the virtual switch.


VMcheckThe G8272 primarily identifies virtual machines by their MAC addresses. An untrusted server or a VM could identify itself by a trusted MAC address leading to MAC spoofing attacks. Sometimes, MAC addresses get transferred to another VM, or they get duplicated.

The VMcheck solution addresses these security concerns by validating the MAC addresses assigned to VMs. The switch periodically sends hello messages on server ports. These messages include the switch identifier and port number. The hypervisor listens to these messages on physical NICs and stores the information, which can be retrieved using the VMware Infrastructure Application Programming Interface (VI API). This information is used to validate VM MAC addresses. Two modes of validation are available: Basic and Advanced.

Use the following command to select the validation mode or to disable validation:

Basic Validation

This mode provides port-based validation by identifying the port used by a hypervisor. It is suitable for environments in which MAC reassignment or duplication cannot occur.

The switch, using the hello message information, identifies a hypervisor port. If the hypervisor port is found in the hello message information, it is deemed to be a trusted port. Basic validation should be enabled when:

A VM is added to a VM group, and the MAC address of the VM interface is in the Layer 2 table of the switch.

A VM interface that belongs to a VM group experiences a “source miss” i.e. is not able to learn new MAC address.

A trusted port goes down. Port validation must be performed to ensure that the port does not get connected to an untrusted source when it comes back up.

Use the following command to set the action to be performed if the switch is unable to validate the VM MAC address:

Advanced Validation

This mode provides VM-based validation by mapping a switch port to a VM MAC address. It is suitable for environments in which spoofing, MAC reassignment, or MAC duplication is possible.

RS 8272(config)# [no] virt vmgroup <VM group number> validate basic|advanced

RS 8272(config)# virt vmcheck action basic log|link

log generates a loglink disables the port


When the switch receives frames from a VM, it first validates the VM interface based on the VM MAC address, VM Universally Unique Identifier (UUID), Switch port, and Switch ID available in the hello message information. Only if all the four parameters are matched, the VM MAC address is considered valid.

In advanced validation mode, if the VM MAC address validation fails, an ACL can be automatically created to drop the traffic received from the VM MAC address on the switch port. Use the following command to specify the number of ACLs to be automatically created for dropping traffic:

Use the following command to set the action to be performed if the switch is unable to validate the VM MAC address:

Following are the other VMcheck commands:

RS 8272(config)# virt vmcheck acls max <1-256>

RS 8272(config)# virt vmcheck action advanced log|link|acl

Table 29. VMcheck Commands

Command Description

RS 8272(config)# virt vmware hello ena|hport <port number>|haddr|htimer

Hello messages setting: enable/add port/advertise this IP address in the hello messages instead of the default management IP address/set the timer to send the hello messages

RS 8272(config)# no virt vmware hello enable|hport <port number>

Disable hello messages/remove port

RS 8272(config)# [no] virt vmcheck trust <port number or range>

Mark a port as trusted; Use the no form of the command to mark port as untrusted

RS 8272# no virt vmcheck acls ACLs cannot be used for VMcheck


Virtual Distributed SwitchA virtual Distributed Switch (vDS ) allows the hypervisor’s NIC to be attached to the vDS instead of its own virtual switch. The vDS connects to the vCenter and spans across multiple hypervisors in a datacenter. The administrator can manage virtual machine networking for the entire data center from a single interface. The vDS enables centralized provisioning and administration of virtual machine networking in the data center using the VMware vCenter server.

When a member is added to a distributed VM group, a distributed port group is created on the vDS. The member is then added to the distributed port group.

Distributed port groups on a vDS are available to all hypervisors that are connected to the vDS. Members of a single distributed port group can communicate with each other.Note: vDS works with ESX 4.0 or higher versions.

To add a vDS, use the command:

Prerequisites

Before adding a vDS on the G8272, ensure the following: VMware vCenter is fully installed and configured and includes a “bladevm”

administration account and a valid SSL certificate. A virtual distributed switch instance has been created on the vCenter. The vDS

version must be higher or the same as the hypervisor version on the hosts. At least two hypervisors are configured.

Guidelines

Before migrating VMs to a vDS, consider the following:

At any one time, a VM NIC can be associated with only one virtual switch: to the hypervisor’s virtual switch, or to the vDS.

Management connection to the server must be ensured during the migration. The connection is via the Service Console or the Kernel/Management Interface.

The vDS configuration and migration can be viewed in vCenter at the following locations: vDS: Home> Inventory > Networking vDS Hosts: Home > Inventory > Networking > vDS > Hosts

Note: These changes will not be displayed in the running configuration on the G8272.

RS 8272# virt vmware dvswitch add <datacenter name> <dvSwitch name> [<dvSwitch-version>]


Migrating to vDS

You can migrate VMs to the vDS using vCenter. The migration may also be accomplished using the operational commands on the G8272 available in the following CLI menus:

For VMware vDS operations:

For VMware distributed port group operations:

RS 8272# virt vmware dvswitch ?add Add a dvSwitch to a DataCenteraddhost Add a host to a dvSwitchadduplnk Add a physical NIC to dvSwitch uplink portsdel Remove a dvSwitch from a DataCenterremhost Remove a host from a dvSwitchremuplnk Remove a physical NIC from dvSwitch uplink ports

RS 8272# virt vmware dpg ?add Add a port group to a dvSwitchdel Delete a port group from a dvSwitchupdate Update a port group on a dvSwitchvmac Change a VM NIC's port group


Virtualization Management ServersThe G8272 can connect with a virtualization management server to collect configuration information about associated VEs. The switch can also automatically push VM group configuration profiles to the virtualization management server, which in turn configures the hypervisors and VEs, providing enhanced VE mobility.

One virtual management server must be assigned on the switch before distributed VM groups may be used. N/OS 8.2 currently supports only the VMware Virtual Center (vCenter).

Assigning a vCenter

Assigning a vCenter to the switch requires the following: The vCenter must have a valid IPv4 address which is accessible to the switch

(IPv6 addressing is not supported for the vCenter). A user account must be configured on the vCenter to provide access for the

switch. The account must have (at a minimum) the following vCenter user privi-leges: Network Host Network > Configuration Virtual Machine > Modify Device Settings

Once vCenter requirements are met, the following configuration command can be used on the G8272 to associate the vCenter with the switch:

This command specifies the IPv4 address and account username that the switch will use for vCenter access. Once entered, the administrator will be prompted to enter the password for the specified vCenter account.

The noauth option causes to the switch to ignores SSL certificate authentication. This is required when no authoritative SSL certificate is installed on the vCenter.Note: By default, the vCenter includes only a self-signed SSL certificate. If using the default certificate, the noauth option is required.

Once the vCenter configuration has been applied on the switch, the G8272 will connect to the vCenter to collect VE information.

vCenter Scans

Once the vCenter is assigned, the switch will periodically scan the vCenter to collect basic information about all the VEs in the datacenter, and more detailed information about the local VEs that the switch has discovered attached to its own ports.

RS 8272(config)# virt vmware vcspec <vCenter IPv4 address> <username> [noauth]


The switch completes a vCenter scan approximately every two minutes. Any major changes made through the vCenter may take up to two minutes to be reflected on the switch. However, you can force an immediate scan of the vCenter by using one of the following ISCLI privileged EXEC commands:

Deleting the vCenter

To detach the vCenter from the switch, use the following configuration command:

Note: Without a valid vCenter assigned on the switch, any VE configuration changes must be manually synchronized.

Deleting the assigned vCenter prevents synchronizing the configuration between the G8272 and VEs. VEs already operating in distributed VM groups will continue to function as configured, but any changes made to any VM profile or distributed VM group on the switch will affect only switch operation; changes on the switch will not be reflected in the vCenter or on the VEs. Likewise, any changes made to VE configuration on the vCenter will no longer be reflected on the switch.

RS 8272# virt vmware scan (Scan the vCenter)-or-

RS 8272# show virt vm v r (Scan vCenter and display result)

RS 8272(config)# no virt vmware vcspec


Exporting Profiles

VM profiles for discovered VEs in distributed VM groups are automatically synchronized with the virtual management server and the appropriate hypervisors. However, VM profiles can also be manually exported to specific hosts before individual VEs are defined on them.

By exporting VM profiles to a specific host, virtual machine port groups will be available to the host’s internal virtual switches so that new VMs may be configured to use them.

VM migration requires that the target hypervisor includes all the virtual switch port groups to which the VM connects on the source hypervisor. The VM profile export feature can be used to distribute the associated port groups to all the potential hosts for a given VM.

A VM profile can be exported to a host using the following ISCLI privileged EXEC command:

The host list can include one or more target hosts, specified by host name, IPv4 address, or UUID, with each list item separated by a space.

Once executed, the requisite port group will be created on the specified virtual switch. If the specified virtual switch does not exist on the target host, the port group will not be created.

VMware Operational Commands

The G8272 may be used as a central point of configuration for VMware virtual switches and port groups using the following ISCLI privileged EXEC commands:

RS 8272# virt vmware export <VM profile name> <host list> <virtual switch name>

RS 8272# virt vmware ?dpg Distributed port group operationsdvswitch VMWare dvSwitch operations export Create or update a vm profile on one hostpg Add a port group to a hostscan Perform a VM Agent scan operation nowupdpg Update a port group on a hostvmacpg Change a vnic's port groupvsw Add a vswitch to a host


Pre-Provisioning VEsVEs may be manually added to VM groups in advance of being detected on the switch ports. By pre-provisioning the MAC address of VEs that are not yet active, the switch will be able to later recognize the VE when it becomes active on a switch port, and immediately assign the proper VM group properties without further configuration.

Undiscovered VEs are added to or removed from VM groups using the following configuration commands:

For the pre-provisioning of undiscovered VEs, a MAC address is required. Other identifying properties, such as IPv4 address or VM name permitted for known VEs, cannot be used for pre-provisioning.

RS 8272(config)# [no] virt vmgroup <VM group number> vm <VE MAC address>


VLAN MapsA VLAN map (VMAP) is a type of Access Control List (ACL) that is applied to a VLAN or VM group rather than to a switch port as with regular ACLs (see “Access Control Lists” on page 103). In a virtualized environment, VMAPs allow you to create traffic filtering and metering policies that are associated with a VM group VLAN, allowing filters to follow VMs as they migrate between hypervisors.

N/OS 8.2 supports up to 128 VMAPs.

Individual VMAP filters are configured in the same fashion as regular ACLs, except that VLANs cannot be specified as a filtering criteria (unnecessary, since VMAPs are assigned to a specific VLAN or associated with a VM group VLAN).

VMAPs are configured using the following ISCLI configuration command path:

Once a VMAP filter is created, it can be assigned or removed using the following commands:

For regular VLANs, use config-vlan mode:

For a VM group, use the global configuration mode:

Note: Each VMAP can be assigned to only one VLAN or VM group. However, each VLAN or VM group may have multiple VMAPs assigned to it.

The optional serverports or nonserverports parameter can be specified to apply the action (to add or remove the VMAP) for either the switch server ports (serverports) or switch uplink ports (nonserverports). If omitted, the operation will be applied to all ports in the associated VLAN or VM group.Note: VMAPs have a lower priority than port-based ACLs. If both an ACL and a VMAP match a particular packet, both filter actions will be applied as long as there is no conflict. In the event of a conflict, the port ACL will take priority, though switch statistics will count matches for both the ACL and VMAP.

RS 8272(config)# accesscontrol vmap <VMAP ID> ? action Set filter action egressport Set to filter for packets egressing this port ethernet Ethernet header options ipv4 IP version 4 header options meter ACL metering configuration mirror Mirror options packetformat Set to filter specific packet format types remark ACL remark configuration statistics Enable access control list statistics tcpudp TCP and UDP filtering options

RS 8272(config)# vlan <VLAN ID>RS 8272(configvlan)# [no] vmap <VMAP ID> [serverports|

nonserverports]

RS 8272(config)# [no] virt vmgroup <ID> vmap <VMAP ID> [serverports|nonserverports]


VM Policy Bandwidth ControlIn a virtualized environment where VEs can migrate between hypervisors and thus move among different ports on the switch, traffic bandwidth policies must be attached to VEs, rather than to a specific switch port.

VM Policy Bandwidth Control allows the administrator to specify the amount of data the switch will permit to flow from a particular VE, without defining a complicated matrix of ACLs or VMAPs for all port combinations where a VE may appear.

VM Policy Bandwidth Control Commands

VM Policy Bandwidth Control can be configured using the following configuration commands:

Bandwidth allocation can be defined for transmit (TX) traffic or receive (RX) traffic. Because bandwidth allocation is specified from the perspective of the VE, the switch command for TX Rate Control (txrate) sets the data rate to be sent from the VM to the switch, and the RX rate sets the data rate to be received by the VM from the switch.

The committed rate is specified in multiples of 64 kbps, from 64 to 10,000,000. The maximum burst rate is specified as 32, 64, 128, 256, 1024, 2048, or 4096 kb. If both the committed rate and burst are set to 0, bandwidth control will be disabled.

When txrate is specified, the switch automatically selects an available ACL for internal use with bandwidth control. Optionally, if automatic ACL selection is not desired, a specific ACL may be selected. If there are no unassigned ACLs available, txrate cannot be configured.

Bandwidth Policies vs. Bandwidth Shaping

VM Profile Bandwidth Shaping differs from VM Policy Bandwidth Control.

VM Profile Bandwidth Shaping (see “VM Profiles” on page 243) is configured per VM group and is enforced on the server by a virtual switch in the hypervisor. Shaping is unidirectional and limits traffic transmitted from the virtual switch to the G8272. Shaping is performed prior to transmit VM Policy Bandwidth Control. If the egress traffic for a virtual switch port group exceeds shaping parameters, the traffic is dropped by the virtual switch in the hypervisor. Shaping uses server CPU resources, but prevents extra traffic from consuming bandwidth between the server and the G8272.

RS 8272(config)# virt vmpolicy vmbwidth <VM MAC>|<index>|<UUID>| <IPv4 address>|<name>?txrate <committed rate> <burst> [<ACL number>]

(Set the VM transmit bandwidth – ingress for switch)

rxrate <committed rate> <burst> (Set the VM receive bandwidth – egress for switch)bwctrl (Enable bandwidth control)


VM Policy Bandwidth Control is configured per VE, and can be set independently for transmit traffic. Bandwidth policies are enforced by the G8272. VE traffic that exceeds configured levels is dropped by the switch upon ingress. Setting txrate uses ACL resources on the switch.

Bandwidth shaping and bandwidth policies can be used separately or in concert.


VMready Information DisplaysThe G8272 can be used to display a variety of VMready information.Note: Some displays depict information collected from scans of a VMware vCenter and may not be available without a valid vCenter. If a vCenter is assigned (see “Assigning a vCenter” on page 250), scan information might not be available for up to two minutes after the switch boots or when VMready is first enabled. Also, any major changes made through the vCenter may take up to two minutes to be reflected on the switch unless you force an immediate vCenter scan (see “vCenter Scans” on page 250.

Local VE Information

A concise list of local VEs and pre-provisioned VEs is available with the following ISCLI privileged EXEC command:

Note: The Index numbers shown in the VE information displays can be used to specify a particular VE in configuration commands.

RS 8272# show virt vm

IP Address VMAC Address Index Port VM Group (Profile) *172.16.46.50 00:50:56:4e:62:00 4 3*172.16.46.10 00:50:56:4f:f2:00 2 4+172.16.46.51 00:50:56:72:ec:00 1 3+172.16.46.11 00:50:56:7c:1c:00 3 4 172.16.46.25 00:50:56:9c:00:00 5 4 172.16.46.15 00:50:56:9c:21:00 0 4 172.16.46.35 00:50:56:9c:29:00 6 3 172.16.46.45 00:50:56:9c:47:00 7 3

Number of entries: 8 * indicates VMware ESX Service Console Interface + indicates VMware ESX/ESXi VMKernel or Management Interface


If a vCenter is available, more verbose information can be obtained using the following ISCLI privileged EXEC command option:

To view additional detail regarding any specific VE, see “vCenter VE Details” on page 260).

vCenter Hypervisor Hosts

If a vCenter is available, the following ISCLI privileged EXEC command displays the name and UUID of all VMware hosts, providing an essential overview of the data center:

RS 8272# show virt vm v

Index MAC Address, Name (VM or Host), Port, Group Vswitch, IP Address @Host (VMs only) VLAN Port Group 0 00:50:56:9c:21:2f atom 4 vSwitch0 172.16.46.15 @172.16.46.10 500 Eng_A

+1 00:50:56:72:ec:86 172.16.46.50 3 vSwitch0 172.16.46.51 0 VMkernel

*2 00:50:56:4f:f2:85 172.16.46.10 4 vSwitch0 172.16.46.10 0 Mgmt

+3 00:50:56:7c:1c:ca 172.16.46.10 4 vSwitch0 172.16.46.11 0 VMkernel

*4 00:50:56:4e:62:f5 172.16.46.50 3 vSwitch0 172.16.46.50 0 Mgmt

5 00:50:56:9c:00:c8 quark 4 vSwitch0 172.16.46.25 @172.16.46.10 0 Corp

6 00:50:56:9c:29:29 particle 3 vSwitch0 172.16.46.35 @172.16.46.50 0 VM Network

7 00:50:56:9c:47:fd nucleus 3 vSwitch0 172.16.46.45 @172.16.46.50 0 Finance

12 of 12 entries printed* indicates VMware ESX Service Console Interface+ indicates VMware ESX/ESXi VMkernel or Management Interface

RS 8272# show virt vmware hostsUUID Name(s), IP Address00a42681d0e55910a0bfbd23bd3f7800 172.16.41.30002e063c153cdd118b32a78dd1909a00 172.16.46.1000f1fe30143cdd1184f2a8ba2cd7ae00 172.16.44.500018938e143cdd119f7ad8defa4b8300 172.16.46.20...


Using the following command, the administrator can view more detailed vCenter host information, including a list of virtual switches and their port groups, as well as details for all associated VEs:

vCenter VEs

If a vCenter is available, the following ISCLI privileged EXEC command displays a list of all known VEs:

RS 8272# show virt vmware showhost <UUID>|<IPv4 address>|<host name>Vswitches available on the host:

vSwitch0

Port Groups and their Vswitches on the host:

BNT_Default vSwitch0 VM Network vSwitch0 Service Console vSwitch0 VMkernel vSwitch0

MAC Address 00:50:56:9c:21:2fPort 4Type Virtual MachineVM vCenter Name halibutVM OS hostname localhost.localdomainVM IP Address 172.16.46.15VM UUID 001c41f3ccd894bb1b946b94b03b9200Current VM Host 172.16.46.10Vswitch vSwitch0Port Group BNT_DefaultVLAN ID 0

...

RS 8272# show virt vmware vmsUUID Name(s), IP Address001cdf1d863afa5e58c0d197ed3e3300 30vm1001c1fba5483863fde044953b5caa700 VM90001c0441c9ed184c7030d6a6bc9b4d00 VM91001cc06e393ba36b2da9c71098d9a700 vm_new001c6384f764983c83e3e94fc78f2c00 sturgeon001c74346bf952bdc48ca410da0c2300 VM70001cad788a3c9cbe35f659ca5f392500 VM60001cf762a577f42ac6ea090216c11800 30VM6001c41f3ccd894bb1b946b94b03b9200 halibut, localhost.localdomain, 172.16.46.15001cf17b5581ea80c22c3236b89ee900 30vm5001c4312a145bf447edd49b7a2fc3800 vm3001caf40a40ade6f7b449c496f123b00 30VM7


vCenter VE Details

If a vCenter is available, the following ISCLI privileged EXEC command displays detailed information about a specific VE:

RS 8272# show virt vmware showvm <VM UUID>|<VM IPv4 address>|<VM name>MAC Address 00:50:56:9c:21:2fPort 4Type Virtual MachineVM vCenter Name halibutVM OS hostname localhost.localdomainVM IP Address 172.16.46.15VM UUID 001c41f3ccd894bb1b946b94b03b9200Current VM Host 172.16.46.10Vswitch vSwitch0Port Group BNT_DefaultVLAN ID 0


VMready Configuration ExampleThis example has the following characteristics: A VMware vCenter is fully installed and configured prior to VMready configura-

tion and includes a “bladevm” administration account and a valid SSL certifi-cate.

The distributed VM group model is used. The VM profile named “Finance” is configured for VLAN 30, and specifies

NIC-to-switch bandwidth shaping for 1Mbps average bandwidth, 2MB bursts, and 3Mbps maximum bandwidth.

The VM group includes four discovered VMs on switch server ports 1 and 2, and one static trunk (previously configured) that includes switch uplink ports 3 and 4.

1. Define the server ports.

2. Enable the VMready feature.

3. Specify the VMware vCenter IPv4 address.

When prompted, enter the user password that the switch must use for access to the vCenter.

4. Create the VM profile.

5. Define the VM group.

When VMs are added, the server ports on which they appear are automatically added to the VM group. In this example, there is no need to manually add ports 1 and 2.

6. If necessary, enable VLAN tagging for the VM group:

Note: If the VM group contains ports that also exist in other VM groups, make sure tagging is enabled in both VM groups. In this example configuration, no ports exist in more than one VM group.

7. Save the configuration.

RS 8272(config)# system serverports port 12

RS 8272(config)# virt enable

RS 8272(config)# virt vmware vmware vcspec 172.16.100.1 bladevm

RS 8272(config)# virt vmprofile FinanceRS 8272(config)# virt vmprofile edit Finance vlan 30RS 8272(config)# virt vmprofile edit Finance shaping 1000 2000 3000

RS 8272(config)# virt vmgroup 1 profile FinanceRS 8272(config)# virt vmgroup 1 vm arcticRS 8272(config)# virt vmgroup 1 vm monsterRS 8272(config)# virt vmgroup 1 vm sierraRS 8272(config)# virt vmgroup 1 vm 00:50:56:4f:f2:00RS 8272(config)# virt vmgroup 1 portchannel 1

RS 8272(config)# virt vmgroup 1 tag



Chapter 18. FCoE and CEE

This chapter provides conceptual background and configuration examples for using Converged Enhanced Ethernet (CEE) features of the RackSwitch G8272, with an emphasis on Fibre Channel over Ethernet (FCoE) solutions. The following topics are addressed in this chapter:

“Fibre Channel over Ethernet” on page 265Fibre Channel over Ethernet (FCoE) allows Fibre Channel traffic to be transported over Ethernet links. This provides an evolutionary approach toward network consolidation, allowing Fibre Channel equipment and tools to be retained, while leveraging cheap, ubiquitous Ethernet networks for growth.

“Converged Enhanced Ethernet” on page 267Converged Enhanced Ethernet (CEE) refers to a set of IEEE standards developed primarily to enable FCoE, requiring enhancing the existing Ethernet standards to make them lossless on a per-priority traffic basis, and providing a mechanism to carry converged (LAN/SAN/IPC) traffic on a single physical link. CEE features can also be utilized in traditional LAN (non-FCoE) networks to provide lossless guarantees on a per-priority basis, and to provide efficient bandwidth allocation.

“FCoE Initialization Protocol Snooping” on page 270Using FCoE Initialization Protocol (FIP) snooping, the G8272 examines the FIP frames exchanged between ENodes and FCoE Forwarders (FCFs). This information is used to dynamically determine the ACLs required to block certain types of undesired or unvalidated traffic on FCoE links.

“FCoE Forwarder” on page 275An FCoE Forwarder (FCF) authenticates connecting neighbors, provides Fibre Channel IDs, enforce port security among zones, and informs neighboring devices of network changes.

“Priority-Based Flow Control” on page 281Priority-Based Flow Control (PFC) extends 802.3x standard flow control to allow the switch to pause traffic based on the 802.1p priority value in each packet’s VLAN tag. PFC is vital for FCoE environments, where SAN traffic must remain lossless and must be paused during congestion, while LAN traffic on the same links is delivered with “best effort” characteristics.

“Enhanced Transmission Selection” on page 284Enhanced Transmission Selection (ETS) provides a method for allocating link bandwidth based on the 802.1p priority value in each packet’s VLAN tag. Using ETS, different types of traffic (such as LAN, SAN, and management) that are sensitive to different handling criteria can be configured either for specific bandwidth characteristics, low-latency, or best-effort transmission, despite sharing converged links as in an FCoE environment.


“Data Center Bridging Capability Exchange” on page 290Data Center Bridging Capability Exchange Protocol (DCBX) allows neighboring network devices to exchange information about their capabilities. This is used between CEE-capable devices for the purpose of discovering their peers, negotiating peer configurations, and detecting misconfigurations.

© Copyright Lenovo 2015 Chapter 18: FCoE and CEE 265

Fibre Channel over EthernetFibre Channel over Ethernet (FCoE) is an effort to converge two of the different physical networks in today’s data centers. It allows Fibre Channel traffic (such as that commonly used in Storage Area Networks, or SANs) to be transported without loss over 10Gb Ethernet links (typically used for high-speed Local Area Networks, or LANs). This provides an evolutionary approach toward network consolidation, allowing Fibre Channel equipment and tools to be retained, while leveraging cheap, ubiquitous Ethernet networks for growth.

With server virtualization, servers capable of hosting both Fibre Channel and Ethernet applications will provide advantages in server efficiency, particularly as FCoE-enabled network adapters provide consolidated SAN and LAN traffic capabilities.

The RackSwitch G8272 with Lenovo Networking OS 8.2 software is compliant with the INCITS T11.3, FC-BB-5 FCoE specification.Note: The G8272 supports up to 2048 FCoE login sessions.

The FCoE TopologyNote: The FCoE topology discussed in this section applies to FCoE Initialization Protocol (FIP) snooping only.

In an end-to-end Fibre Channel network, switches and end devices generally establish trusted, point-to-point links. Fibre Channel switches validate end devices, enforce zoning configurations and device addressing, and prevent certain types of errors and attacks on the network.

In a converged multi-hop FCoE network where Fibre Channel devices are bridged to Ethernet devices, the direct point-to-point QoS capabilities normally provided by the Fibre Channel fabric may be lost in the transition between the different network types. The G8272 FIP snooping bridge provides a solution to overcome this.

Figure 24. A Mixed Fibre Channel and FCoE Network

Fibre

ChannelLAN

Servers

0-24

LAN

Business-Critical LAN

802.1p Priority & Usage

3 FCoE Applications

802.1p Priority & UsageFCoECNA

CNA

LenovoSwitch

FCFDevice

Port 2

Port 3 Port 4

Port 1


In Figure 24 on page 265, the Fibre Channel network is connected to the FCoE network through an FCoE Forwarder (FCF). The FCF acts as a Fibre Channel gateway to and from the FCoE network.

For the FCoE portion of the network, the FCF is connected to the FCoE-enabled G8272, which is connected to a server (running Fibre Channel applications) through an FCoE-enabled Converged Network Adapter (CNA) known in Fibre Channel as Ethernet Nodes (ENodes).Note: The figure also shows a non-FCoE LAN server connected to the G8272 using a CNA. This allows the LAN server to take advantage of some CEE features that are useful even outside of an FCoE environment.

To block undesired or unvalidated traffic on FCoE links that exists outside the regular Fibre Channel topology, Ethernet ports used in FCoE are configured with Access Control Lists (ACLs) that are narrowly tailored to permit expected FCoE traffic to and from confirmed FCFs and ENodes, and deny all other FCoE or FIP traffic. This ensures that all FCoE traffic to an from the ENode passes through the FCF.

Because manual ACL configuration is an administratively complex task, the G8272 can automatically and dynamically configure the ACLs required for use with FCoE. Using FCoE Initialization Protocol (FIP) snooping (see “FCoE Initialization Protocol Snooping” on page 270), the G8272 examines the FIP frames normally exchanged between the FCF and ENodes to determine information about connected FCoE devices. This information is used to automatically determine the appropriate ACLs required to block certain types of undesired or unvalidated FCoE traffic.

Automatic FCoE-related ACLs are independent from ACLs used for typical Ethernet purposes.

FIP Snooping Requirements

The following are required for implementing the FIP snooping bridge feature using the RackSwitch G8272 (G8272) with N/OS 8.2 software: The G8272, when configured as an FIP snooping bridge (see “FCoE Initialization

Protocol Snooping” on page 270), must be connected to the Fibre Channel net-work through an FCF such as a Lenovo RackSwitch G8272 or a Cisco Nexus 5000 Series Switch.

For each G8272 port participating in FCoE, the connected server must use a FCoE-licensed CNA.

CEE must be turned on (see “Turning CEE On or Off” on page 267). When CEE is on, the DCBX, PFC, and ETS features are enabled and configured with default FCoE settings. These features may be reconfigured, but must remain enabled for FCoE to function.

FIP snooping must be turned on (see “FCoE Initialization Protocol Snooping” on page 270). When FIP snooping is turned on, the feature is enabled on all ports by default. The administrator can disable FIP snooping on individual ports that do not require FCoE, but FIP snooping must remain enabled on all FCoE ports for FCoE to function.


Converged Enhanced EthernetConverged Enhanced Ethernet (CEE) refers to a set of IEEE standards designed to allow different physical networks with different data handling requirements to be converged together, simplifying management, increasing efficiency and utilization, and leveraging legacy investments without sacrificing evolutionary growth.

CEE standards were developed primarily to enable Fibre Channel traffic to be carried over Ethernet networks. This required enhancing the existing Ethernet standards to make them lossless on a per-priority traffic basis, and to provide a mechanism to carry converged (LAN/SAN/IPC) traffic on a single physical link. Although CEE standards were designed with FCoE in mind, they are not limited to FCoE installations. CEE features can be utilized in traditional LAN (non-FCoE) networks to provide lossless guarantees on a per-priority basis, and to provide efficient bandwidth allocation based on application needs.

Turning CEE On or Off

By default on the G8272, CEE is turned off. To turn CEE on or off, use the following CLI commands:

CAUTION:Turning CEE on will automatically change some 802.1p QoS and 802.3x standard flow control settings on the G8272. Read the following material carefully to determine whether you will need to take action to reconfigure expected settings.

It is recommended that you backup your configuration prior to turning CEE on. Viewing the file will allow you to manually re-create the equivalent configuration once CEE is turned on, and will also allow you to recover your prior configuration if you need to turn CEE off.

Effects on Link Layer Discovery Protocol

When CEE is turned on, Link Layer Discovery Protocol (LLDP) is automatically turned on and enabled for receiving and transmitting DCBX information. LLDP cannot be turned off while CEE is turned on.

RS 8272(config)# [no] cee enable


Effects on 802.1p Quality of Service

While CEE is off (the default), the G8272 allows 802.1p priority values to be used for Quality of Service (QoS) configuration (see page 187). 802.1p QoS default settings are shown in Table 30, but can be changed by the administrator.

When CEE is turned on, 802.1p QoS is replaced by ETS (see “Enhanced Transmission Selection” on page 284). As a result, while CEE is turned on, the 802.1p QoS configuration commands are no longer available on the switch (the menu is restored when CEE is turned off).

In addition, when CEE is turned on, prior 802.1p QoS settings are replaced with new defaults designed for use with ETS priority groups (PGIDs) as shown in Table 30:

When CEE is on, the default ETS configuration also allocates a portion of link bandwidth to each PGID as shown in Table 31:

If the prior, non-CEE configuration used 802.1p priority values for different purposes, or does not expect bandwidth allocation as shown in Table 31 on page 268, when CEE is turned on, have the administrator reconfigure ETS settings as appropriate.

Table 30. CEE Effects on 802.1p Defaults

802.1p QoS ConfigurationWith CEE Off (default)

ETS ConfigurationWith CEE On

Priority- COSq Weight Priority COSq PGID

0 0 1 0 0 0

1 1 2 1 0 0

2 2 3 2 0 0

3 3 4 3 1 1

4 4 5 4 2 2

5 5 7 5 2 2

6 6 15 6 2 2

7 7 0 7 2 2

Table 31. Default ETS Bandwidth Allocation

PGID Typical Use Bandwidth

0 LAN 10%

1 SAN 50%

2 Latency-sensitive LAN

40%


It is recommended that a configuration backup be made prior to turning CEE on or off. Viewing the configuration file will allow the administrator to manually re-create the equivalent configuration under the new CEE mode, and will also allow for the recovery of the prior configuration if necessary.

Effects on Flow Control

When CEE is turned on, standard flow control is disabled on all ports, and in its place, PFC (see “Priority-Based Flow Control” on page 281) is enabled on all ports for 802.1p priority value 3. This default is chosen because priority value 3 is commonly used to identify FCoE traffic in a CEE environment and must be guaranteed lossless behavior. PFC is disabled for all other priority values.

Each time CEE is turned off, the prior 802.3x standard flow control settings will be restored (including any previous changes from the defaults).

It is recommend that a configuration backup be made prior to turning CEE on or off. Viewing the configuration file will allow the administrator to manually re-create the equivalent configuration under the new CEE mode, and will also allow for the recovery of the prior configuration if necessary.

When CEE is on, PFC can be enabled only on priority value 3 and one other priority. If flow control is required on additional priorities on any given port, consider using standard flow control on that port, so that regardless of which priority traffic becomes congested, a flow control frame is generated.


FCoE Initialization Protocol SnoopingFCoE Initialization Protocol (FIP) snooping is an FCoE feature. To enforce point-to-point links for FCoE traffic outside the regular Fibre Channel topology, Ethernet ports used in FCoE can be automatically and dynamically configured with Access Control Lists (ACLs).

Using FIP snooping, the G8272 examines the FIP frames normally exchanged between the FCF and ENodes to determine information about connected FCoE devices. This information is used to create narrowly tailored ACLs that permit expected FCoE traffic to and from confirmed Fibre Channel nodes, and deny all other undesirable FCoE or FIP traffic.

Global FIP Snooping Settings

By default, the FIP snooping feature is turned off for the G8272. The following commands are used to turn the feature on or off:

Note: FIP snooping requires CEE to be turned on (see “Turning CEE On or Off” on page 267).

When FIP snooping is on, port participation may be configured on a port-by-port basis (see the next sections).

When FIP snooping is off, all FCoE-related ACLs generated by the feature are removed from all switch ports.

FIP Snooping for Specific Ports

When FIP snooping is globally turned on (see the previous section), ports may be individually configured for participation in FIP snooping and automatic ACL generation. By default, FIP snooping is enabled for each port. To change the setting for any specific port, use the following CLI commands:

When FIP snooping is enabled on a port, FCoE-related ACLs will be automatically configured.

When FIP snooping is disabled on a port, all FCoE-related ACLs on the port are removed, and the switch will enforce no FCoE-related rules for traffic on the port.

RS 8272(config)# [no] fcoe fips enable

RS 8272(config)# [no] fcoe fips port <port alias, number, list, or range> enable


Port FCF and ENode Detection

When FIP snooping is enabled on a port, the port is placed in FCF auto-detect mode by default. In this mode, the port assumes connection to an ENode unless FIP packets show the port is connected to an FCF.

Ports can also be specifically configured as to whether automatic FCF detection will be used, or whether the port is connected to an FCF or ENode:

When FCF mode is on, the port is assumed to be connected to a trusted FCF, and only ACLs appropriate to FCFs will be installed on the port. When off, the port is assumed to be connected to an ENode, and only ACLs appropriate to ENodes will be installed. When the mode is changed (either through manual configuration or as a result of automatic detection), the appropriate ACLs are automatically added, removed, or changed to reflect the new FCF or ENode connection.

FCoE Connection Timeout

FCoE-related ACLs are added, changed, and removed as FCoE device connection and disconnection are discovered. In addition, the administrator can enable or disable automatic removal of ACLs for FCFs and other FCoE connections that timeout (fail or are disconnected) without FIP notification.

By default, automatic removal of ACLs upon timeout is enabled. To change this function, use the following CLI command:

FCoE ACL Rules

When FIP Snooping is enabled on a port, the switch automatically installs the appropriate ACLs to enforce the following rules for FCoE traffic: Ensure that FIP frames from ENodes may only be addressed to FCFs. Flag important FIP packets for switch processing. Ensure no end device uses an FCF MAC address as its source. Each FCoE port is assumed to be connected to an ENode and include ENode-spe-

cific ACLs installed, until the port is either detected or configured to be con-nected to an FCF.

Ports that are configured to have FIP snooping disabled will not have any FIP or FCoE related ACLs installed.

Prevent transmission of all FCoE frames from an ENode prior to its successful completion of login (FLOGI) to the FCF.

After successful completion of FLOGI, ensure that the ENode uses only those FCoE source addresses assigned to it by FCF.

After successful completion of FLOGI, ensure that all ENode FCoE source addresses originate from or are destined to the appropriate ENode port.

After successful completion of each FLOGI, ensure that FCoE frames may only be addressed to the FCFs that accept them.

RS 8272(config)# fcoe fips port <port alias, number, list, or range> fcfmode auto|on|off

RS 8272(config)# [no] fcoe fips timeoutacl


Initially, a basic set of FCoE-related ACLs will be installed on all ports where FIP snooping is enabled. As the switch encounters FIP frames and learns about FCFs and ENodes that are attached or disconnect, ACLs are dynamically installed or expanded to provide appropriate security.

When an FCoE connection logs out, or times out (if ACL timeout is enabled), the related ACLs will be automatically removed.

FCoE-related ACLs are independent of manually configured ACLs used for regular Ethernet purposes (see “Access Control Lists” on page 103). FCoE ACLs generally have a higher priority over standard ACLs, and do not inhibit non-FCoE and non-FIP traffic.

FCoE VLANs

FCoE packets to any FCF will be confined to the VLAN advertised by the FCF (typically VLAN 1002). The appropriate VLAN must be configured on the switch with member FCF ports and must be supported by the participating CNAs.

Viewing FIP Snooping Information

ACLs automatically generated under FIP snooping are independent of regular, manually configure ACLs, and are not listed with regular ACLs in switch information and statistics output. Instead, FCoE ACLs are shown using the following CLI commands:

For example:

For each ACL, the required traffic criteria are listed, along with the action taken (permit or deny) for matching traffic. ACLs are listed in order of precedence and evaluated in the order shown.

RS 8272# show fcoe fips information (Show all FIP-related information)RS 8272# show fcoe fips port <ports> information (Show FIP info for a selected port)

RS 8272# show fcoe fips port 21 information

FIP Snooping on port 21:This port has been configured to automatically detect FCF. It has currently detected to have 0 FCF connecting to it.

FIPS ACLs configured on this port:SMAC 00:05:73:ce:96:67, action deny.DMAC 00:05:73:ce:96:67, ethertype 0x8914, action permit.SMAC 0e:fc:00:44:04:04, DMAC 00:05:73:ce:96:67, ethertype 0x8906, vlan 1002, action permit.DMAC 01:10:18:01:00:01, Ethertype 0x8914, action permit.DMAC 01:10:18:01:00:02, Ethertype 0x8914, action permit.Ethertype 0x8914, action deny.Ethertype 0x8906, action deny.SMAC 0e:fc:00:00:00:00, SMAC mask ff:ff:ff:00:00:00, action deny.


The administrator can also view other FCoE information:

Operational Commands

The administrator may use the operational commands to delete FIP-related entries from the switch.

To delete a specific FCF entry and all associated ACLs from the switch, use the following command:

FIP Snooping Configuration

In this example, as shown in Figure 24 on page 265, FCoE devices are connected to port 2 for the FCF device, and port 3 for an ENode. FIP snooping can be configured on these ports using the following ISCLI commands:

1. Enable VLAN tagging on the FCoE ports:

2. Place FCoE ports into a VLAN supported by the FCF and CNAs (typically VLAN 1002):

3. Turn CEE on.

Note: Turning CEE on will automatically change some 802.1p QoS and 802.3x standard flow control settings and menus (see “Turning CEE On or Off” on page 267).

4. Turn global FIP snooping on:

RS 8272# show fcoe fips fcf (Show all detected FCFs)RS 8272# show fcoe fips fcoe (Show all FCoE connections)

RS 8272# no fcoe fips fcf <FCF MAC address> [<VLAN number>]

RS 8272(config)# interface port 2,3 (Select FCoE ports)RS 8272(configif)# switchport mode trunk(Enable VLAN tagging)RS 8272(configif)# exit (Exit port configuration mode)

RS 8272(config)# vlan 1002 (Select a VLAN)RS 8272(configvlan)# exit (Exit VLAN configuration mode)RS 8272(config)# interface port 2,3 (Add FCoE ports to the VLAN)RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 1002RS 8272(configif)# exit

RS 8272(config)# cee enable

RS 8272(config)# fcoe fips enable


5. Enable FIP snooping on FCoE ports, and set the desired FCF mode:

Note: By default, FIP snooping is enabled on all ports and the FCF mode set for automatic detection. The configuration in this step is unnecessary, if default settings have not been changed, and is shown merely as a manual configuration example.


RS 8272(config)# fcoe fips port 2 enable(Enable FIPS on port 2)RS 8272(config)# fcoe fips port 2 fcfmode on(Set as FCF connection)RS 8272(config)# fcoe fips port 3 enable(Enable FIPS on port 3)RS 8272(config)# fcoe fips port 3 fcfmode off(Set as ENode connection)


FCoE ForwarderThe RackSwitch G8272 has an integrated FC-BB-5 compliant FCoE Forwarder (FCF), allowing it to take the role of a full fabric FCoE switch. As a full fabric FCoE switch, the G8272 authenticates connecting neighbors, provides Fibre Channel IDs, enforces port security among zones, and informs neighboring devices of network changes. In FCF mode, the G8272 cannot be connected directly to another FCF switch in the same VLAN.

Configuring FCF

The switch’s role as a full fabric switch in the FCoE network can be defined on a per-VLAN basis. The G8272 supports up to 12 FCF VLANs. To enable or disable FCF for a specific VLAN:

To connect an FCoE device or enode to a port of a G8272, the following conditions must be met:

The port must be in trunk mode.

The port must be configured as a Spanning Tree port.

The FCoE VLAN must be included in the trunk allowed VLANs list.

The FCoE VLAN must not be the native VLAN of the trunk port.

For example, to make port 2, which is connected to an FCoE device, part of FCF-enabled vlan 1002, use the following commands:

Fibre Channel Services

The following Fibre Channel (FC) services are supported:

Name Server (Directory Server) – provides a means to discover information about ENodes connected to the FCF. This Service is provided through Well Known Address (WKA) FFFFFCh.

Zone Server – provides partitioning of a SAN fabric into smaller subsets to restrict interference, add security, and simplify management.

Fabric Login – assigns a fabric address (FCID) to the ENode. This service is provided through WKA FFFFFEh.

Fabric Controller – provides State Change Notifications (SCNs) to registered ENodes whenever there is a change in the fabric topology.

RS 8272(config)# vlan <VLAN number>RS 8272(configvlan)# [no] fcf enable

RS 8272(config)# vlan 1002RS 8272(configvlan)# fcf enableRS 8272(configvlan)# exitRS 8272(config)# interface port 2RS 8272(configif)# switchport mode trunkRS 8272(configif)# spanningtree portfastRS 8272(configif)# switchport trunk allowed vlan add 1002RS 8272(configif)# exit


Fabric Configuration Server (FCS) – provides a way for a management application to discover fabric attributes. This Service is provided through WKA FFFFFAh.

Fabric-Device Management Interface (FDMI) – enables management for devices such as CNAs through the fabric.

FC services are provided as Class 3 (Unacknowledged connectionless services) only.

FCF VLAN Configuration

For a FCF VLAN default FCoE parameters will be set once it is enabled. The default values are:

FC-MAP : 0x0efc00

FCF-Priority : 128

FKA-Adv : 8000

If you want to change these values, use the following commands to configure VLAN settings for FCF:

1. Select the FCF vlan:

2. Configure the FCF global fabric priority:

3. Define an FC map to uniquely identify the FCF:

4. Configure the FIP keep-alive duration in ms:

5. Check FCF Vlan Configuration:

Full Fabric Zoning

The G8272 supports FCoE zones and zonesets for VLANs operating in full fabric mode. Zoning allows logical grouping of ports and storage devices within a storage area network. Zoning defines access control between groups of servers and storage devices.

An SAN is typically divided into zones and zonesets, as described in the following sections.

RS 8272(config)# vlan <VLAN number>

RS 8272(configvlan)# fcoe fcfpriority <0 – 255>

RS 8272(configvlan)# fcoe fcmap <0xefc00 – 0xefcff>

RS 8272(configvlan)# fcoe fkaadvperiod <4000 – 90000>

RS 8272(config)# show fcf vlan <VLAN number>


Zones

A zone is a logical grouping of end nodes that are permitted to interact with each other. Zones can be grouped into zonesets that can be activated or deactivated as a single entity. A zone provides security by restricting access to only those devices that reside within the zone. Zoning also confines change notification floods within each zone.

Each zone contains one or more servers and one or more storage devices. Ports and devices in a zone are called zone members. A zone contains one or more zone members. A device can belong to one or more zones. End nodes that are members of a zone can communicate with each other, but they are isolated from nodes in other zones of which they are not a member.

If no zone is configured for the device, it resides in the default zone. You can configure the default zone to permit or deny its member devices to communicate with each other. By default, the default zone is set to deny.

You can specify zone members based on any of the following criteria:

pWWN: The port World Wide Number is a unique ID representing a particular end node. The pWWN is a 64-bit hexadecimal value (for example, 20:34:00:80:e5:23:f4:55)

FC alias: The Fibre Channel alias specifies the device that connects to a node port on the switch. The FC alias is a 1-64 character text value (for example, “StorageOne”).

Notes:

When you create an FC alias using SNMP, a default pWWN of value 10:00:00:00:00:00:00:00 is automatically assigned to the FC alias. You must change this default pWWN value. Not doing so will result in a conflict of pWWN IDs the next time you try to create an FC alias.

The G8272 uses hard zoning, which is enforced in the switch hardware, based on the pWWNs of the Fibre Channel initiators and targets.

The G8272 supports up the 512 zones per zoneset, each with up to 32 member devices.

Zonesets

Zonesets provide a mechanism for conveniently grouping zones. Each zoneset can contain one or more zones. A zone can belong to one or more zonesets. Only one zoneset can be activated at a given time. If you deactivate the active zoneset, no zonesets are active until you activate another zoneset. If you activate one zoneset while another zoneset is active, the currently active zoneset is deactivated.

When you activate a zoneset, the new zoneset access policies are applied. Any changes to the active zoneset will impact only the traffic between the affected ports.

Affected ports are those ports for which there is a change in the peering relationship due to active zoneset change. RSCNs are generated only for the affected ports.

By default the default-zone status is deny all.


Without zoning configuration, none of the Storage targets is visible to hosts. The default-zone configuration can be made permit all using the following command:

Note: We recommend that you activate well-defined zoning configuration for increased security.

Defining and Activating Zoning

Define the following general properties for Fibre Channel zones and zonesets:

1. If desired, create (or remove) aliases for Fibre Channel devices:

Repeat for each alias as necessary.

2. If desired, add (or remove) members to the FC aliases:

3. For each desired zone:

a. Name (or remove) the zone.

b. Add (or remove) one or more members to the zone using either pWWNs or FC Aliases:

or:

Repeat as necessary for each member device.

c. Exit from zone configuration:

d. Check the zone setup:

RS 8272(config)# zone defaultzone permit vlan <VLAN number>

RS 8272(config)# [no] fcalias name <device alias name> vlan <VLAN number>

RS 8272(configfcalias)# [no] member pwwn <Port World Wide Name>

RS 8272(config)# [no] zone name <zone name> vlan <VLAN number>

RS 8272(configzone)# [no] member pwwn <Port World Wide Name>

RS 8272(configzone)# [no] fcalias <device alias name>

RS 8272(configzone)# exit

RS 8272(config)# show zone name <zone name> vlan <VLAN number>


4. For each desired zoneset:

a. Name (or remove) the zoneset.

b. Add (or remove) one or more member zones to the zoneset:

Repeat as necessary for each member zone.

c. Exit from zoneset configuration:

d. Activate the zoneset:.

e. Check the zoneset setup:

5. To check overview of zoning status for a vlan:

Changing the Active Zoneset

Fibre Channel is intended to operate with minimal disruption. To prevent the various synchronization events that would result if each stage of a live zoning configuration was applied, the cumulative configuration changes for zones and zoneset are held in reserve until explicitly activated by an administrator.

When activated, the new zoneset is synchronized throughout the Fibre Channel fabric for each modified zone. Fibre Channel traffic is temporarily disrupted in modified zones as changes to the fabric are recognized by the connected devices. Until activation, the previously established zoneset remains in effect.

The basic zoneset commands are as follows:

Activate or deactivate a zoneset:

View the settings for the active zoneset:

RS 8272(config)# [no] zoneset name <zoneset name> vlan <VLAN number>

RS 8272(configzoneset)# [no] member name <zone name>

RS 8272(configzoneset)# exit

RS 8272(config)# zoneset activate name <zoneset name> vlan <VLAN number>

RS 8272(config)# show zoneset name <zoneset name> vlan <VLAN number>

RS 8272(config)# show zone status vlan <VLAN number>

RS 8272(config)# [no] zoneset activate name <zoneset name> vlan <VLAN number>

RS 8272(config)# show zoneset active vlan <VLAN number>


View the settings for the pending configuration changes:

FCF Scalability

The following scaling limits apply for full fabric FCF:

Maximum number of VLANs on which FCF can be enabled: 12

Maximum number of logins per VLAN: 2048

Maximum number of logins across all 12 VLANs: 2048

Maximum number of zonesets per VLAN: 8

Maximum number of zones per VLAN: 512

Maximum number of members per zone: 32

Maximum number of members in all zones per VLAN: 1024

Maximum number of aliases in all zones per VLAN: 1024

RS 8272(config)# show zoneset vlan <VLAN number>


Priority-Based Flow ControlPriority-based Flow Control (PFC) is defined in IEEE 802.1Qbb. PFC extends the IEEE 802.3x standard flow control mechanism. Under standard flow control, when a port becomes busy, the switch manages congestion by pausing all the traffic on the port, regardless of the traffic type. PFC provides more granular flow control, allowing the switch to pause specified types of traffic on the port, while other traffic on the port continues.

PFC pauses traffic based on 802.1p priority values in the VLAN tag. The administrator can assign different priority values to different types of traffic and then enable PFC for up to two specific priority values: priority value 3, and one other. The configuration can be applied globally for all ports on the switch. Then, when traffic congestion occurs on a port (caused when ingress traffic exceeds internal buffer thresholds), only traffic with priority values where PFC is enabled is paused. Traffic with priority values where PFC is disabled proceeds without interruption but may be subject to loss if port ingress buffers become full.

Although PFC is useful for a variety of applications, it is required for FCoE implementation where storage (SAN) and networking (LAN) traffic are converged on the same Ethernet links. Typical LAN traffic tolerates Ethernet packet loss that can occur from congestion or other factors, but SAN traffic must be lossless and requires flow control.

For FCoE, standard flow control would pause both SAN and LAN traffic during congestion. While this approach would limit SAN traffic loss, it could degrade the performance of some LAN applications that expect to handle congestion by dropping traffic. PFC resolves these FCoE flow control issues. Different types of SAN and LAN traffic can be assigned different IEEE 802.1p priority values. PFC can then be enabled for priority values that represent SAN and LAN traffic that must be paused during congestion, and disabled for priority values that represent LAN traffic that is more loss-tolerant.

PFC requires CEE to be turned on (“Turning CEE On or Off” on page 267). When CEE is turned on, PFC is enabled on priority value 3 by default. Optionally, the administrator can also enable PFC on one other priority value, providing lossless handling for another traffic type, such as for a business-critical LAN application.Note: For any given port, only one flow control method can be implemented at any given time: either PFC or standard IEEE 802.3x flow control.


Global Configuration

PFC requires CEE to be turned on (“Turning CEE On or Off” on page 267). When CEE is turned on, standard flow control is disabled on all ports, and PFC is enabled on all ports for 802.1p priority value 3. While CEE is turned on, PFC cannot be disabled for priority value 3. This default is chosen because priority value 3 is commonly used to identify FCoE traffic in a CEE environment and must be guaranteed lossless behavior. PFC is disabled for all other priority values by default, but can be enabled for one additional priority value.Note: When using global PFC configuration in conjunction with the ETS feature (see “Enhanced Transmission Selection” on page 284), ensure that only pause-tolerant traffic (such as lossless FCoE traffic) is assigned priority values where PFC is enabled. Pausing other types of traffic can have adverse effects on LAN applications that expect uninterrupted traffic flow and tolerate dropping packets during congestion.

PFC Configuration Example

Note: DCBX may be configured to permit sharing or learning PFC configuration with or from external devices. This example assumes that PFC configuration is being performed manually. See “Data Center Bridging Capability Exchange” on page 290 for more information on DCBX. Even if the G8272 learns the PFC configuration from a DCBX peer, the PFC configuration must be performed manually.

This example is consistent with the network shown in Figure 24 on page 265. In this example, the following topology is used.

In this example, PFC is to facilitate lossless traffic handling for FCoE (priority value 3) and a business-critical LAN application (priority value 4).

Table 32. Port-Based PFC Configuration

SwitchPort

802.1pPriority

UsagePFC

Setting

1 0-2 LAN Disabled

3 (not used) Enabled

4 Business-critical LAN Enabled

others (not used) Disabled

3 3 FCoE Enabled


4 0-2 LAN Disabled

3 (not used) Enabled

4 Business-critical LAN Enabled



Assuming that CEE is off (the G8272 default), the example topology shown in Table 32 can be configured using the following commands:

1. Turn CEE on.


2. Enable PFC for the FCoE traffic.

Note: PFC is enabled on priority 3 by default. If using the defaults, the manual configuration commands shown in this step are not necessary.

3. Enable PFC for the business-critical LAN application:



RS 8272(config)# cee port 1 pfc priority 4 enable(Enable on LAN priority)RS 8272(config)# cee port 1 pfc priority 4 description "Critical LAN"

(Optional description)RS 8272(config)# cee port 4 pfc priority 4 enable( Enable on LAN priority)RS 8272(config)# cee port 4 pfc priority 4 description "Critical LAN"

(Optional description)


Enhanced Transmission SelectionEnhanced Transmission Selection (ETS) is defined in IEEE 802.1Qaz. ETS provides a method for allocating port bandwidth based on 802.1p priority values in the VLAN tag. Using ETS, different amounts of link bandwidth can specified for different traffic types (such as for LAN, SAN, and management).

ETS is an essential component in a CEE environment that carries different types of traffic, each of which is sensitive to different handling criteria, such as Storage Area Networks (SANs) that are sensitive to packet loss, and LAN applications that may be latency-sensitive. In a single converged link, such as when implementing FCoE, ETS allows SAN and LAN traffic to coexist without imposing contrary handling requirements upon each other.

The ETS feature requires CEE to be turned on (see “Turning CEE On or Off” on page 267).

802.1p Priority Values

Under the 802.1p standard, there are eight available priority values, with values numbered 0 through 7, which can be placed in the priority field of the 802.1Q VLAN tag:

Servers and other network devices may be configured to assign different priority values to packets belonging to different traffic types (such as SAN and LAN).

ETS uses the assigned 802.1p priority values to identify different traffic types. The various priority values are assigned to priority groups (PGID), and each priority group is assigned a portion of available link bandwidth.

Priority values within in any specific ETS priority group are expected to have similar traffic handling requirements with respect to latency and loss.

802.1p priority values may be assigned by the administrator for a variety of purposes. However, when CEE is turned on, the G8272 sets the initial default values for ETS configuration as follows:

Figure 25. Default ETS Priority Groups

16 bits 3 bits 1 12 bits

Tag Protocol ID (0x8100) Priority CFI

VLAN ID

0 15 16 32

802.1pPriorityTypical Traffic Type

LAN

LAN

Latency-Sensitive LAN




LAN

SAN

PGID

01234567

0

1

2

BandwidthAllocation

10%

50%

40%


In the assignment model shown in Figure 25 on page 284, priority values 0 through 2 are assigned for regular Ethernet traffic, which has “best effort” transport characteristics.

Because CEE and ETS features are generally associated with FCoE, Priority 3 is typically used to identify FCoE (SAN) traffic.

Priorities 4-7 are typically used for latency sensitive traffic and other important business applications. For example, priority 4 and 5 are often used for video and voice applications such as IPTV, Video on Demand (VoD), and Voice over IP (VoIP). Priority 6 and 7 are often used for traffic characterized with a “must get there” requirement, with priority 7 used for network control which is requires guaranteed delivery to support configuration and maintenance of the network infrastructure.Note: The default assignment of 802.1p priority values on the G8272 changes depending on whether CEE is on or off. See “Turning CEE On or Off” on page 267 for details.

Priority Groups

For ETS use, each 801.2p priority value is assigned to a priority group which can then be allocated a specific portion of available link bandwidth. To configure a priority group, the following is required:

CEE must be turned on (“Turning CEE On or Off” on page 267) for the ETS feature to function.

A priority group must be assigned a priority group ID (PGID), one or more 802.1p priority values, and allocated link bandwidth greater than 9%.

PGIDEach priority group is identified with number (0 through 7, and 15) known as the PGID.

PGID 0 through 7 may each be assigned a portion of the switch’s available bandwidth.

PGID 8 through 14 are reserved as per the 802.1Qaz ETS standard.

PGID 15 is a strict priority group. It is generally used for critical traffic, such as network management. Any traffic with priority values assigned to PGID 15 is permitted as much bandwidth as required, up to the maximum available on the switch. After serving PGID 15, any remaining link bandwidth is shared among the other groups, divided according to the configured bandwidth allocation settings.

Make sure all 802.1p priority values assigned to a particular PGID have similar traffic handling requirements. For example, PFC-enabled traffic must not be grouped with non-PFC traffic. Also, traffic of the same general type must be assigned to the same PGID. Splitting one type of traffic into multiple 802.1p priorities, and then assigning those priorities to different PGIDs may result in unexpected network behavior.

Each 802.1p priority value may be assigned to only one PGID. However, each PGID may include multiple priority values. Up to eight PGIDs may be configured at any given time.


Assigning Priority Values to a Priority GroupEach priority group may be configured from its corresponding ETS Priority Group, available using the following command:

where priority list is one or more 802.1p priority values (with each separated by a comma). For example, to assign priority values 0 through 2:

Note: Within any specific PGID, the PFC settings (see “Priority-Based Flow Control” on page 281) must be the same (enabled or disabled) for all priority values within the group. PFC can be enabled only on priority value 3 and one other priority.

When assigning priority values to a PGID, the specified priority value will be automatically removed from its old group and assigned to the new group when the configuration is applied.

Each priority value must be assigned to a PGID. Priority values may not be deleted or unassigned. To remove a priority value from a PGID, it must be moved to another PGID.

For PGIDs 0 through 7, bandwidth allocation can also be configured through the ETS Priority Group menu. See for “Allocating Bandwidth” on page 286 for details.

Deleting a Priority GroupA priority group is automatically deleted when it contains no associated priority values, and its bandwidth allocation is set to 0%.Note: The total bandwidth allocated to PGID 0 through 7 must equal exactly 100%. Reducing the bandwidth allocation of any group will require increasing the allocation to one or more of the other groups (see “Allocating Bandwidth” on page 286).

Allocating Bandwidth

Allocated Bandwidth for PGID 0 Through 7

The administrator may allocate a portion of the switch’s available bandwidth to PGIDs 0 through 7. Available bandwidth is defined as the amount of link bandwidth that remains after priorities within PGID 15 are serviced (see “Unlimited Bandwidth for PGID 15” on page 287), and assuming that all PGIDs are fully subscribed. If any PGID does not fully consume its allocated bandwidth, the unused portion is made available to the other priority groups.

Priority group bandwidth allocation can be configured using the following command:

RS 8272(config)# cee global ets prioritygroup pgid <group number (0-7, or 15)> priority <priority list>

RS 8272(config)# cee global ets prioritygroup pgid <group number (0-7, or 15)> priority 0,1,2

RS 8272(config)# cee global ets prioritygroup pgid <priority group number> bandwidth <bandwidth allocation> pgid <priority group number> bandwidth <bandwidth allocation>


where bandwidth allocation represents the percentage of link bandwidth, specified as a number between 10 and 100, in 1% increments, or 0.

The following bandwidth allocation rules apply: Bandwidth allocation must be 0% for any PGID that has no assigned 802.1p pri-

ority values. Any PGID assigned one or more priority values must have a bandwidth allocation

greater than 9%. Total bandwidth allocation for groups 0 through 7 must equal exactly 100%.

Increasing or reducing the bandwidth allocation of any PGID also requires adjusting the allocation of other PGIDs to compensate.

If these conditions are not met, the switch will report an error when applying the configuration.Note: Actual bandwidth used by any specific PGID may vary from configured values by up to 10% of the available bandwidth in accordance with 802.1Qaz ETS standard. For example, a setting of 10% may be served anywhere from 0% to 20% of the available bandwidth at any given time.

Unlimited Bandwidth for PGID 15

PGID 15 is permitted unlimited bandwidth and is generally intended for critical traffic (such as switch management). Traffic in this group is given highest priority and is served before the traffic in any other priority group.

If PGID 15 has low traffic levels, most of the switch’s bandwidth will be available to serve priority groups 0 through 7. However, if PGID 15 consumes a larger part of the switch’s total bandwidth, the amount available to the other groups is reduced.Note: Consider traffic load when assigning priority values to PGID 15. Heavy traffic in this group may restrict the bandwidth available to other groups.

Configuring ETS

Consider an example consistent with that used for port-based PFC configuration (on page 282):

Table 33. ETS Configuration

Priority Usage PGID Bandwidth

0 LAN (best effort delivery)

0 10%1 LAN (best effort delivery)

2 LAN (best effort delivery)

3 SAN (Fibre Channel over Ethernet, with PFC) 1 20%

4 Business Critical LAN (lossless Ethernet, with PFC)

2 30%

5 Latency-sensitive LAN3 40%

6 Latency-sensitive LAN

7 Network Management (strict) 15 unlimited


The example shown in Table 33 is only slightly different than the default configuration shown in Figure 25 on page 284. In this example, latency-sensitive LAN traffic (802.1p priority 5 through 6) are moved from priority group 2 to priority group 3. This leaves Business Critical LAN traffic (802.1p priority 4) in priority group 2 by itself. Also, a new group for network management traffic has been assigned. Finally, the bandwidth allocation for priority groups 1, 2, and 3 are revised.Note: DCBX may be configured to permit sharing or learning PFC configuration with or from external devices. This example assumes that PFC configuration is being performed manually. See “Data Center Bridging Capability Exchange” on page 290 for more information on DCBX.

This example can be configured using the following commands:

1. Turn CEE on.


2. Configure each allocated priority group with a description (optional), list of 802.1p priority values, and bandwidth allocation:

3. Configure the strict priority group with a description (optional) and a list of 802.1p priority values:


RS 8272(config)# cee global ets prioritygroup pgid 0 priority 0,1,2(Select a group for regular LAN, andset for 802.1p priorities 0, 1, and 2)

RS 8272(config)# cee global ets prioritygroup pgid 0 description "Regular LAN" (Set a group description—optional)

RS 8272(config)# cee global ets prioritygroup pgid 1 priority 3(Select a group for SAN traffic, andset for 802.1p priority 3)

RS 8272(config)# cee global ets prioritygroup pgid 1 description "SAN"(Set a group description—optional)

RS 8272(config)# cee global ets prioritygroup pgid 2 priority 4(Select a group for latency traffic,and set for 802.1p priority 4)

RS 8272(config)# cee global ets prioritygroup pgid 2 description "BizCritical LAN" (Set a group description—optional)

RS 8272(config)# cee global ets prioritygroup pgid 3 description "LatencySensitive LAN" (Set a group description—optional)

RS 8272(config)# cee global ets prioritygroup pgid 3 priority 5,6 pgid 0 bandwidth 10 pgid 1 bandwidth 20 pgid 2 bandwidth 30 pgid 3 bandwidth 40 (Configure link bandwidth restriction))

RS 8272(config)# cee global ets prioritygroup pgid 15 priority 7(Select a group for strict traffic, andSet 802.1p priority 7)

RS 8272(config)# cee global ets prioritygroup pgid 15 description "Network Management" (Set a group description—optional)


Note: Priority group 15 is permitted unlimited bandwidth. As such, the commands for priority group 15 do not include bandwidth allocation.


To view the configuration, use the following command:

RS 8272(config)# show cee global ets

Current ETS Configuration:Number of COSq: 8

Current Mapping of 802.1p Priority to Priority Groups:

Priority PGID COSq 0 0 0 1 0 0 2 0 0 3 1 1 4 2 2 5 3 3 6 3 3 7 15 7

Current Bandwidth Allocation to Priority Groups:

PGID PG% Description 0 10 Regular LAN 1 20 SAN 2 30 BizCritical LAN 3 40 Latencysensitive LAN 15 Network Management


Data Center Bridging Capability ExchangeData Center Bridging Capability Exchange (DCBX) protocol is a vital element of CEE. DCBX allows peer CEE devices to exchange information about their advanced capabilities. Using DCBX, neighboring network devices discover their peers, negotiate peer configurations, and detect misconfigurations.

DCBX provides two main functions on the G8272:

Peer information exchangeThe switch uses DCBX to exchange information with connected CEE devices. For normal operation of any FCoE implementation on the G8272, DCBX must remain enabled on all ports participating in FCoE.

Peer configuration negotiationDCBX also allows CEE devices to negotiate with each other for the purpose of automatically configuring advanced CEE features such as PFC, ETS, and (for some CNAs) FIP. The administrator can determine which CEE feature settings on the switch are communicated to and matched by CEE neighbors, and also which CEE feature settings on the switch may be configured by neighbor requirements.

The DCBX feature requires CEE to be turned on (see “Turning CEE On or Off” on page 267).

DCBX Settings

When CEE is turned on, DCBX is enabled for peer information exchange on all ports. For configuration negotiation, the following default settings are configured:

Application Protocol: FCoE and FIP snooping is set for traffic with 802.1p priority 3

PFC: Enabled on 802.1p priority 3

ETS Priority group includes priority values 0 through 2, with bandwidth

allocation of 10% Priority group includes priority value 3, with bandwidth allocation of 50% Priority group includes priority values 4 through 7, with bandwidth

allocation of 40%

Enabling and Disabling DCBX

When CEE is turned on, DCBX can be enabled and disabled on a per-port basis, using the following commands:

When DCBX is enabled on a port, Link Layer Detection Protocol (LLDP) is used to exchange DCBX parameters between CEE peers. Also, the interval for LLDP transmission time is set to one second for the first five initial LLDP transmissions,

RS 8272(config)# [no] cee port <port alias or number> dcbx enable


after which it is returned to the administratively configured value. The minimum delay between consecutive LLDP frames is also set to one second as a DCBX default.

Peer Configuration Negotiation

CEE peer configuration negotiation can be set on a per-port basis for a number of CEE features. For each supported feature, the administrator can configure two independent flags:

The advertise flagWhen this flag is set for a particular feature, the switch settings will be transmit to the remote CEE peer. If the peer is capable of the feature, and willing to accept the G8272 settings, it will be automatically reconfigured to match the switch.

The willing flagSet this flag when required by the remote CEE peer for a particular feature as part of DCBX signaling and support. Although some devices may also expect this flag to indicate that the switch will accept overrides on feature settings, the G8272 retains its configured settings. As a result, the administrator must configure the feature settings on the switch to match those expected by the remote CEE peer.

These flags are available for the following CEE features:

Application ProtocolDCBX exchanges information regarding FCoE and FIP snooping, including the 802.1p priority value used for FCoE traffic. The advertise flag is set or reset using the following command:

The willing flag is set or reset using the following command:

PFCDCBX exchanges information regarding whether PFC is enabled or disabled on the port. The advertise flag is set or reset using the following command:


RS 8272(config)# [no] cee port <port alias or number> dcbx app_proto advertise

RS 8272(config)# [no] cee port <port alias or number> dcbx app_proto willing

RS 8272(config)# [no] cee port <port alias or number> dcbx pfc advertise

RS 8272(config)# [no] cee port <port alias or number> dcbx pfc willing


ETSDCBX exchanges information regarding ETS priority groups, including their 802.1p priority members and bandwidth allocation percentages. The advertise flag is set or reset using the following command:


Configuring DCBX

Consider an example consistent Figure 24 on page 265 and used with the previous FCoE examples in this chapter: FCoE is used on ports 2 and 3. CEE features are also used with LANs on ports 1 and 4. All other ports are disabled or are connected to regular (non-CEE) LAN devices.

In this example, the G8272 acts as the central point for CEE configuration. FCoE-related ports will be configured for advertising CEE capabilities, but not to accept external configuration. Other LAN ports that use CEE features will also be configured to advertise feature settings to remote peers, but not to accept external configuration. DCBX will be disabled on all non-CEE ports.

This example can be configured using the following commands:

1. Turn CEE on.


2. Enable desired DCBX configuration negotiation on FCoE ports:

RS 8272(config)# [no] cee port <port alias or number> dcbx ets advertise

RS 8272(config)# [no] cee port <port alias or number> dcbx ets willing


RS 8272(config)# cee port 2 dcbx enableRS 8272(config)# cee port 2 dcbx app_proto advertiseRS 8272(config)# cee port 2 dcbx ets advertiseRS 8272(config)# cee port 2 dcbx pfc advertise



3. Enable desired DCBX advertisements on other CEE ports:

4. Disable DCBX for each non-CEE port as appropriate:




RS 8272(config)# no cee port 564 dcbx enable


© Copyright Lenovo 2015 Chapter 19: Edge Virtual Bridging 295

Chapter 19. Edge Virtual Bridging

The 802.1Qbg/Edge Virtual Bridging (EVB) is an emerging IEEE standard for allowing networks to become virtual machine (VM)-aware. EVB bridges the gap between physical and virtual network resources. The IEEE 802.1Qbg simplifies network management by providing a standards-based protocol that defines how virtual Ethernet bridges exchange configuration information. In EVB environments, physical end stations, containing multiple virtual end stations, use a bridge to form a LAN. The virtual NIC (vNIC) configuration information of a virtual machine is available to these EVB devices. This information is generally not available to an 802.1Q bridge.

Lenovo Networking OS EVB features are compliant with the IEEE 802.1Qbg Authors Group Draft 0.2. For a list of documents on this feature, see: http://www.ieee802.org/1/pages/802.1bg.html.

The RackSwitch G8272 performs the role of a 802.1Qbg bridge in an EVB environment.

Lenovo N/OS implementation of EVB supports the following protocols:

Virtual Ethernet Bridging (VEB) and Virtual Ethernet Port Aggregator (VEPA): VEB and VEPA are mechanisms for switching between VMs on the same hypervisor. VEB enables switching with the server, either in the software (vSwitch), or in the hardware (using single root I/O virtualization capable NICs). VEPA requires the edge switch to support “Reflective Relay”— an operation where the switch forwards a frame back to the port on which it arrived if the destination MAC address is on the same port.

Edge Control Protocol (ECP): ECP is a transport protocol that operates between two peers over an IEEE 802 LAN. ECP provides reliable, in-order delivery of ULP (Upper Layer Protocol) PDUs (Protocol Data Units).

Virtual Station Interface (VSI) Discovery and Configuration Protocol (VDP): VDP allows hypervisors to advertise VSIs to the physical network. This protocol also allows centralized configuration of network policies that will persist with the VM, independent of its location.

EVB Type-Length-Value (TLV): EVB TLV is a Link Layer Discovery protocol (LLDP)-based TLV used to discover and configure VEPA, ECP, and VDP.


EVB Operations OverviewThe N/OS includes a pre-standards VSI Type Database (VSIDB) implemented through the System Networking Switch Center (SNSC), the Flex System Manager (FSM), or the IBM System Networking Distributed Switch 5000V. The VSIDB is the central repository for defining sets of network policies that apply to VM network ports. You can configure only one VSIDB.Note: This document does not include the VSIDB configuration details. Please see the SNSC, FSM, or IBM System Networking Distributed Switch 5000V guide for details on how to configure VSIDB.

The VSIDB operates in the following sequence:

1. Define VSI types in the VSIDB. The VSIDB exports the database when the G8272 sends a request.

2. Create a VM. Specify VSI type for each VM interface. See the SNSC, FSM, or IBM System Networking Distributed Switch 5000V guide for details on how to specify the VSI type.

The hypervisor sends a VSI ASSOCIATE, which contains the VSI type ID, to the switch port after the VM is started. The switch updates its configuration based on the requested VSI type. The switch configures the per-VM bandwidth using the VMpolicy.

The N/OS supports the following policies for VMs:

ACLs

Bandwidth metering

VSIDB Synchronization

The switch periodically checks for VSIDB changes based on the configured interval. You can configure this interval using the following command:

To disable periodic updates, configure the interval value as 0.

If the switch finds that the VSIDB has changed, it updates the local VSIDB cache. When the cache is successfully updated, it sends a syslog message.

After updating the local VSIDB cache, the switch disassociates any VM whose type ID or VLAN no longer exists in the updated cache.

The switch updates the local VSIDB cache when any of the following takes place:

When, at the configured refresh interval, the switch finds that the VSIDB configuration has changed since the last poll.

When a VM sends an ASSOCIATE message, but the VSI type does not exist in the local VSIDB cache.

When a VM sends an ASSOCIATE message, and the VSI type exists but the VSI type’s VLAN ID does not exist in the local VSIDB cache.

RS 8272(config)# virt evb vsidb <number>RS 8272(confvsidb)# updateinterval <time in seconds>


When you update the VSIDB using the following command:RS 8272# virt evb update vsidb <number>

When the management port link status changes from down to up

VLAN Behavior

When a VM gets associated, the corresponding VLAN is dynamically created on the switch port if the VLAN does not already exist.

VLANs that are dynamically created will be automatically removed from the switch port when there are no VMs using that VLAN on the port.

Dynamic VLAN information will not be displayed in the running configuration. However, the VLAN, port, and STP commands display the dynamic VLAN information with a “*”.

If you configure any Layer 2/Layer 3 features on dynamically created VLANs, the VLAN information is displayed in the running configuration.

Deleting a VLAN

If you delete a VLAN that has a VM associated with it, you will see a warning message similar to the following:

The VMs will not get disassociated.

If a VM is associated with a port, and you remove this port from a VLAN, you will see a warning message similar to the following:

The VMs will not get disassociated.

Manual Reflective Relay

Reflective Relay (RR) is an operation where the switch forwards a frame back to the port on which it arrived if the destination MAC address is on the same port. When an EVB profile is configured on a port, RR is automatically enabled on the port after capability exchange with the peer, using the IEEE802.1QBG protocol. This is the usual mode of operation.

When the switch interoperates with devices that do not support IEEE 802.1QBG protocols, RR can be manually configured using the following command:

Manual RR and EVB profile cannot be configured on a port at the same time.

Warning: Vlan 10 is used by VM and can't be removed.

Warning: Port 23 in Vlan 10 is used by VM and can't be removed.

RS 8272(configif)# reflectiverelay force enable


VSIDB - IPv6 Support

The VSIDB manager can be configured with an IPv4 or IPv6 address. Use the following command to configure the VSIDB manager IP address:

RS 8272(config)# virt evb vsidb 1RS 8272(conf-vsidb)# host <IPv4 or IPv6 address> (Set VSI database Manager IP)


EVB ConfigurationThis section includes the steps to configure EVB based on the following values:

Profile number: 1

Port number: 1

Retry interval: 8000 milliseconds

VSI Database: Manager IP: 172.31.37.187 Port: 80

Note: VSI Database can be accessed via HTTP or HTTPS. The manager IP can be configured with an IPv4 or IPv6 address.

1. Create an EVB profile.

2. Enable Reflective Relay.

3. Enable VSI discovery.

4. Add EVB profile to port.

Note: This port must be a server port (RS 8272(config)# system serverports port <port number>)

5. Configure ECP retransmission interval.

6. Set VSI database information.

RS 8272(config)# virt evb profile 1 (Enter number from 1-16)

RS 8272(confevbprof)# reflectiverelay

RS 8272(confevbprof)# vsidiscoveryRS 8272(conf-evbprof)# exit

RS 8272(config)# interface port 1RS 8272(config-if)# evb profile 1 (Enter EVB profile ID)RS 8272(configif)# exit

RS 8272(config)# ecp retransmitinterval 8000 (Enter retransmission interval in milliseconds (100-9000)

RS 8272(config)# virt evb vsidb 1RS 8272(confvsidb)# host 172.31.37.187 (Set VSI database Manager IP)RS 8272(confvsidb)# port 80 (Set VSI database Manager port)RS 8272(confvsidb)# filepath “vsidb” (Set VSI database document path)RS 8272(confvsidb)# filename “all.xml”(Set VSI database file name)RS 8272(confvsidb)# updateinterval 30(Set update interval in seconds) RS 8272(confvsidb)# exit


Note: When you connect to a SNSC VSIDB, the port/docpath configuration is as follows:

HTTP:

Port: 40080

Docpath: snsc/rest/vsitypes

HTTPS:

Port: 40443

Docpath: snsc/rest/vsitypes

When you connect to a 5000v VSIDB, the port/docpath configuration is as follows:

Port: 80

Docpath: vsitypes

7. Enable LLDP.

RS 8272(config)# lldp enable (Turn on LLDP)


Limitations If both ACL and egress bandwidth metering are enabled, traffic will first be

matched with the ACL and will not be limited by bandwidth metering.

ACLs based on a source MAC or VLAN must match the source MAC and VLAN of the VM. If not, the policy will be ignored and you will see the following warning message:

Unsupported featuresThe following features are not supported with EVB:

LAG/VLAG

vNIC

"vm: VSI Type ID 100 Associated mac 00:50:56:b6:c0:ff on port 6, ignore 1 mismatched ACL"


© Copyright Lenovo 2015 Chapter 20: Static Multicast ARP 303

Chapter 20. Static Multicast ARP

The Microsoft Windows operating system includes the Network Load Balancing (NLB) technology that helps to balance incoming IP traffic among multi-node clusters. In multicast mode, NLB uses a shared multicast MAC address with a unicast IP address. Since the address resolution protocol (ARP) can map an IP address to only one MAC address, port, and VLAN, the packet reaches only one of the servers (the one attached to the port on which the ARP was learnt).

To avoid the ARP resolution, you must create a static ARP entry with multicast MAC address. You must also specify the list of ports through which the multicast packet must be sent out from the gateway or Layer 2/Layer 3 node.

With these configurations, a packet with a unicast IPv4 destination address and multicast MAC address can be sent out as per the multicast MAC address configuration. NLB maps the unicast IP address and multicast MAC address as follows:

Cluster multicast MAC address: 03-BF-W-X-Y-Z; where W.X.Y.Z is the cluster unicast IP address.

You must configure the static multicast ARP entry only at the Layer 2/Layer 3 or Router node, and not at the Layer 2-only node.

Lenovo Networking OS supports a maximum of 20 static multicast ARP entries.Note: If you use the ACL profile, an ACL entry is consumed for each Static Multicast ARP entry that you configure. Hence, you can configure a maximum of 896 ACLs and multicast MAC entries together when using the ACL profile.The ACL entries have a higher priority. In the default profile, the number of static multicast ARP entries that you configure does not affect the total number of ACL entries.


Configuring Static Multicast ARPTo configure multicast MAC ARP, you must perform the following steps:

Configure the static multicast forwarding database (FDB) entry: Since there is no port list specified for static multicast ARP, and the associated MAC address is multicast, you must specify a static multicast FDB entry for the cluster MAC address to limit the multicast domain. If there is no static multicast FDB entry defined for the cluster MAC address, traffic will not be forwarded. Use the following command:

Configure the static multicast ARP entry: Multicast ARP static entries should be configured without specifying the list of ports to be used. Use the following command:


Consider the following example:

Cluster unicast IP address: 10.10.10.42

Cluster multicast MAC address: 03:bf:0A:0A:0A:2A

Cluster VLAN: 42

List of individual or port trunks to which traffic should be forwarded: 54 and 56

Following are the steps to configure the static multicast ARP based on the given example:

1. Configure the static multicast FDB entry.

2. Configure the static multicast ARP entry:

You can verify the configuration using the following commands:

Verify static multicast FDB entry:

RS 8272(config)# macaddresstable multicast <cluster MAC address> <port(s)>

RS 8272(config)# ip arp <destination unicast IP address> <destination multicast MAC address> vlan <cluster VLAN number>

RS 8272(config)# macaddresstable multicast 03:bf:0A:0A:0A:2A 42 54,56

RS 8272(config)# ip arp 10.10.10.42 03:bf:0A:0A:0A:2A vlan 42

RS 8272(config)# show macaddresstable multicast address 03:bf:0A:0A:0A:2A

Multicast Address VLAN Port(s) 03:bf:0A:0A:0A:2A 42 54 56

© Copyright Lenovo 2015 Chapter 20: Static Multicast ARP 305

Verify static multicast ARP entry:

Limitations You must configure the ARP only in the Layer 2/Layer 3 node or the router node

but not in the Layer 2-only node. Lenovo N/OS cannot validate if the node is Layer 2-only.

The packet is always forwarded to all the ports as specified in the Multicast MAC address configuration. If VLAN membership changes for the ports, you must update this static multicast MAC entry. If not, the ports, whose membership has changed, will report discards.

ACLs take precedence over static multicast ARP. If an ACL is configured to match and permit ingress of unicast traffic, the traffic will be forwarded based on the ACL rule, and the static multicast ARP will be ignored.

RS 8272(config)# show ip arp

Current ARP configuration: rearp 5Current static ARP: ip mac port vlan 10.10.10.42 03:bf:0A:0A:0A:2A 42Total number of arp entries : 2 IP address Flags MAC address VLAN Age Port 10.10.10.1 P fc:cf:62:9d:74:00 42 10.10.10.42 P 03:bf:0A:0A:0A:2A 42 0


© Copyright Lenovo 2015 Chapter 21: Unified Fabric Port 307

Chapter 21. Unified Fabric Port

Unified Fabric Port (UFP) is a cost-effective way to allocate, share and dynamically control network bandwidth between a server and a switch. UFP lets you create multiple virtual connections. The UFP protocol is a link-level protocol that runs a separate instance for each physical communication link established between a server NIC and a switch port. Virtualizing the ports allows you to separate or aggregate port traffic by applying the network policies defined on the switch. Virtualization lessens bottlenecks and provides higher bandwidth while consolidating equipment use.

UFP provides a switch fabric component to control NICs. The server operating system (OS) or hypervisor recognizes each subdivided link (channel) as an independent physical NIC. Each channel has a unique identity and profile that defines its properties and functionality. The server communicates with the switch over the channel as defined in the channel profile. The channels share the high-speed physical link bandwidth.

For each channel, the vNIC on the server side communicates with virtual port on the switch side.

Figure 26. UFP vPorts

The UFP protocol has the following operation categories:

Channel Initialization: The server NIC and the switch port negotiate the number of channels and establish channel identifiers. Each UFP channel has a data component and a control component. The two components have the same UFP channel ID.

Channel Control: For an established channel, the switch can modify configurable channel properties by sending a control message on the UFP channel. While the channel ID is the same for the control and data components, the destination MAC address of the control message frame is the well-known address “01-80-C2-00-00-03”.

Discovery Capability: UFP can discover other ports that are UFP enabled. Once you enable UFP, you can check the information statistics for established channels.

NIC

OS or

Hypervisor

Top of Rack Server

Lenovo

Switch VNIC

VNIC

VNIC

VNIC

PhysicalNIC Port vPort

vPort

vPort

vPort

ServerSwitch Port


UFP LimitationsThe following limitations apply when configuring UFP:

FCoE must be configured only on vPort 2 of the physical NIC.

UFP port in FCoE mode cannot operate with FIP auto-VLAN feature.

VLANs that have member vPorts configured in trunk-, access-, or auto-modes cannot have member vPorts configured in tunnel mode or FCoE.

vPorts on a physical port must be members of separate VLANs.

VLANs 4002-4005 are reserved for outer tagging.

A UFP-enabled port with no vPorts configured cannot belong to the same VLAN as a UFP-enabled port that has vPorts configured in trunk, access, or auto modes.

UFP bandwidth is guaranteed lossless only for unicast traffic.

VMready is supported only on a vPort which is configured in auto-VLAN mode. When a vPort is in auto-VLAN mode, it can support up to 32 VMGroups.

EVB is supported only on a vPort which is configured in auto-VLAN mode.

VMready and EVB cannot be configured on the same physical port.

UFP vPorts can support up to 1024 VLANs.

When CEE is turned on, FCoE vPort must be used for lossless priority traffic. For loss-tolerant priority traffic, a non-FCoE UFP vPort must be used. The lossless property of FCoE vPort is not guaranteed, if lossless and loss-tolerant traffic are combined.

When the vPort is enabled and the channel link state is up, the system does not support changing vPort VLAN type from private/non-private to non-private/private.

A maximum of four vPorts can be configured for each physical switch port.

VMReady Local Group configuration is not supported by UFP.


Virtual Ports ModesA single physical switch port is configured with virtual ports (vPorts). Each UFP channel connects the server vNIC with a switch vPort. Properties that are defined for a vPort, such as native VLAN and bandwidth, are applied to the traffic that belongs to the vPort.Note: A maximum of four vPorts can be configured for each physical switch port.

vPort-S-Tag Mapping A vPort can also be identified with an S-tag (service tag or outer tag). When a vPort is initialized, the switch communicates the UFP channel ID of the vPort to the server vNIC. When the server NIC or switch transmit frames, they add this S-tag to indicate the vPort or vNIC to which the packet is being transmitted. No VLAN mapping is required. Such packets can be single tagged or double tagged (with S-tag).

vPort-VLAN MappingIn local domain data path type, the switch and server identify the vPort and vNIC by the port and VLAN tag in the incoming and outgoing packets. Because no two vPorts carry traffic for the same VLAN, the port-and-VLAN combination must be uniquely mapped to a vPort.

UFP vPort ModeThe UFP mode is configured based on the type of switching domain (single VLAN or multiple VLANs) where the vPort is connected.

Use local domain data path types for trunk or access mode.

Use pass-through domain data path types for tunnel mode. In tunnel mode, a vPort can belong to only one VLAN.

Use the following command to configure UFP vPort mode:

Tunnel Mode

In tunnel mode, a vPort can belong to only one VLAN. An outer tag with the vPort’s VLAN ID is inserted in packets that egress the vPort. The inner VLAN tag remains unchanged. The switch processes packets based on the outer tag. When all the ports or vPorts that belong to a particular VLAN are placed in tunnel mode, they belong to one pass-through domain.

Use tunnel mode to send all VM data traffic to an upstream switch, for Layer 2 or Layer 3 processing, in one domain. In such cases, the UFP port or vPort must be in tunnel mode and the upstream switch port must be in 802.1Q trunk mode.Note: Two vPorts on a physical port cannot be members of the same VLAN.

RS 8272(config)# ufp port <num> vport <num>RS 8272(config_ufp_vport)# network mode access|trunk|auto|tunnel|fcoe

Default mode is ‘tunnel’


Figure 27. Packet pass-through in Tunnel Mode

802.1Q Trunk Mode

In trunk mode, a vPort can carry packets that have inner tags that belong to up to 1024 VLANs. A maximum of 4089 VLANs for all UFP vPorts can be configured on the switch in stand-alone mode. Each VLAN in the inner tag requires a VLAN translation entry.Note: Two vPorts operating in trunk mode on the same physical port cannot carry the same set of VLANs in the inner tag.

Figure 28. Packet passing through in Trunk Mode

Access Mode

In access mode, a vPort carries packets with inner tags that belong to one VLAN. The vPort is associated with the VLAN defined by the command:

Note: VLANs 4002-4005 are reserved for outer tagging.

OutboundPacket

InboundPacket

RegularVLAN ID NIC attaches UFP

Channel VLAN ID

Switch adds outerChannel VLAN ID

Outer tag sets vNIC;NIC strips outer tag

Switching uses outer tag;Ignores regular VLAN

Switching uses outer tag;Ignores regular VLAN

Switch stripsouter tag

Server Lenovo Switch Ports withoutvNICs

vNICsOS/Hypervisor NIC

vPorts

OutboundPacket

RegularVLAN IDs NIC attaches UFP

Channel VLAN IDSwitch strips

outer tag

Server Lenovo Switch Ports withoutvNICs

vNICOS/Hypervisor NIC

vPort

VLAN Translation

VLAN Classification

RS 8272(config_ufp_vport)# network defaultvlan <2-4094>


FCoE Mode

FCoE traffic is carried by a vPort. The server-side endpoint of this virtual port will be represented through a FC vHBA. Setting a virtual port in FCoE mode will enable Priority-based Flow Control (PFC) on the physical port.

A vPort configured in FCoE mode can only be attached to a Fibre Channel (FC) VLAN. Only vPort 2 on a physical port can be configured in FCoE mode. A vPort in FCoE mode operates as a local domain data path type with packets being single tagged.

Auto-VLAN Mode

When a vPort is configured in auto-VLAN mode, the vPort participates in VM discovery using VMready or 802.1Qbg. VLANs are dynamically provisioned based on VMready discovery or 802.1Qbg VM association.

When a vPort operates in auto-VLAN mode, it supports 32 VM groups. In the case of 802.1Qbg, when a vPort operates in auto-VLAN mode, the maximum number of VLANs in the inner tag are 1024. The vPort cannot be configured in Virtual Ethernet Port Aggregator (VEPA) mode.


UFP Bandwidth ProvisioningUFP provides one mode of bandwidth provisioning for vPort: Strict Bandwidth Provisioning Mode.

UFP Strict Bandwidth Provisioning Mode

Strict bandwidth provisioning mode configures the switch and NIC apply bidirectional bandwidth control on the vPort as per the defined configuration. By default, a bandwidth of 2.5 Gbps per vPort is guaranteed. If other vPorts are idle, the bandwidth of a vPort can be up to 10 Gbps. A minimum bandwidth of 1 Gbps is provisioned, which can be raised by 100 Mbps increments. The sum of the minimum bandwidth guaranteed for all vPorts together cannot exceed the capacity of the physical link. A vPort can also be configured with a maximum bandwidth.

This mode works with the port scheduler to avoid unintended packet drops due to policing through EFP metering block. If flow control is enabled, the switch provides a no-drop packet forwarding behavior, which improves end-to-end TCP-throughput performance. Note: If a vPort is configured with low upper limit, it might lead to head-of-line congestion on the egress port.

By default, uplink ports have a separate traffic class for storage traffic with guaranteed bandwidth. The rest of the bandwidth is shared equally among other traffic.

Use the following command to configure strict bandwidth provisioning:

RS 8272(config_ufp_vport)# qos bandwidth max|min <10-100>

min Set minimum guaranteed bandwidthmax Set maximum allowed bandwidth


Using UFP with Other RackSwitch G8272 FeaturesUFP works with other G8272 features, as described with limitations and details.

Layer 2 Failover

UFP failover can be configured with manual monitoring.

Layer 2 failover is not supported on UFP ports in auto mode.

For more information on failover, see “Layer 2 Failover” on page 495.

For an example configuration, see “Example 6: Layer 2 Failover Configuration” on page 320.

Increased VLAN Limits

Configured with UFP and VLANs, a vPort can support a maximum of 1024 VLANs. A UFP port supports 1024 VLANs.

For more information on VLAN configuration, see “VLANs” on page 117.

VMReady

Configuring with UFP and VMReady, the G8272 can support up to 32 VMGroups with UFP vPorts in auto-mode.

VMReady is supported only on a vPort which is configured in auto-VLAN mode.

For more information on VMReady, see “VMready” on page 239.

802.1Qbg

Configured with Edge Virtual Bridging (EVB), UFP supports up to 1024 VLANs on a vPort.

EVB is supported only on a vPort which is configured in auto-VLAN mode.

For more information on EVB, see “Edge Virtual Bridging” on page 295.


UFP Configuration ExamplesFollowing is an example configuration of UFP vPorts in access mode.

Example 1: Access Mode

1. Configure port 1 as a UFP server port.

2. Turn on UFP.

3. Configure port 1 as UFP.

4. Configure virtual port.

5. Configure vPort access mode.

6. Configure vPort default VLAN.

7. Ensure tagging is disabled on vPort.

8. Specify QoS parameters for the vPort.

9. Enable the vPort.

G8272(config)# system serverports port 1

G8272(config)# ufp enable

G8272(config)# ufp port 1 enable

Warning: "Tagging/Trunkmode" is enabled on UFP port 1

G8272(config)# ufp port 1 vport 1

G8272(config_ufp_vport)# network mode access

G8272(config_ufp_vport)# network defaultvlan 100

G8272(config_ufp_vport)# no network defaulttag

G8272(config_ufp_vport)# qos bandwidth min 25 (in percentage)G8272(config_ufp_vport)# qos bandwidth max 100 (in percentage)

G8272(config_ufp_vport)# enableG8272(config_ufp_vport)# exit


10. Configure PVID/Native VLAN for port 2.

Note: Port 2 must be an upstream port.

Example 2: Trunk Mode

Following is an example configuration of UFP vPorts in trunk mode.

1. Configure ports 1 and 2 as UFP server ports.

2. Turn on UFP.



5. Configure vPort trunk mode.




G8272(config)# interface port 2G8272(configif)# switchport mode accessG8272(configif)# switchport access vlan 100

G8272(config)# system serverports port 1,2





G8272(config_ufp_vport)# network mode trunk







11. Configure vPort trunk mode.





16. Enable tagging/trunk mode on port 3.

17. Configure VLAN 100 parameters.




G8272(config_ufp_vport)# network mode trunk





G8272(config)# interface port 3G8272(configif)# switchport mode trunkG8272(configif)# switchport trunk native vlan 100G8272(configif)# switchport trunk allowed vlan add 200,300G8272(configif)# exit

G8272(config)# vlan 100G8272(configvlan)# vmember 1.1G8272(configvlan)# vmember 2.3G8272(configvlan)# exit




Example 3: Auto-VLAN Mode


2. Turn on UFP.




6. Configure vPort auto mode.

Note: VLAN is dynamically added by 802.1Qbg.










G8272(config_ufp_vport)# network mode auto




Example 4: Tunnel Mode

Following is an example configuration of UFP vPorts in tunnel mode.


2. Turn on UFP.

3. Configure port as UFP.


5. Configure vPort tunnel mode.





10. Configure tagging on port 2.







G8272(config_ufp_vport)# network mode tunnel






Note: Port 2 must be an upstream port.

Example 5: FCoE Mode

Following is an example configuration of UFP vPorts in FCoE mode.


2. Enable CEE.

3. Enable FIPs.

4. Turn on UFP.

5. Configure port as UFP.


7. Configure vPort FCoE mode.



G8272(config)# interface port 2G8272(configif)# tagpvidingressG8272(configif)# no vlan dot1q tag native G8272(configif)# switchport access vlan 4000G8272(configif)# exit


G8272(config)# cee enable

G8272(config)# fcoe fips enable

RS 8272(config)# ufp enable




G8272(config_ufp_vport)# network mode fcoe







13. Enable tagging/trunk mode on port.

Note: Port 2 is connected to the upstream FCF.

Example 6: Layer 2 Failover Configuration

While configuring a failover trigger, you cannot use the member command for a physical port that has vPorts configured. Instead, you must use the vmember command to add the vPorts as members of a failover trigger. The following example includes the commands to configure a failover trigger using a physical port 8 (a non-UFP port) and port 9 (a UFP-enabled port with vPorts 9.1, 9.2, 9.3, and 9.4).

See “Example 1: Access Mode” on page 314 for steps to configure a vPort in access mode. Follow the steps below for configuring the failover trigger:

1. Enable failover globally:

2. Configure trigger 1 and add monitor and control ports:

Note: If you try to add a physical port (that has vPorts configured) with the “member” attribute as a member of a trigger (as opposed to the attribute “vmember”), you may see the following error message when you enable the trigger:

G8272(config)#failover trigger 1 ena

Failover Error: trigger 1 physical port 9 has virtual ports.


G8272(config_ufp_vport)# system serverports port 1


G8272(config)# interface port 2G8272(configif)# switchport mode trunkG8272(configif)# switchport trunk native vlan 1G8272(configif)# switchport trunk allowed vlan add 1102G8272(configif)# exit

G8272(config)# failover enable

G8272(config)# failover trigger 1 mmon monitor member 5G8272(config)# failover trigger 1 mmon control member 8G8272(config)# failover trigger 1 mmon control vmember 9.1,9.2,9.3,9.4


3. Enable failover trigger:

G8272(config)# failover trigger 1 enable



Part 5: IP RoutingThis section discusses Layer 3 switching functions. In addition to switching traffic at near line rates, the application switch can perform multi-protocol routing. This section discusses basic routing and advanced routing protocols:

Basic Routing

Policy-Based Routing

Routed Ports

IPv6 Host Management

Routing Information Protocol (RIP)

Internet Group Management Protocol (IGMP)

Border Gateway Protocol (BGP)

Open Shortest Path First (OSPF)

Service Location Protocol (SLP)

Protocol Independent Multicast (PIM)



Chapter 22. Basic IP Routing

This chapter provides configuration background and examples for using the G8272 to perform IP routing functions. The following topics are addressed in this chapter:

“IP Routing Benefits” on page 326

“Routing Between IP Subnets” on page 326

“Example of Subnet Routing” on page 327

“ARP - Local Proxy” on page 331

“Network Address Translation” on page 332

“ECMP Static Routes” on page 337

“Dynamic Host Configuration Protocol” on page 339


IP Routing BenefitsThe switch uses a combination of configurable IP switch interfaces and IP routing options. The switch IP routing capabilities provide the following benefits:

Connects the server IP subnets to the rest of the backbone network.

Provides the ability to route IP traffic between multiple Virtual Local Area Networks (VLANs) configured on the switch.

Routing Between IP SubnetsThe physical layout of most corporate networks has evolved over time. Classic hub/router topologies have given way to faster switched topologies, particularly now that switches are increasingly intelligent. The G8272 is intelligent and fast enough to perform routing functions at wire speed.

The combination of faster routing and switching in a single device allows you to build versatile topologies that account for legacy configurations.

For example, consider a corporate campus that has migrated from a router-centric topology to a faster, more powerful, switch-based topology. As is often the case, the legacy of network growth and redesign has left the system with a mix of illogically distributed subnets.

This is a situation that switching alone cannot cure. Instead, the router is flooded with cross-subnet communication. This compromises efficiency in two ways:

Routers can be slower than switches. The cross-subnet side trip from the switch to the router and back again adds two hops for the data, slowing throughput considerably.

Traffic to the router increases, increasing congestion.

Even if every end-station could be moved to better logical subnets (a daunting task), competition for access to common server pools on different subnets still burdens the routers.

This problem is solved by using switches with built-in IP routing capabilities. Cross-subnet LAN traffic can now be routed within the switches with wire speed switching performance. This eases the load on the router and saves the network administrators from reconfiguring every end-station with new IP addresses.

© Copyright Lenovo 2015 Chapter 22: Basic IP Routing 327

Example of Subnet RoutingConsider the role of the G8272 in the following configuration example:

Figure 29. Switch-Based Routing Topology

The switch connects the Gigabit Ethernet and Fast Ethernet trunks from various switched subnets throughout one building. Common servers are placed on another subnet attached to the switch. A primary and backup router are attached to the switch on yet another subnet.

Without Layer 3 IP routing on the switch, cross-subnet communication is relayed to the default gateway (in this case, the router) for the next level of routing intelligence. The router fills in the necessary address information and sends the data back to the switch, which then relays the packet to the proper destination subnet using Layer 2 switching.

With Layer 3 IP routing in place on the switch, routing between different IP subnets can be accomplished entirely within the switch. This leaves the routers free to handle inbound and outbound traffic for this group of subnets.

Default router:205.21.17.1

Server subnet 1:100.20.10.2-254

Server subnet 2:131.15.15.2-254

Server subnet 3:206.30.15.2-254

IF 1VLAN 1

IF 2VLAN 2

IF 3VLAN 3

IF 4VLAN 4


Using VLANs to Segregate Broadcast Domains

If you want to control the broadcasts on your network, use VLANs to create distinct broadcast domains. Create one VLAN for each server subnet, and one for the router.


This section describes the steps used to configure the example topology shown in Figure 29 on page 327.

1. Assign an IP address (or document the existing one) for each router and each server.

The following IP addresses are used:

2. Assign an IP interface for each subnet attached to the switch.

Since there are four IP subnets connected to the switch, four IP interfaces are needed:

3. Determine which switch ports and IP interfaces belong to which VLANs.

The following table adds port and VLAN information:

Table 34. Subnet Routing Example: IP Address Assignments

Subnet Devices IP Addresses

1 Default router 205.21.17.1

2 Web servers 100.20.10.2-254

3 Database servers 131.15.15.2-254

4 Terminal Servers 206.30.15.2-254

Table 35. Subnet Routing Example: IP Interface Assignments

Interface Devices IP Interface Address

IF 1 Default router 205.21.17.3

IF 2 Web servers 100.20.10.1

IF 3 Database servers 131.15.15.1

IF 4 Terminal Servers 206.30.15.1

Table 36. Subnet Routing Example: Optional VLAN Ports

Devices IP Interface Switch Ports VLAN #

Default router 1 22 1

Web servers 2 1 and 2 2

Database servers 3 3 and 4 3

Terminal Servers 4 5 and 6 4


Note: To perform this configuration, you must be connected to the switch Command Line Interface (CLI) as the administrator.

4. Add the switch ports to their respective VLANs.

The VLANs shown in Table 36 are configured as follows:

Each time you add a port to a VLAN, you may get the following prompt:


RS 8272(config)# interface port 22 (Add ports to VLAN 1)RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 1RS 8272(configif)# exit


RS 8272(config)# interface port 1,2 (Add ports to VLAN 2)RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit





Port 4 is an untagged port and its PVID is changed from 1 to 3.


5. Assign a VLAN to each IP interface.

Now that the ports are separated into VLANs, the VLANs are assigned to the appropriate IP interface for each subnet. From Table 36 on page 328, the settings are made as follows:

6. Configure the default gateway to the routers’ addresses.

The default gateway allows the switch to send outbound traffic to the router:

7. Enable IP routing.


Examine the resulting information. If any settings are incorrect, make the appropriate changes.

RS 8272(config)# interface ip 1 (Select IP interface 1)RS 8272(configipif)# ip address 205.21.17.3RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 1 (Add VLAN 1)RS 8272(configipif)# enableRS 8272(configvlan)# exitRS 8272(config)# interface ip 2 (Select IP interface 2)RS 8272(configipif)# ip address 100.20.10.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 2 (Add VLAN 2)RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 3 (Select IP interface 3)RS 8272(configipif)# ip address 131.15.15.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 3 (Add VLAN 3)RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 4 (Select IP interface 4)RS 8272(configipif)# ip address 206.30.15.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 4 (Add VLAN 4)RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway 1 address 205.21.17.1RS 8272(config)# ip gateway 1 enable

RS 8272(config)# ip routing

RS 8272(config)# show vlanRS 8272(config)# show interface informationRS 8272(config)# show interface ip


ARP - Local ProxyAn IP interface or a routed port that has local proxy ARP enabled allows the RackSwitch G8272 to respond to all ARP requests for IP addresses within the subnetwork, and to forward all traffic between hosts in the subnetwork. This feature is useful when hosts in a subnetwork are separated at Layer 2 with features such as Private VLAN. After responding to an ARP request, the G8272 sends an ARP request to the destination host for creating an ARP entry, if such an entry does not already exist in the ARP cache. If VRRP is enabled, the G8272 uses the virtual router MAC address of the master in the ARP response. If VRRP is not enabled, the G8272 uses the switch base MAC address.

When local proxy ARP is enabled on an interface, ICMP redirects must be disabled globally.

This feature can be enabled using the following commands:

On an IP interface:

On a routed port:

For more information on routed ports, see Chapter 24, “Routed Ports”.

RS 8272(config-ip-if)# ip local-proxy-arp

RS 8272(config-if)# ip local-proxy-arp


Network Address TranslationAnother way to circumvent using an upstream router, this time for communication between local subnets and the rest of the backbone network, is to use the G8272’s integrated Network Address Translation (NAT) functionality. NAT changes the IP addresses inside packets as they pass between different IP address spaces or realms, based on predefined mappings.

Network addresses can be segregated into two realms: the inside realm and the outside realm. This is a naming convention originating from the prevailing use case, where NAT is used to connect an internal address realm with private unregistered addresses to an external realm with globally unique registered addresses. Technically, however, the two realms are symmetrical. It is possible, for example, to define a LAN in the outside realm and the backbone network in the inside realm.

Network addresses are classified as follows:

Inside Realm (local IPs) inside local IP – the configured IP address of the inside host. All hosts from

the inside realm can access the inside local address if they have a route to it. outside local IP – the IP address of an outside host as it appears in the inside

realm. Hosts in the inside realm use the outside local address when sending packets to a host in the outside realm.

Outside Realm (global IPs) inside global IP – the IP address of the inside host as it appears in the outside

realm. Hosts in the outside realm use the inside global address as destination when sending packets to a host in the inside realm.

outside global IP – the configured IP address of the outside host.

Figure 30. NAT Address Mapping

When an IP packet passes from the inside realm to the outside realm, its original source IP is the inside local IP and the destination IP is the outside local IP. NAT can replace both the source (SNAT) and destination (DNAT) IP addresses as follows:

SNAT – The inside local IP is replaced with the inside global IP

DNAT – The outside local IP is replaced with the outside global IP

When an IP packet arrives from the outside realm to the inside realm, the following network address translations are applied:

SNAT – The outside global IP is replaced with the outside local IP

Inside

Network

Outside

Network

Inside Realm Outside Realm

NAT Router

Inside

Local IP

Outside

Local IP

Inside

Global IP

Outside

Global IP


DNAT – The inside global IP is replaced with the inside local IP

By default, IP interfaces do not participate in NAT. To configure an interface as part of the inside realm or outside realm, use the following commands:

To exclude the interface from NAT, revert it to the default state:

Notes:

All IP interfaces defined on the same VLAN or on VLANs participating in the same realm (either inside, outside or default) must be configured as members of the same realm. Setting an interface as part of a realm will automatically add all the interfaces in the VLAN to the respective realm. Reverting an interface to the default state, will automatically revert all interfaces in the VLAN to default.

Setting up NAT on the switch’s management IP or on IP addresses used for routing protocols may compromise your setup.

Static NAT

Static NAT allows one-to-one translations of the local IP addresses to the global IP addresses or of the global IP address to the local IP address.

To set up NAT for traffic passing from the inside realm to the outside realm, use the following commands:

For traffic passing from the outside realm to the inside realm, use the following commands:

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# ip nat inside|outside

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# ip nat default

RS 8272(config)# ip nat inside source static <inside local IP> <inside global IP> (SNAT)

RS 8272(config)# ip nat inside destination static <outside local IP> <outside

global IP> (DNAT)

RS 8272(config)# ip nat outside source static <outside global IP> <outside local IP>

(SNAT)RS 8272(config)# ip nat outside destination static <inside global IP> <inside local IP>

(DNAT)


Unidirectional NAT TranslationBy default, static NAT rules create mappings that permit translations for bidirectional flows. A static inside SNAT rule for instance, in addition to the inside local IP to inside global IP mapping for outgoing traffic, will also create a corresponding inside global IP to inside local IP mapping for incoming traffic. In other words:

An inside SNAT also creates an outside DNAT

An outside DNAT also creates an inside SNAT

An outside SNAT also creates an inside DNAT

An inside DNAT also creates an outside SNAT

Figure 31. SNAT – DNAT Equivalence

To cancel these secondary mappings, use the one-way parameter at the end of the static NAT commands:

Network Address Port TranslationNetwork Address Port Translation (NAPT) allows NAT to isolate specific traffic streams by translating socket addresses (both the IP address and port number) instead of only the IP addresses. NAPT also enables port forwarding.

To set up NAPT for a static inside SNAT for instance, use the following command:

Dynamic NAT

Dynamic NAT allows mapping pools of multiple IPs in one rule, instead of individual IP network addresses. Dynamic NAT acts similarly to Static NAT, except that the entries are only temporarily added to hardware when a packet matches the translation rule and age out after a predefined time-out interval.

RS 8272(config)# ip nat inside source static <inside local IP> <inside global IP> oneway

Inside

Network

Outside

Network

Inside Realm Outside Realm

NAT Router

Inside

Local IP

Outside

Local IP

Inside

Global IP

Outside

Global IP

SNAT SNAT

DNAT DNAT

RS 8272(config)# ip nat inside source static tcp|udp <inside local IP> <local TCP/UDP port> <inside global IP> <global TCP/UDP port>


Up to 1000 IP address pools can be defined. To create IP address pools, use the following command:

Once the IP address pools are defined, you can configure a dynamic NAT:

Notes:

The overload parameter is redundant, and used only for Cisco compatibility.

The translation-pool maps only the first IP address in the range. The parameter is defined as a pool for compatibility reasons.

Because of how the dynamic rules are defined, inside dynamic rules only allow inside nodes to initiate communication with outside nodes. Likewise, outside dynamic rules allow only outside nodes to initiate communication with inside nodes. Port forwarding can be used to circumvent this behavior and allow outside nodes to initiate communication with inside nodes based on inside dynamic rules, and inside nodes to initiate communication with outside nodes based on outside dynamic rules.

Match pools cannot overlap between NAT rules. Translation pools can. It is possible, for instance, to set up two different IP ranges to translate to the same IP address.

If a static and a dynamic rule overlap, the NAT defined in the static rule will take precedence.

NAT Proxy ARP

ARP requests from inside nodes to outside nodes will be addressed to the outside nodes’ locally translated IPs (outside local IPs). Likewise, ARP requests from outside nodes to inside nodes will be addressed to the inside global IPs. To enable/disable the switch from replying to these ARP requests for outside local IPs and inside global IPs, use the following command:

Global NAT Settings

To globally turn NAT on and off without erasing the current NAT configuration, use the following commands:

To set up the time-out in seconds for dynamic NAT rules:

RS 8272(config)# ip nat pool <pool-name> <start_IP_address> <end_IP_address> netmask <netmask> [portrange <start_port> <end_port>]

RS 8272(config)# ip nat inside|outside source pool <match-pool-name> pool <translation-pool> [overload] [oneway]

RS 8272(config)# [no] ip nat proxyarp enable

RS 8272(config)# [no] ip nat enable

RS 8272(config)# ip nat translation timeout <0-4294967>


To delete all current dynamically created NAT translations before their time-out expires:

To delete various NAT rules and IP pools:

To display current NAT settings and statistics:

Scaling and Limitations

The following limitations apply for NAT:

Supported protocols for static NAPT and dynamic translations: TCP, UDP

Only ICMP Echo Request/Reply packets are supported for dynamic rules. All other ICMP packets are supported only for static NAT rules

IPv6 is not supported

Multicast traffic is not supported

Maximum bidirectional (two-way) active translations (SNAT and DNAT): 1024

Maximum unidirectional (one-way) active translations: 2048 (1024 SNAT + 1024 DNAT)

Maximum DNAT translations (no SNAT): 1024

Maximum bidirectional static/dynamic entries: 1024

RS 8272(config)# clear ip nat translations

RS 8272(config)# no ip nat all|static|dynamic|pools

RS 8272(config)# show ip nat [statistics|translations]


ECMP Static RoutesEqual-Cost Multi-Path (ECMP) is a forwarding mechanism that routes packets along multiple paths of equal cost. ECMP provides equally-distributed link load sharing across the paths. The hashing algorithm used is based on the destination IP and source IP (DIPSIP) addresses or only on the source IP address (SIP). ECMP routes allow the switch to choose between several next hops toward a given destination. The switch performs periodic health checks (ping) on each ECMP gateway. If a gateway fails, it is removed from the routing table, and an SNMP trap is sent.

ECMP Route Hashing

You can configure the parameters used to perform ECMP route hashing, as follows: sip: Source IP address dipsip: Source IP address and destination IP address (default)

The ECMP hash setting applies to all ECMP routes.


Configuring ECMP Static Routes

To configure ECMP static routes, add the same route multiple times, each with the same destination IP address, but with a different gateway IP address. These routes become ECMP routes.

1. Add a static route (IP address, subnet mask, gateway, and interface number).

2. Add another static route with the same IP address and mask, but a different gateway address.

3. Select an ECMP hashing method (optional).

You may add up to 32 gateways for each static route.

Use the following commands to check the status of ECMP static routes:

RS 8272(config)# ip route 10.10.1.1 255.255.255.255 100.10.1.1 1

RS 8272(config)# ip route 10.10.1.1 255.255.255.255 200.20.2.2 1

RS 8272(config)# ip route ecmphash [sip|dipsip]

RS 8272(config)# show ip route staticCurrent static routes: Destination Mask Gateway If ECMP 10.20.2.2 255.255.255.255 10.4.4.1 * 10.5.5.1 * 10.6.6.1 * ... 10.35.35.1 * ECMP healthcheck ping interval: 1ECMP healthcheck retries number: 3ECMP Hash Mechanism: dipsipGateway healthcheck: enabled

RS 8272(config)# show ip ecmp Current ecmp static routes: Destination Mask Gateway If GW Status 10.20.2.2 255.255.255.255 10.4.4.1 up 10.5.5.1 up 10.6.6.1 up ... 10.34.34.1 up 10.35.35.1 up


Dynamic Host Configuration ProtocolDynamic Host Configuration Protocol (DHCP) is a transport protocol that provides a framework for automatically assigning IP addresses and configuration information to other IP hosts or clients in a large TCP/IP network. Without DHCP, the IP address must be entered manually for each network device. DHCP allows a network administrator to distribute IP addresses from a central point and automatically send a new IP address when a device is connected to a different place in the network.

The switch accepts gateway configuration parameters if they have not been configured manually. The switch ignores DHCP gateway parameters if the gateway is configured.

DHCP is an extension of another network IP management protocol, Bootstrap Protocol (BOOTP), with an additional capability of being able to allocate reusable network addresses and configuration parameters for client operation.

Built on the client/server model, DHCP allows hosts or clients on an IP network to obtain their configurations from a DHCP server, thereby reducing network administration. The most significant configuration the client receives from the server is its required IP address; (other optional parameters include the “generic” file name to be booted, the address of the default gateway, and so forth).

To enable DHCP on a switch interface, use the following command:

DHCP Relay Agent

DHCP is described in RFC 2131, and the DHCP relay agent supported on the G8272 is described in RFC 1542. DHCP uses UDP as its transport protocol. The client sends messages to the server on port 67 and the server sends messages to the client on port 68.

DHCP defines the methods through which clients can be assigned an IP address for a finite lease period and allowing reassignment of the IP address to another client later. Additionally, DHCP provides the mechanism for a client to gather other IP configuration parameters it needs to operate in the TCP/IP network.

In the DHCP environment, the G8272 can act as a relay agent. The DHCP relay feature enables the switch to forward a client request for an IP address to five DHCP/ BOOTP servers with IP addresses that have been configured on the switch.

When a switch receives a UDP broadcast on port 67 from a DHCP client requesting an IP address, the switch acts as a proxy for the client, replacing the client source IP (SIP) and destination IP (DIP) addresses. The request is then forwarded as a UDP Unicast MAC layer message to five DHCP/ BOOTP servers whose IP addresses are configured on the switch. The servers respond as a UDP Unicast message back to the switch, with the default gateway and IP address for the client. The destination IP address in the server response represents the interface address on the switch that received the client request. This interface address tells the switch on which VLAN to send the server response to the client.

RS 8272(config)# system dhcp


To enable the DHCP relay feature on the G8272, you need to configure the DHCP/BOOTP server IP addresses on the switch. Generally, it is best to configure the switch IP interface on the client side to match the client’s subnet, and configure VLANs to separate client and server subnets. The DHCP server knows from which IP subnet the newly allocated IP address will come.

In G8272 implementation, there is no need for primary or secondary servers. The client request is forwarded to the BOOTP servers configured on the switch. The use of five servers provide failover redundancy. However, no health checking is supported.

Use the following commands to configure the switch as a DHCP relay agent:

Additionally, DHCP Relay functionality can be assigned on a per interface basis. Use the following commands to enable the Relay functionality:

RS 8272(config)# ip bootprelay server 1 <IP address>RS 8272(config)# ip bootprelay server 2 <IP address>RS 8272(config)# ip bootprelay server 3 <IP address>RS 8272(config)# ip bootprelay server 4 <IP address>RS 8272(config)# ip bootprelay server 5 <IP address>RS 8272(config)# ip bootprelay enableRS 8272(config)# show ip bootprelay

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# relay


Chapter 23. Policy-Based Routing

Policy-based routing (PBR) allows the RackSwitch G8272 to forward traffic based on defined policies rather than entries in the routing table. Such policies are defined based on the protocol, source IP, or other information present in a packet header. PBR provides a mechanism for applying the defined policies based on access control lists (ACLs), and marking packets with a type of service (ToS) to provide preferential treatment.

PBR can be applied only to the ingress traffic. You can configure a PBR policy using route maps and apply the route map to an ingress interface. You need to specify the match (using ACLs) and set (using route maps) criteria in the policy. Based on the defined rules, an action is triggered. If no match is found, or the policy rule specifies that the packet be denied, the packet is routed based on an entry in the routing table.

PBR Policies and ACLsUp to 256 ACLs can be configured for networks that use IPv4 addressing. Regular ACLs and PBR ACLs together cannot exceed the maximum ACLs supported.

ACLs are prioritized based on the ACL number. Lower numbers have higher priority. You must configure regular ACLs with lower numbers and PBR ACLs with higher numbers.Note: You cannot apply an ACL directly to an interface and using a PBR policy at the same time.

Applying PBR ACLsPBR ACLs must be applied to an IP interface that has a VLAN configured. In addition to the defined ACL rules, the Lenovo Networking OS uses the VLAN ID as a matching criterion. Traffic is filtered on a per-VLAN basis rather than a per-interface basis. If multiple IP interfaces have the same VLAN ID, route maps applied to each interface are used to filter traffic on the VLAN. For example: if interface IP 10 and interface IP 11 are members of VLAN 100; interface IP 10 uses PBR ACL 410 and interface IP 11 uses PBR ACL 411. Traffic on VLAN 100 will be filtered using PBR ACLs 410 and 411.Note: You cannot apply the PBR ACL to a Layer 2-only port.


Configuring Route MapsA route map is used to control and modify routing information. When PBR is enabled on an interface, all incoming packets are filtered based on the criteria defined in the route maps. For packets that match the filtering criteria, the precedence or Differentiated Services Code Point (DSCP) value can be changed, or the packets can be routed/forwarded to the appropriate next hop.

PBR and dynamic routing protocols, such as Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF), use route maps. You can define a maximum of 255 route maps. Route maps used by a PBR policy cannot be used by a dynamic routing protocol. You can configure a maximum of 32 access list statements in a route map. You can assign only one route map to a non-management IP interface.

You must define route map criteria using match and set commands. All sequential match clauses must be met by the packets for the set clauses to be applied.

Match Clauses

IPv4 ACLs can be used to specify the match criteria. The following match criteria can be used in a PBR ACL:

Source IP

Destination IP

Protocol

ToS

TCP/UDP source port

TCP/UDP destination port

If criteria other than the above are used in a PBR ACL, the switch will display an error message.

If ingress packets do not meet any of the match criteria, or if a deny statement is configured in the ACL, then the packets are routed based on the entries in the routing table.

Set Clauses

When the match clause(s) is satisfied, one of the following set clauses can be used to specify the packet forwarding criteria:

Next hop IP address: This must be the IP address of an interface on the adjacent router. A remote router interface cannot be used to specify the next hop. Packets are forwarded to the next hop IP address. The PBR policy uses the next hops in the order you specify. If the first next hop is down, then the second next hop is used, and so on. If you specify the next hop addresses using separate statements, then the next hops are used in the order you specify, starting from top to down. A maximum of 64 unique next hops can be configured across all route maps.

IP Differentiated Services Code Point (DSCP) value: A value used to set the DSCP value of the matching packets.

© Copyright Lenovo 2015 Chapter 23: Policy-Based Routing 343

IP precedence value: A value or keyword used to set the precedence value of the matching packets.

You can use a combination of set commands. However, you cannot use the set commands for DSCP and precedence together in the same route map.

Following are the basic steps and commands for configuring route maps.

1. Configure a route map.

2. Define an access list statement and assign an ACL to the route map.

3. Enable the access list.

4. Set next hop IP address (the IP address of an adjacent router).

OR

Set IP precedence value.

OR

Set IP DSCP value.

Configuring Health Check

You can configure tracking/health check parameters for each of the next hop IP address you specify in the route map. By default, Address Resolution Protocol (ARP) resolves the next hop IP address. The ARP re-try interval is two minutes.

RS 8272(config)# routemap <route map number>

RS 8272(configroutemap)# accesslist <1-32> matchaccesscontrol <IP ACL number>

RS 8272(configroutemap)# accesslist <1-32> enable

RS 8272(configroutemap)# set ip nexthop <IP address> [<nh2 IP address>] [<nh3 IP address>] [<nh4 IP address>] [accesslist <access list ID>|<access list range>]

RS 8272(configroutemap)# set ip precedence <value or keyword> [accesslist <access list ID>|<access list range>]

RS 8272(configroutemap)# set ip dscp <value> [accesslist <access list ID>|<access list range>]


Use the command below to configure health check:

You must configure a separate statement for verifying health check of each next hop. A maximum of four health check statements can be included in a route map.Note: When you configure next hops using set ip nexthop command and health check using the set ip nexthop verifyavailability command in the same route map, only the health check statements will be considered.

Following is an example of a route map health check statement:

Similarly, if there are inconsistent tracking parameters for a particular next hop IP address among multiple route maps, the route map with the lowest route map number is considered.Note: We strongly recommend that you configure health check if all/multiple next hops specified in the route map belong to the same Spanning Tree Group (STG). This is required in case of an STP topology change where all forwarding database (FDB) entries on all the ports in an STG are cleared. In such a scenario, the associated ARP entries are purged and the next hop specified in the PBR policy will not get resolved. When health check is configured, the PBR policy will route the traffic based on the second next hop that you have specified.

RS 8272(configroutemap)# set ip nexthop verifyavailability <next hop IP address> <priority> [icmp|arp] [interval] [retry] [accesslist <access list ID>|<access list range>]

Default values:Protocol: ARPInterval: 2 secondsRetry: 3 times

RS 8272(configroutemap)# set ip nexthop verifyavailability 12.1.1.1 10 icmp accesslist 4


Example PBR ConfigurationFollowing is an example of configuring PBR to match packets with a destination network address of 3.0.0.0. The PBR is applied to ingress packets on the IP interface 11. The next hop IP address is configured as 5.5.5.5 or 10.10.10.10.

1. Configure an ACL and specify the match criteria.

2. Configure a route map.

3. Apply the ACL to the route map.

4. Set the next hop IP addresses.

5. Apply the route map to an IP interface that has a VLAN configured.

6. Verify PBR configuration.

RS 8272(config)# accesscontrol list 100 action permitRS 8272(config)# accesscontrol list 100 ipv4 destinationipaddress 3.0.0.0 255.0.0.0

RS 8272(config)# routemap 126

RS 8272(configroutemap)# accesslist 1 matchaccesscontrol 100

RS 8272(configroutemap)# set ip nexthop 5.5.5.5 10.10.10.10RS 8272(configroutemap)# exit

RS 8272(config)# interface ip 11RS 8272(configipif)# ip policy routemap 126RS 8272(configipif)# exitRS 8272(config)# exit

RS 8272# show ip policy

IP Interface Route map11 126

RS 8272# show routemap 126

126: PBR, enabled Match clauses: alist 1: accesscontrol list 100, enabled Set clauses: ip nexthop 5.5.5.5 10.10.10.10, alist all Policy routing matches: 0 packets


Configuring PBR with other Features Consider the following PBR behavior when configured with the features given below:

DSCP: PBR ACLs can be used to remark an IP packet with a new precedence/DSCP value. PBR ACL remark statements have higher priority than the DSCP remark commands configured on ports.

Virtual Router Redundancy Protocol (VRRP): If PBR is enabled on a VRRP IP interface, the PBR becomes effective on the interface when the switch becomes the VRRP master on that IP interface.

Virtual Link Aggregation Group (VLAG): When configuring PBR on VLAG ports, you must configure the same PBR policy on both the VLAG peers. You cannot configure the next hop to be on a remote switch or on the VLAG ports.

Unsupported FeaturesPBR cannot be configured for:

Routed ports

Multicast traffic

IPv6 packets

Simple Network Management Protocol (SNMP)

Virtual Network Interface Card (vNIC)

Loopback Interface


Dynamic PBRDynamic Policy-Based Routing enables simplified configuration of multi-tenant networks. An IP interface can be set up as either a:

downlink to a specific tenant’s endpoint

uplink for one or more tenants

link to a service network accessible to one or more tenants

Traffic between different tenants is routed through their uplinks (firewall). Only intra-tenant and service network traffic is routed locally. When configuring interface tenant settings, ACLs are dynamically generated to route data traffic correspondingly.

Features and Limitations

The following features and limitations apply to Dynamic Policy-Based Routing:

Tenants must not use overlapping IP subnets.

If a tenant owns multiple subnets, data traffic between these subnets is not forwarded upstream. Instead, it is routed locally.

Dynamic PBR is not supported in IPv6

Tenant configuration is not supported on management interfaces

Support for up to: 64 tenants 64 uplinks 2 uplinks per tenant 5 service networks 10 subnets per tenant

Example Configuration

Following is a configuration example for a three tenants setup, two of which are supported by a local service network:

1. Set up Tenant 1 with endpoints on interfaces 5 and 6

2. Set up Tenant 2 with an endpoint on interface 7

RS 8272(config)# interface ip 5RS 8272(configipif)# tenant tenantid 1RS 8272(configipif)# interface ip 6RS 8272(configipif)# tenant tenantid 1

RS 8272(configipif)# interface ip 7RS 8272(configipif)# tenant tenantid 2


3. Set interface 8 as a common uplink for Tenants 1 and 2

4. Set up Tenant 3 with endpoints on interfaces 9 and 10 and uplinks on interfaces 11 and 12

5. Set interface 13 as a link to a service network available to Tenants 1 and 3

RS 8272(configipif)# interface ip 8RS 8272(configipif)# tenant uplink tenantid 1,2

RS 8272(configipif)# interface ip 9RS 8272(configipif)# tenant tenantid 3RS 8272(configipif)# interface ip 10RS 8272(configipif)# tenant tenantid 3RS 8272(configipif)# interface ip 11RS 8272(configipif)# tenant uplink tenantid 3RS 8272(configipif)# interface ip 12RS 8272(configipif)# tenant uplink tenantid 3

RS 8272(configipif)# interface ip 13RS 8272(configipif)# tenant services tenantid 1,3


Chapter 24. Routed Ports

By default, all ports on the RackSwitch G8272 behave as switch ports, which are capable of performing Layer 2 switch functions, such as VLANs, STP, or bridging. Switch ports also provide a physical point of access for the switch IP interfaces, which can perform global Layer 3 functions, such as routing for BGP or OSPF.

However, G8272 ports can also be configured as routed ports. Routed ports are configured with their own IP address belonging to a unique Layer 3 network, and behave similar to a port on a conventional router. Routed ports are typically used for connecting to a server or to a router.

When a switch port is configured as a routed port, it forwards Layer 3 traffic and no longer performs Layer 2 switching functions.

OverviewA routed port has the following characteristics:

Does not participate in bridging.

Does not belong to any user-configurable VLAN.

Does not implement any Layer 2 functionality, such as Spanning Tree Protocol (STP).

Is always in a forwarding state.

Can participate in IPv4 routing.

Can be configured with basic IP protocols, such as Internet Control Message Protocol (ICMP), and with Layer 3 protocols, such as Protocol-Independent Multicast (PIM), Routing Information Protocol (RIP), Open Shortest Path First (OSPF), and Border Gateway Protocol (BGP).

Can be configured with Internet Group Management Protocol (IGMP) querier and snooping functionality.

Layer 3 configuration is saved even when the interface is shutdown.

MAC address learning is always enabled.

Tagging and port VLAN ID (PVID) tagging is disabled.

Flooding is disabled.

Bridge Protocol Data Unit (BPDU)-guard is disabled.

Link Aggregation Control Protocol (LACP) is disabled.

Multicast threshold is disabled.

Static Multicast MAC and static unicast MAC can be configured.

Note: Ports on which LACP or portchannel is enabled cannot be changed to routed ports.

Note: Ports that have Static MAC addresses configured cannot be changed to routed ports.


When a switch port is configured as a routed port, the following configuration changes are automatically implemented:

The port is removed from all the VLANs it belonged to.

The port is added to an internal VLAN on which flooding is disabled. The ID of this internal VLAN could be 4094 or lower. The internal VLAN is assigned to Spanning Tree Group (STG) 1, if RSTP/PVRST is configured; or to Common Internal Spanning Tree (CIST), if MSTP is configured. You cannot change the VLAN number assigned to the routed port.

STP is disabled and the port is set to a forwarding state.

Note: The maximum number of VLANs you can configure on the RackSwitch G8272 is 4095. This maximum number will be reduced by the number of routed ports you configure.

All the Layer 2 configuration is lost.

When a routed port is changed back to a switch port, the following changes take place:

All the IP configuration is lost.

The ARP entry corresponding to the IP address is lost.

The switch port is added to the default VLAN and STG. In case of MSTP, it is added to the CIST.

STP is turned on.

The switch port can participate in STG and VLAN flooding.

Can participate in bridging.

LACP port attributes are set to default.

Multicast threshold remains disabled.

BPDU guard remains disabled.

IGMP configuration is lost.Note: When you configure a routed port to back to a switch port, it does not restore the Layer 2 configuration it had before it was changed to a routed port.

© Copyright Lenovo 2015 Chapter 24: Routed Ports 351

Configuring a Routed PortNote: You cannot configure a management port to be a routed port.

Following are the basic steps for configuring a routed port:

1. Enter the interface configuration mode for the port.

Note: You must enter only one port number. If you need to change multiple ports to routed ports, repeat the configuration steps for each port.

2. Enable routing.

3. Assign an IP address.

4. (Optional) Enable a Layer 3 routing protocol.

Note: Configure the Layer 3 routing protocol-related parameters in the interface configuration mode.

Configuring OSPF on Routed Ports

The following OSPF configuration commands are supported on routed ports:

See Chapter 31, “OSPF for details on the OSPF protocol and its configuration.

OSPFv3 cannot be configured on routed ports.

RS 8272(config)# interface port <port number>

RS 8272(configif)# no switchport

RS 8272(configif)# ip address <IP address> <Subnet Mask> enable

RS 8272(configif)# ip <ospf>|<pim>|<rip>

RS 8272(configif)# ip ospf ?

area Set area index cost Set interface cost deadinterval Set dead interval in seconds or milliseconds enable Enable OSPF for this interface hellointerval Set hello interval in seconds or milliseconds key Set authentication key messagedigestkey Set MD5 key ID passiveinterface Enable passive interface pointtopoint Enable pointtopoint interface priority Set interface router priority retransmitinterval Set retransmit interval in seconds transitdelay Set transit delay in seconds


OSPF Configuration ExampleThe following example includes the basic steps for configuring OSPF on a routed port:

Configuring RIP on Routed Ports

The following RIP configuration commands are supported on routed ports:

See Chapter 27, “Routing Information Protocol for details on the RIP protocol and its configuration.

RIP Configuration ExampleThe following example includes steps for a basic RIP configuration on a routed port:

RS 8272(config)# router ospfRS 8272(configrouterospf)# area 0 enableRS 8272(configrouterospf)# enableRS 8272(config-router-ospf)# exitRS 8272(config)# interface port 1RS 8272(configif)# no switchportwait...RS 8272(configif)# ip address 11.1.12.1 255.255.255.0 enablewait...RS 8272(configif)# ip ospf area 0RS 8272(configif)# ip ospf enableRS 8272(configif)# exit

RS 8272(configif)# ip rip ?

authentication Set IP authentication defaultaction Set default route action enable Enable RIP interface listen Enable listening to route updates metric Set metric multicastupdates Enable multicast updates poison Enable poisoned reverse splithorizon Enable split horizon supply Enable supplying route updates triggered Enable triggered updates version RIP version

RS 8272(config)# router ripRS 8272(configrouterrip)# enableRS 8272(config-router-rip)# exitRS 8272(config)# interface port 1RS 8272(configif)# no switchportwait...RS 8272(configif)# ip address 11.1.12.1 255.255.255.0 enablewait...RS 8272(configif)# ip rip enableRS 8272(configif)# exit


Configuring PIM on Routed Ports

The following PIM configuration commands are supported on routed ports:

See Chapter 33, “Protocol Independent Multicast for details on the PIM protocol and its configuration.

PIM Configuration ExampleThe following example includes the basic steps for configuring PIM on a routed port:

Verify the configuration using the following command:

RS 8272(configif)# ip pim ?

borderbit Set interface as border interface cbsrpreference Set preference for local interface as a candidate

bootstrap router componentid Add interface to the component drpriority Set designated router priority for the router

interface enable Enable PIM on this interface helloholdtime Set hello message holdtime for the interface hellointerval Set the frequency of PIM hello messages on the

interface joinpruneinterval Set frequency of PIM Join or Prune interval landelay Set lan delay for the router interface lanprunedelay Enable lan delay advertisement on interface neighboraddr Neighbor address neighborfilter Enable neighbor filter overrideinterval Set override interval for router interface

RS 8272(config)# ip pim enableRS 8272(config)# interface port 26RS 8272(configif)# no switchportwait...RS 8272(configif)# ip address 26.26.26.1 255.255.255.0 enablewait...RS 8272(configif)# ip pim enableRS 8272(configif)# exit

RS 8272(config)# ip pim component 1RS 8272(config-ip-pim-component)# rpcandidate rpaddress 224.0.0.0 240.0.0.0 33.33.33.1RS 8272(config-ip-pim-component)# rpcandidate holdtime 200RS 8272(configippimcomponent)# exit

RS 8272(config)# interface port 26RS 8272(configif)# ip pim cbsrpreference 200RS 8272(configif)# exit

RS 8272(config)# show ip pim interface port 26

Address IfName/IfId Ver/Mode Nbr Qry DRAddress DRPrio Count Interval 26.26.26.1 Rport 26 2/Sparse 0 30 26.26.26.1 1


Configuring BGP on Routed Ports

The routed port can be used to establish a TCP connection to form peer relationship with another BGP router. See Chapter 30, “Border Gateway Protocol for details on the BGP protocol and its configuration.

The following BGP configurations are not supported on routed ports:

Update source - configuring a local IP interface

Configuring IGMP on Routed Ports

IGMP querier and snooping can be configured on routed ports. For details, see Chapter 28, “Internet Group Management Protocol.

To configure IGMP snooping on a routed port, enter the following command in the Global Configuration mode:

To configure fastleave on routed ports, enter the following command in the Global Configuration mode:

The following IGMP querier commands are supported on routed ports:

RS 8272(config)# ip igmp snoop port <routed port ID>

RS 8272(config)# ip igmp fastleave port <routed port ID>

RS 8272(config)# ip igmp querier port <routed port ID> ?

electiontype Set IGMP querier type enable Turn IGMP Querier on maxresponse Set Queriers max response time queryinterval Set general query interval for IGMP Querier only robustness Set IGMP robustness sourceip Set source IP to be used for IGMP startupcount Set startupcount for IGMP startupinterval Set startup query interval for IGMP version Sets the operating version of the IGMP snooping

switch


LimitationsFollowing features/configurations are not supported on routed ports:

Subinterfaces

BPDU Guard

Broadcast Threshold

Multicast Threshold

Link Aggregation Control Protocol (LACP)

Static Trunking

Fibre Channel over Ethernet (FCoE)

Converged Enhanced Ethernet (CEE)

IPv6

IP Security (IPsec)

Internet Key Exchange version 2 (IKEv2)

Virtual Router Redundancy Protocol (VRRP)

Policy-based Routing (PBR)

Hotlinks

Failover

802.1X

Dynamic Host Configuration Protocol (DHCP)

BOOTP

Simple Network Management Protocol (SNMP)

IGMP Relay

Static Multicast Routes

Static Mrouter Port

Management Port



Chapter 25. Internet Protocol Version 6

Internet Protocol version 6 (IPv6) is a network layer protocol intended to expand the network address space. IPv6 is a robust and expandable protocol that meets the need for increased physical address space. The switch supports the following RFCs for IPv6-related features:

This chapter describes the basic configuration of IPv6 addresses and how to manage the switch via IPv6 host management.

RFC 1981 RFC 2404 RFC 2410 RFC 2451 RFC 2460 RFC 2474 RFC 2526 RFC 2711 RFC 2740 RFC 3289



RFC 4443 RFC 4552 RFC 4718 RFC 4835 RFC 4861 RFC 4862 RFC 5095 RFC 5114 RFC 5340


IPv6 LimitationsThe following IPv6 features are not supported in this release. Dynamic Host Control Protocol for IPv6 (DHCPv6) Border Gateway Protocol for IPv6 (BGP) Routing Information Protocol for IPv6 (RIPng)

Most other Lenovo Networking OS 8.2 features permit IP addresses to be configured using either IPv4 or IPv6 address formats. However, the following switch features support IPv4 only: Bootstrap Protocol (BOOTP) and DHCP RADIUS, TACACS+ and LDAP VMware Virtual Center (vCenter) for VMready Routing Information Protocol (RIP) Border Gateway Protocol (BGP) Protocol Independent Multicast (PIM) Virtual Router Redundancy Protocol (VRRP) sFlow

© Copyright Lenovo 2015 Chapter 25: Internet Protocol Version 6 359

IPv6 Address FormatThe IPv6 address is 128 bits (16 bytes) long and is represented as a sequence of eight 16-bit hex values, separated by colons.

Each IPv6 address has two parts:

Subnet prefix representing the network to which the interface is connected

Local identifier, either derived from the MAC address or user-configured

The preferred hexadecimal format is as follows: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx

Example IPv6 address: FEDC:BA98:7654:BA98:FEDC:1234:ABCD:5412

Some addresses can contain long sequences of zeros. A single contiguous sequence of zeros can be compressed to :: (two colons). For example, consider the following IPv6 address:FE80:0:0:0:2AA:FF:FA:4CA2

The address can be compressed as follows:FE80::2AA:FF:FA:4CA2

Unlike IPv4, a subnet mask is not used for IPv6 addresses. IPv6 uses the subnet prefix as the network identifier. The prefix is the part of the address that indicates the bits that have fixed values or are the bits of the subnet prefix. An IPv6 prefix is written in address/prefix-length notation. For example, in the following address, 64 is the network prefix:21DA:D300:0000:2F3C::/64

IPv6 addresses can be either user-configured or automatically configured. Automatically configured addresses always have a 64-bit subnet prefix and a 64-bit interface identifier. In most implementations, the interface identifier is derived from the switch's MAC address, using a method called EUI-64.

Most Lenovo N/OS 8.2 features permit IP addresses to be configured using either IPv4 or IPv6 address formats. Throughout this manual, IP address is used in places where either an IPv4 or IPv6 address is allowed. In places where only one type of address is allowed, the type (IPv4 or IPv6) is specified.


IPv6 Address TypesIPv6 supports three types of addresses: unicast (one-to-one), multicast (one-to-many), and anycast (one-to-nearest). Multicast addresses replace the use of broadcast addresses.

Unicast Address

Unicast is a communication between a single host and a single receiver. Packets sent to a unicast address are delivered to the interface identified by that address. IPv6 defines the following types of unicast address:

Global Unicast address: An address that can be reached and identified globally. Global Unicast addresses use the high-order bit range up to FF00, therefore all non-multicast and non-link-local addresses are considered to be global unicast. A manually configured IPv6 address must be fully specified. Autoconfigured IPv6 addresses are comprised of a prefix combined with the 64-bit EUI. RFC 4291 defines the IPv6 addressing architecture. The interface ID must be unique within the same subnet.

Link-local unicast address: An address used to communicate with a neighbor on the same link. Link-local addresses use the format FE80::EUILink-local addresses are designed to be used for addressing on a single link for purposes such as automatic address configuration, neighbor discovery, or when no routers are present.Routers must not forward any packets with link-local source or destination addresses to other links.

Multicast

Multicast is communication between a single host and multiple receivers. Packets are sent to all interfaces identified by that address. An interface may belong to any number of multicast groups.

A multicast address (FF00 - FFFF) is an identifier for a group interface. The multicast address most often encountered is a solicited-node multicast address using prefix FF02::1:FF00:0000/104 with the low-order 24 bits of the unicast or anycast address.

The following well-known multicast addresses are pre-defined. The group IDs defined in this section are defined for explicit scope values, as follows:FF00:::::::0 through FF0F:::::::0

Anycast

Packets sent to an anycast address or list of addresses are delivered to the nearest interface identified by that address. Anycast is a communication between a single sender and a list of addresses.

Anycast addresses are allocated from the unicast address space, using any of the defined unicast address formats. Thus, anycast addresses are syntactically indistinguishable from unicast addresses. When a unicast address is assigned to


more than one interface, thus turning it into an anycast address, the nodes to which the address is assigned must be explicitly configured to know that it is an anycast address.


IPv6 Address AutoconfigurationIPv6 supports the following types of address autoconfiguration:

Stateful address configurationAddress configuration is based on the use of a stateful address configuration protocol, such as DHCPv6, to obtain addresses and other configuration options.

Stateless address configurationAddress configuration is based on the receipt of Router Advertisement messages that contain one or more Prefix Information options.

N/OS 8.2 supports stateless address configuration.

Stateless address configuration allows hosts on a link to configure themselves with link-local addresses and with addresses derived from prefixes advertised by local routers. Even if no router is present, hosts on the same link can configure themselves with link-local addresses and communicate without manual configuration.


IPv6 InterfacesEach IPv6 interface supports multiple IPv6 addresses. You can manually configure up to two IPv6 addresses for each interface, or you can allow the switch to use stateless autoconfiguration.

You can manually configure two IPv6 addresses for each interface, as follows:

Initial IPv6 address is a global unicast or anycast address.

Note that you cannot configure both addresses as anycast. If you configure an anycast address on the interface you must also configure a global unicast address on that interface.

Second IPv6 address can be a unicast or anycast address.

You cannot configure an IPv4 address on an IPv6 management interface. Each interface can be configured with only one address type: either IPv4 or IPv6, but not both. When changing between IPv4 and IPv6 address formats, the prior address settings for the interface are discarded.

Each IPv6 interface can belong to only one VLAN. Each VLAN can support only one IPv6 interface. Each VLAN can support multiple IPv4 interfaces.

Use the following commands to configure the IPv6 gateway:

IPv6 gateway 1 is reserved for IPv6 data interfaces. IPv6 gateway 4 is the default IPv6 management gateway.

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# ipv6 address <IPv6 address>

RS 8272(configipif)# ipv6 secaddr6 <IPv6 address>RS 8272(configipif)# exit

RS 8272(config)# ip gateway6 1 address <IPv6 address>RS 8272(config)# ip gateway6 1 enable


Neighbor Discovery

Neighbor Discovery Overview

The switch uses Neighbor Discovery protocol (ND) to gather information about other router and host nodes, including the IPv6 addresses. Host nodes use ND to configure their interfaces and perform health detection. ND allows each node to determine the link-layer addresses of neighboring nodes, and to keep track of each neighbor’s information. A neighboring node is a host or a router that is linked directly to the switch. The switch supports Neighbor Discovery as described in RFC 4861.

Neighbor Discover messages allow network nodes to exchange information, as follows:

Neighbor Solicitations allow a node to discover information about other nodes.

Neighbor Advertisements are sent in response to Neighbor Solicitations. The Neighbor Advertisement contains information required by nodes to determine the link-layer address of the sender, and the sender’s role on the network.

IPv6 hosts use Router Solicitations to discover IPv6 routers. When a router receives a Router Solicitation, it responds immediately to the host.

Routers uses Router Advertisements to announce its presence on the network, and to provide its address prefix to neighbor devices. IPv6 hosts listen for Router Advertisements, and uses the information to build a list of default routers. Each host uses this information to perform autoconfiguration of IPv6 addresses.

Redirect messages are sent by IPv6 routers to inform hosts of a better first-hop address for a specific destination. Redirect messages are only sent by routers for unicast traffic, are only unicast to originating hosts, and are only processed by hosts.

ND configuration for general advertisements, flags, and interval settings, as well as for defining prefix profiles for router advertisements, is performed on a per-interface basis using the following command path:

To add or remove entries in the static neighbor cache, use the following command path:

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# [no] ipv6 nd ?RS 8272(configipif)# exit

RS 8272(config)# [no] ip neighbors ?


Host vs. Router

Each IPv6 interface can be configured as a router node or a host node, as follows:

A router node’s IP address is configured manually. Router nodes can send Router Advertisements.

A host node’s IP address is autoconfigured. Host nodes listen for Router Advertisements that convey information about devices on the network.

Note: When IP forwarding is turned on, all IPv6 interfaces configured on the switch can forward packets.

You can configure each IPv6 interface as either a host node or a router node. You can manually assign an IPv6 address to an interface in host mode, or the interface can be assigned an IPv6 address by an upstream router, using information from router advertisements to perform stateless auto-configuration.

To set an interface to host mode, use the following command:

The G8272 supports up to 1156 IPv6 routes.

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# ip6hostRS 8272(configipif)# exit


Supported ApplicationsThe following applications have been enhanced to provide IPv6 support.

PingThe ping command supports IPv6 addresses. Use the following format to ping an IPv6 address: ping <host name>|<IPv6 address> [<tries (0-4294967295)>] [dataport] [mgmtport]

TracerouteThe traceroute command supports IPv6 addresses (but not link-local addresses). Use the following format to perform a traceroute to an IPv6 address: traceroute <host name>| <IPv6 address> [<max-hops (1-32)> [<msec delay (1-4294967295)>]]

Telnet serverThe telnet command supports IPv6 addresses (but not link-local addresses). Use the following format to Telnet into an IPv6 interface on the switch: telnet <host name>| <IPv6 address> [<port>]

Telnet clientThe telnet command supports IPv6 addresses (but not link-local addresses). Use the following format to Telnet to an IPv6 address: telnet <host name>| <IPv6 address> [<port>]

HTTP/HTTPSThe HTTP/HTTPS servers support both IPv4 and IPv6 connections.

SSHSecure Shell (SSH) connections over IPv6 are supported (but not link-local addresses). The following syntax is required from the client: ssh u <IPv6 address>

Example: ssh u 2001:2:3:4:0:0:0:142

TFTPThe TFTP commands support both IPv4 and IPv6 addresses. Link-local addresses are not supported.

FTPThe FTP commands support both IPv4 and IPv6 addresses. Link-local addresses are not supported.


DNS clientDNS commands support both IPv4 and IPv6 addresses. Link-local addresses are not supported. Use the following command to specify the type of DNS query to be sent first:

If you set the request version to ipv4, the DNS application sends an A query first, to resolve the hostname with an IPv4 address. If no A record is found for that hostname (no IPv4 address for that hostname) an AAAA query is sent to resolve the hostname with a IPv6 address. If you set the request version to ipv6, the DNS application sends an AAAA query first, to resolve the hostname with an IPv6 address. If no AAAA record is found for that hostname (no IPv6 address for that hostname) an A query is sent to resolve the hostname with an IPv4 address.

Configuration GuidelinesWhen you configure an interface for IPv6, consider the following guidelines:

Support for subnet router anycast addresses is not available.

A single interface can accept either IPv4 or IPv6 addresses, but not both IPv4 and IPv6 addresses.

A single interface can accept multiple IPv6 addresses.

A single interface can accept only one IPv4 address.

If you change the IPv6 address of a configured interface to an IPv4 address, all IPv6 settings are deleted.

A single VLAN can support only one IPv6 interface.

Health checks are not supported for IPv6 gateways.

IPv6 interfaces support Path MTU Discovery. The CPU’s MTU is fixed at 1500 bytes.

Support for jumbo frames (1,500 to 9,216 byte MTUs) is limited. Any jumbo frames intended for the CPU must be fragmented by the remote node. The switch can re-assemble fragmented packets up to 9k. It can also fragment and transmit jumbo packets received from higher layers.

RS 8272(config)# ip dns ipv6 requestversion ipv4|ipv6


IPv6 Configuration ExamplesThis section provides steps to configure IPv6 on the switch.

IPv6 Example 1

The following example uses IPv6 host mode to autoconfigure an IPv6 address for the interface. By default, the interface is assigned to VLAN 1.

1. Enable IPv6 host mode on an interface.

2. Configure the IPv6 default gateway.

3. Verify the interface address.

IPv6 Example 2

Use the following example to manually configure IPv6 on an interface.

1. Assign an IPv6 address and prefix length to the interface.

The secondary IPv6 address is compressed, and the prefix length is 32.

2. Configure the IPv6 default gateway.

3. Configure router advertisements for the interface (optional)

RS 8272(config)# interface ip 2RS 8272(configipif)# ip6hostRS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway6 1 address 2001:BA98:7654:BA98:FEDC:1234:ABCD:5412

RS 8272(config)# ip gateway6 1 enable

RS 8272(config)# show interface ip 2

RS 8272(config)# interface ip 3RS 8272(configipif)# ipv6 address

2001:BA98:7654:BA98:FEDC:1234:ABCD:5214RS 8272(configipif)# ipv6 prefixlen 64RS 8272(configipif)# ipv6 seccaddr6 2003::1 32RS 8272(configipif)# vlan 2RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway6 1 address 2001:BA98:7654:BA98:FEDC:1234:ABCD:5412

RS 8272(config)# ip gateway6 1 enable

RS 8272(config)# interface ip 3RS 8272(configipif)# no ipv6 nd suppressra



RS 8272(configipif)# show layer3


© Copyright Lenovo 2015 Chapter 26: IPsec with IPv6 371

Chapter 26. IPsec with IPv6

Internet Protocol Security (IPsec) is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a communication session. IPsec also includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session.

Since IPsec was implemented in conjunction with IPv6, all implementations of IPv6 must contain IPsec. To support the National Institute of Standards and Technology (NIST) recommendations for IPv6 implementations, Lenovo Networking OS IPv6 feature compliance has been extended to include the following IETF RFCs, with an emphasis on IP Security (IPsec) and Internet Key Exchange version 2, and authentication/confidentiality for OSPFv3:

RFC 4301 for IPv6 security

RFC 4302 for the IPv6 Authentication Header

RFCs 2404, 2410, 2451, 3602, and 4303 for IPv6 Encapsulating Security Payload (ESP), including NULL encryption, CBC-mode 3DES and AES ciphers, and HMAC-SHA-1-96.

RFCs 4306, 4307, 4718, and 4835 for IKEv2 and cryptography

RFC 4552 for OSPFv3 IPv6 authentication/confidentiality

RFC 5114 for Diffie-Hellman groupsNote: This implementation of IPsec supports DH groups 1, 2, 5, 14, and 24.

The following topics are discussed in this chapter:

“IPsec Protocols” on page 372

“Using IPsec with the RackSwitch G8272” on page 373


IPsec ProtocolsThe Lenovo N/OS implementation of IPsec supports the following protocols:

Authentication Header (AH)AHs provide connectionless integrity outand data origin authentication for IP packets, and provide protection against replay attacks. In IPv6, the AH protects the AH itself, the Destination Options extension header after the AH, and the IP payload. It also protects the fixed IPv6 header and all extension headers before the AH, except for the mutable fields DSCP, ECN, Flow Label, and Hop Limit. AH is defined in RFC 4302.

Encapsulating Security Payload (ESP)ESPs provide confidentiality, data origin authentication, integrity, an anti-replay service (a form of partial sequence integrity), and some traffic flow confidentiality. ESPs may be applied alone or in combination with an AH. ESP is defined in RFC 4303.

Internet Key Exchange Version 2 (IKEv2)IKEv2 is used for mutual authentication between two network elements. An IKE establishes a security association (SA) that includes shared secret information to efficiently establish SAs for ESPs and AHs, and a set of cryptographic algorithms to be used by the SAs to protect the associated traffic. IKEv2 is defined in RFC 4306.

Using IKEv2 as the foundation, IPsec supports ESP for encryption and/or authentication, and/or AH for authentication of the remote partner.

Both ESP and AH rely on security associations. A security association (SA) is the bundle of algorithms and parameters (such as keys) that encrypt and authenticate a particular flow in one direction.


Using IPsec with the RackSwitch G8272IPsec supports the fragmentation and reassembly of IP packets that occurs when data goes to and comes from an external device. The RackSwitch G8272 acts as an end node that processes any fragmentation and reassembly of packets but does not forward the IPsec traffic. The IKEv2 key must be authenticated before you can use IPsec.

The security protocol for the session key is either ESP or AH. Outgoing packets are labeled with the SA SPI (Security Parameter Index), which the remote device will use in its verification and decryption process.

Every outgoing IPv6 packet is checked against the IPsec policies in force. For each outbound packet, after the packet is encrypted, the software compares the packet size with the MTU size that it either obtains from the default minimum maximum transmission unit (MTU) size (1500) or from path MTU discovery. If the packet size is larger than the MTU size, the receiver drops the packet and sends a message containing the MTU size to the sender. The sender then fragments the packet into smaller pieces and retransmits them using the correct MTU size.

The maximum traffic load for each IPsec packet is limited to the following:

IKEv2 SAs: 5

IPsec SAs: 10 (5 SAs in each direction)

SPDs: 20 (10 policies in each direction)

IPsec is implemented as a software cryptography engine designed for handling control traffic, such as network management. IPsec is not designed for handling data traffic, such as a VPN.

Setting up Authentication

Before you can use IPsec, you need to have key policy authentication in place. There are two types of key policy authentication:

Preshared key (default)The parties agree on a shared, secret key that is used for authentication in an IPsec policy. During security negotiation, information is encrypted before transmission by using a session key created by using a Diffie-Hellman calculation and the shared, secret key. Information is decrypted on the receiving end using the same key. One IPsec peer authenticates the other peer's packet by decryption and verification of the hash inside the packet (the hash inside the packet is a hash of the preshared key). If authentication fails, the packet is discarded.

Digital certificate (using RSA algorithms)The peer being validated must hold a digital certificate signed by a trusted Certificate Authority and the private key for that digital certificate. The side performing the authentication only needs a copy of the trusted certificate authorities digital certificate. During IKEv2 authentication, the side being validated sends a copy of the digital certificate and a hash value signed using the private key. The certificate can be either generated or imported.


Note: During the IKEv2 negotiation phase, the digital certificate takes precedence over the preshared key.

Creating an IKEv2 ProposalWith IKEv2, a single policy can have multiple encryption and authentication types, as well as multiple integrity algorithms.

To create an IKEv2 proposal:

1. Enter IKEv2 proposal mode.

2. Set the DES encryption algorithm.

3. Set the authentication integrity algorithm type.

4. Set the Diffie-Hellman group.

Importing an IKEv2 Digital CertificateTo import an IKEv2 digital certificate for authentication:

1. Import the CA certificate file.

2. Import the host key file.

3. Import the host certificate file.

Note: When prompted for the port to use for download the file, if you used a management port to connect the switch to the server, enter mgt, otherwise enter data.

RS 8272(config)# ikev2 proposal

RS 8272(config-ikev2-prop)# encryption 3des|aescbc (default: 3des)

RS 8272(configikev2prop)# integrity sha1 (default: sha1)

RS 8272(config-ikev2-prop)# group 24 (default: 24)


Generating an IKEv2 Digital CertificateTo create an IKEv2 digital certificate for authentication:

1. Create an HTTPS certificate defining the information you want to be used in the various fields.

2. Save the HTTPS certificate.

The certificate is valid only until the switch is rebooted. To save the certificate so that it is retained beyond reboot or power cycles, use the following command:

3. Enable IKEv2 RSA-signature authentication:

Enabling IKEv2 Preshared Key AuthenticationTo set up IKEv2 preshared key authentication:

1. Enter the local preshared key.

2. If asymmetric authentication is supported, enter the remote key:

where the following parameters are used:

preshared key A string of 1-256 characters

IPv6 host An IPv6-format host, such as “3000::1”

3. Set up the IKEv2 identification type by entering one of the following commands:

To disable IKEv2 RSA-signature authentication method and enable preshared key authentication, enter:

Setting Up a Key Policy

When configuring IPsec, you must define a key policy. This key policy can be either manual or dynamic. Either way, configuring a policy involves the following steps: Create a transform set—This defines which encryption and authentication algo-

rithms are used.

Create a traffic selector—This describes the packets to which the policy applies.

Country Name (2 letter code) [US]: <country code>State or Province Name (full name) [CA]: <state>Locality Name (eg, city) [Santa Clara]: <city>Organization Name (eg, company) [Lenovo]: <company>Organizational Unit Name (eg, section) [Engineering]: <org. unit>Common Name (eg, YOUR name) []: <your current IP address>Email (eg, email address) []: <email address>Confirm generat‘eywing certificate? [y/n]: yGenerating certificate. Please wait (approx 30 seconds)restarting SSL agent

RS 8272(config)# ikev2 presharekey local <preshared key, a string of 1-256 chars>

RS 8272(config)# ikev2 presharekey remote <preshared key> <IPv6 host>


Establish an IPsec policy.

Apply the policy.

1. To define which encryption and authentication algorithms are used, create a transform set:


transform ID A number from 1-10

encryption method One of the following: esp3des | espaescbc | espnull

integrity algorithm One of the following: espsha1

AH authentication algorithm One of the following: ahsha1

2. Decide whether to use tunnel or transport mode. The default mode is transport.

3. To describe the packets to which this policy applies, create a traffic selector using the following command:


traffic selector number an integer from 1-10

permit|deny whether or not to permit IPsec encryption of traffic that meets the criteria specified in this command

any apply the selector to any type of traffic

icmp <type>|any only apply the selector only to ICMP traffic of the specified type (an integer from 1-255) or to any ICMP traffic

tcp only apply the selector to TCP traffic

source IP address|any the source IP address in IPv6 format or “any” source

destination IP address|any the destination IP address in IPv6 format or “any” destination

prefix length (Optional) the length of the destination IPv6 prefix; an integer from 1-128

Permitted traffic that matches the policy in force is encrypted, while denied traffic that matches the policy in force is dropped. Traffic that does not match the policy bypasses IPsec and passes through clear (unencrypted).

4. Choose whether to use a manual or a dynamic policy.

RS 8272(config)# ipsec transformset tunnel|transport

RS 8272(config)# ipsec trafficselector <traffic selector number> permit|deny any|icmp <type|any> |tcp > <source IP address|any> <destination IP address|any> [<prefix length>]


Using a Manual Key Policy

A manual policy involves configuring policy and manual SA entries for local and remote peers.

To configure a manual key policy, you need: The IP address of the peer in IPv6 format (for example, “3000::1”). Inbound/Outbound session keys for the security protocols.

You can then assign the policy to an interface. The peer represents the other end of the security association. The security protocol for the session key can be either ESP or AH.

To create and configure a manual policy:

1. Enter a manual policy to configure.

2. Configure the policy.


peer’s IPv6 address The IPv6 address of the peer (for example, 3000::1)

IPsec traffic-selector A number from1-10

IPsec of transform-set A number from1-10

inbound AH IPsec key The inbound AH key code, in hexadecimal

inbound AH IPsec SPI A number from 256-4294967295

inbound ESP cipher key The inbound ESP key code, in hexadecimal

inbound ESP SPI A number from 256-4294967295

inbound ESP authenticator key The inbound ESP authenticator key code, in hexadecimal

outbound AH IPsec key The outbound AH key code, in hexadecimal

outbound AH IPsec SPI A number from 256-4294967295

outbound ESP cipher key The outbound ESP key code, in hexadecimal

outbound ESP SPI A number from 256-4294967295

outbound ESP authenticator key The outbound ESP authenticator key code, in hexadecimal

Notes:

When configuring a manual policy ESP, the ESP authenticator key is optional.

If using third-party switches, the IPsec manual policy session key must be of fixed length as follows: For AH key: SHA1 is 20 bytes; MD5 is 16 bytes For ESP cipher key: 3DES is 24 bytes; AES-cbc is 24 bytes; DES is 8 bytes For ESP auth key: SHA1 is 20 bytes; MD5 is 16 bytes


3. After you configure the IPSec policy, you need to apply it to the interface to enforce the security policies on that interface and save it to keep it in place after a reboot. To accomplish this, enter:


Using a Dynamic Key Policy

When you use a dynamic key policy, the first packet triggers IKE and sets the IPsec SA and IKEv2 SA. The initial packet negotiation also determines the lifetime of the algorithm, or how long it stays in effect. When the key expires, a new key is automatically created. This helps prevent break-ins.

To configure a dynamic key policy:

1. Choose a dynamic policy to configure.

2. Configure the policy.


peer’s IPv6 address The IPv6 address of the peer (for example, 3000::1)

index of traffic-selector A number from1-10

index of transform-set A number from1-10

SA lifetime, in seconds The length of time the SA is to remain in effect; an integer from120-86400

pfs enable|disable Whether to enable or disable the perfect forward security feature. The default is disable.

Note: In a dynamic policy, the AH and ESP keys are created by IKEv2.

3. After you configure the IPSec policy, you need to apply it to the interface to enforce the security policies on that interface and save it to keep it in place after a reboot. To accomplish this, enter:



Chapter 27. Routing Information Protocol

In a routed environment, routers communicate with one another to keep track of available routes. Routers can learn about available routes dynamically using the Routing Information Protocol (RIP). Lenovo Networking OS software supports RIP version 1 (RIPv1) and RIP version 2 (RIPv2) for exchanging TCP/IPv4 route information with other routers. Note: Lenovo N/OS 8.2 does not support IPv6 for RIP.


Distance Vector ProtocolRIP is known as a distance vector protocol. The vector is the network number and next hop, and the distance is the metric associated with the network number. RIP identifies network reachability based on metric, and metric is defined as hop count. One hop is considered to be the distance from one switch to the next, which typically is 1.

When a switch receives a routing update that contains a new or changed destination network entry, the switch adds 1 to the metric value indicated in the update and enters the network in the routing table. The IPv4 address of the sender is used as the next hop.

StabilityRIP includes a number of other stability features that are common to many routing protocols. For example, RIP implements the split horizon and hold-down mechanisms to prevent incorrect routing information from being propagated.

RIP prevents routing loops from continuing indefinitely by implementing a limit on the number of hops allowed in a path from the source to a destination. The maximum number of hops in a path is 15. The network destination network is considered unreachable if increasing the metric value by 1 causes the metric to be 16 (that is infinity). This limits the maximum diameter of a RIP network to less than 16 hops.

RIP is often used in stub networks and in small autonomous systems that do not have many redundant paths.

Routing UpdatesRIP sends routing-update messages at regular intervals and when the network topology changes. Each router “advertises” routing information by sending a routing information update every 30 seconds. If a router doesn’t receive an update from another router for 180 seconds, those routes provided by that router are declared invalid. The routes are removed from the routing table, but they remain in the RIP routes table. After another 120 seconds without receiving an update for those routes, the routes are removed from respective regular updates.

When a router receives a routing update that includes changes to an entry, it updates its routing table to reflect the new route. The metric value for the path is increased by 1, and the sender is indicated as the next hop. RIP routers maintain only the best route (the route with the lowest metric value) to a destination.

For more information, see the Configuration section, Routing Information Protocol Configuration in the Lenovo Networking OS Command Reference.

© Copyright Lenovo 2015 Chapter 27: Routing Information Protocol 383

RIPv1RIP version 1 use broadcast User Datagram Protocol (UDP) data packets for the regular routing updates. The main disadvantage is that the routing updates do not carry subnet mask information. Hence, the router cannot determine whether the route is a subnet route or a host route. It is of limited usage after the introduction of RIPv2. For more information about RIPv1 and RIPv2, refer to RFC 1058 and RFC 2453.

RIPv2RIPv2 is the most popular and preferred configuration for most networks. RIPv2 expands the amount of useful information carried in RIP messages and provides a measure of security. For a detailed explanation of RIPv2, refer to RFC 1723 and RFC 2453.

RIPv2 improves efficiency by using multicast UDP (address 224.0.0.9) data packets for regular routing updates. Subnet mask information is provided in the routing updates. A security option is added for authenticating routing updates, by using a shared password. N/OS supports using clear password for RIPv2.

RIPv2 in RIPv1 Compatibility ModeN/OS allows you to configure RIPv2 in RIPv1compatibility mode, for using both RIPv2 and RIPv1 routers within a network. In this mode, the regular routing updates use broadcast UDP data packet to allow RIPv1 routers to receive those packets. With RIPv1 routers as recipients, the routing updates have to carry natural or host mask. Hence, it is not a recommended configuration for most network topologies. Note: When using both RIPv1 and RIPv2 within a network, use a single subnet mask throughout the network.


RIP FeaturesN/OS provides the following features to support RIPv1 and RIPv2:

Poison

Simple split horizon in RIP scheme omits routes learned from one neighbor in updates sent to that neighbor. That is the most common configuration used in RIP, that is setting this Poison to DISABLE. Split horizon with poisoned reverse includes such routes in updates, but sets their metrics to 16. The disadvantage of using this feature is the increase of size in the routing updates.

Triggered Updates

Triggered updates are an attempt to speed up convergence. When Triggered Updates is enabled, whenever a router changes the metric for a route, it sends update messages almost immediately, without waiting for the regular update interval. It is recommended to enable Triggered Updates.

Multicast

RIPv2 messages use IPv4 multicast address (224.0.0.9) for periodic broadcasts. Multicast RIPv2 announcements are not processed by RIPv1 routers. IGMP is not needed since these are inter-router messages which are not forwarded.

To configure RIPv2 in RIPv1 compatibility mode, set multicast to disable, and set version to both.

Default

The RIP router can listen and supply a default route, usually represented as IPv4 0.0.0.0 in the routing table. When a router does not have an explicit route to a destination network in its routing table, it uses the default route to forward those packets.

Metric

The metric field contains a configurable value between 1 and 15 (inclusive) which specifies the current metric for the interface. The metric value typically indicates the total number of hops to the destination. The metric value of 16 represents an unreachable destination.

Authentication

RIPv2 authentication uses plaintext password for authentication. If configured using Authentication password, then it is necessary to enter an authentication key value.

The following method is used to authenticate an RIP message:

If the router is not configured to authenticate RIPv2 messages, then RIPv1 and unauthenticated RIPv2 messages are accepted; authenticated RIPv2 messages are discarded.

If the router is configured to authenticate RIPv2 messages, then RIPv1 messages and RIPv2 messages which pass authentication testing are accepted; unauthenticated and failed authentication RIPv2 messages are discarded.

© Copyright Lenovo 2015 Chapter 27: Routing Information Protocol 385

For maximum security, RIPv1 messages are ignored when authentication is enabled; otherwise, the routing information from authenticated messages is propagated by RIPv1 routers in an unauthenticated manner.

RIP Configuration ExampleThe following is an example of RIP configuration.Note: An interface RIP disabled uses all the default values of the RIP, no matter how the RIP parameters are configured for that interface. RIP sends out RIP regular updates to include an UP interface, but not a DOWN interface.

1. Add VLANs for routing interfaces.

2. Add IP interfaces with IPv4 addresses to VLANs.

3. Turn on RIP globally and enable RIP for each interface.

>> (config)# vlan 2>> (configvlan)# exit>> (config)# interface port 2>> (configif)# switchport mode trunk>> (configif)# switchport trunk allowed vlan add 2>> (configif)# exit

Port 2 is an UNTAGGED port and its current PVID is 1.Confirm changing PVID from 1 to 2 [y/n]: y>> (config)# vlan 3>> (configvlan)# exit>> (config)# interface port 3>> (configif)# switchport mode trunk>> (configif)# switchport trunk allowed vlan add 3>> (configif)# exitPort 3 is an UNTAGGED port and its current PVID is 1.Confirm changing PVID from 1 to 3 [y/n]: y

>> # interface ip 2>> (configipif)# enable>> (configipif)# ip address 102.1.1.1>> (configipif)# vlan 2>> (configipif)# exit>> # interface ip 3>> (configipif)# enable>> (configipif)# ip address 103.1.1.1>> (configipif)# vlan 3

>> # router rip>> (configrouterrip)# enable>> (configrouterrip)# exit>> # interface ip 2>> (configipif)# ip rip enable>> (configipif)# exit>> # interface ip 3>> (configipif)# ip rip enable>> (configipif)# exit


Use the following command to check the current valid routes in the routing table of the switch:

For those RIP routes learned within the garbage collection period, that are routes phasing out of the routing table with metric 16, use the following command:

Locally configured static routes do not appear in the RIP Routes table.

>> # show ip route

>> # show ip rip routes


Chapter 28. Internet Group Management Protocol

Internet Group Management Protocol (IGMP) is used by IPv4 Multicast routers (Mrouters) to learn about the existence of host group members on their directly attached subnet. The IPv4 Mrouters get this information by broadcasting IGMP Membership Queries and listening for IPv4 hosts reporting their host group memberships. This process is used to set up a client/server relationship between an IPv4 multicast source that provides the data streams and the clients that want to receive the data. The switch supports three versions of IGMP:

IGMPv1: Defines the method for hosts to join a multicast group. However, this version does not define the method for hosts to leave a multicast group. See RFC 1112 for details.

IGMPv2: Adds the ability for a host to signal its desire to leave a multicast group. See RFC 2236 for details.

IGMPv3: Adds support for source filtering by which a host can report interest in receiving packets only from specific source addresses, or from all but specific source addresses, sent to a particular multicast address. See RFC 3376 for details.

The G8272 can perform IGMP Snooping, and connect to static Mrouters.The G8272 can act as a Querier, and participate in the IGMP Querier election process.


“IGMP Terms” on page 388

“How IGMP Works” on page 389

“IGMP Capacity and Default Values” on page 390

“IGMP Snooping” on page 391

“IGMP Relay” on page 404

“Additional IGMP Features” on page 413


IGMP TermsThe following are commonly used IGMP terms:

Multicast traffic: Flow of data from one source to multiple destinations.

Group: A multicast stream to which a host can join. Multicast groups have IP addresses in the range: 224.0.1.0 to 239.255.255.255.

IGMP Querier: A router or switch in the subnet that generates Membership Queries.

IGMP Snooper: A Layer 3 device that forwards multicast traffic only to hosts that are interested in receiving multicast data. This device can be a router or a Layer 3 switch.

Multicast Router: A router configured to make routing decisions for multicast traffic. The router identifies the type of packet received (unicast or multicast) and forwards the packet to the intended destination.

IGMP Proxy: A device that filters Join messages and Leave messages sent upstream to the Mrouter to reduce the load on the Mrouter.

Membership Report: A report sent by the host that indicates an interest in receiving multicast traffic from a multicast group.

Leave: A message sent by the host when it wants to leave a multicast group.

FastLeave: A process by which the switch stops forwarding multicast traffic to a port as soon as it receives a Leave message.

Membership Query: Message sent by the Querier to verify if hosts are listening to a group.

General Query: A Membership Query sent to all hosts. The Group address field for general queries is 0.0.0.0 and the destination address is 224.0.0.1.

Group-specific Query: A Membership Query sent to all hosts in a multicast group.

© Copyright Lenovo 2015 Chapter 28: Internet Group Management Protocol 389

How IGMP WorksWhen IGMP is not configured, switches forward multicast traffic through all ports, increasing network load. When IGMPv2 is configured on a switch, multicast traffic flows as follows:

A server sends multicast traffic to a multicast group.

The Mrouter sends Membership Queries to the switch, which forwards them to all ports in a given VLAN.

Hosts respond with Membership Reports if they want to join a group. The switch forwards these reports to the Mrouter.

The switch forwards multicast traffic only to hosts that have joined a group.

The Mrouter periodically sends Membership Queries to ensure that a host wants to continue receiving multicast traffic. If a host does not respond, the IGMP Snooper stops sending traffic to the host.

The host can initiate the Leave process by sending an IGMP Leave packet to the IGMP Snooper.

When a host sends an IGMPv2 Leave packet, the IGMP Snooper queries to find out if any other host connected to the port is interested in receiving the multicast traffic. If it does not receive a Join message in response, the IGMP Snooper removes the group entry and passes on the information to the Mrouter.

The G8272 supports the following: IGMP version 1, 2, and 3 128 static Mrouters and 128 dynamic MroutersNote: Unknown multicast traffic is sent to all ports if the flood option is enabled and no Membership Report was learned for that specific IGMP group. If the flood option is disabled, unknown multicast traffic is discarded if no hosts or Mrouters are learned on a switch. To enable or disable IGMP flood, use the following command: RS 8272(config)# vlan <vlan ID>RS 8272(config-vlan)# [no] flood


IGMP Capacity and Default ValuesThe following table lists the maximum and minimum values of the G8272 variables.

The following table lists the default settings for IGMP features and variables.

Table 37. G8272 Capacity Table

Variable Maximum

IGMP Entries - Snoop 3072

IGMP Entries - Relay 1000

VLANs - Snoop 1024

VLANs - Relay 8

Static Mrouters 128

Dynamic Mrouters 128

Number of IGMP Filters 16

IPMC Groups (IGMP Relay) 1000

Table 38. IGMP Default Configuration Settings

Field Default Value

Global IGMP State Disabled

IGMP Querier Disabled

IGMP Snooping Disabled

IGMP Filtering Disabled

IP Multicast (IPMC) Flood Enabled

IGMP FastLeave Disabled for all VLANs

IGMP Mrouter Timeout 255 Seconds

IGMP Report Timeout Variable 10 Seconds

IGMP Query-Interval Variable 125 Seconds

IGMP Robustness Variable 2

IGMPv3 Disabled

IGMPv3 number of sources 8 (The switch processes only the first eight sources listed in the IGMPv3 group record.)

Valid range: 1 - 64

IGMPv3 - allow v1v2 Snooping Enabled


IGMP SnoopingIGMP Snooping allows a switch to listen to the IGMP conversation between hosts and Mrouters. By default, a switch floods multicast traffic to all ports in a broadcast domain. With IGMP Snooping enabled, the switch learns the ports interested in receiving multicast data and forwards it only to those ports. IGMP Snooping conserves network resources.

The switch can sense IGMP Membership Reports from attached hosts and acts as a proxy to set up a dedicated path between the requesting host and a local IPv4 Mrouter. After the path is established, the switch blocks the IPv4 multicast stream from flowing through any port that does not connect to a host member, thus conserving bandwidth.

IGMP Querier

For IGMP Snooping to function, you must have an Mrouter on the network that generates IGMP Query packets. Enabling the IGMP Querier feature on the switch allows it to participate in the Querier election process. If the switch is elected as the Querier, it will send IGMP Query packets for the LAN segment.

Querier Election

If multiple Mrouters exist on the network, only one can be configured as a Querier. The Mrouters elect the one with the lowest source IPv4 address or MAC address as the Querier. The Querier performs all periodic membership queries. All other Mrouters (non-Queriers) do not send IGMP Query packets.Note: When IGMP Querier is enabled on a VLAN, the switch performs the role of an IGMP Querier only if it meets the IGMP Querier election criteria.

Each time the Querier switch sends an IGMP Query packet, it initializes a general query timer. If a Querier receives a General Query packet from an Mrouter with a lower IP address or MAC address, it transitions to a non-Querier state and initializes an other querier present timer. When this timer expires, the Mrouter transitions back to the Querier state and sends a General Query packet.

Follow this procedure to configure IGMP Querier.

1. Enable IGMP and configure the source IPv4 address for IGMP Querier on a VLAN.

2. Enable IGMP Querier on the VLAN.

3. Configure the querier election type and define the address.

RS 8272(config)# ip igmp enableRS 8272(config)# ip igmp querier vlan 2 sourceip 10.10.10.1

RS 8272(config)# ip igmp querier vlan 2 enable

RS 8272(config)# ip igmp querier vlan 2 electiontype ipv4



IGMP Groups

One IGMP entry is allocated for each unique join request, based on the VLAN and IGMP group address. If multiple ports join the same IGMP group using the same VLAN, only a single IGMP entry is used.

IGMPv3 Snooping

IGMPv3 includes new Membership Report messages that extend IGMP functionality. The switch provides snooping capability for all types of IGMPv3 Membership Reports.

IGMPv3 supports Source-Specific Multicast (SSM). SSM identifies session traffic by both source and group addresses.

The IGMPv3 implementation keeps records on the multicast hosts present in the network. If a host is already registered, when it receives a new IS_INC, TO_INC, IS_EXC, or TO_EXC report from same host, the switch makes the correct transition to new (port-host-group) registration based on the IGMPv3 RFC. The registrations of other hosts for the same group on the same port are not changed.

The G8272 supports the following IGMPv3 filter modes:

INCLUDE mode: The host requests membership to a multicast group and provides a list of IPv4 addresses from which it wants to receive traffic.

EXCLUDE mode: The host requests membership to a multicast group and provides a list of IPv4 addresses from which it does not want to receive traffic. This indicates that the host wants to receive traffic only from sources that are not part of the Exclude list. To disable snooping on EXCLUDE mode reports, use the following command:

By default, the G8272 snoops the first eight sources listed in the IGMPv3 Group Record. Use the following command to change the number of snooping sources:

RS 8272# show ip igmp querier vlan 2

Current IGMP snooping Querier information: IGMP Querier information for vlan 2: Other IGMP querier none Switchquerier enabled, current state: Querier Switchquerier type: Ipv4, address 10.10.10.1, Switchquerier general query interval: 125 secs, Switchquerier maxresponse interval: 100 'tenths of secs', Switchquerier startup interval: 31 secs, count: 2 Switchquerier robustness: 2 IGMP configured version is v3 IGMP Operating version is v3

RS 8272(config)# no ip igmp snoop igmpv3 exclude

RS 8272(config)# ip igmp snoop igmpv3 sources <1-64>


IGMPv3 Snooping is compatible with IGMPv1 and IGMPv2 Snooping. To disable snooping on version 1 and version 2 reports, use the following command:

RS 8272(config)# no ip igmp snoop igmpv3 v1v2


IGMP Snooping Configuration Guidelines

Consider the following guidelines when you configure IGMP Snooping:

IGMP operation is independent of the routing method. You can use RIP, OSPF, or static routes for Layer 3 routing.

When multicast traffic flood is disabled, the multicast traffic sent by the multicast server is discarded if no hosts or Mrouters are learned on the switch.

The Mrouter periodically sends IGMP Queries.

The switch learns the Mrouter on the port connected to the router when it sees Query messages. The switch then floods the IGMP queries on all other ports including a Trunk Group, if any.

Multicast hosts send IGMP Reports as a reply to the IGMP Queries sent by the Mrouter.

The switch can also learn an Mrouter when it receives a PIM hello packet from another device. However, an Mrouter learned from a PIM packet has a lower priority than an Mrouter learned from an IGMP Query. A switch overwrites an Mrouter learned from a PIM packet when it receives an IGMP Query on the same port.

A host sends an IGMP Leave message to its multicast group. The expiration timer for this group is updated to 10 seconds. The Layer 3 switch sends IGMP Group-Specific Query to the host that had sent the Leave message. If the host does not respond with an IGMP Report during these 10 seconds, all the groups expire and the switch deletes the host from the IGMP groups table. The switch then proxies the IGMP Leave messages to the Mrouter.


IGMP Snooping Configuration Example

This section provides steps to configure IGMP Snooping on the G8272.


2. Add VLANs to IGMP Snooping.

3. Enable IGMP Snooping.

4. Enable IGMPv3 Snooping (optional).

5. Enable the IGMP feature.

6. View dynamic IGMP information.

These commands display information about IGMP Groups and Mrouters learned by the switch.

RS 8272(config)# ip igmp snoop vlan 1

RS 8272(config)# ip igmp snoop enable

RS 8272(config)# ip igmp snoop igmpv3 enable

RS 8272(config)# ip igmp enable

RS 8272# show ip igmp groups

Total entries: 5 Total IGMP groups: 3Note: The <Total IGMP groups> number is computed as

the number of unique (Group, Vlan) entries!Note: Local groups (224.0.0.x) are not snooped/relayed and will not

appear.Source Group VLAN Port Version Mode Expires Fwd 10.1.1.1 232.1.1.1 2 4 V3 INC 4:16 Yes10.1.1.5 232.1.1.1 2 4 V3 INC 4:16 Yes * 232.1.1.1 2 4 V3 INC No10.10.10.43 235.0.0.1 9 1 V3 INC 2:26 Yes * 236.0.0.1 9 1 V3 EXC Yes

RS 8272# show ip igmp mrouter

Total entries: 3 Total number of dynamic mrouters: 2Total number of installed static mrouters: 1

SrcIP VLAN Port Version Expires MRT QRV QQIC 10.1.1.1 2 21 V3 4:09 128 2 12510.1.1.5 2 23 V2 4:09 125 * 9 24 V2 static


Advanced Configuration Example: IGMP Snooping

Figure 32 shows an example topology. Switches B and C are configured with IGMP Snooping.

Figure 32. Topology

Devices in this topology are configured as follows:

STG2 includes VLAN2; STG3 includes VLAN3.

The multicast server sends IP multicast traffic for the following groups: VLAN 2, 225.10.0.11 – 225.10.0.12, Source: 22.10.0.11 VLAN 2, 225.10.0.13 – 225.10.0.15, Source: 22.10.0.13 VLAN 3, 230.0.2.1 – 230.0.2.2, Source: 22.10.0.1 VLAN 3, 230.0.2.3 – 230.0.2.5, Source: 22.10.0.3

The Mrouter sends IGMP Query packets in VLAN 2 and VLAN 3. The Mrouter’s IP address is 10.10.10.10.

The multicast hosts send the following IGMP Reports: IGMPv2 Report, VLAN 2, Group: 225.10.0.11, Source: * IGMPv2 Report, VLAN 3, Group: 230.0.2.1, Source: * IGMPv3 IS_INCLUDE Report, VLAN 2, Group: 225.10.0.13, Source: 22.10.0.13 IGMPv3 IS_INCLUDE Report, VLAN 3, Group: 230.0.2.3, Source: 22.10.0.3

Multicast

Server

Multicast

Host 1

Multicast

Host 2

VLAN 2 VLANs 2,3

Switch B5 6

Switch A

14

Trunk 1VLANs 2, 3

Trunk 2VLANs 2, 3

Trunk 3VLANs 2, 3

VLANs 2,3

1 2

34

Multicast

Host 3

Multicast

Router

VLAN 3 VLANs 2,3

Switch C5 6

34

1 2

5

23


The hosts receive multicast traffic as follows: Host 1 receives multicast traffic for groups (*, 225.10.0.11), (22.10.0.13,

225.10.0.13) Host 2 receives multicast traffic for groups (*, 225.10.0.11), (*, 230.0.2.1),

(22.10.0.13, 225.10.0.13), (22.10.0.3, 230.0.2.3) Host 3 receives multicast traffic for groups (*, 230.0.2.1), (22.10.0.3, 230.0.2.3)

The Mrouter receives all the multicast traffic.

PrerequisitesBefore you configure IGMP Snooping, ensure you have performed the following actions:

Configured VLANs.

Enabled IGMP.

Added VLANs to IGMP Snooping.

Configured a switch or Mrouter as the Querier.

Identified the IGMP version(s) you want to enable.

Disabled IGMP flooding.

ConfigurationThis section provides the configuration details of the switches shown in Figure 32.

Switch A Configuration

1. Configure VLANs and tagging.

2. Configure an IP interface with IPv4 address, and assign a VLAN.

3. Assign a bridge priority lower than the default bridge priority to enable the switch to become the STP root in STG 2 and 3.

RS 8272(config)# interface port 15RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2,3RS 8272(configif)# switchport trunk allowed vlan remove 1RS 8272(configif)# exit

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 10.10.10.1 enableRS 8272(configipif)# vlan 2RS 8272(configipif)# exit

RS 8272(config)# spanningtree stp 2 bridge priority 4096RS 8272(config)# spanningtree stp 3 bridge priority 4096


4. Configure LACP dynamic trunk groups (portchannels).

Switch B Configuration



3. Configure STP. Reset the ports to make the edge configuration operational.




RS 8272(config)# interface port 4RS 8272(configif)# lacp key 200RS 8272(configif)# lacp mode active

RS 8272(config)# interface port 14,6RS 8272(configif)# switchport mode trunkRS 8272(configif)# exit

RS 8272(config)# interface port 16RS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit

RS 8272(config)# interface port 14,6RS 8272(configif)# switchport trunk allowed vlan add 3RS 8272(configif)# exit

RS 8272(config)# interface port 15RS 8272(configif)# switchport trunk allowed vlan remove 1RS 8272(configif)# exit


RS 8272(config)# interface port 5,6RS 8272(configif)# spanningtree portfastRS 8272(configif)# shutdownRS 8272(configif)# no shutdownRS 8272(configif)# exit


4. Configure an LACP dynamic trunk group (portchannel).

5. Configure a static trunk group (portchannel).

6. Configure IGMP Snooping.

Switch C Configuration




RS 8272(config)# portchannel 1 port 3,4 enable

RS 8272(config)# ip igmp enableRS 8272(config)# ip igmp snoop vlan 2,3RS 8272(config)# ip igmp snoop sourceip 10.10.10.2RS 8272(config)# ip igmp snoop igmpv3 enableRS 8272(config)# ip igmp snoop igmpv3 sources 64RS 8272(config)# ip igmp snoop enable

RS 8272(config)# vlan 2RS 8272(configvlan)# no floodRS 8272(configvlan)# exit


RS 8272(config)# interface port 14,6RS 8272(configip)# switchport mode trunkRS 8272(configip)# exit

RS 8272(config)# interface port 14,6RS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit

RS 8272(config)# interface port 16RS 8272(configif)# switchport trunk allowed vlan add 3RS 8272(configif)# exit

RS 8272(config)# interface 16RS 8272(configif)# switchport trunk allowed vlan remove 1RS 8272(configif)# exit



3. Configure STP. Reset the ports to make the edge configuration operational.



6. Configure IGMP Snooping.




RS 8272(config)# ip igmp enableRS 8272(config)# ip igmp snoop vlan 2,3RS 8272(config)# ip igmp snoop sourceip 10.10.10.3RS 8272(config)# ip igmp snoop igmpv3 enableRS 8272(config)# ip igmp snoop igmpv3 sources 64RS 8272(config)# ip igmp snoop enable




Troubleshooting

This section provides the steps to resolve common IGMP Snooping configuration issues. The topology described in Figure 32 is used as an example.

Multicast traffic from non-member groups reaches the host or Mrouter

Check if traffic is unregistered. For unregistered traffic, an IGMP entry is not displayed in the IGMP groups table.

Ensure IPMC flooding is disabled and CPU is enabled.

Check the egress port’s VLAN membership. The ports to which the hosts and Mrouter are connected must be used only for VLAN 2 and VLAN 3.

Note: To avoid such a scenario, disable IPMC flooding for all VLANs enabled on the switches (if this is an acceptable configuration).

Check IGMP Reports on switches B and C for information about the IGMP groups.

If the non-member IGMP groups are displayed in the table, close the application that may be sending the IGMP Reports for these groups. Identify the traffic source by using a sniffer on the hosts and reading the source IP/MAC address. If the source IP/MAC address is unknown, check the port statistics to find the ingress port.

Ensure no static multicast MACs, static multicast groups, or static Mrouters are configured.

Ensure IGMP Relay and PIM are not configured.

Not all multicast traffic reaches the appropriate receivers.

Ensure hosts are sending IGMP Reports for all the groups. Check the VLAN on which the groups are learned.

If some of the groups are not displayed, ensure the multicast application is running on the host device and the generated IGMP Reports are correct.


RS 8272(config)# vlan <vlan id>RS 8272(configvlan)# no floodRS 8272(configvlan)# cpu

RS 8272# show vlan


RS 8272# show interface port <port id> interfacecounters



Ensure multicast traffic reaches the switch to which the host is connected.Close the application sending the IGMP Reports. Clear the IGMP groups by flapping (disabling, then re-enabling) the port.

Note: To clear all IGMP groups, use the following command:RS 8272(config)# clear ip igmp groupsHowever, this will clear all the IGMP groups and will influence other hosts.

Check if the multicast traffic reaches the switch.

If the multicast traffic group is not displayed in the table, check the link state, VLAN membership, and STP convergence.

Ensure multicast server is sending all the multicast traffic.

Ensure no static multicast MACs, static multicast groups, or static multicast routes are configured.

IGMP queries sent by the Mrouter do not reach the host.

Ensure the Mrouter is learned on switches B and C.

If it is not learned on switch B but is learned on switch C, check the link state of the trunk group, VLAN membership, and STP convergence.If it is not learned on any switch, ensure the multicast application is running and is sending correct IGMP Query packets.If it is learned on both switches, check the link state, VLAN membership, and STP port states for the ports connected to the hosts.

IGMP Reports/Leaves sent by the hosts do not reach the Mrouter

Ensure IGMP Queries sent by the Mrouter reach the hosts.

Ensure the Mrouter is learned on both switches. Note that the Mrouter may not be learned on switch B immediately after a trunk group failover/failback.

Ensure the host’s multicast application is started and is sending correct IGMP Reports/Leaves.

A host receives multicast traffic from the incorrect VLAN

Check port VLAN membership.

Check IGMP Reports sent by the host.

Check multicast data sent by the server.

RS 8272# show ip igmp ipmcgrp



RS 8272# show ip igmp groupsRS 8272# show ip igmp counters


The Mrouter is learned on the incorrect trunk group

Check link state. Trunk group 1 might be down or in STP discarding state.

Check STP convergence.

Check port VLAN membership.

Hosts receive multicast traffic at a lower rate than normal

Note: This behavior is expected if IPMC flood is disabled and CPU is enabled. As soon as the IGMP/IPMC entries are installed on ASIC, the IPMC traffic recovers and is forwarded at line rate. This applies to unregistered IPMC traffic.

Ensure a storm control is not configured on the trunks.

Check link speeds and network congestion.

RS 8272(config)# interface port <port id>RS 8272(configif)# no stormcontrol multicast


IGMP RelayThe G8272 can act as an IGMP Relay (or IGMP Proxy) device that relays IGMP multicast messages and traffic between an Mrouter and end stations. IGMP Relay allows the G8272 to participate in network multicasts with no configuration of the various multicast routing protocols, so you can deploy it in the network with minimal effort.

To an IGMP host connected to the G8272, IGMP Relay appears to be an IGMP Mrouter. IGMP Relay sends Membership Queries to hosts, which respond by sending an IGMP response message. A host can also send an unsolicited Join message to the IGMP Relay.

To an Mrouter, IGMP Relay appears as a host. The Mrouter sends IGMP host queries to IGMP Relay, and IGMP Relay responds by forwarding IGMP host reports and unsolicited Join messages from its attached hosts.

IGMP Relay also forwards multicast traffic between the Mrouter and end stations, similar to IGMP Snooping.

You can configure up to two Mrouters to use with IGMP Relay. One Mrouter acts as the primary Mrouter, and one is the backup Mrouter. The G8272 uses health checks to select the primary Mrouter.


Consider the following guidelines when you configure IGMP Relay: IGMP Relay and IGMP Snooping are mutually exclusive—if you enable IGMP

Relay, you must turn off IGMP Snooping/Querier. Add the upstream Mrouter VLAN to the IGMP Relay list, using the following

command:

If IGMP hosts reside on different VLANs, you must: Disable IGMP flooding.

Ensure CPU forwarding is enabled; Ensure that multicast data is forwarded across the VLANs.

RS 8272(config)# ip igmp relay vlan <VLAN number>

RS 8272(config)# vlan <vlan id>RS 8272(configvlan)# no flood

RS 8272(config)# vlan <vlan id>RS 8272(configvlan)# cpu


Configure IGMP Relay

Use the following procedure to configure IGMP Relay.

1. Configure IP interfaces with IPv4 addresses, and assign VLANs.

2. Turn IGMP on.

3. Configure the upstream Mrouters with IPv4 addresses.

4. Enable IGMP Relay and add VLANs to the downstream network.

RS 8272(config)# interface ip 2RS 8272(configipif)# ip address 10.10.1.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 2RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 3RS 8272(configipif)# ip address 10.10.2.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# vlan 3RS 8272(configipif)# enableRS 8272(configipif)# exit


RS 8272(config)# ip igmp relay mrouter 1 address 100.0.1.2RS 8272(config)# ip igmp relay mrouter 1 enableRS 8272(config)# ip igmp relay mrouter 2 address 100.0.2.4RS 8272(config)# ip igmp relay mrouter 2 enable

RS 8272(config)# ip igmp relay vlan 2RS 8272(config)# ip igmp relay vlan 3RS 8272(config)# ip igmp relay enable


Advanced Configuration Example: IGMP Relay

Figure 33 shows an example topology. Switches B and C are configured with IGMP Relay.

Figure 33. Topology

Devices in this topology are configured as follows:

The IP address of Multicast Router 1 is 5.5.5.5

The IP address of Multicast Router 2 is 5.5.5.6

STG 2 includes VLAN2; STG 3 includes VLAN 3; STG 5 includes VLAN 5.

The multicast server sends IP multicast traffic for the following groups: VLAN 2, 225.10.0.11 – 225.10.0.15

The multicast hosts send the following IGMP Reports: Host 1: 225.10.0.11 – 225.10.0.12, VLAN 3 Host 2: 225.10.0.12 – 225.10.0.13, VLAN 2; 225.10.0.14 – 225.10.0.15, VLAN 3 Host 3: 225.10.0.13 – 225.10.0.14, VLAN 2

The Mrouter receives all the multicast traffic.

PrerequisitesBefore you configure IGMP Relay, ensure you have performed the following actions:

Configured VLANs.

Multicast

Server

Multicast

Host 1

Multicast

Host 2

VLAN 3 VLANs 2,3

Switch B5 6

Switch A

14

Trunk 1VLAN 2

Trunk 2VLAN 2

Trunk 3VLAN 2

VLAN 2

1 2

34

Multicast

Host 3

Multicast

Router 1

Multicast

Router 2

VLAN 2 VLAN 5

VLAN 5

Switch C5 6

734

1 2

5

23


Enabled IGMP.

Disabled IGMP flooding.

Disabled IGMP Snooping.

ConfigurationThis section provides the configuration details of the switches in Figure 33.

Switch A Configuration

1. Configure a VLAN.

2. Configure an IP interface with IPv4 address, and assign a VLAN..

3. Assign a bridge priority lower than the default bridge priority to enable the switch to become the STP root in STG 2 and 3.

4. Configure LACP dynamic trunk groups (portchannels).



RS 8272(config)# spanningtree stp 2 bridge priority 4096


RS 8272(config)# interface port 3,4RS 8272(configif)# lacp key 200RS 8272(configif)# lacp mode active


Switch B Configuration


2. Configure IP interfaces with IPv4 addresses, and assign VLANs.

3. Configure STP.



RS 8272(config)# interface port 14,6RS 8272(configif)# switchport mode trunkRS 8272(configif)# switchport trunk allowed vlan add 2RS 8272(configif)# exit




RS 8272(config)# ip gateway 2 address 2.2.2.30 enable





6. Configure IGMP Relay.

Switch C Configuration

1. Configure VLANs.

2. Configure IP interfaces with IPv4 addresses and assign VLANs.

3. Configure STP.

4. Configure LACP dynamic trunk group (portchannel).

RS 8272(config)# ip igmp enableRS 8272(config)# ip igmp relay vlan 2,3RS 8272(config)# ip igmp relay mrouter 1 address 5.5.5.5 enableRS 8272(config)# ip igmp relay mrouter 2 address 5.5.5.6 enableRS 8272(config)# ip igmp relay enable







RS 8272(config)# ip gateway 2 address 2.2.2.20 enable

RS 8272(config)# interface port 5,6,7RS 8272(configif)# spanningtree portfastRS 8272(configif)# shutdownRS 8272(configif)# no shutdownRS 8272(configif)# exit




6. Enable IGMP.

7. Configure IGMP Relay.

Troubleshooting

This section provides the steps to resolve common IGMP Relay configuration issues. The topology described in Figure 33 is used as an example.

Multicast traffic from non-member groups reaches the hosts or the Mrouter

Ensure IPMC flood is disabled.

Check the egress port’s VLAN membership. The ports to which the hosts and Mrouter are connected must be used only for VLAN 2, VLAN 3, or VLAN 5.

Note: To avoid such a scenario, disable IPMC flooding for all VLANs enabled on the switches (if this is an acceptable configuration).



RS 8272(config)# ip igmp relay vlan 2,5RS 8272(config)# ip igmp relay mrouter 1 address 5.5.5.5 enableRS 8272(config)# ip igmp relay mrouter 2 address 5.5.5.6 enableRS 8272(config)# ip igmp relay enable



RS 8272(config)# vlan <vlan id>RS 8272(configvlan)# no flood

RS 8272(config)# show vlan


Check IGMP Reports on switches B and C for information about IGMP groups.

If non-member IGMP groups are displayed in the table, close the application that may be sending the IGMP Reports for these groups. Identify the traffic source by using a sniffer on the hosts and reading the source IP address/MAC address. If the source IP address/MAC address is unknown, check the port statistics to find the ingress port.

Ensure no static multicast MACs and static Mrouters are configured.

Not all multicast traffic reaches the appropriate receivers

Ensure hosts are sending IGMP Reports for all the groups. Check the VLAN on which the groups are learned.

If some of the groups are not displayed, ensure the multicast application is running on the host device and the generated IGMP Reports are correct.

Ensure the multicast traffic reaches the switch to which the host is connected.Close the application sending the IGMP Reports. Clear the IGMP groups by flapping (disabling, then re-enabling) the port.

Note: To clear all IGMP groups, use the following command:RS 8272(config)# clear ip igmp groupsHowever, this will clear all the IGMP groups and will influence other hosts.

Check if the multicast traffic reaches the switch.

If the multicast traffic group is not displayed in the table, check the link state, VLAN membership, and STP convergence.

Ensure the multicast server is sending all the multicast traffic.

Ensure no static multicast MACs or static multicast routes are configured.

Ensure PIM is not enabled on the switches.

IGMP Reports/Leaves sent by the hosts do not reach the Mrouter

Ensure that the primary or secondary Mrouter is reachable. If not, the IGMP Reports/Leaves are not forwarded. Note that the Mrouter may not be reachable immediately after a trunk group failover/failback.

RS 8272(config)# show ip igmp groups

RS 8272(config)# show interface port <port id> interfacecounters


RS 8272(config)# show ip igmp ipmcgrp



Ensure the host’s multicast application is started and is sending correct IGMP Reports/Leaves.

The Mrouter is reachable on the incorrect trunk group

Check link state. Trunk group 1 may be down or in STP discarding state.

Check STP convergence and port VLAN membership.

Check IP connectivity between the switch and the configured Mrouter (primary or secondary).

Hosts receive multicast traffic at a lower rate than normal

Ensure a multicast threshold is not configured on the trunk groups.

Check link speeds and network congestion.

RS 8272(config)# show ip igmp groupsRS 8272(config)# show ip igmp counters

RS 8272(config)# interface port <port id>RS 8272(configif)# no stormcontrol multicast


Additional IGMP FeaturesThe following topics are discussed in this section:

“FastLeave” on page 413

“IGMP Filtering” on page 413

“Static Multicast Router” on page 414

FastLeave

In normal IGMP operation, when the switch receives an IGMPv2 Leave message, it sends a Group-Specific Query to determine if any other devices in the same group (and on the same port) are still interested in the specified multicast group traffic. The switch removes the affiliated port from that particular group, if the switch does not receive an IGMP Membership Report within the query-response-interval.

With FastLeave enabled on the VLAN, a port can be removed immediately from the port list of the group entry when the IGMP Leave message is received. Note: Only IGMPv2 supports FastLeave. Enable FastLeave on ports that have only one host connected. If more than one host is connected to a port, you may lose some hosts unexpectedly.

Use the following command to enable FastLeave.

IGMP Filtering

With IGMP filtering, you can allow or deny certain IGMP groups to be learned on a port.

If access to a multicast group is denied, IGMP Membership Reports from the port are dropped, and the port is not allowed to receive IPv4 multicast traffic from that group. If access to the multicast group is allowed, Membership Reports from the port are forwarded for normal processing.

To configure IGMP filtering, you must globally enable IGMP filtering, define an IGMP filter, assign the filter to a port, and enable IGMP filtering on the port. To define an IGMP filter, you must configure a range of IPv4 multicast groups, choose whether the filter will allow or deny multicast traffic for groups within the range, and enable the filter.

Configuring the Range

Each IGMP filter allows you to set a start and end point that defines the range of IPv4 addresses upon which the filter takes action. Each IPv4 address in the range must be between 224.0.0.0 and 239.255.255.255.

Configuring the Action

Each IGMP filter can allow or deny IPv4 multicasts to the range of IPv4 addresses configured. If you configure the filter to deny IPv4 multicasts, then IGMP Membership Reports from multicast groups within the range are dropped. You can

RS 8272(config)# ip igmp fastleave <VLAN number>


configure a secondary filter to allow IPv4 multicasts to a small range of addresses within a larger range that a primary filter is configured to deny. The two filters work together to allow IPv4 multicasts to a small subset of addresses within the larger range of addresses.Note: Lower-numbered filters take precedence over higher-number filters. For example, the action defined for IGMP filter 1 supersedes the action defined for IGMP filter 2.

Configure IGMP Filtering

1. Enable IGMP filtering on the switch.

2. Define an IGMP filter with IPv4 information.

3. Assign the IGMP filter to a port.

Static Multicast Router

A static Mrouter can be configured for a particular port on a particular VLAN. A static Mrouter does not have to be learned through IGMP Snooping. Any data port can accept a static Mrouter.

When you configure a static Mrouter on a VLAN, it replaces any dynamic Mrouters learned through IGMP Snooping.

Configure a Static Multicast Router

1. For each Mrouter, configure a port, VLAN, and IGMP version of the multicast router.


RS 8272(config)# ip igmp filtering

RS 8272(config)# ip igmp profile 1 range 224.0.0.0 226.0.0.0RS 8272(config)# ip igmp profile 1 action denyRS 8272(config)# ip igmp profile 1 enable

RS 8272(config)# interface port 3RS 8272(configif)# ip igmp profile 1RS 8272(configif)# ip igmp filtering

RS 8272(config)# ip igmp mrouter 5 1 2

RS 8272(config)# show ip igmp mrouter


Chapter 295. Multicast Listener Discovery

Multicast Listener Discovery (MLD) is an IPv6 protocol that a host uses to request multicast data for a multicast group. An IPv6 router uses MLD to discover the presence of multicast listeners (nodes that want to receive multicast packets) on its directly attached links, and to discover specifically the multicast addresses that are of interest to those neighboring nodes.

MLD version 1 is derived from Internet Group Management Protocol version 2 (IGMPv2) and MLDv2 is derived from IGMPv3. MLD uses ICMPv6 (IP Protocol 58) message types. See RFC 2710 and RFC 3810 for details.

MLDv2 protocol, when compared to MLDv1, adds support for source filtering—the ability for a node to report interest in listening to packets only from specific source addresses, or from all but specific source addresses, sent to a particular multicast address. MLDv2 is interoperable with MLDv1. See RFC 3569 for details on Source-Specific Multicast (SSM).


“MLD Terms” on page 416

“How MLD Works” on page 417

“MLD Capacity and Default Values” on page 420

“Configuring MLD” on page 421


MLD TermsFollowing are the commonly used MLD terms:

Multicast traffic: Flow of data from one source to multiple destinations.

Group: A multicast stream to which a host can join.

Multicast Router (Mrouter): A router configured to make routing decisions for multicast traffic. The router identifies the type of packet received (unicast or multicast) and forwards the packet to the intended destination.

Querier: An Mrouter that sends periodic query messages. Only one Mrouter on the subnet can be elected as the Querier.

Multicast Listener Query: Messages sent by the Querier. There are three types of queries: General Query: Sent periodically to learn multicast address listeners from an

attached link. G8272 uses these queries to build and refresh the Multicast Address Listener state. General Queries are sent to the link-scope all-nodes multicast address (FF02::1), with a multicast address field of 0, and a maximum response delay of query response interval.

Multicast Address Specific Query: Sent to learn if a specific multicast address has any listeners on an attached link. The multicast address field is set to the IPv6 multicast address.

Multicast Address and Source Specific Query: Sent to learn if, for a specified multicast address, there are nodes still listening to a specific set of sources. Supported only in MLDv2.

Note: Multicast Address Specific Queries and Multicast Address and Source Specific Queries are sent only in response to State Change Reports, and never in response to Current State Reports.

Multicast Listener Report: Sent by a host when it joins a multicast group, or in response to a Multicast Listener Query sent by the Querier. Hosts use these reports to indicate their current multicast listening state, or changes in the multicast listening state of their interfaces. These reports are of two types: Current State Report: Contains the current Multicast Address Listening State

of the host. State Change Report: If the listening state of a host changes, the host

immediately reports these changes through a State Change Report message. These reports contain either Filter Mode Change records and/or Source List Change records. State Change Reports are retransmitted several times to ensure all Mrouters receive it.

Multicast Listener Done: Sent by a host when it wants to leave a multicast group. This message is sent to the link-scope all-routers IPv6 destination address of FF02::2. When an Mrouter receives a Multicast Listener Done message from the last member of the multicast address on a link, it stops forwarding traffic to this multicast address.

© Copyright Lenovo 2015 Chapter 29: Multicast Listener Discovery 417

How MLD WorksThe software uses the information obtained through MLD to maintain a list of multicast group memberships for each interface and forwards the multicast traffic only to interested listeners.

Without MLD, the switch forwards IPv6 multicast traffic through all ports, increasing network load. Following is an overview of operations when MLD is configured on the G8272:

The switch acts as an Mrouter when MLDv1/v2 is configured and enabled on each of its directly attached links. If the switch has multiple interfaces connected to the same link, it operates the protocol on any one of the interfaces.

If there are multiple Mrouters on the subnet, the Mrouter with the numerically lowest IPv6 address is elected as the Querier.

The Querier sends general queries at short intervals to learn multicast address listener information from an attached link.

Hosts respond to these queries by reporting their per-interface Multicast Address Listening state, through Current State Report messages sent to a specific multicast address that all MLD routers on the link listen to.

If the listening state of a host changes, the host immediately reports these changes through a State Change Report message.

The Querier sends a Multicast Address Specific Query to verify if hosts are listening to a specified multicast address or not. Similarly, if MLDv2 is configured, the Querier sends a Multicast Address and Source Specific Query to verify, for a specified multicast address, if hosts are listening to a specific set of sources, or not. MLDv2 listener report messages consists of Multicast Address Records: INCLUDE: to receive packets from source specified in the MLDv2 message EXCLUDE: to receive packets from all sources except the ones specified in the

MLDv2 message

A host can send a State Change Report to indicate its desire to stop listening to a particular multicast address (or source in MLDv2). The Querier then sends a multicast address specific query to verify if there are other listeners of the multicast address. If there aren’t any, the Mrouter deletes the multicast address from its Multicast Address Listener state and stops sending multicast traffic. Similarly in MLDv2, the Mrouter sends a Multicast Address and Source Specific Query to verify if, for a specified multicast address, there are hosts still listening to a specific set of sources.

G8272 supports MLD versions 1 and 2.Note: MLDv2 operates in version 1 compatibility mode when, in a specific network, not all hosts are configured with MLDv2.


How Flooding Impacts MLD

When flood option is disabled, the unknown multicast traffic is discarded if no Mrouters are learned on the switch. You can set the flooding behavior by configuring the flood and cpu options. You can optimize the flooding to ensure that unknown IP multicast (IPMC) data packets are not dropped during the learning phase.

The flooding options include:

flood: Enable hardware flooding in VLAN for the unregistered IPMC; This option is enabled by default.

cpu: Enable sending unregistered IPMC to the Mrouter ports. However, during the learning period, there will be some packet loss. The cpu option is enabled by default. You must ensure that the flood and optflood options are disabled.

optflood: Enable optimized flooding to allow sending the unregistered IPMC to the Mrouter ports without having any packet loss during the learning period; This option is disabled by default; When optflood is enabled, the flood and cpu settings are ignored.

The flooding parameters must be configured per VLAN. Enter the following command to set the flood or cpu option:

MLD Querier

An Mrouter acts as a Querier and periodically (at short query intervals) sends query messages in the subnet. If there are multiple Mrouters in the subnet, only one can be the Querier. All Mrouters on the subnet listen to the messages sent by the multicast address listeners, and maintain the same multicast listening information state.

All MLDv2 queries are sent with the FE80::/64 link-local source address prefix.

Querier Election

Only one Mrouter can be the Querier per subnet. All other Mrouters will be non-Queriers. MLD versions 1 and 2 elect the Mrouter with the numerically lowest IPv6 address as the Querier.

If the switch is configured as an Mrouter on a subnet, it also acts as a Querier by default and sends multiple general queries. If the switch receives a general query from another Querier with a numerically lower IPv6 address, it sets the other querier present timer to the other querier present timeout, and changes its state to non-Querier. When the other querier present timer expires, it regains the Querier state and starts sending general queries.Note: When MLD Querier is enabled on a VLAN, the switch performs the role of an MLD Querier only if it meets the MLD Querier election criteria.

RS 8272(config)# vlan <vlan number>RS 8272(configvlan)# [no] floodRS 8272(configvlan)# [no] cpuRS 8272(configvlan)# [no] optflood


Dynamic Mrouters

The switch learns Mrouters on the ingress VLANs of the MLD-enabled interface. All report or done messages are forwarded to these Mrouters. By default, the option of dynamically learning Mrouters is disabled. To enable it, use the following command:

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# ipv6 mld dmrtr enable


MLD Capacity and Default ValuesTable 39 lists the maximum and minimum values of the G8272 variables.

Note: IGMP and MLD share the IPMC table. When the IPMC table is full, you cannot allocate additional IGMP/MLD groups.

Table 40 lists the default settings for MLD features and variables.

Table 39. G8272 Capacity Table

Variable Maximum Value

IPv6 Multicast Entries 256

IPv6 Interfaces for MLD 8

Table 40. MLD Timers and Default Values

Field Default Value

Robustness Variable (RV) 2

Query Interval (QI) 125 seconds

Query Response Interval (QRI) 10 seconds

Multicast Address Listeners Interval (MALI)

260 seconds [derived: RV*QI+QRI]

Other Querier Present Interval [OQPT] 255 seconds [derived: RV*QI + ½ QRI]

Start up Query Interval [SQI] 31.25 seconds [derived: ¼ * QI]

Startup Query Count [SQC] 2 [derived: RV]

Last Listener Query Interval [LLQI] 1 second

Last Listener Query Count [LLQC] 2 [derived: RV]

Last Listener Query Time [LLQT] 2 seconds [derived: LLQI * LLQT]

Older Version Querier Present Timeout: [OVQPT]

260 seconds [derived: RV*QI+ QRI]

Older Version Host Present Interval [OVHPT]

260 seconds [derived: RV* QI+QRI]


Configuring MLDFollowing are the steps to enable MLD and configure the interface parameters:

1. Turn on MLD globally.

2. Create an IPv6 interface.

3. Enable MLD on the IPv6 interface.

4. Configure the MLD parameters on the interface: version, robustness, query response interval, MLD query interval, and last listener query interval.

RS 8272(config)# ipv6 mldRS 8272(configroutermld)# enableRS 8272(configroutermld)# exit

RS 8272(config)# interface ip 2RS 8272(configipif)# enableRS 8272(configipif)# ipv6 address 2002:1:0:0:0:0:0:3RS 8272(configipif)# ipv6 prefixlen 64

RS 8272(configipif)# ipv6 mld enable

RS 8272(configipif)# ipv6 mld version <1-2>(MLD version)RS 8272(configipif)# ipv6 mld robust <1-10>(Robustness)RS 8272(configipif)# ipv6 mld qri <1-256>(In seconds)RS 8272(configipif)# ipv6 mld qintrval <1-608>(In seconds)RS 8272(configipif)# ipv6 mld llistnr <1-32>(In seconds)



Chapter 30. Border Gateway Protocol

Border Gateway Protocol (BGP) is an Internet protocol that enables routers on an IPv4 network to share and advertise routing information with each other about the segments of the IPv4 address space they can access within their network and with routers on external networks. BGP allows you to decide what is the “best” route for a packet to take from your network to a destination on another network rather than simply setting a default route from your border router(s) to your upstream provider(s). BGP is defined in RFC 1771.

RackSwitch G8272s can advertise their IP interfaces and IPv4 addresses using BGP and take BGP feeds from as many as 96 BGP router peers. This allows more resilience and flexibility in balancing traffic from the Internet.Note: Lenovo Networking OS 8.2 does not support IPv6 for BGP.


“Internal Routing Versus External Routing” on page 424

“Forming BGP Peer Routers” on page 428

“Loopback Interfaces” on page 430

“What is a Route Map?” on page 430

“Aggregating Routes” on page 434

“Redistributing Routes” on page 434

“BGP Attributes” on page 436

“Selecting Route Paths in BGP” on page 438

“BGP Failover Configuration” on page 439

“Default Redistribution and Route Aggregation Example” on page 441


Internal Routing Versus External RoutingTo ensure effective processing of network traffic, every router on your network needs to know how to send a packet (directly or indirectly) to any other location/destination in your network. This is referred to as internal routing and can be done with static routes or using active, internal dynamic routing protocols, such as RIP, RIPv2, and OSPF.

Static routes must have a higher degree of precedence than dynamic routing protocols. If the destination route is not in the route cache, the packets are forwarded to the default gateway which may be incorrect if a dynamic routing protocol is enabled.

It is also useful to tell routers outside your network (upstream providers or peers) about the routes you can access in your network. External networks (those outside your own) that are under the same administrative control are referred to as autonomous systems (AS). Sharing of routing information between autonomous systems is known as external routing.

External BGP (eBGP) is used to exchange routes between different autonomous systems whereas internal BGP (iBGP) is used to exchange routes within the same autonomous system. An iBGP is a type of internal routing protocol you can use to do active routing inside your network. It also carries AS path information, which is important when you are an ISP or doing BGP transit.

The iBGP peers have to maintain reciprocal sessions to every other iBGP router in the same AS (in a full-mesh manner) to propagate route information throughout the AS. If the iBGP session shown between the two routers in AS 20 was not present (as indicated in Figure 34), the top router would not learn the route to AS 50, and the bottom router would not learn the route to AS 11, even though the two AS 20 routers are connected via the RackSwitch G8272.

Figure 34. iBGP and eBGP

When there are many iBGP peers, having a full-mesh configuration results in large number of sessions between the iBGP peers. In such situations, configuring a route reflector eliminates the full-mesh configuration requirement, prevents route propagation loops, and provides better scalability to the peers. For details, see “Route Reflector” on page 425.

InternetInternet

© Copyright Lenovo 2015 Chapter 30: Border Gateway Protocol 425

Typically, an AS has one or more border routers—peer routers that exchange routes with other ASs—and an internal routing scheme that enables routers in that AS to reach every other router and destination within that AS. When you advertise routes to border routers on other autonomous systems, you are effectively committing to carry data to the IPv4 space represented in the route being advertised. For example, if you advertise 192.204.4.0/24, you are declaring that if another router sends you data destined for any address in 192.204.4.0/24, you know how to carry that data to its destination.

Route Reflector

The Lenovo N/OS implementation conforms to the BGP Route Reflection specification defined in RFC 4456.

As per RFC 1771 specification, a route received from an iBGP peer cannot be advertised to another iBGP peer. This makes it mandatory to have full-mesh iBGP sessions between all BGP routers within an AS. A route reflector—a BGP router—breaks this iBGP loop avoidance rule. It does not affect the eBGP behavior. A route reflector is a BGP speaker that advertises a route learnt from an iBGP peer to another iBGP peer. The advertised route is called the reflected route.

A route reflector has two groups of internal peers: clients and non-clients. A route reflector reflects between these groups and among the clients. The non-client peers must be fully meshed. The route reflector and its clients form a cluster.

When a route reflector receives a route from an iBGP peer, it selects the best path based on its path selection rule. It then does the following based on the type of peer it received the best path from:

A route received from a non-client iBGP peer is reflected to all clients.

A route received from an iBGP client peer is reflected to all iBGP clients and iBGP non-clients.

In Figure 35, the G8272 is configured as a route reflector. All clients and non-clients are in the same AS.


Figure 35. iBGP Route Reflector

The following attributes are used by the route reflector functionality:

ORIGINATOR ID: BGP identifier (BGP router ID) of the route originator in the local AS. If the route does not have the ORIGINATOR ID attribute (it has not been reflected before), the router ID of the iBGP peer from which the route has been received is copied into the Originator ID attribute.This attribute is never modified by subsequent route reflectors. A router that identifies its own ID as the ORIGINATOR ID, it ignores the route.

CLUSTER LIST: Sequence of the CLUSTER ID (i.e. router ID) values representing the reflection path that the route has passed. The value configured with the RS 8272(configrouterbgp)# clusterid <ID> command (or the router ID of the route reflector if the cluster-id is not configured) is prepended to the Cluster list attribute. If a route reflector detects its own CLUSTER ID in the CLUSTER LIST, it ignores the route. Up to 10 CLUSTER IDs can be added to a CLUSTER LIST.

Route reflection functionality can be configured as follows:

1. Configure an AS.

2. Configure a route reflector client.

Route Reflector

Cluster

iBGP iBGP

iBGPiBGP

iBGP

RR Client RR Client

RR Non-Client RR Non-Client

RS 8272(config)# router bgpRS 8272(configrouterbgp)# as 22RS 8272(configrouterbgp)# enable

RS 8272(configrouterbgp)# neighbor 2 remoteaddress 10.1.50.1RS 8272(configrouterbgp)# neighbor 2 remoteas 22RS 8272(configrouterbgp)# neighbor 2 routereflectorclientRS 8272(configrouterbgp)# no neighbor 2 shutdown


Note: When a client is configured on the G8272, the switch automatically gets configured as a route reflector.

3. Verify configuration.

Once configured as a route reflector, the switch, by default, passes routes between clients. If required, you can disable this by using the following command:

You can view the route reflector BGP attributes attached to a BGP route using the following command:

RestrictionsConsider the following restrictions when configuring route reflection functionality:

When a CLUSTER ID is changed, all iBGP sessions are restarted.

When a route reflector client is enabled/disabled, the session is restarted.

RS 8272(config)# show ip bgp neighbor 2 information

BGP Peer 2 Information: 2: 10.1.50.1 , version 0, TTL 255, TTL Security hops 0 Remote AS: 0, Local AS: 22, Link type: IBGP Remote router ID: 0.0.0.0, Local router ID: 9.9.9.9 nexthopself disabled RR client enabled BGP status: connect, Old status: connect Total received packets: 0, Total sent packets: 0 Received updates: 0, Sent updates: 0 Keepalive: 0, Holdtime: 0, MinAdvTime: 60 LastErrorCode: unknown(0), LastErrorSubcode: unspecified(0) Established state transitions: 0

RS 8272(configrouterbgp)# no clienttoclient reflection

RS 8272(configrouterbgp)# show ip bgp information 5.0.0.0 255.255.255.0BGP routing table entry for 5.0.0.0/255.255.255.0Paths: (1 available, best #1)Multipath: eBGP Local 30.1.1.1 (metric 0) from 22.22.1.1(17.17.17.17) Origin: IGP, localpref 0, valid, internal, best Originator: 1.16.0.195 Cluster list: 17.17.17.17


Forming BGP Peer RoutersTwo BGP routers become peers or neighbors once you establish a TCP connection between them. You can configure BGP peers statically or dynamically. While it may be desirable to configure static peers for security reasons, dynamic peers prove to be useful in cases where the remote address of the peer is unknown. For example in B-RAS applications, where subscriber interfaces are dynamically created and the address is assigned dynamically from a local pool or by using RADIUS.

For each new route, if a peer is interested in that route (for example, if a peer would like to receive your static routes and the new route is static), an update message is sent to that peer containing the new route. For each route removed from the route table, if the route has already been sent to a peer, an update message containing the route to withdraw is sent to that peer.

For each Internet host, you must be able to send a packet to that host, and that host has to have a path back to you. This means that whoever provides Internet connectivity to that host must have a path to you. Ultimately, this means that they must “hear a route” which covers the section of the IPv4 space you are using; otherwise, you will not have connectivity to the host in question.

Static Peers

You can configure BGP static peers by using the following commands:

Static peers always take precedence over dynamic peers. Consider the following:

If the remote address of an incoming BGP connection matches both a static peer address and an IP address from a dynamic group, the peer is configured statically and not dynamically.

If a new static peer is enabled while a dynamic peer for the same remote address exists, BGP automatically removes the dynamic peer.

If a new static peer is enabled when the maximum number of BGP peers were already configured, then BGP deletes the dynamic peer that was last created and adds the newly created static peer. A syslog will be generated for the peer that was deleted.

Dynamic Peers

To configure dynamic peers, you must define a range of IP addresses for a group. BGP waits to receive an open message initiated from BGP speakers within that range. Dynamic peers are automatically created when a peer group member accepts the incoming BGP connection. Dynamic peers are passive. When they are not in the established state, they accept inbound connections but do not initiate outbound connections.

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor <1-96> remoteaddress <IP address>RS 8272(configrouterbgp)# neighbor <1-96> remoteas <1-65535>RS 8272(configrouterbgp)# no neighbor <1-96> shutdown


You can configure up to 6 AS numbers per group. When the BGP speaker receives an open message from a dynamic peer, the AS number from the packet must match one of the remote AS numbers configured on the corresponding group.

When you delete a remote AS number, all dynamic peers established from that remote AS will be deleted.

You can define attributes for the dynamic peers only at the group level. You cannot configure attributes for any one dynamic peer. All static peer attributes, except the BGP passive mode, can also be configured for groups.

To set the maximum number of dynamic peers for a group that can simultaneously be in an established state, enter the following command:

If you reset this limit to a lower number, and if the dynamic peers already established for the group are higher than this new limit, then BGP deletes the last created dynamic peer(s) until the new limit is reached.Note: The maximum number of static and dynamic peers established simultaneously cannot exceed the maximum peers, i.e. 96, that the switch can support. If the maximum peers are established, no more dynamic peers will be enabled even if the maximum dynamic peers limit you had configured for the groups was not reached.

Given below are the basic commands for configuring dynamic peers:

Removing Dynamic Peers

You cannot remove dynamic peers manually. However, you can stop a dynamic peer using the following command:

The stop command interrupts the BGP connection until the peer tries to re-establish the connection.

Also, when a dynamic peer state changes from established to idle, BGP removes the dynamic peer.

RS 8272(configrouterbgp)# neighbor group <1-8> listen limit <1-96>

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor group <1-8> listen range <IP address> <subnet mask> (Define IP address range)RS 8272(configrouterbgp)# neighbor group <1-8> remoteas <1-65535> alternateas <1-65535> (Enter up to 5 alternate AS numbers)RS 8272(configrouterbgp)# no neighbor group <1-8> shutdown

RS 8272(config)# router bgp stop <neighbor number>


Loopback InterfacesIn many networks, multiple connections may exist between network devices. In such environments, it may be useful to employ a loopback interface for a common BGP router address, rather than peering the switch to each individual interface.Note: To ensure that the loopback interface is reachable from peer devices, it must be advertised using an interior routing protocol (such as OSPF), or a static route must be configured on the peer.

To configure an existing loopback interface for BGP neighbor, use the following commands:

What is a Route Map?A route map is used to control and modify routing information. Route maps define conditions for redistributing routes from one routing protocol to another or controlling routing information when injecting it in and out of BGP. For example, a route map is used to set a preference value for a specific route from a peer router and another preference value for all other routes learned via the same peer router. For example, the following command is used to enter the Route Map mode for defining a route map:

A route map allows you to match attributes, such as metric, network address, and AS number. It also allows users to overwrite the local preference metric and to append the AS number in the AS route. See “BGP Failover Configuration” on page 439.

Lenovo N/OS allows you to configure 255 route maps. Each route map can have up to 32 access lists. Each access list consists of a network filter. A network filter defines an IPv4 address and subnet mask of the network that you want to include in the filter. Figure 36 illustrates the relationship between route maps, access lists, and network filters.

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor <#> updatesource loopback <1-5>RS 8272(configrouterbgp)# exit

RS 8272(config)# routemap <map number> (Select a route map)RS 8272(configroutemap)# ? (List available commands)


Figure 36. Distributing Network Filters in Access Lists and Route Maps

Next Hop Peer IP AddressNext hop peer IP address can be configured only for route maps used in BGP. When a route map is applied on ingress, the next hop of learnt routes is replaced with peer IP address. When applied on egress, the next hop of the redistributed routes is replaced with the local IP address.

Incoming and Outgoing Route Maps

You can have two types of route maps: incoming and outgoing. A BGP peer router can be configured to support up to eight route maps in the incoming route map list and outgoing route map list.

If a route map is not configured in the incoming route map list, the router imports all BGP updates. If a route map is configured in the incoming route map list, the router ignores all unmatched incoming updates. If you set the action to deny, you must add another route map to permit all unmatched updates.

Route maps in an outgoing route map list behave similar to route maps in an incoming route map list. If a route map is not configured in the outgoing route map list, all routes are advertised or permitted. If a route map in the outgoing route map list is set to permit, matched routes are advertised and unmatched routes are ignored.

Access Lists (alist)

Network Filter (nwf)

Route Maps (rmap)

1

Route Map 1

32

1

8

1

Route Map 2

32

9

16

1

Route Map 255

32

249

256

------

---

------

---

------

---

RS 8272(config)# routemap <map number>RS 8272(configroutermap)# set ip nexthop <peer IP address>


Precedence

You can set a priority to a route map by specifying a precedence value with the following command (Route Map mode):

The smaller the value the higher the precedence. If two route maps have the same precedence value, the smaller number has higher precedence.

Configuration Overview

To configure route maps, you need to do the following:

1. Define a network filter.

Enter a filter number from 1 to 256. Specify the IPv4 address and subnet mask of the network that you want to match. Enable the network filter. You can distribute up to 256 network filters among 64 route maps each containing 32 access lists.

2. (Optional) Define the criteria for the access list and enable it.

Specify the access list and associate the network filter number configured in Step 1.

Steps 2 and 3 are optional, depending on the criteria that you want to match. In Step 2, the network filter number is used to match the subnets defined in the network filter. In Step 3, the autonomous system number is used to match the subnets. Or, you can use both (Step 2 and Step 3) criteria: access list (network filter) and access path (AS filter) to configure the route maps.

3. (Optional) Configure the AS filter attributes.

4. (Optional) Set up the BGP attributes.

If you want to overwrite the attributes that the peer router is sending, define the following BGP attributes:

Specify up to three AS numbers that you want to prepend to a matched route and the local preference for the matched route.

RS 8272(config)# routemap <map number> (Select a route map)RS 8272(configroutemap)# precedence <1-255>(Specify a precedence)RS 8272(configroutemap)# exit

RS 8272(config)# ip matchaddress 1 <IPv4 address> <IPv4 subnet mask> RS 8272(config)# ip matchaddress 1 enable

RS 8272(config)# routemap 1RS 8272(configroutemap)# accesslist 1 matchaddress 1RS 8272(configroutemap)# accesslist 1 metric <metric value> RS 8272(configroutemap)# accesslist 1 action denyRS 8272(configroutemap)# accesslist 1 enable

RS 8272(configroutemap)# aspathlist 1 as 1RS 8272(configroutemap)# aspathlist 1 action denyRS 8272(configroutemap)# aspathlist 1 enable


Specify the metric [Multi Exit Discriminator (MED)] for the matched route.

5. Enable the route map.

6. Turn BGP on.

7. Assign the route map to a peer router.

Select the peer router and then add the route map to the incoming route map list,

or to the outgoing route map list.

8. Exit Router BGP mode.

RS 8272(configroutemap)# aspathpreference <AS number> [<AS number>] [<AS number>]

RS 8272(configroutemap)# localpreference <local preference value>RS 8272(configroutemap)# metric <metric value>

RS 8272(configroutemap)# enableRS 8272(configroutemap)# exit

RS 8272(config)# router bgpRS 8272(configrouterbgp)# enable

RS 8272(configrouterbgp)# neighbor 1 routemap in <1-255>

RS 8272(configrouterbgp)# neighbor 1 routemap out <1-255>

RS 8272(configrouterbgp)# exit


Aggregating RoutesAggregation is the process of combining several different routes in such a way that a single route can be advertised, which minimizes the size of the routing table. You can configure aggregate routes in BGP either by redistributing an aggregate route into BGP or by creating an aggregate entry in the BGP routing table.

To define an aggregate route in the BGP routing table, use the following commands:

The origin code for the aggregated route is either IGP or INCOMPLETE.

An example of creating a BGP aggregate route is shown in “Default Redistribution and Route Aggregation Example” on page 441.

Redistributing RoutesIn addition to running multiple routing protocols simultaneously, N/OS software can redistribute information from one routing protocol to another. For example, you can instruct the switch to use BGP to re-advertise static routes. This applies to all of the IP-based routing protocols.

You can also conditionally control the redistribution of routes between routing domains by defining a method known as route maps between the two domains. For more information on route maps, see “What is a Route Map?” on page 430. Redistributing routes is another way of providing policy control over whether to export OSPF routes, fixed routes, and static routes. For an example configuration, see “Default Redistribution and Route Aggregation Example” on page 441.

Default routes can be configured using the following methods:

Import

Originate—The router sends a default route to peers if it does not have any default routes in its routing table.

Redistribute—Default routes are either configured through the default gateway or learned via other protocols and redistributed to peer routers. If the default routes are from the default gateway, enable the static routes because default routes from the default gateway are static routes. Similarly, if the routes are learned from another routing protocol, make sure you enable that protocol for redistribution.

None

The origin code for the redistributed routes is INCOMPLETE.

>> # router bgp>> (configrouterbgp)# aggregateaddress <1-16> <IPv4 address> <mask>>> (configrouterbgp)# aggregateaddress <1-16> enable


BGP CommunitiesBGP communities are attribute tags that allow controlled distribution of routing information based on an agreement between BGP peers. Communities are commonly used by transit service providers to enable peering customers to choose specific routing destinations for their outgoing routes. The transit service provider would typically publish a list of well-known or proprietary communities along with their descriptions, and take it upon itself to advertise incoming routes accordingly. For instance, an ISP may advertise that incoming routes tagged with community XY:01 will be advertised only to European peers while incoming routes tagged with community XY:02 will be advertised only to Asian peers.

The RackSwitch G8272 can be configured to manage the community tags applied to the outgoing route updates. It does not, however, modify any routing decisions based on the community tags.

Up to 32 community tags can be applied to prefixes that pass a route-map. Valid values are between 0:0 and 65535:65535. Newly added communities will replace the existing communities. To set communities to prefixes that pass the route-map, use the following commands:

To remove all community tags from prefixes that pass the route-map, use the following command:

To propagate prefixes that pass the route-map with their original community settings, use the following command:

To enable or disable community tags forwarding for specific neighbors or neighbor groups, use the following commands:

RS 8272(config)# routemap <map number>RS 8272(configroutemap)# set community aa:nn [aa:nn]

RS 8272(configroutemap)# set community none

RS 8272(configroutemap)# no set community

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor 5 sendcommunityRS 8272(configrouterbgp)# no neighbor 6 sendcommunityRS 8272(configrouterbgp)# neighbor group 1 sendcommunity


BGP AttributesThe following BGP attributes are discussed in this section: Local preference, metric (Multi-Exit Discriminator), and Next hop.

Local Preference Attribute

When there are multiple paths to the same destination, the local preference attribute indicates the preferred path. The path with the higher preference is preferred (the default value of the local preference attribute is 100). Unlike the weight attribute, which is only relevant to the local router, the local preference attribute is part of the routing update and is exchanged among routers in the same AS.

The local preference attribute can be set in one of two ways:

The following commands use the BGP default local preference method, affecting the outbound direction only.

The following commands use the route map local preference method, which affects both inbound and outbound directions.

Metric (Multi-Exit Discriminator) Attribute

This attribute is a hint to external neighbors about the preferred path into an AS when there are multiple entry points. A lower metric value is preferred over a higher metric value. The default value of the metric attribute is 0.

Unlike local preference, the metric attribute is exchanged between ASs; however, a metric attribute that comes into an AS does not leave the AS.

When an update enters the AS with a certain metric value, that value is used for decision making within the AS. When BGP sends that update to another AS, the metric is reset to 0.

Unless otherwise specified, the router compares metric attributes for paths from external neighbors that are in the same AS.

>> # router bgp>> (config_router_bgp)# localpreference <0-4294967294>>> (config_router_bgp)# exit

>> # routemap 1>> (config_route_map)# localpreference>> (config_router_map)# exit


Next Hop Attribute

BGP routing updates sent to a neighbor contain the next hop IP address used to reach a destination. In eBGP, the edge router, by default, sends its own IP address as the next hop address. However, this can sometimes cause routing path failures in Non-Broadcast Multiaccess Networks (NBMA) and when the edge router sends iBGP updates.

To avoid routing failures, you can manually configure the next hop IP address. In case of NBMA networks, you can configure the external BGP speaker to advertise its own IP address as the next hop. In case of iBGP updates, you can configure the edge iBGP router to send its IP address as the next hop.

Next hop can be configured on a BGP peer or a peer group. Use the following commands:

Next Hop for a BGP Peer

Next Hop for a BGP Peer Group:

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor <number> nexthopself

RS 8272(config)# router bgpRS 8272(configrouterbgp)# neighbor group <number> nexthopself


Selecting Route Paths in BGPBGP selects only one path as the best path. It does not rely on metric attributes to determine the best path. When the same network is learned via more than one BGP peer, BGP uses its policy for selecting the best route to that network. The BGP implementation on the G8272 uses the following criteria to select a path when the same route is received from multiple peers.

1. Local fixed and static routes are preferred over learned routes.

2. With iBGP peers, routes with higher local preference values are selected.

3. In the case of multiple routes of equal preference, the route with lower AS path weight is selected.

AS path weight = 128 x AS path length (number of autonomous systems traversed).

4. In the case of equal weight and routes learned from peers that reside in the same AS, the lower metric is selected.

Note: A route with a metric is preferred over a route without a metric.

5. In the case of equal cost, the eBGP route is preferred over iBGP.

6. The lower cost to the next hop of routes is selected.

7. If all routes have same route type (eBGP or iBGP), the route with the lower router ID is selected.

8. The first learned route is selected if the same router ID is present.

When the path is selected, BGP puts the selected path in its routing table and propagates the path to its neighbors.

Equal Cost Multi-Path

BGP can be configured to load balance the traffic over multiple paths if first six steps in path selection are identical and the next-hop of the route differs.

Multipath Relax

BGP multipath relax functionality allows load balancing across different autonomous system paths that have equal AS path length. This functionality can be enabled using the command:

RS 8272(config-router-bgp)# bestpath as-path multipath-relax


BGP Failover ConfigurationUse the following example to create redundant default gateways for a G8272 at a Web Host/ISP site, eliminating the possibility, if one gateway goes down, that requests will be forwarded to an upstream router unknown to the switch.

As shown in Figure 37, the switch is connected to ISP 1 and ISP 2. The customer negotiates with both ISPs to allow the switch to use their peer routers as default gateways. The ISP peer routers will then need to announce themselves as default gateways to the G8272.

Figure 37. BGP Failover Configuration Example

On the G8272, one peer router (the secondary one) is configured with a longer AS path than the other, so that the peer with the shorter AS path will be seen by the switch as the primary default gateway. ISP 2, the secondary peer, is configured with a metric of “3,” thereby appearing to the switch to be three router hops away.

1. Define the VLANs.

For simplicity, both default gateways are configured in the same VLAN in this example. The gateways could be in the same VLAN or different VLANs.

BladeCenter

Switch

Server 1IP: 200.200.200.10

Server 2IP: 200.200.200.11

IP: 200.200.200.1IP: 210.210.210.1

RS 8272(config)# vlan 1


2. Define the IP interfaces with IPv4 addresses.

The switch will need an IP interface for each default gateway to which it will be connected. Each interface must be placed in the appropriate VLAN. These interfaces will be used as the primary and secondary default gateways for the switch.

3. Enable IP forwarding.

IP forwarding is turned on by default and is used for VLAN-to-VLAN (non-BGP) routing. Make sure IP forwarding is on if the default gateways are on different subnets or if the switch is connected to different subnets and those subnets need to communicate through the switch (which they almost always do).

Note: To help eliminate the possibility for a Denial of Service (DoS) attack, the forwarding of directed broadcasts is disabled by default.

4. Configure BGP peer router 1 and 2 with IPv4 addresses.

>> # interface ip 1>> (configipif)# ip address 200.200.200.1>> (configipif)# ip netmask 255.255.255.0>> (configipif)# enable>> (configipif)# exit>> # interface ip 2>> (configipif)# ip address 210.210.210.1>> (configipif)# ip netmask 255.255.255.0>> (configipif)# enable>> (configipif)# exit

>> # ip routing

>> # router bgp>> (configrouterbgp)# neighbor 1 remoteaddress 200.200.200.2>> (configrouterbgp)# neighbor 1 remoteas 100>> (configrouterbgp)# neighbor 2 remoteaddress 210.210.210.2>> (configrouterbgp)# neighbor 2 remoteas 200


Default Redistribution and Route Aggregation ExampleThis example shows you how to configure the switch to redistribute information from one routing protocol to another and create an aggregate route entry in the BGP routing table to minimize the size of the routing table.

As illustrated in Figure 38, you have two peer routers: an internal and an external peer router. Configure the G8272 to redistribute the default routes from AS 200 to AS 135. At the same time, configure for route aggregation to allow you to condense the number of routes traversing from AS 135 to AS 200.

Figure 38. Route Aggregation and Default Route Redistribution

1. Configure the IP interface.

2. Configure the AS number (AS 135) and router ID (10.1.1.135).

3. Configure internal peer router 1 and external peer router 2 with IPv4 addresses.

4. Configure redistribution for Peer 1.

5. Configure aggregation policy control.

Switch10.1.1.135

>> # router bgp>> (configrouterbgp)# as 135>> (configrouterbgp)# exit

>> # ip routerid 10.1.1.135

>> # router bgp>> (configrouterbgp)# neighbor 1 remoteaddress 10.1.1.4>> (configrouterbgp)# neighbor 1 remoteas 135>> (configrouterbgp)# neighbor 2 remoteaddress 20.20.20.2>> (configrouterbgp)# neighbor 2 remoteas 200

>> (configrouterbgp)# neighbor 1 redistribute defaultaction redistribute

>> (configrouterbgp)# neighbor 1 redistribute fixed


Configure the IPv4 routes that you want aggregated.

>> (configrouterbgp)# aggregateaddress 1 135.0.0.0 255.0.0.0>> (configrouterbgp)# aggregateaddress 1 enable


Chapter 31. OSPF

Lenovo Networking OS supports the Open Shortest Path First (OSPF) routing protocol. The Lenovo N/OS implementation conforms to the OSPF version 2 specifications detailed in Internet RFC 1583, and OSPF version 3 specifications in RFC 5340. The following sections discuss OSPF support for the RackSwitch G8272:

“OSPFv2 Overview” on page 444. This section provides information on OSPFv2 concepts, such as types of OSPF areas, types of routing devices, neighbors, adjacencies, link state database, authentication, and internal versus external routing.

“OSPFv2 Implementation in Lenovo N/OS” on page 449. This section describes how OSPFv2 is implemented in N/OS, such as configuration parameters, electing the designated router, summarizing routes, defining route maps and so forth.

“OSPFv2 Configuration Examples” on page 459. This section provides step-by-step instructions on configuring different OSPFv2 examples: Creating a simple OSPF domain Creating virtual links Summarizing routes

“OSPFv3 Implementation in Lenovo N/OS” on page 468. This section describes differences and additional features found in OSPFv3.


OSPFv2 OverviewOSPF is designed for routing traffic within a single IP domain called an Autonomous System (AS). The AS can be divided into smaller logical units known as areas.

All routing devices maintain link information in their own Link State Database (LSDB). OSPF allows networks to be grouped together into an area. The topology of an area is hidden from the rest of the AS, thereby reducing routing traffic. Routing within an area is determined only by the area’s own topology, thus protecting it from bad routing data. An area can be generalized as an IP subnetwork.

The following sections describe key OSPF concepts.

Types of OSPF Areas

An AS can be broken into logical units known as areas. In any AS with multiple areas, one area must be designated as area 0, known as the backbone. The backbone acts as the central OSPF area. All other areas in the AS must be connected to the backbone. Areas inject summary routing information into the backbone, which then distributes it to other areas as needed.

As shown in Figure 39, OSPF defines the following types of areas:

Stub Area—an area that is connected to only one other area. The stub area receives information from other areas, but external route information is not distributed into stub areas.

Not-So-Stubby-Area (NSSA)—similar to a stub area with additional capabilities. Routes originating from within the NSSA can be propagated to adjacent transit and backbone areas. External routes from outside the AS can be advertised within the NSSA, but external routes coming from backbone area are not accepted.

Transit Area—an area that also carries data traffic which neither originates nor terminates in the area itself.

© Copyright Lenovo 2015 Chapter 31: OSPF 445

Figure 39. OSPF Area Types

Types of OSPF Routing Devices

As shown in Figure 40, OSPF uses the following types of routing devices:

Internal Router (IR)—a router that has all of its interfaces within the same area. IRs maintain LSDBs identical to those of other routing devices within the local area.

Area Border Router (ABR)—a router that has interfaces in multiple areas. ABRs maintain one LSDB for each connected area and disseminate routing information between areas.

Autonomous System Boundary Router (ASBR)—a router that acts as a gateway between the OSPF domain and non-OSPF domains, such as RIP, BGP, and static routes.

BackboneArea 0

Stub AreaNot-So-Stubby Area

(NSSA)

Transit AreaNo External Routes

from Backbone

Stub Area, NSSA,or Transit Area

Connected to Backbonevia Virtual Link

(Also a Transit Area)

External LSA Routes

Internal LSA Routes

ABR ABRABR

ASBR

Non-OSPF AreaRIP/BGP AS

VirtualLink

ABR

ABR = Area Border RouterASBR = Autonomous System Boundary Router


Figure 40. OSPF Domain and an Autonomous System

Neighbors and Adjacencies

In areas with two or more routing devices, neighbors and adjacencies are formed.

Neighbors are routing devices that maintain information about each others’ state. To establish neighbor relationships, routing devices periodically send hello packets on each of their interfaces. All routing devices that share a common network segment, appear in the same area, and have the same health parameters (hello and dead intervals) and authentication parameters respond to each other’s hello packets and become neighbors. Neighbors continue to send periodic hello packets to advertise their health to neighbors. In turn, they listen to hello packets to determine the health of their neighbors and to establish contact with new neighbors.

The hello process is used for electing one of the neighbors as the network segment’s Designated Router (DR) and one as the network segment’s Backup Designated Router (BDR). The DR is adjacent to all other neighbors on that specific network segment and acts as the central contact for database exchanges. Each neighbor sends its database information to the DR, which relays the information to the other neighbors.

The BDR is adjacent to all other neighbors (including the DR). Each neighbor sends its database information to the BDR just as with the DR, but the BDR merely stores this data and does not distribute it. If the DR fails, the BDR will take over the task of distributing database information to the other neighbors.

The Link-State Database

OSPF is a link-state routing protocol. A link represents an interface (or routable path) from the routing device. By establishing an adjacency with other OSPF routers, each routing device in an OSPF area maintains an identical Link-State Database (LSDB) describing the network topology for its area.

Each routing device transmits a Link-State Advertisement (LSA) on each of its active interfaces. LSAs are entered into the LSDB of each routing device. OSPF uses flooding to distribute LSAs between routing devices. Interfaces may also be passive. Passive interfaces send LSAs to active interfaces, but do not receive LSAs, hello

BackboneArea 0 Area 3

Area 2Area 1

Inter-Area Routes(Summary Routes) ABR

ABRABR

ASBR

InternalRouterASBR

ExternalRoutes

BGP

RIP

OSPF Autonomous System


packets, or any other OSPF protocol information from active interfaces. Passive interfaces behave as stub networks, allowing OSPF routing devices to be aware of devices that do otherwise participate in OSPF (either because they do not support it, or because the administrator chooses to restrict OSPF traffic exchange or transit).

When LSAs result in changes to the routing device’s LSDB, the routing device forwards the changes to the adjacent neighbors (the DR and BDR) for distribution to the other neighbors.

OSPF routing updates occur only when changes occur, instead of periodically. For each new route, if a neighbor is interested in that route (for example, if configured to receive static routes and the new route is indeed static), an update message containing the new route is sent to the adjacency. For each route removed from the route table, if the route has already been sent to a neighbor, an update message containing the route to withdraw is sent.


The Shortest Path First Tree

The routing devices use a link-state algorithm (Dijkstra’s algorithm) to calculate the shortest path to all known destinations, based on the cumulative cost required to reach the destination.

The cost of an individual interface in OSPF is an indication of the overhead required to send packets across it. The cost is inversely proportional to the bandwidth of the interface. A lower cost indicates a higher bandwidth.

Internal Versus External Routing

To ensure effective processing of network traffic, every routing device on your network needs to know how to send a packet (directly or indirectly) to any other location/destination in your network. This is referred to as internal routing and can be done with static routes or using active internal routing protocols, such as OSPF, RIP, or RIPv2.

It is also useful to tell routers outside your network (upstream providers or peers) about the routes you have access to in your network. Sharing of routing information between autonomous systems is known as external routing.

Typically, an AS will have one or more border routers (peer routers that exchange routes with other OSPF networks) as well as an internal routing system enabling every router in that AS to reach every other router and destination within that AS.

When a routing device advertises routes to boundary routers on other autonomous systems, it is effectively committing to carry data to the IP space represented in the route being advertised. For example, if the routing device advertises 192.204.4.0/24, it is declaring that if another router sends data destined for any address in the 192.204.4.0/24 range, it will carry that data to its destination.


OSPFv2 Implementation in Lenovo N/OSN/OS supports a single instance of OSPF and up to 4K routes on the network. The following sections describe OSPF implementation in N/OS: “Configurable Parameters” on page 449 “Defining Areas” on page 450 “Interface Cost” on page 452 “Electing the Designated Router and Backup” on page 452 “Summarizing Routes” on page 452 “Default Routes” on page 453 “Virtual Links” on page 454 “Router ID” on page 454 “Authentication” on page 455

Configurable Parameters

In N/OS, OSPF parameters can be configured through the Command Line Interfaces (CLI/ISCLI), Browser-Based Interface (BBI), or through SNMP. For more information, see “Switch Administration” on page 29.

The ISCLI supports the following parameters: interface output cost, interface priority, dead and hello intervals, retransmission interval, and interface transmit delay.

In addition to the preceding parameters, you can specify the following:

Shortest Path First (SPF) interval—Time interval between successive calculations of the shortest path tree using the Dijkstra’s algorithm.

Stub area metric—A stub area can be configured to send a numeric metric value such that all routes received via that stub area carry the configured metric to potentially influence routing decisions.

Default routes—Default routes with weight metrics can be manually injected into transit areas. This helps establish a preferred route when multiple routing devices exist between two areas. It also helps route traffic to external networks.

Passive—When enabled, the interface sends LSAs to upstream devices, but does not otherwise participate in OSPF protocol exchanges.

Point-to-Point—For LANs that have only two OSPF routing agents (the G8272 and one other device), this option allows the switch to significantly reduce the amount of routing information it must carry and manage.


Defining Areas

If you are configuring multiple areas in your OSPF domain, one of the areas must be designated as area 0, known as the backbone. The backbone is the central OSPF area and is usually physically connected to all other areas. The areas inject routing information into the backbone which, in turn, disseminates the information into other areas.

Since the backbone connects the areas in your network, it must be a contiguous area. If the backbone is partitioned (possibly as a result of joining separate OSPF networks), parts of the AS will be unreachable, and you will need to configure virtual links to reconnect the partitioned areas (see “Virtual Links” on page 454).

Up to six OSPF areas can be connected to the G8272 with N/OS software. To configure an area, the OSPF number must be defined and then attached to a network interface on the switch. The full process is explained in the following sections.

An OSPF area is defined by assigning two pieces of information: an area index and an area ID. The commands to define and enable an OSPF area are as follows:

Note: The area option is an arbitrary index used only on the switch and does not represent the actual OSPF area number. The actual OSPF area number is defined in the area portion of the command as explained in the following sections.

Assigning the Area IndexThe area <area index> option is actually just an arbitrary index (0-19) used only by the G8272. This index number does not necessarily represent the OSPF area number, though for configuration simplicity, it ought to where possible.

For example, both of the following sets of commands define OSPF area 0 (the backbone) and area 1 because that information is held in the area ID portion of the command. However, the first set of commands is easier to maintain because the arbitrary area indexes agree with the area IDs:

Area index and area ID agreearea 0 areaid 0.0.0.0 (Use index 0 to set area 0 in ID octet

format)area 1 areaid 0.0.0.1 (Use index 1 to set area 1 in ID octet

format)

Area index set to an arbitrary valuearea 1 areaid 0.0.0.0 (Use index 1 to set area 0 in ID octet

format)area 2 areaid 0.0.0.1 (Use index 2 to set area 1 in ID octet

format)

RS 8272(config)# router ospf

RS 8272(configrouterospf)# area <area index> areaid <n.n.n.n>RS 8272(configrouterospf)# area <area index> enableRS 8272(configrouterospf)# exit


Using the Area ID to Assign the OSPF Area NumberThe OSPF area number is defined in the areaid <IP address> option. The octet format is used to be compatible with two different systems of notation used by other OSPF network vendors. There are two valid ways to designate an area ID:

Single NumberMost common OSPF vendors express the area ID number as a single number. For example, the Cisco IOS-based router command “network 1.1.1.0 0.0.0.255 area 1” defines the area number simply as “area 1.”

Multi-octet (IP address): Placing the area number in the last octet (0.0.0.n)Some OSPF vendors express the area ID number in multi-octet format. For example, “area 0.0.0.2” represents OSPF area 2 and can be specified directly on the G8272 as “areaid 0.0.0.2”.

On the G8272, using the last octet in the area ID, “area 1” is equivalent to “areaid 0.0.0.1”.Note: Although both types of area ID formats are supported, be sure that the area IDs are in the same format throughout an area.

Attaching an Area to a NetworkOnce an OSPF area has been defined, it must be associated with a network. To attach the area to a network, you must assign the OSPF area index to an IP interface that participates in the area. The format for the command is as follows:

For example, the following commands could be used to configure IP interface 14 to use 10.10.10.1 on the 10.10.10.0/24 network, to define OSPF area 1, and to attach the area to the network:

Note: OSPFv2 supports IPv4 only. IPv6 is supported in OSPFv3 (see “OSPFv3 Implementation in Lenovo N/OS” on page 468).

RS 8272(config)# interface ip <interface number>RS 8272(configipif)# ip ospf area <area index>RS 8272(configipif)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# area 1 areaid 0.0.0.1RS 8272(configrouterospf)# area 1 enableRS 8272(configrouterospf)# enableRS 8272(configrouterospf)# exit

RS 8272(config)# interface ip 14 RS 8272(configipif)# ip address 10.10.10.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# ip ospf area 1RS 8272(configipif)# ip ospf enable


Interface Cost

The OSPF link-state algorithm (Dijkstra’s algorithm) places each routing device at the root of a tree and determines the cumulative cost required to reach each destination. Usually, the cost is inversely proportional to the bandwidth of the interface. Low cost indicates high bandwidth. You can manually enter the cost for the output route with the following command (Interface IP mode):

Electing the Designated Router and Backup

In any area with more than two routing devices, a Designated Router (DR) is elected as the central contact for database exchanges among neighbors, and a Backup Designated Router (BDR) is elected in case the DR fails.

DR and BDR elections are made through the hello process. The election can be influenced by assigning a priority value to the OSPF interfaces on the G8272. The command is as follows:

A priority value of 255 is the highest, and 1 is the lowest. A priority value of 0 specifies that the interface cannot be used as a DR or BDR. In case of a tie, the routing device with the highest router ID wins. Interfaces configured as passive do not participate in the DR or BDR election process:

Summarizing Routes

Route summarization condenses routing information. Without summarization, each routing device in an OSPF network would retain a route to every subnet in the network. With summarization, routing devices can reduce some sets of routes to a single advertisement, reducing both the load on the routing device and the perceived complexity of the network. The importance of route summarization increases with network size.

Summary routes can be defined for up to 16 IP address ranges using the following command:

where <range number> is a number 1 to 16, <IP address> is the base IP address for the range, and <mask> is the IP address mask for the range. For a detailed configuration example, see “Example 3: Summarizing Routes” on page 466.

RS 8272(configipif)# ip ospf cost <cost value (1-65535)>

RS 8272(configipif)# ip ospf priority <priority value (0-255)>

RS 8272(configipif)# ip ospf passiveinterfaceRS 8272(configipif)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# arearange <range number> address

<IP address> <mask>


Default Routes

When an OSPF routing device encounters traffic for a destination address it does not recognize, it forwards that traffic along the default route. Typically, the default route leads upstream toward the backbone until it reaches the intended area or an external router.

Each G8272 acting as an ABR automatically inserts a default route into each attached area. In simple OSPF stub areas or NSSAs with only one ABR leading upstream (see Area 1 in Figure 41), any traffic for IP address destinations outside the area is forwarded to the switch’s IP interface, and then into the connected transit area (usually the backbone). Since this is automatic, no further configuration is required for such areas.

Figure 41. Injecting Default Routes

If the switch is in a transit area and has a configured default gateway, it can inject a default route into rest of the OSPF domain. Use the following command to configure the switch to inject OSPF default routes (Router OSPF mode):

In this command, <metric value> sets the priority for choosing this switch for default route. The value none sets no default and 1 sets the highest priority for default route. Metric type determines the method for influencing routing decisions for external routes.

When the switch is configured to inject a default route, an AS-external LSA with link state ID 0.0.0.0 is propagated throughout the OSPF routing domain. This LSA is sent with the configured metric value and metric type.

The OSPF default route configuration can be removed with the command:

RS 8272(configrouterospf)# defaultinformation <metric value> <metric type (1 or 2)>

RS 8272(configrouterospf)# no defaultinformation


Virtual Links

Usually, all areas in an OSPF AS are physically connected to the backbone. In some cases where this is not possible, you can use a virtual link. Virtual links are created to connect one area to the backbone through another non-backbone area (see Figure 39 on page 445).

The area which contains a virtual link must be a transit area and have full routing information. Virtual links cannot be configured inside a stub area or NSSA. The area type must be defined as transit using the following command:

The virtual link must be configured on the routing devices at each endpoint of the virtual link, though they may traverse multiple routing devices. To configure a G8272 as one endpoint of a virtual link, use the following command:

where <link number> is a value between 1 and 3, <area index> is the OSPF area index of the transit area, and <router ID> is the IP address of the virtual neighbor, the routing device at the target endpoint. Another router ID is needed when configuring a virtual link in the other direction. To provide the G8272 with a router ID, see the following section Router ID.

For a detailed configuration example on Virtual Links, see “Example 2: Virtual Links” on page 462.

Router ID

Routing devices in OSPF areas are identified by a router ID. The router ID is expressed in IP address format. The IP address of the router ID is not required to be included in any IP interface range or in any OSPF area, and may even use the G8272 loopback interface.

The router ID can be configured in one of the following two ways: Dynamically—OSPF protocol configures the lowest IP interface IP address as the

router ID (loopback interface has priority over the IP interface). This is the default.

Statically—Use the following command to manually configure the router ID:

If there is a loopback interface, its IP address is always preferred as the router ID, instead of an IP interface address. The ip routerid command is the preferred method to set the router ID and it is always used in preference to the other methods.

To modify the router ID from static to dynamic, set the router ID to 0.0.0.0, save the configuration, and reboot the G8272.

To view the router ID, use the following command:

RS 8272(configrouterospf)# area <area index> type transit

RS 8272(configrouterospf)# areavirtuallink <link number> neighborrouter <router ID>

RS 8272(configrouterospf)# ip routerid <IPv4 address>

RS 8272(configrouterospf)# show ip ospf


Authentication

OSPF protocol exchanges can be authenticated so that only trusted routing devices can participate. This ensures less processing on routing devices that are not listening to OSPF packets.

OSPF allows packet authentication and uses IP multicast when sending and receiving packets. Routers participate in routing domains based on pre-defined passwords. N/OS supports simple password (type 1 plain text passwords) and MD5 cryptographic authentication. This type of authentication allows a password to be configured per area.

We strongly recommend that you implement MD5 cryptographic authentication as a best practice.

Figure 42 shows authentication configured for area 0 with the password test. Simple authentication is also configured for the virtual link between area 2 and area 0. Area 1 is not configured for OSPF authentication.

Figure 42. OSPF Authentication

Switch 2

Switch 1 Switch 3

Switch 4

Switch 5

key=blade


Configuring Plain Text OSPF PasswordsTo configure simple plain text OSPF passwords on the switches shown in Figure 42 use the following commands:

1. Enable OSPF authentication for Area 0 on switches 1, 2, and 3.

2. Configure a simple text password up to eight characters for each OSPF IP interface in Area 0 on switches 1, 2, and 3.

3. Enable OSPF authentication for Area 2 on switch 4.

4. Configure a simple text password up to eight characters for the virtual link between Area 2 and Area 0 on switches 2 and 4.

Configuring MD5 AuthenticationUse the following commands to configure MD5 authentication on the switches shown in Figure 42:

1. Enable OSPF MD5 authentication for Area 0 on switches 1, 2, and 3.

2. Configure MD5 key ID for Area 0 on switches 1, 2, and 3.

RS 8272(configrouterospf)# area 0 authenticationtype passwordRS 8272(configrouterospf)# exit

RS 8272(config)# interface ip 1RS 8272(configipif)# ip ospf key testRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip ospf key testRS 8272(configipif)# exitRS 8272(config)# interface ip 3RS 8272(configipif)# ip ospf key testRS 8272(configipif)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# area 2 authenticationtype password

RS 8272(configrouterospf)# areavirtuallink 1 key blade

RS 8272(configrouterospf)# area 0 authenticationtype md5

RS 8272(configrouterospf)# messagedigestkey 1 md5key test

RS 8272(configrouterospf)# exit


3. Assign MD5 key ID to OSPF interfaces on switches 1, 2, and 3.

4. Enable OSPF MD5 authentication for Area 2 on switch 4.

5. Configure MD5 key for the virtual link between Area 2 and Area 0 on switches 2 and 4.

6. Assign MD5 key ID to OSPF virtual link on switches 2 and 4.

Host Routes for Load Balancing

N/OS implementation of OSPF includes host routes. Host routes are used for advertising network device IP addresses to external networks, accomplishing the following goals:

ABR Load SharingAs a form of load balancing, host routes can be used for dividing OSPF traffic among multiple ABRs. To accomplish this, each switch provides identical services but advertises a host route for a different IP address to the external network. If each IP address serves a different and equal portion of the external world, incoming traffic from the upstream router must be split evenly among ABRs.

ABR FailoverComplementing ABR load sharing, identical host routes can be configured on each ABR. These host routes can be given different costs so that a different ABR is selected as the preferred route for each server and the others are available as backups for failover purposes.

Equal Cost Multipath (ECMP)With equal cost multipath, a router potentially has several available next hops towards any given destination. ECMP allows separate routes to be calculated for each IP Type of Service. All paths of equal cost to a given destination are calculated, and the next hops for all equal-cost paths are inserted into the routing table.

RS 8272(config)# interface ip 1RS 8272(configipif)# ip ospf messagedigestkey 1RS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip ospf messagedigestkey 1RS 8272(configipif)# exitRS 8272(config)# interface ip 3RS 8272(configipif)# ip ospf messagedigestkey 1RS 8272(configipif)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# area 1 authenticationtype md5

RS 8272(configrouterospf)# messagedigestkey 2 md5key test

RS 8272(configrouterospf)# areavirtuallink 1 messagedigestkey 2RS 8272(configrouterospf)# exit


Loopback Interfaces in OSPF

A loopback interface is an IP interface which has an IP address, but is not associated with any particular physical port. The loopback interface is thus always available to the general network, regardless of which specific ports are in operation. Because loopback interfaces are always available on the switch, loopback interfaces may present an advantage when used as the router ID.

If dynamic router ID selection is used (see “Router ID” on page 454) loopback interfaces can be used to force router ID selection. If a loopback interface is configured, its IP address is automatically selected as the router ID, even if other IP interfaces have lower IP addresses. If more than one loopback interface is configured, the lowest loopback interface IP address is selected.

Loopback interfaces can be advertised into the OSPF domain by specifying an OSPF host route with the loopback interface IP address.

To enable OSPF on an existing loopback interface:

OSPF Features Not Supported in This Release

The following OSPF features are not supported in this release:

Summarizing external routes

Filtering OSPF routes

Using OSPF to forward multicast routes

Configuring OSPF on non-broadcast multi-access networks (such as frame relay, X.25, or ATM)

RS 8272(config)# interface loopback <1-5>RS 8272(configiploopback)# ip ospf area <area ID> enableRS 8272(configiploopback)# exit


OSPFv2 Configuration ExamplesA summary of the basic steps for configuring OSPF on the G8272 is listed here. Detailed instructions for each of the steps is covered in the following sections:

1. Configure IP interfaces.

One IP interface is required for each desired network (range of IP addresses) being assigned to an OSPF area on the switch.

2. (Optional) Configure the router ID.

The router ID is required only when configuring virtual links on the switch.

3. Enable OSPF on the switch.

4. Define the OSPF areas.

5. Configure OSPF interface parameters.

IP interfaces are used for attaching networks to the various areas.

6. (Optional) Configure route summarization between OSPF areas.

7. (Optional) Configure virtual links.

8. (Optional) Configure host routes.


Example 1: Simple OSPF Domain

In this example, two OSPF areas are defined—one area is the backbone and the other is a stub area. A stub area does not allow advertisements of external routes, thus reducing the size of the database. Instead, a default summary route of IP address 0.0.0.0 is automatically inserted into the stub area. Any traffic for IP address destinations outside the stub area will be forwarded to the stub area’s IP interface, and then into the backbone.

Figure 43. A Simple OSPF Domain

Follow this procedure to configure OSPF support as shown in Figure 43:

1. Configure IP interfaces on each network that will be attached to OSPF areas.

In this example, two IP interfaces are needed:

Interface 1 for the backbone network on 10.10.7.0/24

Interface 2 for the stub area network on 10.10.12.0/24


2. Enable OSPF.

3. Define the backbone.

The backbone is always configured as a transit area using areaid 0.0.0.0.

Network10.10.12.0/2410.10.7.0/24

Network

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 10.10.7.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip address 10.10.12.1RS 8272(configipif)# ip netmask 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# enable

RS 8272(configrouterospf)# area 0 areaid 0.0.0.0RS 8272(configrouterospf)# area 0 type transitRS 8272(configrouterospf)# area 0 enable


4. Define the stub area.

5. Attach the network interface to the backbone.

6. Attach the network interface to the stub area.

RS 8272(configrouterospf)# area 1 areaid 0.0.0.1RS 8272(configrouterospf)# area 1 type stubRS 8272(configrouterospf)# area 1 enableRS 8272(configrouterospf)# exit

RS 8272(config)# interface ip 1RS 8272(configipif)# ip ospf area 0RS 8272(configipif)# ip ospf enableRS 8272(configipif)# exit



Example 2: Virtual Links

In the example shown in Figure 44, area 2 is not physically connected to the backbone as is usually required. Instead, area 2 will be connected to the backbone via a virtual link through area 1. The virtual link must be configured at each endpoint.

Figure 44. Configuring a Virtual Link


Configuring OSPF for a Virtual Link on Switch #1

1. Configure IP interfaces on each network that will be attached to the switch.


Interface 1 for the backbone network on 10.10.7.0/24

Interface 2 for the transit area network on 10.10.12.0/24

2. Configure the router ID.

A router ID is required when configuring virtual links. Later, when configuring the other end of the virtual link on Switch 2, the router ID specified here will be used as the target virtual neighbor (nbr) address.

3. Enable OSPF.

Switch 2Switch 2 Switch 1 Switch 1


RS 8272(config)# ip routerid 10.10.10.1




5. Define the transit area.

The area that contains the virtual link must be configured as a transit area.


7. Attach the network interface to the transit area.

8. Configure the virtual link.

The nbr router ID configured in this step must be the same as the router ID that will be configured for Switch #2 in Step 2 on page 464.

Configuring OSPF for a Virtual Link on Switch #2

1. Configure IP interfaces on each network that will be attached to OSPF areas.


Interface 1 for the transit area network on 10.10.12.0/24


RS 8272(configrouterospf)# area 1 areaid 0.0.0.1RS 8272(configrouterospf)# area 1 type transitRS 8272(configrouterospf)# area 1 enableRS 8272(configrouterospf)# exit



RS 8272(config)# router ospfRS 8272(configrouterospf)# areavirtuallink 1 area 1RS 8272(configrouterospf)# areavirtuallink 1 neighborrouter

10.10.14.1RS 8272(configrouterospf)# areavirtuallink 1 enable


Interface 2 for the stub area network on 10.10.24.0/24

2. Configure the router ID.

A router ID is required when configuring virtual links. This router ID must be the same one specified as the target virtual neighbor (nbr) on switch 1 in Step 8 on page 463.

3. Enable OSPF.


This version of N/OS requires that a backbone index be configured on the non-backbone end of the virtual link as follows:

5. Define the transit area.


7. Attach the network interface to the transmit area.


RS 8272(config)# ip routerid 10.10.14.1


RS 8272(configrouterospf)# area 0 areaid 0.0.0.0RS 8272(configrouterospf)# area 0 enable






9. Configure the virtual link.

The nbr router ID configured in this step must be the same as the router ID that was configured for switch #1 in Step 2 on page 462.

Other Virtual Link Options

You can use redundant paths by configuring multiple virtual links.

Only the endpoints of the virtual link are configured. The virtual link path may traverse multiple routers in an area as long as there is a routable path between the endpoints.


RS 8272(config)# router ospfRS 8272(configrouterospf)# areavirtuallink 1 area 1RS 8272(configrouterospf)# areavirtuallink 1 neighborrouter

10.10.10.1RS 8272(configrouterospf)# areavirtuallink 1 enable


Example 3: Summarizing Routes

By default, ABRs advertise all the network addresses from one area into another area. Route summarization can be used for consolidating advertised addresses and reducing the perceived complexity of the network.

If network IP addresses in an area are assigned to a contiguous subnet range, you can configure the ABR to advertise a single summary route that includes all individual IP addresses within the area.

The following example shows one summary route from area 1 (stub area) injected into area 0 (the backbone). The summary route consists of all IP addresses from 36.128.192.0 through 36.128.254.255 except for the routes in the range 36.128.200.0 through 36.128.200.255.Note: OSPFv2 supports IPv4 only. IPv6 is supported in OSPFv3 (see “OSPFv3 Implementation in Lenovo N/OS” on page 468).

Figure 45. Summarizing Routes

Note: You can specify a range of addresses to prevent advertising by using the hide option. In this example, routes in the range 36.128.200.0 through 36.128.200.255 are kept private.

Use the following procedure to configure OSPF support as shown in Figure 45:

1. Configure IP interfaces for each network which will be attached to OSPF areas.

2. Enable OSPF.








7. Configure route summarization by specifying the starting address and mask of the range of addresses to be summarized.

8. Use the hide command to prevent a range of addresses from advertising to the backbone.

Verifying OSPF Configuration

Use the following commands to verify the OSPF configuration on your switch: show ip ospf show ip ospf neighbor show ip ospf database databasesummary show ip ospf routes

Refer to the Lenovo Networking OS Command Reference for information on the preceding commands.





RS 8272(config)# router ospfRS 8272(configrouterospf)# arearange 1 address 36.128.192.0

255.255.192.0RS 8272(configrouterospf)# arearange 1 area 1RS 8272(configrouterospf)# arearange 1 enableRS 8272(configrouterospf)# exit

RS 8272(config)# router ospfRS 8272(configrouterospf)# arearange 2 address 36.128.200.0

255.255.255.0RS 8272(configrouterospf)# arearange 2 area 1RS 8272(configrouterospf)# arearange 2 hide RS 8272(configrouterospf)# exit


OSPFv3 Implementation in Lenovo N/OSOSPF version 3 is based on OSPF version 2, but has been modified to support IPv6 addressing. In most other ways, OSPFv3 is similar to OSPFv2: They both have the same packet types and interfaces, and both use the same mechanisms for neighbor discovery, adjacency formation, LSA flooding, aging, and so on. The administrator must be familiar with the OSPFv2 concepts covered in the preceding sections of this chapter before implementing the OSPFv3 differences as described in the following sections.

Although OSPFv2 and OSPFv3 are very similar, they represent independent features on the G8272. They are configured separately, and both can run in parallel on the switch with no relation to one another, serving different IPv6 and IPv4 traffic, respectively.

The Lenovo N/OS implementation conforms to the OSPF version 3 authentication/confidentiality specifications in RFC 4552.

OSPFv3 Differences from OSPFv2

Note: When OSPFv3 is enabled, the OSPF backbone area (0.0.0.0) is created by default and is always active.

OSPFv3 Requires IPv6 InterfacesOSPFv3 is designed to support IPv6 addresses. This requires IPv6 interfaces to be configured on the switch and assigned to OSPF areas, in much the same way IPv4 interfaces are assigned to areas in OSPFv2. This is the primary configuration difference between OSPFv3 and OSPFv2.

See “Internet Protocol Version 6” on page 357 for configuring IPv6 interfaces.

OSPFv3 Uses Independent Command PathsThough OSPFv3 and OSPFv2 are very similar, they are configured independently. OSPFv3 command paths are located as follows:

In the ISCLI

RS 8272(config)# ipv6 router ospf (OSPFv3 router config mode)RS 8272(configrouterospf3)# ?

RS 8272(config)# interface ip <Interface number>(Configure OSPFv3)RS 8272(configipif)# ipv6 ospf ? (OSPFv3 interface config)

RS 8272# show ipv6 ospf ? (Show OSPFv3 information)


OSPFv3 Identifies Neighbors by Router IDWhere OSPFv2 uses a mix of IPv4 interface addresses and Router IDs to identify neighbors, depending on their type, OSPFv3 configuration consistently uses a Router ID to identify all neighbors.

Although Router IDs are written in dotted decimal notation, and may even be based on IPv4 addresses from an original OSPFv2 network configuration, it is important to realize that Router IDs are not IP addresses in OSPFv3, and can be assigned independently of IP address space. However, maintaining Router IDs consistent with any legacy OSPFv2 IPv4 addressing allows for easier implementation of both protocols.

Other Internal ImprovementsOSPFv3 has numerous improvements that increase the protocol efficiency in addition to supporting IPv6 addressing. These improvements change some of the behaviors in the OSPFv3 network and may affect topology consideration, but have little direct impact on configuration. For example:

Addressing fields have been removed from Router and Network LSAs.

Flexible treatment of unknown LSA types to make integration of OSPFv3 easier.

Interface network type can be specified using the command: RS 8272(configipif)# ipv6 ospf network broadcast|nonbroadcast|pointtomultipoint|pointtopoint

For an interface network type that is not broadcast or NBMA, link LSA suppression can be enabled so link LSA is not originated for the interface. Use the command: RS 8272(configipif)# ipv6 ospf linklsasuppress

OSPFv3 Limitations

N/OS 8.2 does not currently support multiple interfaces of OSPFv3 on the same link.

OSPFv3 Configuration Example

The following example depicts the OSPFv3 equivalent configuration of “Example 3: Summarizing Routes” on page 466 for OSPFv2.

In this example, one summary route from area 1 (stub area) is injected into area 0 (the backbone). The summary route consists of all IP addresses from the 36::0/32 portion of the 36::0/56 network, except for the routes in the 36::0/8 range.

Figure 46. Summarizing Routes

IF 310::1

IF 436::1

10::0/56Network

36::0/56Network

36::0/32(- 36::0/8)

Backbone Stub Area

Summary RouteABR

Area 0(0.0.0.0)

Area 1(0.0.0.1)


Note: You can specify a range of addresses to prevent advertising by using the hide option. In this example, routes in the 36::0/8 range are kept private.

Use the following procedure to configure OSPFv3 support as shown in Figure 45:

1. Configure IPv6 interfaces for each link which will be attached to OSPFv3 areas.

This is equivalent to configuring the IP address and netmask for IPv4 interfaces.

2. Enable OSPFv3.

This is equivalent to the OSPFv2 enable option in the router ospf command path.


This is identical to OSPFv2 configuration.


This is identical to OSPFv2 configuration.


The ipv6 command path is used instead of the OSPFv2 ip command path


RS 8272(config)# interface ip 3RS 8272(configipif)# ipv6 address 10:0:0:0:0:0:0:1RS 8272(configipif)# ipv6 prefixlen 56RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 4RS 8272(configipif)# ip address 36:0:0:0:0:0:1RS 8272(configipif)# ipv6 prefixlen 56RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ipv6 router ospfRS 8272(configrouterospf3)# enable

RS 8272(configrouterospf3)# area 0 areaid 0.0.0.0RS 8272(configrouterospf3)# area 0 type transitRS 8272(configrouterospf3)# area 0 enable

RS 8272(configrouterospf3)# area 1 areaid 0.0.0.1RS 8272(configrouterospf3)# area 1 type stubRS 8272(configrouterospf3)# area 1 enableRS 8272(configrouterospf3)# exit

RS 8272(config)# interface ip 3RS 8272(configipif)# ipv6 ospf area 0RS 8272(configipif)# ipv6 ospf enableRS 8272(configipif)# exit

RS 8272(config)# interface ip 4RS 8272(configipif)# ipv6 ospf area 1RS 8272(configipif)# ipv6 ospf enableRS 8272(configipif)# exit


The ipv6 command path is used instead of the OSPFv2 ip command path

7. Configure route summarization by specifying the starting address and prefix length of the range of addresses to be summarized.

This differs from OSPFv2 only in that the OSPFv3 command path is used, and the address and prefix are specified in IPv6 format.

8. Use the hide command to prevent a range of addresses from advertising to the backbone.

This differs from OSPFv2 only in that the OSPFv3 command path is used, and the address and prefix are specified in IPv6 format.

RS 8272(config)# ipv6 router ospfRS 8272(configrouterospf3)# arearange 1 address 36:0:0:0:0:0:0:0 32RS 8272(configrouterospf3)# arearange 1 area 0RS 8272(configrouterospf3)# arearange 1 enable

RS 8272(configrouterospf)# arearange 2 address 36:0:0:0:0:0:0:0 8RS 8272(configrouterospf)# arearange 2 area 0RS 8272(configrouterospf)# arearange 2 hide RS 8272(configrouterospf)# exit


Neighbor Configuration ExampleWhen using NBMA or point to multipoint interfaces, you must manually configure neighbors. Following example includes the steps for neighbor configuration.

1. Configure IPv6 interface parameters:

2. Enable OSPFv3:


4. Configure neighbor entry:

RS 8272(config# interface ip 10RS 8272(configipif)# ipv6 address 10:0:0:0:0:0:0:12 64RS 8272(configipif)# vlan 10RS 8272(configipif)# enableRS 8272(configipif)# ipv6 ospf area 0RS 8272(configipif)# ipv6 ospf retransmitinterval 5RS 8272(configipif)# ipv6 ospf transmitdelay 1RS 8272(configipif)# ipv6 ospf priority 1RS 8272(configipif)# ipv6 ospf hellointerval 10RS 8272(configipif)# ipv6 ospf deadinterval 40RS 8272(configipif)# ipv6 ospf network pointtomultipointRS 8272(configipif)# ipv6 ospf pollinterval 120RS 8272(configipif)# ipv6 ospf enableRS 8272(configipif)# exit

RS 8272(config# ipv6 router ospfRS 8272(configrouterospf3)# routerid 12.12.12.12RS 8272(configrouterospf3)# enable

RS 8272(configrouterospf3)# area 0 areaid 0.0.0.0RS 8272(configrouterospf3)# area 0 stabilityinterval 40RS 8272(configrouterospf3)# area 0 defaultmetric 1RS 8272(configrouterospf3)# area 0 defaultmetric type 1RS 8272(configrouterospf3)# area 0 translationrole candidateRS 8272(configrouterospf3)# area 0 type transitRS 8272(configrouterospf3)# area 0 enable

RS 8272(configrouterospf3)# neighbor 1 address fe80:0:0:0:dceb:ff:fe00:9RS 8272(configrouterospf3)# neighbor 1 interface 10RS 8272(configrouterospf3)# neighbor 1 priority 1RS 8272(configrouterospf3)# neighbor 1 enable

© Copyright Lenovo 2015 Chapter 32: Service Location Protocol 473

Chapter 32. Service Location Protocol

Service Location Protocol (SLP) allows the switch to provide dynamic directory services that help users find servers by attributes rather than by name or address. SLP eliminates the need for a user to know the name of a network host supporting a service. SLP allows the user to bind a service description to the network address of the service.

Service Location Protocol is described in RFC 2608.

SLP defines specialized components called agents that perform tasks and support services as follows:

User Agent (UA) supports service query functions. It requests service information for user applications. The User Agent retrieves service information from the Service Agent or Directory Agents. A Host On-Demand client is an example of a User Agent.

Service Agent (SA) provides service registration and service advertisement. Note: In this release, SA supports UA/DA on Linux with SLPv2 support.

Directory Agent (DA) collects service information from Service Agents to provide a repository of service information in order to centralize it for efficient access by User Agents. There can only be one Directory Agent present per given host.

The Directory Agent acts as an intermediate tier in the SLP architecture, placed between the User Agents and the Service Agents, so they communicate only with the Directory Agent instead of with each other. This eliminates a large portion of the multicast request or reply traffic on the network, and it protects the Service Agents from being overwhelmed by too many service requests.

Services are described by the configuration of attributes associated with a type of service. A User Agent can select an appropriate service by specifying the attributes that it needs in a service request message. When service replies are returned, they contain a Uniform Resource Locator (URL) pointing to the service desired, and other information, such as server load, needed by the User Agent.

Active DA DiscoveryWhen a Service Agent or User Agent initializes, it can perform Active Directory Agent Discovery using a multicast service request and specifies the special, reserved service type (service:directory-agent). Active DA Discovery is achieved through the same mechanism as any other discovery using SLP.

The Directory Agent replies with unicast service replies, which provides the URLs and attributes of the requested service.


SLP ConfigurationUse the following ISCLI commands to configure SLP for the switch:

Table 41. SLP ISCLI Commands

Command Syntax and Usage

[no] ip slp enableEnables or disables SLP on the switch. Command mode: Global configuration

[no] ip slp active-da-discovery enableEnables or disables Active DA Discovery. Command mode: Global configuration

clear ip slp directory-agentsClears all Directory Agents learned by the switch. Command mode: Global configuration

show ip slp information

Displays SLP information. Command mode: All

show ip slp directoryagents

Displays Directory Agents learned by the switch. Command mode: All

show ip slp useragents

Displays User Agents information. Command mode: All

show ip slp counter

Displays SLP statistics. Command mode: All

clear ip slp countersClears all Directory Agents learned by the switch. Command mode: Global configuration


Chapter 33. Protocol Independent Multicast

Lenovo Networking OS supports Protocol Independent Multicast (PIM) in Sparse Mode (PIM-SM) and Dense Mode (PIM-DM).Note: Lenovo N/OS 8.2 does not support IPv6 for PIM.

The following sections discuss PIM support for the RackSwitch G8272:

“PIM Overview” on page 476

“Supported PIM Modes and Features” on page 477

“Basic PIM Settings” on page 478

“Additional Sparse Mode Settings” on page 481

“Using PIM with Other Features” on page 484

“PIM Configuration Examples” on page 485


PIM OverviewPIM is designed for efficiently routing multicast traffic across one or more IPv4 domains. This has benefits for application such as IP television, collaboration, education, and software delivery, where a single source must deliver content (a multicast) to a group of receivers that span both wide-area and inter-domain networks.

Instead of sending a separate copy of content to each receiver, a multicast derives efficiency by sending only a single copy of content toward its intended receivers. This single copy only becomes duplicated when it reaches the target domain that includes multiple receivers, or when it reaches a necessary bifurcation point leading to different receiver domains.

PIM is used by multicast source stations, client receivers, and intermediary routers and switches, to build and maintain efficient multicast routing trees. PIM is protocol independent; It collects routing information using the existing unicast routing functions underlying the IPv4 network, but does not rely on any particular unicast protocol. For PIM to function, a Layer 3 routing protocol (such as BGP, OSPF, RIP, or static routes) must first be configured on the switch.

PIM-SM is a reverse-path routing mechanism. Client receiver stations advertise their willingness to join a multicast group. The local routing and switching devices collect multicast routing information and forward the request toward the station that will provide the multicast content. When the join requests reach the sending station, the multicast data is sent toward the receivers, flowing in the opposite direction of the original join requests.

Some routing and switching devices perform special PIM-SM functions. Within each receiver domain, one router is elected as the Designated Router (DR) for handling multicasts for the domain. DRs forward information to a similar device, the Rendezvous Point (RP), which holds the root tree for the particular multicast group.

Receiver join requests as well as sender multicast content initially converge at the RP, which generates and distributes multicast routing data for the DRs along the delivery path. As the multicast content flows, DRs use the routing tree information obtained from the RP to optimize the paths both to and from send and receive stations, bypassing the RP for the remainder of content transactions if a more efficient route is available.

DRs continue to share routing information with the RP, modifying the multicast routing tree when new receivers join, or pruning the tree when all the receivers in any particular domain are no longer part of the multicast group.

© Copyright Lenovo 2015 Chapter 33: Protocol Independent Multicast 477

Supported PIM Modes and FeaturesFor each interface attached to a PIM network component, PIM can be configured to operate either in PIM Sparse Mode (PIM-SM) or PIM Dense Mode (PIM-DM).

PIM-SM is used in networks where multicast senders and receivers comprise a relatively small (sparse) portion of the overall network. PIM-SM uses a more complex process than PIM-DM for collecting and optimizing multicast routes, but minimizes impact on other IP services and is more commonly used.

PIM-DM is used where multicast devices are a relatively large (dense) portion of the network, with very frequent (or constant) multicast traffic. PIM-DM requires less configuration on the switch than PIM-SM, but uses broadcasts that can consume more bandwidth in establishing and optimizing routes.

The following PIM modes and features are not currently supported in N/OS 8.2:

Hybrid Sparse-Dense Mode (PIM-SM/DM). Sparse Mode and Dense Mode may be configured on separate IP interfaces on the switch, but are not currently supported simultaneously on the same IP interface.

PIM Source-Specific Multicast (PIM-SSM)

Anycast RP

PIM RP filters

Only configuration via the switch CLI is supported. PIM configuration is currently not available using the BBI or via SNMP.


Basic PIM SettingsTo use PIM the following is required: The PIM feature must be enabled globally on the switch. PIM network components and PIM modes must be defined. IP interfaces must be configured for each PIM component. PIM neighbor filters may be defined (optional). If PIM-SM is used, define additional parameters:

Rendezvous Point Designated Router preferences (optional) Bootstrap Router preferences (optional)

Each of these tasks is covered in the following sections.Note: In N/OS 8.2, PIM can be configured through the switch CLI only. PIM configuration and information are not available using the BBI or via SNMP.

Globally Enabling or Disabling the PIM Feature

By default, PIM is disabled on the switch. PIM can be globally enabled or disabled using the following commands:

Defining a PIM Network Component

The G8272 can be attached to a maximum of two independent PIM network components. Each component represents a different PIM network, and can be defined for either PIM-SM or PIM-DM operation. Basic PIM component configuration is performed using the following commands:

The sparse option will place the component in Sparse Mode (PIM-SM). The dense option will place the component in Dense Mode (PIM-DM). By default, PIM component 1 is configured for Sparse Mode. PIM component 2 is unconfigured by default.Note: A component using PIM-SM must also be configured with a dynamic or static Rendezvous Point (see “Specifying the Rendezvous Point” on page 481).

Defining an IP Interface for PIM Use

Each network attached to an IP interface on the switch may be assigned one of the available PIM components. The same PIM component can be assigned to multiple IP interfaces. The interfaces may belong to the same VLAN, and they may also belong to different VLANs as long as their member IP addresses do not overlap.

RS 8272(config)# [no] ip pim enable

RS 8272(config)# ip pim component <1-2>RS 8272(configippimcomp)# mode sparse|denseRS 8272(configippimcomp)# exit


To define an IP interface for use with PIM, first configured the interface with an IPv4 address and VLAN as follows:

Note: The PIM feature currently supports only one VLAN for each IP interface. Configurations where different interfaces on different VLANs share IP addresses are not supported.

Next, PIM must be enabled on the interface, and the PIM network component ID must be specified:

By default, PIM component 1 is automatically assigned when PIM is enabled on the IP interface.Note: While PIM is enabled on the interface, the interface VLAN cannot be changed. To change the VLAN, first disable PIM on the interface.

PIM Neighbor Filters

The G8272 accepts connection to up to 24 PIM interfaces. By default, the switch accepts all PIM neighbors attached to the PIM-enabled interfaces, up to the maximum number (72 neighbors). Once the maximum is reached, the switch will deny further PIM neighbors.

To ensure that only the appropriate PIM neighbors are accepted by the switch, the administrator can use PIM neighbor filters to specify which PIM neighbors may be accepted or denied on a per-interface basis.

To turn PIM neighbor filtering on or off for a particular IP interface, use the following commands:

When filtering is enabled, all PIM neighbor requests on the specified IP interface will be denied by default. To allow a specific PIM neighbor, use the following command:

To remove a PIM neighbor from the accepted list, use the following command.

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# ip address <IPv4 address> <IPv4 mask>RS 8272(configipif)# vlan <VLAN number>RS 8272(configipif)# enable

RS 8272(configipif)# ip pim enableRS 8272(configipif)# ip pim componentid <1-2>RS 8272(configipif)# exit

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# [no] ip pim neighborfilter

RS 8272(configipif)# ip pim neighboraddr <neighbor IPv4 address> allow

RS 8272(configipif)# ip pim neighboraddr <neighbor IPv4 address> denyRS 8272(configipif)# exit


You can view configured PIM neighbor filters globally or for a specific IP interface using the following commands:

RS 8272(config)# show ip pim neighborfiltersRS 8272(config)# show ip pim interface <Interface number> neighborfilters


Additional Sparse Mode Settings

Specifying the Rendezvous PointUsing PIM-SM, at least one PIM-capable router must be a candidate for use as a Rendezvous Point (RP) for any given multicast group. If desired, the G8272 can act as an RP candidate. To assign a configured switch IP interface as a candidate, use the following procedure.

1. Select the PIM component that will represent the RP candidate:

2. Configure the IPv4 address of the switch interface which will be advertised as a candidate RP for the specified multicast group:

The switch interface will participate in the election of the RP that occurs on the Bootstrap Router, or BSR (see “Specifying a Bootstrap Router” on page 482).

3. If using dynamic RP candidates, configure the amount of time that the elected interface will remain the RP for the group before a re-election is performed:

Static RP

If RP no election is desired, the switch can provide a static RP. Use the following commands:

1. Enable static RP configuration.

2. Select the PIM component that will represent the RP candidate:

3. Configure the static IPv4 address.

Influencing the Designated Router Selection

Using PIM-SM, All PIM-enabled IP interfaces are considered as potential Designate Routers (DR) for their domain. By default, the interface with the highest IP address on the domain is selected. However, if an interface is configured with a

RS 8272(config)# ip pim component <1-2>

RS 8272(configippimcomp)# rpcandidate rpaddress <group address> <group address mask> <candidate IPv4 address>

RS 8272(configippimcomp)# rpcandidate holdtime <0-255>RS 8272(configippimcomp)# exit

RS 8272(config)# ip pim staticrp enable

RS 8272(config)# ip pim component <1-2>

RS 8272(configippimcomp)# rpstatic rpaddress <group address> <group address mask> <static IPv4 address>


DR priority value, it overrides the IP address selection process. If more than one interface on a domain is configured with a DR priority, the one with the highest number is selected.

Use the following commands to configure the DR priority value (Interface IP mode):

Note: A value of 0 (zero) specifies that the G8272 will not act as the DR. This setting requires the G8272 to be connected to a peer that has a DR priority setting of 1 or higher to ensure that a DR will be present in the network.

Specifying a Bootstrap Router

Using PIM-SM, a Bootstrap Router (BSR) is a PIM-capable router that hosts the election of the RP from available candidate routers. For each PIM-enabled IP interface, the administrator can set the preference level for which the local interface becomes the BSR:

A value of 255 highly prefers the local interface as a BSR. A value of 0 indicates that the PIM CBSR preference is not configured on the switch.

Configuring a Loopback Interface

Loopback interfaces can be used in PIM Sparse Mode for Rendezvous Points (RPs) and Bootstrap Routers (BSRs). For example:

As a static RP

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# ip pim drpriority <value (0-4294967294)>RS 8272(configipif)# exit

RS 8272(config)# interface ip <Interface number>RS 8272(configipif)# ip pim cbsrpreference <0 to 255>RS 8272(configipif)# exit

interface loopback 1 ip address 55.55.1.1 255.255.255.0 enable exit

ip pim staticrp enable

ip pim component 1 rpstatic rpaddress 224.0.0.0 240.0.0.0 55.55.1.1

interface loopback 1 ip pim enable exit


As a candidate RP

As a BSR


ip pim component 1 rpcandidate holdtime 60 rpcandidate rpaddress 224.0.0.0 240.0.0.0 55.55.1.1

interface loopback 1 ip pim enable exit


interface loopback 1 ip pim enable ip pim cbsrpreference 2 exit


Using PIM with Other Features

PIM with ACLs or VMAPs

If using ACLs or VMAPs, be sure to permit traffic for local hosts and routers.

PIM with IGMP

If using IGMP (see “Internet Group Management Protocol” on page 387):

IGMP static joins can be configured with a PIM-SM or PIM-DM multicast group IPv4 address. Using the ISCLI:

IGMP Querier is disabled by default. If IGMP Querier is needed with PIM, be sure to enable the IGMP Query feature globally, as well as on each VLAN where it is needed.

If the switch is connected to multicast receivers and/or hosts, be sure to enable IGMP snooping globally, as well as on each VLAN where PIM receivers are attached.

PIM with VLAG

If using VLAG, see “VLAG with PIM” on page 185.

RS 8272(config)# ip mroute <multicast group IPv4 address> <VLAN> <port>


PIM Configuration Examples

Example 1: PIM-SM with Dynamic RP

This example configures PIM Sparse Mode for one IP interface, with the switch acting as a candidate for dynamic Rendezvous Point (RP) selection.

1. Globally enable the PIM feature:

2. Configure a PIM network component with dynamic RP settings, and set it for PIM Sparse Mode:

Where 225.1.0.0 is the multicast group base IP address, 255.255.0.0 is the multicast group address mask, and 10.10.1.1 is the switch RP candidate address.

Note: Because, Sparse Mode is set by default for PIM component 1, the mode command is needed only if the mode has been previously changed.

3. Define an IP interface for use with PIM:

The IP interface represents the PIM network being connected to the switch. The IPv4 addresses in the defined range must not be included in another IP interface on the switch under a different VLAN.

4. Enable PIM on the IP interface and assign the PIM component:

Note: Because, PIM component 1 is assigned to the interface by default, the componentid command is needed only if the setting has been previously changed.

5. Set the Bootstrap Router (BSR) preference:

RS 8272(config)# ip pim enable

RS 8272(config)# ip pim component 1RS 8272(configippimcomp)# mode sparseRS 8272(configippimcomp)# rpcandidate rpaddress 225.1.0.0

255.255.0.0 10.10.1.1RS 8272(configippimcomp)# rpcandidate holdtime <0-255>RS 8272(configippimcomp)# exit

RS 8272(config)# interface ip 111RS 8272(configipif)# ip address 10.10.1.1 255.255.255.255RS 8272(configipif)# vlan 11RS 8272(configipif)# enable

RS 8272(configipif)# ip pim enableRS 8272(configipif)# ip pim componentid 1

RS 8272(configipif)# ip pim cbsrpreference 135RS 8272(configipif)# exit


Example 2: PIM-SM with Static RP

The following commands can be used to modify the prior example configuration to use a static RP:

Where 225.1.0.0 255.255.0.0 is the multicast group base address and mask, and 10.10.1.1 is the static RP address.Note: The same static RP address must be configured for all switches in the group.

Example 3: PIM-DM

This example configures PIM Dense Mode (PIM-DM) on one IP interface. PIM-DM can be configured independently, or it can be combined with the prior PIM-SM examples (which are configured on a different PIM component) as shown in Figure 47.

Figure 47. Network with both PIM-DM and PIM-SM Components

RS 8272(config)# ip pim staticrp enableRS 8272(config)# ip pim component 1RS 8272(configippimcomp)# rpstatic rpaddress 225.1.0.0 255.255.0.0

10.10.1.1RS 8272(configippimcomp)# exit

PIM-SM

MediaServers

PIM-DMMulticast

225.1.0.0/16

Multicast

239.1.0.0/16

IP 10.10.1.1

VLAN 101

Component 1

IP 10.10.2.1

VLAN 102

Component 2

IP Interface 11 IP Interface 22

PIM EnabledSwitch


1. Configure the PIM-SM component as shown in the prior examples, or if using PIM-DM independently, enable the PIM feature.

2. Configure a PIM component and set the PIM mode:

3. Define an IP interface for use with PIM:

4. Enable PIM on the IP interface and assign the PIM component:

5. (Optional) Configure PIM border router if the IPMC traffic is flowing between PIM domains:

Note: For PIM Dense Mode, the DR, RP, and BSR settings do not apply.

RS 8272(config)# ip pim enable

RS 8272(config)# ip pim component 2RS 8272(configippimcomp)# mode denseRS 8272(configippimcomp)# exit

RS 8272(config)# interface ip 22RS 8272(configipif)# ip address 10.10.2.1 255.255.255.255RS 8272(configipif)# vlan 102RS 8272(configipif)# enable

RS 8272(configipif)# ip pim enableRS 8272(configipif)# ip pim componentid 2RS 8272(configipif)# exit

RS 8272(config)# ip pim pmbr enableRS 8272(config)# interface ip 22RS 8272(configipif)# ip pim borderbitRS 8272(configipif)# exit



Part 6: High Availability Fundamentals

Internet traffic consists of myriad services and applications which use the Internet Protocol (IP) for data delivery. However, IP is not optimized for all the various applications. High Availability goes beyond IP and makes intelligent switching decisions to provide redundant network configurations.



Chapter 34. Basic Redundancy

Lenovo Networking OS 8.2 includes various features for providing basic link or device redundancy:

“Trunking for Link Redundancy” on page 492

“Virtual Link Aggregation” on page 492

“Hot Links” on page 493


Trunking for Link RedundancyMultiple switch ports can be combined together to form robust, high-bandwidth trunks to other devices. Since trunks are comprised of multiple physical links, the trunk group is inherently fault tolerant. As long as one connection between the switches is available, the trunk remains active.

In Figure 48, four ports are trunked together between the switch and the enterprise routing device. Connectivity is maintained as long as one of the links remain active. The links to the server are also trunked, allowing the secondary NIC to take over in the event that the primary NIC link fails.

Figure 48. Trunking Ports for Link Redundancy

For more information on trunking, see “Ports and Trunking” on page 129.

Virtual Link AggregationUsing the VLAG feature, switches can be paired as VLAG peers. The peer switches appear to the connecting device as a single virtual entity for the purpose of establishing a multi-port trunk. The VLAG-capable switches synchronize their logical view of the access layer port structure and internally prevent implicit loops. The VLAG topology also responds more quickly to link failure and does not result in unnecessary MAC flooding.

VLAGs are useful in multi-layer environments for both uplink and downlink redundancy to any regular LAG-capable device. They can also be used in for active-active VRRP connections.

For more information on VLAGs, see “Virtual Link Aggregation Groups” on page 165.

Trunk Trunk

Server

NIC 1

NIC 2Internet


© Copyright Lenovo 2015 Chapter 34: Basic Redundancy 493

Hot LinksHot Links provides basic link redundancy with fast recovery.

Hot Links consists of up to 25 triggers. A trigger consists of a pair of layer 2 interfaces, each containing an individual port, trunk, or LACP adminkey. One interface is the Master, and the other is a Backup. While the Master interface is set to the active state and forwards traffic, the Backup interface is set to the standby state and blocks traffic until the Master interface fails. If the Master interface fails, the Backup interface is set to active and forwards traffic. Once the Master interface is restored, it regains its active state and forwards traffic. The Backup transitions to the standby state.

You may select a physical port, static trunk, or an LACP adminkey as a Hot Link interface.

Forward Delay

The Forward Delay timer allows Hot Links to monitor the Master and Backup interfaces for link stability before selecting one interface to transition to the active state. Before the transition occurs, the interface must maintain a stable link for the duration of the Forward Delay interval.

For example, if you set the Forward delay timer to 10 seconds, the switch will select an interface to become active only if a link remained stable for the duration of the Forward Delay period. If the link is unstable, the Forward Delay period starts again.

Preemption

You can configure the Master interface to resume the active state whenever it becomes available. With Hot Links preemption enabled, the Master interface transitions to the active state immediately upon recovery. The Backup interface immediately transitions to the standby state. If Forward Delay is enabled, the transition occurs when an interface has maintained link stability for the duration of the Forward Delay period.

FDB Update

Use the FDB update option to notify other devices on the network about updates to the Forwarding Database (FDB). When you enable FDB update, the switch sends multicasts of addresses in the forwarding database (FDB) over the active interface, so that other devices on the network can learn the new path. The Hot Links FDB update option uses the station update rate to determine the rate at which to send FDB packets.


The following configuration guidelines apply to Hot links:

When Hot Links is turned on, STP must be turned off on the Hot Links ports.


A port that is a member of the Master interface cannot be a member of the Backup interface. A port that is a member of one Hot Links trigger cannot be a member of another Hot Links trigger.

An individual port that is configured as a Hot Link interface cannot be a member of a trunk.

Configuring Hot Links

Use the following commands to configure Hot Links.

RS 8272(config)# hotlinks trigger 1 enable (Enable Hot Links Trigger 1)RS 8272(config)# hotlinks trigger 1 master port 1 (Add port to Master interface)RS 8272(config)# hotlinks trigger 1 backup port 2 (Add port to Backup interface)RS 8272(config)# hotlinks enable (Turn on Hot Links)


Chapter 35. Layer 2 Failover

The primary application for Layer 2 Failover is to support Network Adapter Teaming. With Network Adapter Teaming, all the NICs on each server share the same IP address, and are configured into a team. One NIC is the primary link, and the other is a standby link. For more details, refer to the documentation for your Ethernet adapter. Note: Only two links per server can be used for Layer 2 Trunk Failover (one primary and one backup). Network Adapter Teaming allows only one backup NIC for each server blade.

Monitoring Trunk LinksLayer 2 Failover can be enabled on any trunk group in the G8272, including LACP trunks. Trunks can be added to failover trigger groups. Then, if some specified number of monitor links fail, the switch disables all the control ports in the switch. When the control ports are disabled, it causes the NIC team on the affected servers to failover from the primary to the backup NIC. This process is called a failover event.

When the appropriate number of links in a monitor group return to service, the switch enables the control ports. This causes the NIC team on the affected servers to fail back to the primary switch (unless Auto-Fallback is disabled on the NIC team). The backup switch processes traffic until the primary switch’s control links come up, which can take up to five seconds.

Figure 49 is a simple example of Layer 2 Failover. One G8272 is the primary, and the other is used as a backup. In this example, all ports on the primary switch belong to a single trunk group, with Layer 2 Failover enabled, and Failover Limit set to 2. If two or fewer links in trigger 1 remain active, the switch temporarily disables all control ports. This action causes a failover event on Server 1 and Server 2.

Figure 49. Basic Layer 2 Failover

Trigger 1

Trigger 1

PrimarySwitch

BackupSwitch

Server 1

Server 2

NIC 1

NIC 2

NIC 1

NIC 2

Internet

EnterpriseRouting Switches


Setting the Failover LimitThe failover limit lets you specify the minimum number of operational links required within each trigger before the trigger initiates a failover event. For example, if the limit is two, a failover event occurs when the number of operational links in the trigger is two or fewer. When you set the limit to zero, the switch triggers a failover event only when no links in the trigger are operational.

© Copyright Lenovo 2015 Chapter 35: Layer 2 Failover 497

Manually Monitoring Port LinksThe Manual Monitor allows you to configure a set of ports and trunks to monitor for link failures (a monitor list), and another set of ports and trunks to disable when the trigger limit is reached (a control list). When the switch detects a link failure on the monitor list, it automatically disables the items in control list. When server ports are disabled, the corresponding server’s network adapter can detect the disabled link, and trigger a network-adapter failover to another port or trunk on the switch, or another switch.

The switch automatically enables the control list items when the monitor list items return to service.

Monitor Port State

A monitor port is considered operational as long as the following conditions are true: The port must be in the Link Up state. If STP is enabled, the port must be in the Forwarding state. If the port is part of an LACP trunk, the port must be in the Aggregated state.

If any of these conditions is false, the monitor port is considered to have failed.

Control Port State

A control port is considered Operational if the monitor trigger is up. As long as the trigger is up, the port is considered operational from a teaming perspective, even if the port itself is actually in the Down state, Blocking state (if STP is enabled on the port), or Not Aggregated state (if part of an LACP trunk).

A control port is considered to have failed only if the monitor trigger is in the Down state.

To view the state of any port, use one of the following commands:

>> # show interface link (View port link status)>> # show interface port <x> spanningtree stp <x>(View port STP status)>> # show lacp information (View port LACP status)


L2 Failover with Other FeaturesL2 Failover works together with static trunks, Link Aggregation Control Protocol (LACP), and with Spanning Tree Protocol (STP), as described in the next sections.

Static Trunks

When you add a portchannel (static trunk group) to a failover trigger, any ports in that trunk become members of the trigger. You can add up to 64 static trunks to a failover trigger, using manual monitoring.

LACP

Link Aggregation Control Protocol allows the switch to form dynamic trunks. You can use the admin key to add up to two LACP trunks to a failover trigger using automatic monitoring. When you add an admin key to a trigger, any LACP trunk with that admin key becomes a member of the trigger.

Spanning Tree Protocol

If Spanning Tree Protocol (STP) is enabled on the ports in a failover trigger, the switch monitors the port STP state rather than the link state. A port failure results when STP is not in a Forwarding state (such as Learning, Discarding, or No Link) in all the Spanning Tree Groups (STGs) to which the port belongs. The switch automatically disables the appropriate control ports.

When the switch determines that ports in the trigger are in STP Forwarding state in any one of the STGs it belongs to, then it automatically enables the appropriate control ports. The switch fails back to normal operation.

For example, if a monitor port is a member of STG1, STG2, and STG3, a failover will be triggered only if the port is not in a forwarding state in all the three STGs. When the port state in any of the three STGs changes to forwarding, then the control port is enabled and normal switch operation is resumed.

© Copyright Lenovo 2015 Chapter 35: Layer 2 Failover 499

Configuration GuidelinesThis section provides important information about configuring Layer 2 Failover.

Any specific failover trigger can monitor ports only, static trunks only, or LACP trunks only. The different types cannot be combined in the same trigger.

A maximum of 64 LACP keys can be added per trigger.

Management ports cannot be monitored.

Control ports for different triggers must not overlap. Monitor ports may overlap.

Configuring Layer 2 FailoverUse the following procedure to configure a Layer 2 Failover Manual Monitor.

1. Specify the links to monitor.

2. Specify the links to disable when the failover limit is reached.

3. Configure general Failover parameters.

RS 8272(config)# failover trigger 1 mmon monitor member 15

RS 8272(config)# failover trigger 1 mmon control member 610

RS 8272(config)# failover enableRS 8272(config)# failover trigger 1 enableRS 8272(config)# failover trigger 1 limit 2



Chapter 36. Virtual Router Redundancy Protocol

The RackSwitch G8272 (G8272) supports IPv4 high-availability network topologies through an enhanced implementation of the Virtual Router Redundancy Protocol (VRRP).Note: Lenovo Networking OS 8.2 does not support IPv6 for VRRP.


“VRRP Overview” on page 502. This section discusses VRRP operation and Lenovo N/OS redundancy configurations.

“Failover Methods” on page 505. This section describes the three modes of high availability.

“Lenovo N/OS Extensions to VRRP” on page 506. This section describes VRRP enhancements implemented in N/OS.

“Virtual Router Deployment Considerations” on page 507. This section describes issues to consider when deploying virtual routers.

“High Availability Configurations” on page 509. This section discusses the more useful and easily deployed redundant configurations.


VRRP OverviewIn a high-availability network topology, no device can create a single point-of-failure for the network or force a single point-of-failure to any other part of the network. This means that your network will remain in service despite the failure of any single device. To achieve this usually requires redundancy for all vital network components.

VRRP enables redundant router configurations within a LAN, providing alternate router paths for a host to eliminate single points-of-failure within a network. Each participating VRRP-capable routing device is configured with the same virtual router IPv4 address and ID number. One of the virtual routers is elected as the master, based on a number of priority criteria, and assumes control of the shared virtual router IPv4 address. If the master fails, one of the backup virtual routers will take control of the virtual router IPv4 address and actively process traffic addressed to it.

With VRRP, Virtual Interface Routers (VIR) allow two VRRP routers to share an IP interface across the routers. VIRs provide a single Destination IPv4 (DIP) address for upstream routers to reach various servers, and provide a virtual default Gateway for the servers.

VRRP Components

Each physical router running VRRP is known as a VRRP router.

Virtual Router

Two or more VRRP routers can be configured to form a virtual router (RFC 2338). Each VRRP router may participate in one or more virtual routers. Each virtual router consists of a user-configured virtual router identifier (VRID) and an IPv4 address.

Virtual Router MAC Address

The VRID is used to build the virtual router MAC Address. The five highest-order octets of the virtual router MAC Address are the standard MAC prefix (00-00-5E-00-01) defined in RFC 2338. The VRID is used to form the lowest-order octet.

Owners and Renters

Only one of the VRRP routers in a virtual router may be configured as the IPv4 address owner. This router has the virtual router’s IPv4 address as its real interface address. This router responds to packets addressed to the virtual router’s IPv4 address for ICMP pings, TCP connections, and so on.

There is no requirement for any VRRP router to be the IPv4 address owner. Most VRRP installations choose not to implement an IPv4 address owner. For the purposes of this chapter, VRRP routers that are not the IPv4 address owner are called renters.

© Copyright Lenovo 2015 Chapter 36: Virtual Router Redundancy Protocol 503

Master and Backup Virtual Router

Within each virtual router, one VRRP router is selected to be the virtual router master. See “Selecting the Master VRRP Router” on page 504 for an explanation of the selection process.Note: If the IPv4 address owner is available, it will always become the virtual router master.

The virtual router master forwards packets sent to the virtual router. It also responds to Address Resolution Protocol (ARP) requests sent to the virtual router's IPv4 address. Finally, the virtual router master sends out periodic advertisements to let other VRRP routers know it is alive and its priority.

Within a virtual router, the VRRP routers not selected to be the master are known as virtual router backups. If the virtual router master fails, one of the virtual router backups becomes the master and assumes its responsibilities.

Virtual Interface Router

At Layer 3, a Virtual Interface Router (VIR) allows two VRRP routers to share an IP interface across the routers. VIRs provide a single Destination IPv4 (DIP) address for upstream routers to reach various destination networks, and provide a virtual default Gateway.Note: Every VIR must be assigned to an IP interface, and every IP interface must be assigned to a VLAN. If no port in a VLAN has link up, the IP interface of that VLAN is down, and if the IP interface of a VIR is down, that VIR goes into INIT state.

VRRP Operation

Only the virtual router master responds to ARP requests. Therefore, the upstream routers only forward packets destined to the master. The master also responds to ICMP ping requests. The backup does not forward any traffic, nor does it respond to ARP requests.

If the master is not available, the backup becomes the master and takes over responsibility for packet forwarding and responding to ARP requests.


Selecting the Master VRRP Router

Each VRRP router is configured with a priority between 1–254. A bidding process determines which VRRP router is or becomes the master—the VRRP router with the highest priority.

The master periodically sends advertisements to an IPv4 multicast address. As long as the backups receive these advertisements, they remain in the backup state. If a backup does not receive an advertisement for three advertisement intervals, it initiates a bidding process to determine which VRRP router has the highest priority and takes over as master. In addition to the three advertisement intervals, a manually set holdoff time can further delay the backups from assuming the master status.

If, at any time, a backup determines that it has higher priority than the current master does, it can preempt the master and become the master itself, unless configured not to do so. In preemption, the backup assumes the role of master and begins to send its own advertisements. The current master sees that the backup has higher priority and will stop functioning as the master.

A backup router can stop receiving advertisements for one of two reasons—the master can be down, or all communications links between the master and the backup can be down. If the master has failed, it is clearly desirable for the backup (or one of the backups, if there is more than one) to become the master.Note: If the master is healthy but communication between the master and the backup has failed, there will then be two masters within the virtual router. To prevent this from happening, configure redundant links to be used between the switches that form a virtual router.


Failover MethodsWith service availability becoming a major concern on the Internet, service providers are increasingly deploying Internet traffic control devices, such as application switches, in redundant configurations. N/OS high availability configurations are based on VRRP. The N/OS implementation of VRRP includes proprietary extensions.

Active-Active Redundancy

In an active-active configuration, shown in Figure 50, two switches provide redundancy for each other, with both active at the same time. Each switch processes traffic on a different subnet. When a failure occurs, the remaining switch can process traffic on all subnets.

For a configuration example, see “High Availability Configurations” on page 509.

Figure 50. Active-Active Redundancy

Virtual Router Group

The virtual router group ties all virtual routers on the switch together as a single entity. As members of a group, all virtual routers on the switch (and therefore the switch itself), are in either a master or standby state.

A VRRP group has the following characteristics:

When enabled, all virtual routers behave as one entity, and all group settings override any individual virtual router settings.

All individual virtual routers, once the VRRP group is enabled, assume the group’s tracking and priority.

When one member of a VRRP group fails, the priority of the group decreases, and the state of the entire switch changes from Master to Standby.

Each VRRP advertisement can include up to 16 addresses. All virtual routers are advertised within the same packet, conserving processing and buffering resources.

InternetInternet


Switch 1

Switch 2

Servers

Active (subnet A and C)

Active (subnet B and D)


Lenovo N/OS Extensions to VRRPThis section describes VRRP enhancements that are implemented in N/OS.

N/OS supports a tracking function that dynamically modifies the priority of a VRRP router, based on its current state. The objective of tracking is to have, whenever possible, the master bidding processes for various virtual routers in a LAN converge on the same switch. Tracking ensures that the selected switch is the one that offers optimal network performance. For tracking to have any effect on virtual router operation, preemption must be enabled.

N/OS can track the attributes listed in Table 42 (Router VRRP mode):

Each tracked parameter has a user-configurable weight associated with it. As the count associated with each tracked item increases (or decreases), so does the VRRP router's priority, subject to the weighting associated with each tracked item. If the priority level of a standby is greater than that of the current master, then the standby can assume the role of the master.

See “Configuring the Switch for Tracking” on page 507 for an example on how to configure the switch for tracking VRRP priority.

Table 42. VRRP Tracking Parameters

Parameter Description

Number of IP interfaces on the switch that are active (“up”)

trackingpriorityincrement interfaces

Helps elect the virtual routers with the most available routes as the master. (An IP interface is considered active when there is at least one active port on the same VLAN.) This parameter influences the VRRP router's priority in virtual interface routers.

Number of active ports on the same VLAN

trackingpriorityincrement ports

Helps elect the virtual routers with the most available ports as the master. This parameter influences the VRRP router's priority in virtual interface routers.

Number of virtual routers in master mode on the switch

trackingpriorityincrement virtualrouters

Useful for ensuring that traffic for any particular client/server pair is handled by the same switch, increasing routing efficiency. This parameter influences the VRRP router's priority in virtual interface routers.

Next hop tracking

virtualrouter <x> nexthop <IP address> [ICMP|ARP] [<interval>] [<retries>]

A health check mechanism that is used to track the next hop. This parameter influences the VRRP router’s priority based on the availability of the next hop.


Virtual Router Deployment Considerations

Assigning VRRP Virtual Router ID

During the software upgrade process, VRRP virtual router IDs will be automatically assigned if failover is enabled on the switch. When configuring virtual routers at any point after upgrade, virtual router ID numbers must be assigned. The virtual router ID may be configured as any number between 1 and 128. Use the following command to configure the virtual router ID:

Configuring the Switch for Tracking

Tracking configuration largely depends on user preferences and network environment. Consider the configuration shown in Figure 50 on page 505. Assume the following behavior on the network:

Switch 1 is the master router upon initialization.

If switch 1 is the master and it has one fewer active servers than switch 2, then switch 1 remains the master.This behavior is preferred because running one server down is less disruptive than bringing a new master online and severing all active connections in the process.

If switch 1 is the master and it has two or more active servers fewer than switch 2, then switch 2 becomes the master.

If switch 2 is the master, it remains the master even if servers are restored on switch 1 such that it has one fewer or an equal number of servers.

If switch 2 is the master and it has one active server fewer than switch 1, then switch 1 becomes the master.

You can implement this behavior by configuring the switch for tracking as follows:

1. Set the priority for switch 1 to 101.

2. Leave the priority for switch 2 at the default value of 100.

3. On both switches, enable tracking based on ports, interfaces, next hops, or virtual routers. You can choose any combination of tracking parameters, based on your network configuration.

Note: There is no shortcut to setting tracking parameters. The goals must first be set and the outcomes of various configurations and scenarios analyzed to find settings that meet the goals.

RS 8272(config)# router vrrpRS 8272(configvrrp)# virtualrouter 1 virtualrouterid <1-128>


VRRP - Next Hop Tracking

VRRP can be configured to track next hops. A health check mechanism, using ICMP ping or ARP requests, is used to track the next hop. If the health check succeeds or fails, the priority of the virtual router, for which the next hop tracking was configured, changes based on the configured tracking-priority-increment value.

A VRRP group’s priority is calculated as the sum of all priorities for all active next hops. If an active next hop belongs to two virtual routers, then that next-hop’s priority is added twice.

VRRP next hop tracking can be configured using the following commands:

Enable VRRP tracking on next hop:

Configure next hop IP address:

Note: A maximum of four unique next-hop IP addresses can be configured.

Configure priority for each next hop. The value is added to the virtual router’s priority when the next hop is active, and subtracted, when the next hop goes down:

RS 8272(config-vrrp)# virtual-router <x> track next-hops

RS 8272(config-vrrp)# virtual-router <x> next-hop <IP address> [ICMP|ARP] [<interval>] [<retries>]

Default Values:

Health check protocol: ICMPInterval: 2 seconds

Retries: 3

RS 8272(config-vrrp)# tracking-priority-increment next-hop <0-254>


High Availability Configurations

VRRP High-Availability Using Multiple VIRs

Figure 51 shows an example configuration where two G8272s are used as VRRP routers in an active-active configuration. In this configuration, both switches respond to packets.

Figure 51. Active-Active Configuration using VRRP

Although this example shows only two switches, there is no limit on the number of switches used in a redundant configuration. It is possible to implement an active-active configuration across all the VRRP-capable switches in a LAN.

Each VRRP-capable switch in an active-active configuration is autonomous. Switches in a virtual router need not be identically configured.

In the scenario illustrated in Figure 51, traffic destined for IPv4 address 10.0.1.1 is forwarded through the Layer 2 switch at the top of the drawing, and ingresses G8272 1 on port 1. Return traffic uses default gateway 1 (192.168.1.1), which must be in the same network.

If the link between G8272 1 and the Layer 2 switch fails, G8272 2 becomes the Master because it has a higher priority. Traffic is forwarded to G8272 2, which forwards it to G8272 1 through port 4. Return traffic uses default gateway 2 (192.168.2.2), and is forwarded through the Layer 2 switch at the bottom of the drawing.

Internet


VIR 1: 192.168.1.200 (Master)VIR 2: 192.168.2.200 (Backup)

VIR 1: 192.168.1.200 (Backup)VIR 2: 192.168.2.200 (Master)

NIC 1: 10.0.1.1/24NIC 2: 10.0.2.1/24

NIC 1: 10.0.1.2/24NIC 2: 10.0.2.2/24

NIC 1: 10.0.1.3/24NIC 2: 10.0.2.3/24

NIC 1: 10.0.1.4/24NIC 2: 10.0.2.4/24L2 Switch

L2 Switch1

2

4

4

1

2

Server 1

Server 2

Server 3

Server 4

Switch 2

Switch 1


To implement the active-active example, perform the following switch configuration.

Task 1: Configure G8272 1

1. Configure client and server interfaces.

2. Configure the default gateways. Each default gateway points to a Layer 3 router.

3. Turn on VRRP and configure two Virtual Interface Routers.

4. Enable tracking on ports. Set the priority of Virtual Router 1 to 101, so that it becomes the Master.

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 192.168.1.100 255.255.255.0RS 8272(configipif)# vlan 10RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip address 192.168.2.101 255.255.255.0RS 8272(configipif)# vlan 20RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 3RS 8272(configipif)# ip address 10.0.1.100 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 4RS 8272(configipif)# ip address 10.0.2.101 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway 1 address 192.168.1.1RS 8272(config)# ip gateway 1 enableRS 8272(config)# ip gateway 2 address 192.168.2.1RS 8272(config)# ip gateway 2 enable

RS 8272(config)# router vrrpRS 8272(configvrrp)# enableRS 8272(configvrrp)# virtualrouter 1 virtualrouterid 1RS 8272(configvrrp)# virtualrouter 1 interface 1RS 8272(configvrrp)# virtualrouter 1 address 192.168.1.200RS 8272(configvrrp)# virtualrouter 1 enableRS 8272(configvrrp)# virtualrouter 2 virtualrouterid 2RS 8272(configvrrp)# virtualrouter 2 interface 2RS 8272(configvrrp)# virtualrouter 2 address 192.168.2.200RS 8272(configvrrp)# virtualrouter 2 enable

RS 8272(configvrrp)# virtualrouter 1 track portsRS 8272(configvrrp)# virtualrouter 1 priority 101RS 8272(configvrrp)# virtualrouter 2 track portsRS 8272(configvrrp)# exit


5. Configure ports.

6. Turn off Spanning Tree Protocol globally.

Task 2: Configure G8272 2

1. Configure client and server interfaces.

2. Configure the default gateways. Each default gateway points to a Layer 3 router.



RS 8272(config)# no spanningtree stp 1

RS 8272(config)# interface ip 1RS 8272(configipif)# ip address 192.168.1.101 255.255.255.0RS 8272(configipif)# vlan 10RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 2RS 8272(configipif)# ip address 192.168.2.100 255.255.255.0RS 8272(configipif)# vlan 20RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 3RS 8272(configipif)# ip address 10.0.1.101 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exitRS 8272(config)# interface ip 4RS 8272(configipif)# ip address 10.0.2.100 255.255.255.0RS 8272(configipif)# enableRS 8272(configipif)# exit

RS 8272(config)# ip gateway 1 address 192.168.2.1RS 8272(config)# ip gateway 1 enableRS 8272(config)# ip gateway 2 address 192.168.1.1RS 8272(config)# ip gateway 2 enable


3. Turn on VRRP and configure two Virtual Interface Routers.

4. Enable tracking on ports. Set the priority of Virtual Router 2 to 101, so that it becomes the Master.

5. Configure ports.

6. Turn off Spanning Tree Protocol globally.

RS 8272(config)# router vrrpRS 8272(configvrrp)# enableRS 8272(configvrrp)# virtualrouter 1 virtualrouterid 1RS 8272(configvrrp)# virtualrouter 1 interface 1RS 8272(configvrrp)# virtualrouter 1 address 192.168.1.200RS 8272(configvrrp)# virtualrouter 1 enableRS 8272(configvrrp)# virtualrouter 2 virtualrouterid 2RS 8272(configvrrp)# virtualrouter 2 interface 2 RS 8272(configvrrp)# virtualrouter 2 address 192.168.2.200RS 8272(configvrrp)# virtualrouter 2 enable

RS 8272(configvrrp)# virtualrouter 1 track portsRS 8272(configvrrp)# virtualrouter 2 track portsRS 8272(configvrrp)# virtualrouter 2 priority 101RS 8272(configvrrp)# exit



RS 8272(config)# no spanningtree stp 1


VRRP High-Availability Using VLAGs

VRRP can be used in conjunction with VLAGs and LACP-capable servers and switches to provide seamless redundancy.

Figure 52. Active-Active Configuration using VRRP and VLAGs

See “VLAGs with VRRP” on page 176 for a detailed configuration example.

Internet

10.0.1.1

10.0.1.2

10.0.1.3Layer 3

Router

Layer 3

Router1

2

4 5

4 5

1

2

Server 1

Server 2

Server 3

VLAG Peer 1

ISL

VLAG 1

VLAG 2

VLAG 3

VRRP Master

VRRP Backup

Network 10.0.1.0/24

VIR: 10.0.1.100

VLAG Peer 2

VIR: 10.0.1.100

10

11

12

10

11

12



Part 7: Network Management



Chapter 37. Link Layer Discovery Protocol

The Lenovo Networking OS software support Link Layer Discovery Protocol (LLDP). This chapter discusses the use and configuration of LLDP on the switch:

“LLDP Overview” on page 518

“Enabling or Disabling LLDP” on page 519

“LLDP Transmit Features” on page 520

“LLDP Receive Features” on page 524

“LLDP Example Configuration” on page 528


LLDP OverviewLink Layer Discovery Protocol (LLDP) is an IEEE 802.1AB-2005 standard for discovering and managing network devices. LLDP uses Layer 2 (the data link layer), and allows network management applications to extend their awareness of the network by discovering devices that are direct neighbors of already known devices.

With LLDP, the G8272 can advertise the presence of its ports, their major capabilities, and their current status to other LLDP stations in the same LAN. LLDP transmissions occur on ports at regular intervals or whenever there is a relevant change to their status. The switch can also receive LLDP information advertised from adjacent LLDP-capable network devices.

In addition to discovery of network resources, and notification of network changes, LLDP can help administrators quickly recognize a variety of common network configuration problems, such as unintended VLAN exclusions or mis-matched port aggregation membership.

The LLDP transmit function and receive function can be independently configured on a per-port basis. The administrator can allow any given port to transmit only, receive only, or both transmit and receive LLDP information.

The LLDP information to be distributed by the G8272 ports, and that which has been collected from other LLDP stations, is stored in the switch’s Management Information Base (MIB). Network Management Systems (NMS) can use Simple Network Management Protocol (SNMP) to access this MIB information. LLDP-related MIB information is read-only.

Changes, either to the local switch LLDP information or to the remotely received LLDP information, are flagged within the MIB for convenient tracking by SNMP-based management systems.

For LLDP to provide expected benefits, all network devices that support LLDP must be consistent in their LLDP configuration.

© Copyright Lenovo 2015 Chapter 37: Link Layer Discovery Protocol 519

Enabling or Disabling LLDP

Global LLDP Setting

By default, LLDP is enabled on the G8272. To turn LLDP on or off, use the following command:

Transmit and Receive Control

The G8272 can also be configured to transmit or receive LLDP information on a port-by-port basis. By default, when LLDP is globally enabled on the switch, G8272 ports transmit and receive LLDP information (see the tx_rx option in the following example). To change the LLDP transmit and receive state, the following commands are available:

To view the LLDP transmit and receive status, use the following commands:

RS 8272(config)# [no] lldp enable (Turn LLDP on or off globally)

RS 8272(config)# interface port 1 (Select a switch port)RS 8272(configif)# lldp adminstatus tx_rx (Transmit and receive LLDP)RS 8272(configif)# lldp adminstatus tx_only (Only transmit LLDP)RS 8272(configif)# lldp adminstatus rx_only (Only receive LLDP)RS 8272(configif)# no lldp adminstatus (Do not participate in LLDP)RS 8272(configif)# exit (Exit port mode)

RS 8272(config)# show lldp port (status of all ports)RS 8272(config)# show interface port <n> lldp (status of selected port)


LLDP Transmit FeaturesNumerous LLDP transmit options are available, including scheduled and minimum transmit interval, expiration on remote systems, SNMP trap notification, and the types of information permitted to be shared.

Scheduled Interval

The G8272 can be configured to transmit LLDP information to neighboring devices once each 5 to 32768 seconds. The scheduled interval is global; the same interval value applies to all LLDP transmit-enabled ports. However, to help balance LLDP transmissions and keep them from being sent simultaneously on all ports, each port maintains its own interval clock, based on its own initialization or reset time. This allows switch-wide LLDP transmissions to be spread out over time, though individual ports comply with the configured interval.

The global transmit interval can be configured using the following command:

where interval is the number of seconds between LLDP transmissions. The range is 5 to 32768. The default is 30 seconds.

Minimum Interval

In addition to sending LLDP information at scheduled intervals, LLDP information is also sent when the G8272 detects relevant changes to its configuration or status (such as when ports are enabled or disabled). To prevent the G8272 from sending multiple LLDP packets in rapid succession when port status is in flux, a transmit delay timer can be configured.

The transmit delay timer represents the minimum time permitted between successive LLDP transmissions on a port. Any interval-driven or change-driven updates will be consolidated until the configured transmit delay expires.

The minimum transmit interval can be configured using the following command:

where interval is the minimum number of seconds permitted between successive LLDP transmissions on any port. The range is 1 to one-quarter of the scheduled transmit interval (lldp refreshinterval <value>), up to 8192. The default is 2 seconds.

Time-to-Live for Transmitted Information

The transmitted LLDP information is held by remote systems for a limited time. A time-to-live parameter allows the switch to determine how long the transmitted data is held before it expires. The hold time is configured as a multiple of the configured transmission interval.

RS 8272(config)# lldp refreshinterval <interval>

RS 8272(config)# lldp transmissiondelay <interval>

RS 8272(config)# lldp holdtimemultiplier <multiplier>


where multiplier is a value between 2 and 10. The default value is 4, meaning that remote systems will hold the port’s LLDP information for 4 x the 30-second transmission interval value, or 120 seconds, before removing it from their MIB.

Trap Notifications

If SNMP is enabled on the G8272 (see “Using Simple Network Management Protocol” on page 38), each port can be configured to send SNMP trap notifications whenever LLDP transmissions are sent. By default, trap notification is disabled for each port. The trap notification state can be changed using the following commands (Interface Port mode):

In addition to sending LLDP information at scheduled intervals, LLDP information is also sent when the G8272 detects relevant changes to its configuration or status (such as when ports are enabled or disabled). To prevent the G8272 from sending multiple trap notifications in rapid succession when port status is in flux, a global trap delay timer can be configured.

The trap delay timer represents the minimum time permitted between successive trap notifications on any port. Any interval-driven or change-driven trap notices from the port will be consolidated until the configured trap delay expires.

The minimum trap notification interval can be configured using the following command:

where interval is the minimum number of seconds permitted between successive LLDP transmissions on any port. The range is 1 to 3600. The default is 5 seconds.

If SNMP trap notification is enabled, the notification messages can also appear in the system log. This is enabled by default. To change whether the SNMP trap notifications for LLDP events appear in the system log, use the following command:

Changing the LLDP Transmit State

When the port is disabled, or when LLDP transmit is turned off for the port using the LLDP admin-status command options (see “Transmit and Receive Control” on page 519), a final LLDP packet is transmitted with a time-to-live value of 0. Neighbors that receive this packet will remove the LLDP information associated with the G8272 port from their MIB.

RS 8272(config)# interface port 1RS 8272(configif)# [no] lldp trapnotificationRS 8272(configif)# exit

RS 8272(config)# lldp trapnotificationinterval <interval>

RS 8272(config)# [no] logging log lldp


In addition, if LLDP is fully disabled on a port and then later re-enabled, the G8272 will temporarily delay resuming LLDP transmissions on the port to allow the port LLDP information to stabilize. The reinitialization delay interval can be globally configured for all ports using the following command:

where interval is the number of seconds to wait before resuming LLDP transmissions. The range is between 1 and 10. The default is 2 seconds.

Types of Information Transmitted

When LLDP transmission is permitted on the port (see “Enabling or Disabling LLDP” on page 519), the port advertises the following required information in type/length/value (TLV) format: Chassis ID Port ID LLDP Time-to-Live

LLDP transmissions can also be configured to enable or disable inclusion of optional information, using the following command (Interface Port mode):

where type is an LLDP information option from Table 43:

RS 8272(config)# lldp reinitdelay <interval>

RS 8272(config)# interface port 1RS 8272(configif)# [no] lldp tlv <type>RS 8272(configif)# exit

Table 43. LLDP Optional Information Types

Type Description Default

portdesc Port Description Enabled

sysname System Name Enabled

sysdescr System Description Enabled

syscap System Capabilities Enabled

mgmtaddr Management Address Enabled

portvid IEEE 802.1 Port VLAN ID Disabled

portprot IEEE 802.1 Port and Protocol VLAN ID Disabled

vlanname IEEE 802.1 VLAN Name Disabled

protid IEEE 802.1 Protocol Identity Disabled

macphy IEEE 802.3 MAC/PHY Configuration/Status, including the auto-negotiation, duplex, and speed status of the port.

Disabled


powermdi IEEE 802.3 Power via MDI, indicating the capabilities and status of devices that require or provide power over twisted-pair copper links.

Disabled

linkaggr IEEE 802.3 Link Aggregation status for the port.

Disabled

framesz IEEE 802.3 Maximum Frame Size for the port.

Disabled

dcbx Data Center Bridging Capability Exchange Protocol (DCBX) for the port.

Enabled

all Select all optional LLDP information for inclusion or exclusion.

Disabled

Table 43. LLDP Optional Information Types (continued)

Type Description Default


LLDP Receive Features

Types of Information Received

When the LLDP receive option is enabled on a port (see “Enabling or Disabling LLDP” on page 519), the port may receive the following information from LLDP-capable remote systems: Chassis Information Port Information LLDP Time-to-Live Port Description System Name System Description System Capabilities Supported/Enabled Remote Management Address

The G8272 stores the collected LLDP information in the MIB. Each remote LLDP-capable device is responsible for transmitting regular LLDP updates. If the received updates contain LLDP information changes (to port state, configuration, LLDP MIB structures, deletion), the switch will set a change flag within the MIB for convenient notification to SNMP-based management systems.

Viewing Remote Device Information

LLDP information collected from neighboring systems can be viewed in numerous ways: Using a centrally-connected LLDP analysis server Using an SNMP agent to examine the G8272 MIB Using the G8272 Browser-Based Interface (BBI) Using commands on the G8272

The following command displays remote LLDP information:

To view a summary of remote information, omit the Index number parameter. For example:

RS 8272(config)# show lldp remotedevice [<index number>]

RS 8272(config)# show lldp remotedeviceLLDP Remote Devices InformationLegend(possible values in DMAC column) :NB Nearest Bridge 0180C200000ENnTB Nearest nonTPMR Bridge 0180C2000003NCB Nearest Customer Bridge 0180C2000000Total number of current entries: 2

LocalPort|Index|Remote Chassis ID |Remote Port|Remote System Name|DMAC|| ||| MGT | 1 | 00 00 00 00 11 00| 5 | C12 | NB 20 | 2 | 74 99 75 1c 75 00| 44 | C3+ | NB


To view detailed information for a remote device, specify the Index number as found in the summary. For example, in keeping with the sample summary, to list details for the first remote device (with an Index value of 1), use the following command:

Note: Received LLDP information can change very quickly. When using show commands, it is possible that flags for some expected events may be too short-lived to be observed in the output.

RS 8272(config)# show lldp remotedevice 1Local Port Alias: 3 Remote Device Index : 1 Remote Device TTL : 99 Remote Device RxChanges : false Chassis Type : Mac Address Chassis Id : 0018b1331d00 Port Type : Locally Assigned Port Id : 23 Port Description : 7

System Name : System Description : Lenovo Networking Operating System RackSwitch G8272, Lenovo Networking OS: version 8.2.1, Boot Image: version 8.2.1

System Capabilities Supported : bridge, router System Capabilities Enabled : bridge, router

Remote Management Address: Subtype : IPv4 Address : 10.100.120.181 Interface Subtype : ifIndex Interface Number : 128 Object Identifier :


To view detailed information of all remote devices, use the following command:

Time-to-Live for Received Information

Each remote device LLDP packet includes an expiration time. If the switch port does not receive an LLDP update from the remote device before the time-to-live clock expires, the switch will consider the remote information to be invalid, and will remove all associated information from the MIB.

RS 8272# show lldp remotedevice detail

Local Port Alias: MGTA Remote Device Index : 1 Remote Device TTL : 4678 Remote Device RxChanges : false Chassis Type : Mac Address Chassis Id : 0817f4a1db00 Port Type : Locally Assigned Port Id : 25 Port Description : MGTA

System Name : System Description : Lenovo Networking Operating System RackSwitch G8272, Lenovo Networking OS: version 8.2.1, Boot Image: version 8.2.1 System Capabilities Supported : bridge, router System Capabilities Enabled : bridge, router


Local Port Alias: 2 Remote Device Index : 2 Remote Device TTL : 4651 Remote Device RxChanges : false Chassis Type : Mac Address Chassis Id : 0817f4a1db00 Port Type : Locally Assigned Port Id : 2 Port Description : 2

System Name : System Description : Lenovo Networking Operating System RackSwitch G8272, Lenovo Networking OS: version 8.2.1, Boot Image: version 8.2.1 System Capabilities Supported : bridge, router System Capabilities Enabled : bridge, router


Total entries displayed: 2


Remote devices can also intentionally set their LLDP time-to-live to 0, indicating to the switch that the LLDP information is invalid and must be immediately removed.


LLDP Example Configuration1. Turn LLDP on globally.

2. Set the global LLDP timer features.

3. Set LLDP options for each port.

4. Enable syslog reporting.

5. Verify the configuration settings:

6. View remote device information as needed.

RS 8272(config)# lldp enable

RS 8272(config)# lldp refreshinterval 30 (Transmit each 30 seconds)RS 8272(config)# lldp transmissiondelay 2 (No more often than 2 sec.)RS 8272(config)# lldp holdtimemultiplier 4 (Remote hold 4 intervals)RS 8272(config)# lldp reinitdelay 2 (Wait 2 sec. after reinit.)RS 8272(config)# lldp trapnotificationinterval 5 (Minimum 5 sec. between)

RS 8272(config)# interface port <n> (Select a switch port)RS 8272(configif)# lldp adminstatus tx_rx (Transmit and receive LLDP)RS 8272(configif)# lldp trapnotification (Enable SNMP trap notifications)RS 8272(configif)# lldp tlv all (Transmit all optional information)RS 8272(configif)# exit

RS 8272(config)# logging log lldp

RS 8272(config)# show lldp

RS 8272(config)# show lldp remotedevice

orRS 8272(config)# show lldp remotedevice <index number>

orRS 8272(config)# show lldp remotedevices detail


Chapter 38. Simple Network Management Protocol

Lenovo Networking OS provides Simple Network Management Protocol (SNMP) version 1, version 2, and version 3 support for access through any network management software, such as IBM Director or HP-OpenView.Note: SNMP read and write functions are enabled by default. For best security practices, if SNMP is not needed for your network, it is recommended that you disable these functions prior to connecting the switch to the network.


SNMP Version 1 & Version 2To access the SNMP agent on the G8272, the read and write community strings on the SNMP manager must be configured to match those on the switch. The default read community string on the switch is public and the default write community string is private.

The read and write community strings on the switch can be changed using the following commands on the CLI:

The SNMP manager must be able to reach the management interface or any one of the IP interfaces on the switch.

For the SNMP manager to receive the SNMPv1 traps sent out by the SNMP agent on the switch, configure the trap host on the switch with the following command:

Note: You can use a loopback interface to set the source IP address for SNMP traps. Use the following command to apply a configured loopback interface:RS 8272(config)# snmpserver trapsource loopback <1-5>

RS 8272(config)# snmpserver readcommunity <1-32 characters>

-and-RS 8272(config)# snmpserver writecommunity <1-32 characters>

RS 8272(config)# snmpserver trapsource <trap source IP interface>RS 8272(config)# snmpserver host <IPv4 address> <trap host community string>

© Copyright Lenovo 2015 Chapter 38: Simple Network Management Protocol 531

SNMP Version 3SNMP version 3 (SNMPv3) is an enhanced version of the Simple Network Management Protocol, approved by the Internet Engineering Steering Group in March, 2002. SNMPv3 contains additional security and authentication features that provide data origin authentication, data integrity checks, timeliness indicators and encryption to protect against threats such as masquerade, modification of information, message stream modification and disclosure.

SNMPv3 allows clients to query the MIBs securely.

SNMPv3 configuration is managed using the following command path menu:

For more information on SNMP MIBs and the commands used to configure SNMP on the switch, see the Lenovo Networking OS 8.2 Command Reference.

Default Configuration

Lenovo N/OS has three SNMPv3 users by default. All the three users have access to all the MIBs supported by the switch:

User 1 name is adminmd5 (password adminmd5). Authentication used is MD5. Privacy protocol used is DES.

User 2 name is adminsha (password adminsha). Authentication used is SHA. Privacy protocol used is DES.

User 3 name is adminshaaes (password Edpq132x!#9Zpx432w). Authentica-tion used is SHA. Privacy protocol used is AES-128.

In boot strict mode (See “Boot Strict Mode” on page 45), Lenovo N/OS has one SNMPv3 user: User 1 name is adminshaaes (password Edpq132x!#9Zpx432w). Authentica-

tion used is SHA. Privacy protocol used is AES-128.

Up to 16 SNMP users can be configured on the switch. To modify an SNMP user, enter the following commands:

Users can be configured to use the authentication/privacy options. The G8272 support two authentication algorithms: MD5 and SHA, as specified in the following command:

RS 8272(config)# snmpserver ?

RS 8272(config)# snmpserver user <1-16> name <1-32 characters>

RS 8272(config)# snmpserver user <1-16> authenticationprotocol md5|sha authenticationpassword

-or-RS 8272(config)# snmpserver user <1-16> authenticationprotocol none


User Configuration Example

1. To configure a user with name “admin,” authentication type MD5, and authentication password of “admin,” privacy option DES with privacy password of “admin,” use the following CLI commands.

2. Configure a user access group, along with the views the group may access. Use the access table to configure the group’s access level.

Because the read view, write view, and notify view are all set to “iso,” the user type has access to all private and public MIBs.

3. Assign the user to the user group. Use the group table to link the user to a particular access group.

RS 8272(config)# snmpserver user 5 name adminRS 8272(config)# snmpserver user 5 authenticationprotocol md5

authenticationpasswordChanging authentication password; validation required:

Enter current admin password: <admin. password>Enter new authentication password:

<auth. password; Should be more than 18 characters >Reenter new authentication password: <auth. password>New authentication password accepted.

RS 8272(config)# snmpserver user 5 privacyprotocol des privacypasswordChanging privacy password; validation required:

Enter current admin password: <admin. password>Enter new privacy password:

<privacy password; Should be more than 18 characters>Reenter new privacy password: <privacy password>New privacy password accepted.

RS 8272(config)# snmpserver access 5 name admingrpRS 8272(config)# snmpserver access 5 level authprivRS 8272(config)# snmpserver access 5 readview isoRS 8272(config)# snmpserver access 5 writeview isoRS 8272(config)# snmpserver access 5 notifyview iso

RS 8272(config)# snmpserver group 5 username adminRS 8272(config)# snmpserver group 5 groupname admingrp


Configuring SNMP Trap Hosts

SNMPv1 Trap Host

1. Configure a user with no authentication and password.

2. Configure an access group and group table entries for the user. Use the following menu to specify which traps can be received by the user:

In the following example the user will receive the traps sent by the switch.

3. Configure an entry in the notify table.

4. Specify the IPv4 address and other trap parameters in the targetAddr and targetParam tables. Use the following commands to specify the user name associated with the targetParam table:

Note: N/OS 8.2 supports only IPv4 addresses for SNMPv1 and SNMPv2 trap hosts.

5. Use the community table to specify which community string is used in the trap.

RS 8272(config)# snmpserver user 10 name v1trap

RS 8272(config)# snmpserver access <user number>

RS 8272(config)# snmpserver access 10 (Access group to view SNMPv1 traps) name v1trap security snmpv1 notifyview iso

RS 8272(config)# snmpserver group 10 (Assign user to the access group) security snmpv1 username v1trap groupname v1trap

RS 8272(config)# snmpserver notify 10 name v1trapRS 8272(config)# snmpserver notify 10 tag v1trap

RS 8272(config)# snmpserver targetaddress 10 name v1trap address 10.70.70.190

RS 8272(config)# snmpserver targetaddress 10 parametersname v1paramRS 8272(config)# snmpserver targetaddress 10 taglist v1paramRS 8272(config)# snmpserver targetparameters 10 name v1paramRS 8272(config)# snmpserver targetparameters 10 username v1trapRS 8272(config)# snmpserver targetparameters 10 message snmpv1

RS 8272(config)# snmpserver community 10 (Define the community string) index v1trap name public username v1trap


SNMPv2 Trap Host Configuration

The SNMPv2 trap host configuration is similar to the SNMPv1 trap host configuration. Wherever you specify the model, use snmpv2 instead of snmpv1.

Note: N/OS 8.2 supports only IPv4 addresses for SNMPv1 and SNMPv2 trap hosts.

RS 8272(config)# snmpserver user 10 name v2trap

RS 8272(config)# snmpserver group 10 security snmpv2RS 8272(config)# snmpserver group 10 username v2trapRS 8272(config)# snmpserver group 10 groupname v2trapRS 8272(config)# snmpserver access 10 name v2trapRS 8272(config)# snmpserver access 10 security snmpv2RS 8272(config)# snmpserver access 10 notifyview iso

RS 8272(config)# snmpserver notify 10 name v2trapRS 8272(config)# snmpserver notify 10 tag v2trap

RS 8272(config)# snmpserver targetaddress 10 name v2trap address 100.10.2.1

RS 8272(config)# snmpserver targetaddress 10 taglist v2trapRS 8272(config)# snmpserver targetaddress 10 parametersname

v2paramRS 8272(config)# snmpserver targetparameters 10 name v2paramRS 8272(config)# snmpserver targetparameters 10 message snmpv2cRS 8272(config)# snmpserver targetparameters 10 username v2trapRS 8272(config)# snmpserver targetparameters 10 security snmpv2

RS 8272(config)# snmpserver community 10 index v2trapRS 8272(config)# snmpserver community 10 username v2trap


SNMPv3 Trap Host Configuration

To configure a user for SNMPv3 traps, you can choose to send the traps with both privacy and authentication, with authentication only, or without privacy or authentication.

This is configured in the access table using the following commands:

Configure the user in the user table accordingly.

It is not necessary to configure the community table for SNMPv3 traps because the community string is not used by SNMPv3.

The following example shows how to configure an SNMPv3 user v3trap with authentication only:

RS 8272(config)# snmpserver access <1-32> levelRS 8272(config)# snmpserver targetparameters <1-16> level

RS 8272(config)# snmpserver user 11 name v3trapRS 8272(config)# snmpserver user 11 authenticationprotocol md5

authenticationpasswordChanging authentication password; validation required:

Enter current admin password: <admin. password>Enter new authentication password: <auth. password>Reenter new authentication password: <auth. password>New authentication password accepted.RS 8272(config)# snmpserver access 11 notifyview isoRS 8272(config)# snmpserver access 11 level authNoprivRS 8272(config)# snmpserver access 11 name v3trapRS 8272(config)# snmpserver group 11 username v3trapRS 8272(config)# snmpserver group 11 groupname v3trapRS 8272(config)# snmpserver notify 11 name v3trapRS 8272(config)# snmpserver notify 11 tag v3trapRS 8272(config)# snmpserver targetaddress 11 name v3trap address

47.81.25.66RS 8272(config)# snmpserver targetaddress 11 taglist v3trapRS 8272(config)# snmpserver targetaddress 11 parametersname v3paramRS 8272(config)# snmpserver targetparameters 11 name v3paramRS 8272(config)# snmpserver targetparameters 11 username v3trapRS 8272(config)# snmpserver targetparameters 11 level authNoPriv


SNMP MIBsThe N/OS SNMP agent supports SNMP version 3. Security is provided through SNMP community strings. The default community strings are “public” for SNMP GET operation and “private” for SNMP SET operation. The community string can be modified only through the Command Line Interface (CLI). Detailed SNMP MIBs and trap definitions of the N/OS SNMP agent are contained in the N/OS enterprise MIB document.

The N/OS SNMP agent supports the following standard MIBs: dot1x.mib ieee8021ab.mib ieee8023ad.mib rfc1213.mib rfc1215.mib rfc1493.mib rfc1573.mib rfc1643.mib rfc1657.mib rfc1757.mib rfc1850.mib rfc1907.mib rfc2037.mib rfc2233.mib rfc2465.mib rfc2571.mib rfc2572.mib rfc2573.mib rfc2574.mib rfc2575.mib rfc2576.mib rfc2790.mib rfc3176.mib rfc4133.mib rfc4363.mib

The N/OS SNMP agent supports the following generic traps as defined in RFC 1215: ColdStart WarmStart LinkDown LinkUp AuthenticationFailure

The SNMP agent also supports two Spanning Tree traps as defined in RFC 1493: NewRoot TopologyChange


The following are the enterprise SNMP traps supported in N/OS:

Table 44. Lenovo N/OS-Supported Enterprise SNMP Traps

Trap Name Description

swLoginFailure Signifies that someone failed to enter a valid username/password combination. swTrapDisplayString specifies whether the login attempt was from CONSOLE or TELNET. In case of TELNET login it also specifies the IP address of the host from which the attempt was made.

swValidLogin Signifies that a user login has occurred.

swApplyComplete Signifies that new configuration has been applied.

swSaveComplete Signifies that new configuration has been saved.

swFwDownloadSucess Signifies that firmware has been downloaded to [image1|image2|boot image].

swFwDownloadFailure Signifies that firmware downloaded failed to [image1|image2|boot image].

swValidLogout Signifies that a user logout has occurred.

swPrimaryPowerSupplyFailure Signifies that the primary power supply has failed.

swPrimaryPowerSupplyFixed Signifies that the primary power supply has been restored.

swDefAdminDisable Signifies that the default admin account has been disabled.

swAcntStrngPswdNotMet Signifies that the configured password does not match strong password complexity.

swAcntLocked Signifies that account has been locked.

swAcntUnlocked Signifies that account has been unlocked.

swStgNewRoot Signifies that the bridge has become the new root of the STG.


swCistNewRoot Signifies that the bridge has become the new root of the CIST.

swStgTopologyChanged Signifies that there was a STG topology change.

swCistTopologyChanged Signifies that there was a CIST topology change.

swHotlinksMasterUp Signifies that the Master interface is active.

swHotlinksMasterDn Signifies that the Master interface is not active.

swHotlinksBackupUp Signifies that the Backup interface is active.

swHotlinksBackupDn Signifies that the Backup interface is not active.

swHotlinksNone Signifies that there are no active interfaces.

swTeamingCtrlUp Signifies that the teaming is up.

swTeamingCtrlDown Signifies that the teaming control is down.

swTeamingCtrlDownTearDownBlked Signifies that the teaming control is down but teardown is blocked.

swTeamingCtrlError Signifies error, action is undefined.

swLACPPortBlocked Signifies that LACP is operationally down on a port, and traffic is blocked on the port.

swLACPPortUnblocked Signifies that LACP is operationally up on a port, and traffic is no longer blocked on the port.

swLFDPortErrdisabled Signifies that a port is error-disabled due to excessive link flaps.

swVlagInstanceUp Signifies that VLAG instance is up identified in the trap message.

swVlagInstanceRemoteUp Signifies that VLAG is down but instance on the remote instance is up.

swVlagInstanceLocalUp Signifies that VLAG is down but local instance is up.

Table 44. Lenovo N/OS-Supported Enterprise SNMP Traps (continued)



swVlagInstanceDown Signifies that VLAG instance is down identified in the trap message.

swVlagIslUp Signifies that connection between VLAG switches is up.

swVlagIslDown Signifies that connection between VLAG switches is down.

sw8021x Signifies 802.1x feature is enabled.

swDefGwUp Signifies that the default gateway is alive. ipCurCfgGwIndex is the index of the Gateway in ipCurCfgGwTable. The range for ipCurCfgGwIndex is from 1 to ipGatewayTableMax. ipCurCfgGwAddr is the IP address of the default gateway.

swDefGwDown Signifies that the default gateway is down. ipCurCfgGwIndex is the index of the Gateway in ipCurCfgGwTable. The range for ipCurCfgGwIndex is from 1 to ipGatewayTableMax. ipCurCfgGwAddr is the IP address of the default gateway.

swDefGwInService Signifies that the default gateway is up and in service. ipCurCfgGwIndex is the index of the Gateway in ipCurCfgGwTable. The range for ipCurCfgGwIndex is from 1 to ipGatewayTableMax. ipCurCfgGwAddr is the IP address of the default gateway.

swDefGwNotInService Signifies that the default gateway is alive but not in service. ipCurCfgGwIndex is the index of the Gateway in ipCurCfgGwTable. The range for ipCurCfgGwIndex is from 1 to ipGatewayTableMax. ipCurCfgGwAddr is the IP address of the default gateway.




swVrrpNewMaster Indicates that the sending agent has transitioned to “Master” state. vrrpCurCfgVirtRtrIndx is the VRRP virtual router table index referenced in vrrpCurCfgVirtRtrTable. The range is from 1 to vrrpVirtRtrTableMaxSize. vrrpCurCfgVirtRtrAddr is the VRRP virtual router IP address.

swVrrpNewBackup Indicates that the sending agent has transitioned to “Backup” state. vrrpCurCfgVirtRtrIndx is the VRRP virtual router table index referenced in vrrpCurCfgVirtRtrTable. The range is from 1 to vrrpVirtRtrTableMaxSize. vrrpCurCfgVirtRtrAddr is the VRRP virtual router IP address.

swVrrpAuthFailure Signifies that a packet has been received from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type. vrrpCurCfgIfIndx is the VRRP interface index. This is equivalent to ifIndex in RFC 1213 mib. The range is from 1 to vrrpIfTableMaxSize. vrrpCurCfgIfPasswd is the password for authentication. It is a DisplayString of 0 to 7 characters.

swTcpHoldDown Signifies that new TCP connection requests from a particular client will be blocked for a pre-determined amount of time since the rate of new TCP connections from that client has reached a pre-determined threshold. The fltCurCfgSrcIp is the client source IP address for which new TCP connection requests will be blocked. The swTrapRate specifies the amount of time in minutes that the particular client will be blocked.




swNTPSyncFailed Signifies that synchronization with the NTP server has failed.

swNTPUpdateClock Signifies that the system clock is updated with NTP server.

swECMPGatewayUp Signifies that the ECMP gateway is up.

swECMPGatewayDown Signifies that the ECMP gateway is down.

swTempExceedThreshold Signifies that the switch temperature has exceeded maximum safety limits.

swFanFailure Signifies that the fan failure has been detected.

swFanFailureFixed Signifies that the fan failure has been fixed.

swTempReturnThreshold Signifies that the switch temperature has returned to under maximum safety limits.

swVMGroupVMotion Signifies that a virtual machine has moved from a port to another.

swVMGroupVMOnline Signifies that an advance provisioned virtual machine has came online.

swVMGroupVMVlanChange Signifies that a virtual machine has entered a VLAN, or changed the VLAN.

swVmCheckSpoofedvm Signifies that a spoofed VM MAC was found.

swOflowConnectControllerFailure Signifies that the connection to OpenFlow controller is broken.

swOflowConnectControllerSuccess Signifies that the connection to OpenFlow controller is successful.

swOflowEmergencyState Signifies that the OpenFlow switch has moved to emergency state.

swOflowNoEmergencyState Signifies that the OpenFlow switch is out of emergency state.

swOflowSwitchOflowMode Signifies that the device is working in OpenFlow switch mode.




swOflowSwitchNomalMode Signifies that the device is working in normal switch mode.

swOflowSwitchFlowtableClr Signifies that the flow table entries are cleared from the device.

swOflowSwitchStatsClr Signifies that the OpenFlow statistics are cleared from the device.

swOflowFlowtableEntryUnavail Signifies that the device is unable to add flow entry in OpenFlow due to unavailability of system resources.

swOflowFlowtableLimit Signifies that the device has reached its configured flow limit.

swOflowPortDownController Signifies that the port is operationally down by OpenFlow controller.

swOflowPortUpController Signifies that the port is operationally up by OpenFlow controller.

swOflowVersionNegotiationError Signifies that the device is unable to connect to controller either due to bad version, or negotiation/hello failure.




Switch Images and Configuration FilesThis section describes how to use MIB calls to work with switch images and configuration files. You can use a standard SNMP tool to perform the actions, using the MIBs listed in Table 45.

Table 45 lists the MIBs used to perform operations associated with the Switch Image and Configuration files.

The following SNMP actions can be performed using the MIBs listed in Table 45.

Load a new Switch image (boot or running) from a FTP/TFTP server

Load a previously saved switch configuration from a FTP/TFTP server

Save the switch configuration to a FTP/TFTP server

Save a switch dump to a FTP/TFTP server

Table 45. MIBs for Switch Image and Configuration Files

MIB Name MIB OID

agTransferServer 1.3.6.1.4.1.26534.2.7.6.1.1.7.1

agTransferImage 1.3.6.1.4.1.26534.2.7.6.1.1.7.2

agTransferImageFileName 1.3.6.1.4.1.26534.2.7.6.1.1.7.3

agTransferCfgFileName 1.3.6.1.4.1.26534.2.7.6.1.1.7.4

agTransferDumpFileName 1.3.6.1.4.1.26534.2.7.6.1.1.7.5

agTransferAction 1.3.6.1.4.1.26534.2.7.6.1.1.7.6

agTransferLastActionStatus 1.3.6.1.4.1.26534.2.7.6.1.1.7.7

agTransferPort 1.3.6.1.4.1.26534.2.7.6.1.1.7.8

agTransferUserName 1.3.6.1.4.1.26534.2.7.6.1.1.7.9

agTransferPassword 1.3.6.1.4.1.26534.2.7.6.1.1.7.10

agTransferTSDumpFileName 1.3.6.1.4.1.26534.2.7.6.1.1.7.11


Loading a New Switch Image

To load a new switch image with the name “MyNewImage1.img” into image2, follow these steps. This example shows an FTP/TFTP server with the IPv4 address 192.168.10.10, though IPv6 is also supported.

1. Set the FTP/TFTP server address where the switch image resides:

Set agTransferServer.0 "192.168.10.10"

2. Set the area where the new image will be loaded:

Set agTransferImage.0 "image2"

3. Set the name of the image:

Set agTransferImageFileName.0 "MyNewImage1.img"

4. If you are using an FTP server, enter a username:

Set agTransferUserName.0 "MyName"

5. If you are using an FTP server, enter a password:

Set agTransferPassword.0 "MyPassword"

6. Initiate the transfer. To transfer a switch image, enter 2 (gtimg):

Set agTransferAction.0 "2"

Loading a Saved Switch ConfigurationTo load a saved switch configuration with the name “MyRunningConfig.cfg” into the switch, follow these steps. This example shows a TFTP server at IPv4 address 192.168.10.10, though IPv6 is also supported.

1. Set the FTP/TFTP server address where the switch configuration file resides:


2. Set the name of the configuration file:

Set agTransferCfgFileName.0 "MyRunningConfig.cfg"





5. Initiate the transfer. To restore a running configuration, enter 3:



Saving the Switch Configuration

To save the switch configuration to a FTP/TFTP server follow these steps. This example shows a FTP/TFTP server with the IPv4 address 192.168.10.10, though IPv6 is also supported.

1. Set the FTP/TFTP server address where the configuration file is saved:


2. Set the name of the configuration file:

Set agTransferCfgFileName.0 "MyRunningConfig.cfg"





5. Initiate the transfer. To save a running configuration file, enter 4:


Saving a Switch Dump

To save a switch dump to a FTP/TFTP server, follow these steps. This example shows an FTP/TFTP server with the 192.168.10.10, though IPv6 is also supported.

1. Set the FTP/TFTP server address where the dump file will be saved:


2. Set the name of the dump file:

Set agTransferDumpFileName.0 "MyDumpFile.dmp"





5. Initiate the transfer. To save a dump file, enter 5:




Chapter 39. NETCONF

The Network Configuration Protocol (NETCONF) provides a mechanism to manage the G8272, retrieve or modify existing configuration data, and upload new configuration data. See RFC 4741 for details on NETCONF.

NETCONF operates in a client/server model. The NETCONF client establishes a session with the switch (acting as a NETCONF server) using a Remote Procedure Call (RPC). NETCONF is based on the Extensible Markup Language (XML) for encoding data and for exchanging configuration and protocol messages.


“NETCONF Overview” on page 548

“XML Requirements” on page 549

“Installing the NETCONF Client” on page 550

“Using Juniper Perl Client” on page 552

“Establishing a NETCONF Session” on page 553

“NETCONF Operations” on page 555

“Protocol Operations Examples” on page 556


NETCONF OverviewNETCONF provides a method to quickly configure the switch. It also allows you to implement a configuration across multiple switches, thereby saving time and reducing the chances of configuration errors.

The NETCONF protocol defines basic operations that are equivalent to the switch ISCLI commands.Note: The current implementation of NETCONF supports only ISCLI commands.

NETCONF is a connection-oriented protocol. See Figure 53 for an overview of NETCONF operation.

Figure 53. NETCONF Operations Procedure

1. The client establishes a transport layer connection to the switch (acting as a NETCONF server).

2. The client and switch exchange hello messages to declare their capabilities.

3. The client sends a request via rpc message to the switch.

4. The switch sends a response via rpcreply message to the client.

Note: Steps 3 and 4 must be repeated for each request that the client sends to the switch.

5. The client sends a closesession message to the switch to end the NETCONF session and the transport layer connection.

6. The switch sends an ok response.

<hello>

<capabilities/>

</hello>

<rpc>

<operation/>

</rpc>

<rpc>

<close-session/>

</rpc>

<hello>

<capabilities/>

</hello>

<rpc-reply>

<operation-response/>

</rpc-reply>

<rpc-reply>

<ok/>

</rpc-reply>

NETCONF

Client

NETCONF

Server

Transport Layer

Protocol

Transport Layer

Protocol

Session• Session-ID

Connection• Authentication

• Data integrity

• Confidentiality

© Copyright Lenovo 2015 Chapter 39: NETCONF 549

XML RequirementsXML is the encoding format used within NETCONF. When using XML for NETCONF:

All NETCONF protocol elements are defined in the following namespace:urn:ietf:params:xml:ns:netconf:base:1.0

NETCONF capability names must be Uniform Resource Identifiers (URIs):urn:ietf:params:netconf:capability:name:1.0

where name is the name of the capability.

Document type declarations must not appear in the NETCONF content.

For Secure Shell (SSH), you must use a special message termination sequence of six characters to provide message framing:]]>]]>


Installing the NETCONF ClientYou can download the required NETCONF Client installation files from www.ibm.com. Select Support & downloads > Fixes, updates and drivers. Follow instructions on the IBM Support Portal page to find the files.

Before installing the NETCONF client, ensure you have completed the following tasks:

Install a supported version of Python (Python 2.6 or higher, up to but not including Python 3.0) in the folder C:\.

Install the PyCrypto application appropriate to the Python version you are using.

Note: The following steps are for the Windows operating systems.

Follow these steps to install the Blade NETCONF Python Client (BNClient):

1. Extract the file bladenetconfpythonclientv0.1.zip to the root (C:\) folder.

You will see two folders under the root folder C:\bladenetconfpythonclientv0.1:

bladenetconfpythonclient

pythonsshlibrary

Note: Ensure you see Paramiko version 1.7.4 or higher in the folder C:\bladenetconfpythonclientv0.1\pythonsshlibrary\

2. Open the command prompt (Select Start > Run > cmd).

3. Enter the following command to install the SSH library:

Note: If the python command does not work from the command prompt, you may need to add a system variable to set the path to the directory where you have installed Python. You can add the system variable at the following location: My Computer > Properties > Advanced > Environment Variables

Follow these steps to install BNClient as a python script:

1. Enter the following command for help:

2. Enter the following command to establish a NETCONF session:

Using SSH to connect to default port 830:

python C:\bladenetconfpythonclientv0.1\pythonsshlibrary\paramiko1.7.6\setup.py install

python C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\bnclient\bnclient.py –h

python C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\bnclient\bnclient.py switch IP address –u admin –p admin –o get


Using SSH to connect to port 22:

Follow these steps to install BNClient as a python library:

1. Open the file C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\example\get.py in a Python editor (For example, IDLE).

2. Change the IP address in the hostname field to the switch IP address, and save the file.

3. Enter the following command to establish a session:

4. Enter the following command to get the running configuration:

Note: The file get.py is an example of a NETCONF operation python script. You can edit the script or write a new script as per your requirements.

python C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\bnclient\bnclient.py switch IP address:22 –u admin –p admin –o get

python C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\setup.py install

python C:\bladenetconfpythonclientv0.1\bladenetconfpythonclient\example\get.py


Using Juniper Perl ClientYou can use Juniper Perl client instead of BNClient to communicate with the NETCONF feature on the switch. Follow these steps to use the Juniper Perl client.Note: You must use the Linux operating system for the Juniper Perl client.

1. Extract the file junipernetconfperlclient.zip to the folder /home/user/.You will see two folders:

junipernetconfperlclient

bladenetconfperlscripts

2. Follow these steps to install the Juniper Perl client:

As a Perl library:

a. Change to the following directory:

/home/user/junipernetconfperlclient

b. Extract the following file:

netconfperl10.0R2.10.tar.gz

c. Change to the following directory:

/home/user/junipernetconfperlclient/netconfperl10.0R2.10

d. Install the client as per the instructions in the README file.

Note: If the prerequisites package installation fails, manually install each file in /home/user/junipernetconfperlclient\netconfperlprereqspatch.

As a Perl script:

a. Change to the following directory:

/home/user/bladenetconfperlscripts/

b. Enter the following command:

Note: The file get.pl is an example of a NETCONF operation Perl script. You can edit the script or write a new script as per your requirement.

perl get/get.pl l admin p admin swich IP address


Establishing a NETCONF SessionSSH is the widely used protocol for NETCONF sessions. The default SSH port for NETCONF is 830. The client may also connect to the switch through SSH port 22.

Follow these steps to establish a NETCONF session. Enter commands in the client Linux Shell.Note: You can open a maximum of four simultaneous sessions.

1. Enter the following command to open an SSH connection:

2. Type or paste the following hello message:

The switch returns a hello message:

3. Type or paste the following rpc message. The get operation is used as an example.

ssh admin@switch IP address p 830 s netconf

<hello><capabilities><capability>urn:ietf:params:netconf:base:1.0</capability>

</capabilities></hello>]]>]]>

<hello xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><capabilities><capability>urn:ietf:params:netconf:base:1.0</capability><capability>urn:ietf:params:netconf:capability:writablerunning:1.0</capability><capability>urn:ietf:params:netconf:capability:rollbackonerror:1.0</capability><capability>urn:ietf:params:netconf:capability:startup:1.0</capability>

</capabilities> <sessionid>102</sessionid>

</hello> ]]>]]>

<rpc messageid=“100”><get><filter type=“subtree”>

<configurationtext/></filter>

</get></rpc>]]>]]>


The switch sends an rpcreply message:

Note: Repeat Step 3 for each request you need to send to the switch.

4. Type or paste the following closesession message to close the NETCONF session and terminate the SSH connection.

The switch sends the following response:

<rpcreply messageid=“100”><data>

<configurationtext xmlns=“http://www.ibm.com/netconf/1.0/configtext”> version “8.2.1”

switchtype “Lenovo Networking Operating System RackSwitch G8272”!!no system dhcp mgta!!interface ip 127 ip address 172.31.36.51enableexit!ip gateway 3 address 172.31.1.1ip gateway 3 enable!!end

</configurationtext></data>

</rpcreply>]]>]]>

<rpc messageid=“101”><closesession/>

</rpc>]]>]]>

<rpcreply messageid=“101”><ok/>

</rpcreply>]]>]]>


NETCONF OperationsThe NETCONF protocol provides a set of operations to manage and retrieve switch configuration. Table 46 provides a list of protocol operations supported by the switch.

Table 46. Protocol Operations

Operation Description

getconfig Retrieve all or part of the running or startup configuration.

editconfig Load all or part of a specified configuration to the running or startup configuration.

copyconfig Replace the target running or startup configuration with a source running or startup configuration.

deleteconfig Delete startup configuration.

lock Lock the running configuration to prevent other users (via another NETCONF session) from changing it.

unlock Release a locked running configuration.

get Retrieve running configuration and device state information.

closesession Request graceful termination of a NETCONF session.

killsession Force the termination of a NETCONF session.

getconfiguration Retrieve configuration data from the switch.

getinterfaceinformation Retrieve interface status information.


Protocol Operations ExamplesFollowing are examples of the NETCONF protocol operations supported by the G8272.

<get-config>

Usage:

Response from the switch:

See Table 47 for the tag elements and their values.

<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><getconfig>

<source><running/>

</source><filter type=“subtree”>

<configurationtext xmlns=“http://www.ibm.com/netconf/1.0/configtext”/>

</filter></getconfig>

</rpc>

<rpcreply messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”>

<data><configurationtext xmlns=“http://www.ibm.com/netconf/1.0/configtext”><! configuration text... >

</configurationtext></data>

</rpcreply>

Table 47. getconfig Tag Element Values

Tag Element Description Value

source The configuration text you want to retrieve.

running/ or startup/

filter type=“subtree” The filter type. subtree

!configuration text...

Contains the running configuration in ISCLI format.


<edit-config>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><editconfig>

<target><running/>

</target><defaultoperation><merge/>

</defaultoperation><erroroption><stoponerror/>

</erroroption><configtext xmlns=“http://www.ibm.com/netconf/1.0/configtext”><configurationtext>hostname Router</configurationtext>

</configtext></editconfig></rpc>


<ok/></rpcreply>

Table 48. editconfig Tag Element Values


target The configuration you want to edit.

running/ or startup/


defaultoperation Set the default operation for the editconfig request.

merge: The new configuration is merged with the target configuration at the corresponding level.

replace: The new configuration replaces the target configuration.

none: The target configuration does not change unless the configuration data in the configurationtext parameter uses the operation attribute to request a different operation.

erroroption Set the option to handle configuration error.

stoponerror: Abort the editconfig operation on first error. This is the default error-option.

continueonerror: Continue to process configuration data on error.

rollbackonerror: Abort the editconfig operation on first error and discard the requested configuration changes.

Table 48. editconfig Tag Element Values



<copy-config>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><copyconfig><target><startup/>

</target><source>

<running/></source>

</copyconfig></rpc>


<ok/></rpcreply>

Table 49. copyconfig Tag Element Values


target Configuration that needs to be changed. running/ or startup/

source Source configuration. running/ or startup/


<delete-config>

Usage:



<lock>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><deleteconfig><target>

<startup/></target>

</deleteconfig></rpc>


<ok/></rpcreply>

Table 50. deleteconfig Tag Element Values


target Configuration that needs to be deleted. startup/

<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><lock><target>

<running/></target>

</lock></rpc>


<ok/></rpcreply>

Table 51. lock Tag Element Values


target Configuration that needs to be edited. running/


<unlock>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><unlock>

<target><running/>

</target></unlock>

</rpc>


<ok/></rpcreply>

Table 52. unlock Tag Element Values


target Configuration being edited. running/


<get>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><get>

<filter type=“subtree”><! request a text version of the configuration ><configurationtext xmlns=“http://www.ibm.com/netconf/1.0/configtext”/>

</filter></get>

</rpc>



</configuration text></data>

</rpcreply>

Table 53. get Tag Element Values


filter Filter type. subtree

configurationtext Configuration in ISCLI format.


<close-session>

Usage:


<kill-session>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><closesession/>

</rpc>


<ok/></rpcreply>

<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><killsession><sessionid>4</sessionid>

</killsession></rpc>


<ok/></rpcreply>

Table 54. killsession Tag Element Values

Tag Element Description

sessionid ID number of the session to be killed


<get-configuration>

Usage:



<rpc messageid=“101” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”><getconfiguration database=“commited” format=“text”/>

</rpc>



</configuration text></data>

</rpcreply>

Table 55. getconfiguration Tag Element Values

Tag Element Description Attributes

getconfiguration

Retrieve the configuration.

database - supports only committed

format - supports only text


<get-interface-information>

Usage:

Response from switch:

Port detail information

<rpc messageid=“101”><getinterfaceinformation>

<interfacename> port xx </interfacename><brief/>

</getinterfaceinformation></rpc>


<interfaceinformation><physicalinterface>

<name></name> <adminstatus></adminstatus><operstatus></operstatus><localindex></localindex><iftype></iftype><linkleveltype></linkleveltype><mtu></mtu><speed></speed><linktype></linktype><trafficstatistics>

<inputbytes></inputbytes><outputbytes></outputbytes><inputpackets></inputpackets><outputpackets></outputpackets>

</trafficstatistics><inputerrorlist>

<inputerrors></inputerrors><framingerrors></framingerrors><inputgiants></inputgiants><inputdiscards></inputdiscards>

</inputerrorlist><outputerrorlist>

<outputcollisions></outputcollisions> <outputerrors></outputerrors><outputdrops></outputdrops>

</outputerrorlist></physicalinterface>

</interfaceinformation></rpcreply>


IP detail information



<interfaceinformation><physicalinterface><logicalinterface>

<name></name><localindex></localindex><addressfamily><addressfamilyname></addressfamilyname><mtu></mtu><interfaceaddress><ifadestination></ifadestination><ifalocal></ifalocal><ifabroadcast></ifabroadcast></interfaceaddress></addressfamily>

</logicalinterface></physicalinterface>

</interfaceinformation></rpcreply>

Table 56. getinterfaceinformation Tag Element Values


interfacename Interface name or number. You can use the tags brief/ or detail/ to specify the amount of information you need.

name Name of the port or IP interface.

adminstatus Administration status of port interface; shutdown or no shutdown.

operstatus Operational status of port interface; link-up or link-down.

localindex Local index of port.

iftype Type of port; GE, XGE.

linkleveltype Ethernet

mtu 9216 for port; 1500 for IP interface.

speed Speed of port; 1000M, 10000M.

linktype Type of duplex port; full, half.

inputbytes Number of bytes received at the port.

outputbytes Number of bytes sent from the port.

inputpackets Number of frames received at port.

outputpackets Number of frames sent out from the port.


inputerrors Sum of discarded frames and FCS Errors.

framingerrors Number of failed frames received.

inputgiants Number of frames that are too long.

inputdiscards Number of frames in discarding state.

outputcollisions Number of Ethernet collisions.

outputerrors Sum of the outgoing frame aborts and FCS errors.

outputdrops Number of frames dropped.

addressfamilyname inet

ifadestination Protocol network address of the interface.

ifalocal Protocol host address on the interface.

ifabroadcast Network broadcast address.

Table 56. getinterfaceinformation Tag Element Values




Part 8: MonitoringThe ability to monitor traffic passing through the G8272 can be invaluable for troubleshooting some types of networking problems. This sections cover the following monitoring features:

Remote Monitoring (RMON)

sFlow

Port Mirroring



Chapter 40. Remote Monitoring

Remote Monitoring (RMON) allows network devices to exchange network monitoring data.

RMON allows the switch to perform the following functions:

Track events and trigger alarms when a threshold is reached.

Notify administrators by issuing a syslog message or SNMP trap.

RMON OverviewThe RMON MIB provides an interface between the RMON agent on the switch and an RMON management application. The RMON MIB is described in RFC 1757.

The RMON standard defines objects that are suitable for the management of Ethernet networks. The RMON agent continuously collects statistics and proactively monitors switch performance. RMON allows you to monitor traffic flowing through the switch.

The switch supports the following RMON Groups, as described in RFC 1757:

Group 1: Statistics

Group 2: History

Group 3: Alarms

Group 9: Events


RMON Group 1—StatisticsThe switch supports collection of Ethernet statistics as outlined in the RMON statistics MIB, in reference to etherStatsTable. You can configure RMON statistics on a per-port basis.

RMON statistics are sampled every second, and new data overwrites any old data on a given port.Note: RMON port statistics must be enabled for the port before you can view RMON statistics.

Example Configuration

1. Enable RMON on a port.

2. View RMON statistics for the port.

RS 8272(config)# interface port 1RS 8272(configif)# rmon

RS 8272(configif)# show interface port 1 rmoncountersRMON statistics for port 1:etherStatsDropEvents: NAetherStatsOctets: 7305626etherStatsPkts: 48686etherStatsBroadcastPkts: 4380etherStatsMulticastPkts: 6612etherStatsCRCAlignErrors: 22etherStatsUndersizePkts: 0etherStatsOversizePkts: 0etherStatsFragments: 2etherStatsJabbers: 0etherStatsCollisions: 0etherStatsPkts64Octets: 27445etherStatsPkts65to127Octets: 12253etherStatsPkts128to255Octets: 1046etherStatsPkts256to511Octets: 619etherStatsPkts512to1023Octets: 7283etherStatsPkts1024to1518Octets: 38

© Copyright Lenovo 2015 Chapter 40: Remote Monitoring 573

RMON Group 2—HistoryThe RMON History Group allows you to sample and archive Ethernet statistics for a specific interface during a specific time interval. History sampling is done per port. Note: RMON port statistics must be enabled for the port before an RMON History Group can monitor the port.

Data is stored in buckets, which store data gathered during discreet sampling intervals. At each configured interval, the History index takes a sample of the current Ethernet statistics, and places them into a bucket. History data buckets reside in dynamic memory. When the switch is re-booted, the buckets are emptied.

Requested buckets are the number of buckets, or data slots, requested by the user for each History Group. Granted buckets are the number of buckets granted by the system, based on the amount of system memory available. The system grants a maximum of 50 buckets.

You can use an SNMP browser to view History samples.

History MIB Object ID

The type of data that can be sampled must be of an ifIndex object type, as described in RFC 1213 and RFC 1573. The most common data type for the History sample is as follows:

1.3.6.1.2.1.2.2.1.1.<x>

The last digit (x) represents the number of the port to monitor.

Configuring RMON History

Perform the following steps to configure RMON History on a port.

1. Enable RMON on a port.

2. Configure the RMON History parameters for a port.

where <x> is the number of the port to monitor. For example, the full OID for port 1 would be:

1.3.6.1.2.1.2.2.1.1.129

RS 8272(config)# interface port 1RS 8272(configif)# rmonRS 8272(configif)# exit

RS 8272(config)# rmon history 1 interfaceoid 1.3.6.1.2.1.2.2.1.1.<x>RS 8272(config)# rmon history 1 requestedbuckets 30RS 8272(config)# rmon history 1 pollinginterval 120RS 8272(config)# rmon history 1 owner "rmon port 1 history"


3. View RMON history for the port.

RMON Group 3—AlarmsThe RMON Alarm Group allows you to define a set of thresholds used to determine network performance. When a configured threshold is crossed, an alarm is generated. For example, you can configure the switch to issue an alarm if more than 1,000 CRC errors occur during a 10-minute time interval.

Each Alarm index consists of a variable to monitor, a sampling time interval, and parameters for rising and falling thresholds. The Alarm Group can be used to track rising or falling values for a MIB object. The object must be a counter, gauge, integer, or time interval.

Use one of the following commands to correlate an Alarm index to an Event index:

When the alarm threshold is reached, the corresponding event is triggered.

Alarm MIB objects

The most common data types used for alarm monitoring are ifStats: errors, drops, bad CRCs, and so on. These MIB Object Identifiers (OIDs) correlate to the ones tracked by the History Group. An example statistic follows: 1.3.6.1.2.1.2.2.1.1.129 – mgmt.icmp.icmpInMsgs

This value represents the alarm’s MIB OID, as a string. Note that for non-tables, you must supply a .0 to specify end node.

Configuring RMON Alarms

Configure the RMON Alarm parameters to track ICMP messages.

RS 8272(config)# show rmon historyRMON History group configuration:

Index IFOID Interval Rbnum Gbnum 1 1.3.6.1.2.1.2.2.1.1.129 120 30 30

Index Owner 1 rmon port 1 history

RS 8272(config)# rmon alarm <alarm number> risingcrossingindex <event number>RS 8272(config)# rmon alarm <alarm number> fallingcrossingindex

<event number>

RS 8272(config)# rmon alarm 1 oid 1.3.6.1.2.1.5.8.0RS 8272(config)# rmon alarm 1 alarmtype risingRS 8272(config)# rmon alarm 1 risingcrossingindex 110RS 8272(config)# rmon alarm 1 interval 60RS 8272(config)# rmon alarm 1 risinglimit 200RS 8272(config)# rmon alarm 1 sample deltaRS 8272(config)# rmon alarm 1 owner "Alarm for icmpInEchos"

© Copyright Lenovo 2015 Chapter 40: Remote Monitoring 575

This configuration creates an RMON alarm that checks icmpInEchos on the switch once every minute. If the statistic exceeds 200 within a 60 second interval, an alarm is generated that triggers event index 110.


RMON Group 9—EventsThe RMON Event Group allows you to define events that are triggered by alarms. An event can be a log message, an SNMP trap, or both.

When an alarm is generated, it triggers a corresponding event notification. Use the following commands to correlate an Event index to an alarm:

RMON events use SNMP and syslogs to send notifications. Therefore, an SNMP trap host must be configured for trap event notification to work properly.

RMON uses a syslog host to send syslog messages. Therefore, an existing syslog host must be configured for event log notification to work properly. Each log event generates a syslog of type RMON that corresponds to the event.

For example, to configure the RMON event parameters.

This configuration creates an RMON event that sends a syslog message each time it is triggered by an alarm.

RS 8272(config)# rmon alarm <alarm number> risingcrossingindex <event number>RS 8272(config)# rmon alarm <alarm number> fallingcrossingindex

<event number>

RS 8272(config)# rmon event 110 type logRS 8272(config)# rmon event 110 description "SYSLOG_this_alarm"RS 8272(config)# rmon event 110 owner "log icmpInEchos alarm"


Chapter 41. sFlow

The G8272 supports sFlow technology for monitoring traffic in data networks. The switch includes an embedded sFlow agent which can be configured to provide continuous monitoring information of IPv4 traffic to a central sFlow analyzer.

The switch is responsible only for forwarding sFlow information. A separate sFlow analyzer is required elsewhere on the network to interpret sFlow data.Note: Lenovo Networking OS 8.2 does not support IPv6 for sFlow.

sFlow Statistical CountersThe G8272 can be configured to send network statistics to an sFlow analyzer at regular intervals. For each port, a polling interval of 5 to 60 seconds can be configured, or 0 (the default) to disable this feature.

When polling is enabled, at the end of each configured polling interval, the G8272 reports general port statistics and port Ethernet statistics.

sFlow Network SamplingIn addition to statistical counters, the G8272 can be configured to collect periodic samples of the traffic data received on each port. For each sample, 128 bytes are copied, UDP-encapsulated, and sent to the configured sFlow analyzer.

For each port, the sFlow sampling rate can be configured to occur once each 256 to 65536 packets, or 0 to disable (the default). A sampling rate of 256 means that one sample will be taken for approximately every 256 packets received on the port. The sampling rate is statistical, however. It is possible to have slightly more or fewer samples sent to the analyzer for any specific group of packets (especially under low traffic conditions). The actual sample rate becomes most accurate over time, and under higher traffic flow.

sFlow sampling has the following restrictions:

Sample Rate—The fastest sFlow sample rate is 1 out of every 256 packets.

ACLs—sFlow sampling is performed before ACLs are processed. For ports configured both with sFlow sampling and one or more ACLs, sampling will occur regardless of the action of the ACL.

Port Mirroring—sFlow sampling will not occur on mirrored traffic. If sFlow sampling is enabled on a port that is configured as a port monitor, the mirrored traffic will not be sampled.

Egress traffic—sFlow sampling will not occur on egress traffic.Note: Although sFlow sampling is not generally a CPU-intensive operation, configuring fast sampling rates (such as once every 256 packets) on ports under heavy traffic loads can cause switch CPU utilization to reach maximum. Use larger rate values for ports that experience heavy traffic.


sFlow Example Configuration1. Specify the location of the sFlow analyzer (the server and optional port to which

the sFlow information will be sent):

By default, the switch uses established sFlow service port 6343.

To disable sFlow features across all ports, use the no sflow enable command.

2. On a per-port basis, define the statistics polling rate:

Specify a polling rate between 5 and 60 seconds, or 0 to disable. By default, polling is 0 (disabled) for each port.

3. On a per-port basis, define the data sampling rate:

Specify a sampling rate between 256 and 65536 packets, or 0 to disable. By default, the sampling rate is 0 (disabled) for each port.


RS 8272(config)# sflow server <IPv4 address>(sFlow server address)RS 8272(config)# sflow port <service port> (Set the optional service port)RS 8272(config)# sflow enable (Enable sFlow features)

RS 8272(config)# interface port <port>RS 8272(configif)# sflow polling <polling rate>(Statistics polling rate)

RS 8272(configif)# sflow sampling <sampling rate>(Data sampling rate)


Chapter 42. Port Mirroring

The Lenovo Networking OS port mirroring feature allows you to mirror (copy) the packets of a target port, and forward them to a monitoring port. Port mirroring functions for all layer 2 and layer 3 traffic on a port. This feature can be used as a troubleshooting tool or to enhance the security of your network. For example, an IDS server or other traffic sniffer device or analyzer can be connected to the monitoring port to detect intruders attacking the network.

The G8272 supports a “many to one” mirroring model. As shown in Figure 54, selected traffic for ports 1 and 2 is being monitored by port 3. In the example, both ingress traffic and egress traffic on port 2 are copied and forwarded to the monitor. However, port 1 mirroring is configured so that only ingress traffic is copied and forwarded to the monitor. A device attached to port 3 can analyze the resulting mirrored traffic.

Figure 54. Mirroring Ports

Monitor Port

Specified traffic is copiedand forwarded to Monitor Port

Mirrored PortsIngressTraffic Both Connected to

sniffer device

1 2 3 4


The G8272 supports four monitor ports. Each monitor port can receive mirrored traffic from any number of target ports.

Lenovo N/OS does not support “one to many” or “many to many” mirroring models where traffic from a specific port traffic is copied to multiple monitor ports. For example, port 1 traffic cannot be monitored by both port 3 and 4 at the same time, nor can port 2 ingress traffic be monitored by a different port than its egress traffic.

Ingress and egress traffic is duplicated and sent to the monitor port after processing.

Configuring Port Mirroring

The following procedure may be used to configure port mirroring for the example shown in Figure 54 on page 579:

1. Specify the monitoring port, the mirroring port(s), and the port-mirror direction.

2. Enable port mirroring.

3. View the current configuration.

RS 8272(config)# portmirroring monitorport 3 mirroringport 1 inRS 8272(config)# portmirroring monitorport 3 mirroringport 2 both

RS 8272(config)# portmirroring enable

RS 8272# show portmirroring

Port Monitoring : Enabled

Monitoring Ports Mirrored Ports

3 1, in

2, both


Part 9: Appendices Glossary

Getting help and technical assistance

Notices



Appendix A. Glossary

CNA Converged Network Adapter. A device used for I/O consolidation such as that in Converged Enhanced Ethernet (CEE) environments implementing Fibre Channel over Ethernet (FCoE). The CNA performs the duties of both a Network Interface Card (NIC) for Local Area Networks (LANs) and a Host Bus Adapter (HBA) for Storage Area Networks (SANs).

DIP The destination IP address of a frame.

Dport The destination port (application socket: for example, http-80/https-443/DNS-53)

HBA Host Bus Adapter. An adapter or card that interfaces with device drivers in the host operating system and the storage target in a Storage Area Network (SAN). It is equivalent to a Network Interface Controller (NIC) from a Local Area Network (LAN).

NAT Network Address Translation. Any time an IP address is changed from one source IP or destination IP address to another address, network address translation can be said to have taken place. In general, half NAT is when the destination IP or source IP address is changed from one address to another. Full NAT is when both addresses are changed from one address to another. No NAT is when neither source nor destination IP addresses are translated.

Preemption In VRRP, preemption will cause a Virtual Router that has a lower priority to go into backup if a peer Virtual Router starts advertising with a higher priority.

Priority In VRRP, the value given to a Virtual Router to determine its ranking with its peer(s). Minimum value is 1 and maximum value is 254. Default is 100. A higher number will win out for master designation.

Proto (Protocol) The protocol of a frame. Can be any value represented by a 8-bit value in the IP header adherent to the IP specification (for example, TCP, UDP, OSPF, ICMP, and so on.)

SIP The source IP address of a frame.

SPort The source port (application socket: for example, HTTP-80/HTTPS-443/DNS-53).

Tracking In VRRP, a method to increase the priority of a virtual router and thus master designation (with preemption enabled). Tracking can be very valuable in an active/active configuration.

You can track the following: Active IP interfaces on the Web switch (increments priority by 2 for each) Active ports on the same VLAN (increments priority by 2 for each) Number of virtual routers in master mode on the switch

VIR Virtual Interface Router. A VRRP address is an IP interface address shared between two or more virtual routers.

Virtual Router A shared address between two devices utilizing VRRP, as defined in RFC 2338. One virtual router is associated with an IP interface. This is one of the IP interfaces that the switch is assigned. All IP interfaces on the G8272s must be in a VLAN. If there is more than one VLAN defined on the Web switch, then the VRRP broadcasts will only be sent out on the VLAN of which the associated IP interface is a member.


VRID Virtual Router Identifier. In VRRP, a numeric ID is used by each virtual router to create its MAC address and identify its peer for which it is sharing this VRRP address. The VRRP MAC address as defined in the RFC is 00-00-5E-00-01-<VRID>.

If you have a VRRP address that two switches are sharing, then the VRID number needs to be identical on both switches so each virtual router on each switch knows with whom to share.

VRRP Virtual Router Redundancy Protocol. A protocol that acts very similarly to Cisco's proprietary HSRP address sharing protocol. The reason for both of these protocols is so devices have a next hop or default gateway that is always available. Two or more devices sharing an IP interface are either advertising or listening for advertisements. These advertisements are sent via a broadcast message to an address such as 224.0.0.18.

With VRRP, one switch is considered the master and the other the backup. The master is always advertising via the broadcasts. The backup switch is always listening for the broadcasts. If the master stops advertising, the backup will take over ownership of the VRRP IP and MAC addresses as defined by the specification. The switch announces this change in ownership to the devices around it by way of a Gratuitous ARP, and advertisements. If the backup switch didn't do the Gratuitous ARP the Layer 2 devices attached to the switch would not know that the MAC address had moved in the network. For a more detailed description, refer to RFC 2338.


Appendix B. Getting help and technical assistance

If you need help, service, or technical assistance or just want more information about Lenovo products, you will find a wide variety of sources available from Lenovo to assist you.

Use this information to obtain additional information about Lenovo and Lenovo products, and determine what to do if you experience a problem with your Lenovo system or optional device.Note: This section includes references to IBM web sites and information about obtaining service. IBM is Lenovo's preferred service provider for the System x, Flex System, and NeXtScale System products.

Before you call, make sure that you have taken these steps to try to solve the problem yourself.

If you believe that you require warranty service for your Lenovo product, the service technicians will be able to assist you more efficiently if you prepare before you call.

Check all cables to make sure that they are connected.

Check the power switches to make sure that the system and any optional devices are turned on.

Check for updated software, firmware, and operating-system device drivers for your Lenovo product. The Lenovo Warranty terms and conditions state that you, the owner of the Lenovo product, are responsible for maintaining and updating all software and firmware for the product (unless it is covered by an additional maintenance contract). Your service technician will request that you upgrade your software and firmware if the problem has a documented solution within a software upgrade.

If you have installed new hardware or software in your environment, check the IBM ServerProven website to make sure that the hardware and software is supported by your product.

Go to the IBM Support portal to check for information to help you solve the problem.

Gather the following information to provide to the service technician. This data will help the service technician quickly provide a solution to your problem and ensure that you receive the level of service for which you might have contracted. Hardware and Software Maintenance agreement contract numbers, if

applicable Machine type number (if applicable–Lenovo 4-digit machine identifier) Model number Serial number Current system UEFI and firmware levels Other pertinent information such as error messages and logs

http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us

https://www-947.ibm.com/support/entry/myportal


Start the process of determining a solution to your problem by making the pertinent information available to the service technicians. The IBM service technicians can start working on your solution as soon as you have completed and submitted an Electronic Service Request.

You can solve many problems without outside assistance by following the troubleshooting procedures that Lenovo provides in the online help or in the Lenovo product documentation. The Lenovo product documentation also describes the diagnostic tests that you can perform. The documentation for most systems, operating systems, and programs contains troubleshooting procedures and explanations of error messages and error codes. If you suspect a software problem, see the documentation for the operating system or program.


Appendix C. Notices

Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area.

Any reference to a Lenovo product, program, or service is not intended to state or imply that only that Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any Lenovo intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any other product, program, or service.

Lenovo may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

Lenovo (United States), Inc.1009 Think Place - Building OneMorrisville, NC 27560U.S.A.Attention: Lenovo Director of Licensing

LENOVO PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

The products described in this document are not intended for use in implantation or other life support applications where malfunction may result in injury or death to persons. The information contained in this document does not affect or change Lenovo product specifications or warranties.

Nothing in this document shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or third parties. All information contained in this document was obtained in specific environments and is presented as an illustration. The result obtained in other operating environments may vary.

Lenovo may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this Lenovo product, and use of those Web sites is at your own risk.


Any performance data contained herein was determined in a controlled environment. Therefore, the result obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

© Copyright Lenovo 2015 Appendix C: Notices 589

TrademarksLenovo, the Lenovo logo, Flex System, System x, NeXtScale System, and X-Architecture are trademarks of Lenovo in the United States, other countries, or both.

Intel and Intel Xeon are trademarks of Intel Corporation in the United States, other countries, or both.

Internet Explorer, Microsoft, and Windows are trademarks of the Microsoft group of companies.

Linux is a registered trademark of Linus Torvalds.

Other company, product, or service names may be trademarks or service marks of others.


Important NotesProcessor speed indicates the internal clock speed of the microprocessor; other factors also affect application performance.

CD or DVD drive speed is the variable read rate. Actual speeds vary and are often less than the possible maximum.

When referring to processor storage, real and virtual storage, or channel volume, KB stands for 1 024 bytes, MB stands for 1 048 576 bytes, and GB stands for 1 073 741 824 bytes.

When referring to hard disk drive capacity or communications volume, MB stands for 1 000 000 bytes, and GB stands for 1 000 000 000 bytes. Total user-accessible capacity can vary depending on operating environments.

Maximum internal hard disk drive capacities assume the replacement of any standard hard disk drives and population of all hard-disk-drive bays with the largest currently supported drives that are available from Lenovo.

Maximum memory might require replacement of the standard memory with an optional memory module.

Each solid-state memory cell has an intrinsic, finite number of write cycles that the cell can incur. Therefore, a solid-state device has a maximum number of write cycles that it can be subjected to, expressed as total bytes written (TBW). A device that has exceeded this limit might fail to respond to system-generated commands or might be incapable of being written to. Lenovo is not responsible for replacement of a device that has exceeded its maximum guaranteed number of program/erase cycles, as documented in the Official Published Specifications for the device.

Lenovo makes no representations or warranties with respect to non-Lenovo products. Support (if any) for the non-Lenovo products is provided by the third party, not Lenovo.

Some software might differ from its retail version (if available) and might not include user manuals or all program functionality.


Recycling InformationLenovo encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. Lenovo offers a variety of programs and services to assist equipment owners in recycling their IT products. For information on recycling Lenovo products, go to:

http://www.lenovo.com/recycling

http://www.lenovo.com/recycling


Particulate ContaminationAttention: Airborne particulates (including metal flakes or particles) and reactive gases acting alone or in combination with other environmental factors such as humidity or temperature might pose a risk to the device that is described in this document.

Risks that are posed by the presence of excessive particulate levels or concentrations of harmful gases include damage that might cause the device to malfunction or cease functioning altogether. This specification sets forth limits for particulates and gases that are intended to avoid such damage. The limits must not be viewed or used as definitive limits, because numerous other factors, such as temperature or moisture content of the air, can influence the impact of particulates or environmental corrosives and gaseous contaminant transfer. In the absence of specific limits that are set forth in this document, you must implement practices that maintain particulate and gas levels that are consistent with the protection of human health and safety. If Lenovo determines that the levels of particulates or gases in your environment have caused damage to the device, Lenovo may condition provision of repair or replacement of devices or parts on implementation of appropriate remedial measures to mitigate such environmental contamination. Implementation of such remedial measures is a customer responsibility..

Contaminant Limits

Particulate • The room air must be continuously filtered with 40% atmospheric dust spot efficiency (MERV 9) according to ASHRAE Standard 52.21.

• Air that enters a data center must be filtered to 99.97% efficiency or greater, using high-efficiency particulate air (HEPA) filters that meet MIL-STD-282.

• The deliquescent relative humidity of the particulate contamination must be more than 60%2.

• The room must be free of conductive contamination such as zinc whis-kers.

Gaseous • Copper: Class G1 as per ANSI/ISA 71.04-19853

• Silver: Corrosion rate of less than 300 Å in 30 days

1 ASHRAE 52.2-2008 - Method of Testing General Ventilation Air-Cleaning Devices for Removal Efficiency by Particle Size. Atlanta: American Society of Heating, Refrigerating and Air-Con-ditioning Engineers, Inc.2 The deliquescent relative humidity of particulate contamination is the relative humidity at which the dust absorbs enough water to become wet and promote ionic conduction.3 ANSI/ISA-71.04-1985. Environmental conditions for process measurement and control systems: Airborne contaminants. Instrument Society of America, Research Triangle Park, North Car-olina, U.S.A.


Telecommunication Regulatory StatementThis product may not be certified in your country for connection by any means whatsoever to interfaces of public telecommunications networks. Further certification may be required by law prior to making any such connection. Contact a Lenovo representative or reseller for any questions.


Electronic Emission NoticesWhen you attach a monitor to the equipment, you must use the designated monitor cable and any interference suppression devices that are supplied with the monitor.

Federal Communications Commission (FCC) Statement

Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.

Properly shielded and grounded cables and connectors must be used to meet FCC emission limits. Lenovo is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user’s authority to operate the equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that might cause undesired operation.

Industry Canada Class A Emission Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de Conformité à la Réglementation d'Industrie Canada

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

Australia and New Zealand Class A Statement

Attention: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

European Union EMC Directive Conformance Statement

This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. Lenovo cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the installation of option cards from other manufacturers.


This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment.

Lenovo, Einsteinova 21, 851 01 Bratislava, Slovakia

Germany Class A Statement

Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Betriebsmitteln, EMVG vom 20. Juli 2007 (früher Gesetz über die elektromagnetische Verträglichkeit von Geräten), bzw. der EMV EG Richtlinie 2004/108/EC (früher 89/336/EWG), für Geräte der Klasse A.

Dieses Gerät ist berechtigt, in übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die Lenovo (Deutschland) GmbH, Gropiusplatz 10, D-70563 Stuttgart.

Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4:

Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.

Nach der EN 55022: “Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funkstörungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Maßnahmen durchzuführen und dafür aufzukommen.”

Nach dem EMVG: Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG (früher 89/336/EWG) zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein.

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der Lenovo empfohlene Kabel angeschlossen werden. Lenovo übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der Lenovo verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der Lenovo gesteckt/eingebaut werden.

Deutschland:

Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Betriebsmittein Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit von Betriebsmitteln” EMVG (früher “Gesetz über die elektromagnetische Verträglichkeit von Geräten"). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG (früher 89/336/EWG) in der Bundesrepublik Deutschland.


Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Betriebsmitteln, EMVG vom 20. Juli 2007 (früher Gesetz über die elektromagnetische Verträglichkeit von Geräten), bzw. der EMV EG Richtlinie 2004/108/EC (früher 89/336/EWG), für Geräte der Klasse A.

Dieses Gerät ist berechtigt, in übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die Lenovo (Deutschland) GmbH, Gropiusplatz 10, D-70563 Stuttgart.

Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4: Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.

Nach der EN 55022: “Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funkstörungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Maßnahmen durchzuführen und dafür aufzukommen."

Nach dem EMVG: “Geräte dürfen an Orten, für die sie nicht ausreichend entstört sind, nur mit besonderer Genehmigung des Bundesministers für Post und Telekommunikation oder des Bundesamtes für Post und Telekommunikation betrieben werden. Die Genehmigung wird erteilt, wenn keine elektromagnetischen Störungen zu erwarten sind.” (Auszug aus dem EMVG, Paragraph 3, Abs. 4). Dieses Genehmigungsverfahren ist nach Paragraph 9 EMVG in Verbindung mit der entsprechenden Kostenverordnung (Amtsblatt 14/93) kostenpflichtig.

Anmerkung: Um die Einhaltung des EMVG sicherzustellen sind die Geräte, wie in den Handbüchern angegeben, zu installieren und zu betreiben.

Japan VCCI Class A Statement

This is a Class A product based on the standard of the Voluntary Control Council for Interference (VCCI). If this equipment is used in a domestic environment, radio interference may occur, in which case the user may be required to take corrective actions.


Japan Electronics and Information Technology Industries Association (JEITA) Statement

Japan Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guidelines (products less than or equal to 20 A per phase)

Japan Electronics and Information Technology Industries Association (JEITA) Confirmed Harmonics Guidelines with Modifications (products greater than 20 A per phase).

Korea Communications Commission (KCC) Statement

This is electromagnetic wave compatibility equipment for business (Type A). Sellers and users need to pay attention to it. This is for any areas other than home.


Russia Electromagnetic Interference (EMI) Class A statement


People’s Republic of China Class A electronic emission statement


Taiwan Class A compliance statement

© Copyright Lenovo 2015 Index 601

Index

Symbols[ ] 26

Numerics40GbE ports 130802.1p QoS 268802.1Q VLAN tagging 120, 284802.1Qaz ETS 284802.1Qbb PFC 281802.1Qbg. See EVB802.3x flow control 281

AAccess Control List (ACL) 189Access Control Lists. See ACLs.accessing the switch

Browser-based Interface 30, 35LDAP authentication 92RADIUS authentication 84security 75, 83TACACS+ 88

ACL metering 190ACLs 103, 189

FCoE 271FIP snooping 265, 266, 270Policy-based routing 341

active-active redundancy 505administrator account 42, 86advertise flag (DCBX) 291aggregating routes 434

example 441AH 372anycast address, IPv6 360application ports 105assistance, getting 581, 585Australia Class A statement 594authenticating, in OSPF 455Authentication Header (AH) 372autoconfiguration

IPv6 362link 56

auto-negotiationsetup 56

autonomous systems (AS) 448

Bbandwidth allocation 268, 286BBI 30

See Browser-Based Interface 449Bootstrap Router, PIM 482

Border Gateway Protocol (BGP) 423attributes 436failover configuration 439route aggregation 434route maps 430selecting route paths 438

Bridge Protocol Data Unit (BPDU) 146broadcast domains 117broadcast storm control 114Browser-Based Interface 30, 449BSR, PIM 482

CCanada Class A electronic emission statement 594CEE 263, 267

802.1p QoS 268bandwidth allocation 268DCBX 264, 267, 290ETS 263, 268, 284FCoE 266, 267LLDP 267on/off 267PFC 263, 269, 281priority groups 285

China Class A electronic emission statement 599Cisco EtherChannel 133, 135CIST 160Class A electronic emission notice 594Class of Service queueCOS queue 198CNA 266command conventions 26Command Line Interface 449Command-Line Interface (CLI) 51Community VLANPrivate VLANs

Community VLAN 127component, PIM 478configuration rules

CEE 267FCoE 266Trunking 133

configuringBGP failover 439DCBX 292ETS 287FIP snooping 273IP routing 328OSPF 459PFC 282port trunking 134spanning tree groups 156, 162

contamination, particulate and gaseous 592Converged Enhanced Ethernet. See CEE.Converged Network Adapter. See CNA.


DData Center Bridging Capability Exchange. See DCBX.date

setup 54DCBX 264, 267, 290default gateway 327

configuration example 330default password 42, 86default route

OSPF 453Dense Mode, PIM 477, 478, 486Designated Router, PIM 476, 481Differentiated Services Code Point (DSCP) 191digital certificate 373

generating 375importing 374

downloading software 66DR, PIM 476, 481DSCP 191

EEAPoL 96ECMP route hashing 337ECP 295Edge Control Protocol. See ECPEdge Virtual Bridging. See EVBelectronic emission Class A notice 594Encapsulating Security Payload (ESP) 372End user access control

configuring 80Enhanced Transmission Selection. See ETS.ENodes 266, 270ESP 372EtherChannel 132

as used with port trunking 133, 135Ethernet Nodes (FCoE). See ENodes.ETS 263, 268, 284

bandwidth allocation 268, 286configuring 287DCBX 292PGID 268, 285priority groups 285priority values 286

European Union EMC Directive conformance statement594

EVB 295Extensible Authentication Protocol over LAN 96external routing 424, 448

Ffactory default configuration 44, 52failover 495

overview 505FC-BB-5 265FCC Class A notice 594FCC, Class A 594

FCF 263, 266, 270, 275detection mode 271

FCoE 263, 265CEE 266, 267CNA 266ENodes 266FCF 266FIP snooping 263, 265, 266, 270FLOGI 271point-to-point links 265requirements 266SAN 265, 267topology 265VLANs 272

FCoE Forwarder. See FCF.FCoE Initialization Protocol snooping. See FIP snooping.Fibre Channel over Ethernet. See FCoE.Final Steps 63FIP snooping 263, 265, 266, 270

ACL rules 271ENode mode 271FCF mode 271timeout 271

first-time configuration 44, 51 to ??FLOGI 271flow control 281

setup 56frame size 118frame tagging. See VLANs tagging.

Ggaseous contamination 592gateway. See default gateway.Germany Class A statement 595getting help 585

Hhelp

sources of 585help, getting 585high-availability 501Host routes

OSPF 457Hot Links 493HP-OpenView 38, 529

IIBM DirectorSNMP

IBM Director 38, 529ICMP 104


IEEE standards802.1D 144802.1p 197802.1Q 120802.1Qaz 284802.1Qbb 281802.1Qbg 295802.1s 160802.1x 96802.3x 281

IGMP 104, 387PIM 484Querier 391, 418

IGMP Relay 404IGMPv3 392IKEv2 372

digital certificate 373, 374, 375preshared key 373, 375

IKEv2 proposal 374image

downloading 66INCITS T11.3 265incoming route maps 431internal routing 424, 448Internet Group Management Protocol (IGMP) 387Internet Key Exchange Version 2 (IKEv2) 372Internet Protocol Security

See also IPsec 371IP address 59

IP interface 59routing example 328

IP configuration via setup 59IP interfaces 59

example configuration 328, 330IP routing 59

cross-subnet example 326default gateway configuration 330IP interface configuration 328, 330IP subnets 326NAT mapping 332subnet configuration example 327switch-based topology 327

IP subnet mask 59IP subnets 327

routing 326, 327VLANs 117

IPsec 371key policy 375maximum traffic load 373

IPv6 addressing 357, 359ISL Trunking 132Isolated VLANPrivate VLANs

Isolated VLAN 127

JJapan Class A electronic emission statement 596

Japan Electronics and Information Technology Indus-tries Association statement 597

JEITA statement 597jumbo frames 118

KKorea Class A electronic emission statement 597

LLACP 136Layer 2 Failover 495LDAP

authentication 92Link Aggregation Control Protocol 136Link Layer Discovery Protocol 517LLDP 267, 290, 517logical segment. See IP subnets.lossless Ethernet 265, 267LSAs 446

Mmanual style conventions 26Maximum Transmission Unit 118meter 107meter (ACL) 190mirroring ports 579modes, PIM 477monitoring ports 579MSTPMultiple Spanning Tree Protocol (MSTP) 160MTU 118multi-links between switches

using port trunking 129multiple spanning tree groups 151Multiple Spanning Tree Protocol 160

NNeighbor Discovery, IPv6 364network component, PIM 478Network Load Balancing, See NLB,network management 30, 38, 529New Zealand Class A statement 594NLB 303notes, important 590notices 587


OOSPF

area types 444authentication 455configuration examples 460default route 453external routes 458filtering criteria 104host routes 457link state database 446neighbors 446overview 444redistributing routes 434route maps 430, 432route summarization 452router ID 454virtual link 454

outgoing route maps 431

Ppacket size 118particulate contamination 592password

administrator account 42, 86default 42, 86user account 42, 86

passwords 42payload size 118PBR.See Policy-Based RoutingPeople’s Republic of China Class A electronic emission

statement 599Per Hop Behavior (PHB)PHB 192PFC 263, 269, 281

DCBX 291PGID 268, 285PIM 475 to 487

Bootstrap Router (BSR) 482component 478Dense Mode 477, 478, 486Designated Router (DR) 476, 481examples 485 to 487IGMP 484modes 477, 478overview 476Rendezvous Point (RP) 476, 481Sparse Mode 476, 477, 478

PIM-DM 477, 478, 486PIM-SM 476, 477, 478Policy-Based Routing 341

Health Check 343port flow control. See flow control.port mirroring 579port modes 130Port Trunking 133

port trunkingconfiguration example 134description 135EtherChannel 132

portsconfiguration 56for services 105monitoring 579physical. See switch ports.

preshared key 373enabling 375

priority groups 285priority value (802.1p) 269, 284Priority-based Flow Control. See PFC.Private VLANs 127promiscuous port 127Protocol Independant Multicast (see PIM) 475 to 487protocol types 104PVID (port VLAN ID) 119

QQoS 187, 547QSFP+ 130Quality of Service 187, 547Querier (IGMP) 391, 418

RRADIUS

authentication 84port 1812 and 1645 105port 1813 105SSH/SCP 79

Rapid Spanning Tree Protocol (RSTP) 158Rapid Spanning Tree Protocol (RSTP)RSTP 158receive flow control 56redistributing routes 434, 441redundancy

active-active 505re-mark 107, 190Rendezvous Point, PIM 476, 481restarting switch setup 53RIP (Routing Information Protocol)

advertisements 382distance vector protocol 382hop count 382TCP/IP route information 23, 381version 1 382

RMON alarms 574RMON events 576RMON History 573RMON statistics 572route aggregation 434, 441route maps 430

configuring 432incoming and outgoing 431

route paths in BGP 438


Routed Ports 349Router ID

OSPF 454routers 326, 330

border 448peer 448port trunking 132switch-based routing topology 327

routes, advertising 448routing 424

internal and external 448Routing Information Protocol. See RIPRP candidate, PIM 476, 481RSA keys 79RSTP 158Russia Class A electronic emission statement 598rx flow control 56

SSA 372SAN 265, 267security

LDAP authentication 92port mirroring 579RADIUS authentication 84TACACS+ 88VLANs 117

security association (SA) 372segmentation. See IP subnets.segments. See IP subnets.server ports 240service and support

before you call 585service ports 105setup facility 44, 51

IP configuration 59IP subnet mask 59port auto-negotiation mode 56port configuration 56port flow control 56restarting 53Spanning-Tree Protocol 55starting 52stopping 53system date 54system time 54VLAN name 58VLAN tagging 56VLANs 58

SNMP 30, 38, 449, 529HP-OpenView 38, 529

SNMP Agent 529software

image 65Source-Specific MulticastSSM 392

Spanning-Tree Protocolmultiple instances 151setup (on/off) 55

Sparse Mode, PIM 476, 477, 478SSH/SCP

configuring 76RSA host and server keys 79

starting switch setup 52Static ARP 303stopping switch setup 53Storage Area Network. See SAN.subnet mask 59subnets 59summarizing routes 452switch failover 505switch ports VLANs membership 119

TTACACS+ 88tagging. See VLANs tagging.Taiwan Class A electronic emission statement 600TCP 104technical assistance 585technical terms

port VLAN identifier (PVID) 120tagged frame 120tagged member 120untagged frame 120untagged member 120VLAN identifier (VID) 120

Telnet supportoptional setup for Telnet support 64

text conventions 26time

setup 54trademarks 589transmit flow control 56Trunking

configuration rules 133tx flow control 56typographic conventions 26

UUDP 104United States FCC Class A notice 594upgrade, switch software 65uplink ports 240USB drive 68user account 42, 86

VVDP 295vDS. See virtual Distributed SwitchVEB 295VEPA 295


virtual Distributed Switch 248Virtual Ethernet Bridging. See VEBVirtual Ethernet Port Aggregator.See VEPAvirtual interface router (VIR) 502virtual link, OSPF 454Virtual Local Area Networks. See VLANs.virtual router group 505virtual router ID numbering 507Virtual Station Interface.See VSIVLAN tagging

setup 56VLANs 59

broadcast domains 117default PVID 119example showing multiple VLANs 124FCoE 272ID numbers 118interface 59IP interface configuration 330multiple spanning trees 145multiple VLANs 120name setup 58port members 119PVID 119routing 328security 117setup 58Spanning-Tree Protocol 145tagging 56, 119 to 125topologies 124

VRRP (Virtual Router Redundancy Protocol)active-active redundancy 505overview 502virtual interface router 502virtual router ID numbering 507vrid 502

VSI 295VSI Database.See VSIDBVSI Discovery and Configuration Protocol.See VDPVSIDB 296

Wwilling flag (DCBX) 291

Documents

Lenovo RackSwitch G8272 · 10/10/2010 · RackSwitch G8272: Application Guide