I don't really need to run STP on them, these are switchports connecting into physical servers which host hundreds of VMs, so I need to trunk all my vlans into about 20 ports per switch
Not quite sure how Q-in-Q would help... How do I configure the ports facing the servers, who does the tagging? MVRP looks more like cisco's VTP, so probably not what i'm after right? ________________________________________ From: Alex Arseniev [[email protected]] Sent: Sunday, 3 March 2013 7:41 PM To: Luca Salvatore; [email protected] Subject: Re: [j-nsp] thoughs on MVRP? If you don't need to run STP on these VLANs, why not use QinQ/dot1q-tunneling? http://kb.juniper.net/InfoCenter/index?page=content&id=KB21686&actp=RSS Saves you Thanks Alex ----- Original Message ----- From: "Luca Salvatore" <[email protected]> To: <[email protected]> Sent: Sunday, March 03, 2013 12:13 AM Subject: [j-nsp] thoughs on MVRP? > Hi, > We have a requirment to trunk about 3500 VLANs into multiple ports on some > EX4200 switches in VC mode. > > This breaches the vmember limit but a huge amout, and once we did this I > have seen lots of errors in the logs such as: > > fpc0 RT-HAL,rt_entry_create,2414: failed to allocate memory for route > entry > /kernel: RT_PFE: RT msg op 3 (PREFIX CHANGE) failed, err 5 (Invalid) > fpc0 RT-HAL,rt_entry_add_msg_proc,2702: route entry create failed > fpc0 RT-HAL,rt_entry_add_msg_proc,2886: proto L2 bridge,len 48 prefix > 06:d4:f2:00:00:cb/48 nh 2850 > fpc0 RT-HAL,rt_entry_create,2414: failed to allocate memory for route > entry > > These messages worry me. I have been looking into MVRP which seems like > it will allow us to not need all 3500 VLANs trunked into the switches all > the time, but will dynmicaly register VLANs as needed. > > Wondering peoples thoughts on MVRP, is this a good use case? Is it stable > and reliable? > > thanks, > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
