While extending vxlan NSX segment from on-prem to cloud, I am getting below error. "Unable to find Layer2 Id for segment /infra/segments/d0363700-b5f2-494f-8225-dce9b765cc98" tried upgrading HCX to...
See more...
While extending vxlan NSX segment from on-prem to cloud, I am getting below error. "Unable to find Layer2 Id for segment /infra/segments/d0363700-b5f2-494f-8225-dce9b765cc98" tried upgrading HCX to latest version , still same error. This error is coming only on one of segment. rest all are working fine. Segment with error has VM's connected and working fine. Let me know if anyone has faced similar error and fix.
Hello All, I am facing issue with vtep ips of transport nodes esxi. NSX transport nodes vtep ip is showing as apipa ip (169 ip range). i checked my DHCP pool and it is correct. i can see nsx vmk in...
See more...
Hello All, I am facing issue with vtep ips of transport nodes esxi. NSX transport nodes vtep ip is showing as apipa ip (169 ip range). i checked my DHCP pool and it is correct. i can see nsx vmk in the vcenter with correct ip but NSX-T manager GUI is showing ips as apipa ips. Let me know if anyone did face similar issue and what was the workaround. any specific service needs to be restarted ?
Currently I am not getting any NSX T logs in syslog servers loginsight. I need to know what logging level we should set on NSX-T components so that we will get alerts related to BGP status up/down ...
See more...
Currently I am not getting any NSX T logs in syslog servers loginsight. I need to know what logging level we should set on NSX-T components so that we will get alerts related to BGP status up/down and Loadbalancer vip and pool up/down onto loginsight. I have seen 3 levels are there. 0 is default. but i am having confusion on which logging level i should set to get logs. Also any other health checks I can set from network insight ?
