Forum Replies Created
-
Posts
-
Hello,
Due to DNS IP renaming of docker and other Nat64 related changes, there has been a minor update to the MFLIB library being used. We are in the process of pushing out the latest version of the mflib library to jupterhub as a default, but in the mean time, before you begin any of your notebooks, please do
pip install fabrictestbed-mflib==1.0.4
Then “reload kernel ” in the jupyterhub menu if you have any notebooks open. Then redo the tutorial. It should work.
You may have to do the pip install step every time a new jupyterhub session is created until this version is made default in FABRIC.
Unfortunately not at this moment since it’s a policy decision affecting the whole Testbed. If you are unable to use this workaround, I would suggest using nat64.net since that seems to work fine.Based on the decision taken by the FABRIC Dev and Security team, we have deployed a temporary fix for this issue. The fix should be transparent and work for the site you mentioned without any workarounds on your part. Please let us know if you still have issues.
We are seeing issues related to the site objects.githubusercontent.com when used with FABRIC NAT64. For now a workaround that is being used for this is to add
2a01:4f9:c010:3f02:64:0:b9c7:6e85 objects.githubusercontent.com
in your /etc/hosts file. This line forces this one site to route through one of the nat64 servers offered by the NAT64.net site while using FABRIC NAT64 for all others.
Please try your test again and let us know if this works. We have applied a fix to the FABRIC DNS servers so that it no longer provides AAAA records for FABNETv4 addresses and RFC 1918 addresses
1 user thanked author for this post.
Hi Fraida,
The MICH site is currently down. We are trying to determine why but no ETA has been provided.
HI,
Apologize for the delay in responding. Our MF team looked into this and saw the errors you mentioned. There are two major issues we found that are likely the causing the issue. One of them pertains to the NCSA rack MF uses for creating the measurement node. The other was software related. They have a workaround for the software issue but will need some time to fix the NCSA Site issue. Is this an urgent requirement or can this wait for a few days while we resolve the issues without any workarounds?
There was no attachements in your post. Could you please provide a screenshot of the errors you see ?
WASH is back online
star-w6 issue was resolved
SRI MTU issue is being worked on but this rack is not in production yet.
The VM does come with some defaults that do work. Additionally, you can use any of the public ones available like google(8.8.8.8 , 8.8.4.4) or Cloudflare(1.1.1.1).
As you mentioned TACC has an IPv4 address for management and you are using IPV6 nameservers. Its not going to work. You have to use ipv4 nameservers
