Re: [j-nsp] MX240+QFX5100 using Fusion - Any positive experience

2017-08-15 Thread Alain Hebert

Hi,

Can you provide a "show version" and "show chassis satellite softwar"

Might be faster just to match your version.

-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 08/10/17 14:34, santiago martinez wrote:

Hi there, which MPC are you using. We have fusion edge on our lab with mx104 
and no problem so far.

We have a mx240 , if we have the same MPC I guess I can give it a try.

Can you share your chassis config /  show chassis satellite output / show 
interface ge-102/0/20

Santi



Sent from my iPhone


On 10 Aug 2017, at 13:08, Alain Hebert  wrote:

Hi,

I'm thinking our local Juniper vendor is taking us for his personal Q&A...

Another tech sold to us instead of VCF: Fusion.

Anyone got it working on MX240+QFX5100...


Config:

< basic satellite config >

set interfaces ge-102/0/20 unit 0 family inet address 10.25.1.13/31


Test:

Every time I try to ping .12, I get this log.

Aug 10 07:49:56   fpc2 KERNEL/PFE APP=NH OUT OF SYNC: error code 3 
REASON: NH add received for an ifl that does not exist ERROR-SPECIFIC INFO: nh_id=684 
, type = Hold, ifl index 348 does not exist  TYPE-SPECIFIC INFO: none


What we looked at:

1. Yes everything was rebooted;

2. Yes The satellite look fine;

3. Yes the latest firmware is on the MX and the QFX;

MX: junos-install-mx-x86-32-17.2R1.13.tgz

QFX: satellite-3.1R1.3-signed.tgz since satellite-3.1R1.4.tgz is not 
signed so it cannot be installed.

4. Yes the optic are the same that those working in our QFX Junos native;

And no amount of GoogleFu could find a solution.  Our next step is JTAC.

--
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

___
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] MX240+QFX5100 using Fusion - Any positive experience

2017-08-10 Thread Alain Hebert

Yeah,

We have 104's too but since they're in production, its not a good 
idea to even sneeze nearthem =D.


So we're using one of our future productionMX240 with "MPCE Type 3 
3D" with a "10X10GE SFP+" MIC.  Pretty much the generic one for MX240


The cascade ports works enough to talk to the satellite and 
convert/upgrade/downgrade them.  Had no issue testing with xe-2/0/3-9 
with generic stuff.


Thanks for the input.


> show chassis hardware
Hardware inventory:
Item Version  Part number  Description
ChassisMX240
Midplane REV 07   760-021404   MX240 Backplane
FPM BoardREV 03   760-021392   Front Panel Display
PEM 0Rev 10   740-029970   PS 1.4-2.52kW; 90-264VAC in
PEM 1Rev 06   740-029970   PS 1.4-2.52kW; 90-264VAC in
PEM 2Rev 05   740-029970   PS 1.4-2.52kW; 90-264VAC in
PEM 3Rev 07   740-029970   PS 1.4-2.52kW; 90-264VAC in
Routing Engine 0 REV 08   740-031116   RE-S-1800x4
Routing Engine 1 REV 08   740-031116   RE-S-1800x4
CB 0 REV 14   750-031391   Enhanced MX SCB
CB 1 REV 14   750-031391   Enhanced MX SCB
FPC 2REV 07   750-045372   MPCE Type 3 3D
  CPUREV 08   711-035209   HMPC PMB 2G
  MIC 0  REV 07   750-033307   10X10GE SFPP
PIC 0 BUILTIN  10X10GE SFPP
  Xcvr 0 REV 01   740-031980   SFP+-10G-SR
  Xcvr 1 REV 01   740-021308   SFP+-10G-SR
Fan Tray 0   REV 01   710-030216   Enhanced Fan Tray


set chassis redundancy routing-engine 0 master
set chassis redundancy routing-engine 1 backup
set chassis network-services enhanced-ip
set chassis satellite-management fpc 101 serial-number 
set chassis satellite-management fpc 101 SAT1
set chassis satellite-management fpc 101 cascade-ports xe-2/0/1
set chassis satellite-management fpc 102 serial-number 
set chassis satellite-management fpc 102 SAT2
set chassis satellite-management fpc 102 cascade-ports xe-2/0/0
set chassis satellite-management upgrade-groups GROUP1 satellite 101
set chassis satellite-management upgrade-groups GROUP2 satellite 102
set chassis satellite-management auto-satellite-conversion satellite 101
set chassis satellite-management auto-satellite-conversion satellite 102

> show chassis satellite
Device  Cascade Port   Extended Ports
AliasSlot   State   Ports State  Total/Up
SAT1 101Online  xe-2/0/1 online 4/4
SAT2 102Online  xe-2/0/0 online 7/6


This is a Copper/SFP, same source SFP as those that are currently 
working in your QFX5100, but with Junos.


