Skip to content

Commit

Permalink
Added TS topic on 172 networks (vmware#729)
Browse files Browse the repository at this point in the history
  • Loading branch information
stuclem authored Sep 5, 2017
1 parent 041aa23 commit 8e74103
Show file tree
Hide file tree
Showing 3 changed files with 19 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/user_doc/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@
* [No Single Host Can Access All Datastores](vic_vsphere_admin/ts_datastore_access_error.md)
* [Plug-In Scripts Fail](vic_vsphere_admin/ts_plugin_script_fails.md)
* [Plug-In Does Not Appear](vic_vsphere_admin/ts_ui_not_appearing.md)
* [Some Users Cannot Access Services](vic_vsphere_admin/ts_no_access_to_vic_services.md)
* [Deleting or Inspecting a VCH Fails](vic_vsphere_admin/ts_delete_inspect_error.md)
* [Certificate Errors when Using Full TLS Authentication with Trusted Certificates](vic_vsphere_admin/ts_clock_skew.md)
* [Security Reference](vic_vsphere_admin/security_reference.md)
Expand Down
1 change: 1 addition & 0 deletions docs/user_doc/vic_vsphere_admin/troubleshoot_vic.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,6 @@ This section provides solutions for common problems that you might encounter dur
* [VCH Deployment with a Shared NFS Datastore Fails with an Error About No Single Host Being Able to Access All Datastores](ts_datastore_access_error.md)
* [vSphere Client Plug-In Scripts Fail with No Error Message](ts_plugin_script_fails.md)
* [vSphere Integrated Containers Plug-Ins Not Deploying Correctly](ts_ui_not_appearing.md)
* [Some Users Cannot Access vSphere Integrated Containers Services](ts_no_access_to_vic_services.md)
* [Deleting or Inspecting a VCH Fails with a Not a VCH or Resource Pool Not Found Error](ts_delete_inspect_error.md)
* [Connections Fail with Certificate Errors when Using Full TLS Authentication with Trusted Certificates](ts_clock_skew.md)
17 changes: 17 additions & 0 deletions docs/user_doc/vic_vsphere_admin/ts_no_access_to_vic_services.md
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.

0 comments on commit 8e74103

Please sign in to comment.