M1 VDX Ethenet Fabrice

VDX Ethernet FabricChul Ki KwonSystem Engineering30 April, 2014

1. Brocade Product Portfolio2. VDX Ethernet Fabric (VCS)3. Management - Firmware Upgrade - SNMP - Telnet / IP Address / MTU - Password Recovery - Licenses

4. Fabric Formations - ISL

5. Ethernet Fabric 2 Layer - VLAN - vLAGs

© 2013 Brocade Communications Systems, Inc. Company Proprietary Information 2

Agenda

11/13/2022

Brocade Product Portfolio

11/13/2022 3© 2011 Brocade Communications Systems, Inc. CONFIDENTIAL—For Internal Use Only

11/13/2022© 2014 Brocade Communications Systems, Inc. Company Proprietary Information 4

Brocade Product PortfolioBrocade Network AdvisorSimplified Management (SAN, LAN, VCS Fabrics, Wireless)

Plug-ins and

Integration

Lay

er 2

–3 (W

ired +

Wire

less)

Service Provider

Software Networking

Campus LAN

Brocade ICX 6430/6450

Brocade FastIron SX Series

Brocade MLXe Series

Data Center SAN

Fibre Channel

Brocade Blade Server Switches

Brocade 6520 Switch

Brocade Encryption Switch

Brocade 7800 Extension Switch

Brocade 6510 Switch

FS8–18Encrypt

ionBlade

FX8–24Extensi

onBlade

Layer 2–3

Layer 4–

7

Data Center LAN

Ethernet/IP

Brocade FCX Series

Brocade 300 Switch

FC16–32, –48

Switch Blade

Brocade VDX 6710/6720/6730/6740

Brocade DCX 8510

Backbones

Chassis

Fixed

Brocade ICX 6610

Brocade VDX Series

Brocade 6910 Ethernet Access

Switch

Brocade NetIronCES/CER Series

Brocade ADX

Series

Brocade Mobility Series

Brocade FCX Series

Brocade ADX 1000

Brocade ADX 4000

Brocade ADX 10000 Brocade 6505

Switch

Brocade VDX 8770

Brocade MLXe Series

Traditional Ethernet

Ethernet Fabric

Brocade ICX 6650

Brocade ICX 6650

FC8–64Blade

Brocade DCX and DCX-4S Backbones

Brocade Blade Server Switches

Brocade

Virtual ADX

Brocade Vyatta vRouter

Brocade ICX 7750

Brocade ICX 7750

© 2012 Brocade Communications Systems, Inc. Proprietary Information: NDA Required. Violators will be Hunted to the Ends of the Earth

VDX Ethernet Fabric (VCS)

What Is an

Ethernet

Fabric?

Optimized for server virtualization and cloud architectures

More efficient, higher throughput, lower latency

Scale-out vs. scale-up to increase flexibility and reduce cost

Simplified deployment and administration11/13/2022 6© 2012 Brocade Communications Systems, Inc. Proprietary Information

Data Center Challenges TodayAND REQUIREMENTS FOR TOMORROW

11/13/2022© 2012 Brocade Communications Systems, Inc. CONFIDENTIAL. FOR INTERNAL USE ONLY7

Poorly utilized Network Resources

Explosive Growth onVirtual Machines

Rip and Replace toSupport New Tech

Issu

es

More Efficient and Automated

Networking

Increased Scalability

and Performance

Flexibility to Support

New Technologies

Requir

ements

2009

Newly deployed Virtual Machines (VMs)Newly deployed physical hosts

The Tipping Point

Source: IDC

–Gartner

“By 2014, 80 percent of networking traffic will be between servers.”

8© 2011 Brocade Communications Systems, Inc. Proprietary Information 11/13/2022

코코코코

1Gbps 코코 10Gbps 코코코 코코코코 코코

코코

코코코

코코코

코코코 코코코 코코코코

11/13/2022© 2013 Brocade Communications Systems, Inc. Proprietary Information 9

코코코코 코코코코코 IP/ 코코코 코코코코

Client-Server Flow(North-South)

80%

Server-Server Flow(East-West)

20%

Server-Server Flow(East-West)

80%


The Changing Nature of Applications

Database

DISTRIBUTEDApplicat

ion

AppComponent

VM VM VM

Firewall

Database

VM

AppComponent


Ethernet Fabrics

11

CLASSIC HIERARCHICAL ARCHITECTURE

Core

Aggr

egati

onAc

cess

Rigid architecture, north-south optimized

Inefficient link utilization Individually managed switches, complex

