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)
I prefer to use port-channel interfaces for the fabric interfaces when connecting fabric extenders (FEXs). If a single interface in the bundle fails, it won’t remove the fabric extender interface – it simply reduces it’s bandwidth. This results in stable, predictable, redundant and resilient behavior. Let’s prove this point. Read more »
Tags: 2148T, associate, bundle, channel-group, cisco, config, configuration, etherchannel, example, fabric interface, fex, n2148t, n5010, n5020, nexus, nexus 2000, nexus 2148T, nexus 5000, nexus 5010, nexus 5020, nx-os, port-channel, training, tutorial
Cisco Nexus, Networking | tim |
2010-02-08 11:25 am |
Comments (0)