Rare project developers

[Eoin Kenny <>]

Hi all,

Thank you all for your help and support. 

I now have a 100G up and working between our APS BF2556X-1T and an Arista 
DCS-7280QRA-C36S-F. 

Happy Friday!
Eoin

rare#show running-config interface sdn52                                      
                                                                              
                                                      
interface sdn52
 mtu 1500
 macaddr 003c.0925.5a7b
 lldp enable
 vrf forwarding CORE
 ipv4 address 192.168.52.1 255.255.255.252
 no shutdown
 no log-link-change
 exit
!

server p4lang p4
 export-vrf CORE 1
 export-port sdn50 140 100 1 1 0
 export-port sdn49 156 100 1 1 0
 export-port sdn52 172 100 1 1 0
 export-port sdn51 188 100 1 1 0
 interconnect ethernet0
 vrf p4
 exit
!
First 3 are just hard loop but the last one is a 100G to the Arista.
rare#show lldp neighbor                                                       
                                                                              
                                                      
interface  hostname                 iface         ipv4          ipv6
sdn49      rare                     sdn49         192.168.3.1   null
sdn50      rare                     sdn50         null          null
sdn51      rare                     sdn51         null          null
sdn52      arista                   Ethernet25/1  192.168.52.2  null

rare#ping 192.168.52.2 vrf CORE                                               
                                                                              
                                                      
pinging 192.168.52.2, src=null, vrf=CORE, cnt=5, len=64, df=false, tim=1000, 
gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 1, min/avg/max/dev 
rtt=0/0.0/0/0.0, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
rare#     
________________________________________
From: Alexander Gall <>
Sent: Friday 15 July 2022 10:08
To: Eoin Kenny
Cc: ; ; 
Subject: RE: [rare-dev] [RARE-users] RARE/freeRtr first release for [Wedge 
100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

CAUTION[External]: This email originated from outside of the organisation. Do 
not click on links or open the attachments unless you recognise the sender 
and know the content is safe.


Hi Eoin

On Fri, 15 Jul 2022 08:33:32 +0000, Eoin Kenny <> said:

> Hi Alex,
> Thanks for the explanation. I am still struggling with how to identify the 
> ports.

> Ports 1-16  are the Gearbox ports - 1/10/25G and I understand these will 
> not work.

Actually, they should work (kind of) with the version you're running
which still includes the Marvell "SAL" that manages the gearbox.

> Ports 17-32 are 10/25G
> Ports 33-48 are 10/25G
> Ports 49-56 are 10/25/40/50/100G - ie the 8 QSFP ports.

> I have 4 QSFPs installed in the box and I can see them  using the following 
> command.
bf-sde.bf_pltfm.qsfp> info

> ================
> Info for QSFP  :
> ================
> ---------------------------------------------------------------------------------------------------------------------
>                                                              Date     
> Nominal                 Power
> Port  Vendor           PN               rev Serial#          code     Bit 
> Rate     OUI        Class            Media
> ---------------------------------------------------------------------------------------------------------------------
>  49:  01    2206060016       220607   OEM              100G-QSFP-LR4-F  
> 25500 MBps   00:00:00   6 (4.5 W max.)   (SMF): 10 km
>  50:  01    2206060015       220607   OEM              100G-QSFP-LR4-F  
> 25500 MBps   00:00:00   6 (4.5 W max.)   (SMF): 10 km
>  51:  01    2206060017       220607   OEM              100G-QSFP-LR4-F  
> 25500 MBps   00:00:00   6 (4.5 W max.)   (SMF): 10 km
>  52:  01    2206060018       220607   OEM              100G-QSFP-LR4-F  
> 25500 MBps   00:00:00   6 (4.5 W max.)   (SMF): 10 km

bf-sde.pm> show -a
> -----+----+---+----+-------+----+--+--+---+---+---+--------+----------------+----------------+-
> PORT |MAC |D_P|P/PT|SPEED  |FEC |AN|KR|RDY|ADM|OPR|LPBK    |FRAMES RX       
> |FRAMES TX       |E
> 49/0 
> |20/0|156|2/28|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 49/1 
> |20/1|157|2/29|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 49/2 
> |20/2|158|2/30|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 49/3 
> |20/3|159|2/31|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 50/0 
> |22/0|140|2/12|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 50/1 
> |22/1|141|2/13|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 50/2 
> |22/2|142|2/14|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 50/3 
> |22/3|143|2/15|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 51/0 
> |16/0|188|2/60|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 51/1 
> |16/1|189|2/61|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 51/2 
> |16/2|190|2/62|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 51/3 
> |16/3|191|2/63|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 52/0 
> |18/0|172|2/44|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 52/1 
> |18/1|173|2/45|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 52/2 
> |18/2|174|2/46|-------|----|--|--|YES|---|---|--------|----------------|----------------|-
> 52/3 
> |18/3|175|2/47|-------|----|--|--|YES|---|---|--------|----------------|----------------|-

> So I think I should use port "sdn156" to identify the QSFP in port 49. Is 
> this correct?

Correct in the sense that you'll have to use "device port" #156 to
address lane 0 of connector 49.

> The reason I have doubts is that the output of "show p4land p4 port-names" 
> does not reference frontpanel-49/x or port 156.

> Any thoughts?

Yes, this is a flaw in the bf_forwarder which does not report the
proper frontpanel ports for the 2556. That needs to be fixed. The
output from bfshell is always correct.

You'll have to work around that by using the numbers from the D_P
column above directly, e.g. to configure port 49 for 100G (no FEC for
LR4)

export-port sdn49 156 100 1 1 0

--
Alex

> Regards
> Eoin

> rare#show p4lang p4 port-names
> num  name
> 0    frontpanel-1/0
> 13   frontpanel-10/0
> 14   frontpanel-11/0
> 15   frontpanel-12/0
> 28   frontpanel-13/0
> 29   frontpanel-14/0
> 30   frontpanel-15/0
> 31   frontpanel-16/0
> 44   frontpanel-17/0
> 45   frontpanel-18/0
> 46   frontpanel-19/0
> 1    frontpanel-2/0
> 47   frontpanel-20/0
> 60   frontpanel-21/0
> 61   frontpanel-22/0
> 62   frontpanel-23/0
> 63   frontpanel-24/0
> 176  frontpanel-25/0
> 177  frontpanel-26/0
> 178  frontpanel-27/0
> 179  frontpanel-28/0
> 160  frontpanel-29/0
> 2    frontpanel-3/0
> 161  frontpanel-30/0
> 162  frontpanel-31/0
> 163  frontpanel-32/0
> 3    frontpanel-4/0
> 4    frontpanel-5/0
> 5    frontpanel-6/0
> 6    frontpanel-7/0
> 7    frontpanel-8/0
> 12   frontpanel-9/0

> rare(cfg)#server p4lang p4
> rare(cfg-server)#export-port sdn156 ?
>   <num>           - port number
>   dynamic         - dynamic port number
>   frontpanel-1/0  - port number
>   frontpanel-10/0 - port number
>   frontpanel-11/0 - port number
>   frontpanel-12/0 - port number
>   frontpanel-13/0 - port number
>   frontpanel-14/0 - port number
>   frontpanel-15/0 - port number
>   frontpanel-16/0 - port number
>   frontpanel-17/0 - port number
>   frontpanel-18/0 - port number
>   frontpanel-19/0 - port number
>   frontpanel-2/0  - port number
>   frontpanel-20/0 - port number
>   frontpanel-21/0 - port number
>   frontpanel-22/0 - port number
>   frontpanel-23/0 - port number
>   frontpanel-24/0 - port number
>   frontpanel-25/0 - port number
>   frontpanel-26/0 - port number
>   frontpanel-27/0 - port number
>   frontpanel-28/0 - port number
>   frontpanel-29/0 - port number
>   frontpanel-3/0  - port number
>   frontpanel-30/0 - port number
>   frontpanel-31/0 - port number
>   frontpanel-32/0 - port number
>   frontpanel-4/0  - port number
>   frontpanel-5/0  - port number
>   frontpanel-6/0  - port number
>   frontpanel-7/0  - port number
>   frontpanel-8/0  - port number
>   frontpanel-9/0  - port number
> -----Original Message-----
> From: Alexander Gall <>
> Sent: Thursday 14 July 2022 07:44
> To: Eoin Kenny <>
> Cc: ; ; 
> Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release for [Wedge 
> 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

> CAUTION[External]: This email originated from outside of the organisation. 
> Do not click on links or open the attachments unless you recognise the 
> sender and know the content is safe.


> Hi Eoin

> We now understand what's happening wrt to the "Object not found"
> messages. The short answer is that they can be safely ignored :)

> The long answer is that the mapping from "logical" port designations in the 
> form <connector>/<channel> is chosen by the platform-dependent component of 
> the SDE. Tofino groups the serdes lanes into bunches of 4 and calls them a 
> "quad". This is natural for QSFP ports, where a quad maps to a connector 
> and the channels are the 4 lanes.

> The 2556 only has 8 QSFP ports and those are labelled like that, e.g. 49/0 
> is lane #0 of the first QSFP port, 49/1 is the second etc.

> All other ports are SFP and they are connected to infividual serdes lanes 
> where the quad-grouping is meaningless. So they have chosen to use a 
> different mapping scheme where the <channel> is always 0, i.e. 1/0, 2/0 up 
> to 48/0. Internally, 1/0 maps to quad #8, lane #0,
> 2/0 to quad #8, lane #1 for example.

> When freeRtr starts up, one component (called "bf_forwarder") tries to 
> determine the current status of ports. It does this by scanning all 
> <connector>/<channel> pairs (this is currently the only way to do it due to 
> a flaw in the SDE BFRT implementation). When the scan hits a non-zero 
> channel like 1/1, you get this error, because 1/1 simply doesn't exist on 
> this platform.

> What we need to do is make the bf_forwarder aware of the port assignments 
> of the 2556 so we only scan for existing ports.

> Simple, right? :)

