Re: [j-nsp] MX routers and DAC cables?
--- Begin Message --- Seconding Eric's point, depending on the version of Junos and transceiver, fec will be auto-configured, can be turned off, but depending on the transceiver, for example CWDM4, fec must be enabled on both sides to get link-up. Along with disabling auto-negotiation on one side or both can sometimes help. Just make sure to wait 1min after committing as changes to take effect can be delayed. -Aaron Jun 12, 2020, 13:55 by e...@telic.us: > That's what I was going to chime in on. Behaviour differences between > software versions have done different defaults. > > ekrichbaum@atl-bdr1> show interfaces et-0/0/1 | grep FEC > Active defects : None > Ethernet FEC Mode : NONE > > eric@cht-bdr2> show interfaces et-0/0/1 | grep FEC > Active defects : None > Ethernet FEC Mode : FEC91 > > These are 204s with a difference in default from 17.4 to 18.2 somewhere. > Manually setting FEC on both ends seems to correct and bring up the links. > > > -Original Message- > From: juniper-nsp On Behalf Of Tobias > Heister > Sent: Friday, June 12, 2020 2:03 PM > To: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] MX routers and DAC cables? > > Hi, > > On 12.06.2020 20:39, Chris Adams wrote: > >> Is anybody using DAC cables on MX routers? We have a customer with an >> MX10003 connected to EX4600 switches with 40G DAC cables (Juniper >> parts, not third-party). Upon upgrading the router JUNOS to >> 18.2R3-S3, none of the interfaces with a DAC cable would come up on the >> > router end. > >> >> JTAC's response was that no DAC cables are supported on any MX routers. >> >> That seems a little odd to me... I thought DAC cables are a part of >> the various specs, so saying they're not supported is saying those >> aren't actually Ethernet ports to me. >> > > DAC and AOC are transceivers, and officially only a specific set of > transceivers are supported per platform. > > For MX10003 you can check here: > https://apps.juniper.net/hct/product/#prd=MX10003 > > There are 40GE AOC supported for that box, but not 40GE DAC. For 100GE DAC > are actually supported in later Junos version. > > That being said typically DAC worked in MX for 10G and even 40G on most > noxes, but on MX10003 we had a lot of problems with 40G DACs and eventually > replaced most/all of of them with optical transceivers. > > Even on 100GE you might need to set the FEC config depending on what and > where you connect the other DAC end. > > While 10G mostly worked everywhere we had a fair share of trouble on 40 and > 100GE on various vendors and platforms. > > -- > regards > Tobias > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > -- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX routers and DAC cables?
That's what I was going to chime in on. Behaviour differences between software versions have done different defaults. ekrichbaum@atl-bdr1> show interfaces et-0/0/1 | grep FEC Active defects : None Ethernet FEC Mode : NONE eric@cht-bdr2> show interfaces et-0/0/1 | grep FEC Active defects : None Ethernet FEC Mode : FEC91 These are 204s with a difference in default from 17.4 to 18.2 somewhere. Manually setting FEC on both ends seems to correct and bring up the links. -Original Message- From: juniper-nsp On Behalf Of Tobias Heister Sent: Friday, June 12, 2020 2:03 PM To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] MX routers and DAC cables? Hi, On 12.06.2020 20:39, Chris Adams wrote: > Is anybody using DAC cables on MX routers? We have a customer with an > MX10003 connected to EX4600 switches with 40G DAC cables (Juniper > parts, not third-party). Upon upgrading the router JUNOS to > 18.2R3-S3, none of the interfaces with a DAC cable would come up on the router end. > > JTAC's response was that no DAC cables are supported on any MX routers. > > That seems a little odd to me... I thought DAC cables are a part of > the various specs, so saying they're not supported is saying those > aren't actually Ethernet ports to me. DAC and AOC are transceivers, and officially only a specific set of transceivers are supported per platform. For MX10003 you can check here: https://apps.juniper.net/hct/product/#prd=MX10003 There are 40GE AOC supported for that box, but not 40GE DAC. For 100GE DAC are actually supported in later Junos version. That being said typically DAC worked in MX for 10G and even 40G on most noxes, but on MX10003 we had a lot of problems with 40G DACs and eventually replaced most/all of of them with optical transceivers. Even on 100GE you might need to set the FEC config depending on what and where you connect the other DAC end. While 10G mostly worked everywhere we had a fair share of trouble on 40 and 100GE on various vendors and platforms. -- regards Tobias ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX routers and DAC cables?
Hi, On 12.06.2020 20:39, Chris Adams wrote: Is anybody using DAC cables on MX routers? We have a customer with an MX10003 connected to EX4600 switches with 40G DAC cables (Juniper parts, not third-party). Upon upgrading the router JUNOS to 18.2R3-S3, none of the interfaces with a DAC cable would come up on the router end. JTAC's response was that no DAC cables are supported on any MX routers. That seems a little odd to me... I thought DAC cables are a part of the various specs, so saying they're not supported is saying those aren't actually Ethernet ports to me. DAC and AOC are transceivers, and officially only a specific set of transceivers are supported per platform. For MX10003 you can check here: https://apps.juniper.net/hct/product/#prd=MX10003 There are 40GE AOC supported for that box, but not 40GE DAC. For 100GE DAC are actually supported in later Junos version. That being said typically DAC worked in MX for 10G and even 40G on most noxes, but on MX10003 we had a lot of problems with 40G DACs and eventually replaced most/all of of them with optical transceivers. Even on 100GE you might need to set the FEC config depending on what and where you connect the other DAC end. While 10G mostly worked everywhere we had a fair share of trouble on 40 and 100GE on various vendors and platforms. -- regards Tobias ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX routers and DAC cables?
Juniper's official Hardware Compatibility Guide lists 100G DACs as officially supported on MX10003, so "no DACs" being officially supported is not true. https://apps.juniper.net/hct/product/#prd=MX10003 We have used DAC cables (10G, 40G, & 40G -> 4x10G) with MX204s up to 18.4R3. I have also labbed up 40G DACs with EX4300s (for VC and uplink to MX) with no issues. -- __ David Miller dmil...@tiggee.com On Fri, Jun 12, 2020 at 2:41 PM Chris Adams wrote: > > Is anybody using DAC cables on MX routers? We have a customer with an > MX10003 connected to EX4600 switches with 40G DAC cables (Juniper parts, > not third-party). Upon upgrading the router JUNOS to 18.2R3-S3, none of > the interfaces with a DAC cable would come up on the router end. > > JTAC's response was that no DAC cables are supported on any MX routers. > > That seems a little odd to me... I thought DAC cables are a part of the > various specs, so saying they're not supported is saying those aren't > actually Ethernet ports to me. > > -- > Chris Adams > ___ > 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] [EXT] MX routers and DAC cables?
I've used SFP+ DACs on MX, EX and QFX without problems. I have not tried QSFP DACs on MX, but they work on EX/QFX. On Fri, Jun 12, 2020 at 01:39:11PM -0500, Chris Adams wrote: > Is anybody using DAC cables on MX routers? We have a customer with an > MX10003 connected to EX4600 switches with 40G DAC cables (Juniper parts, > not third-party). Upon upgrading the router JUNOS to 18.2R3-S3, none of > the interfaces with a DAC cable would come up on the router end. > > JTAC's response was that no DAC cables are supported on any MX routers. > > That seems a little odd to me... I thought DAC cables are a part of the > various specs, so saying they're not supported is saying those aren't > actually Ethernet ports to me. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX routers and DAC cables?
Though not had any experience with MX's, we were never successful in getting DAC's to work with our EX's. Had to go for optics. We learned to just not bother with DAC's in future due to off-list anecdotes of such behavior - not just with Juniper (HPE, Cisco...) -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Chris Adams Sent: Friday, June 12, 2020 11:39 AM To: juniper-nsp@puck.nether.net Subject: [j-nsp] MX routers and DAC cables? Is anybody using DAC cables on MX routers? We have a customer with an MX10003 connected to EX4600 switches with 40G DAC cables (Juniper parts, not third-party). Upon upgrading the router JUNOS to 18.2R3-S3, none of the interfaces with a DAC cable would come up on the router end. JTAC's response was that no DAC cables are supported on any MX routers. That seems a little odd to me... I thought DAC cables are a part of the various specs, so saying they're not supported is saying those aren't actually Ethernet ports to me. -- Chris Adams ___ 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] MX routers and DAC cables?
Is anybody using DAC cables on MX routers? We have a customer with an MX10003 connected to EX4600 switches with 40G DAC cables (Juniper parts, not third-party). Upon upgrading the router JUNOS to 18.2R3-S3, none of the interfaces with a DAC cable would come up on the router end. JTAC's response was that no DAC cables are supported on any MX routers. That seems a little odd to me... I thought DAC cables are a part of the various specs, so saying they're not supported is saying those aren't actually Ethernet ports to me. -- Chris Adams ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] [EXT] Wishing for clarification on how dhcp-relay works with multiple server addresses
--- Begin Message --- Matti Saarinen writes: > Based on the forum responses[1] I'd say we have to live with the > situation where we need to run dhcp-relay without forward-only on > interfaces connecting networks needing PXE. The annoying issue is that > every interface without forward-only eats one scale-subsrciber licence. One of many annoying issues... The old DHCP helper solution worked. The new has been a disaster. It is great that the new solution is there for those who need subscriber management. However, for regular enterprise DHCP relay it is over-complex, brittle, and buggy. It took more than 3 years to get the new code halfway-workable on the SRX series. For the longest time we had to run a script every minute to clear out the relay table, otherwise some legitimate replies from servers would not be forwarded. /Benny --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Wishing for clarification on how dhcp-relay works with multiple server addresses
On Fri, Jun 12, 2020 at 08:44:48AM +0300, Matti Saarinen wrote: > Chuck Anderson wrote: > > > On Thu, Jun 11, 2020 at 08:40:23AM +0300, Matti Saarinen wrote: > >> We have a setup where one set of DHCP servers deliver IP configuration > >> to clients and another set of DHCP servers deliver the PXE options. This > > > > Don't do that. Clients do not aggregate DHCP options from different > > responses--they pick ONE DHCP server to bind to and use the info from > > that one only. That's how the DHCP spec is written. > > Actually, this setup has been working for years. I suppose the PXE code > is more flexible in that matter. In any case, it worries me that we have > been relying on a feature that may change without any notice when NIC > firmwares are updated. > > Back to my question: > > Based on the forum responses[1] I'd say we have to live with the > situation where we need to run dhcp-relay without forward-only on > interfaces connecting networks needing PXE. The annoying issue is that > every interface without forward-only eats one scale-subsrciber licence. You can try using the legacy helpers configuration, but I'm not sure it works on MX10003: set forwarding-options helpers bootp server x.x.x.x set forwarding-options helpers bootp server y.y.y.y set forwarding-options helpers bootp server z.z.z.z set forwarding-options helpers bootp maximum-hop-count 16 set forwarding-options helpers bootp client-response-ttl 20 set forwarding-options helpers bootp interface xe-x/x/x. broadcast ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
