Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello Cisco, I think there is an error about VCenter compatiblity in the n1v compatiblity document for version 1.5.2 and 1.5.2b. Both versions support ESXi5.1, but in the section "VMware Version Compatibility" the only supported Vcenter versions are ...
Hello,in the past it was always a problem to move ESX-Hosts with n1v to a new vcenter. The only possibility was to migrate all hosts/VMs back to vswitch before, what's a big effort in large environments.The procedure to do that was already discussed ...
Hello Cisco,I have a question about VSM performance. In our largest n1v environment (44 hosts, 432 vnic, 172vmnic) we see that the VSM (version 4.2(1)SV1(4a) ) has often a very high CPU load. The vcenter shows that the average VSM load is always ~75...
Hello, like some other people we hit also the bug CSCtl70759: #####################################################################Addition of new NIC to port-channel fails if profile has queueing policy Symptom: Addition of NIC(s) to port-channel f...
Hello, in the release notes for version 4.2(1)SV1(4a) I found a limitation about the vethernet trunk interfaces. 256 veth trunk are supported for the whole DVS with a maximum of 8 veth trunks per host. For a new n1v environment we need more then 8 ve...
I opened a TAC case for this. Cisco agreed that it is a failure in the compatibility doucmention, they created bug CSCue78269 for this.Today I could see that they already changed the compatiblity documention for version 1.5.2 and 1.5.2b. As expected...
We have the same issue , our LMS version is already 4.2.2 (Win2008 based) Immediate Report works fine, scheduled reports show this error. And it makes no difference if there is an entry for the email address or not, the error comes always.An noticea...
Louis,is it planed to implement a solution for n1v ?It would be very,very helpful. One of our n1v environments has for example 62 host in one DC with ~800vnics. All this have to me migrated to vswitch and , after the move to the new VCenter, back to ...
We had very close contact with Cisco develpoment about this. Finally it was a bug in n1v software with the mac pinning feature. It's fixed since version 1.5.1Hendrik
That issue sounds not good. We use also CA Spectrum and have different n1v environement, but we still use snmpv2. We use for some n1v already version 1.5.1, but also in this version we can see that the snmp engine-id is still the same as in version 1...
