Re: [j-nsp] Understanding DPC Cards

2010-05-05 Thread Paul Stewart
-Original Message- From: Richard A Steenbergen [mailto:r...@e-gerbil.net] Sent: Tuesday, May 04, 2010 7:21 PM To: Paul Stewart Cc: 'jnsp' Subject: Re: [j-nsp] Understanding DPC Cards On Tue, May 04, 2010 at 05:05:04PM -0400, Paul Stewart wrote: Can someone give me in simple terms what

Re: [j-nsp] Understanding DPC Cards

2010-05-04 Thread Judah Scott
I don't have time to get all of it but very quickly the command you mentioned: set chassis network-services ip; refers to if you want this MX to be a L2 or L3 box. Changing this requires a reset AFAIK. When in network-services ethernet mode you can only use the DPC-X cards which are priced

Re: [j-nsp] Understanding DPC Cards

2010-05-04 Thread Martin Levin
I'll try to help... We also run MX and EX. So, first off. MX and EX are not even remotely related in respect to what they can and can not do. The MX is a L3 box with L2 capabilities, the EX is a L2 box with L3 capabilities. So, vlans in an MX are not global (at least not necessarily). This

Re: [j-nsp] Understanding DPC Cards

2010-05-04 Thread Richard A Steenbergen
On Tue, May 04, 2010 at 05:05:04PM -0400, Paul Stewart wrote: Can someone give me in simple terms what the differences are between chassis network-services Ethernet and chassis network-services IP? When Juniper came out with the MX they had two large potential customer bases with two

Re: [j-nsp] Understanding DPC Cards

2010-05-04 Thread Nilesh Khambal
On MX, you can create access-ports connected to the hosts using interface-mode access with a unique vlan id assigned to the port. This is conceptually similar to switchport mode access on Cisco. With either interface-mode access you do not need to explicitly assign the logical unit to the