> --
> Alex

> On Wed, 13 Jul 2022 10:59:50 +0000, Eoin Kenny <> said:

>> Hi Alex,
>> I installed did the "release-manager --install-experimental". All 
>> installed ok.

>> I had to do a cold reboot afterwards but now I see the physical ports.
>> Log is here:
>> https://github.com/sonicepk/BF2556X-1T-ONIE-freeRouter/blob/main/sde-f
>> ix

>> I still get the these error messages on boot. I assume I can ignore these?

>> [2022-07-13 12:48:23.374961] <info> 
>> :[./src/grpc/salGrpcServices.cpp::190]: Gearbox successfully started.
>> 2022-07-13 12:48:23.621300 BF_PIPE ERROR -
>> pipe_mgr_adt_mgr_get_ent_hdl_from_location:4148 Entry info not present
>> for action tabl 0x200000a, device id 0
>> 2022-07-13 12:48:23.643101 BF_PM ERROR -
>> bf_pm_port_front_panel_port_to_dev_port_get:4279
>> bf_pm_port_front_panel_port_to_dev_port_get: front port 1/1 : not
>> found
>> 2022-07-13 12:48:23.643163 BF_PAL ERROR - Unable to get the dev port
>> for dev : 0 : front panel port : 1/1 : Object not found (6)


