Re: [j-nsp] L2VPN Termination

Hi, On the core instance: set routing-instances xyz_IP_Transit protocols vpls connectivity-type irb Krasi On Mon, Jul 29, 2013 at 11:35 PM, Paul Stewart wrote: > Thanks folksŠ > > I have an issue with implementing this and was hoping for a "sanity > check". ;) > > On the "core" side of this i

Re: [j-nsp] vlan-tagging issue

Yes, the ARP table has the MAC of each -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Paul Stewart Sent: Tuesday, 30 July 2013 9:28 AM To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] vlan-tagging issue Do you get a MAC address at all

Re: [j-nsp] vlan-tagging issue

Do you get a MAC address at all from the other box? On 2013-07-29 6:17 PM, "Luca Salvatore" wrote: >I have an MX5 and SRX240 directly connected to each other. I need to >setup multuple VLANs between them. My config looks like this: > >MX - Ge-1/0/2 > > >show configuration interfaces ge-1/0/2 >

[j-nsp] vlan-tagging issue

I have an MX5 and SRX240 directly connected to each other. I need to setup multuple VLANs between them. My config looks like this: MX - Ge-1/0/2 show configuration interfaces ge-1/0/2 vlan-tagging; unit 10 { vlan-id 10; family inet { address 198.xxx.xxx.21/30; SRX - Ge-0/0/

Re: [j-nsp] L2VPN Termination

Thanks folksŠ I have an issue with implementing this and was hoping for a "sanity check". ;) On the "core" side of this implementation I am not taking the VPLS instance to any form of a physical interface - I only have an IRB interface and the VPLS path will not come up. I'm assuming the VPLS pa

[j-nsp] Understanding of a CoS statement

Hi group, I've just been refreshing myself on some CoS bits and pieces and came across this statement: "Note: When a source MAC address is learned, the frame that contains the source MAC address is always sent out on queue 0 while egressing from the network interface, irrespective of the cl

Re: [j-nsp] Protect router from ssh/telnet DDOS attacks, or unauthorised access.

Hi Darren, It is a burden to maintain the interface list updated per router, as we have a lot of routers in our network (100's), and the mgmt & transit interface names are not the sames. This is different from the MGMT IP ranges because this ranges do not usually change and we can keep it stand