Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Unable to access Harbor from some specific network (70418)

Last Updated: 5/30/2019Categories: TroubleshootingTotal Views: 2883Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You are unable to access Harbor from some specific IP subnets.

Traceroute to Harbor from these subnets shows, packet is reaching however the Harbor vm is dropping the packet.

When you run ifconfig on the Harbor VM, you the docker bridge network subnets conflicts with the other subnets in your environment.

Cause

This issue occurs due to IP conflict between docker bridge network on Harbor and other subnets in your PKS environment. As per the documentation, 172.17.0.0/16 > 172.22.0.0/16 are Docker reserved network CIDR (Classless Inter-Dormain Routing). However we could see that 172.23.0.0/16 > 172.26.0.0/16 bridge interfaces were also created on the latest Harbor versions.
https://docs.pivotal.io/runtimes/pks/1-3/nsxt-prepare-env.html#reserved-ip-blocks

Resolution

To avoid this issue, ensure to not to use the Docker reserved IP ranges in your PKS environment.

If the Docker bridge subnets are conflicting with your existing networks, resolve the issue by customizing the container networks on Harbor and cleaning up the docker bridge stale entries if exist.

Log in to Ops Manager and select Harbor Tile.

Customize the container network settings on Harbor by following the documentation:
https://docs.pivotal.io/partners/vmware-harbor/installing.html#configure_general

Apply changes from Ops Manager to apply the customized networks.

Once you applied the changes, log in to Harbor VM and verify if you have any stale entries of previous networks by running the command: ifconfig

If there are any stale networks, clean them up by following the below steps.

Stop the Harbor service by running the command: monit stop harbor

Check the interfaces on harbor by running ifconfig, you would see the stale entries of bridge network, names starting with br_xxxxxx.

Export docker alias : alias docker='/var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock'

Remove the docker bridge networks by running the command:
docker network rm $(docker network ls -q )
Note: This should remove the stale bridge network interfaces, you can confirm by checking ifconfig. They will be re-created automatically when you start the Harbor service.

Start the Harbor service by running the command:
monit start harbor

Verify that docker networks are created and working fine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
当适用于服务提供商的 VMware Cloud Foundation 中的目标数据存储包含空格时，无法创建内容库 (70521)

KB
•
オンプレミスの vCloud Availability 3.0 用の vSphere Client プラグインを使用すると、vCloud Director の userPrincipleName LDAP 認証情報を指定できない (68100)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant