Forum Replies Created
-
Posts
-
Hello vaiden,
Firstly you no longer need to run any script for NAT64. FABRIC DNS servers provided to your VMS now can do NAT64. With that said, the other is misunderstanding of how NAT64 service works. Most of the time when they say NAT64, it is meant to work in conjunction with DNS64.
When a hostname (with an IPv4-only address) is resolved for an IP at the DNS servers and the DNS server does a DNS64, it will create a fake IPV6 address for that host which will be sent to your application. Your application then uses that fake IPv6 address which is an IP that is managed by the NAT64/DNS64 server. The server will then route your traffic by converting from IPv6 to ipv4 and then back in reverse.
In your case, you are directly trying the IPv4 address which will not work. If you don’t have a hostname that was resolved to that IPv4 address, there is a complex workaround for this issue. You must create your own fake IPv6 address using the NAT64 server’s IPv6 prefix. If this is really needed, I can provide more details on how to do it.
This is a reminder to all FABRIC Users that the FABRIC MASS Rack will be shut down tomorrow by 11:00am Eastern. We have noticed many users still have slices on the rack. If they are set to expire within the downtime timeframe, those nodes may not be recoverable after the maintenance ends. Please plan your work accordingly.
Your VMs should be working again. The physical workers had crashed. We just recovered them and restarted all the VMs on those nodes.
The physical node has crashed again. I am working on restoring it now. Please restore your data plane IPs in about 2 hrs and check and let me know.
Can you check now. The VM had crashed. We restored it, but it may be missing its IP config on the data plane NICS that you may have to restore.
Can you please provide us some details about your slice and VM ? WHat is the IP of the node you are trying to ssh into ?
Just to follow up, this issue may take a while to resolve as it involves working with upstream campus network providers too.
Thank you for reporting this. It seems this may be a campus issue. We have notified the local campus to investigate and report back to us. We will inform you when its resolved.
Please try this again now and let us know if this works. We fixed some of the nodes involved in your slice that had errors.
From looking at the console boot messages of your VM, we observed that you may have changed the default route for the VM which overwrote the gateway IP needed to ssh into your VM. I see that the default gateway is now your FABNETv4 subnet. This would cause you to lose ssh connectivity to your. You have to delete this VM and start over and make sure not to change the default gateway of the VM.
Hello Nirmala,
Komal’s reply to your question may not have made it to your inbox as we (admin team) were updating the mailer component of this forum while she replied to you. Hopefully, this repost will make it to you.
Hi Nirmala,
Which JH container are you using? This error typically happens due to a version mismatch for Fablib. Please see below:
Fablib – if you are still using Release 1.5, please update fablib using the command:
pip install fabrictestbed-extensions==1.5.6Also, if you face issues running notebooks on JH, please ensure there are no entries for
fabrictestbed-extensionsinfabric_config/requirements.txt. If you have any entries there, Please remove them and restart your JH container.Thanks,
Komal
