Re: [j-nsp] ldp signaling vpls can't up

2012-04-12 Thread Ben Dale
Hi Bruno

 
  i don't know what did i miss?

VPLS routing instances on J Series or SRX Series devices use BGP to send 
signals to other PE routers. LDP signaling is not supported.

http://www.juniper.net/techpubs/en_US/junos11.4/information-products/topic-collections/security/software-all/mpls/index.html?topic-47047.html#jd0e7877

Cheers,

Ben
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] ldp signaling vpls can't up

2012-04-12 Thread bruno
hello ben, 


check this link http://sioduy.blogsome.com/2010/10/27/l2vpn-vpls/ . he run ldp 
vpls success on srx . so i think it's support on srx .




--
Best Regards,
Bruno




 


 
 
-- Original --
From:  Ben Dalebd...@comlinx.com.au;
Date:  Thu, Apr 12, 2012 03:28 PM
To:  brunobruno.juni...@gmail.com; 
Cc:  juniper-nspjuniper-nsp@puck.nether.net; 
Subject:  Re: [j-nsp] ldp signaling vpls can't up

 
Hi Bruno

 
  i don't know what did i miss?

VPLS routing instances on J Series or SRX Series devices use BGP to send 
signals to other PE routers. LDP signaling is not supported.

http://www.juniper.net/techpubs/en_US/junos11.4/information-products/topic-collections/security/software-all/mpls/index.html?topic-47047.html#jd0e7877

Cheers,

Ben
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Emmanuel Halbwachs
Hello, 

I would like to monitor with Nagios and graph the power received by
the optical transceivers (MX240 + DPCE-R, MX80).

My understanding of the situation is: 

- digital optic monitoring is available on both 1 GE SFP and 10 GE XFP
  transceivers

- the CLI command
  show interfaces diagnostics optics ge-1/0/0 | match Receiver
  works for both 1 and 10 GE

- starting with 10.4, the DOM MIB [1] is *only* for 10 GE XFP

So there is no way to poll by SNMP the power for 1 G SFP. Strange. 

And one have to handcraft a little shell script to ssh the CLI command
above to get the value.

Am I wrong? I hope yes.

Refs:

[1] 
http://www.juniper.net/techpubs/en_US/junos10.4/topics/reference/mibs/mib-jnx-dom.txt

Cheers,


-- 
Emmanuel Halbwachs  Observatoire de Paris
Resp. Réseau/Sécurité   5 Place Jules Janssen
tel  : +33 1 45 07 75 54 F 92195 MEUDON CEDEX
   véhicules : 11 av. Marcellin Berthelot
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread sthaug
 I would like to monitor with Nagios and graph the power received by
 the optical transceivers (MX240 + DPCE-R, MX80).
 
 My understanding of the situation is: 
 
 - digital optic monitoring is available on both 1 GE SFP and 10 GE XFP
   transceivers
 
 - the CLI command
   show interfaces diagnostics optics ge-1/0/0 | match Receiver
   works for both 1 and 10 GE
 
 - starting with 10.4, the DOM MIB [1] is *only* for 10 GE XFP
 
 So there is no way to poll by SNMP the power for 1 G SFP. Strange. 

Yes, this is a significant omission, and you're certainly not the only
one to notice it. If enough people ask about it, maybe Juniper will do
something...

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Saku Ytti
On (2012-04-12 10:20 +0200), sth...@nethelp.no wrote:

  So there is no way to poll by SNMP the power for 1 G SFP. Strange. 
 
 Yes, this is a significant omission, and you're certainly not the only
 one to notice it. If enough people ask about it, maybe Juniper will do
 something...

And when we do get them, next problem is, we don't know programmatically
what values to expect. As JNPR lacks 'entity mib' you can't ask it via SNMP
what type of optic it is, to determine what TX/RX/power etc are expected
for this optic.

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Emmanuel Halbwachs
Saku Ytti a écrit (Thu, Apr 12, 2012 at 11:41:06AM +0300) :
  If enough people ask about it, maybe Juniper will do something...
 
 And when we do get them, next problem is, we don't know programmatically
 what values to expect.

OK, so let's shout high and loud:

Juniper fellows subscribed to this list, please bring us useful,
complete and sane SNMP MIBs. We badly need it! Thank you very
much.

:-)

