SRX

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

Can you expand on what you mean by multi-link trunking?  Do you mean aggregated ethernet interfaces (like LACP) or WAN bonding?

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

The number of links in an AE bundle supported vary by platform. But should scale beyond 4.  Also, if you mean number of AEs that set via a cli command and goes past 8. 

I'm kind of confused on what your concerns are, can you state platform and config bits?

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

I am only worried about how SRX Series supports my multilink trunks in my avaya switch cluster. The need to try to extend my trunks through these SRX's is my goal for now. The link I gave is the BASE for the technology. I realize that how my avaya cluster communicates with other devices is out of the scope here, but I haven't chosen to extend alot of srx work beyond subsystem coding. Thus is why I'm seeking srx coding. To know if getting me past my 4 links is plausible is my main question. What's holding me back? Okd technology? Thank for the 8 and above quote!!!!

The number of links in an AE bundle supported vary by platform. But should scale beyond 4.  Also, if you mean number of AEs that set via a cli command and goes past 8. 

I'm kind of confused on what your concerns are, can you state platform and config bits?

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

I havve worked with MLT, SMLT and R-SMLT in Avaya switches in the past. As Extreme Networks bought the Avaya networking part, they also own the MLT technology. MLT is equivalent to LG, or aggregated Ethernet as Juniper calls it. You can run LACP over MLT/SMLT if you like, making it fully compatible with a normal LAG using LACP, or do without LACP, making it a static LAG.

In the SRX, you have these limitations:

"For SRX4600 and SRX5000 line of devices, a redundant Ethernet interface LAG can have up to eight links per redundant Ethernet interface per node "

"For SRX300 Series, SRX1500, SRX1600, SRX2300, SRX4100/SRX4200, and SRX4300 devices, a redundant Ethernet interface LAG can have up to maximum four links per redundant Ethernet interface per node"

https://www.juniper.net/documentation/us/en/software/junos/chassis-cluster-security-devices/topics/topic-map/security-chassis-cluster-redundant-ethernet-lag-interfaces.html

If you only have one interface in a reth (redundant Ethernet) per node, it is not a LAG and, cannot run LACP. If you have two interfaces per node or more, they form a LAG and can run LACP. This is not commonly known and makes extending the number of links from one to two or more a bit complicated. I'd have preferred to be able to create a one port LAG with LACP so I had the flexibility to just add member interface to the LAG in the switch where I connect the SRX, but you need to rebuild it. Once you have two or more interface, you can just add more in the LAG of course.

"When at least two physical child interface links from each node are included in a redundant Ethernet interface configuration, the interfaces are combined within the redundant Ethernet interface to form a redundant Ethernet interface LAG." (same link as above).

Steve: 16 members are allowed in "aggregated Ethernet", but I suspect Eugene (OP) wants reth, not ae in this case.

I am only worried about how SRX Series supports my multilink trunks in my avaya switch cluster. The need to try to extend my trunks through these SRX's is my goal for now. The link I gave is the BASE for the technology. I realize that how my avaya cluster communicates with other devices is out of the scope here, but I haven't chosen to extend alot of srx work beyond subsystem coding. Thus is why I'm seeking srx coding. To know if getting me past my 4 links is plausible is my main question. What's holding me back? Okd technology? Thank for the 8 and above quote!!!!

The number of links in an AE bundle supported vary by platform. But should scale beyond 4.  Also, if you mean number of AEs that set via a cli command and goes past 8. 

I'm kind of confused on what your concerns are, can you state platform and config bits?

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

I havve worked with MLT, SMLT and R-SMLT in Avaya switches in the past. As Extreme Networks bought the Avaya networking part, they also own the MLT technology. MLT is equivalent to LG, or aggregated Ethernet as Juniper calls it. You can run LACP over MLT/SMLT if you like, making it fully compatible with a normal LAG using LACP, or do without LACP, making it a static LAG.

In the SRX, you have these limitations:

"For SRX4600 and SRX5000 line of devices, a redundant Ethernet interface LAG can have up to eight links per redundant Ethernet interface per node "

"For SRX300 Series, SRX1500, SRX1600, SRX2300, SRX4100/SRX4200, and SRX4300 devices, a redundant Ethernet interface LAG can have up to maximum four links per redundant Ethernet interface per node"

https://www.juniper.net/documentation/us/en/software/junos/chassis-cluster-security-devices/topics/topic-map/security-chassis-cluster-redundant-ethernet-lag-interfaces.html

If you only have one interface in a reth (redundant Ethernet) per node, it is not a LAG and, cannot run LACP. If you have two interfaces per node or more, they form a LAG and can run LACP. This is not commonly known and makes extending the number of links from one to two or more a bit complicated. I'd have preferred to be able to create a one port LAG with LACP so I had the flexibility to just add member interface to the LAG in the switch where I connect the SRX, but you need to rebuild it. Once you have two or more interface, you can just add more in the LAG of course.

