Module 4
Advanced Networking using Network Manager
Setting Up Static Routing
Understanding Network Bridges
Setting Up Network Bridges
Understanding Network Teaming and Bonding
Configuring Network Teaming
Configuring IPv6
Advanced Networking
Configuring Static Route to different Network on Linux Box.
Static Route may be required when we need to reach to other network which the
default gateway can not reach.
Configuring Network Bridge interface will be required for virtualization environment.
Bridge Interface will allow the Virtual Machine to have access to external network.
To provide Bandwidth Availability , Redundancy and Load Balance so we need to
configure Link Aggregation or Network Teaming.
Getting IPv4 Address Range Exhausted so we need to configure IPv6 on Linux
Server.
nmcli Command:
To show all Devices:
# nmcli device show
To show the Active Connection:
# nmcli connection show –active
To disconnect Device and reconnect:
# nmcli device disconnect eno16777736
# nmcli device connect eno16777736
To create a connection:
# nmcli connection add con-name course ifname eno16777736 type Ethernet
To Modify a Connection:
# nmcli connection modify course [Link] [Link]/24 [Link]
[Link] [Link] [Link]
nmcli Command:
To Show the detailed information of the connection:
# nmcli –p connection show eno16777736
To show the Connected Devices:
# nmcli device status
Link Aggregation
The Availability to aggregate multiple Network links into one Link to increase the
Reachability , redundancy and load balancing on the level of the Network.
On CentOS 7 & RHEL 7 it is named as teaming while in Centos 6 & RHEL 6 is
bonding but Teaming is most effective than bonding.
There are many aggregation modes :
1- roundrobin :
is the default mode , it balances the load to all ports per network request.
2- broadcast :
All traffic will be sent over all ports.
3- active-backup :
One interface will be handling network requests while the other is in passive state
in case any failover changes.
Network Teaming
Install the team daemon :
# yum install –y teamd
Add the team interface:
# nmcli con add type team con-name team0 ifname team0 autoconnect yes config „ {
“runner” : { “name”: ”activebackup”} } ‟
Disconnect the physical interface and add it again to team0 :
# nmcli device disconnect eno16777736
# nmcli con add type team-slave ifname eno16777736 con-name team-eno1 master
team0
Assign IP Configuration to team0 interface:
# nmcli con up team0
# nmcli con mod team0 [Link] [Link]/24 [Link] [Link]
# nmcli con mod team0 [Link] manual
activate the slave interfaces:
# nmcli con up team-eno1
Network Teaming
We can specify the teaming mode by opening the configuration file :
# vim /etc/sysconfig/network-scripts/ifcfg-team0
TEAM_CONFIG=„ {“runner”: {“name”: “activebackup”}, “link_watch”: {“name”:
“ethtool”} } „
To verify :
# teamdctl team0 stat
Network Bridging
Is used in a virtualization Environment ( KVM ).
Is used to make the physical network interface card accessed by all
virtual machines.
Virtual Bridge interface will be created to link the VMs to the Physical
NIC of the host Server.
Network Bridging
Configuring Bridging
Install Related Package:
# yum install –y bridge-utils
Disconnect the current physical interface and add it to bridge:
# nmcli dev show
# nmcli dev disconnect eno167777736
Add the bridge interface:
# nmcli con add type bridge con-name br0 ifname br0 autoconnect yes
Connect the physical interface to the bridge:
# nmcli con add type bridge-slave con-name br0-nic ifname eno16777736
master br0
Finally To Verify the configuration:
# brctl show