[j-nsp] Moving onto EX2300

[Chris Morrow]

On Wed, 20 Sep 2017 22:29:44 -0400,
Jason Healy <jhealy at logn.net> wrote:
> 
> 
> > On Sep 20, 2017, at 10:10 PM, Chris Morrow <morrowc at ops-netman.net> wrote:
> > 
> > man.. I'd like to take a gander at your setup.. because I'm fairly
> > certain I'm going to send this 3400 back and work out my anger on some
> > firewood. :)
> 
> Mail it my way; I'd be happy to have a spare!  I probably have a few
> 3200s left for trade.  ;-)
>

ha :)

> I misread your earlier email; yes, you would need an irb as the L3
> interface for management where you previously used a vlan... a find
> and replace should take care of that, though.
>

ah! ok, so... that's a bit of a bummer, I didn't see this sort of
thing documented in the release-notes, though I admit to quick-skim :(
I suppose I'm really opposed to a mounds turning into an almond joy on
me without pretty clear notice.

> I haven't bumped into the "default VC" port issue yet, but I guess I
> was lucky and chose xe-0/2/3 as my uplink.
>

our standard config was 0 & 1 .. so we just went with that :(
good thing there's a 2 & 3 though :)

> We had some growing pains when we got a QFX5100 for our all-EX
> network and had to adjust to the ELS stuff.  "port" became
> "interface", "vlan" became "irb", etc.  Plus they moved a bunch of
> stuff around.
>

I think we don't actually do the ELS functions, and at other places
i've run into the QFX I hadn't notice this problem either, but... I
also don't deploy switch stacks (voodoo!) and we happen to treat the
qfx more like a tiny router ... that has a slew of lan ports :(

> Juniper does have a conversion tool where you dump in your non-ELS
> config and it will output the ELS version (requires JTAC login).  It
> wasn't perfect, but if you work through it by hand you can figure most
> of it out:
> 
>   https://www.juniper.net/customers/support/configtools/elstranslator/index.jsp
>

ok, cool.. this would be handy for 'not this time' switch installs :)
I think I'll also just update my 'make me a switch!' script to just do
the right thing here... we were over eager and tried to mangle the config
by hand.. oops.

> Since we did the QFX a couple years ago, once the 3400s, I was
> familiar enough that it wasn't a huge deal.
> 
> The commit script I wrote lets you put stuff like this in the config:
> 
>       interfaces {
>         ge-0/0/0 {
>           apply-macro sa-portrole {
>             role static;   # or trunk/dot1x
>             vlan some-vlan;
>           }
>         }
>       }
>

oh,that's pretty neat.. i think we just whack on the port types with
an apply-group choice (and then add the vlan, of course). I tried to keep the ports 'simple':
  TRUNK-PORT -> carry all vlans, used to link to the core.
  EDGE-PORT -> connect hosts, don't trunk...

we aren't 100% that simple, but.. mostly :)

> I just finished that last month, so I'm still rolling it out.  Happy
> to share if you think it will help.  Unfortunately, it won't paper
> over the other ELS differences for you; just the stuff dealing with
> VLANs, trunk/access, STP, and dot1x.
>

ah. .I'll see how the now-working-ports 3400 fares, hopefully less
headaches than so far ;)

thanks! (for also making me re-think and find the other ports
solution) -chris