Scale-up VM-ignorant

Topology freedom, east-west optimized

All links active, L1/2/3 multipathing

Fabric managed as one logical switch

Scale-out VM-aware

ETHERNET FABRIC ARCHITECTURE

Leaf

/

Spin

eCo

re

Scale-out

11/13/2022 12© 2013 Brocade Communications Systems, Inc. Company CONFIDENTIAL—For Internal Use Only

Brocade VCS Fabric Evolves Data Centers

11/13/2022 © 2012 Brocade Communications Systems, Inc. Proprietary Information12

Zero touch provisioning

Zero-touch VM discovery, configuration, and mobility

Self-forming trunks

Manage many switches as single logical device

5x faster to deploy

AUTOMATEDAUTOMATED All links fully active

Multi-pathing at all layers: L1/L2/L3

IP storage-aware

2x greater network utilization

AUTOMATEDEFFICIENT Multi-tenancy at scale with VCS Virtual Fabrics and VMware NSX

Scale-out non-disruptively

OpenFlow-ready Orchestration thru OpenStackFaster time to application deployment

CLOUD-OPTIMIZED

Brocade Continual Evolution with VCS Fabrics

Zero touch provisioning

Zero-touch VM discovery, configuration, and mobility

Self-forming trunks

Manage many switches as single logical device

50% lower opex

AUTOMATEDAUTOMATED

11/13/2022 13

Automation

• Zero-touch VM discovery, configuration, and mobility

• Self-forming trunks• Minimal configuration to add links or switches

• Manage many switches as single logical device

© 2014 Brocade Communications Systems, Inc. Proprietary Information

50% Lower Operating Expenses

Brocade VCS Fabrics Are Self-Forming• Automatic fabric creation and expansion (two steps, 1 to 2 minutes)• Automatic trunk creation

11/13/2022 14

30 GbE Data Center Bridging (DCB) trunk (3×10 GbE)10 GbE DCB link

RBridge 1

RBridge 2

RBridge 3

GEHA reduced basic network

management time by 20 percent, or over 1000man-hours per

year.

SunPower reduced setup time by over 80 percent compared

to its three-tier network.


•Brocade VCS Fabric technology, with 10 Brocade VDX 6740 Switches:•Step 1: Turn switches on•Step 2: Configure RBridge IDs

•Step 3: Connect cables•Step 4: There’s no step 4

•Cisco FabricPath, 10 Nexus 7000 Switches:•Step 1: Create two portchannels between a Nexus pair•Step 2: Activate Virtual PortChannel (vPC) between them•Step 3: Activate FabricPath on the vPC pair•Step 4: Activate vPC+ in the pair (~7 commands per switch)•[…]•Step 19: Configure Media Access Control (MAC) learning mode for FabricPath Virtual LANs (FP VLANs)•Step 20: Activate FabricPath in the defined portchannel•Step 21: Repeat the previous 20 steps for the four other vPC+ pairs•[…]•Step 101: Configure two portchannels between each edge vPC pair and the core vPC pair•[…]•Step 106: Activate FabricPath on the eight defined portchannels•[…]•Step 114: On each Nexus 7000 in the core vPC, define eight portchannels•[…]11/13/2022 15

10-Node Fabric SetupBrocade VCS Fabric technology vs. competitor


•Simplified Brocade VCS Fabric deployment, scalability, and management of the network

•Enable VCS fabric capabilities on each switch (on by default)

•Connect the switches•Fabric automatically forms• Common configuration across all switches, Inter-Switch Link (ISL) Trunks auto-form

•Managed as a single logical chassis

16

Logical Chassis DetailsAuto-configuration

VCS

VCS

VCS

© 2014 Brocade Communications Systems, Inc. Proprietary Information 11/13/2022

11/13/2022 17

Brocade VM-Aware Network Automation and MigrationDynamic configuration and secure communication

• No need for manual configuration of MAC addresses and port profiles; less error-prone

• Minimizes procedural delays between the server and network IT teams

• Eases integration of multiple Brocade VCS fabrics with VMware

• Protects against VM/MAC spoofing via secure vCenter communication

conf

BrocadeNetworkAdvisor

conf

conf

confconf

conf

conf

NAS iSCSI FCoE FC iSCSIInfiniBand

VM

vCenter


11/13/2022 18

Efficient

• All links fully active; none on standby

• Multipathing at all layers of the network: Layer 1, Layer 2, and Layer 3

• IP Storage Aware


2x Greater Network Utilization


