Re: [j-nsp] MPLS EX4550

2015-03-06 Thread Giuliano (WZTECH)
We didnt find a solution because ex4550 (junos) code does not support 2 
different families for the same interface (yet) ... Using 12.3R8

I think the new switches ex4600, ex4300 fiber and qfx5100 will support it 
considering junos ELS and it new hardware

Sent from my iPhone

> On Mar 6, 2015, at 18:01, Levi Pederson  
> wrote:
> 
> Giuliano,
> 
> I thank you for the prompt reply.  I had originally thought that would create 
> a loop on the switch, but I believe you are right in that it will just shunt 
> the VLAN as anticipated.  However,  I was wondering if there was a a solution 
> that can be accomplished without having to use a loop-cable?
> 
> Thank you,
> 
> 
> Levi Pederson
> Mankato Networks LLC
> cell | 612.481.0769
> work | 612.787.7392
> levipeder...@mankatonetworks.net
> 
> 
>> On Fri, Mar 6, 2015 at 2:57 PM, Giuliano (WZTECH)  
>> wrote:
>> We have a situation here and we find a way ... We connect 2 interfaces in a 
>> optical cable loop ... One that came from a trunk interface ... Family 
>> ethernet-switching and other family mpls with L2-circuit to do a vlan 
>> traffic to enter in a mpls interface
>> 
>> Sent from my iPhone
>> 
>> > On Mar 6, 2015, at 17:51, Levi Pederson  
>> > wrote:
>> >
>> > All,
>> >
>> > I've got a simple MPLS setup with 4 EX4550's.
>> >
>> > They are currently in an incomplete ring but will soon have a full ring
>> > situation.
>> >
>> > I've currently got 3 circuits on the transport working wonderfully.
>> > However I'm trying to add another alas I'm a bit confused as how to 
>> > proceed.
>> >
>> > Previous other circuits were easier in the fact they were simply saying the
>> > port on MPLS1-1 is equivalent to this port on MPLS 3-1.
>> >
>> > The new circuit is different in that I have to take a VLAN recieved on a
>> > trunk port and send it through the MPLS network to 3-1 and then into a
>> > vlan-tagged MX-10.
>> >
>> > I was wondering if anyone has attempted this and has any pointers.
>> >
>> > Thank you,
>> >
>> > *Levi Pederson*
>> > Mankato Networks LLC
>> > cell | 612.481.0769
>> > work | 612.787.7392
>> > levipeder...@mankatonetworks.net
>> > ___
>> > 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


Re: [j-nsp] MPLS EX4550

2015-03-06 Thread Levi Pederson
Giuliano,

I thank you for the prompt reply.  I had originally thought that would
create a loop on the switch, but I believe you are right in that it will
just shunt the VLAN as anticipated.  However,  I was wondering if there was
a a solution that can be accomplished without having to use a loop-cable?

Thank you,


*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net


On Fri, Mar 6, 2015 at 2:57 PM, Giuliano (WZTECH) 
wrote:

> We have a situation here and we find a way ... We connect 2 interfaces in
> a optical cable loop ... One that came from a trunk interface ... Family
> ethernet-switching and other family mpls with L2-circuit to do a vlan
> traffic to enter in a mpls interface
>
> Sent from my iPhone
>
> > On Mar 6, 2015, at 17:51, Levi Pederson <
> levipeder...@mankatonetworks.net> wrote:
> >
> > All,
> >
> > I've got a simple MPLS setup with 4 EX4550's.
> >
> > They are currently in an incomplete ring but will soon have a full ring
> > situation.
> >
> > I've currently got 3 circuits on the transport working wonderfully.
> > However I'm trying to add another alas I'm a bit confused as how to
> proceed.
> >
> > Previous other circuits were easier in the fact they were simply saying
> the
> > port on MPLS1-1 is equivalent to this port on MPLS 3-1.
> >
> > The new circuit is different in that I have to take a VLAN recieved on a
> > trunk port and send it through the MPLS network to 3-1 and then into a
> > vlan-tagged MX-10.
> >
> > I was wondering if anyone has attempted this and has any pointers.
> >
> > Thank you,
> >
> > *Levi Pederson*
> > Mankato Networks LLC
> > cell | 612.481.0769
> > work | 612.787.7392
> > levipeder...@mankatonetworks.net
> > ___
> > 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


Re: [j-nsp] MPLS EX4550

2015-03-06 Thread Giuliano (WZTECH)
We have a situation here and we find a way ... We connect 2 interfaces in a 
optical cable loop ... One that came from a trunk interface ... Family 
ethernet-switching and other family mpls with L2-circuit to do a vlan traffic 
to enter in a mpls interface

Sent from my iPhone

