Technically you can operate a 1000v system in a mixed configuration (VEM at 1.4 while VSM at 1.3) but this is not recommended or supported for a lengthy amount of time, nor for testing. Many of the "new" features are enabled with the VSM. The new bells & whistles aren't turned on until the VSM is upgraded. By upgrading the VEM, you're just running an updated VEM agent that is compatible with the new VSM.
For proper testing, we'd suggest you run up a lab with everything at the desired version(1.4a) and do testing in this controlled environment.
From a overall stance, I can say that 1.4a has been extremely stable. From 1.4 -> 1.4a there are some bug fixes so if you were looking for a recommendation on a version I'd push you towards 1.4a.
just for my understanding, Nexus version is called 4.2(1)SV1(4a) what does mean 4.2(1), I guess that SV1(4a) is the VEM version. Since I'm running 4.0(4)SV1(3), you said that I haven't to worry about upgrade to 1.4a but what about upgrade from 4.0(4) to 4.2(1). what I'm upgrading there ?
onother thing, I downloaded N1K SW from CCO and there I found VEM folder where i suppose that VEM SW is stored, is that correct ?
If I'm installing, for exemple, VEM410-201107407.zip with vihostupdate command I'm going to patching ESX and install the VEM 1.4a or just install the VEM ?
And, just for understanding, if I'm going to update VEM with VEM500-201108271.zip vihostupdate I'll do also upgrade ESX to 5.0 version ? isn't ?
Don't worry about the versioning, the difference in 1.4 compared to other builds is the updated underlying NXOS software.
The common name vs. the full software version is below
1,1 = 4.0(4)SV1(1)
1.2 = 4.0(4)SV1(2)
1.3 = 4.0(4)SV1(3)
1.4 = 4.2(1)SV1(4)
Yes, the full 1000v image will have sub folders containing all the VEM VIB files (used for manual installations).
If you have VUM (Update Manager) you can automate the upgrade, however if you want to do it manually in a controlled manner. IF you want to update the VEM to the latest release (1.4a) you can just pull the appropriate VEM update, and run it against the hosts you wish to upgrade, using either VI Host or esxupdate.
常见的数据中心之间通信均会采用运营商MSTP/OTN专线进行互联实现通信，由于长途线路价格昂贵通常我们需要最大化使用线路带宽，传统的网络传输中通常是尽力而为传输一旦突发流量较大就会发生线路拥塞的情况，从而影响业务正常通信传输。这时候我们可以采用Qos技术来实现数据中心思科设备之间关键网络流量保障，从而实现链路最大化利用。拓扑图场景如下：如上图，SW01是位于数据中心A的广域网接入Cisco Nexus 3048交换机，SW02是位于数据中心B的广域网接...
Cloud Networking Community on Cisco Customer Connection
Join our community!!
As a valued Cisco Cloud Networking (former DCN) customer, you can be part of Cisco Customer Connection Program (CCP), Cisco’s global online community program. Connect ...
Join us for a live demo of Cisco Intersight Cloud Orchestrator to learn how you can simplify the orchestration and automation of your infrastructure and workloads across your hybrid cloud environment. We will take a closer look at Cisco Intersight Cloud O...
Hybrid Cloud Demo Series: Simplify Orchestration of Your Infrastructure and Workloads
Tuesday, September 7, 202110:00 am Pacific Time(San Francisco, GMT-08:00)Join us for a live demo of Cisco Intersight Cloud Orchestrator to learn how you can simpli...
Hybrid Cloud Demo Series: Simplify your hybrid cloud environment with Cisco Cloud ACI
Tuesday, August 24, 202110:00 am Pacific Time(San Francisco, GMT-08:00)Join us for a special Hybrid Cloud Demo Series webinar featuring Cisco Cloud Application Cen...