cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6600
Views
0
Helpful
4
Replies

vlans allowed to FEX member port

Goutam Biswas
Level 1
Level 1

Hi,

I am getting confused with FEX Associated to 7k.  I am going to connect 2k Fex to 7k and using 4 10g link to 2k configuring ether-channel.  Then Fex associating under ether-channel configuration, I hope it is understandable, I am not expert in Nexus so trying to explain as much as possible,

in summary  7k --> 4*10G--->2k

Sample configuration as below:

N7k-1(config)# feature fex

N7k-1(config)# fex 101

N7k-1(config-if)# interface eth1/1-4

N7k-1(config-if)# channel-group 101 mode on

N7k-1(config-if)# interface po101

N7k-1(config-if)# switchport mode fex-fabric

N7k-1(config-if)# fex associate 101

 

Please correct me if I am configuring in wrong way.  Now I dont understand, where is the trunk command used and how I can assign multiple vlans in 2k port configuration.  I mean, some ports of 2k are part of vlan 10 and some port of 2k are part of vlan 11 and so on.

Is it possible?  How may VLANs i can allowed to FEX associated ether-channel.

 

 

 

 

1 Accepted Solution

Accepted Solutions

eduardopozo56
Level 1
Level 1

Hi Goutam,

A fex, as it name says (Fabric Extender) is basically an extension for your Nexus switch. It is not a second switch with uplink port-channels to your nexus 7000 and vlans sent to it.

When you configure the FEX port channel on mode fex-fabric and plug in the FEX, it will boot up and you will see all the interfaces on the FEX as part of the Nexus7000, as it were an extra linecard on it. the fex-fabric command enables this feature, this is not a common trunk port.


For example, for fex 101, you should see the interfaces 101/1/1, 101/1/2, and so on.
Then you configure this ports as if they were normal ports on your Nexus 7000 linecards.

 

For example:

switch# show interface port-channel 4 fex-intf
Fabric           FEX
Interface        Interfaces
---------------------------------------------------
Po4              Eth101/1/48   Eth101/1/47   Eth101/1/46   Eth101/1/45
                 Eth101/1/44   Eth101/1/43   Eth101/1/42   Eth101/1/41
                 Eth101/1/40   Eth101/1/39   Eth101/1/38   Eth101/1/37
                 Eth101/1/36   Eth101/1/35   Eth101/1/34   Eth101/1/33
                 Eth101/1/32   Eth101/1/31   Eth101/1/30   Eth101/1/29
                 Eth101/1/28   Eth101/1/27   Eth101/1/26   Eth101/1/25
                 Eth101/1/24   Eth101/1/23   Eth101/1/22   Eth101/1/21
                 Eth101/1/20   Eth101/1/19   Eth101/1/18   Eth101/1/17
                 Eth101/1/16   Eth101/1/15   Eth101/1/14   Eth101/1/13
                 Eth101/1/12   Eth101/1/11   Eth101/1/10   Eth101/1/9
                 Eth101/1/8    Eth101/1/7    Eth101/1/6    Eth101/1/5
                 Eth101/1/4    Eth101/1/3    Eth101/1/2    Eth101/1/1

 

You can find more information about FEXs and their configuration on:

http://www.cisco.com/c/en/us/solutions/data-center-virtualization/fabric-extender-technology-fex-technology/index.html

http://www.cisco.com/c/en/us/products/switches/nexus-2000-series-fabric-extenders/index.html

Configuration:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_521/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_5_2/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_5_2_chapter_010.html

View solution in original post

4 Replies 4

eduardopozo56
Level 1
Level 1

Hi Goutam,

A fex, as it name says (Fabric Extender) is basically an extension for your Nexus switch. It is not a second switch with uplink port-channels to your nexus 7000 and vlans sent to it.

When you configure the FEX port channel on mode fex-fabric and plug in the FEX, it will boot up and you will see all the interfaces on the FEX as part of the Nexus7000, as it were an extra linecard on it. the fex-fabric command enables this feature, this is not a common trunk port.


For example, for fex 101, you should see the interfaces 101/1/1, 101/1/2, and so on.
Then you configure this ports as if they were normal ports on your Nexus 7000 linecards.

 

For example:

