Hello and welcome to this episode of Wired Assurance. We’ll talk about link aggregation with LACP or not. And my name is Abishan [inaudible]. I’m a part of the product management team. We’ll look at the Wired Assurance configuration template back again where all of the elements that are pertaining to any switch configuration start with. It’s under organization and switch templates. If you look at any of the templates, and you’re looking to actually configure link aggregation, how would you go about it? Any of the port configurations themselves are all performed under select switch configurations, which is at a template level. The same can be achieved at the site level with site and switch configuration, as well as individual switches as a hierarchical model. Every single configuration that is defined at the template is inherited by applying it to a bunch of sites. Each of these sites has switches under them who will inherit all of these templates.
At each of these layers, you’ll be able to make configuration changes or overrides, as we call them, if required on a particular site. Let’s take in this particular example as to how do we configure link aggregation. Link aggregation, primarily used as up links to a particular interface. In a use case, if it is a access switch, if you’re up linking to a distribution switch, how would you actually have a link aggregation in place? And you could also decide if you’d like to do LACP or not. If it is an exit port that you are combining the configuration where you’re having a combination of ports and you would want to call it the up link port profile, which is the first thing that you would create, which may be you allowing all up links or all VLANs or whatever the choice may be that you would’ve defined in your port profiles in here, up link port profile in this example is a trunk port with a native VLAN of VLAN two and all of the other networks allowed.
So that was just an example, and it could be anything that is dependent on your particular network. Now, you have combined ports XC 0 0, XC 1 0 1 and 1 0 2. You’d like for it to be a link aggregated port, connecting two more ports on the other end to your distribution switch. The way you would achieve that is you would click on the port aggregation button. There is also options for you to disable LACP if the other side does not actually speak LACP by default, we can choose the A index as it’s called aggregated ethernet index as it is called. It’s also just ethernet channel or code channel numbers that we use for aggregation on each of these devices. By default, we populate the numbers for you. If you’d like to have a particular choice, you can always put them in here. Now you could have a host of different kinds of devices that are there and it could all have the same kind of uplinks. You could always add port ranges, allow them and apply them based on a switch role. Now you could apply the switch role on a per switch basis. Now let’s go into the switches themselves and let’s see how it looks like from a switch front panel perspective.
In this example, this is one of the switches which has the role of live demo. Live demo is one of the switches that is incorporated. Subsequently, we can also look at some of the other switches that are on the network. In this example, if this one is a 4400 access 1 device. Now in this example on this particular switch, you can see ports gig 0 0 10 and 0 0 11 have been made port aggregation. You could see the port aggregation is enabled and you have specifically pointed that the link aggregation index needs to be one. Now let’s go in and dig in as to what those two ports indicate as in the front panel. As soon as you would see the aggregated interfaces actually do have a halo around them and they’re purple in color. Both 0 0 10 and 0 0 11 have a similar construct. If you also, on Howard, you would see that aggregated ethernet index is a one in this particular case and it has a port mode of trunk and it also is a profile of ac.
And on the other end, there’s a core device that is sitting and that’s what the peer device notification at the bottom half of the, however, that showcases E V P N 4,400 core one and it’s IP address on the other side as so on. So if you scroll down, gig 1 0 0 11 also is part of the same LACP interface. Granted it’s down, but whenever that interface comes up, you would see these student faces bundle in together for to formal link aggregation. So as you saw, link aggregation can be done at the template level. It could be further inherited at the site as well as the individual switches. And if you’d like to override, we can all always have, we can provide an option for the same.
If you’re somebody who’s interested as to how this looks like underneath, you can show LACP interfaces and then you would see that LACP interface is a one. The port that is up is collecting and distributing, which is what you would want to see. Port 11 is detached, but it is because of port, there’s no real interface connected. But we’ve tried in bundle these two ports together and that is how you would create link aggregation with wire assurance with a quick couple of buttons in there for you to enable port aggregation. Hopefully this was useful and thank you for listening.