>> Thanks
>> Eoin
>> ________________________________________
>> From: Alexander Gall <>
>> Sent: Wednesday 13 July 2022 11:23
>> To: Eoin Kenny
>> Cc: ; ; 
>> Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release for
>> [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

>> CAUTION[External]: This email originated from outside of the organisation. 
>> Do not click on links or open the attachments unless you recognise the 
>> sender and know the content is safe.


>> Hi Eoin

>> This problem was caused by a regression in the packaging of the SDE.
>> You should be able to get a working version with

>> # release-manager --install-git origin/master

>> or

>> # release-manager --install-experimental

>> if you need the newest freertr code.

>> Regards,
>> Alex

>> On Tue, 12 Jul 2022 17:52:30 +0200, Alexander Gall <> said:

>>> Hi Eoin
>>> On Tue, 12 Jul 2022 14:27:23 +0000, Eoin Kenny <> 
>>> said:

>>>> Hi Alex,
>>>> I need some more help, if you don't mind. I am working from the docs 
>>>> here:
>>>> http://docs.freertr.org/guides/installation/wedge100bf32/interface/

>>>> Firstly, when I run bfshell
>>>> root@localhost:~# bfshell
>>>> connect: Connection refused

>>> That means that the bf_switchd process isn't running.

>>>> root@localhost:~#

>>>> Also the "show p4land p4" now requires an additional parameter. The docs 
>>>> must be showing a different version of code for this command.

>>> Yes, csaba has made significant changes since release 1 and you're
>>> running now very new freertr code. The "port-names" option must have
>>> been added pretty recently as well, I've never seen it myself :)

>>> It seems that version release-1-61-g2a33342 is bad :( The bf_switchd
>>> process (or rather the APS 2556-sepcific "SAL") is failing with

>>> /nix/store/jqm46f8ccl4dcdq6cwm4lwrg5mmshlyn-aps-sal-refapp-9.7.2/bin/
>>> salRefApp: symbol lookup error:
>>> /nix/store/fbwz8nc3nqvl2d6h7031ky9bkqgjds4s-bf-sde-aps_bf2556-runtime
>>> -9.7.2-bf_router-artifacts/lib/libdriver.so: undefined symbol:
>>> rl_instream

>>> That's also why bfshell doesn't work.  I'll look into it and get back
>>> to you.

>>> --
>>> Alex

>>>> rare#show p4lang p4 port-names
>>>> num  name

>>>> rare#

>>>> I assume I should be seeing my P4 ports. Attached is a copy of my 
>>>> rtr-hw.txt file from /etc/feertr. Any suggestions?

>>>> Thanks for your help.
>>>> Regards
>>>> Eoin

>>>> rare#show p4lang p4 status
>>>> category       value
>>>> peer           ::
>>>> closed         3
>>>> reconn         0
>>>> since          1970-01-01 00:59:59
>>>> for            never
>>>> capability     null
>>>> platform       null
>>>> cpuport        0
>>>> dynamicid      65536 131072
>>>> messages sent  0
>>>> messages got   0
>>>> rounds done    0
>>>> last done      1970-01-01 00:59:59 (never ago)
>>>> time took      0
>>>> rounds skip    0
>>>> last skip      1970-01-01 00:59:59 (never ago)

>>>> rare#






>>>> ________________________________________
>>>> From: Alexander Gall <>
>>>> Sent: Monday 11 July 2022 09:59
>>>> To: Eoin Kenny
>>>> Cc: ; ; 
>>>> Subject: RE: [rare-dev] [RARE-users] RARE/freeRtr first release for
>>>> [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

>>>> CAUTION[External]: This email originated from outside of the 
>>>> organisation. Do not click on links or open the attachments unless you 
>>>> recognise the sender and know the content is safe.


>>>> Hi Eoin

>>>> On Mon, 11 Jul 2022 08:23:44 +0000, Eoin Kenny <> 
>>>> said:

>>>>> I suspect, I should have used DHCP rather than statically configuring 
>>>>> the IP address/default route when doing the installation from ONIE. 
>>>>> Anyway, I added a public IP/Default gateway to the Debian Host, 
>>>>> installed git and then the tna-? Commands worked fine.

>>>> Ok, happy to hear that :)

>>>>> One thing that was missing was adding the oath to release-manger for 
>>>>> the root user. I had to add the path 
>>>>> /nix/var/nix/profiles/RARE/bin/release-manager and then I was able to 
>>>>> run the command  "release-manager --switch-to-generation 2" as the root 
>>>>> user.

>>>> Yes, PATH is set via /etc/profile.d/RARE.sh, which is only read for
>>>> login shells, i.e. not if you use sudo. I should probably make this
>>>> work for non-login root shells as well.

>>>>> rare#tna-list-installed
>>>>> Generation Current Release Git Tag                    KernelID       
>>>>> Kernel Release            Platform                   Install date
>>>>> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>> 1         1       release-1                  Debian11_0     
>>>>> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-07-08 
>>>>> 01:00:18.258226175 +0200
>>>>> 2 *       2       release-1-61-g2a33342-free Debian11_0     
>>>>> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-07-11 
>>>>> 10:04:07.215572514 +0200


>>>>> rare#exit

>>>>> Here is the log of what I did, in case  you want to have a look.
>>>>> https://github.com/sonicepk/BF2556X-1T-ONIE-freeRouter/blob/main/tn
>>>>> a-install

>>>> Good, that looks as expected. Please don't hesitate to ask if
>>>> anything is unlcear, confusing or broken :) And, yes, we're working
>>>> on documentation...

>>>> --
>>>> Alex

>>>>> Thanks for your help, so far.

>>>>> Regards
>>>>> Eoin



>>>>> -----Original Message-----
>>>>> From: Alexander Gall <>
>>>>> Sent: Monday 11 July 2022 07:56
>>>>> To: Eoin Kenny <>
>>>>> Cc: ; ; 
>>>>> Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release for
>>>>> [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and APS6064X]

>>>>> CAUTION[External]: This email originated from outside of the 
>>>>> organisation. Do not click on links or open the attachments unless you 
>>>>> recognise the sender and know the content is safe.


>>>>> Hi Eoin

>>>>> Sorry, I had already left for the weekend.

>>>>> On Fri, 8 Jul 2022 15:07:56 +0000, Eoin Kenny <> 
>>>>> said:

>>>>>> Hi Alex,
>>>>>> Sorry for the delay.
>>>>>> I have rare-nix now on the box.

>>>>>> How do I use install this TNA version from freeRouter cli?

>>>>> Let me explain a bit about how this works. First of all, the 
>>>>> "tna-install-*" commands in the freerouter CLI actually just execute 
>>>>> variants of the "release-manager" command, which should be in your 
>>>>> PATH.  Some variants have to be run as root, so you either have to use 
>>>>> the full path /nix/var/nix/profiles/RARE/bin/release-manager, start a 
>>>>> root login shell (e.g. with "sudo su -") or source 
>>>>> /etc/profile.d/RARE.sh when you try to run them from Linux.

>>>>> To install the latest development version, use "tna-install-latest"
>>>>> or "release-manager --install-git origin/master". Alternatively,
>>>>> you can clone the rare-nix repo and execute "make install". All
>>>>> three will have the same result. However, the version of freerouter
>>>>> that will be installed will be the one that has been committed to
>>>>> the rare-nix
>>>>> repo:
>>>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare-nix/b
>>>>> rowse/overlay/freerouter/repo.nix

>>>>> In general, this will not be the newest version from 
>>>>> https://github.com/rare-freertr/freeRtr. To install the latest commit 
>>>>> of that repo, you have to use "tna-install-experimental" or 
>>>>> "release-manager --install-experimental".  There currently is no simple 
>>>>> equivalent with a Makefile target to achieve the same.  When you do 
>>>>> this, you have to be aware that it can result in a build failure or a 
>>>>> non-working system.

>>>>> Having said that, we still need to understand why some of these 
>>>>> commands are not working on your system. It appears that you can clone 
>>>>> the rare-nix repository but access to the Bitbucket API fails.

>>>>> The trace of the command you sent shows that curl terminates with 
>>>>> status code 6:

>>>>>>> + '[' 6 -gt 0 -a 6 -ne 255 ']'
>>>>>>> + echo 'Unexpected error, aborting'

>>>>> According to the curl man page, this means:

>>>>> 6      Couldn't resolve host. The given remote host was not resolved.

>>>>> This doesn't really make sense since at least git was able to resolve 
>>>>> bitbucket.software.geant.org when you cloned the repo, but that's where 
>>>>> I would start the investigation.

>>>>> --
>>>>> Alex

>>>>>> Thanks & regards
>>>>>> Eoin


>>>>>> rare@localhost:~/rare-nix$ ls
>>>>>> default.nix  rare             scripts                
>>>>>> update-dataplane.sh
>>>>>> Makefile     release-manager  services               
>>>>>> update-freerouter.sh
>>>>>> onie         release.nix      spec.json              
>>>>>> update-freerouter.txt
>>>>>> overlay      release-notes    spec-ONIE-SWITCH.json
>>>>>> rare@localhost:~/rare-nix$
>>>>>> ________________________________________
>>>>>> From: Alexander Gall <>
>>>>>> Sent: Friday 8 July 2022 15:00
>>>>>> To: Eoin Kenny
>>>>>> Cc: ; ; 
>>>>>> Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release
>>>>>> for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and
>>>>>> APS6064X]