Brocade VCS Multi-pathing at Multiple LayersDramatic Increases In Network Utilization and Reliability

L3: Fabric load balancing across multiple L3 gateways

FEATUREL1: Trunking with frame striping

33%

33%

33% L2: Equal Cost

Multi-Pathing (ECMP)

Improved scalability and resiliency

BENEFITNear-perfect load balancing across all links in a trunk groupAll links utilized with flow-based load balancing

Layer 3 Core

Brocade VCS Fabric

11/13/2022 20

Cloud Optimized

Multi-tenancy at scale with VCS Virtual Fabrics and VMware NSX

Scale-out non-disruptively

OpenFlow-ready Orchestration thru OpenStack


Faster Time to Application Deployment

21© 2013 Brocade Communications Systems, Inc. CONFIDENTIAL — Discussion under NDA

ManagementFirmware Upgrade / SNMP / Telnet / Password Recovery / Licenses

3. Management

• After completing this module, students should able to discuss hot to troubleshoot firmware upgrade issues :

- Show commands firmware download show if downgrading check enabled features firmware download history RASlog – Look for reason firmware download failed if using a USB drive: Is the USB a Brocade branded USB drive? Is USB device mounted Do a dir – check path is correct Can you ping the remote server Check path to firmware

Firmware Upgrade

11/13/2022© 2011 Brocade Communications Systems, Inc. CONFIDENTIAL—For Internal Use Only 22

3. Management

• Upgrading firmware via CLI : - Put everything on one command line, example : If in logical chassis mode and want to upgrade all switches at once : VDX1#firmware download logical-chassis ftp host 10.255.252.50 user dev password dev123 directory /nos file nos4.0.0a auto-activate rbridge-id all

When the auto-activate option is specified, all of the specified Rbridges in the command will be rebooted at the same time

Which can cause traffic disruption Auto-activate is not recommand If only want to upgrade a single switch : VDX1#firmware download ftp host 10.255.252.50 user dev password dev123 directory /nos file nos4.0

VDX Firmware Download


3. Management

• Using interactive mode, example :VDX1# firmware download interactiveDo you want to download to multiple nodes in the cluster? [y/n] : yServer name or IP address : 10.255.252.50File name : /nos/nos4.0.0aProtocol (ftp, scp, sftp) : ftpUser : adminPassword : ********Enter ‘all’ for all nodes or range of rbridgeIds : allActivate firmware on all nodes after download? [y/n] : yDo you want to continue? [y/n] : y

VDX Firmware Download (Cont.)


3. Management

• Detailed display of all firmware partitionsVDX1# show versionNetwork Operating System SoftwareNetwork Operating System Version : 4.0.0Copyight (c) 1995-2012 Brocade Communications Systems, Inc.Firmware name : 4.0.0aBuild Time : 17:26:29 Aug 2, 2013Install Time : 20:46:17 Aug 26, 2013Kernel : 2.6.34.6BootProm : 1.0.1Control Processor : e500mc with 7168 MB of memorySlot Name Primary/Secondary Versions Status-----------------------------------------------------------------------------------------------------------M1 NOS 4.0.0a ACTIVE*

Command : show version


3. Management

• Detailed the firmware download history

VDX1# show firmwaredownloadhistory

Firmware version history

Sno Date & Time Switch Name Slot PID OS Version1 Thu Mar 6 02:48:59 2014 sw0 0 1651 4.1.0a2 Mon Dec 30 19:28:59 2013 sw0 0 1719 4.0.1

Command : firmwaredownloadhistory


3. Management

• If the server is not accessible or the firmware path is not valid the firmware download will fail and the this message will be displayed :

The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, the user/password and the firmware path are valid.

• Check - User name / Password - Path/filename on remote server - Can you ping the server from the switch? - Check for the presents of a firewall blocking ports

Common Error Message


3. Management

• If using a USB drive : - Must be Brocade braded - Must be mounted (usb on command) - Verify firmware version is on USB

VDX1# usb dirNos4.0.0a/ 600MB 2012 Feb 12 09:22

• Example of firmware download from the USB drive :VDX1# firmware download usb directory nos4.0.0a

USB drive


3. Management

• After completing this module students should be able to describe things to look at when troubleshooting issues with SNMP Traps, including:

- Where to get MIBs - Verifying switch configuration - Missing SNMP traps - Certain SNMP MIB’s not reporting a correct value - CPU utilixation

SNMP


3. Management

• Information on NOS MIBs - Do a search on “Brocade mibs download” and you should see the below link :