-- 
Emmanuel Halbwachs  Observatoire de Paris
Resp. Réseau/Sécurité   5 Place Jules Janssen
tel  : +33 1 45 07 75 54 F 92195 MEUDON CEDEX
   véhicules : 11 av. Marcellin Berthelot
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Per Granath
It should be possible to get the values via an op-script ... 
Not sure if that can also populate MIB values.


   So there is no way to poll by SNMP the power for 1 G SFP. Strange.
 
  Yes, this is a significant omission, and you're certainly not the only
  one to notice it. If enough people ask about it, maybe Juniper will do
  something...
 
 And when we do get them, next problem is, we don't know
 programmatically what values to expect. As JNPR lacks 'entity mib' you can't
 ask it via SNMP what type of optic it is, to determine what TX/RX/power etc
 are expected for this optic.

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Saku Ytti
On (2012-04-12 11:12 +0200), Emmanuel Halbwachs wrote:

 Juniper fellows subscribed to this list, please bring us useful,
 complete and sane SNMP MIBs. We badly need it! Thank you very
 much.

And maybe basic trap support, like ISIS up/down, BGP max-prefix, BGP trap
which reports previous state (so you don't need to keep track of states).

(Don't give me event script and tell me it's CAEK).
-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Jonathan Lassoff
On Thu, Apr 12, 2012 at 2:28 AM, Saku Ytti s...@ytti.fi wrote:
 On (2012-04-12 11:12 +0200), Emmanuel Halbwachs wrote:

     Juniper fellows subscribed to this list, please bring us useful,
     complete and sane SNMP MIBs. We badly need it! Thank you very
     much.

 And maybe basic trap support, like ISIS up/down, BGP max-prefix, BGP trap
 which reports previous state (so you don't need to keep track of states).

Nor poll too often.

Since 10.x, I get the sense that Juniper has been chasing so many
other bugs that good SNMP support has slipped somewhat.
It's probably a lot of extra work, especially for things that mutate state.
I can imagine it involving managing MIB contents and naming, finding
every place in which a hook or function needs to be defined to support
representing things into SNMP-compatible types.

What if I do a write to shut an interface? Should a whole commit happen?


It's too bad that netconf and op scripts are so hard to use (and
utilize relatively-obscure XML-based languages). They hold the full
power to read and manipulate states of just about everything in JunOS.
However, I think this can sometimes be too big of a hammer.

When you just want to pull out some counter data, routing protocol
states, route next-hops, etc., who wants to have to haul out XML and
XML-centric editing tools? The netconf Perl library seems like a step
in the right direction, but seems like just a thinly veiled
higher-layer API to build XML documents.

I'll cherish the day when I can just curl
http://r00ter/protocols/bgp/neighbors.json?key=d756d378f8e7bf506bf1c7d3aac2f8d480c84776

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] ldp signaling vpls can't up

2012-04-12 Thread William McLendon
looks like you left out 'family mpls' on the core interface ge-0/0/0.14 config, 
which is required for MPLS to function.

will



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] DOM: SNMP polling of RX power for 1 GE SFP impossible?

2012-04-12 Thread Michael Hare
We use an event script that converts parts of 'show interface 
diagnostics optics' and stuffs values into a MIB that is pollable.


The SLAX was given to us by Juniper several years ago after we whined a 
lot [ and didn't invest the effort to learn SLAX ].  It may not do 
everything -you- want, but might be useful as a start point.  We've used 
it successfully for 1/10g 'stuff' for several years.  I can't imagine 
they'd be upset with us sharing it.


-Michael

On 4/12/2012 4:13 AM, Per Granath wrote:

It should be possible to get the values via an op-script ...
Not sure if that can also populate MIB values.



So there is no way to poll by SNMP the power for 1 G SFP. Strange.


Yes, this is a significant omission, and you're certainly not the only
one to notice it. If enough people ask about it, maybe Juniper will do
something...


And when we do get them, next problem is, we don't know
programmatically what values to expect. As JNPR lacks 'entity mib' you can't
ask it via SNMP what type of optic it is, to determine what TX/RX/power etc
are expected for this optic.


___
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


[j-nsp] CGN ob MX5?

2012-04-12 Thread Matthias Brumm
Hi!

I would like to know, if no, some or all implementations of CGN will
be working on a MX5?

Regards,

Matthias
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] EX-UM-2X4SFP- 2-port 10G SFP+ / 4-port 1G SFP Uplink Module

