When you set native vlan26 you are saying, do not tag vlan 26 even though it's a tagged trunk. Generally, it is best practice to set vlan 1 or an unused vlan or your management vlan for the native vlan, typically, you would NOT set a real data vlan as a native vlan. It just doesn't make any sense.
Gerald (Gerry) Justice
Team Lead, Research Computing Support, Operations Branch Shared Services Canada / Government of Canada gerald.justice@ssc-spc.gc.ca / Tel: 250-363-0055
Chef d'équipe, Soutien de la recherche informatique, Direction générale des opérations Services partagés Canada / Gouvernement du Canada gerald.justice@ssc-spc.gc.ca / Tél: 250-363-0055 ________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Bob McKim [bob.mckim@us.ibm.com] Sent: Tuesday, November 25, 2014 8:17 AM To: Toasters Subject: Need Working Nexus 7000 Config for cDOT - 2 scenarios
Hi toasters, I'm looking for a working Nexus 7000 config for the following 2 scenarios -
Single mode 10g ifgrp (2 interfaces) with 2 vlans 2 switch vPC for a two interface 10g ifgrp with 2 vlans
If we bring the single mode ifgrp (e0b and e0d) up with no vlan tagging, it works fine for each sub-net. As soon as we add vlan tagging on cluster nodes, we can't ping the gateways. Require the vlan tagging to support our failover groups.
This is what we tried on the Cisco for the single mode with 2 vlans - no dice.
config t interface Ethernet1/14 description <<xxx>> switchport mode trunk switchport trunk native vlan 26 switchport trunk allowed vlan 26, 28 no shutdown
Thanks in advance,
Bob McKim Senior IT Specialist IBM Global Technology Services NetApp Certified Professional
Although no hardware was injured in the creation of this note, a few billion electrons and photons were utilized against their will.