Does anyone happen to know the LACP hello interval on a CN5160?
I've been really side tracked from here. Here is an example of the ciena side of the Config:
! saos-06-15-00-0331! Note: these steps may not be in the exact order.
vlan create vlan 4091-4092
interface remote set vlan 4092interface remote set ip (IPv4-addr)/32 priority 6 !Note: nertmask is whatever you are using /25 maybe.
!DISABLE ACL befreo creating an AGG interface. Then ENA it adfter everyhting is UPinterface ip-acl DISABLE
!I Disable the Local I/F:interface local disable
aggregation create agg ae4aggregation add agg ae4 port 2.1aggregation add agg ae4 port 2.2aggregation add agg ae4 port 3.1aggregation add agg ae4 port 3.2!-OR-agg add agg ae4 port 2.1,2.2,3.1,3.2
vl add vl 4091,4092,127 po ae4
aggregation set port 2.1 timeout shortaggregation set port 2.2 timeout shortaggregation set port 3.1 timeout shortaggregation set port 3.2 timeout shortaggregation set agg ae4 hash ip-addr-based
! I did these, you may or may not need them:port set port 2.1 egress-frame-cos-policy rcos-to-l2-outer-pcp-map max-frame-size 9130 description " xe-3/3/3"port set port 2.2 egress-frame-cos-policy rcos-to-l2-outer-pcp-map max-frame-size 9130 description " xe-3/3/1"port set port 3.1 egress-frame-cos-policy rcos-to-l2-outer-pcp-map max-frame-size 9130 description " xe-4/3/3"port set port 3.2 egress-frame-cos-policy rcos-to-l2-outer-pcp-map max-frame-size 9130 description " xe-4/3/1"
vlan add vlan 4092 port 2.1vlan remove vlan 127,1 port 2.1vlan add vlan 4091 port 2.2vlan remove vlan 1 port 2.2vlan remove vlan 127 port 3.1vlan remove vlan 127 port 3.2vlan add vlan 4091-4092 port ae4vlan remove vlan 1 port ae4
Which software version are you running?
First, look at the Juniper side of the equation to find what is set on the LACP interface:
"> show lacp interfaces ae4 "
And from the Ciena side of things, use the LLDP show commnd to find the ports in the AGG.
"> lldp sh neighbors "
These port numbers should resolve to the LACP interface ports on the Juniper LAG side.
From ciena, find the port info and stats:
> agg show agg ae4
In my instance, I'm using a CN5150, with an AGG port named 'ae4". It contains four XE ports.
Looking at the primary port on the Juniper, I find it has set to the "fast" timeout interval.
"> show lacp interfaces xe-3/3/3 "
The Juniper LACP TX and RX counters should be incremening periodically, in an even count fashion.
The Juniper (and Cisco) timers can be set to either "rate fast" - 1 second, or "rate normal" - 30 seconds.
If you need Fast, set it accordingly in Juniper. I believe Ciena will follow suit.
You must all ensure the MTU is the same on both ends of the AGG tunnel, and on the PHY ports, in case the AGG falls apart.
Thanks for this info, awesome stuff, but your suggestions might be putting the cart before the horse as we haven't created the LAG groups or assigned interfaces yet. This is our first time setting up LAG/LACP on Ciena and on Juniper. Would you happen to have an example of how you configured LAG/LACP on both sides of this equation (Ciena & Junier) that you wouldn't mind sharing.
I had intended to use the example on pg 13-23 of the SAOS_6.15 Advanced Ethernet Config guide to set up LAG/LACP on the CN5160, which seems to be pretty straight forward.
As we are fairly new to Juniper products, so I was going to follow the example for configuring LACP in a Juniper security device provided below to set up LAG/LACP on our SRX345
Example: Configuring Link Aggregation Control Protocol on aSecurity Device (CLI Procedure) - Technical Documentation - S…
The info you provided regarding "fast rate" & "normal rate" and how Ciena should follow suite is extremely helpful as that was where I was getting bogged down on the Juniper config. I couldn't find any corresponding info w/ regards to fast or normal rate (or any timers for that matter) in the Ciena config or any info that indicates that Ciena will follow suite other than a brief statement in the previously mentioned Advanced Ethernet guide an how the Ciena device handles LACP communications with another device.
"Traditionally, network administrators had to configure parameters such as Actor Admin Keys, Operational keys, and collector max delay. In the Ciena implementation, all of these parameters are handled behind the scenes. After a LAG has been created on one device and ports are added, it will look for eligible ports on its peer to aggregate with. It doesn’t matter if the two LAGs have the same configurations as their peer, as long as the groups are valid they will find each other and negotiate an aggregation"
Any info you could provide would be greatly appreciated.
Ok John. I guess I thought things were previously provisioned.
I’ll read over the Ciena references you’ve provided and give you more feedback tomorrow.
Creating the agg itself on both devices is straight forward. At least to me it is.
In the real world, the two devices are required to be physically connected, with both Oper and Admin UP, and in the same management VLAN ID. Which is either, 1 - not recommended, 127, also not recommended, and 4072 which is the ordinary ID, and 4071 as the secondary ur backup/fall back MGNT VID. Note: DO NOT assign. 4072 to more the the first (primary) phy port in the AGG. AGGs can be 1, 2, 3, or 4 ports.
Either 1gig or 10gig ports. But cannot with them.
I’ll forward a case agg config tomorrow.
Sent from my iPhone
Thanks for the example, this seems pretty straight forward.
Regarding VLANs, if only 1 VLAN is on an interface and I would like to create a LAG with that interface and an additional interface to increase throughput capabilities, does the VLAN need to be assigned to the second interface as well as the LAG?
Yes. On the Ciena side, use the ‘vlan add’ command fir the pri Agg port and on the virtual agg port.
On the juniper side, add the clans as sub-ports to the main agg interface.
I’ll post screen shots later this afternoon.
I mos-read your last question. No. The Management VLAN should only be assigned to the Primary physical port of the AGG, the the virtual AGG port itself. This is to prevent STP loops. Use a second VLAN on the second Physical port of the AGG. Then add this second vlan to the agg as well. While constructing trhe AGG, do NT enable IP-ACL on the device until after you have verified your LINKs and AGG is UP/UP.
For example, this is my AGG port.
My config looks like this:
Retrieving data ...