1 / 94

Cuong Tran SAVBU – TME August 2009

Nexus 1000V and HP’s Virtual Connect. Cuong Tran SAVBU – TME August 2009. Configurations of Nexus 1000V with HPVC. Nexus 1000V and HPVC Environment Nexus 5000 Configurations Ethernet/Port-Channel configs HPVC Configurations Network Settings (Ethernet & FC) Server Profiles

delila
Télécharger la présentation

Cuong Tran SAVBU – TME August 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Nexus 1000V and HP’s Virtual Connect Cuong Tran SAVBU – TME August 2009

  2. Configurations of Nexus 1000V with HPVC • Nexus 1000V and HPVC Environment • Nexus 5000 Configurations • Ethernet/Port-Channel configs • HPVC Configurations • Network Settings (Ethernet & FC) • Server Profiles • Nexus 1000V Configurations • Network Configurations • Adding Servers • Migrating Service Console • VMotion of VM • VMotion within same HP c7000 chassis

  3. Nexus 1000V – HPVC Test Environment EMC CX4-480 MDS9124-1 MDS9124-2 Nexus 5000-1 Nexus 5000-2 Interconnect Bay1 Interconnect Bay2 Fibre Channel Bays 3 & 4 HPVC Flex-10 HPVC 1G/10G HPVC FC HPVC FC HP c7000-1 HP c7000-2 • Blade Servers Info: • 2 BL460c G5 • Dual 1G LOMs • Dual 1G Port Mez (slot 1) • Dual 4G FC Mez (slot 2) • Blade Servers Info: • 5 BL490c G6 • Dual 10G LOMs • Dual 4G FC Mez (slot 1)

  4. VMWare ESX Server - VEM View for BL460c G5 • Nexus 1000V VEM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • VMotion  VLAN 50 • VM Data VLANs  VLAN 51 – 52 • Nexus 1000V Traffic FLow • vmnic0/vmnic1 (PC) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2/vmnic3 (PC) used for vm-uplink (VM Data traffic VLANs 51 & 52) Nexus 5000-1 Nexus 5000-2 HPVC 1G/10G Bay1 HPVC 1G/10G Bay2 Stacking Links HPVC 1G/10G Bay4 HPVC 1G/10G Bay3 vmnic0 vmnic1 vmnic2 vmnic3 HP c7000-1 1G 1G 1G 1G Nexus 1000V Service Console, VMotion, Control & Packet N1K Port Profiles (VM Port Groups) VM #1 VM #2 VM #3 ESX Blade Server

  5. VMWare ESX Server - VSM View for BL490c G6 • Nexus 1000V VSM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • ESX – VSM Traffic Flow • vmnic0 allows VLANs 250-251, 182 • vmnic1 can be used as standby • This ESX server will not be using N1K to manage the vmnics • VSMs will be installed on the BL490c G6 blade servers on HP c7000 - 1 Nexus 5000-1 Nexus 5000-2 Flex-10 Bay1 Flex-10 Bay2 vmnic0 vmnic1 HP c7000-2 4G 4G VMWare vSwitch Service Console, Control & Packet N1K-VSM (VM) ESX Blade Server

  6. VMWare ESX Server - VEM View for BL490c G6 • Nexus 1000V VEM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • VMotion  VLAN 50 • VM Data VLANs  VLAN 51 – 52 • Nexus 1000V Traffic FLow • vmnic0/vmnic1 (PC) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2/vmnic3 (PC) used for vm-uplink (VM Data traffic VLANs 51 & 52) Nexus 5000-1 Nexus 5000-2 Flex-10 Bay1 Flex-10 Bay2 vmnic0 vmnic1 vmnic2 vmnic3 HP c7000-2 4G 4G 6G 6G Nexus 1000V Service Console, VMotion, Control & Packet N1K Port Profiles (VM Port Groups) VM #1 VM #2 VM #3 ESX Blade Server

  7. Nexus 5000 Configurations

  8. Nexus 5000-1 with HPVC 1/G/10G Configuration Nexus 5000-1 (HPVC 1/G10G) n5k-1# show running-config interface ethernet 1/1-2 version 4.1(3)N1(1) interface Ethernet1/1 description "HP Chassis 1 HPVC 1G/10G Bay1 - GE Port1" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 speed 1000 channel-group 200 mode active interface Ethernet1/2 description "HP Chassis 1 HPVC 1G/10G Bay1 - GE Port2" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 speed 1000 channel-group 200 mode active n5k-1# show running-config interface port-channel 200 version 4.1(3)N1(1) interface port-channel200 switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 N5K-1 & N5K-2 Port-Channel n5k-1# show running-config interface ethernet 1/17-18 version 4.1(3)N1(1) interface Ethernet1/17 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 interface Ethernet1/18 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 N5K-1 & N5K-2 Port-Channel n5k-1# show running-config interface port-channel 1 version 4.1(3)N1(1) interface port-channel1 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 Nexus 5000-1 Nexus 5000-2 Eth1/17 Eth1/17 Eth1/18 Eth1/18 Eth1/1 Eth1/2 Eth1/1 Eth1/2 Port 1 Port 2 Port 1 Port 2 Chassis-1 HPVC 1G/10G Bay1 Chassis-1 HPVC 1G/10G Bay2

  9. Nexus 5000-2 with HPVC 1/G/10G Configuration Nexus 5000-2 (HPVC 1/G10G) n5k-2# show running-config interface ethernet 1/1-2 version 4.1(3)N1(1) interface Ethernet1/1 description "HP Chassis 1 HPVC 1G/10G Bay2 - GE Port1" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 speed 1000 channel-group 200 mode active interface Ethernet1/2 description "HP Chassis 1 HPVC 1G/10G Bay2 - GE Port2" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 speed 1000 channel-group 200 mode active n5k-2# show running-config interface port-channel 200 version 4.1(3)N1(1) interface port-channel200 switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 N5K-1 & N5K-2 Port-Channel n5k-2# show running-config interface ethernet 1/17-18 version 4.1(3)N1(1) interface Ethernet1/17 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 interface Ethernet1/18 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 N5K-1 & N5K-2 Port-Channel n5k-2# show running-config interface port-channel 1 version 4.1(3)N1(1) interface port-channel1 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 Nexus 5000-1 Nexus 5000-2 Eth1/17 Eth1/17 Eth1/18 Eth1/18 Eth1/1 Eth1/2 Eth1/1 Eth1/2 Port 1 Port 2 Port 1 Port 2 Chassis-1 HPVC 1G/10G Bay1 Chassis-1 HPVC 1G/10G Bay2

  10. Nexus 5000-1 with Flex-10 Configuration Nexus 5000-1 (Flex-10) n5k-1# show running-config interface ethernet 1/13-14 version 4.1(3)N1(1) interface Ethernet1/13 description "HP Chassis 2 Flex-10 Bay1 - Port2" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 channel-group 100 mode active interface Ethernet1/14 description "HP Chassis 2 Flex-10 Bay1 - Port3" switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 channel-group 100 mode active n5k-1# show running-config interface port-channel 100 version 4.1(3)N1(1) interface port-channel100 switchport mode trunk switchport trunk native vlan 182 switchport trunk allowed vlan 2-3967,4048-4093 N5K-1 & N5K-2 Port-Channel n5k-1# show running-config interface ethernet 1/17-18 version 4.1(3)N1(1) interface Ethernet1/17 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 interface Ethernet1/18 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 N5K-1 & N5K-2 Port-Channel n5k-1# show running-config interface port-channel 1 version 4.1(3)N1(1) interface port-channel1 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 Nexus 5000-1 Nexus 5000-2 Eth1/17 Eth1/17 Eth1/18 Eth1/18 Eth1/13 Eth1/14 Eth1/13 Eth1/14 Port 2 Port 3 Port 2 Port 3 Chassis-2 Flex-10 Bay1 Chassis-2 Flex-10 Bay2

  11. Nexus 5000-2 with Flex-10 Configuration Nexus 5000-2 (Flex-10) n5k-2# show running-config interface ethernet 1/13-14 version 4.1(3)N1(1) interface Ethernet1/13 description "HP Chassis 2 Flex-10 Bay2 - Port2" switchport mode trunk switchport trunk native vlan 300 switchport trunk allowed vlan 2-3967,4048-4093 channel-group 100 mode active interface Ethernet1/14 description "HP Chassis 2 Flex-10 Bay2 - Port3" switchport mode trunk switchport trunk native vlan 300 switchport trunk allowed vlan 2-3967,4048-4093 channel-group 100 mode active n5k-2# show running-config interface port-channel 100 version 4.1(3)N1(1) interface port-channel100 switchport mode trunk switchport trunk native vlan 300 switchport trunk allowed vlan 2-3967,4048-4093 N5K-1 & N5K-2 Port-Channel n5k-2# show running-config interface ethernet 1/17-18 version 4.1(3)N1(1) interface Ethernet1/17 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 interface Ethernet1/18 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 channel-group 1 N5K-1 & N5K-2 Port-Channel n5k-2# show running-config interface port-channel 1 version 4.1(3)N1(1) interface port-channel1 switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 Nexus 5000-1 Nexus 5000-2 Eth1/17 Eth1/17 Eth1/18 Eth1/18 Eth1/13 Eth1/14 Eth1/13 Eth1/14 Port 2 Port 3 Port 2 Port 3 Chassis-2 Flex-10 Bay1 Chassis-2 Flex-10 Bay2

  12. HP Virtual Connect Configurations

  13. HP’s Virtual Connect Tasks • Build a “Shared Uplink” • Define Ethernet Uplinks • Configure “Associated” Networks • Build SAN Fabrics • Define FC Uplinks • Build Server Profiles (For VSM and VEM Servers) • Define NIC(s) • Assign Network(s) • Set port speed (Flex-NIC can be customized) • Define HBA • Assign to physical blade server

  14. HP c7000-2 Flex-10 - Shared Uplinks Bay 1 • Within Virtual Connect Manager, create a “Shared Uplink Set” • Name: “C7K2-Uplink Bay1” • Added Port X2 and Port X3 to Uplink Set • Speed should be left at “auto” • Repeat steps for Bay 2 “Shared Uplink Set”

  15. HP c7000-2 Flex-10 - Associating Networks Bay 1 • In the same area with the “Shared Uplink Set”, you will want to associate Networks (a.k.a. VLANs) to the uplink set. This will determine which VLANs will traverse these uplinks • Click “Add”  Give name for each of the networks needed (ex: b1-cisco-lab, b1-vsm-control, etc) • Provide VLAN number for the network • For ESX “Service Console” VLAN, please make that VLAN to be the “Native VLAN” in this “Associated Networks” – this example is VLAN 182 • When finished, click on “Apply” – Adding/Removing Networks is not disruptive. • Repeat steps for Bay2 “Shared Uplink Set”, should have the exact same networks (VLANs)

  16. HP c7000-2 Flex-10 – Shared Uplink Set for Bay 2 Configuration for Shared Uplink Set and Associated Networks for Bay 2

  17. HP c7000-1 HPVC1G/10G - Shared Uplinks Bay 1 HPVC 1G/10G Configuration for Shared Uplink Set and Associated Networks for Bay1

  18. HP c7000-1 HPVC1G/10G - Shared Uplinks Bay 2 HPVC 1G/10G Configuration for Shared Uplink Set and Associated Networks for Bay2

  19. HP c7000-1 HPVC FC – C7K1-Fabric-A • In Virtual Connect Manager, defining “SAN Fabrics” chooses which uplink ports on the HPVC FC module to use for the SAN traffic • Provide a Fabric Name: ex: C7K1-Fabric-A • Add the uplink ports for the Fabric (in this example is uplinks port 1 & 2 on bay 5) • Repeat steps for the second Fabric (C7K1-Fabric-B) using Bay 6

  20. HP c7000-1 HPVC FC – C7K1-Fabric-B

  21. HP c7000-2 HPVC FC – C7K2-Fabric-A

  22. HP c7000-2 HPVC FC – C7K2-Fabric-B

  23. Server Profile VSM Servers

  24. ESX VSM Server Network Layout • Nexus 1000V VSM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • ESX – VSM Traffic Flow • vmnic0 allows VLANs 250-251, 182 • vmnic1 can be used as standby • This ESX server will not be using N1K to manage the vmnics Flex-10 Bay1 Flex-10 Bay2 vmnic0 vmnic1 4G 4G VMWare vSwitch Service Console, Control & Packet N1K-VSM (VM) ESX Blade Server

  25. Server Profile (ESX VSM) In Virtual Connect, creation of a “Server Profile” defines a few parameters Ethernet Network - how many NICs and which VLAN(s) those NICs will be using FC SAN – how many HBAs and which SAN Fabric they will connect to Assign Profile – Binds this Server Profile to a particular Blade Server in the chassis

  26. Server Profile (ESX VSM) – Ethernet Network With building a Blade Server to host the VSM (VM), validating that the NIC(s) allows the required N1K VLANs is needed. Since there are multiple VLANs needed, then these NICs must allow multiple networks. To do this for the Server Profile, select the NIC “port” and click on the drop-down box and choose “Multiple Networks”. Setting the “Port Speed” is allowed and can be traffic shape to a specific speed (Tx only). In this example, we have set the speed to be “Custom”, which will set the speed of the link (i.e. 4G)

  27. Server Profile (ESX VSM) – Ethernet Network continued… When choosing “Multiple Networks”, a new window will pop up. The window below shows what Networks are allowed to flow through this NIC. Just click on the drop-down box and choose the network. When finished, click “OK”. Note: Any Changes to the “Server Profile” will have to be an offline task (i.e. Server is down)

  28. Server Profile (ESX VSM) – FC SAN In the HP Blade Servers, the FC Mez cards are hard code to a specific Interconnect bay. The test environment has the FC Mez card placed in slot1, which will bind FC Port 1 to Bay3 and FC Port 2 to Bay4. With that in mind, click on the drop-down section for the FC SAN Name that was created and choose the appropriate SAN Fabric.

  29. Server Profile (ESX VSM) – Assign Profile Last portion for the Server profile is to assign the profile to the physical blade server in the chassis. In this example, Blade Server in slot 1 will be assign for the VSM. This server is a BL490c G6 (Intel processor). Since the test environment will have 2 VSMs (dual-supervisors), another blade server will be used. The second blade server should have the same settings as this server profile bound to Server in slot 2.

  30. Server Profile VEM Servers for c7000-1

  31. ESX VEM Server for HP c7000-1 • Nexus 1000V VEM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • VMotion  VLAN 50 • Data VLANs  VLAN 51 – 52 • Nexus 1000V Traffic FLow • vmnic0/vmnic1 (PC) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2/vmnic3 (PC) used for vm-uplink • (Data traffic VLANs 51 & 52) HPVC 1G/10G Bay1 HPVC 1G/10G Bay2 Stacking Links HPVC 1G/10G Bay4 HPVC 1G/10G Bay3 vmnic0 vmnic1 vmnic2 vmnic3 1G 1G 1G 1G Nexus 1000V Service Console, VMotion, Control & Packet N1K Port Profiles (VM Port Groups) VM #1 VM #2 VM #3 ESX Blade Server

  32. Server Profile (ESX VEM) • Similar to creating a Server Profile for the ESX VSM server, the Server Profile for the “ESX VEM” server will be slightly different. In this Server Profile, 4 GE NICs will be used. With the topology that is being deployed in the test environment, the following are the VLAN traffic flows: • vmnic0 (GE) & vmnic1 (GE) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2 (GE) & vmnic3 (GE) used for vm-uplink (VM Data traffic VLANs 51 & 52)

  33. Server Profile (ESX VEM) – Ethernet Network (Port 1 = vmnic0) As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The window below shows what Networks are allowed to flow through this Port 1 (vmnic0). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  34. Server Profile (ESX VEM) – Ethernet Network (Port 2 = vmnic1) As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The window below shows what Networks are allowed to flow through this Port 2 (vmnic1). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  35. Server Profile (ESX VEM) – Ethernet Network (Port 3 = vmnic2) The window below shows what Networks are allowed to flow through this Port 3 (vmnic2). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  36. Server Profile (ESX VEM) – Ethernet Network (Port 4 = vmnic3) The window below shows what Networks are allowed to flow through this Port 4 (vmnic3). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  37. Server Profile VEM Servers for c7000-2

  38. ESX VEM Server for HP c7000-2 • Nexus 1000V VEM VLANs • VSM- Control  VLAN 250 • VSM-Packet  VLAN 251 • Service Console/Mgmt  VLAN 182 • VMotion  VLAN 50 • Data VLANs  VLAN 51 – 52 • Nexus 1000V Traffic FLow • vmnic0/vmnic1 (PC) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2/vmnic3 (PC) used for vm-uplink • (Data traffic VLANs 51 & 52) Flex-10 Bay1 Flex-10 Bay2 vmnic0 vmnic1 vmnic2 vmnic3 4G 4G 6G 6G Nexus 1000V Service Console, VMotion, Control & Packet N1K Port Profiles (VM Port Groups) VM #1 VM #2 VM #3 ESX Blade Server

  39. Server Profile (ESX VEM) • Similar to creating a Server Profile for the ESX VSM server, the Server Profile for the “ESX VEM” server will be slightly different. In this Server Profile, 4 NICs will be used and the bandwidth of the NICs will be different. With the topology that is being deployed in the test environment, the following are the VLAN traffic flows: • vmnic0 (4G) & vmnic1 (4G) used for system-uplink (VLANs 50, 250-251, 182) • vmnic2 (6G) & vmnic3 (6G) used for vm-uplink (VM Data traffic VLANs 51 & 52)

  40. Server Profile (ESX VEM) – Ethernet Network (Port 1 = vmnic0) As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The window below shows what Networks are allowed to flow through this Port 1 (vmnic0). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  41. Server Profile (ESX VEM) – Ethernet Network (Port 2 = vmnic1) The window below shows what Networks are allowed to flow through this Port 2 (vmnic1). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.

  42. Server Profile (ESX VEM) – Ethernet Network (Port 3 = vmnic2) The window below shows what Networks are allowed to flow through this Port 3 (vmnic2). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”. Note: The Flex-NIC Port 3 is bound to Interconnect Bay1, which is using the Shared Uplink Set “Uplink Bay1”

  43. Server Profile (ESX VEM) – Ethernet Network (Port 4 = vmnic3) The window below shows what Networks are allowed to flow through this Port 4 (vmnic3). Just click on the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”. Note: Flex-NIC Port 4 is bound to Interconnect Bay2, which is using the Shared Uplink Set “Uplink Bay2”

  44. Server Profile (ESX VEM) – Ethernet Network (Port Speed Setting) With Flex-NICs, it is possible to traffic shape the amount of bandwidth each of the Flex-NICs are allowed to be allowed to have. To set the port speed of the ports, click on the drop-down at the “Port Speed Setting” and choose “Custom”. Another pop-up window will appear where the port bandwidth can be set. Repeat this for each of the Ports (NICs).

  45. Server Profile (ESX VEM) – FC SAN In the HP Blade Servers, the FC Mez cards are hard code to a specific Interconnect bay. The test environment has the FC Mez card placed in slot1, which will bind FC Port 1 to Bay3 and FC Port 2 to Bay4. With that in mind, click on the drop-down section for the FC SAN Name that was created and choose the appropriate SAN Fabric.

  46. Server Profile (ESX VEM) – Assign Profile Last portion for the Server profile is to assign the profile to the physical blade server in the chassis. In this example, Blade Server in slot 8 will be assign for the VEM. This server is a BL490c G6 (Intel Nehalem processor). This Server Profile can be copied and assigned to another blade server in the same chassis, which will be blade server in slot 16. Another Server Profile needs to be configured on another HP c7000 chassis to be identical to this Server Profile, so as to be able to VMotion a VM across the 2 HP chassis.

  47. Nexus 1000V Configuration

  48. Nexus 1000V Configurations • Creating Port-Profiles • Configuring system-uplink (create asymmetrical port-channel) • Configuring vm-uplink (create asymmetrical port-channel) • Configuring Service-Console, Vmotion, Exchange and Web port-profiles • Adding ESX VEMs into DVS • Migrating “Service Console” into Nexus 1000V • Creating “vmkernel” for VMotion through Nexus 1000V • VMotion of VMs • Vmotion VM from one ESX server to another ESX server within same HP c7000 chassis • Vmotion VM from one ESX server to another ESX server between separate HP c7000 chassis • Note: These steps will not include how to install the VSM. Please consult the “Nexus 1000V installation guide” for details

  49. Port-Profile: System-Uplink • Configuration of “System-Uplink” • capability is set to “uplink = yes” • system vlans: list of vlans that will be enabled in case of system errors • switchport mode is set to “trunk” • list of allowed vlans that will use this port-profile (in this case vmotion, control, packet and service console) • Since HP Flex-10 does not support CDP, setting the channel-group to auto will insure creation of port-channels using this port-profile • System-Uplink Configuration from VSM • hpvc-n1k# show port-profile name system-uplink • port-profile system-uplink • description: • status: enabled • capability uplink: yes • capability l3control: no • system vlans: 250-251,182 • port-group: system-uplink • max-ports: - • inherit: • config attributes: • switchport mode trunk • switchport trunk allowed vlan 50,250-251,182 • channel-group auto mode on sub-group cdp • no shutdown • evaluated config attributes: • switchport mode trunk • switchport trunk allowed vlan 50,250-251,182 • channel-group auto mode on sub-group cdp • no shutdown • assigned interfaces

  50. Port-Profile: VM-Uplink • Configuration of “VM-Uplink” • capability is set to “uplink = yes” • switchport mode is set to “trunk” • list of allowed vlans that will use this port-profile (in this case vlan 51 & 52) • Since HP Flex-10 does not support CDP, setting the channel-group to auto will insure creation of port-channels using this port-profile • VM-Uplink Configuration from VSM • hpvc-n1k# show port-profile name vm-uplink • port-profile vm-uplink • description: • status: enabled • capability uplink: yes • capability l3control: no • system vlans: none • port-group: vm-uplink • max-ports: - • inherit: • config attributes: • switchport mode trunk • switchport trunk allowed vlan 51-52 • channel-group auto mode on sub-group cdp • no shutdown • evaluated config attributes: • switchport mode trunk • switchport trunk allowed vlan 51-52 • channel-group auto mode on sub-group cdp • no shutdown • assigned interfaces:

More Related