[c-nsp] Wanting to learn Juniper...

[Wink]

I think the "more intuitive" part is in reference to the structured 
nature of the configuration.  I can easily justify the comment based on 
my own preferences.

It seems easier to find things w/reference to the routing-instance you 
are dealing with or the interface you are dealing with at the moment, 
within the configuration.  The CLI has a nicer feel to it just in how 
you navigate and look at things.  I prefer formatted/hierarchical data 
any day over a flat list when looking at things. JUNOS has a more 
"legos" feel to it.  You build your elements and then you arrange them 
how you like.  At least thats the thought.  But first you have to learn 
all the elements... and how they string together isn't all that 
intuitive sometimes.

Indeed, things like NAT (which I just posted about on the j-nsp list) 
and some IPSec configurations seem.... convoluted on JUNOS compared to 
an IOS box.   Another thing...  Filter-based forwarding isn't nearly as 
intuitive as PBR...   rib-groups anyone?

Still, I almost fell out my chair at the "Cisco is flawless" comment.  
Look, those people with all those headaches with the 6500 on the 6500 vs 
7600 thread...  they're not lying.  The split got off to a shaky start 
and it aggravated a lot of people.   A lot of those boxes got ripped out 
of networks because every new IOS was deferred or redacted.  I 
personally spent a lot of time at my previous job banging my head 
against the wall troubleshooting them.  I guess its a lot better now 
that time has passed and some wrinkles got ironed out, but man... 

if model == switch(6500,sup720) then software != stable;

At least for a while it was that way.  Not to mention the endless 
caveats and restrictions.

I agree with previous comments though... you should know the 
differences... apply the strengths where needed. 

We're all "engineers" right?  We should know the technologies... not let 
the small stuff get in the way.  If the best router in the world could 
only be programmed with environment variables in UNIX, or had to be 
handcoded with its own variant of TL/1....  I would still do it if it 
meant better uptime and performance... and a paycheck...  :-)

Derick Winkworth
CCIE #15672



jason.plank at comcast.net wrote:
> The reality though is that both JunOS and Cisco IOS have their quirks. Having used both I find it hard to believe anyone can actually justify that JunOS is "more intuitive" than Cisco IOS. JunOS does have some cooler features, that I will definitely admit.
>
> --
> Regards,
>
> Jason Plank
> CCIE #16560
> e: jason.plank at comcast.net
>
>  -------------- Original message ----------------------
> From: Florian Weimer <fweimer at bfk.de>
>   
>> * Jonathan Crawford:
>>
>>     
>>> I do have to agree with Ben on this one... shutdown/negation of
>>> shutdown is one of the last things I would say is
>>> counter-intuitive... with JunOS the equivalent would be "deactivate
>>> interfaces ge-0/0/0" to shutdown ge-0/0/0. They are active by
>>> default when you create the entries for them and commit, but to
>>> activate a deactivated... it is just "activate interface ..."
>>>       
>> Uhm, no.  A deactivated configuration item is considered not to be
>> present in the configuration at all, which means you cannot reference
>> that interface anywhere else in the configuration (that would be an
>> error that prevents you from committing the change).  If you want to
>> shut down an interface (while keeping it in the configuration), you
>> need to disable it, and the equivalent of "no shutdown" in that sense
>> is "delete disable".
>>
>> Talk about intuitive...
>>
>> -- 
>> Florian Weimer                <fweimer at bfk.de>
>> BFK edv-consulting GmbH       http://www.bfk.de/
>> Kriegsstraße 100              tel: +49-721-96201-1
>> D-76133 Karlsruhe             fax: +49-721-96201-99
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>     
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG. 
> Version: 7.5.519 / Virus Database: 269.22.12/1372 - Release Date: 4/10/2008 5:36 PM
>