>>>>>> CAUTION[External]: This email originated from outside of the 
>>>>>> organisation. Do not click on links or open the attachments unless you 
>>>>>> recognise the sender and know the content is safe.


>>>>>> On Fri, 8 Jul 2022 13:22:12 +0000, Eoin Kenny <> 
>>>>>> said:

>>>>>>> Interesting, git is not found.

>>>>>> Yes, that's why I said you might have to install it first :) The
>>>>>> update mechanism doesn't use the Debian packages, in case you're
>>>>>> wondering.

>>>>>> The debugging doesn't show a clear error, except that the curl
>>>>>> command doesn't get what it expects. Can you execute this please:

>>>>>> curl 
>>>>>> 'https://bitbucket.software.geant.org/rest/api/1.0/projects/RARE/repos/RARE-NIX/tags?limit=1000'

>>>>>> --
>>>>>> Alex

>>>>>>> root@localhost:/home/rare# git clone
>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git
>>>>>>> bash: git: command not found
>>>>>>> root@localhost:/home/rare# cd /
>>>>>>> root@localhost:/# ls
>>>>>>> bin   home            lib32       media  __platforms  sbin  usr
>>>>>>> boot  initrd.img      lib64       mnt    proc         srv   var
>>>>>>> dev   initrd.img.old  libx32      nix    root         sys   vmlinuz
>>>>>>> etc   lib             lost+found  opt    run          tmp   
>>>>>>> vmlinuz.old
>>>>>>> root@localhost:/#



