04-30-2013 04:18 AM - edited 03-01-2019 07:19 AM
I have a single 7009 with dual Sup-2 running 6.1(3) for a core replacement, modules include one N7K-M148GT-11L and two N7K-F248XP-25 modules. I am looking at creating multiple VDCs, and will eventually link my DR site via OTV using the M1 card.
My question(s) is/are, how would one tie the M1 card back into the VDC design if M1 and F2 cards are not compatible in the same VDC? It seem somewhat useless for not being able to have access to my copper ports within a VDC. Even if I setup a VDC for just the M1 card, do I need an external device to connect to the other VDCs F2 ports or can I use a VRF to achieve the internal connection?
Any suggestions would be helpful and thanks!
Dave
Solved! Go to Solution.
05-11-2013 09:23 AM
As Andras mentioned you need to separate the M1 and F2 in two different VDCs
if you want to deploy OVT you will need to have a third VDC for the OVT using the recommended OVT appliance design
see the third example in the below document i posted in CSC before
https://supportforums.cisco.com/docs/DOC-27427
keep in mind that you need to have a good traffic engineering L2/L3 with proper link capacity planing in a topology like this and try to keep it simple as three VDCs topology is complex enough !
HTH
05-11-2013 04:59 PM
My question(s) is/are, how would one tie the M1 card back into the VDC design if M1 and F2 cards are not compatible in the same VDC?
Late in 2012, Cisco released the improved version of the F2 card, F2e. F2 card, you see, has a technical design fault of not being able to co-habitate with M1/M2/F1 card in the same vDC.
F2e, in the next NX-OS, will bridge that.
If you are interested, talk to your AM and talk to them about getting your F2 swapped/replaced with an F2e card.
05-11-2013 10:23 PM
Inter-VDC communication can only be done via external cabling ( Intra chassis ) between the differnt VDC ports in this case M1 to F2
if you add OTV it will be between M1 & F2, and between M1-OTV VDC and (M1,F2 VDCs ) based on your design
04-30-2013 05:17 AM
You have to separate them into two VDCs, but you can connect the two VDC directly. It may look weird for the first time , but it works.
05-11-2013 09:23 AM
As Andras mentioned you need to separate the M1 and F2 in two different VDCs
if you want to deploy OVT you will need to have a third VDC for the OVT using the recommended OVT appliance design
see the third example in the below document i posted in CSC before
https://supportforums.cisco.com/docs/DOC-27427
keep in mind that you need to have a good traffic engineering L2/L3 with proper link capacity planing in a topology like this and try to keep it simple as three VDCs topology is complex enough !
HTH
05-11-2013 04:59 PM
My question(s) is/are, how would one tie the M1 card back into the VDC design if M1 and F2 cards are not compatible in the same VDC?
Late in 2012, Cisco released the improved version of the F2 card, F2e. F2 card, you see, has a technical design fault of not being able to co-habitate with M1/M2/F1 card in the same vDC.
F2e, in the next NX-OS, will bridge that.
If you are interested, talk to your AM and talk to them about getting your F2 swapped/replaced with an F2e card.
05-11-2013 10:23 PM
Inter-VDC communication can only be done via external cabling ( Intra chassis ) between the differnt VDC ports in this case M1 to F2
if you add OTV it will be between M1 & F2, and between M1-OTV VDC and (M1,F2 VDCs ) based on your design
05-13-2013 04:15 AM
Good information. Thanks for all the responses.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide