Network Configuration Guide for centos with vlan id in the Cisco UCS Environment

Recently, a number of Cisco ucs c Series servers have been added. After two weeks of deployment and installation, the server can finally be tested. This document briefly introduces the network configuration of the Operating System (centos 6) in the Cisco UCS server. It can be simply considered that this article describes the network configuration of a physical server connecting the NIC to the trunk mode port of the Upper-layer switch with a network cable.

The physical connection topology is shown as follows.

The top layer uses a Cisco c3560 physical switch to provide Internet connection for the entire cluster. VLAN is divided into two, one management VLAN and one application VLAN. VLAN IDs are 4 and 31 respectively, and all uplink ports are set to trunk mode.

The two fabric interconnect clusters connect six UCMS servers together, reducing network complexity and improving server management capabilities and large-scale scalability. Each UCS rack server is equipped with a VIF interface card that provides two Gigabit Ethernet interfaces. using Cisco Network virtualization technology, it provides both management network interfaces and operating system network interfaces.

FI is the old version of 6120, which is inconsistent with the new server version. Therefore, you need to set all versions to the latest version, for example, to upgrade fi to Version 2.2 (11d, in this way, these ucs c rackmount servers can be managed through fi.

In the Cisco UCS manager, four NICs are virtualized for each server. The first Nic is used as the management network interface for remote management. During the configuration process, all the four virtual NICs are set to "trunk mode", which can process two VLANs (VLAN 4, 31) and native VLAN (vlan1) traffic (this should be set to "Access Mode", because it is the trunk mode, the following is available ). If you do not add a VLAN tag to the NIC, the operating system network will be disconnected, which is different from the connection between the upstream switch and the downstream switch (the downstream switch can be manually configured or automatically negotiated ), as shown in the following connection mode.

Because it is not an access mode, you must unify the VLAN "vest" in the operating system and attach the vlan id to the NIC. The specific process is as follows:

1. because the installation is minimized and the network is not connected, centos dvd iso must be mounted to the server. You can use KVM's virtual optical drive to remotely mount the file. Generally, in centos, CDROM number is 1, that is,/dev/cdrom1. You can use the Mount/dev/cdrom1/mnt command to complete the prompt judgment. If the prompt is to execute the file system type of the device, it is the wrong number.

2. Run the RPM command to install vconfig (VLAN (802.1Q) configuration program) to handle VLAN tags, rpm-IVH/mnt/packages/vconfig-1.9-8.1.el6.x86_64.rpm, as shown in the following figure.

3. The 8021q module exists before vconfig is installed. It is not loaded to the kernel by default. It is automatically added to the kernel module when the vconfig command is executed. You can use the modprobe command to add the 8021q module to the kernel and modprobe 8021q. After successful addition, no prompt information is displayed and the module is automatically exited. You can use the lsmod command to list whether the 8021q module is successfully added or not, lsmod | grep 8021q. For more information, see the following figure.

4. use vconfig to add a VLAN tag to the NIC. Run the command "add eth0 4" for vconfig. "eth0" indicates the NIC to be used and "4" indicates the vlan id. After the vlan id xx is added to eth0, a prompt is displayed, for more information, see the following figure.

5. Copy the ifcfg-eth0 to the ifcfg-eth0.4, note that eth0 must be enabled, but you do not need to enter an IP address, just like a switch. Key Point: Set onboot to yes and bootproto to none.

6. edit the ifcfg-eth0.4 file, set onboot to yes, set bootproto static or DHCP, just like configuring a common Nic, restart the network after the configuration ends, use ping to check whether the network is smooth.

End

This article from "communication, my favorite" blog, please be sure to keep this source http://dgd2010.blog.51cto.com/1539422/1529770