-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to establish session with the server #49
Comments
|
Yes, I have already read the README but I don't understand it. Which is the IP address assigned to the Docker bridge? |
I think I have found the error. The file p4runtime-sh-docker lacks of --grpc-addr argument to pass on. Since neither IP nor port is specified, the error is: Failed to connect to all addresses |
Hi @SergiVera |
When running the P4 Switch Container, you need to expose ports with the -p 50001:50001 flag. This way, you can run p4runtime-shell for localhost: 50001. For example, if you run a topology with mn-stratum, you can run p4runtime-shell for localhost:50001, localhost:50002, and localhost:50003, as your host's port has been bound to your container. Check this example:
|
Hello, thanks @fatihusta @emdneto for your time, I've been able to solve the problem. Regards |
Hi @SergiVera I have the same problem. How did you solve it? Many thanks |
Hello @belenbrandino, In the end, I haven't used p4 in my project, but I'm sure I solve it too but I don't remember it well. I'm glad that you've solved it too! Thanks |
Hi everyone,
I have some issues when trying to run the p4runtime shell, as shown in the following figure:
I have used the following command: sudo ./p4runtime-sh-docker --grpc-addr 0.0.0.0:50001 --device-id 0 --election-id 0,1 --config ../p4-tutorial/basic-forwarding/build/basic.p4.p4info.txt,../p4-tutorial/basic-forwarding/build/basic.json I guess the error is in the --grpc-addr but I don't know how to proceed. I have tested it with addresses 0.0.0.0 and localhost but I always obtain the same error. Thanks in advance!
The text was updated successfully, but these errors were encountered: