RARE user and assistance email list

[mc36 <>]

hi,
you can have both tagged and untagged bridge, even vlan rewriting ones mixed 
together, there should not be restrictions...
and as you can spot in frederic's show commands, you already have macs 
learned from sdn20 both tagged and untagged...
only sdn19 is the one which i cannot spot tagged macs learned.... can you 
please give us sho inter summ to see if there were packets at all?
thanks,
cs


On 8/29/21 5:42 PM, Marcos Felipe Schwarz wrote:
> I'm doing some preliminary test.
>
> I can remove temporarily sdn19 and sdn20 from bridge 1. To test bridge 2 
> tagged. But is there a limitation to why I can't have both bridges 
> simultaneously?
>
> My final objective is to have bridge 1 containing sdn15, 16, 19 and 20 (all 
> preferably untagged, but can be tagged if necessary).
> Bridge 2 containing sdn19 (tagged vid 19) and sdn30 (untagged)
> And bridge 3 containing sdn20 (tagged vid 20) and sdn32 (untagged).
>
> Since I'm not sure about the restrictions, I was trying a tagged bridge 
> between sdn19 and 20 first.
>
> Regard,
>
> Marcos Schwarz
>
>
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *From:*  <> on 
> behalf of Frédéric LOUI <>
> *Sent:* Sunday, August 29, 2021 12:22:12 PM
> *To:*  <>
> *Subject:* Re: [RARE-users] Bridge on tagged ports not working
> Hi Marcos,
>
> There were typos in my previous mail:
>
> Is it voluntary to:
>
> * To put  sdn19 in: bridge 1
> * To put  sdn20 in: bridge 1
>
> * And sdn19.19 and sdn20.19 in bridge 2 ?
>
> Please find the following stanza:
> More info here: http://sources.nop.hu/cfg/conn-bridge02.tst 
> <http://sources.nop.hu/cfg/conn-bridge02.tst>
> Here: http://sources.nop.hu/cfg/p4lang-acl13.tst 
> <http://sources.nop.hu/cfg/p4lang-acl13.tst>
> And there: http://sources.nop.hu/cfg/p4lang-acl14.tst 
> <http://sources.nop.hu/cfg/p4lang-acl14.tst>
>
> conf t
> int sdn19
>   no  bridge-group 1
>  Â exit
> int sdn19.19
>   no  bridge-group 2
>  Â bridge-group 2
>  Â exit
> int sdn20
>   no  bridge-group 1
>  Â exit
> int sdn20.19
>  Â no bridge-group 2
>  Â bridge-group 2
>  Â exit
>  Â end
>
> Sorry for the typo. But I presumed that you get the idea :-)
>
> À bientôt,
> --Â  Frederic
>
>
>
>
> > Le 29 août 2021 à 15:01, Frédéric LOUI <> a 
> > écrit :
> >
> > Hi Marcos,
> >
> > IÂ’d check real quick your config I have a question.
> >
> > This is the output on RIO0001:
> >
> > "show bridge <x>"
> >
> > RIO0001#sh bridge 1                                                                
> >                    packet           byte
> > iface  fwd   phys  tx    rx   drop  tx      rx     drop  
> > grp
> > bvi    true  true  0     0    0     0       0      0
> > sdn15  true  true  5560  0    1     575540  0      116
> > sdn16  true  true  5560  0    1     575540  0      116
> > sdn19  true  true  6216  684  1     595134  33044  116
> > sdn20  true  true  6216  684  1     595134  33044  116
> >
> >                                  packet   
> > Â Â Â Â Â Â Â Â  byte
> > addr            iface  time      tx    rx    drop  
> > tx     rx      drop
> > 004c.7c58.300a  bvi    00:00:56  1298  6830  0     62304  612712 
> >  0
> > 0c42.a15d.2f9c  sdn20  00:00:56  669   684   0     20430  33044 
> > Â  0
> > 0c42.a15d.3084Â  sdn19Â  00:00:56Â  671Â Â  684Â Â  0Â Â Â Â  20526Â  33044Â 
> > Â  0
> >
> >
> > RIO0001#sh bridge 2                                                                
> >                       packet            byte
> > iface     fwd   phys  tx    rx    drop  tx     rx     
> > drop  grp
> > bvi       true  true  0     0     0     0      0  
> > Â Â Â  0
> > sdn19.19  true  true  1246  268   0     44282  11792  0
> > sdn20.19  true  true  1638  1109  0     52892  48796  0
> >
> > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  
> > packet           byte
> > addr            iface     time      tx   rx    drop 
> >  tx     rx     drop
> > 0073.7101.3b3a  bvi       00:03:25  616  1370  0     27104  
> > 41100Â  0
> > 0c42.a15d.2f9c  sdn20.19  00:03:25  884  1109  0     30258  48796  0
> >
> > "end of show bridge <x>"
> >
> > ------------------------------
> >
> > interface sdn19
> > no description
> > mtu 1500
> > macaddr 006a.4247.1173
> > lldp enable
> > bridge-group 1
> > no shutdown
> > no log-link-change
> > exit
> > interface sdn19.19
> > no description
> > bridge-group 2
> > no shutdown
> > no log-link-change
> > exit
> >
> > ------------------------------
> >
> > RIO0001#sh run sdn20                                                               
> > interface sdn20
> > no description
> > mtu 1500
> > macaddr 001a.5b5c.306d
> > lldp enable
> > bridge-group 1
> > no shutdown
> > no log-link-change
> > exit
> > interface sdn20.19
> > no description
> > bridge-group 2
> > no shutdown
> > no log-link-change
> > exit
> >
> > Is it voluntary to:
> >
> > * To put  sdn19 in: bridge 1
> > * To put  sdn20 in: bridge 2
> >
> > * And sdn19.19 and sdn20.19 in bridge 2 ?
> >
> >
> > As you can see on freeRtr test case: http://sources.nop.hu/cfg/conn-bridge02.tst 
> > <http://sources.nop.hu/cfg/conn-bridge02.tst>
> > bridge-group @ sdn MAIN interface is not required. (IÂ’m talking under MC36 
> > control here :) )
> >
> > If this is not mandatory as per your opinion, I would try:
> >
> >
> > conf t
> > int sdn19
> > no  bridge-group 1
> > exit
> > int sdn19.19
> > no  bridge-group 2
> > bridge-group 2
> > exit
> > int sdn20
> > no  bridge-group 2
> > exit
> > int sdn20.19
> > no bridge-group 2
> > bridge-group 2
> > exit
> > end
> >
> > If you notice we configured and reconfigured some feature as this this try to 
> > trigger dataplane update.
> > Check if that works (shut/ no shut sdn<x> —> this will also trigger 
> > dataplane update)
> >
> > And if for any reasons dataplane table are messed up, retry to sync: clear 
> > process bffwd
> >
> > Please let us know if this has solved the situation.
> >
> > À bientôt,
> > --Â  Frederic
> >
> >
> >
> >
> > > Le 28 août 2021 à 14:54, Marcos Felipe Schwarz <> a 
> > > écrit :
> > >
> > > Hi everyone, IÂ’m trying to create a tagged VLAN between two ports. Can you 
> > > spot what's missing?
> > >
> > > 7:56
> > >
> > > RIO0001(cfg)#show config-differences
> > > vrf definition v2
> > > server p4lang p4
> > > export-vrf v2 2
> > > export-bridge 2
> > > export-port sdn19.19 202 0 0 0 0
> > > export-port sdn20.19 203 0 0 0 0
> > > export-port bvi2 204 0 0 0 0
> > > exit
> > > bridge 2
> > > mac-learn
> > > exit
> > > interface bvi2
> > > no description
> > > vrf forwarding v2
> > > ipv4 address 10.0.19.254 255.255.255.0
> > > no shutdown
> > > no log-link-change
> > > exit
> > > interface sdn19.19
> > > no description
> > > bridge-group 2
> > > no shutdown
> > > no log-link-change
> > > exit
> > > interface sdn20.19
> > > no description
> > > bridge-group 2
> > > no shutdown
> > > no log-link-change
> > > exit
> > >
> > > 7:57
> > >
> > > I have an untaged VLAN working on the same ports, so I'm sure the problem is 
> > > on my config
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Marcos Schwarz
> > >
> > >
> > >
> > > Gerente de P&D | R&D Manager
> > >
> > > Gerência de Execução de P&D em Ciberinfraestrutura | Management of R&D 
> > > Execution in Cyberinfrastructure
> > >
> > > Diretoria de Pesquisa e Desenvolvimento | Board of Research and Development
> > >
> > > RNP - Rede Nacional de Ensino e Pesquisa | Brazilian National Research and 
> > > Educational Network
> > >
> > > Promovendo o uso inovador de redes avançadas | Promoting the innovative use 
> > > of advanced networks
> > >
> > > http://www.rnp.br <http://www.rnp.br> | +55 (19) 3787- 3386 | Skype ID: 
> > > marcos.f.sch
> > >
> > > Campinas - SP - Brasil | E-mail: