Model for measuring network traffic and network design for virtual Connect (Active/standby vs active/active)

Determine the mode of the network type and the type of virtual Connect network design (active/standby vs active/active)

When faced with choosing which virtual Connect network design type (active/active (a/a)
Vs. Active/standby (A/S) uplinks), you need to consider the types of enclosure internal needs to support network traffic, for example
For example, if there is more server-to-server traffic inside the enclosure, is there a majority of traffic within the enclosure
All need to be in and out of the machine box. The mode of network traffic, North/south (N/S) vs. East/west (E/W), when designing the virtual connect scenario, you should consider the deployment of network connections to maximize the connection bandwidth, taking into account the server-to-server minimum requirements in the Access box, when communicating with the remaining servers in the same VLAN within the same machine frame.
For example, if you have a higher proportion of in/out or north/south traffic in a deployed scenario, a a/a network design might be the best choice, on the grounds that it enables as many uplink connections as possible. However, if more network traffic is only occurring within the same Enclosure/vlan system, choosing A/S may be the wisest option that will reduce or eliminate any server-to-server communications leaving the enclosure.

Determine the type of network connection used is a/a vs. A/S is not an issue that needs to be considered in domain configuration. The A/A and A/S networks can be deployed independently in the same VC domain, for example, an iSCSI connection can be configured to a/a to support higher rates of N/S traffic on the initiator and target side. At the same time, LAN connections for applications and users can be deployed as A/S to support more e/w communications.

In a A/S network design, all servers connect 2 NICs to the same VC network. Communication between all servers in VC domain is directly connected to this network, regardless of whether the server NIC is active. In the following example, if NIC1 for Windows Host 1 is active, NIC2 for Windows Host 2 is active and communication between servers crosses the internal stacking link. For external communications, all servers in the frame will use active uplinks (current) to connect to Bay1, regardless of which of their NICs is active.

Figure 1-This is a A/S network configuration instance. One uplink is active and the other is standby, enabling standby when a network failure or module failure occurs.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/42/6C/wKioL1PXXG2xn7LpAAQAeflaQJA534.png "title=" 1.PNG " alt= "Wkiol1pxxg2xn7lpaaqaeflaqja534.png"/>

In a a/a network design, all servers connect their network card to the corresponding VC network, the server in VC domain will communicate with each other according to which is active in the server network card. In the following instance, if NIC 1 for Windows Host 1 is active, Windows Host 2 NIC2 is active, and communication between two servers will not span the internal stacking link (internal stacking links), Instead, it leaves the cage and enters again through the corresponding module to obtain communication; However, if a high-speed external communication is required, vs peer to peer, then a a/a configuration may be a better choice since two uplink are active forwarding traffic. If the same NIC on the two servers is active, the communication between the servers will still be stored in the same module/cage.

Figure 2-This is an instance of a a/a network configuration. Two uplinks are active to forward traffic.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/42/6C/wKioL1PXXJ_gwoaoAAG5rh8udag668.png "title=" 2.PNG " alt= "Wkiol1pxxj_gwoaoaag5rh8udag668.png"/>

Figure 3: Both a/a (iscsi_x) and A/S (Vnet_prod) modes are used in the following instances.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/42/6C/wKioL1PXXMjwIoK8AAHCpuJEu70399.png "title=" 3.PNG " alt= "Wkiol1pxxmjwiok8aahcpujeu70399.png"/>

Note: As an option, if FC is not required, the iSCSI network can be connected as iSCSI hardware acceleration, connected Flexhba to use.

For C7000 Virtual Connect, it is currently an important knowledge point for HP Cloudsystem, and although it is a bit crazy to get started, it does find it convenient to use it, especially when combined with vsphere design. We can perfectly design a high-redundancy high-reliability enterprise production environment, the follow-up will continue to try to explore.

Welcome message exchange, thank you.

This article is from the "Dragon Kiss" blog, make sure to keep this source http://728756.blog.51cto.com/718756/1532357