In this section, we will be creating the Endpoint Security Group (ESG) use case where end points will be able to communicate without the need of creating a contract between the aci_p01_epg_web and aci_p01_epg_app.
Below is the logical representation of POD01 leveraging ESG with the name aci_p01_esg.
In this step, we will be removing the contract created in the previously section:
Verify POD01-WEB-SRV-01 can not ping POD01-APP-SRV, do not proceed if ping is succesful
ping 172.16.1.2 -c 3
root@pod01-web-srv-01 ~]#ping 172.16.1.2 -c 3 PING 10.0.144.1 (172.16.1.2) 56(84) bytes of data. --- 172.16.1.2 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms root@pod01-web-srv-01 ~]#
In this step we will be naming our ESG, attaching it to the VRF and provide the necessary selector to be able to make sure devices in different EPGs will be able to communicate.
Configure the ESG by:
If you closed the window to then click on the ICON to the left to connect
and verify the ESG. You will be using the same browser SSH client you are going to click on the ICON on the left to
connect to this linux server. Username:root
and Password:cisco.123
After you have submitted the changes, verify POD01-WEB-SRV-01 can ping POD01-APP-SRV
ping 172.16.1.2 -c 3
root@pod01-web-srv-01 ~]#ping 172.16.1.2 -c 3 PING 172.16.1.2 (172.16.1.25) 56(84) bytes of data. 64 bytes from 172.16.1.2: icmp_seq=1 ttl=63 time=0.162 ms 64 bytes from 172.16.1.2: icmp_seq=2 ttl=63 time=0.156 ms 64 bytes from 172.16.1.2: icmp_seq=3 ttl=63 time=0.158 ms --- 172.16.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.156/0.158/0.162/0.014 ms
To continue to the next section of the lab is important to the remove aci_p01_esg