Printer FriendlyEmail Article Link

Spirent TestCenter: LabServer troubleshooting

Environment/Versions
Troubleshooting an issue with the LabServer
Answer
  1. Verify if issue happens without a LabServer
  2. Verify that the LabServer has the recommended resources assigned
    • For this you can just run the following commands:
      • df <return>
      • top <return>
      • Example:
        • admin@q-labserver3:~$ df
          Filesystem     1K-blocks    Used Available Use% Mounted on
          /dev/sda3        9997600 4978304   4491732  53% /
          udev               10240       0     10240   0% /dev
          tmpfs             411504   15952    395552   4% /run
          tmpfs            1028756     476   1028280   1% /dev/shm
          tmpfs               5120       0      5120   0% /run/lock
          tmpfs            1028756       0   1028756   0% /sys/fs/cgroup
          /dev/sda1         124947   31841     86655  27% /boot
          admin@q-labserver3:~$ top
          top - 15:44:45 up 5 days, 23:36,  1 user,  load average: 0.00, 0.03, 0.00
          Tasks: 136 total,   2 running, 133 sleeping,   0 stopped,   1 zombie
          %Cpu(s):  0.3 us,  0.0 sy,  0.0 ni, 99.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
          KiB Mem:   2057512 total,  1925892 used,   131620 free,    24508 buffers
          KiB Swap:   131068 total,   131060 used,        8 free.   396016 cached Mem
          .....
           <output ommited>
  3. Do a disk speed test (shoud take less than a second)
dd if=/dev/zero of=test bs=1048576 count=500
dd if=test of=/dev/null bs=1048576
  1. Verify number of test sessions running when the issue is seen
  2. Verify if issue happens only in an specific PC
  3. Try rebooting the LabServer
  4. Try redeploying the LabServer
  5. Contact support if none of the above worked, send them the output of  “top” and “df” commands from the shell inside the LabServer, as well as disk speed test outputs

Product : LabServer,Spirent TestCenter