>>>>>>> Also output below from

>>>>>>> $ bash -x /nix/var/nix/profiles/RARE/bin/release-manager
>>>>>>> --list-available

>>>>>>> Regards
>>>>>>> Eoin
>>>>>>> rare@localhost:~$ bash -x
>>>>>>> /nix/var/nix/profiles/RARE/bin/release-manager --list-available
>>>>>>> + set -e
>>>>>>> + set -o pipefail
>>>>>>> + shopt -s extglob
>>>>>>> + shopt -s inherit_errexit
>>>>>>> + PROFILE=/nix/var/nix/profiles/RARE
>>>>>>> + LIB=/nix/store/50wh9p15nlqbg3mc7snfhnmzhmi12lw6-release-manager
>>>>>>> + -1/l
>>>>>>> + ib
>>>>>>> + REPO_URL=https://bitbucket.software.geant.org/scm/rare/rare-nix
>>>>>>> + .git
>>>>>>> + API_URL=https://bitbucket.software.geant.org/rest/api/1.0/proje
>>>>>>> + cts/
>>>>>>> + RARE/repos/RARE-NIX
>>>>>>> + FREERTR_API_URL=https://api.github.com/repos/rare-freertr/freeR
>>>>>>> + tr FREERTR_REPO_URL=https://github.com/rare-freertr/freeRtr
>>>>>>> + PATH=/nix/var/nix/profiles/default/bin:/nix/store/z1qvlavy35wan
>>>>>>> + w5k5
>>>>>>> + 4fvvfffws5bvigj-coreutils-8.31/bin:/nix/store/3zbrk6iinij83qn4x
>>>>>>> + 139x 4b8vr1b94ax-util-linux-2.36-binn NIX_PATH=
>>>>>>> ++ basename /nix/var/nix/profiles/RARE/bin/release-manager
>>>>>>> + self=release-manager
>>>>>>> ++ getopt -l list-installed:: -l list-available -l
>>>>>>> ++ switch-to-generation: -l install-release: -l install-git: -l
>>>>>>> ++ install-local: -l install-experimental -l update-release
>>>>>>> + opts=' --list-available --'
>>>>>>> + '[' 0 -eq 0 ']'
>>>>>>> + '[' 1 -eq 0 ']'
>>>>>>> + eval set -- --list-available --
>>>>>>> ++ set -- --list-available --
>>>>>>> + '[' 2 -gt 0 ']'
>>>>>>> + case "$1" in
>>>>>>> + list_available=1
>>>>>>> + shift
>>>>>>> + '[' 1 -gt 0 ']'
>>>>>>> + case "$1" in
>>>>>>> + break
>>>>>>> + '[' 1 -gt 1 ']'
>>>>>>> + paths_to_rm=()
>>>>>>> + trap _cleanup EXIT TERM INT
>>>>>>> ++ tput colors
>>>>>>> + '[' -t 0 -a -1 -gt 1 ']'
>>>>>>> + declare -A gens gens_by_id gens_by_gitTag install_dates
>>>>>>> + installed_releases available_releases for path in
>>>>>>> + $PROFILE-*-link '[' -h /nix/var/nix/profiles/RARE-1-link ']'
>>>>>>> + add_path /nix/var/nix/profiles/RARE-1-link local path slice id
>>>>>>> + gen version gitTag rest path=/nix/var/nix/profiles/RARE-1-link
>>>>>>> ++ cat /nix/var/nix/profiles/RARE-1-link/slice
>>>>>>> + slice=Debian11_0:5.10.0-8-amd64:stordis_bf2556x_1t
>>>>>>> ++ cat /nix/var/nix/profiles/RARE-1-link/version
>>>>>>> + id=1:release-1:Debian11_0:5.10.0-8-amd64:stordis_bf2556x_1t
>>>>>>> ++ gen_from_path /nix/var/nix/profiles/RARE-1-link echo
>>>>>>> ++ /nix/var/nix/profiles/RARE-1-link sed -e
>>>>>>> ++ 's/.*-\([0-9]*\)-link$/\1/'
>>>>>>> + gen=1
>>>>>>> + '[' -n '' ']'
>>>>>>> + gens[$gen]=1:release-1:Debian11_0:5.10.0-8-amd64:stordis_bf2556
>>>>>>> + x_1t
>>>>>>> + gens_by_id[$id]=1
>>>>>>> ++ stat -c %z /nix/var/nix/profiles/RARE-1-link
>>>>>>> + install_dates[$gen]='2022-07-08 01:00:18.258226175 +0200'
>>>>>>> + read version gitTag rest
>>>>>>> ++ echo 1:release-1:Debian11_0:5.10.0-8-amd64:stordis_bf2556x_1t
>>>>>>> ++ tr : ' '
>>>>>>> + installed_releases[$version]=' release-1'
>>>>>>> + gens_by_gitTag[$gitTag]=1
>>>>>>> +++ readlink /nix/var/nix/profiles/RARE
>>>>>>> ++ gen_from_path RARE-1-link
>>>>>>> ++ echo RARE-1-link
>>>>>>> ++ sed -e 's/.*-\([0-9]*\)-link$/\1/'
>>>>>>> + current_gen=1
>>>>>>> ++ uname -r
>>>>>>> + kernel_release=5.10.0-8-amd64
>>>>>>> + . /etc/machine.conf
>>>>>>> ++ onie_version=master-201912041918stordis_bf2556x_1t_v1.20-dirty
>>>>>>> ++ onie_vendor_id=70567
>>>>>>> ++ onie_build_machine=stordis_bf2556x_1t
>>>>>>> ++ onie_machine_rev=0
>>>>>>> ++ onie_arch=x86_64
>>>>>>> ++ onie_build_platform=x86_64-stordis_bf2556x_1t-r0
>>>>>>> ++ onie_config_version=1
>>>>>>> ++ onie_build_date=2019-12-04T19:18-05:00
>>>>>>> ++ onie_partition_type=gpt
>>>>>>> ++ onie_kernel_version=4.9.95
>>>>>>> ++ onie_firmware=auto
>>>>>>> ++ onie_switch_asic=bft
>>>>>>> ++ onie_skip_ethmgmt_macs=no
>>>>>>> ++ onie_grub_image_name=grubx64.efi
>>>>>>> ++ onie_uefi_boot_loader=grubx64.efi
>>>>>>> ++ onie_uefi_arch=x64
>>>>>>> ++ onie_machine=stordis_bf2556x_1t
>>>>>>> ++ onie_platform=x86_64-stordis_bf2556x_1t-r0
>>>>>>> + platform=stordis_bf2556x_1t
>>>>>>> + '[' -z stordis_bf2556x_1t ']'
>>>>>>> + .
>>>>>>> + /nix/store/50wh9p15nlqbg3mc7snfhnmzhmi12lw6-release-manager-1/l
>>>>>>> + ib/a
>>>>>>> + ctivation.sh
>>>>>>> ++ SYSTEMD_DIR=/etc/systemd/system CONFIG_DIR=/etc/freertr
>>>>>>> ++ CONFIG_SW=/etc/freertr/rtr-sw.txt
>>>>>>> ++ CONFIG_HW=/etc/freertr/rtr-hw.txt SNMP_CONFIG_DIR=/etc/snmp
>>>>>>> ++ SNMPD_CONFIG=/etc/snmp/snmpd.conf
>>>>>>> ++ IFINDEX=/etc/snmp/ifindex.init SNMP_STATE_DIR=/var/lib/snmp
>>>>>>> ++ INTERFACE_CONFIG=/var/lib/snmp/interface.conf
>>>>>>> ++ SHELL_PROFILE=/etc/profile.d/RARE.sh
>>>>>>> + .
>>>>>>> + /nix/store/50wh9p15nlqbg3mc7snfhnmzhmi12lw6-release-manager-1/l
>>>>>>> + ib/a
>>>>>>> + pi.sh
>>>>>>> + '[' -n '' ']'
>>>>>>> + '[' -n 1 ']'
>>>>>>> + list_available
>>>>>>> + local version up_to_date tag branch_commits commit commit_head
>>>>>>> + commit_tag get_available_releases local tags tag version INFO
>>>>>>> + 'Checking for release tags of 
>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git'
>>>>>>> + echo 'INFO: Checking for release tags of 
>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git'
>>>>>>> INFO: Checking for release tags of
>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git
>>>>>>> ++ get_tags
>>>>>>> ++ local result
>>>>>>> +++ api_call '/tags?limit=1000'
>>>>>>> +++ local url api_url out http_code result api_url=
>>>>>>> +++ 
>>>>>>> url='https://bitbucket.software.geant.org/rest/api/1.0/projects/RARE/repos/RARE-NIX/tags?limit=1000'
>>>>>>> ++++ curl -s --write-out '\n%{http_code}\n' 
>>>>>>> 'https://bitbucket.software.geant.org/rest/api/1.0/projects/RARE/repos/RARE-NIX/tags?limit=1000'
>>>>>>> +++ out='
>>>>>>> 000'
>>>>>>> ++ result=
>>>>>>> + tags=
>>>>>>> + _cleanup
>>>>>>> + '[' 6 -gt 0 -a 6 -ne 255 ']'
>>>>>>> + echo 'Unexpected error, aborting'
>>>>>>> Unexpected error, aborting
>>>>>>> rare@localhost:~$


