I have a few questions related to the method of L3 peering between N7k and a generic L3 device (let's say it is a router) - the idea is to connect N7k to the core network. The current design is based on Cat6k switches (they are the core of my network) which have many Vlans and SVI interfaces for them.
EIGRP is also used currently on Cat6k and other L3 devices in my network.
The goal is to extend Vlans from the current Cat6k to a pair of N7k configured for vPC. To do that I would have to configure L2 trunks (and NOT to use vPC links) between Cat6k and a pair of N7k and use them to pass all the current Vlans to N7k. How to establish EIGRP adjajency between Cat6k and N7k and at the same time pass all the vlans? Should I add any new Vlan on N7k/Cat6k, create SVI for it and use it to establish EIGRP peering?
Is the above the correct thinking? if not how to do that?
- One of the design docs say that we MUST use L3 routed interfaces to connect these two devices (N7k and a core network).
- Other ones mention that the _recommended_ way is to use L3 routed interfaces to connect these two devices ('recommended' means what? that any other options are available? what are they?)
- And other ones say that can use Vlan peering (through SVI interfaces) if only we make sure not to use vPC vlans (peering of routing protocols using a VLAN also carried on the vPC peer-link is not supported). Does it mean that if I configure any new/additional Vlan between the core and the vPC domain + I would exclude that vlan from vPC peer-link that I can configure EIGRP/OSPF peering between a generic vPC device and vPC domain???
what about STP root and HSRP? During the migration can they stay on the 6K till I move all my servers from 6k to N7k?
Will the communication be ok? or I can came across the situation that the traffic would be filtered by the peer-link of N7k?
this is not a vaild architecture. You are in need of dedicated routed links between Each 7K to 6K
info from cisco is as follows
"Note When you attach a Layer 3 device to a vPC domain, the peering of routing protocols using a VLAN also carried on the vPC peer-link is not supported. If routing protocol adjacencies are needed between vPC peer devices and a generic Layer 3 device, you must use physical routed interfaces for the interconnection. Use of the vPC peer-gateway feature does not change this requirement. "
No. That is not what I need to do. I want to EXTEND Vlans up to N7k. To do that I can't use L3 link.
My idea was to use L2 links WITHOUT vPC between C6k and N7k and use an additional Vlan to establish l3 peering (eigrp,ospf). I would also exclude that vlan from vPC peer-link. To rule out possible split-area failure I would add 1 more vlan to establish l3 peering between N7k-N7k.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...