01-04-2012 10:49 PM
Could you please help me clarify the following?
2. NOS 2.1.1 Admin guide
According to the above technical architecture document(Ref 1),
VCS supports automated port profile management in vmware environment as follows:
1. Port profiles are automatically created for each port group discovered from the vCenter
2. Port profiles are distributed across the fabric and necessary VLANs are created
on all VDX switches in the fabric
3. VM vNIC MAC addresses are associated to the port profile
Q1. Does NOS 2.1.1 support above?
Related description in NOS 2.1.1 admin guide is as follows:
"NOS automatically creates a port profile with an “auto”
prefix for all the vCenter port groups. User editing of these auto-port
groups is not supported."
But automatic MAC association is not described in NOS 2.1.1 admin guide.
Q2. Then what about QoS,Security and FCoE sub profiles?
Should we create another port profile for those sub profiles and associate it to VM MAC manually?
01-11-2012 01:06 PM
Jagath, the answer to both of your questions is "Yes". With regard to Q1, the VM MAC will be acquired from vCenter. For Q2, QoS etc currently are NOT learned and cannot be associated with the discovered profile.
07-27-2012 05:27 AM
I found that one MAC address cannot be associated with several port profiles.
Hence, even if we create a separate port profile for QoS and Security sub profiles,
that port profile cannot be associated with the same MAC.
That means, if we use VM-aware network automation feature, QoS and Security
sub profiles cannot be used for VMs.
So what is the real advantage of using this feature?.
Even if it creates port profiles (vlan only) automatically, at the same time
it disables some advanced features that can be used with port profiles.
So we have to select one or the other.
1. Automation of port profile creation or
2. QoS and Security