Creating and Managing Subnets Administrative Tasks

 

Creating a Subnet

To create a subnet using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which you want to create the subnet.

4. Click Subnets.

5. Click Create Subnet.

6. Enter the required information, such as the subnet name, CIDR block, and route table.

7. Click Create Subnet.

To create a subnet using the OCI CLI:

1. Run the following command:

oci subnet create --name <subnet_name> --cidr-block <cidr_block> --vcn-id <vcn_id> --route-table-id <route_table_id>

Managing Subnets

Once you have created a subnet, you can manage it using the OCI Console or the OCI CLI.

Using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which the subnet is located.

4. Click Subnets.

5. Click the name of the subnet that you want to manage.

6. Click Edit.

7. Make the desired changes to the subnet, such as the subnet name, CIDR block, or route table.

8. Click Save Changes.

Using the OCI CLI:

To manage a subnet using the OCI CLI, you can use the following commands:

Get subnet information:

oci subnet get --id <subnet_id>

Update subnet information:

oci subnet update --id <subnet_id> --name <subnet_name> --cidr-block <cidr_block> --route-table-id <route_table_id>

Delete subnet:

oci subnet delete --id <subnet_id>

OCI CLI Examples

Here are some examples of using the OCI CLI to create and manage subnets:

# Create a subnet

oci subnet create --name my-subnet --cidr-block 10.0.0.0/24 --vcn-id ocid1.vcn.oc1.iad.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

# Get subnet information

oci subnet get --id ocid1.subnet.oc1.iad.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

# Update subnet information

oci subnet update --id ocid1.subnet.oc1.iad.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa --name new-subnet --cidr-block 10.0.1.0/24

# Delete subnet

oci subnet delete --id ocid1.subnet.oc1.iad.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Creating and managing subnets is an important part of administering a VCN in OCI. You can use the OCI Console or the OCI CLI to create and manage subnets.

VCN Administrative Tasks

 

Creating a VCN

To create a VCN using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click Create VCN.

4. Enter the required information and click Create VCN.

To create a VCN using the OCI CLI:

1. Run the following command:

oci vcn create --name <vcn_name> --cidr-block <cidr_block> --compartment-id <compartment_id>

Creating a Subnet

To create a subnet using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which you want to create the subnet.

4. Click Subnets.

5. Click Create Subnet.

6. Enter the required information and click Create Subnet.

To create a subnet using the OCI CLI:

1. Run the following command:

oci subnet create --name <subnet_name> --cidr-block <cidr_block> --vcn-id <vcn_id>

Creating a Route Table

To create a route table using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which you want to create the route table.

4. Click Route Tables.

5. Click Create Route Table.

6. Enter the required information and click Create Route Table.

To create a route table using the OCI CLI:

1. Run the following command:

oci route-table create --name <route_table_name> --vcn-id <vcn_id>

Creating a Security List

To create a security list using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which you want to create the security list.

4. Click Security Lists.

5. Click Create Security List.

6. Enter the required information and click Create Security List.

To create a security list using the OCI CLI:

1. Run the following command:

oci security-list create --name <security_list_name> --vcn-id <vcn_id>

Attaching a Subnet to a Route Table

To attach a subnet to a route table using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which the subnet is located.

4. Click Subnets.

5. Click the name of the subnet that you want to attach to the route table.

6. Click Edit.

7. Under Route Table, select the route table that you want to attach to the subnet.

8. Click Save Changes.

To attach a subnet to a route table using the OCI CLI:

1. Run the following command:

oci subnet update --id <subnet_id> --route-table-id <route_table_id>

Attaching a Security List to a Subnet

To attach a security list to a subnet using the OCI Console:

1. Go to the OCI Console.

2. Click Networking > Virtual Cloud Networks.

3. Click the name of the VCN in which the subnet is located.

4. Click Subnets.

5. Click the name of the subnet that you want to attach the security list to.

6. Click Edit.

7. Under Security List, select the security list that you want to attach to the subnet.

8. Click Save Changes.

To attach a security list to a subnet using the OCI CLI:

1. Run the following command

oci subnet update --id <subnet_id> --security-list-ids <security_list_id>

These are just a few examples of VCN administrative tasks that you can perform using the OCI Console and the OCI CLI. For more information, please refer to the OCI documentation.

VCN Administration

 

As a VCN administrator, you are responsible for managing and securing your VCN. This includes tasks such as:

