Prime 3.2 Nexus VDC

[exmode]

Hi,

In release 3.2 i found that Prime Infrastructure does not support non-admin virtual device context (VDC) on Nexus devices.
When using 4 Nexus switch 3 VDC in each Nexus
How to add Nexus and VDC switches to Prime? I can only add admin VDC, but what should I do with other VDCs?
And how many licenses are needed in this situation?

Any ideas?

Thanks

[m.hegeraat]

Hi  exmode,

Did you get an answer to this?

I would assume using the admin VDC PI can work out what other VDC are there and should be able to monitor them (assuming SNMP/SSH access in the VDC is present)

I'm not sure if PI can work out what IP's are present on the VDC's.

How do you establish you can't add a non-admin VDC to PI or that it is not supported?

Thanks, 

Michel

[ashishmathew]

Hello ,

I have almost same issues, but slightly different.

Admin and child vdcs are able to join in Prime 3.4 like separate devices, provided snmp strings configured, individually.

Wherein, when we check Admin vdc  details, you may view VDC summary, VDC resources, top VDCs for CPU utilization and allocated CPU, and VDCs managed, according to documentation. 

But no details showing especially VDCs managed.

Do we need to out extra commands to fetch these information from other VDCs?

Is there any snmp configuration to be added anywhere?

Thanks