Configure the Upstream Cisco Nexus 5000 Series Switch ................. 27 Cisco Nexus 1100 Series LOM Ports Connected to Cisco Nexus 2248 ............27 Cisco Nexus 1100 Series Control, Packet, and Data Gigabit Ethernet Ports Connected to Cisco Nexus 2248 ..................................27 Set Up the Primary Cisco Nexus 1100 Series VSA ....................
This document provides design guidelines for deploying Cisco Nexus 1100 Series Virtual Services Appliances (VSAs). The Cisco Nexus 1110-S and 1110-X VSAs are the first appliances in the Cisco Nexus 1100 Series. ® For detailed feature-level configuration documentation, please refer to the respective Cisco product configuration guides located at http://www.cisco.com/go/1100.
Virtual Service Blades A VSB provides expansion capabilities so that new services can be added to the Cisco Nexus 1100 Series in the future. The Cisco Nexus VSA Manager enables customers to install, configure, and manage a variety of VSBs.
Nexus 1100 Series. The Cisco Nexus 1110-S can host up to 6 VSBs, and the Cisco Nexus 1110-X can host up to 10 VSBs. These VSBs can be any combination of the VSBs supported. Figure 2 shows an example of a configuration.
To achieve high availability, you should deploy redundant Cisco Nexus 1100 Series appliances, with one Cisco Nexus 1100 Series VSA as the primary device, and the second Cisco Nexus 1100 Series VSA as the secondary device. The two appliances run in an active-standby configuration to offer high availability for both management and VSB deployments.
Cisco Nexus 1100 Series VSA, if you change the management VLAN for the Cisco Nexus 1100 Series, then the change is applied to both the Cisco Nexus 1100 Series VSA and all its hosted VSBs at the next reload.
Network Connection Option 1 Option 1 is preferred in cases in which customers are not using a Cisco NAM and therefore have little or no data traffic traversing the uplinks to the Cisco Nexus 1100 Series. This option is commonly used when the Cisco Nexus 1100 Series is used only for VSMs.
Page 11
Network Connection Option 2 Option 2 is well suited for customers who are deploying a Cisco NAM in the Cisco Nexus 1100 Series. The management, control, and packet traffic is kept physically separate from the data traffic, helping ensure that data traffic does not divert cycles from the other traffic.
Network Connection Option 3 Option 3 is well suited for customers who are deploying a Cisco NAM or VSG in the Cisco Nexus 1100 Series but require a separate management network. Because there is little control and packet traffic, customers can still use most of the bandwidth from the four 1 Gigabit Ethernet interfaces for Cisco NAM traffic.
Page 14
Network Connection Option 4 Option 4 is well suited for customers who want to use the Cisco NAM but require separate data and control networks. Separating the control from the data network helps ensure that Cisco NAM traffic does not divert cycles from control traffic and therefore affect connectivity (Figure 12).
Network Connection Option 5 (Flexible Network) With the addition of the flexible network option, users can now more flexibly deploy their VSBs on the Cisco Nexus 1100 Series. With this option, you do not need to specify which ports allow which types of traffic (management, control, or data traffic).
Page 16
Another configuration option is dedication of a single interface to a particular VSB. the Cisco Nexus 1100 Series has six physical interfaces but one of the interfaces needs to be used for Cisco Nexus 1100 Series communication, so five interfaces are available to host dedicated VSBs. Figure 15 shows a possible connectivity configuration for this option.
Wide Area Application Services (WAAS) and NAM appliances, are deployed. Typically, the Cisco Nexus 1100 Series is best deployed at the aggregation layer of the network so that it can host a larger set of servers. Because the architecture of the Cisco Nexus 5000 Series Switches and Cisco Nexus 2000...
In the uplink type 1 topology (Figure 16), all traffic (management, control, and VSB data traffic) is switched out at an effective bandwidth of 1 Gbps. Both ports on the Cisco Nexus 1100 Series, Ethernet interfaces 1 and 2, are teamed to form an active-standby pair.
5 Gbps for each Cisco Nexus 1100 Series VSA. This uplink type is well suited when more non-VSM VSBs, such as Cisco NAM or VSG VSBs, are used, because there is more bandwidth for the VSB data traffic to use.
3 through 6. If vPC (or similar clustering) is used on the upstream switches, the effective combined bandwidth is 5 Gbps for each Cisco Nexus 1100 Series VSA. This uplink type is well suited when multiple VSM VSBs are used because it allows the VSM traffic to be shared with other VSBs. This type also provides the flexibility to add either VSM VSBs or different additional VSBs in the future while increasing bandwidth utilization for all VSBs.
Figure 19 shows another option for deploying the Cisco Nexus 1100 Series in the aggregation layer or the Layer 2 and 3 boundary of the network. The VSMs residing on the Cisco Nexus 1100 Series VSA and the hosts that are managed by the VSMs can be connected over Layer 2 or 3 as explained in the previous sections.
Deploying the Cisco Nexus 1000V Series VSM on the Cisco Nexus 1100 Series The Cisco Nexus 1000V Series VSM is one of the VSBs that can be hosted on the Cisco Nexus 1100 Series VSAs. Each VSM can manage a group of up to 64 Cisco VEMs. From a network management perspective, a VSM and the VEMs make up a virtual switch.
As a best practice, back up configurations to a remote site and not on the bootflash drive of the Cisco Nexus 1000V Series VSM. The configuration can be stored on the bootflash drive, but you should have another copy stored remotely as well.
To help ensure high availability, the Cisco Nexus 1100 Series pair must be Layer 2 adjacent, similar to the Cisco Nexus 1000V Series VSM, and it must have a round-trip latency of less than 10 milliseconds (ms).
Configure the Upstream Cisco Nexus 5000 Series Switch The example presented here assumes that network connectivity option 3 is used with the Cisco Nexus 1100 Series. This example configures the two physical LOM interfaces on the Cisco Nexus 1100 Series to carry management traffic as an active-standby pair, and it configures a PortChannel on two of the four 1 Gigabit Ethernet Interfaces for control, packet, and data traffic.
Page 28
139 mode active 5548P-1# The configuration of the second Cisco Nexus 5548P will be similar. The PortChannel interface number can be different, but the port configuration and VLAN information should be the same. Verify that the PortChannel interface is up with the following command:...
Set Up the Primary Cisco Nexus 1100 Series VSA With the upstream access switch configured in preparation for the Cisco Nexus 1100 Series, power on the Cisco Nexus 1100 Series VSA. Follow these steps to set up the primary Cisco Nexus 1100 Series VSA: When asked, enter and confirm the administrator password.
You have completed this procedure. Set Up the Secondary Cisco Nexus 1100 Series VSA With the primary Cisco Nexus 1100 Series VSA configured, power on the secondary Cisco Nexus 1100 Series VSA and follow these steps: When asked, enter and confirm the administrator password.
HA mode set to secondary. Rebooting now... You have completed this procedure. Verify the Cisco Nexus 1100 Series Setup Run the following command on the Cisco Nexus 1100 Series VSA to validate the status of the Cisco Nexus 1100 Series VSA: Nexus1110# show system redundancy status...
Page 33
3532611584 bytes free 3991379968 bytes total The Cisco Nexus 1100 Series VSA is now configured in high-availability mode, and the Cisco Nexus 1000V Series ISO image is downloaded to the bootflash:repository directory, so creation of the first Cisco Nexus 1000V Series can begin.
Verify the Cisco Nexus 1000V Series VSB When the Cisco Nexus 1000V Series VSB is finished powering on, from the Cisco Nexus 1100 Series console, log into the Cisco Nexus 1000V Series instance and verify that both the primary and secondary VSMs are up and operational.
------------------------------------ -------------------- 10.29.172.188 10.29.172.188 this terminal session The Cisco Nexus 1000V Series has been set up in Layer 3 mode. You can verify this setup by running the following command: VSM-1110# show svs domain SVS domain config: Domain id: Control vlan:...
Page 36
The next screen accepts the VSM details and the data center object within VMware vCenter in which the hosts that the VSM will control reside. Enter the IP address for the VSM VSB that was created on the Cisco Nexus 1100 Series VSA and the credentials to log into the VSM.
Connected sync status: Complete version: VMware vCenter Server 5.0.0 build-455964 vc-uuid: 41961E07-7215-460F-85CD-90FC6E71E4EA VSM-1110# To install the VEM software and migrate the hosts to the Cisco Nexus 1000V Series, follow the steps documented in the configuration guide. For More Information Cisco Nexus 1100 Series Technical Documentation ●...