On Friday 11 April 2008, Wink wrote:
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.
I've had a chance to play around with IOS XR - it's a good
thing Cisco have done
Cc: Campbell, Alex; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Wanting to learn Juniper...
Of course it seems intuitive to anyone who's worked with Cisco gear for
even a short amount of time. But in running newbies through the basics
in an introductory Cisco class, this is one thing I've
Minus the fallthrough access-list, that won't work... brain is tired.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Crawford
Sent: Friday, April 11, 2008 12:04 AM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Wanting to learn Juniper
Tolstykh, Andrew wrote:
Cisco IOS is in fact extremely intuitive, there is nothing intuitive
about the JunOS IMHO.
I can't speak on JunOS, but considering that the IOS command to enable
an interface is no shutdown, IOS may not be as intuitive as you think.
stretch
http://packetlife.net
Stretch
Sent: Thursday, April 10, 2008 11:14 PM
To: Tolstykh, Andrew
Cc: Campbell, Alex; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Wanting to learn Juniper...
Tolstykh, Andrew wrote:
Cisco IOS is in fact extremely intuitive, there is nothing intuitive
about the JunOS IMHO.
I can't speak on JunOS
Of course it seems intuitive to anyone who's worked with Cisco gear for
even a short amount of time. But in running newbies through the basics
in an introductory Cisco class, this is one thing I've noticed that
seems odd to them. Obviously this isn't a huge stumbling block, just
noting that
* 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
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:
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
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
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
Of course we also have no neighbor x.x.x.x peer-group MYPEERS, which
rather than disassociating the neighbor from the peer group, will
instead do the same as no neighbor x.x.x.x.
Ben Steele wrote:
That seems very intuitive to me, as soon as you understand that no
in IOS removes/negates
That said, there really is *no* equivalent to 'shutdown'. Even if
you disable an interface, it just disables that interface's ability
to pass traffic. I believe the layer-1 actually still works (lasers
transmit/receive, TDM still receives).
That depends. Modern PICs with replaceable optics
I'm fairly well versed in the Cisco devices and the configuration of those
devices through the CLI using Cisco IOS...but I'm curious, and up for the
learning experience, of starting to familiarize myself with Juniper.
I'm looking for some insight on the best approach to do this?
I prefer
Jeff,
You should look into olive, which is a software simulation of juniper
products. Here is a link
http://juniper.cluepon.net/index.php/Olive
There is also good information at Himawan's site
http://brokenpipes.blogspot.com/2008/01/olive-is-alive.html
Hope this helps,
Greg
On Thu, Apr 10,
On Friday 11 April 2008, Jeff Cartier wrote:
I'm fairly well versed in the Cisco devices and the
configuration of those devices through the CLI using
Cisco IOS...but I'm curious, and up for the learning
experience, of starting to familiarize myself with
Juniper.
I'm looking for some
... and iirc
ScreenOS if you really feel like some punishment.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Cartier
Sent: Thursday, April 10, 2008 6:21 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Wanting to learn Juniper...
I'm fairly well
On Apr 10, 2008, at 7:20 PM, Jeff Cartier wrote:
I'm fairly well versed in the Cisco devices and the configuration of
those devices through the CLI using Cisco IOS...but I'm curious, and
up for the learning experience, of starting to familiarize myself
with Juniper.
I'm looking for
Juniper are offering free training for Cisco certified persons
Check this out here: http://www.juniper.net/training/fasttrack/
Cheers
On Fri, Apr 11, 2008 at 11:20 AM, Jeff Cartier [EMAIL PROTECTED] wrote:
I'm fairly well versed in the Cisco devices and the configuration of those
devices
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Cartier
Sent: Friday, 11 April 2008 11:21 AM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Wanting to learn Juniper...
I'm fairly well versed in the Cisco devices and the configuration of
those devices through the CLI using
Subject: Re: [c-nsp] Wanting to learn Juniper...
I would pick up an old J-series to play with. The JunOS CLI and
configuration structure is extremely intuitive.
Once you've found your way around the CLI, I would work through Team
Cymru's JunOS templates:
http://www.cymru.com/gillsr/documents/junos
21 matches
Mail list logo
