Um...you are forgetting the most important part of the vpc...the vpc

Here is a working set of stanzas from a 5548:

interface port-channel11

description vPC to node01

switchport mode trunk

switchport trunk allowed vlan 1,800-804,3000-3018

spanning-tree port type edge trunk

vpc 11

interface Ethernet1/1

description vPC to mddaas01-01, NetApp Node01, FAS8020

switchport mode trunk

switchport trunk allowed vlan 1,800-804,3000-3018

channel-group 11 mode active

Those two stanzas are the same on both 5548's that are vPC'd together.

You really should use LACP (the mode active above). which means, you should do the same on the netapp side.

You would also need the peer link setup.

Before you go any further, if in fact you are using VPC's, make sure that is working.

A simple "show vpc" should be enough to tell you if it is working or not.

On Tue, Nov 25, 2014 at 11:17 AM, Bob McKim <bob.mckim@us.ibm.com> wrote:

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.

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters