Subject: RARE user and assistance email list
List archive
- From: mc36 <>
- To: rare-dev <>, "" <>
- Cc: edgardcunha <>, Everson Borges <>, gabrieltetznermenegueti16 <>, "Moises R. N. Ribeiro" <>
- Subject: [RARE-users] backplane/stacking/dc functionality arrived to rare...
- Date: Sun, 15 May 2022 21:27:20 +0200
hi,
backplane functionality finally arrived to rare... it happened by adding capability to
"server p4lang" to be able to handle
multiple dataplanes simultaneously... the target use-cases include line-card
based chassis systems, stacking, or management
of a whole data-center... all the current dataplanes support the
functionality, and they could be freely mixed in a cluster...
technically it's a very small addition where freerouter considers how to
export a given route/mac to a given dataplane...
when it looks up the out-interface, it just checks if the given interface is
local or not to the current asic, and if it
finds that it's remote, then it exports the rule as it would be exported over
an mpls vpn...
it points to a nexthop, which includes complex encapsulations like gre or
l2tp, so completely remote line-cards
could be configured to a cluster... the extra functionality above the export
is a very basic discovery
protocol run over the configured backplane ports... it periodically sends a
hello describing the chassis, forwarder
port and a random... upon reception, the given port is considered to be part
of the backplane... this visibility
then fed to a per forwarder spf (the same class used in isis, ospf and lsrp)
to calculate a per forwarder line-card
reachability to the other line-cards, which is used during the route/mac
exporting process...
http://sources.freertr.org/cfg/p4lang-rout211.tst is a routing test case (but
bridging is also supported)
here r1 is the controller router instructing r2..r4 dataplane vms... r4 is
configured as a backplane only
sparateing r2 and r3 who configured to have backplane and user ports in
common... the r5..r8 routers are
surrounding the dataplane vms and test this mini chassis functionality...
(just a small addition, r1 could be a redundant pair of freerouters with auto
config sync in between them,
much like in real routers... this also test covered:
http://sources.freertr.org/cfg/conn-redun.tst)
finally here are some show commands from the backplane enabled p4 exporter,
but basically they're
the same for all the routing protocols using the freerouter spf class...
br,
cs
r1#show p4lang p4 backplane-graph
sfdp -Tpng > net.png << EOF
graph net {
//fwd0
"fwd0" -- "fe80:bad::1/128" [weight=0]
//fwd1
"fwd1" -- "fwd3" [weight=10] [taillabel="prt128"]
"fwd1" -- "fe80:bad::2/128" [weight=0]
//fwd2
"fwd2" -- "fwd3" [weight=10] [taillabel="prt128"]
"fwd2" -- "fe80:bad::3/128" [weight=0]
//fwd3
"fwd3" -- "fwd2" [weight=10] [taillabel="prt128"]
"fwd3" -- "fwd1" [weight=10] [taillabel="prt129"]
"fwd3" -- "fe80:bad::4/128" [weight=0]
}
EOF
r1#
r1#show p4lang p4 backplane-tree 1
`--fwd1
`--fwd3
`--fwd2
r1#show p4lang p4 backplane-tree 2
`--fwd2
`--fwd3
`--fwd1
r1#show p4lang p4 backplane-tree 3
`--fwd3
|`--fwd2
`--fwd1
r1#
r1#show p4lang p4 backplane-ports 1
port metric ready remote iface
p4lang port 128 10 true 3 p4lang port 129
r1#show p4lang p4 backplane-ports 2
port metric ready remote iface
p4lang port 128 10 true 3 p4lang port 128
r1#show p4lang p4 backplane-ports 3
port metric ready remote iface
p4lang port 128 10 true 2 p4lang port 128
p4lang port 129 10 true 1 p4lang port 128
r1#
r1#show p4lang p4 backplane-route 1
typ prefix metric iface hop time
null fe80:bad::3/128 0/20 #128 fe80:bad::4 00:18:29
null fe80:bad::4/128 0/10 #128 fe80:bad::4 00:18:29
r1#show p4lang p4 backplane-route 2
typ prefix metric iface hop time
null fe80:bad::2/128 0/20 #128 fe80:bad::4 00:18:30
null fe80:bad::4/128 0/10 #128 fe80:bad::4 00:18:30
r1#show p4lang p4 backplane-route 3
typ prefix metric iface hop time
null fe80:bad::2/128 0/10 #129 fe80:bad::2 00:18:31
null fe80:bad::3/128 0/10 #128 fe80:bad::3 00:18:31
r1#
r1#show p4lang p4 backplane-spf 1
category value
reach fwd1 fwd2 fwd3
reachable 3
unreach fwd0
unreachable 1
stub fwd0 fwd1 fwd2
segrou
nosegrou fwd0 fwd1 fwd2 fwd3
bier
nobier fwd0 fwd1 fwd2 fwd3
topostr fwd0,false,0,1 fwd1,true,1,1 fwd2,true,1,1 fwd3,true,2,1
topoid a8dc4d8a
last 2022-05-15 19:02:05 (00:18:41 ago)
fill 0
calc 0
table 1
run 4
r1#show p4lang p4 backplane-topology 1
node category value addition
fwd0 reach false 0
fwd0 segrou 0
fwd0 bier 0
fwd0 prefix fe80:bad::1/128 0
fwd1 reach true 1
fwd1 segrou 0
fwd1 bier 0
fwd1 neigh fwd3 10
fwd1 prefix fe80:bad::2/128 0
fwd2 reach true 1
fwd2 segrou 0
fwd2 bier 0
fwd2 neigh fwd3 10
fwd2 prefix fe80:bad::3/128 0
fwd3 reach true 2
fwd3 segrou 0
fwd3 bier 0
fwd3 neigh fwd2 10
fwd3 neigh fwd1 10
fwd3 prefix fe80:bad::4/128 0
r1#
r1#show running-config server p4lang p4
server p4lang p4
dataplanes 4
forwarder 0 remote ::
forwarder 1 export-vrf v1 1
forwarder 1 export-port sdn11 1 10 0 0 0
forwarder 1 export-port sdn12 2 10 0 0 0
forwarder 1 export-port sdn13 3 10 0 0 0
forwarder 1 export-port sdn14 4 10 0 0 0
forwarder 1 export-port bundle1 dynamic 0 0 0 0
forwarder 1 interconnect ethernet2
forwarder 1 backplane bundle1 10
forwarder 1 remote 10.11.12.111
forwarder 2 export-vrf v1 1
forwarder 2 export-port sdn21 1 10 0 0 0
forwarder 2 export-port sdn22 2 10 0 0 0
forwarder 2 export-port sdn23 3 10 0 0 0
forwarder 2 export-port sdn24 4 10 0 0 0
forwarder 2 export-port bundle2 dynamic 0 0 0 0
forwarder 2 interconnect ethernet4
forwarder 2 backplane bundle2 10
forwarder 2 remote 10.12.13.111
forwarder 3 export-vrf v1 1
forwarder 3 export-port sdn31 1 10 0 0 0
forwarder 3 export-port sdn32 2 10 0 0 0
forwarder 3 export-port sdn33 3 10 0 0 0
forwarder 3 export-port sdn34 4 10 0 0 0
forwarder 3 export-port bundle4 dynamic 0 0 0 0
forwarder 3 export-port bundle3 dynamic 0 0 0 0
forwarder 3 interconnect ethernet6
forwarder 3 backplane bundle4 10
forwarder 3 backplane bundle3 10
forwarder 3 remote 10.13.14.111
vrf v9
exit
!
r1#
- [RARE-users] backplane/stacking/dc functionality arrived to rare..., mc36, 05/15/2022
- Re: [RARE-users] backplane/stacking/dc functionality arrived to rare..., Moises R. N. Ribeiro, 05/15/2022
Archive powered by MHonArc 2.6.19.