2012-04-12 Thread Mike Williams
On Tuesday 21 February 2012 14:44:19 Timh Bergström wrote:
  Hope nobody minds me butting in here, but this brings up a related
  question for me.
 
  The built in uplink ports in the EX3300. Do they support running 2 at
  10Gb (for VC) and 2 at 1Gb for regular ethernet?
  I'm sure I've seen it written that all four ports can be used at 10Gb, if
  true that would support my belief mixed mode operation is supported too.

 Afaik two of the four 10Gb ports are pre-configured for VC, the other
 two can be used for ethernet out of the box, or you can use one for VC
 and three for ethernet or the other way round, no problems (at least
 that's what the juniper SE told me when I bought mine).

We got our stack of EX3300s yesterday.
I can confirm that (with 11.4R2.14 at least) you can do mixed 1/10GbE on the 
EX3300.
I've got 3 in a VC ring of 10Gb using ports 2 and 3, 10GbE in port 0, and 1GbE 
in port 1. Didn't have to do anything special either, although I did tell the 
VC to use ports 2 and 3 which was probably unnecessary.
1GbE SFPs cause a ge-x/1/x interface to appear, and 10GbE SFPs cause an 
xe-x/1/x interface to appear.

-- 
Mike Williams
Senior Infrastructure Architect
Comodo CA Ltd
Office Tel Europe: +44 (0) 161 8747070
Fax Europe: +44 (0) 161 8771767

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] CGN ob MX5?

2012-04-12 Thread Saku Ytti
On (2012-04-12 16:31 +0200), Matthias Brumm wrote:

 I would like to know, if no, some or all implementations of CGN will
 be working on a MX5?

This seems in realms of possibility (1ipv6 statically to 1ipv4) for trio.
But if you know you will need CGN I would assume that MX5 will never get
it, this way you'll avoid disappointment and possibly need for another box
while waiting for needed feature to appear.

NAPT (port based, nto1) is not possible as far as I understand on trio,
then you'd need some service slot in the behind, which also I would assume
never to exist when making purchase decision.

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] Capturing/displaying contents of incoming packets

2012-04-12 Thread Tom Storey
Hi all,

I am trying to debug some stubborn circuits that just dont seem to
want to work. I can see incoming packets being recorded on both
interfaces (10GE, both on the same router), but I cannot ping across
either link. Ive verified with the owner of the router at the other
end and we are using the correct subnets, and the same interface
configuration, but neither of us can ping the other.

I am interested to try and work out what is in the packets that are
coming in to work out if they belong to the routers they are supposed
to at the opposite end of each link, or where they are from.

Im wondering if there is some way to output the details like a TCP
dump, or capture to a pcap file which can be read by Wireshark et al?
The later seems possible on certain models, but not the gear in
question here, an MX960 with DPCEs.

The rate of packets is extremely low, as in 1 or 2 packets a minute,
but would potentially reveal a lot to me at this stage. Unfortunately
theres a bit of an air (and sea) gap between me and the router in
question, so any form of local troubleshooting is out of the question
at the moment.

Thanks,
Tom
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Capturing/displaying contents of incoming packets

2012-04-12 Thread Saku Ytti
On (2012-04-12 23:23 +0100), Tom Storey wrote:

 Im wondering if there is some way to output the details like a TCP
 dump, or capture to a pcap file which can be read by Wireshark et al?
 The later seems possible on certain models, but not the gear in
 question here, an MX960 with DPCEs.

Setup GRE tunnel towards your *nix box (no need to config tunnel in *nix) and
mirror packets to the tunnel.

Something to this effect
interfaces {
  gr-1/0/0 {
unit 1 {
  tunnel {
source your_loopback;
destination your_nix_pc;
  }
  family inet {
127.0.0.42/31;
  }
  family inet6 {
address fe80::42/127;
  }
}
  }
}
forwarding-options {
  port-mirroring {
input {
  rate 1;
}
family inet {
  output {
interface gr-1/0/0.1;
  }
}
family inet6 {
  output {
interface gr-1/0/0.1;
  }
}
  }
}

Then in firewall config 'then port-mirror;' for what ever you want to mirror.

I suggest using tshark in your NIX box, rather than tcpdump, as you can see
actual useful packet, not just the top GRE. And you can use display filters
matches to capture only interesting packets

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp