-
Notifications
You must be signed in to change notification settings - Fork 327
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
Cannot connect and not forward properly after adding switch role(with mininet) #228
Comments
I don't see anything with your code snippet. Usually, not being able to connect to the switch with the runtime_CLI means that the switch has crashed. A few things can cause the switch to crash (e.g. out-of-bound register access during packet processing). |
Seems that the problem occurs due to the intrinsic_metadata.
|
You are not supposed to use
The names However, I think that the switch should probably not crash in your case, and I'll leave this issue open until I have time to try and improve it. |
I am adding a switch_role metadata in switch to let administrator to change role in run time CLI making switches perform differently for different role.
I was trying to use ECMP example to test it. However, after implemented, I test it in mininet. I find it make the switch not working.
(Before adding the code it work correctly in both mininet and localhost)
(After adding the code it seems perform correctly when running localhost as switch.
eg. switch role=0 , it work as ecmp,
eg. switch role =1, it do not perform actions(I will implement other role later
But not perform properly in mininet(cannot connect runtime CLI and not forward properly))
I loaded some commands into switch. It show commands are successfully loaded for the first time.
But the switch do not performs properly to forward the packets.
Then I run the run time CLI again it will shows the following error message
The following is the code I added in ECMP example to try adding the switch role.
(I just using the register for tracking the whether switch role is set correctly)
The text was updated successfully, but these errors were encountered: