Hi. It appears that you rebooted the node while the profile setup
scripts were still setting up. Make sure to check
/local/setup/setup-driver.log and look for "Done." a few lines up from
the end. d710s are older machines, and it would not surprise me if
setup took nearly an hour on them. In your current experiment, it seems
that there is something going wrong after the mid-setup reboot, and the
container trying to build the O-RAN e2 term doesn't have internet
connectivity. You should just terminate this experiment and retry... at
this point, I'm not sure where kubespray left off with its setup during
the reboot, etc.
A single d710 probably will not work for this experiment, although I
have not tried. If you cannot get a single d740, I would fall back to
using two d430s. Two d820s might also work, although I have not tried.
that configuration.
David
On 11/17/20 9:06 AM, chuanneng sun wrote:
> Hi David,
> I just rebooted the node and the kubernetes seemed to be correctly
> installed and the commands like `kubectl` works now. However, as I am
> following the document to try srsLTE with this command: `sudo
> /local/setup/srslte-ric/build/srsepc/src/srsepc
> --spgw.sgi_if_addr=192.168.0.1`, the system showed
> `/local/setup/srslet-ric/build/srsepc/src/srsepc: command not found`.
>
> Thanks
>
> chuanneng sun <
sunchu...@gmail.com <mailto:
sunchu...@gmail.com>>
> 于2020年11月17日周二 上午10:50写道:
>
> Thank you for helping me! However, I just tried this morning and it
> still didn't work. Here are the details:
> After clicking "Start Experiment", I selected "O-RAN (Repo b9e02)"
> profile. Then I set parameters as 1 d710. After that, After the
> initiation, I click the node-0 and open its shell. I typed `kubectl`
> in the shell but it stilled showed no command.
>
> Can you help me with this?
> Thanks!!
>
> David M. Johnson <
john...@flux.utah.edu
> <mailto:
john...@flux.utah.edu>> 于2020年11月17日周二 上午10:15写道: