Restart Network Services

Master
Setup linux!
1
Introduction
2
Understanding Containers
3
ACI Access Policies
4
VMware Domain Definition
5
Linux Host Setup
6
ACI Kubernetes
7
Configure VMware Integration
8
Initialize Kubernetes
9
Deploy Applications
10
Conclusion
11
Reference

Step 1 - Restart network service on Master Node

Now that all the underlying infrastructure on VMware is built, you can restart the network service on all three VM's such that they can conclude the setup and DHCP process into the ACI fabric.


systemctl restart network

Once the process has restarted it is important to verify that the sub-interfaces on ens224 have received their correspondence IP DHCP lease. We will be checking for the following interfaces:

  • ens224.3109 which is the sub-interface for the k8s nodes to communicate between eachother.
  • ens224.3967 which is the OpFlex interface.

    
        ip a | grep ens224 | grep 10      
    
    
[root@pod09-master ~]# ip a | grep ens224 | grep 10
3: ens224:  mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    10: ens224.3109@ens224:  mtu 9000 qdisc noqueue state UP group default qlen 1000
        inet 
            10.0.144.XXX/29 brd 10.0.144.XXX scope global ens224.3109
        
        11: ens224.3967@ens224:  mtu 1600 qdisc noqueue state UP group default qlen 1000
            inet 
                10.9.200.XXX/16 brd 10.9.255.255 scope global dynamic ens224.3967
            

Step 2 - Restart network service on Node 1


systemctl restart network

    
        ip a | grep ens224 | grep 10      
    
    
[root@pod09-master ~]# ip a | grep ens224 | grep 10
3: ens224:  mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    10: ens224.3109@ens224:  mtu 9000 qdisc noqueue state UP group default qlen 1000
        inet 
            10.0.144.XXX/29 brd 10.0.144.XXX scope global ens224.3109
        
        11: ens224.3967@ens224:  mtu 1600 qdisc noqueue state UP group default qlen 1000
            inet 
                10.9.200.XXX/16 brd 10.9.255.255 scope global dynamic ens224.3967
            

Step 3 - Restart network service on Node 2


systemctl restart network

    
        ip a | grep ens224 | grep 10      
    
    
[root@pod09-master ~]# ip a | grep ens224 | grep 10
3: ens224:  mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    10: ens224.3109@ens224:  mtu 9000 qdisc noqueue state UP group default qlen 1000
        inet 
            10.0.144.XXX/29 brd 10.0.144.XXX scope global ens224.3109
        
        11: ens224.3967@ens224:  mtu 1600 qdisc noqueue state UP group default qlen 1000
            inet 
                10.9.200.XXX/16 brd 10.9.255.255 scope global dynamic ens224.3967