The N5k maintains the config of the FEXs, even when they’re removed (and even though it’s not visible to us). In this article, we’re going to look into this a little further… We’ll start with a working FEX, using Po100 (with Eth1/19-20 being the physical bundle members). Read more »
Tags: 2000, associate, cisco, config, configuration, example, extender, fabric, fabric extender, fex, fex associate, keep, n2148t, n2k, n5k, nexus, nexus 2000, nexus 2148T, nexus 5000, nexus 5010, nexus 5020, nx-os, retain, retained, store, training, tutorial
Cisco Nexus, Networking | tim | 
2010-02-15 11:39 am | 
Comments (0)
If you’re wondering what an FEX is, check out this article: http://www.cciezone.com/?p=231.
FEXs are connected to the parent switch(es) via fabric interfaces. These are 10Gbps interfaces which connect the two switches (think of a stacking cable on a 3750-series switch).
There are two methods of configuring fabric interfaces:
- Static pinning
- EtherChannels
Although these are somewhat differentiated in some of the documentation, the static pinning looks almost the same as that used for EtherChannels. The main difference is that static pinning uses physical interfaces, whereas EtherChannel uses a single Port-Channel interface for the fabric interface (there are some minor configuration differences and requirements as shown below).
Read more »
Tags: 2000, 2148T, 5000, 5010, 5020, associate, channel-group, cisco, config, configuration, differences, etherchannel, fabric interface, fabric interfaces, fex associate, max-links, n2k, n5k, nexus, nexus 2000, nexus 2148T, nexus 5000, nexus 5010, nx-os, pinning, port-channel, static pinning, training, tutorial
Cisco Nexus, Networking | tim | 2010-01-29 9:27 am | Comments (0)
Subscribe