Hello sir, We did exactly the way you shown. But when we down connection of both of the ports.. in cmd(windows) it shown timed out. We up the connection then check again and it was still showing requested time out.? Pls help
It sounds like you're experiencing issues with NIC Teaming, specifically when both ports are down, and the connection doesn't recover as expected when the ports are brought back up. Let's troubleshoot the issue: ### Possible Causes and Solutions 1. **NIC Teaming Mode Configuration:** - **Switch Independent Mode**: If you're using this mode, the team should function even if the connection to one of the NICs is lost. However, if both NICs are down, there won't be any network connectivity. - **Switch Dependent Mode (LACP or Static)**: In this mode, both NICs work together with the switch. If the switch configuration or NIC settings are incorrect, you might experience timeouts. - **Solution**: Ensure that your NIC Teaming mode is correctly configured based on your network setup. If using LACP, ensure the switch is properly configured for LACP as well. 2. **Network Adapter Drivers:** - Outdated or incompatible drivers can cause issues with NIC Teaming. - **Solution**: Update the drivers for your network adapters to the latest version provided by the manufacturer. 3. **Team Interface IP Configuration:** - **IP Addressing**: Ensure that the IP address configuration on the teamed interface is correct. If using static IPs, make sure they don't conflict with other devices on the network. - **Solution**: Verify the IP settings, and if using DHCP, ensure that the DHCP server is functioning properly. 4. **Teaming Interface Settings:** - **Teaming Interface Status**: After the NICs are brought back online, the teaming interface might not recover automatically. - **Solution**: Disable and re-enable the NIC Teaming interface manually, or run `ipconfig /release` followed by `ipconfig /renew` to refresh the IP configuration. 5. **Windows Firewall or Security Software:** - Sometimes, security software or firewall settings can interfere with NIC Teaming. - **Solution**: Temporarily disable the firewall or security software to see if it resolves the issue. 6. **Physical Layer Issues:** - **Cabling and Switch Ports**: Check the cables and switch ports connected to the NICs. A faulty cable or port can cause the team to fail. - **Solution**: Test the cables and switch ports with different devices to ensure they are working properly. 7. **Persistent Route Configuration:** - If your team is set up with specific routes, ensure these routes persist after the NICs go down and come back up. - **Solution**: Check the routing table with `route print` and ensure no conflicting or missing routes. ### Steps to Test: 1. **Bring Both NICs Back Up**: If the NICs are up and you're still seeing timeouts, disable and then re-enable the NIC Teaming interface in the Network and Sharing Center or Device Manager. 2. **Check IP Configuration**: Run `ipconfig /all` to ensure that the teamed interface has the correct IP configuration. 3. **Ping Test**: Ping the default gateway or another known working device on the network to test connectivity. 4. **Review Event Logs**: Check Windows Event Logs for any errors or warnings related to network connectivity or NIC Teaming. If after these steps you're still facing issues, let me know what specific NIC Teaming mode you're using and any additional network details. This will help me provide more targeted advice.
Hi Sir, Namaskar🙏. I see you have here 3 NICs ens160 and later you added ens192 and ens224. When I'm having 3 NIC's in my VM, then teaming is working fine, in teaming I'm including only two i.e. ens192 & ens224 . While when I have only 2 NIC's i.e. ens160, and ens192 only. Then teaming is not working properly, I mean when I am running "ip link set dev ens160/ens192 down" it's not working. Sir any idea why it's not working with only two NIC's .
Hello sir, I have configured bonding on oracle linux 7.9 .. everything looks good , interfaces shows as connected but gateway and server ip are not pinging...Is there any network service restart needed? This is physical server.. And we are using same gw ip for two bonds..will that work? Or seperate gw is needed? Please guide Thank you
It sounds like you’ve done a great job configuring network bonding on Oracle Linux 7.9, but there are a few details to address to ensure everything works correctly. Here’s a guide to troubleshoot and address your issues: ### 1. **Verify Bonding Configuration** 1. **Check Bonding Status:** Ensure that the bonding interface is correctly configured and active: ```bash cat /proc/net/bonding/bond0 ``` Replace `bond0` with your actual bonding interface name if different. This command will show the status of the bonding interface and its slave interfaces. 2. **Verify Configuration Files:** - Check your bonding configuration in `/etc/sysconfig/network-scripts/ifcfg-bond0` (or similar). Ensure that the configuration is correct, including the bonding mode and any additional options. Example of a basic `/etc/sysconfig/network-scripts/ifcfg-bond0` configuration: ```bash DEVICE=bond0 NAME=bond0 BONDING_OPTS="mode=1 miimon=100 updelay=200 downdelay=200" IPADDR=192.168.1.10 NETMASK=255.255.255.0 GATEWAY=192.168.1.1 ONBOOT=yes BOOTPROTO=none ``` - Also, verify the configuration of the individual slave interfaces, ensuring they have `MASTER=bond0` and `SLAVE=yes` settings. ### 2. **Restart Network Services** Yes, you usually need to restart the network service for changes to take effect: ```bash sudo systemctl restart network ``` Or, if you are using `NetworkManager`: ```bash sudo systemctl restart NetworkManager ``` ### 3. **Check IP Configuration** Ensure that your IP addresses and gateway are correctly configured. You can use the `ip` command to check the current IP configuration: ```bash ip addr show ip route show ``` ### 4. **Verify Gateway Configuration** Using the same gateway IP for multiple bonds can work, but it depends on your network setup and requirements. Typically, each bond or network segment should have its own gateway unless it’s a highly specialized setup. Here are some considerations: - **Single Gateway:** If you have multiple bonds but only one gateway, ensure that the gateway is properly configured and reachable from all bonds. - **Separate Gateways:** If possible, configure separate gateways for each bond to avoid routing issues. ### 5. **Check for Network Issues** 1. **Ping Local Interface:** Ping the local interface IP address to verify that the bonding interface is correctly handling traffic: ```bash ping 192.168.1.10 ``` 2. **Ping Gateway:** Check if the gateway is reachable from the bonded interface: ```bash ping 192.168.1.1 ``` 3. **Check for Errors:** Look at the system logs for any network-related errors: ```bash journalctl -xe dmesg | grep -i bond ``` ### 6. **Consider Network Topology** Ensure that the switch or network device to which the bonded interfaces are connected is correctly configured for bonding (if using LACP, for instance). Mismatches in configuration can cause connectivity issues. ### 7. **Testing and Verification** - **Test with a Single Bond:** Temporarily disable one of the bonds and test connectivity with just one bond to verify that it works. - **Check Link Status:** Verify that all physical links are up and properly connected. By following these steps, you should be able to troubleshoot and resolve the connectivity issues with your bonded interface. If you still encounter problems, providing more details about your network configuration and setup might help in diagnosing the issue further.
i have centos 7 on laptop command base no graphical issue is any reason router is off or restart router or remove cable for lan card and reconnect not coming up even i give manual ip also same until restart centos 7 or manual command given like this i want know what is issue please give some solution
Sirji how can we implement linux bridge using 'brctl' command (not nmcli command) in vmware workstation. No proper/appropriate video found in youtube. I read d documentation from /usr/share/doc/bridge-utils/HOWTO n know d concept(2 network adapters/intetfaces/ethernets should have d same ip series however adding same 2 nat adapters or same 2 hostonly adapters n same ip range on d 2 network adapters on same linux machine cannot be bridge)but I can't implement in vmware (as well as oracle virtual box) due to network adapter configuration problem as follow A(vmnet1/hostonly)(vmnet1/hostonly)B(vmnet5custom/hostonly)(vmnet5custom/hostonly)C. vmnet1 is one segment of lan vmnet5 is another same segment of lan Both vmnet1 n vmnet5 must have d same ip range.This is d concept of bridge ABC However in B vmnet1 n vmnet5 can't have same ip range(not allowed by vmware). If manually made same range ip in B by ifconfig or ip command, either B can ping to A but not to C or B can ping to C but not to A. Same is d case for virtual box( NAT NAT Network Bridged Adapter Internal Network Host-Only Adapter) setting Please suggest ideas how to do linux bridge in virtual environment using brctl command. If we made B as router( ip forward mode n vmnet1 n vmnet5 have different ip series), then B can ping both to A n C. A can also connect to C after adding vmnet1 ip of B as gateway ip in A; C can also connect to A after adding vmnet5 ip of B as gateway ip in C. Please make a video. For kind info
Thanking for your video. I have done it. Very helpfull.
Thank you sir so much
Very useful session Sir Thank you so much
Started following your playlist neat and cool
Hello sir,
We did exactly the way you shown.
But when we down connection of both of the ports.. in cmd(windows) it shown timed out. We up the connection then check again and it was still showing requested time out.?
Pls help
It sounds like you're experiencing issues with NIC Teaming, specifically when both ports are down, and the connection doesn't recover as expected when the ports are brought back up. Let's troubleshoot the issue:
### Possible Causes and Solutions
1. **NIC Teaming Mode Configuration:**
- **Switch Independent Mode**: If you're using this mode, the team should function even if the connection to one of the NICs is lost. However, if both NICs are down, there won't be any network connectivity.
- **Switch Dependent Mode (LACP or Static)**: In this mode, both NICs work together with the switch. If the switch configuration or NIC settings are incorrect, you might experience timeouts.
- **Solution**: Ensure that your NIC Teaming mode is correctly configured based on your network setup. If using LACP, ensure the switch is properly configured for LACP as well.
2. **Network Adapter Drivers:**
- Outdated or incompatible drivers can cause issues with NIC Teaming.
- **Solution**: Update the drivers for your network adapters to the latest version provided by the manufacturer.
3. **Team Interface IP Configuration:**
- **IP Addressing**: Ensure that the IP address configuration on the teamed interface is correct. If using static IPs, make sure they don't conflict with other devices on the network.
- **Solution**: Verify the IP settings, and if using DHCP, ensure that the DHCP server is functioning properly.
4. **Teaming Interface Settings:**
- **Teaming Interface Status**: After the NICs are brought back online, the teaming interface might not recover automatically.
- **Solution**: Disable and re-enable the NIC Teaming interface manually, or run `ipconfig /release` followed by `ipconfig /renew` to refresh the IP configuration.
5. **Windows Firewall or Security Software:**
- Sometimes, security software or firewall settings can interfere with NIC Teaming.
- **Solution**: Temporarily disable the firewall or security software to see if it resolves the issue.
6. **Physical Layer Issues:**
- **Cabling and Switch Ports**: Check the cables and switch ports connected to the NICs. A faulty cable or port can cause the team to fail.
- **Solution**: Test the cables and switch ports with different devices to ensure they are working properly.
7. **Persistent Route Configuration:**
- If your team is set up with specific routes, ensure these routes persist after the NICs go down and come back up.
- **Solution**: Check the routing table with `route print` and ensure no conflicting or missing routes.
### Steps to Test:
1. **Bring Both NICs Back Up**: If the NICs are up and you're still seeing timeouts, disable and then re-enable the NIC Teaming interface in the Network and Sharing Center or Device Manager.
2. **Check IP Configuration**: Run `ipconfig /all` to ensure that the teamed interface has the correct IP configuration.
3. **Ping Test**: Ping the default gateway or another known working device on the network to test connectivity.
4. **Review Event Logs**: Check Windows Event Logs for any errors or warnings related to network connectivity or NIC Teaming.
If after these steps you're still facing issues, let me know what specific NIC Teaming mode you're using and any additional network details. This will help me provide more targeted advice.
Nice informative n useful session sirji
Hi Sir, Namaskar🙏.
I see you have here 3 NICs ens160 and later you added ens192 and ens224. When I'm having 3 NIC's in my VM, then teaming is working fine, in teaming I'm including only two i.e. ens192 & ens224 . While when I have only 2 NIC's i.e. ens160, and ens192 only. Then teaming is not working properly, I mean when I am running "ip link set dev ens160/ens192 down" it's not working. Sir any idea why it's not working with only two NIC's .
Hello sir, I have configured bonding on oracle linux 7.9 .. everything looks good , interfaces shows as connected but gateway and server ip are not pinging...Is there any network service restart needed? This is physical server..
And we are using same gw ip for two bonds..will that work? Or seperate gw is needed?
Please guide
Thank you
It sounds like you’ve done a great job configuring network bonding on Oracle Linux 7.9, but there are a few details to address to ensure everything works correctly. Here’s a guide to troubleshoot and address your issues:
### 1. **Verify Bonding Configuration**
1. **Check Bonding Status:**
Ensure that the bonding interface is correctly configured and active:
```bash
cat /proc/net/bonding/bond0
```
Replace `bond0` with your actual bonding interface name if different. This command will show the status of the bonding interface and its slave interfaces.
2. **Verify Configuration Files:**
- Check your bonding configuration in `/etc/sysconfig/network-scripts/ifcfg-bond0` (or similar). Ensure that the configuration is correct, including the bonding mode and any additional options.
Example of a basic `/etc/sysconfig/network-scripts/ifcfg-bond0` configuration:
```bash
DEVICE=bond0
NAME=bond0
BONDING_OPTS="mode=1 miimon=100 updelay=200 downdelay=200"
IPADDR=192.168.1.10
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
ONBOOT=yes
BOOTPROTO=none
```
- Also, verify the configuration of the individual slave interfaces, ensuring they have `MASTER=bond0` and `SLAVE=yes` settings.
### 2. **Restart Network Services**
Yes, you usually need to restart the network service for changes to take effect:
```bash
sudo systemctl restart network
```
Or, if you are using `NetworkManager`:
```bash
sudo systemctl restart NetworkManager
```
### 3. **Check IP Configuration**
Ensure that your IP addresses and gateway are correctly configured. You can use the `ip` command to check the current IP configuration:
```bash
ip addr show
ip route show
```
### 4. **Verify Gateway Configuration**
Using the same gateway IP for multiple bonds can work, but it depends on your network setup and requirements. Typically, each bond or network segment should have its own gateway unless it’s a highly specialized setup. Here are some considerations:
- **Single Gateway:** If you have multiple bonds but only one gateway, ensure that the gateway is properly configured and reachable from all bonds.
- **Separate Gateways:** If possible, configure separate gateways for each bond to avoid routing issues.
### 5. **Check for Network Issues**
1. **Ping Local Interface:**
Ping the local interface IP address to verify that the bonding interface is correctly handling traffic:
```bash
ping 192.168.1.10
```
2. **Ping Gateway:**
Check if the gateway is reachable from the bonded interface:
```bash
ping 192.168.1.1
```
3. **Check for Errors:**
Look at the system logs for any network-related errors:
```bash
journalctl -xe
dmesg | grep -i bond
```
### 6. **Consider Network Topology**
Ensure that the switch or network device to which the bonded interfaces are connected is correctly configured for bonding (if using LACP, for instance). Mismatches in configuration can cause connectivity issues.
### 7. **Testing and Verification**
- **Test with a Single Bond:** Temporarily disable one of the bonds and test connectivity with just one bond to verify that it works.
- **Check Link Status:** Verify that all physical links are up and properly connected.
By following these steps, you should be able to troubleshoot and resolve the connectivity issues with your bonded interface. If you still encounter problems, providing more details about your network configuration and setup might help in diagnosing the issue further.
Good morning Sir, Please provide script or line where activebackup , may use activeactive for active-active teaming
very beautifully explained..
Thanks 👍
thank u so much sir, for this valuable information.
Thanks a lot
Very nice
Thanks
Sir I have a doubt, what if master goes down on which the IP is assigned ?
Hi sir..do we have round robin bonding like rhel 6 here also?if yes how to do configure nic in round robin method
Rhel 6 is already outdated
Is this using LACP for bonding ?
i have centos 7 on laptop command base no graphical
issue is any reason router is off or restart router or remove cable for lan card and reconnect not coming up
even i give manual ip also same until restart centos 7
or manual command given like this i want know what is issue please give some solution
please contact us in our telegram group.
Sirji how can we implement linux bridge using 'brctl' command (not nmcli command) in vmware workstation.
No proper/appropriate video found in youtube. I read d documentation from /usr/share/doc/bridge-utils/HOWTO n know d concept(2 network adapters/intetfaces/ethernets should have d same ip series however adding same 2 nat adapters or same 2 hostonly adapters n same ip range on d 2 network adapters on same linux machine cannot be bridge)but I can't implement in vmware (as well as oracle virtual box) due to network adapter configuration problem as follow
A(vmnet1/hostonly)(vmnet1/hostonly)B(vmnet5custom/hostonly)(vmnet5custom/hostonly)C.
vmnet1 is one segment of lan
vmnet5 is another same segment of lan
Both vmnet1 n vmnet5 must have d same ip range.This is d concept of bridge
ABC
However in B vmnet1 n vmnet5 can't have same ip range(not allowed by vmware).
If manually made same range ip in B by ifconfig or ip command, either B can ping to A but not to C or B can ping to C but not to A.
Same is d case for virtual box(
NAT
NAT Network
Bridged Adapter
Internal Network
Host-Only Adapter) setting
Please suggest ideas how to do linux bridge in virtual environment using brctl command.
If we made B as router( ip forward mode n vmnet1 n vmnet5 have different ip series), then B can ping both to A n C. A can also connect to C after adding vmnet1 ip of B as gateway ip in A; C can also connect to A after adding vmnet5 ip of B as gateway ip in C.
Please make a video.
For kind info