> show interfaces ge-102/0/20
Physical interface: ge-102/0/20, Enabled, Physical link is Up, Extended Port
  Interface index: 157, SNMP ifIndex: 546
  Description: 
  Link-level type: Ethernet, MTU: 1500, MRU: 1508, LAN-PHY mode,
  Link-mode: *Half-duplex,* Speed: Auto, BPDU Error: None,
  Loop Detect PDU Error: None, Ethernet-Switching Error: None,
  MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
  Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online,
  IEEE 802.3az Energy Efficient Ethernet: Disabled, Auto-MDIX: Enabled
  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  Link flags : None
  CoS queues : 8 supported, 8 maximum usable queues
  Schedulers : 0
  Current address: f4:b5:2f:44:48:04, Hardware address: f4:b5:2f:44:48:04
  Last flapped   : 2017-08-10 08:03:30 EDT (07:11:46 ago)
  Input rate : 464 bps (1 pps)
  Output rate: 0 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled

  Logical interface ge-102/0/20.0 (Index 348) (SNMP ifIndex 552)
Flags: Up 0x4004000 Encapsulation: ENET2
Input packets : 0
Output packets: 100
Protocol inet, MTU: 1486
Max nh cache: 75000, New hold nh limit: 75000, Curr nh cnt: 0,
Curr new hold cnt: 0, NH drop cnt: 0
  Flags: Sendbcast-pkt-to-re
  Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.25.1.12/31, Local: 10.25.1.13
Protocol multiservice, MTU: Unlimited
  Flags: Is-Primary


That bold should be 10Gbps/Full, they're the same source SFP+ as 
the cascade ports


> show interfaces xe-102/0/22
Physical interface: xe-102/0/22, Enabled, Physical link is Up, Extended Port
  Interface index: 161, SNMP ifIndex: 550
  Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 
*Unspecified*, Duplex: *Unspecified*, BPDU Error: None, Loop Detect PDU 
Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, 
Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  Link flags : None
  CoS queues : 8 supported, 8 m

Re: [j-nsp] MX240+QFX5100 using Fusion - Any positive experience

2017-08-10 Thread santiago martinez
Hi there, which MPC are you using. We have fusion edge on our lab with mx104 
and no problem so far.

We have a mx240 , if we have the same MPC I guess I can give it a try.

Can you share your chassis config /  show chassis satellite output / show 
interface ge-102/0/20

Santi



Sent from my iPhone

> On 10 Aug 2017, at 13:08, Alain Hebert  wrote:
> 
>Hi,
> 
>I'm thinking our local Juniper vendor is taking us for his personal Q&A...
> 
> Another tech sold to us instead of VCF: Fusion.
> 
>Anyone got it working on MX240+QFX5100...
> 
> 
> Config:
> 
>< basic satellite config >
> 
>set interfaces ge-102/0/20 unit 0 family inet address 10.25.1.13/31
> 
> 
> Test:
> 
>Every time I try to ping .12, I get this log.
> 
> Aug 10 07:49:56   fpc2 KERNEL/PFE APP=NH OUT OF SYNC: error code 3 
> REASON: NH add received for an ifl that does not exist ERROR-SPECIFIC INFO: 
> nh_id=684 , type = Hold, ifl index 348 does not exist  TYPE-SPECIFIC INFO: 
> none
> 
> 
> What we looked at:
> 
>1. Yes everything was rebooted;
> 
>2. Yes The satellite look fine;
> 
>3. Yes the latest firmware is on the MX and the QFX;
> 
>MX: junos-install-mx-x86-32-17.2R1.13.tgz
> 
>QFX: satellite-3.1R1.3-signed.tgz since satellite-3.1R1.4.tgz is not 
> signed so it cannot be installed.
> 
>4. Yes the optic are the same that those working in our QFX Junos native;
> 
>And no amount of GoogleFu could find a solution.  Our next step is JTAC.
> 
> -- 
> -
> Alain Hebertaheb...@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
> 
> ___
> 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] MX240+QFX5100 using Fusion - Any positive experience

2017-08-10 Thread Alain Hebert

Hi,

I'm thinking our local Juniper vendor is taking us for his personal 
Q&A...


Another tech sold to us instead of VCF: Fusion.

Anyone got it working on MX240+QFX5100...


Config:

< basic satellite config >

set interfaces ge-102/0/20 unit 0 family inet address 10.25.1.13/31


Test:

Every time I try to ping .12, I get this log.

Aug 10 07:49:56   fpc2 KERNEL/PFE APP=NH OUT OF SYNC: error code 3 
REASON: NH add received for an ifl that does not exist ERROR-SPECIFIC 
INFO: nh_id=684 , type = Hold, ifl index 348 does not exist  
TYPE-SPECIFIC INFO: none



What we looked at:

1. Yes everything was rebooted;

2. Yes The satellite look fine;

3. Yes the latest firmware is on the MX and the QFX;

MX: junos-install-mx-x86-32-17.2R1.13.tgz

QFX: satellite-3.1R1.3-signed.tgz since satellite-3.1R1.4.tgz 
is not signed so it cannot be installed.


4. Yes the optic are the same that those working in our QFX Junos 
native;


And no amount of GoogleFu could find a solution.  Our next step is 
JTAC.


--
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

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