>>>>>>> ________________________________________
>>>>>>> From: Alexander Gall <>
>>>>>>> Sent: Friday 8 July 2022 12:36
>>>>>>> To: Eoin Kenny
>>>>>>> Cc: ; ;
>>>>>>> 
>>>>>>> Subject: Re: [rare-dev] [RARE-users] RARE/freeRtr first release
>>>>>>> for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and
>>>>>>> APS6064X]

>>>>>>> CAUTION[External]: This email originated from outside of the 
>>>>>>> organisation. Do not click on links or open the attachments unless 
>>>>>>> you recognise the sender and know the content is safe.


>>>>>>> On Fri, 8 Jul 2022 12:28:32 +0200, Alexander Gall <> 
>>>>>>> said:

>>>>>>>> On Fri, 8 Jul 2022 09:55:03 +0000, Eoin Kenny <> 
>>>>>>>> said:
>>>>>>>>> Hi all,
>>>>>>>>> Thank you for your help and patience. Happy to help with the docs 
>>>>>>>>> if I can.

>>>>>>>>> I have Internet access from the box but tna-list-available and 
>>>>>>>>> tna-install-experimental both fail. See below, any suggestions?

>>>>>>>> It seems like you can't reach bitbucket.software.geant.org. Can
>>>>>>>> you try (you might have to install git first)

