Hi AJ,

Infovista with HP OV NNM Advance Edition is more appropriate option. we are
in the process to implement this in our network these days!!

On Thu, Mar 6, 2008 at 10:00 PM, <[EMAIL PROTECTED]>
wrote:

> Send juniper-nsp mailing list submissions to
>        juniper-nsp@puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://puck.nether.net/mailman/listinfo/juniper-nsp
> or, via email, send a message with subject or body 'help' to
>        [EMAIL PROTECTED]
>
> You can reach the person managing the list at
>        [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of juniper-nsp digest..."
>
>
> Today's Topics:
>
>   1. Re: [JUNOS] Equivalent of a shutdown (Benny Sumitro)
>   2. Re: Service Set Help !! (Ovais Iqbal)
>   3. Re: j-series vs. short pings ? (Alexandre Snarskii)
>   4. MPLS monitoring/management tools (Mera Yar)
>   5. Re: MPLS monitoring/management tools (Jonathan Brashear)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 Mar 2008 14:56:17 +0700
> From: "Benny Sumitro" <[EMAIL PROTECTED]>
> Subject: Re: [j-nsp] [JUNOS] Equivalent of a shutdown
> To: Samuel <[EMAIL PROTECTED]>
> Cc: juniper-nsp <juniper-nsp@puck.nether.net>
> Message-ID:
>        <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I think Juniper has no equivalent command for "shut down" like in Cisco
> but
> I do know that if disable the port the router will not be able to send
> traffic to that interface and will ignore all command related to that
> interface although, the remote peer will still see the port up.
>
> On Wed, Mar 5, 2008 at 12:55 AM, Samuel <[EMAIL PROTECTED]> wrote:
>
> >
> > > The following commands should do the trick on M7i,
> > > regardless of the fact that interface is fixed.
> > > Be careful, though, your second port fe-1/3/1 will be shut-down as
> well.
> > > request chassis pic offline fpc-slot 1 pic-slot 3
> > Thanks Alexander. I had tried, but too quickly. It works fine even on
> > fixed interfaces.
> >
> >
> > Timo, if I use: "set interface fa-x/y/z disable", I get it:
> >
> > [EMAIL PROTECTED]> show interfaces terse
> > Interface               Admin  Link     Proto    Local
> > Remote
> > fe-1/3/0                down   up
> >
> > Hyun, if I use: "deactivate interface fa-0/0/0", I get it:
> >
> > [EMAIL PROTECTED]> show interfaces terse
> > Interface               Admin  Link     Proto    Local
> > Remote
> > fe-1/3/0                up     up
> >
> > And I would like to get:
> > fe-1/3/0                down   down
> >
> >
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Mar 2008 02:49:02 -0800 (PST)
> From: Ovais Iqbal <[EMAIL PROTECTED]>
> Subject: Re: [j-nsp] Service Set Help !!
> To: Jose Madrid <[EMAIL PROTECTED]>, juniper-nsp@puck.nether.net
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=iso-8859-1
>
> Dear Jose, i have already downloaded it and read it before i posted my
> query, it was good but still it didnt solved my confusions
>
> Jose Madrid <[EMAIL PROTECTED]> wrote:  Ovais,
>
> I am not sure if you saw Doug's suggestion of going to the Juniper
> FastTrack site. They have a guide called Advanced Juniper Networks
> Routing in the Enterprise. Chapter 6 (page 257) contains information
> on Service Sets and explanations of all related technologies. I am
> not sure if it is better than what you have already read, but it cant
> hurt. Take a look, its located at
> http://www.drakekryterion.com/clients/juniper/AJRE_SG_8.a.pdf
>
> --
> It has to start somewhere, it has to start sometime. What better
> place than here? What better time than now?
>
>
>
> ---------------------------------
> Never miss a thing.   Make Yahoo your homepage.
>
> ------------------------------
>
> Message: 3
> Date: Thu, 6 Mar 2008 18:09:28 +0300
> From: Alexandre Snarskii <[EMAIL PROTECTED]>
> Subject: Re: [j-nsp] j-series vs. short pings ?
> To: Juniper-NSP Mailing list <juniper-nsp@puck.nether.net>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Feb 29, 2008 at 05:51:20PM +0300, Alexandre Snarskii wrote:
> > Hi!
> >
> > During narrowing down one of our problems, I found, that I'm able
> > to ping juniper from directly connected (vlan) subinterface only
> > when ICMP payload size is more or equal 18 bytes...
> >
> [....]
> >
> > Question: is there any way to fix this behaviour ? (short ICMP pings
> > is the way the RAD IPMux verifies mac-address of his gateway, and
> > we're just unable to use IPMux'es as downlinks to Juniper)..
>
> Just for google: RAD IPMux not checking ICMP code in reply, so
> rejecting 'short' pings with host-prohibited helps them to verify
> next-hop availability.
>
> And that can be done with next firewall filter:
>
> [EMAIL PROTECTED]> show configuration firewall filter drop_shorts
> term main {
>    from {
>        packet-length 20-45;
>        protocol icmp;
>        icmp-type echo-request;
>    }
>    then {
>        reject host-prohibited;
>    }
> }
> term default {
>    then accept;
> }
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 6 Mar 2008 11:20:28 -0500
> From: "Mera Yar" <[EMAIL PROTECTED]>
> Subject: [j-nsp] MPLS monitoring/management tools
> To: juniper-nsp@puck.nether.net
> Message-ID:
>        <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello,
>
> I would like to know if anyone has any experience with any MPLS
> monitoring/management tools.  Looking for something that can do off-line
> traffic engineering, fault analysis for our Juniper based mpls network.
> Can
> you recommend any commercial products?  It seems Dorado's Redcell MPLS
> manager and WANDL would fit this. Anyone have any experience with either
> of
> these? Are there any open-source freeware products out there for something
> like this?
>
> Thanks in advance.
>
> AJ
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 6 Mar 2008 08:31:15 -0800
> From: "Jonathan Brashear" <[EMAIL PROTECTED]>
> Subject: Re: [j-nsp] MPLS monitoring/management tools
> To: "Mera Yar" <[EMAIL PROTECTED]>, <juniper-nsp@puck.nether.net>
> Message-ID:
>        <[EMAIL PROTECTED]
> >
> Content-Type: text/plain;       charset="us-ascii"
>
> I've heard many good things about Cariden's products, but haven't used
> it myself.
>
> http://www.cariden.com/products/
>
> Network Engineer
> > 214-981-1954 (office)
> > 214-642-4075 (cell)
> > [EMAIL PROTECTED]
> http://www.speakeasy.net
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mera Yar
> Sent: Thursday, March 06, 2008 10:20 AM
> To: juniper-nsp@puck.nether.net
> Subject: [j-nsp] MPLS monitoring/management tools
>
> Hello,
>
> I would like to know if anyone has any experience with any MPLS
> monitoring/management tools.  Looking for something that can do off-line
> traffic engineering, fault analysis for our Juniper based mpls network.
> Can
> you recommend any commercial products?  It seems Dorado's Redcell MPLS
> manager and WANDL would fit this. Anyone have any experience with either
> of
> these? Are there any open-source freeware products out there for
> something
> like this?
>
> Thanks in advance.
>
> AJ
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> ------------------------------
>
> _______________________________________________
> juniper-nsp mailing list
> juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> End of juniper-nsp Digest, Vol 64, Issue 7
> ******************************************
>



-- 
Regards,

Yasir Kayani
Service Engineer II MPBN
Ericsson Pakistan Pvt Ltd
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to