1.  Creating and managing subnets
2.  Creating and managing route tables
3.  Creating and managing security lists
4.  Creating and managing DHCP options
5.  Monitoring and managing VCN traffic
6. Troubleshooting and resolving VCN issues

VCN Troubleshooting

Some of the most common VCN troubleshooting issues include:

Connectivity issues: This can be caused by a variety of factors, such as subnet misconfiguration, route table issues, or security list issues.

Performance issues: This can be caused by a variety of factors, such as overloaded subnets, inefficient routing, or security list rules that are too restrictive.

Security issues: This can be caused by a variety of factors, such as misconfigured security lists, vulnerabilities in applications, or malware infections.

To troubleshoot VCN issues, you can use a variety of tools and resources, such as the OCI Console, the OCI CLI, and the OCI SDK. You can also contact Oracle support for assistance.

Here are some additional tips for VCN administration and troubleshooting:

Use subnets to isolate your resources: Subnets allow you to isolate your resources into logical groups. This can make it easier to manage and troubleshoot your VCN.

Use route tables to control traffic flow: Route tables allow you to control how traffic flows within your VCN and between your VCN and other networks.

Use security lists to protect your resources: Security lists allow you to control incoming and outgoing traffic to your VCN resources.

Use DHCP options to configure your clients: DHCP options allow you to configure your clients with the necessary information to connect to the network, such as the IP address of the DHCP server and the default gateway.

Monitor your VCN traffic: Use the OCI Console, the OCI CLI, or the OCI SDK to monitor your VCN traffic for performance issues and security threats.

Have a plan for disaster recovery: Create a plan for how you will recover your VCN in the event of a disaster. This plan should include steps for backing up your data and restoring your resources.

By following these tips, you can help to ensure that your VCN is secure, performant, and reliable.

Here are some additional practical scenario-based examples of how VCN administration and troubleshooting can be used:

Scenario 1: You are a VCN administrator and you are troubleshooting a connectivity issue. One of your subnets is unable to connect to the internet. You use the OCI Console to check the subnet's route table and security list. You discover that there is a missing route to the internet gateway. You add the missing route and the subnet is now able to connect to the internet.

Scenario 2: You are a VCN administrator and you are troubleshooting a performance issue. One of your subnets is experiencing high latency. You use the OCI Console to monitor the subnet's traffic. You discover that the subnet is overloaded. You move some of the resources in the subnet to another subnet and the latency is reduced.

Scenario 3: You are a VCN administrator and you are troubleshooting a security issue. One of your subnets is being attacked by a denial-of-service attack. You use the OCI Console to check the subnet's security list. You create a new security rule to block the traffic from the attacker's IP address.

By following the tips and examples above, you can effectively administer and troubleshoot your VCNs.

Oracle Cloud Infrastructure (OCI) - Tenancy

 

A Tenancy is a unique customer account in Oracle Cloud Infrastructure (OCI). A tenancy is a logical container for all of your OCI resources, such as compute instances, storage, and networking. You can create multiple tenancies in OCI, but each tenancy is isolated from other tenancies. This means that you can control who has access to your resources and how they are used.

Here are some multiple scenario based examples of how tenancies can be used:

Scenario 1:  You are a company with multiple departments, such as sales, marketing, and engineering. Each department has its own set of requirements, so you create a separate tenancy for each department. This allows you to isolate the resources for each department and to control who has access to them.

Scenario 2: You are a developer who is working on a new application. You want to create a separate tenancy for the application so that you can test it and deploy it to production without affecting your other applications.

Scenario 3: You are a consultant who is working with multiple clients. You want to create a separate tenancy for each client so that you can isolate their resources and to control who has access to them.

Scenario 4: You are a company that is expanding into new markets. You want to create a separate tenancy for each market so that you can comply with local regulations and to improve performance.

Tenancies can also be used to create complex multi-tenancy environments. 

For example, 

    You can use tenancies to create a separate tenancy for each customer or partner. This allows you to isolate their resources and to provide them with a customised experience.

Here are some additional benefits of using tenancies:

Security: Tenancies can help to protect your resources from unauthorised access.

Compliance: Tenancies can help you to comply with local regulations.

Performance: Tenancies can improve performance by isolating your resources from other tenancies.

Scalability: Tenancies are scalable and can grow with your business.

Cost Optimisation: Tenancies can help you to optimise your costs by isolating your resources and by using different pricing models for different tenancies.

If you are planning to deploy applications to OCI, you should consider using tenancies. Tenancies can help you to create a secure, compliant, performant, scalable, and cost-effective environment for your applications.