Blade Server Configuration Network switch port experience talk

Http://www.aliyun.com/zixun/aggregation/13737.html "> Blade servers are much simpler to connect to external devices than rack-less servers, but there are some issues to be aware of, especially network devices. HP's bl460c, for example, has two motherboard expansion slots that can be connected to a network card or adapter. The common setting may be a dual-port NIC and a dual-port adapter. For blades, although it is easy to access the network card or adapter, but the chassis equipped with the connection side, the specific switch coding is fixed.

If the NIC is plugged into a socket connected to a SAN switch, the entire server is transformed into a degraded mode, and there is no easy way to redirect the data stream between the slots.

This means that if a room has more than one C7000 chassis, and they want to migrate one blade server from one chassis to another, two chassis must have identical switches, and the two switches must be internal interconnect slots that are fully aligned to the back of the chassis. For example, the Brocadesan switch is plugged into the 3rd and 4th slots, so each blade server chassis must have the same settings. Otherwise, when a blade is migrated from one chassis to another, the blade is not plugged in and the chassis is converted to degraded mode.

When a blade server migrates from one slot to another, its network port configuration cannot be migrated with the server. The San port does not have a problem because it is typically partitioned by a bus adapter address, but the network port cannot be partitioned with the media access control address. Whenever a blade server with a special network configuration (similar to a VMware or cluster hub network interface card) migrates from one slot to another, users who use a network switch must be processed by their network administrator.