Re: [j-nsp] Macsec not working with carrier ethernet link
Hi Ex4300 is fine with license and as I said one of the two carriers is working. As far as I understood the carrier with problems is providing q-in-q tunneling but I still have to get a confirmation on that. @Chuck, wan macsec or macsec is not an ieee standard? Juniper doesn't have any different deployment not standard as far as I know, am I wrong? Cheers Il Gio 26 Lug 2018, 23:01 james list ha scritto: > Dear experts, > I have a virtual chassis of ex4300 connected to another vc of ex4300 with > 2 x 1 Gbs links provided by two carriers. > > Lacp aggregation is up with just one carrier1 link encrypted with macsec, > unfortunately carrier2 is not going to find the problem and macsec packet > are not transported. > > I sent them the 802.1ae standard and ethertype to transport but no way. > > As far as I could understand they have Huawei devices. > > Do you have any suggestion for me to let them verify? > > Cheers > James > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Macsec not working with carrier ethernet link
On Thu, Jul 26, 2018 at 05:24:53PM -0500, Doug McIntyre wrote: > On Thu, Jul 26, 2018 at 05:35:42PM -0400, Chuck Anderson wrote: > > Ask your Juniper rep for a feature that Cisco calls "WAN MACsec". > > Juniper calls it MACsec. "WAN MACsec" is a slightly modified version that Cisco made in order to allow it to work over carrier ethernet systems that are underpinned by protocols that block 802.1x EAPOL and 802.1ae among other L2 PDUs. It is designed to work when you can't get cooperation from your carrier. If your carrier uses L2VPN, L2circuit, or some other type of point-to-point circuit, plain MACsec should "just work" as long as their physical port handoff to your MACsec switch is untagged. However, if they use VPLS or some other p2mp protocol that does MAC learning, it most likely won't bridge the 802.1x and/or 802.1ae frames unless a special config is used on the carrier side. Juniper needs to be configured to tunnel the L2 protocols for example. > The OP probably needs to make sure the firmware is correct for his platform. > https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/macsec.html > MACsec is also a licensed product. > Make sure the switches were ordered with the EX-QFX-MACSEC-ACC3 license. Lack of a license won't prevent it from working, at least with 14.x and 15.x--it will just warn you every time you commit. That might have changed with 17.x or 18.x. > > On Thu, Jul 26, 2018 at 11:01:37PM +0200, james list wrote: > > > Dear experts, > > > I have a virtual chassis of ex4300 connected to another vc of ex4300 with > > > 2 > > > x 1 Gbs links provided by two carriers. > > > > > > Lacp aggregation is up with just one carrier1 link encrypted with macsec, > > > unfortunately carrier2 is not going to find the problem and macsec packet > > > are not transported. > > > > > > I sent them the 802.1ae standard and ethertype to transport but no way. > > > > > > As far as I could understand they have Huawei devices. > > > > > > Do you have any suggestion for me to let them verify? > > > > > > Cheers > > > James ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Macsec not working with carrier ethernet link
On Thu, Jul 26, 2018 at 05:35:42PM -0400, Chuck Anderson wrote: > Ask your Juniper rep for a feature that Cisco calls "WAN MACsec". Juniper calls it MACsec. The OP probably needs to make sure the firmware is correct for his platform. https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/macsec.html MACsec is also a licensed product. Make sure the switches were ordered with the EX-QFX-MACSEC-ACC3 license. > On Thu, Jul 26, 2018 at 11:01:37PM +0200, james list wrote: > > Dear experts, > > I have a virtual chassis of ex4300 connected to another vc of ex4300 with 2 > > x 1 Gbs links provided by two carriers. > > > > Lacp aggregation is up with just one carrier1 link encrypted with macsec, > > unfortunately carrier2 is not going to find the problem and macsec packet > > are not transported. > > > > I sent them the 802.1ae standard and ethertype to transport but no way. > > > > As far as I could understand they have Huawei devices. > > > > Do you have any suggestion for me to let them verify? > > > > Cheers > > James > ___ > 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] Macsec not working with carrier ethernet link
Ask your Juniper rep for a feature that Cisco calls "WAN MACsec". On Thu, Jul 26, 2018 at 11:01:37PM +0200, james list wrote: > Dear experts, > I have a virtual chassis of ex4300 connected to another vc of ex4300 with 2 > x 1 Gbs links provided by two carriers. > > Lacp aggregation is up with just one carrier1 link encrypted with macsec, > unfortunately carrier2 is not going to find the problem and macsec packet > are not transported. > > I sent them the 802.1ae standard and ethertype to transport but no way. > > As far as I could understand they have Huawei devices. > > Do you have any suggestion for me to let them verify? > > Cheers > James ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] SRX550HM max BGP routes in FIB?
Hi, does anybody use SRX550 or SRX550HM as BGP router with full IPv4/IPv6 routing table? SRX550 is older model with 2GB RAM, running Junos 12.1, SRX550HM is current model with 4GB RAM and 8GB CF card, running Junos15.1. The datasheet (https://www.juniper.net/assets/us/en/local/pdf/datasheets/1000281-en.pdf) states any of these two hardware versions can eat 712K BGP routes at maximum. Currently full BGP table contains 728K IPv4 routes + 55K IPv6 routes. I would speculate that at least newer "HM" version can manage much more than just 712K routes. How many routes can the box really squeeze into its FIB? Best regards, Tadej ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Macsec not working with carrier ethernet link
Dear experts, I have a virtual chassis of ex4300 connected to another vc of ex4300 with 2 x 1 Gbs links provided by two carriers. Lacp aggregation is up with just one carrier1 link encrypted with macsec, unfortunately carrier2 is not going to find the problem and macsec packet are not transported. I sent them the 802.1ae standard and ethertype to transport but no way. As far as I could understand they have Huawei devices. Do you have any suggestion for me to let them verify? Cheers James ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
--> so then in a 2node VC one node is Master one node is backup > If they split the master will go down but the backup should survive as it > is > still half of the original cluster > > So this means you should make the part you want to survive to be the > backup-RE and not the master-RE > > --- or did I miss something ?! > > My philosophy is that a default use case of a two nodes VC (and nearly only use case of a VC at all) should be some LAG-based redundancy, when two switches are racked next to each other, connected with two twinax cables and should never split. Of course, technically they can, but a lot of other bloody things, which are out of our control, can happen to them: software bug, misconfiguration, uncontrolled hardware failure like bite errors cased by an overheated SFP, drunk worker with an angle grinder etc. All the exotic cases like geographically distributed VCs etc are, in my opinion, an exercise for the folks who can't figure out what routing protocols are made for. So this should not be the default use case, and the default software behavior should not be adapted to such scenarios. Thus in a two-nodes VC, a *real* failure scenario is a switch failure. When split-detection is enabled, two-nodes VC will only survive in 50% of switch failure cases (if backup RE dies, VC dies, if master RE dies, VC survives). So in fact it's just no better than a signle non-redundant switch. It's worse, in fact, as the added complexity and false expectations are, in fact, more expensive currency than a controlled service outage. Cheers, Pavel ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
Alexander Marhold wrote: > Therefore if you want to put one node out of a 2 node VC you need to put the > Master down not the backup > Sounds strange but this is according to the rules stated below Interesting twist :-) -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
Tobias Heister wrote: > > > > Yes, no-split-detection did help. > > I would like to add to that. My point of view is that you do not > always disable split-detection in a two member VC. You can do so if > you know what that implies. > > The reasoning for the remaining node going into LC mode is that only > the portions of the VC having the majority of nodes stays up and > operational. In a two member VC if for whatever reason one of the > nodes looses connection to the other, we cannot have a majority so > both sides go down. Even if it is the only node remaining. > > But imagine an error scenario where the second node does not crash, > but for whatever reason both sides stay up, but the connection > between them gets lost. With split-detection configured, both sides > will go down and you have a controlled service outage. When no > split-detection is configured both sides remain up and you might > have interesting effects happening in your network with two switches > with the same configuration and same "identity" being up and > forwarding. I have seen that happening in DC scenarios doing stp to > other devices and it is not pretty! Thank you for the explanation. However, in my case I would rather risk an active/active configuration than have two unresponsive switches which can only be revived through manual intervention. This is mainly because: 1. The stacks are in remote locations, you have to ride an all-terrain vehicle to reach them for manual intervention, or sometimes even a helicopter. 2. The stack members are located together in one rack, so the most likely scenarios requiring failover will be a) one switch hardware failure or b) a failure of one of the UPSes or invertors. 3. An active/active situation can be easily mitigated remotely by shutting down a port on the uplink. > > So always check the implications of what the command are doing. If > in your case an active/active split scenario (for worst case) works > out better than a completely offline VC, that is perfectly fine. I > have seen lots of scenarios where it would not be the expected or > wanted behavior. But in my world a VC is no real redundancy method > it is just stacking-NG for additional ports under one MGMT so i > would have two VCs if i relay need redundancy in most setups. But > that is just me ;) I guess, in my case a completely offline VC is unacceptable. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
Therefore if you want to put one node out of a 2 node VC you need to put the Master down not the backup Sounds strange but this is according to the rules stated below Regards alexander -Ursprüngliche Nachricht- Von: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] Im Auftrag von Alexander Marhold Gesendet: Donnerstag, 26. Juli 2018 09:52 An: 'Tobias Heister'; 'Victor Sudakov'; 'Pavel Lunin' Cc: 'juniper-nsp' Betreff: Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode Hi According to the documentation there should be the following behavior with split-detection enabled: In case of a complete split: If the Master-RE sees MORE THAN HALF of the devices it survives otherwise it disables that part of the cluster If the Backup-RE sees HALF of the devices the backup Re will survive and play the master --> so then in a 2node VC one node is Master one node is backup If they split the master will go down but the backup should survive as it is still half of the original cluster So this means you should make the part you want to survive to be the backup-RE and not the master-RE --- or did I miss something ?! Regards Alexander -Ursprüngliche Nachricht- Von: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] Im Auftrag von Tobias Heister Gesendet: Donnerstag, 26. Juli 2018 09:26 An: Victor Sudakov; Pavel Lunin Cc: juniper-nsp Betreff: Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode Hi, On 26.07.2018 09:06, Victor Sudakov wrote: >>> I don't like to explain what others say but I think yes. It's been known >>> behavior since always: in a two-member VC always disable split-detection. >>> You can google for other threads on this in this list. >>> >>> It's always been kind of poorly documented. Last time I checked the docs, >>> instead of just writing clearly that it must be disabled in two-members >>> mode, they "don't recommend" it with some kind of hand-waving explanation >>> that if you estimate that the backup RE failure probability is higher that >>> a split-brain condition blah-blah-blah... Just disable split-detection, >>> that's it :) >> >> Tomorrow we are planning a lab with and without split-detection. I >> hope this solves the issue for us, and if it does, I'm sure to make a >> note in my engineering journal. > > Yes, no-split-detection did help. I would like to add to that. My point of view is that you do not always disable split-detection in a two member VC. You can do so if you know what that implies. The reasoning for the remaining node going into LC mode is that only the portions of the VC having the majority of nodes stays up and operational. In a two member VC if for whatever reason one of the nodes looses connection to the other, we cannot have a majority so both sides go down. Even if it is the only node remaining. But imagine an error scenario where the second node does not crash, but for whatever reason both sides stay up, but the connection between them gets lost. With split-detection configured, both sides will go down and you have a controlled service outage. When no split-detection is configured both sides remain up and you might have interesting effects happening in your network with two switches with the same configuration and same "identity" being up and forwarding. I have seen that happening in DC scenarios doing stp to other devices and it is not pretty! So always check the implications of what the command are doing. If in your case an active/active split scenario (for worst case) works out better than a completely offline VC, that is perfectly fine. I have seen lots of scenarios where it would not be the expected or wanted behavior. But in my world a VC is no real redundancy method it is just stacking-NG for additional ports under one MGMT so i would have two VCs if i relay need redundancy in most setups. But that is just me ;) -- Kind Regards Tobias Heister ___ 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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
Hi According to the documentation there should be the following behavior with split-detection enabled: In case of a complete split: If the Master-RE sees MORE THAN HALF of the devices it survives otherwise it disables that part of the cluster If the Backup-RE sees HALF of the devices the backup Re will survive and play the master --> so then in a 2node VC one node is Master one node is backup If they split the master will go down but the backup should survive as it is still half of the original cluster So this means you should make the part you want to survive to be the backup-RE and not the master-RE --- or did I miss something ?! Regards Alexander -Ursprüngliche Nachricht- Von: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] Im Auftrag von Tobias Heister Gesendet: Donnerstag, 26. Juli 2018 09:26 An: Victor Sudakov; Pavel Lunin Cc: juniper-nsp Betreff: Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode Hi, On 26.07.2018 09:06, Victor Sudakov wrote: >>> I don't like to explain what others say but I think yes. It's been known >>> behavior since always: in a two-member VC always disable split-detection. >>> You can google for other threads on this in this list. >>> >>> It's always been kind of poorly documented. Last time I checked the docs, >>> instead of just writing clearly that it must be disabled in two-members >>> mode, they "don't recommend" it with some kind of hand-waving explanation >>> that if you estimate that the backup RE failure probability is higher that >>> a split-brain condition blah-blah-blah... Just disable split-detection, >>> that's it :) >> >> Tomorrow we are planning a lab with and without split-detection. I >> hope this solves the issue for us, and if it does, I'm sure to make a >> note in my engineering journal. > > Yes, no-split-detection did help. I would like to add to that. My point of view is that you do not always disable split-detection in a two member VC. You can do so if you know what that implies. The reasoning for the remaining node going into LC mode is that only the portions of the VC having the majority of nodes stays up and operational. In a two member VC if for whatever reason one of the nodes looses connection to the other, we cannot have a majority so both sides go down. Even if it is the only node remaining. But imagine an error scenario where the second node does not crash, but for whatever reason both sides stay up, but the connection between them gets lost. With split-detection configured, both sides will go down and you have a controlled service outage. When no split-detection is configured both sides remain up and you might have interesting effects happening in your network with two switches with the same configuration and same "identity" being up and forwarding. I have seen that happening in DC scenarios doing stp to other devices and it is not pretty! So always check the implications of what the command are doing. If in your case an active/active split scenario (for worst case) works out better than a completely offline VC, that is perfectly fine. I have seen lots of scenarios where it would not be the expected or wanted behavior. But in my world a VC is no real redundancy method it is just stacking-NG for additional ports under one MGMT so i would have two VCs if i relay need redundancy in most setups. But that is just me ;) -- Kind Regards Tobias Heister ___ 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] EX4200 virtual chassis problem, master going into linecard mode
Hi, On 26.07.2018 09:06, Victor Sudakov wrote: I don't like to explain what others say but I think yes. It's been known behavior since always: in a two-member VC always disable split-detection. You can google for other threads on this in this list. It's always been kind of poorly documented. Last time I checked the docs, instead of just writing clearly that it must be disabled in two-members mode, they "don't recommend" it with some kind of hand-waving explanation that if you estimate that the backup RE failure probability is higher that a split-brain condition blah-blah-blah... Just disable split-detection, that's it :) Tomorrow we are planning a lab with and without split-detection. I hope this solves the issue for us, and if it does, I'm sure to make a note in my engineering journal. Yes, no-split-detection did help. I would like to add to that. My point of view is that you do not always disable split-detection in a two member VC. You can do so if you know what that implies. The reasoning for the remaining node going into LC mode is that only the portions of the VC having the majority of nodes stays up and operational. In a two member VC if for whatever reason one of the nodes looses connection to the other, we cannot have a majority so both sides go down. Even if it is the only node remaining. But imagine an error scenario where the second node does not crash, but for whatever reason both sides stay up, but the connection between them gets lost. With split-detection configured, both sides will go down and you have a controlled service outage. When no split-detection is configured both sides remain up and you might have interesting effects happening in your network with two switches with the same configuration and same "identity" being up and forwarding. I have seen that happening in DC scenarios doing stp to other devices and it is not pretty! So always check the implications of what the command are doing. If in your case an active/active split scenario (for worst case) works out better than a completely offline VC, that is perfectly fine. I have seen lots of scenarios where it would not be the expected or wanted behavior. But in my world a VC is no real redundancy method it is just stacking-NG for additional ports under one MGMT so i would have two VCs if i relay need redundancy in most setups. But that is just me ;) -- Kind Regards Tobias Heister ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 virtual chassis problem, master going into linecard mode
Victor Sudakov wrote: > Pavel Lunin wrote: > > > > in a virtual chassis you could add: > > > > > > > > set virtual-chassis no-split-detection > > > > > > > > This will ensure that if both VC ports go down, the master routing > > > engine carries on working. > > > > > > Are you referring to "Scenario B" in > > > https://kb.juniper.net/InfoCenter/index?page=content=KB13879 ? > > > or a different case? > > > > > > > > > I don't like to explain what others say but I think yes. It's been known > > behavior since always: in a two-member VC always disable split-detection. > > You can google for other threads on this in this list. > > > > It's always been kind of poorly documented. Last time I checked the docs, > > instead of just writing clearly that it must be disabled in two-members > > mode, they "don't recommend" it with some kind of hand-waving explanation > > that if you estimate that the backup RE failure probability is higher that > > a split-brain condition blah-blah-blah... Just disable split-detection, > > that's it :) > > Tomorrow we are planning a lab with and without split-detection. I > hope this solves the issue for us, and if it does, I'm sure to make a > note in my engineering journal. Yes, no-split-detection did help. Thank you Catalin and Pavel very much again. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp