Dear Team, During V2T getting below message, could someone please assist how to resolve the same. "DFW Rule ID 1133 with name RSA Auth Access cannot be migrated because the following group...
See more...
Dear Team, During V2T getting below message, could someone please assist how to resolve the same. "DFW Rule ID 1133 with name RSA Auth Access cannot be migrated because the following grouping object of type: SecurityGroup, value: securitygroup-50, name: NSX_SG_All-VMs was not correctly translated to NSX-T" Thank you in advance
Dear Team During V2T getting below message, Could someone please asisst how to resolve the same. "If you have IP-based IDFW rules and do not want traffic to be interrupted during migration, you...
See more...
Dear Team During V2T getting below message, Could someone please asisst how to resolve the same. "If you have IP-based IDFW rules and do not want traffic to be interrupted during migration, you need to manually create shadow firewall rules and remove them after the migration is completed." Thank you in advance
During V2T getting below messgae, how to resolve the same, Please assist. Feedback for 'NSX_SG_www-proxy-access' with id 'securitygroup-14': 'NSX_SG_www-proxy-access' contains 1 exclude member...
See more...
During V2T getting below messgae, how to resolve the same, Please assist. Feedback for 'NSX_SG_www-proxy-access' with id 'securitygroup-14': 'NSX_SG_www-proxy-access' contains 1 exclude member(s). Exclude members are not supported on NSX-T. Please redefine this securitygroup on NSXv by removing all the exclude members." Thank you in advance
Dear Team, During V2T getting below message ClusterComputeResource' is not supported in NSX-T. On few DFW rules Cluster is selected, how to mitigate the same. Please assist. thank you in adv...
See more...
Dear Team, During V2T getting below message ClusterComputeResource' is not supported in NSX-T. On few DFW rules Cluster is selected, how to mitigate the same. Please assist. thank you in advance
Dear Team, In what all use cases we need to select Shared Transit Uplink VLAN (left) and Point to Point Transit Uplink VLANs (right), Please assist. Thank you in advance
Dear Team, I'm not able to see which Transport node profile is applied on second cluster as that field is showing blank. How to check which TN profile has been applied to this cluster?...
See more...
Dear Team, I'm not able to see which Transport node profile is applied on second cluster as that field is showing blank. How to check which TN profile has been applied to this cluster? Please assist. Thank you in advance
Dear Team, we create 2 segment VLAN (Seg-vlan100 & Seg-vlan 200) for deterministic routing and map the same to appropriate interface and interface mapped to respective Edges. proper flow of determ...
See more...
Dear Team, we create 2 segment VLAN (Seg-vlan100 & Seg-vlan 200) for deterministic routing and map the same to appropriate interface and interface mapped to respective Edges. proper flow of deterministic routing we need to set appropriate segment vlan on fpeth1 (Seg-Vlan100) on edge node1 & fpeth1 (Seg-Vlan200) on edge node2 is above config is proper or instead of segment we need to map dvpg? Also need to know for deterministic routing what needs to be mapped on egde node dvpg or segment
Dear Team, There are two additional teamings (failover order) for uplink 1 and uplink 2. Both have different active uplinks; this is specifying which uplink on the VDS the teaming policy should u...
See more...
Dear Team, There are two additional teamings (failover order) for uplink 1 and uplink 2. Both have different active uplinks; this is specifying which uplink on the VDS the teaming policy should use. After the uplink profile has been modified, the VLAN Transport Zone that is attached to the Edge Nodes must be modified or a new one created and attached to the Edge Nodes. This allows segments that are created and attached to this Transport Zone to utilize the named teaming policies. an existing Transport Zone that is used specifically for Edge uplink segments being modified. Segments that are created and attached to the Edge uplink Transport Zone can now utilize named teaming policies. below screen shows the configuration of a segment that will utilize a named teaming policy. The final step is to create an interface using the segment created Remember, using this segment ensures that traffic leaving this Tier-0 interface egresses the Edge Node on a specific uplink. When an uplink profile is applied to an Edge Node, the Edge uplinks are mapped to a VDS port group Just wanted to know if same dvPGs flow the TEP and as well as VLAN traffic then what should be the teaming config on dvpg1 and dvpg2 would be ? DVPG1 Vmnic1 (Active) Vmnic2 (Active) DVPG2 Vmnic1 (Active) Vmnic2 (Active) OR DVPG1 VMnic1 (Active) and VMnic2 (Standby DVPG2 VMnic2 (Active) and VMnic1 (Standby OR DVPG1 VMNic1 (Active) DVPG2 VMNic2 (Active)
Hello Team, Whatever timer and password is configured on physical layer same needs to be configured on T0 or whatever Timer and password we define on T0 that needs to be configure on physic...
See more...
Hello Team, Whatever timer and password is configured on physical layer same needs to be configured on T0 or whatever Timer and password we define on T0 that needs to be configure on physical layer, Please assist, also need to know in what use case we need to use this option. Thank you in advance
Dear Team, I'v seen In route and out route filter configured in customer environment, just wanted to know what exactly this option do and also need to know when to select what option? Could...
See more...
Dear Team, I'v seen In route and out route filter configured in customer environment, just wanted to know what exactly this option do and also need to know when to select what option? Could some throw some light on this. wh Thank you in advance
Hi Team, Once we migrate the Edges to NSX-T then N/S will flow from NSX-T and E/W from NSX-V, but I'm able to see NSX-V Uplink interface for N/S is still showing in a connected state and the same...
See more...
Hi Team, Once we migrate the Edges to NSX-T then N/S will flow from NSX-T and E/W from NSX-V, but I'm able to see NSX-V Uplink interface for N/S is still showing in a connected state and the same Uplink is also showing connected in NSX-T , so will there be IP conflict in this case? Thank you in advance,
Hi Team, We have receive a requirement from customer. we can't migrate complete cluster from V2T in one go, we have 10 Hosts in the cluster and we can only migrate 7 hosts during week days and mi...
See more...
Hi Team, We have receive a requirement from customer. we can't migrate complete cluster from V2T in one go, we have 10 Hosts in the cluster and we can only migrate 7 hosts during week days and migrate rest 3 on Weekends for any reason, if we follow this approach then i've below queries. 1) how communication will work from nsxv to nsx-t host VMs, bcoz nsx-v host vms are connected to LS and NSX-T hosts VMs are connected to Segments, means if nsx-v VM wants to talk to nsx-t VMs then it will not work? right. for example web is on nsx-v and app is on nsx-t host then how this communication will work 2) if we follow this approch then we may also need to disable DRS or it;s not required. Thank you in advance...
Dear Team, Just wanted to understand what is the use of Service Interface? Could some one please try to explain me in simple english. Thank you in Advance
