Hello and welcome to this hands-on lab. Today we're doing remote peering. We've already done local peering. We actually did two local peering gateways, one in each VCN, and then we peer them together. We create our route and we're able to ping from this compute instance to this other compute instance. Then we also did a local peering connection using the DRG with enhanced services, where you can attach two VCNs to it. We basically did the same exercise, ping from this compute instance to this other compute instance. What we're doing right now is basically creating a VCN in another region, attaching it to a DRG that we will also be creating, and then do a remote peering connection, establish a route, and be able to ping from this compute instance in our current region where we have this VCN with the CIDR block, and then we will ping to the compute instance in this other VCN through the remote peering connection. Let's go ahead and do that. This is what we have so far. This is our DRG and as you can see, we attached two VCNs. What I want to bring to your attention here is that we don't have a remote peering connection attached. Let's go ahead and create one. We are going to name it 2Phoenix because that's the remote region that we're targeting. We're creating this attachment. Once this attachment is created, you can go ahead and click on it. This is the remote peering connection. We can establish a connection right now, but we don't have our matching resources in Phoenix. Let's go ahead and copy this OCID, we will need it shortly. Now let's go ahead to Phoenix. Here, I already created a VCN, I already created a DRG, the current remote DRG, the one in San Jose. I call that local, remember? Here, we don't have any remote peering connection attachment. We'll see in a minute, and we don't have the VCN attach either. Let's go ahead and attach a virtual Cloud network, which I know already exists because I already created it. This time, see how attachment name is optional. I'll leave it empty so you can see what happens. I'll select my VCN, which I labeled RemoteVCN, remote to San Jose. Now we have our VCN. As you can see, it automatically gave a name code, drgattachment, with today's date, and down to the hour. This is our VCN, it's attached. Let's go ahead and create a remote peering connection. This one I'm going to call it 2San Jose, California. We're creating the remote peering connection. It will appear here shortly. Well, it's attached. In attach, I can go in and click on my remote peering connection right here, and you see how it says establish a connection. I'm going to select to what region I'm going. I'm currently in Phoenix, so I'm going all the way down to San Jose, California. Here is where I'm going to paste matching because it's the remote peering connection. Now I will establish the connection. Right now, the peer status is pending. While it's doing that, let's go ahead and create a route table. I'm going to go into my VCN. I'm going to find my default route table. Here it is. I'm going to add a destination rule. What type I'm going to my dynamic routing gateway? My CIDR block in San Jose with one of my VCNs is 10.254.0.0/16. I'll leave the description empty. Now I have a route going from here to there. I can go into San Jose and do something similar. I'm using my demo, as you can see by the CIDR. This is the demo VCN, the one that I created with the wizard. I'm going to go to my default route table. This is the previous route for the local peering through the dynamic routing gateway. I'm going to add a route rule, select my dynamic routing gateway. My destination in this case is 192.168.0.0/16. Again, the description will be pending. Now let's go ahead and see the status of that remote peering connection. I'll go into my dynamic routing gateway. If you want to get to a resource quite fast, go ahead and type it. Here, I only type the initial letters. Here are the options. This case is dynamic routing gateway. If I open my local DRG and if I go to my remote peering connection, I'll go to the attachment, select mirror remote peering connection, and you should see that is attached and it's peered already. If I log in to my compute instance in San Jose, and if you recall from the compute instances I named them according to the VCN that they're in, so this is the one that I'm going to be logging in. Let's go ahead and do that, or association to it. Curiously public IP is matching, so I can go ahead and open this. In my counterpart in Phoenix, I call it Remote_VM. If I open it, you will see that the IP address is 192.168, so I should be able to ping that IP address right now. There it is.
