forked from vmware/vic
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added TS topic on 172 networks (vmware#729)
- Loading branch information
Showing
3 changed files
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 changes: 17 additions & 0 deletions
17
docs/user_doc/vic_vsphere_admin/ts_no_access_to_vic_services.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Some Users Cannot Access vSphere Integrated Containers Services # | ||
|
||
Attempts to connect to the Web-based services of the vSphere Integrated Containers appliance fail for certain users but not for others. The appliance and its services are running correctly. | ||
|
||
## Problem ## | ||
|
||
The appliance and its services are running correctly. Some users can access the Getting Started page, file server, and vSphere Integrated Containers Management Portal, and Demo VCH Installer Wizard without problems, but for other users the connections fail. | ||
|
||
## Cause ## | ||
|
||
Some users are attempting to access the Getting Started page, file server, vSphere Integrated Containers Management Portal, and Demo VCH Installer Wizard from client systems that have IP addresses in the range 172.17.0.0-172.22.0.0/16. | ||
|
||
vSphere Integrated Containers appliance use the 172.17.0.0-172.22.0.0/16 networks internally. The routing table in the appliance contains routes for these subnets, which causes issues if users attempt to access vSphere Integrated Containers services from an address for which the appliance has a directly connected route. Attempts to connect to the appliance from client systems with IP addresses in the range 172.17.0.0-172.22.0.0/16 fail because the appliance routes return traffic to itself instead of to the client system. | ||
|
||
## Solution ## | ||
|
||
Access the Getting Started page, file server, vSphere Integrated Containers Management Portal, and Demo VCH Installer Wizard from client systems with IP addresses that are not in the 172.17.0.0-172.22.0.0/16 subnets. |