[j-nsp] Understanding DPC Cards

[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 means 
you can have the same vlan id on different ports without them being the 
same service (this may be a bit unclear, I apologize if that is the case)

Encapsulation flexible-ethernet-services gives you the opportunity to 
use different encapsulation on different units (i.e vlan, mpls, vpls and 
so forth).

vlan-tagging enables support for reception of singel tagged ethernet 
frames. If you want double-tagged it's stacked-vlan-tagging or if you 
want the option of doing both on the same physical port it's 
flexible-vlan-tagging.

If you intend solely to terminate a vlan in a L3 interface you would 
simply state it like this.

ge-0/0/0 {
   encapsulation flexible-ethernet-services;
   vlan-tagging;
   unit 0 {
     vlan-id z;
     family inet {
       address xx.xx.xx.xx/yy;
     }
}

If you want the option of bridging several interfaces together and 
simultaneously have a routable interface enabled it get's a bit more 
complicated. Basicly you have to set up a bridge-domain and then an 
routing-interface (interface irb) on it.

//Martin

On 2010-05-04 23:05, Paul Stewart wrote:
> Hi there..
>
>
>
> I'm not sure if I'm asking this right . again, as I mentioned earlier - I'm
> a Cisco guy jumping into the JunOS world so pardon me if I've missed this
> somewhere in the docs. my translation between the two worlds is "slow but
> steady"..
>
>
>
> Working on an MX480 that has a pair of DPC cards (DPCE 20x 1GE + 2x 10GE R).
>
>
>
> Some questions ;)
>
>
>
> Can someone give me in "simple terms" what the differences are between
> "chassis network-services Ethernet" and "chassis network-services IP"?
>
>
>
> Secondly, on EX switches (which I'm just getting used too) we can do:
>
>
>
>      ge-0/0/12 {
>
>          description xxxxxxxxxxxxxxx;
>
>          unit 0 {
>
>              family ethernet-switching {
>
>                  port-mode trunk;
>
>                  vlan {
>
>                      members [ xxxxxxxx yyyyyyyy ]
>
>
>
> On the MX it seems this is quite different?  I have the following:
>
>
>
>      ge-5/0/2 {
>
>          description xxxxxxxxxxxxxxxxxxxx;
>
>          vlan-tagging;
>
>          encapsulation flexible-ethernet-services;
>
>          unit 0 {
>
>              family bridge {
>
>                  interface-mode trunk;
>
>                  vlan-id-list 61;
>
>              }
>
>          }
>
>
>
>
>
> I'm sure this isn't correct J  This is what I created after reading some of
> the Juniper docs with a lack of understanding what
> "flexible-ethernet-services" actually refers too..
>
>
>
> My goal is to have a dot1q trunk come in with a dozen or so VLAN's on it and
> then create layer3 RVI's for them.  The RVI configuration I have is this
> (which again I know is wrong):
>
>
>
>      vlan {
>
>          unit 61 {
>
>              family inet {
>
>                  address xxx.xx.235.34/24;
>
>              }
>
>              family inet6 {
>
>                  address xxx:xxx:235::34/64;
>
>              }
>
>          }
>
>
>
>
>
> Any assistance is much appreciated - thanks again to those folks who helped
> earlier with my BGP questions.
>
>
>
> Paul
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>