Nexus PC across M and F blades

[wintermute000]

re: Nexus 7k,
Anyone know if there is any issues splitting a port channel across a M blade and a F blade?


i.e. 4 members in a port channel, 2 are on a M series blade, the other 2 are on a F series blade.


I have a customer with peer-link across F series who want to migrate to M series ports. Sounds like a straightforwards add-members, move patching, remove members - but are there any gotchas?

[wintermute000]

Answer is no lol

[Reggle]

Answer is no lol

No, as in no issues? Or not possible?

[wintermute000]

Not possible, be warned. It's in the vpc best practices guide as well as the config guide itself

[that1guy15]

Not possible, be warned. It's in the vpc best practices guide as well as the config guide itself

DONT CROSS THE STREAMS!!

This is another one of the reasons Im starting to really hate the 7Ks. Too many linecards and SUPs and too many restrictions/gotchas. Its almost like you are forced to hire a dedicated Nexus 7K consultant to get the damn thing deployed. Or you have to spend a large amount of time just squaring everything away. I really dont know how consultants do these under tight deadlines.

[NetworkGroover]

Yep.... something I hear frequently.  That and the power draw.

[wintermute000]

This is another one of the reasons Im starting to really hate the 7Ks. Too many linecards and SUPs and too many restrictions/gotchas. Its almost like you are forced to hire a dedicated Nexus 7K consultant to get the damn thing deployed. Or you have to spend a large amount of time just squaring everything away. I really dont know how consultants do these under tight deadlines.

I'm finding out on the job as usual LOL. As a consultant, par for the course.... Hey, still beats a firewall project. Its actually my first real nexus hardware gig in years, only really configured routing previously so xp not really different from working on an ios device, then it's back to 2012 last time I installed a 5k/2k setup and I wasn't the lead.
I get to work on all the bells and whistles this time (moving peer links, putting in dual supervisors, implementing proper split FHRP across OTV, routing redesign etc) so pretty happy