[cisco-voip] vmware support on BE7K - painful - tips on reducing ?

[Ryan Ratliff (rratliff)]

The trick is when choosing the Technology for the case you must pick "UC Hypervisor and VMware Foundation on Cisco Business Edition Servers (Non ISV1)” under "Voice - Communications Manager”. If you pick any of the Data Center ones they are looking for your ISV1 contract number.

If that’s what you picked and you are still getting pushback send me the SR number please.

-Ryan

On Jan 31, 2017, at 1:28 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


I had a few outstanding, but rather simple issues, with our BE7K deployment, so I thought I'd try my luck with TAC. These were specifically vmWare issues, so I was pessimistically optimistic (or optimistically pessimistic) about the whole thing.

Turns out, my expectations of entitlement issues were spot on.

Anyone have any tricks to speed things along?

I provide the serial number which should have the original vmware hypervisor support attached. But they just don't seem to acknowledge that. They're looking for data centre SKUs.

I wish there was html support in the case open tool, I'd write it in big fonts.






---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170131/eb12bf90/attachment.html>