>>>>>>>> git clone
>>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git

>>>>>>> Or, maybe better, you can send me the output of

>>>>>>> $ bash -x /nix/var/nix/profiles/RARE/bin/release-manager
>>>>>>> --list-available

>>>>>>> --
>>>>>>> Alex

>>>>>>>> --
>>>>>>>> Alex

>>>>>>>>> DNS is working. I also cannot find bf_shell.

>>>>>>>>> Thanks
>>>>>>>>> Eoin

>>>>>>>>> rare#ping www.freertr.org vrf oob resolving www.freertr.org for
>>>>>>>>> ipv4 ok!
>>>>>>>>> pinging 81.2.241.46, src=null, vrf=oob, cnt=5, len=64,
>>>>>>>>> tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, 
>>>>>>>>> sweep=false, multi=false !!!!!
>>>>>>>>> result=100%, recv/sent/lost/err=5/5/0/0, rtt
>>>>>>>>> min/avg/max/sum=36/36/37/183, ttl min/avg/max=235/235/235, tos 
>>>>>>>>> min/avg/max=164/164/164 rare#tna-list-installed
>>>>>>>>> Generation Current Release Git Tag                    KernelID      
>>>>>>>>>  Kernel Release            Platform                   Install date
>>>>>>>>> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>>>>>> 1 *       1       release-1                  Debian11_0     
>>>>>>>>> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-07-08 
>>>>>>>>> 01:00:18.258226175 +0200