switch# show interface port-channel 4 fex-intf
Fabric           FEX
Interface        Interfaces
---------------------------------------------------
Po4              Eth101/1/48   Eth101/1/47   Eth101/1/46   Eth101/1/45
                 Eth101/1/44   Eth101/1/43   Eth101/1/42   Eth101/1/41
                 Eth101/1/40   Eth101/1/39   Eth101/1/38   Eth101/1/37
                 Eth101/1/36   Eth101/1/35   Eth101/1/34   Eth101/1/33
                 Eth101/1/32   Eth101/1/31   Eth101/1/30   Eth101/1/29
                 Eth101/1/28   Eth101/1/27   Eth101/1/26   Eth101/1/25
                 Eth101/1/24   Eth101/1/23   Eth101/1/22   Eth101/1/21
                 Eth101/1/20   Eth101/1/19   Eth101/1/18   Eth101/1/17
                 Eth101/1/16   Eth101/1/15   Eth101/1/14   Eth101/1/13
                 Eth101/1/12   Eth101/1/11   Eth101/1/10   Eth101/1/9
                 Eth101/1/8    Eth101/1/7    Eth101/1/6    Eth101/1/5
                 Eth101/1/4    Eth101/1/3    Eth101/1/2    Eth101/1/1

 

You can find more information about FEXs and their configuration on:

http://www.cisco.com/c/en/us/solutions/data-center-virtualization/fabric-extender-technology-fex-technology/index.html

http://www.cisco.com/c/en/us/products/switches/nexus-2000-series-fabric-extenders/index.html

Configuration:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_521/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_5_2/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_5_2_chapter_010.html

Hi,

Thanks for clearing my doubts.

 

One another issue I am getting, I have posted in this category.  Could you please check and help me out here.

which is I have configured two nexus 7009 in vpc domain. But i have some other vlan which should not be part of vpc peer link or port-channel. So, i have configured separate port-channel between two nexus for non-vpc vlans.

Everything is up and looks fine.  but when I allowed a vlan in normal port-channle it goes down in secondary switch and hsrp is not forming.  can you tell me something on non vpc vlan and port-channel.

No problem, Regarding the second issue,

could you please share the port-channel VPC configuration, the non-port channel VPC and the VLAN?
I don't know if i am understanding the issue correctly:
- You create the vlan and interface vlan on both nexuses

- allow it only on a non-vpc port channel

-All seems good, but when you allow it on a NON vpc port channel it goes down in one switch?, you should get a log explaining why the vlan is going down

If is a non-vpc vlan, you can not allow it on any vpc port-channel

 

 Merry Christmas!

Hi here is my configuration on both nexus;

Nexus 1 (Primary):

vlan 1000
 

interface Vlan1000
  no shutdown
  no ip redirects
  ip address 10.16.0.2/24
  hsrp version 2
  hsrp 1000
    preempt
    priority 120
    ip 10.16.0.1

interface port-channel11
  description *** For Non-vPC Trunk to N7K-02 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000

interface Ethernet3/47
  description *** For Non-vPC Trunk to N7K-02 port eth3/47 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000
  channel-group 11 mode active
  no shutdown

interface Ethernet4/47
  description *** For Non-vPC Trunk to N7K-02 port eth4/47 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000
  channel-group 11 mode active
  no shutdown

interface port-channel10
  description *** For vPC Peer Link to N7K-02 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  spanning-tree port type network
  vpc peer-link

interface Ethernet3/48

  description *** For vPC Peer Link to N7K-02 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  channel-group 10 mode active
  no shutdown

interface Ethernet4/48
description *** For vPC Peer Link to N7K-02 ***

switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  channel-group 10 mode active
  no shutdown

 

Nexus 2 (Secondary):

vlan 1000


interface Vlan1000
  
  no shutdown
  no ip redirects
  ip address 10.16.0.3/24
  hsrp version 2
  hsrp 1000
    preempt
    priority 110
    ip 10.16.0.1

interface port-channel11
  description *** For Non-vPC Trunk to N7K-01 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000
  spanning-tree port type network

interface Ethernet3/47
  description *** For Non-vPC Trunk to N7K-01 port eth3/47 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000
  channel-group 11 mode active
  no shutdown

interface Ethernet4/47
  description *** For Non-vPC Trunk to N7K-01 port eth4/47 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1000
  channel-group 11 mode active
  no shutdown

interface port-channel10

  description *** For Peer Link to N7K-01 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  spanning-tree port type network
  vpc peer-link

interface Ethernet3/48
  description *** For vPC Peer Link to N7K-01 port eth3/48 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  channel-group 10 mode active
  no shutdown

interface Ethernet4/48
  description *** For vPC Peer Link to N7K-01 port eth4/48 ***
  switchport
  switchport mode trunk
  switchport trunk allowed vlan 1007
  channel-group 10 mode active
  no shutdown

 

Note: Everything up and running, but only issue is vlan 1000 is down in secondary switch and hsrp is not forming.  But it was working when vlan 1000 was allowed in vPC peer link problem appeared while I remove vlan 1000 from peer link and allowed into non-vPC port-channel and link.

 

Thanks,

Happy Cistmas and new year to you.