The image above shows a link aggregation group between two switches. The reason we use Link Aggregation Groups (LAGs) are they allow you to combine multiple network physical connections to make a single higher load sharing bandwidth path thus increase the throughput beyond what a single connection could support, and also to provide redundancy incase one of the links should fail.
You can read on how to configure LAG’s on Ruckus Switches here:
Ruckus : Configure Link Aggregation Groups
This is how to build a Link Aggregation Group on the Ruckus 7150. It is slightly different on the 7250’s.
Configure the Link Aggregation Group. There are multiple LAG types and they must match on both sides of the lag, other vendors may use different names for the same thing here are the common ones:
|Ruckus LAG Types
||Other Vendor Types
Configure a static LAG.
tpwsw1(config)# lag <name-of-the-lag> static id 1
Configure a dynamic LAG.
tpwsw1(config)# lag <name-of-the-lag> dynamic id 1
The LAG ID can be automatically generated and assigned to a LAG using the auto option.
tpwsw1(config)# lag <name-of-the-lag> dynamic id auto
The Link Aggregation Group IDs are unique for each LAG on the switch. The LAG ID can’t be assigned to more than one LAG. If a LAG ID is already used, the CLI will reject the new LAG configuration and display an error message that suggests the next available LAG ID that can be used.
Once the LAG is built you have to add ports to the LAG.
tpwsw1(config-lag-<name-of-the-lag>)# ports ethernet 1/2/7 ethernet 1/2/8
I am home! I have been travelling for work for the best part of the past 5 weeks. I was in Boston doing a network refresh the week before Easter, which included replacing all the network cables, installing new Palo Alto Firewalls and removing Cisco ASA’s. I also removed all Cisco Switches and installed a new stack of Ruckus 7250, replace the core switches with 2 new Arista’s. I then came home for 2 days and I left again for Singapore for 3 weeks. I was in Singapore integrating a new company we bought into our network, this was a team effort as we had other sites to bring online within 48 hours. Copenhagen and a small site in Kaohsiung, Taiwan. I have learned a lot over the past 2 month. I have some articles to write on what I have learned but for now, I just wanted to give a quick update. Here is some cable porn from the Boston Network Refresh.
Today, I officially start the CCNP Route Switch Course.
I have purchased the following book set, I have provided a link if you wish to purchase them:
I am also using Chris Bryant’s Video Udemy Course (Who helped me pass the CCNA R&S and Security, very thorough video series) and I will try and get his books. I have provided a link if you wish to purchase them :
I plan to have passed the CCNP Switch by July, because I have some pretty big work trips coming up and I know that is going to get in the way a little. However the 18hr flight to Singapore, I should be able to get through a power of reading and labs 🙂
I will start to blog on my progress and things I am learning.
Wish me Luck!