http://my.brocade.com/wps/myportal/!ut/p/b1/04_Sj9Q1MjazMDI0NrDUj9CPykssy0xPLMnMz0vMAfGjzOKd3BzDjE2MjQ39vbycDTzdXYJCLb18jQycTIEKIoEKDHAARwO8-n3MoPpxKjAhzn48FhDQH64fhd-JJlAFeLzo55Gfm6qfG5Xj5mbpqQsAytaOsQ!!/dl4/d5/L2dJQSEvUUt3QS80SmtFL1o2X0JGQVYzNDMzMU9KSkMwSUdEUlU5Sk0yMEI1/

SNMP


3. Management

VDX1# show running-config snmp-server

snmp-server host 172.24.130.66 private version 1 udp-port 162

SNMP Run Command : show running-config snmp-server


3. Management

• After completing this module students should be able to describe how to troubleshoot issues with telneting into the management port of the switch including :

- Check IP address configuration - Check the fabric VIP configuration - Can you ping the switch - Use trace route to verify network connectivity

TELNET


3. Management

• Use the console port to access the switch - If Logical Chassis mode is enable all management interface for every switch in the fabric will be displayed VDX1# show running-config interface ManagementInterface Management 1/0 ip address 10.255.248.7/25 ip gateway-address 10.255.248.126!no telnet server shutdown

• Verify the Gateway is setup correctly

VDX1# show running-config rbridge-id 1Rbridge-id 1

TELNET Run Command : show run int management


3. Management

• The show vcs command will display the management IP address for very switch in the fabric :

VDX1# show vcsConfig Mode : DistributedVCS Mode : Logical ChassisVCS ID : 1VCS GUID : 53a32dc4-d159-4e34-b7f8-4ed5645e262fTotal Number of Nodes : 2Rbridge-Id WWN Management IP VCS Status Fabric Status HostName-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------2 10:00:00:27:F8:D8:6A:82* 172.24.130.232 Online Online sw03 >10:00:00:27:F8:D3:C6:6C 172.24.130.233 Online Online sw0

TELNET Run Command : show vcs


3. Management

• After completing this module students should be able to describe steps to recover an account password

• If the fabric is in Logical Chassis mode, this must be done on the principal switch• Must login as root

Must login as root :SW1:root>noscliSW1# configurare terminalSW1(config)#username new_account_name password new_password

Password Recovery


3. Management

• After completing this module students should be able to verify the required licenses are installed

Licenses


3. ManagementLicenses


• Command : show license

sw02# show license rbridge-id: 2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FCoE Base license Feature name:FCOE_BASE License is validxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 10G Port Upgrade license Feature name:PORT_10G_UPGRADE License is valid Capacity: 24xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 40G Port Upgrade license Feature name:PORT_40G_UPGRADE License is valid Capacity: 4

• Command : show license

sw02# show license xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx VCS Fabric license Feature name:VCS_FABRIC License is valid

3. Management

• Here is some examples on issues you might see if licenses are not installed : - In this example the user is trying to configure an FCoE port on a switch that does not have an FCoE licenses installed SW1(config-if-te-1/0/10)# fcoeport default %%Error”FCoE license not present.

- In this example the user is trying to enable BGP on a switch that does not have a Layer 3 license SW1(config-rbridge-id-3)# router bgp %%Error Layer 3 license not present.

- In this example the user is trying to reserve a port but does not have any available ports and needs a DPOD license SW1(config-dpod-1/0/25)# reserve %%No more license available to assign to port

Licenses


Test LAB Topology


▷ Traffic Flow - 10 G - 1 G - Traffic Flow

▷ IP Address - VDX#02 10.1.1.1/24 - VDX#03 10.1.1.2/24 - ICX#04 10.1.1.3/24 ▷ 기기 기기기 - Default Routing

▷ 기기 Traffic - Traffic : 1 G

Ten3/0/15Ten3/0/16

N2X

1 2

Ten3/0/1

Ten2/0/3

E1/1/1

ICX6450#04VALN10_10.1.1.3/

24

VDX#02VLAN10_10.1.1.1/

24

VDX#03VLAN10_10.1.1.2/24

10.1.1.12/24

10.1.1.11/24

E1/1/2

Ten3/0/3

Ten4/0/1

LAG

vLAG-1 vLAG-1

Fabric Formations

Click icon to add picture

40© 2013 Brocade Communications Systems, Inc. CONFIDENTIAL — Discussion under NDA

ISL / Trunk

4. Fabric Formations

