An administrator created a new Tier-1 Gateway and is attempting to change the connected gateway for a deployed segment to use the new gateway. In the UI, when the administrator clicks the Connected Gateway dropdown, the new Tier-1 gateway is not shown as an available gateway. What would prevent the new Tier-1 gateway from showing in the list of available gateways?
An administrator is configuring NSX resource sharing to allow shared access to multiple resources in the default space.
By default, which user role owns the shared resources for the default space?
An administrator is troubleshooting a BGP connectivity issue on a Tier-0 Gateway (Active/Active). The Tier-0 has the following configuration:
* Uplink VLAN 100: 192.168.100.0/24
* Uplink VLAN 101: 192.168.101.0/24
* BGP neighbors configured: 192.168.100.1 and 192.168.101.1
* A single static default route (0.0.0.0/0) exists with next-hop 192.168.100.1.
Symptoms observed on both Edge Nodes:
* Get BGP neighbors ---> both neighbors stuck in Idle (Connect) --- "No route to peer"
* Ping to 192.168.100.1 and 192.168.101.1 succeeds from the Edge nodes
* Get route shows the default route present only on VLAN 100 interface (fp-eth0), missing on VLAN 101 (fp-eth1)
What is the root cause of both BGP sessions remaining in Idle state?
An administrator encountered a failure with one of the NSX Managers in a VCF Fleet. The administrator has successfully re-deployed an NSX Manager from SFTP backups. However, after replacing the failed manager node, the new node joins successfully, but the cluster status remains "Degraded".
* The get cluster status command on the leader still shows the old UUID with state "REMOVED".
What is the command to resolve the issue?
An administrator is troubleshooting why workloads in NSX cannot reach the external network 10.100.0.0/16. The Tier-0 Gateway is in Active/Active mode and has the following configuration:
* Uplink-1 (VLAN 100): 192.168.100.0/24 -> router R1 at 192.168.100.1
* Uplink-2 (VLAN 101): 192.168.101.0/24 -> router R2 at 192.168.101.1
* A static route for 10.100.0.0/16 was added with both next-hops (192.168.100.1 and 192.168.101.1).
* The Scope of this route is set to Uplink-1.
Symptoms:
* Virtual Machines (VMs) cannot reach 10.100.0.0/16
* Traceroute from the VM stops at the Tier-0 gateway with "Destination Net Unreachable"
* Pings from the Edge nodes to both 192.168.100.1 and 192.168.101.1 are success
What explains why workloads in NSX cannot reach the external network?