> On Mar 6, 2015, at 17:51, Levi Pederson  
> wrote:
> 
> All,
> 
> I've got a simple MPLS setup with 4 EX4550's.
> 
> They are currently in an incomplete ring but will soon have a full ring
> situation.
> 
> I've currently got 3 circuits on the transport working wonderfully.
> However I'm trying to add another alas I'm a bit confused as how to proceed.
> 
> Previous other circuits were easier in the fact they were simply saying the
> port on MPLS1-1 is equivalent to this port on MPLS 3-1.
> 
> The new circuit is different in that I have to take a VLAN recieved on a
> trunk port and send it through the MPLS network to 3-1 and then into a
> vlan-tagged MX-10.
> 
> I was wondering if anyone has attempted this and has any pointers.
> 
> Thank you,
> 
> *Levi Pederson*
> Mankato Networks LLC
> cell | 612.481.0769
> work | 612.787.7392
> levipeder...@mankatonetworks.net
> ___
> 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] MPLS EX4550

2015-03-06 Thread Levi Pederson
All,

I've got a simple MPLS setup with 4 EX4550's.

They are currently in an incomplete ring but will soon have a full ring
situation.

I've currently got 3 circuits on the transport working wonderfully.
However I'm trying to add another alas I'm a bit confused as how to proceed.

Previous other circuits were easier in the fact they were simply saying the
port on MPLS1-1 is equivalent to this port on MPLS 3-1.

The new circuit is different in that I have to take a VLAN recieved on a
trunk port and send it through the MPLS network to 3-1 and then into a
vlan-tagged MX-10.

I was wondering if anyone has attempted this and has any pointers.

Thank you,

*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Juniper MX and VZ FIOS question

2015-03-06 Thread Mark Tinka


On 6/Mar/15 16:48, Chris Evans wrote:
> Thanks..  Exactly the answer that I was looking.. Just needed to know
> the feature/solution name so I can go research it.
>
> Found this
> doc: 
> http://www.juniper.net/techpubs/en_US/release-independent/solutions/information-products/pathway-pages/solutions/8010092-en.pdf
>
> IPoE would be what it is.
>
> Another Example:
> http://rickmur.com/bras-on-juniper-mx/

Yes, IPoE is the industry marketing term that used to float around a
lot. I prefer the DHCP term :-).

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


Re: [j-nsp] Juniper MX and VZ FIOS question

2015-03-06 Thread Chris Evans
Thanks..  Exactly the answer that I was looking.. Just needed to know the
feature/solution name so I can go research it.

Found this doc:
http://www.juniper.net/techpubs/en_US/release-independent/solutions/information-products/pathway-pages/solutions/8010092-en.pdf

IPoE would be what it is.

Another Example:
http://rickmur.com/bras-on-juniper-mx/


On Thu, Mar 5, 2015 at 11:59 PM, Mark Tinka  wrote:

>
>
> On 6/Mar/15 00:34, Chris Evans wrote:
> > I'm a FIOS user and they use Juniper MX in many locations (along with E
> > series in older installs) and I'm curious of a typical configuration
> they'd
> > be using. WIth FIOS I just have a straight ethernet connection, no
> logging
> > in, no providing user information, etc..
> >
> > So since i'm not logging in would that still be a BRAS configuration?
> > Also they have a feature enabled that poisons ARP entries if you try to
> put
> > a box on the wire that has a different IP than what your DHCP lease is
> > given you. What feature would that be?
> >
> > Very curious how they'd do this. I've only worked with JUNOS boxes in the
> > enterprise so I don't have experience with features like this.
>
> Yes, it would still be a BNG solution, but using DHCP (in lieu of PPPoE).
>
> Authentication could be based on several things such as MAC address,
> VLAN ID, switch/OLT port, or a combination of them.
>
> The MX as a BNG supports DHCP subscriber management. I'm sure the ERX
> does too.
>
> Personally, I prefer DHCP to PPPoE.
>
> Mark.
> ___
> 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] EX4500 SFP+ laser lit when interface is admin down and vice versa

2015-03-06 Thread Tore Anderson
Hi,

I've got an EX4500 running 12.3R8.7 that has a port that's misbehaving
in a rather odd way: If I disable the interface in the config and
commit, the laser is turned on (normal Tx levels in show interfaces
diagnostics optics). If I re-enable the interface and commit, the laser
is switched off (Tx level of -Inf dBm). So it's doing precisely the
opposite of what I'd expect it to.

When I commit the configuration that enables the interface, the
following message is logged:

chassism[1405]: Tx Disable called for port: 0, enable: 0

I've tried multiple SFP+ modules and they all behave the same. Also
I've tried re-seating the SFP+ with as many different combinations of
the interface being disabled/enabled when I remove/insert the module as
I could think of, no luck. Finally it's only impacting port 0, e.g.,
port 4 works as expected (i.e., Tx off when interface is disabled and
on when enabled) - even with the very same module that don't work right
when inserted in port 0.

Anyone seen anything like that? I'm hoping to find a way fix it without
needing a maintenance window to reboot it.

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