By default, many Oracle Cloud Infrastructure
Compute images don't come with telnet and nc utilities installed. To install these utilities on an instance, use the following yum command:
Copy
sudo yum install telnet nc -y
Verify that the oci-fss service is running for the mounted file system 🔗
When you install the oci-fss-utils package, it creates three systemd-managed services called oci-fss-gc.timer, oci-fss-init.service and oci-fss-monitor.service.
Open a terminal window on the instance.
Verify that the services are running using the following commands:
systemctl status oci-fss-gc.timer
The status should be active and waiting.
systemctl status oci-fss-init.service
The status should be active and exited.
systemctl status oci-fss-monitor.service
The status should be active and running.
After you mount a file system using the mount.oci-fss command, it creates a systemd-managed service called oci-fss-0<number>.service which is the oci-fss-forwarder process. Verify it's running by using the following command:
Use the following command to verify the namespace and see the network interface:
Copy
sudo ip netns exec ns1 ip link list
You should see output displaying all the ethernet devices within namespace ns1. For example:
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: x-peer0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65535 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 56:e9:e0:7a:02:f6 brd ff:ff:ff:ff:ff:ff link-netnsid 0
Use the tcpdump utility to analyze traffic between the oci-fss service and the NFS client 🔗
-f displays the most recent journal entries, and prints new entries as
they are appended to the journal.
-u specifies a specific systemd service unit. In this case, oci-fss-0<sequence_number> is the specified unit. If no unit is specified, journalctl returns allsystemd entries.