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.
vSphere 6 adds the ability to vMotion across virtual distributed switches. I am attempting to vMotion a live VM and vSphere will not allow it due to a version mismatch. I have two identical and working Nexus 1000v switches (n1000v-dk9.5.2.1.SV3.1.15....
I am unable to find Cisco documentation on backwards compatibility of VEMs when performing an upgrade to the VSM. I am looking to upgrade the VSM from 4.2(1)SV2(2.1a) to 5.2(1)SV3(1.15).
Do the hosts need to be upgraded simultaneously or will they c...
I have SNR configured as I always have done it. This particular system works fine with SNR as long as the caller is external from PSTN. If an internal IP phone user dials another IP phone user that is SNR enabled, the remote destination doesn't ring....
I am in the process of building out a new IM and P environment. I have added the name of the second node in the topology on the CUP Publisher, as well as created the proper DNS entries. Security Password is correct, of course and all services are pro...
I am in the process of building out a new IM and P environment. I have added the name of the second node in the topology on the CUP Publisher, as well as created the proper DNS entries. Security Password is correct, of course and all services are pro...
I figured out the issue. There is an intercluster trunk between new system and old that was causing a problem with the shortened four digit and ten digit dialing. Taking that out of the picture fixed it. The ICT is only temporary during a migration.
Thanks, I ended up rebuilding the both the Pub and Sub since it was a new environment. The second time it worked but oddly the processes were identical both builds.Bugs are odd though so... Thanks for posting bug id.Aaron
Upgrade 6.1.4 to 7.1.5 in lab prior to upgrading to 9.12. Then when your 9.1 upgrade fails you can at least gather logs. 6.1.4 cannot recover from a refresh upgrade failure, which is why you receive 'e2fsck: Get a newer version of e2fsck' error. Once...