• ISLs not coming up on certain ports - If the ISL is segmented and the interface is up/up, the problem is most likely a configuration issue Ensure both end Brocade switches are configured correctly with respect to ISL configuration, VCS mode, VCS ID and Rbridge ID

- ISL config disabled? (no fabric isl enable) If disabled, it becomes an edge port, See Fabric Formation module for more information

- Check the interface status and error statistics - Ping the remote Rbridge

ISL (Inter Switch Link)



• Verify configuration of VCS, VCS_ID and RB_ID - Make sure the number of switches in the fabric has not exceed the supported nomber - Run command : show vcs

- Verify configuration of ISL ports

ISL Verify Configuration



• To quickly identify which ports are being used as ISLs ports, use the show ip interface brief command

ISL Verifying VCS Fabric ISL Formation



• To quickly identify which ports are being used as ISLs ports, use the show ip interface brief command

ISL Check Error Counters


Ethernet Fabric 2 Layer

© 2013 Brocade Communications Systems, Inc. CONFIDENTIAL—For Internal Use Only 45

VLAN / vLAGs / ELD

5. Ethernet Fabric 2 Layer

• Physical Ethernet interface can be configured either as access (untagged) ports or a trunk (tagged) ports, as follows :

- An access port can have only one VLAN configured on the interface : it can carry traffic for only one VLAN - A trunk port can have two or more VLANs configured on the interface : it can carry traffic for several VLANs simultaneously

• When you configure a port in access mode, you can specify which VLAN it will carry the traffic for that interface

- If you do not configure a VLAN for a port in access mode, the interface carries traffic for the default VLAN

• By default, a trunk port sends traffic to and from all VLANs - You can remove VLANs from this inclusive list to prevent traffic from specific VLANs from passing over that trunk port

VLAN Verify Tagged / Untagged Requirements



• When troubleshooting connectivity issues between hosts, verify the configurations to confirm :

- That traffic is either tagged or untagged based on requirements

- That no port in the path of the devices is restricting the VLAN that is being used to connect the two hosts

- If in same VLAN, confirm that host hosts are in the same subnet For host on different VLANS, a router (or VE) will need to be configured

- For a trunk (LAG/vLAG) in the path, parameters that must match on both ends before a trunk can operate correctly are : Trunking mode Native VLAN Allowed VLANs

VLAN Verify Tagged / Untagged Requirements (cont.)



• Verify the VLAN configuration of the physical port

• This port is configured as a trunk port

VLAN Check Physical Port Assigned VLANs(cont.)



• If hosts within the same VLAN cannot communicate, verify their VLAN membership / configuration

- Use show vlan brief command to verify switch port membership

VLAN Check Physical Port Assigned VLANs



• You can verify VLAN information for each L2 interface - Use show vlan brief command to verify switch port membership

VLAN Check Physical Port Assigned VLANs(cont.)



• Verify that the MAC of the problem hosts are associated with the correct VLAN in the VLAN database

• When an end device comes online in the fabric, the database learns the VLAN ID of that specific MAC through the normal MAC learning process

• You can view the database using the show mac-address-table command

VLAN to MAC Association



• VLink aggregation allows you to bundle multiple physical Ethernet links to form a single logical trunk providing enhanced performance and redundancy. The aggregated trunk is referred to as a Link Aggregation Group (LAG).

• The LAG is viewed as a single link by connected devices, the Spanning Tree Protocol, IEEE 802.1Q VLANs, and so on. When one physical link in the LAG fails, the other links stay up and there is no disruption to traffic.

vLAGs





Interface port-channel 10vlag ignore-splitNo shut!interface TenGigabitEthernet 2/0/1channel-group 10 mode active type standardNo shut

vLAGs





switch# show port-channel detailLACP Aggregator: Po 27Aggregator type: StandardIgnore-split is disabledActor System ID - 0x8000,00-05-33-6f-18-18Admin Key: 0027 - Oper Key 0027Receive link count: 4 - Transmit link count: 4Individual: 0 - Ready: 1Partner System ID - 0x8000,00-05-1e-cd-6e-9fPartner Oper Key 0027Member ports on rbridge-id 231:Link: Te 231/0/22 (0xE718160201) sync: 1 *Link: Te 231/0/23 (0xE718170202) sync: 1Link: Te 231/0/36 (0xE718240305) sync: 1Link: Te 231/0/37 (0xE718250306) sync: 1

vLAGs


Thank You

M1 VDX Ethenet Fabrice

Documents

Transcript of M1 VDX Ethenet Fabrice