Updated: 09/03/2019 by Computer Hope Show Short for network interface card, the NIC is also referred to as an Ethernet card and network adapter. A NIC is a computer expansion card for connecting to a network (e.g., home network or Internet) using an Ethernet cable with an RJ-45 connector. Due to the popularity and low cost of the Ethernet standard, nearly all new computers have a network interface build directly into the motherboard. The top image shows the SMC EZ Card 10/100 PCI network card, one of the more common examples. The bottom picture shows a PC Card. More specifically, the SMC EZ Card 10/100 wireless network card, which is found with older laptop computers that do not have onboard wireless capabilities. Tip A network card is sometimes improperly referred to as a broadband card or Internet card. The network card is what allows your computer to connect to the Internet (a network) using a cable (Cat 5). That cable is connected to a router that allows your computer to use a broadband connection. How does a computer with a network card connect to a network?Network cards can communicate with each other over the same network using a network switch, or if two computers are directly connected. When computers need to connect to a different network (e.g., the Internet), they must be use a router to route the network packets to the correct network. Where is a network card located in a computer?In a desktop computer, the network card is often located near the USB ports on the back if it's an onboard version. If it's a separate network card expansion card (not onboard), it usually is on the back of the computer, near the bottom, taking up a PCI slot. In a laptop, the network card is integrated into the motherboard. The network port is usually on the side on the laptop, or it may be on the back. If you cannot find a network port on your laptop, it may only have a wireless network connection. You can purchase a network card for laptops, which is installed into a PC card slot on the side of the laptop, if available. Broadband, Computer acronyms, Connection, Hardware terms, LAN, Network terms, Processing device
Computer EngineeringComputer NetworkMCA A network interface card (NIC) is a hardware component without which a computer cannot be connected over a network. It is a circuit board installed in a computer that provides a dedicated network connection to the computer. It is also called network interface controller, network adapter or LAN adapter. Purpose
Types of NIC CardsNIC cards are of two types − Internal Network CardsIn internal networks cards, motherboard has a slot for the network card where it can be inserted. It requires network cables to provide network access. Internal network cards are of two types. The first type uses Peripheral Component Interconnect (PCI) connection, while the second type uses Industry Standard Architecture (ISA). External Network CardsIn desktops and laptops that do not have an internal NIC, external NICs are used. External network cards are of two types: Wireless and USB based. Wireless network card needs to be inserted into the motherboard, however no network cable is required to connect to the network. They are useful while traveling or accessing a wireless signal.
Updated on 30-Jul-2019 22:30:24
This topic describes how to manage the virtual network interface cards (VNICs) in a virtual cloud network (VCN).
The servers in Oracle Cloud Infrastructure data centers have physical network interface cards (NICs). When you launch an instance on one of these servers, the instance communicates using Networking service virtual NICs (VNICs) associated with the physical NICs. The next sections talk about VNICs and NICs, and how they're related. A VNIC enables an instance to connect to a VCN and determines how the instance connects with endpoints inside and outside the VCN. Each VNIC resides in a subnet in a VCN and includes these items:
Each VNIC also has a friendly name you can assign, and an Oracle-assigned OCID (see Resource Identifiers). Each instance has a primary VNIC that is automatically created and attached during launch. That VNIC resides in the subnet you specify during launch. The primary VNIC cannot be removed from the instance. A secondary VNIC can be removed or detached from an instance, but it is always immediately deleted and can't exist when no longer attached to an instance. This section is relevant to bare metal instances. The OS on a bare metal instance recognizes two physical network devices and configures them as two physical NICs, 0 and 1. Whether they're both active depends on the underlying hardware. You can determine which NICs are active for a shape by reviewing the network bandwidth specifications for bare metal shapes. If the network bandwidth is listed as "2 x <bandwidth> Gbps," it means that both NIC 0 and NIC 1 are active, and each physical NIC has the indicated amount of bandwidth. If the network bandwidth is listed as "1 x <bandwidth> Gbps," it means that only NIC 0 is active. On current generation Standard and DenseIO shapes, typically both NIC 0 and NIC 1 are active. NIC 0 is automatically configured with the primary VNIC's IP configuration (the IP addresses, DNS hostname, and so on). If you add a secondary VNIC to an instance, you must specify which physical NIC the secondary VNIC should use. You must also configure the OS so that the physical NIC has the secondary VNIC's IP configuration. For Linux instances, see Linux: Configuring the OS for Secondary VNICs. For Windows instances, see Windows: Configuring the OS for Secondary VNICs. You can add secondary VNICs to an instance after it's launched. Each secondary VNIC can be in a subnet in the same VCN as the primary VNIC, or in a different subnet that is either in the same VCN or a different one. However, all the VNICs must be in the same availability domain as the instance.
Here are some reasons why you might use secondary VNICs:
Here are more details about secondary VNICs:
By default, every VNIC performs the source/destination check on its network traffic. The VNIC looks at the source and destination listed in the header of each network packet. If the VNIC is not the source or destination, then the packet is dropped. If the VNIC needs to forward traffic (for example, if it needs to perform Network Address Translation (NAT)), you must disable the source/destination check on the VNIC. For instructions, see To update an existing VNIC. For information about the general scenario, see Using a Private IP as a Route Target.
To use Oracle Cloud Infrastructure, you must be granted security access in a policy by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment to work in. VNICs reside in a subnet but attach to an instance. The VNIC's attachment to the instance is a separate object from the VNIC or the instance itself. Be aware that the VNIC and subnet always exist together in the same compartment, but the VNIC's attachment to the instance always exists in the instance's compartment. This distinction isn't important if you have a simple access control scenario where all the cloud resources are in the same compartment (for example, for a proof-of-concept). When you move to a production implementation, you might decide to have network administrators manage the network, and other personnel administer instances. That means you might put instances in a different compartment than the subnet.
For administrators: see IAM Policies for Networking.
You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring and Notifications. For information about monitoring the traffic coming in and out of VNICs, see VNIC Metrics. To view an instance's VNICs
To create and attach a secondary VNIC
To add or remove a VNIC from a network security group
You can change which network security groups (NSGs) a VNIC belongs to, or remove a VNIC from all NSGs.
To detach and delete a secondary VNIC
Caution If the VNIC has a private IP that is the target of a route rule, deleting the VNIC causes the route rule to blackhole and traffic will be dropped. This procedure detaches and deletes the specified secondary VNIC. You can't detach and delete an instance's primary VNIC. When you terminate an instance, all attached VNICs (primary and secondary) are automatically detached and deleted.
It takes typically a few seconds before the VNIC is deleted. If the secondary VNIC is on a Linux instance: If you then run the provided script in Linux: Configuring the OS for Secondary VNICs, it removes the secondary VNIC from the OS configuration.
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface. To manage VNICs on an instance, use these operations:
This section gives details about OS configuration that is required for secondary VNICs on instances that run a variant of Linux. At the end of the section is a script that you can use to configure secondary VNICs on either VM instances or bare metal instances. When you add a secondary VNIC to a Linux VM instance, a new interface (that is, an Ethernet device) is added to the instance and automatically recognized by the OS. However, DHCP is not active for the secondary VNIC, and you must configure the interface with the static IP address and default route. The script provided here handles that configuration for you. When you add a secondary VNIC to a Linux bare metal instance, the OS does not automatically recognize the secondary VNIC, so you must configure it in the OS. Depending on your requirements, you can configure it as either:
The following script works for both VM instances and bare metal instances. It looks at the secondary VNIC information in the instance metadata and configures the OS accordingly. You could run the script periodically to bring the OS configuration up to date with the instance metadata. For VM instances in particular, the OS automatically recognizes the secondary VNIC's interface, and the script just needs to configure the static IP address and default route. For bare metal instances in particular, the script creates the interface for the secondary VNIC and configures it with the relevant information. If the instance has two active physical NICs (NIC 0 and NIC 1), the script configures the secondary VNIC to use whichever physical NIC you chose when you added the VNIC to the instance. Note that for NIC 1, if a secondary VNIC has VLAN tag 0, it uses the NIC's interface. The script doesn't create an interface for that secondary VNIC. Here are some additional notes about how the script works for both VM instances and bare metal instances:
Important The script uses a simple configuration process that does not persist if you reboot the instance. If you use the script, make sure to rerun it after each reboot. Here are basic examples of how to run the script:
See the script's help for more information. View the script that configures a Linux-variant OS for a new secondary VNIC Important This script is intended for use in situations where non-hypervisor compute instances need to be assigned an additional VNIC and IP address.
Secondary VNICs are supported on VM and bare metal instances (except for instances that use previous generation Standard1 and StandardB1 shapes). For bare metal instances, secondary VNICs are supported only on the second physical NIC. Tip The first physical NIC is NIC 0, and the second is NIC 1. You must configure the secondary VNIC within the OS. There's an Oracle-provided PowerShell script that performs configuration. When running the script, you can optionally provide the secondary VNIC's OCID (which you can get from the instance's VNIC metadata): .\secondary_vnic_windows_configure.ps1 "<secondary_VNIC_OCID>"Otherwise, the script shows a list of the secondary VNICs on the instance and asks you to choose the one you want to configure. Here's generally what the script does:
View the Powershell script that configures Windows for a new secondary VNIC The overall process for configuration varies slightly depending on the type of instance (VM or bare metal) and how many secondary VNICs you add to the instance. Windows VM instances
Here's the overall process:
|