Basically client is currently using esxi5 hosts using vswitch. they have a totally sperated monitoring network & swtiches from their prod network and swtiches.
Today they are wanting implement the 1000v platform and migrate the hosts to the n1k.
Upon preparing for their migration I notieced they would have an uplink to their mon network with a primary private-vlan ID # 825 and isolated vlan 826 no biggy here. We currently setup similar n1k on their staging network. However I noticed that they also have vlan#825 defined on their prod network for web servers.
So using the nexus creating port-profiles I am sure that the creating a primary pvlan 825 will conflict with web-prod vlan 825 I don't think we can have two vlan IDs the same and ask them to perform differently.
I've given the recommendation to change either the prod or mon vlan tag to something that does not conflict and of course that will cause an outage of sorts for a small periord of time.
One of my co-workers mentioned a VLAN NAT to rewrite the vlan ID, have to admit sounds like a hack.
So any ideas if there is a way to have the same vlan ID on the nexus with two different port-profiles? One for normal vlan 825 while the other is a primary pvlan 825 assocated with an isolated 826 vlan?
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...