Skip to Content.

rare-dev - Re: [rare-dev] Exception when deleting a subinterface in p4lang

Subject: Rare project developers

List archive


Re: [rare-dev] Exception when deleting a subinterface in p4lang


Chronological Thread 
  • From: mc36 <>
  • To: , Alexander Gall <>
  • Subject: Re: [rare-dev] Exception when deleting a subinterface in p4lang
  • Date: Mon, 14 Mar 2022 17:50:38 +0100

with this really small change
https://github.com/mc36/freeRouter/commit/3fe645570bdba1c5a87f551239b4018ec1f464c9
i just added the new ports_add/del/mod message.... for now, i kept the same
format
for the state message until all the dataplanes completely catch up on the
news... :)
regards,
cs


sid(cfg)#
sid(cfg)#
sid(cfg)#interface sdn3
sid(cfg-if)#shutdown
debug servP4lang.sendLine:servP4lang.java:614 tx: state 3 0 0 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_del 1.1.1.9/32 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_del 1.1.1.8/30 3 2
sid(cfg-if)#
sid(cfg-if)#
sid(cfg-if)#no shutdown
debug servP4lang.sendLine:servP4lang.java:614 tx: state 3 1 0 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_add 1.1.1.8/30 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_add 1.1.1.9/32 3 2
sid(cfg-if)#
sid(cfg-if)#
sid(cfg-if)#^Z
sid(cfg)#server p4lang p4
sid(cfg-server)#
sid(cfg-server)#no export-port sdn3 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: portvrf_del 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: state 3 0 0 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: ports_del 30 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_del 1.1.1.9/32 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_del 1.1.1.8/30 3 2
sid(cfg-server)#
sid(cfg-server)# export-port sdn3 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: ports_add 3 0 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: state 3 1 0 0 0 0
debug servP4lang.sendLine:servP4lang.java:614 tx: mtu 3 1500
debug servP4lang.sendLine:servP4lang.java:614 tx: portvrf_add 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: tcpmss4in_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: tcpmss4out_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: tcpmss6in_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: tcpmss6out_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: verify4_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: verify6_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: mplspack_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: nshpack_add 3 0
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_add 1.1.1.8/30 3 2
debug servP4lang.sendLine:servP4lang.java:614 tx: myaddr4_add 1.1.1.9/32 3 2
sid(cfg-server)#


On 3/14/22 17:11, mc36 wrote:

okkk, got the point... i'll add the new message then....

but since the state message will only have to deal with the (no)shutdown
state finally,
what if we move all the parameters from it to the new message?
i mean the following:
state id 0/1 --- just to indicate the shutdown state
ports_add/del/mod id speed etc --- to indicate the port config change




Archive powered by MHonArc 2.6.19.

Top of Page