[j-nsp] Understanding DPC Cards

[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 cheaper and have limited
L3 functionality.  Chances are you want to keep this in IP mode since
you are using an R card (I assume they are both R cards, and not X
cards).

Also, comparing EX vs MX configs should be viewed like comparing cisco
ios to ios-xr.  AFAIK, these are separate codebases.  You need to
compare to J, T, or M series configs.

-J Scott


On Tue, May 4, 2010 at 2:05 PM, Paul Stewart <paul at paulstewart.org> 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
>