>>>>>>>>> rare#tna-list-available
>>>>>>>>> INFO: Checking for release tags of
>>>>>>>>> https://bitbucket.software.geant.org/scm/rare/rare-nix.git
>>>>>>>>> Unexpected error, aborting


>>>>>>>>> rare#tna-install-experimental
>>>>>>>>> child 14518 created on 3
>>>>>>>>> child started
>>>>>>>>> Unexpected error, aborting

>>>>>>>>> process exited with 1536 code
>>>>>>>>> % returned 6
>>>>>>>>> rare#


>>>>>>>>> ________________________________________
>>>>>>>>> From: 
>>>>>>>>> <> on behalf of mc36
>>>>>>>>> <>
>>>>>>>>> Sent: Friday 8 July 2022 09:35
>>>>>>>>> To: ; Alexander Gall;
>>>>>>>>> 
>>>>>>>>> Subject: Re: [RARE-users] [rare-dev] RARE/freeRtr first release
>>>>>>>>> for [Wedge 100BF-32X, Wedge 100BF-32QS, Wedge 100BF-64X and
>>>>>>>>> APS6064X]

>>>>>>>>> CAUTION[External]: This email originated from outside of the 
>>>>>>>>> organisation. Do not click on links or open the attachments unless 
>>>>>>>>> you recognise the sender and know the content is safe.


>>>>>>>>> hi,

>>>>>>>>> On 7/8/22 10:08, Alexander Gall wrote:
>>>>>>>>>> On Fri, 8 Jul 2022 09:31:47 +0200, Fr  d  ric LOUI 
>>>>>>>>>> <> said:
>>>>>>>>>>
>>>>>>>>>>> Hi Eoin,
>>>>>>>>>>> http://docs.freertr.org/guides/installation/wedge100bf32/onie
>>>>>>>>>>> -nos
>>>>>>>>>>> -install/
>>>>>>>>>>
>>>>>>>>>> I think the question was where the login credentials are
>>>>>>>>>> documented. I can't find it myself on http://docs.freertr.org/
>>>>>>>>>> :(
>>>>>>>>>>

>>>>>>>>> what if frederic adds you to the
>>>>>>>>> https://github.com/rare-freertr org, then you can easily add/edit 
>>>>>>>>> info there as it's a github pages?

>>>>>>>>> thanks,
>>>>>>>>> cs
>>>>>> --
>>>>>> Alexander Gall, Network

>>>>>> SWITCH
>>>>>> Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268
>>>>>> 15 15, direct +41 44 268 15 22 https://switch.ch
>>>>>> https://swit.ch/linkedin https://swit.ch/twitter
--
Alexander Gall, Network

SWITCH
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 15, direct +41 44 268 15 22
https://switch.ch https://swit.ch/linkedin  https://swit.ch/twitter