"When at least two physical child interface links from each node are included in a redundant Ethernet interface configuration, the interfaces are combined within the redundant Ethernet interface to form a redundant Ethernet interface LAG." (same link as above).

Steve: 16 members are allowed in "aggregated Ethernet", but I suspect Eugene (OP) wants reth, not ae in this case.

I am only worried about how SRX Series supports my multilink trunks in my avaya switch cluster. The need to try to extend my trunks through these SRX's is my goal for now. The link I gave is the BASE for the technology. I realize that how my avaya cluster communicates with other devices is out of the scope here, but I haven't chosen to extend alot of srx work beyond subsystem coding. Thus is why I'm seeking srx coding. To know if getting me past my 4 links is plausible is my main question. What's holding me back? Okd technology? Thank for the 8 and above quote!!!!

The number of links in an AE bundle supported vary by platform. But should scale beyond 4.  Also, if you mean number of AEs that set via a cli command and goes past 8. 

I'm kind of confused on what your concerns are, can you state platform and config bits?

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

A slight correction: In recent Junos releases, it is sufficient with only one interface per node in a reth to make it a LAG and run LACP on it. I just tried this in an SRX1600 cluster running 23.4R2-S2.

set interfaces xe-0/2/0 ether-options redundant-parent reth1
set interfaces xe-7/2/0 ether-options redundant-parent reth1
set interfaces reth1 vlan-tagging
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 redundant-ether-options lacp active
set interfaces reth1 redundant-ether-options lacp periodic fast

I think this change may have come in Junos 22 somewhere.

I havve worked with MLT, SMLT and R-SMLT in Avaya switches in the past. As Extreme Networks bought the Avaya networking part, they also own the MLT technology. MLT is equivalent to LG, or aggregated Ethernet as Juniper calls it. You can run LACP over MLT/SMLT if you like, making it fully compatible with a normal LAG using LACP, or do without LACP, making it a static LAG.

In the SRX, you have these limitations:

"For SRX4600 and SRX5000 line of devices, a redundant Ethernet interface LAG can have up to eight links per redundant Ethernet interface per node "

"For SRX300 Series, SRX1500, SRX1600, SRX2300, SRX4100/SRX4200, and SRX4300 devices, a redundant Ethernet interface LAG can have up to maximum four links per redundant Ethernet interface per node"

https://www.juniper.net/documentation/us/en/software/junos/chassis-cluster-security-devices/topics/topic-map/security-chassis-cluster-redundant-ethernet-lag-interfaces.html

If you only have one interface in a reth (redundant Ethernet) per node, it is not a LAG and, cannot run LACP. If you have two interfaces per node or more, they form a LAG and can run LACP. This is not commonly known and makes extending the number of links from one to two or more a bit complicated. I'd have preferred to be able to create a one port LAG with LACP so I had the flexibility to just add member interface to the LAG in the switch where I connect the SRX, but you need to rebuild it. Once you have two or more interface, you can just add more in the LAG of course.

"When at least two physical child interface links from each node are included in a redundant Ethernet interface configuration, the interfaces are combined within the redundant Ethernet interface to form a redundant Ethernet interface LAG." (same link as above).

Steve: 16 members are allowed in "aggregated Ethernet", but I suspect Eugene (OP) wants reth, not ae in this case.

I am only worried about how SRX Series supports my multilink trunks in my avaya switch cluster. The need to try to extend my trunks through these SRX's is my goal for now. The link I gave is the BASE for the technology. I realize that how my avaya cluster communicates with other devices is out of the scope here, but I haven't chosen to extend alot of srx work beyond subsystem coding. Thus is why I'm seeking srx coding. To know if getting me past my 4 links is plausible is my main question. What's holding me back? Okd technology? Thank for the 8 and above quote!!!!

The number of links in an AE bundle supported vary by platform. But should scale beyond 4.  Also, if you mean number of AEs that set via a cli command and goes past 8. 

I'm kind of confused on what your concerns are, can you state platform and config bits?

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.

Thanx for the replies...

The reason I am asking is because I have implemented a multilink trunk set but the documentation provides descriptions for links for up to  8 ports. I FEAR that due to my limitations that I cannot increase past 4 ports. My thoughts are that I need to check if the routes are able to run properly, but that I can extend past the subsystem. Maybe I am wrong, and maybe a work around is necessary.

From what I can see here MLT is compatible with IEEE 802.3ad which is known as Aggregated Ethernet in the Juniper documentation

MLT history

https://en.wikipedia.org/wiki/Multi-link_trunking

Juniper SRX support for AE / LAG

https://supportportal.juniper.net/s/article/SRX-EX-Link-aggregation-LACP-supported-non-supported-configurations-on-SRX-and-EX?language=en_US

I would like to know how the SRX series gateway supports multilink trunking. I don't believe I have ever seen anything on this? Does anyone have commentary on this subject. Any code examples if they exist would be helpful as well. If I've read anything it had to have been very little.