layer 3 p3p link best practice

[zinkann]

I am just trying to get some clarification about something. I am in the middle of redesigning a fairly large network. I am trying to get the IP structured where i can use summarization with EIGRP. I plan to use routed p2p links on most of my layer 3 switches and routers. My question is what is the best method of managing them? Should i use loopback interfaces and advertise them in EIGRP or use the p2p link IP? Also, lets say i have a layer 3 link and a 4506 doing inter vlan routing with a few 2960s hanging off of it. Since the default native vlan will not be in use, whats the best method of managing those 2960s?

CCNA, Network+

 

[vipergg]

Loopbacks are preferable as they always up even if a connecting link goes down . I would assign separate management vlans for a given area to manage the switches . if they are trunked switches the new mgt. vlan would have to be allowed on the switches and the SVI on the switches would have to changed to the new management vlan .

 

[zinkann]

i see. so if i have several distribution switches i should advertise their Loopbacks for remote mgt and create a new management vlan for STP, CDP, remote mgt and other l2 services for the access layer switches. Now since i won't be using vlan 1 as the native, could you give an example of a native config?

CCNA, Network+

 

[vipergg]

The management vlan would be to manage the switches. STP, cdp and other control plane protocols will always use vlan 1 to talk even if vlan 1 is not allowed on the trunks for data transmission . The native vlan can be any vlan number you want , best practice says just make it a vlan that will never be used for anything else .