Interfaces not seen on AS5812-54X #562
Comments
|
Did you manage to get anywhere with this? I also have this problem |
|
Hi,
unfortunately no, I gave up and switched to other tasks after many weeks of
unsuccessful attempts =(
Sincerely,
Simone.
Il giorno mer 10 giu 2020 alle ore 23:08 Andy Powell <
notifications@github.com> ha scritto:
… Did you manage to get anywhere with this? I also have this problem
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#562 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3QEN3RFFUNTHDANLX7IODRV7Y5FANCNFSM4KXG3JRQ>
.
|
|
Hi everyone! Im also find this issues today as I try to install the images on the switch. When I see at the supported devices and platform, total port is 72 x 10G ports, eventhough on the real switch is 54 ports (48x10G and 6x40G). I dont know exactly what is the problem.
And I already use the latest version:
All the front port will be disabled, eventhough the status is UP. I try to shutdown then startup the port, output still same. Cant configure anything to the port. Hopefully someone have the answer. |
|
In #546, @Lewis-Kang mentioned that SAI package released by Broadcom doesn't support TD2+ ASIC. |
|
Also in sonic-net/sonic-buildimage#3428, the author (roylee123) mentioned that the SDK config is not ready yet. Only access to peripherals are ready! |
Hi Kiniton, thank you so much for providing another information about this issue, it really helps me a lot. So its more like the asic which not supported yet. |
|
@hantekno I am a newbie and struggling to make this working myself. The more I gathered the info, it seems nobody actually gets this to work yet. |
|
@kitinon yeah, I think this is the issue with TD2+ asic. Anyway, appreciate your help so much, thanks! |
|
@hantekno So, can you point me to any free NOS that works on AS5812-54X? What your switch is running on at the moment? |
|
@kitinon actually im quite new in this field too. I know several NOS name like stratum, danos, cord besides of sonic. Currently im running on white commercial NOS. But I suggest you to search for this: https://docs.trellisfabric.org/1.12/supported-hardware.html As in there ONOS control plane support 5812-54X. But its a part of CORD Node, where you can find the material at https://www.opennetworking.org/cord And For stratum you can found out in here: |
|
I have tried Stratum without any luck. There is no config files available
for AS5812.
At the moment, I am trying to compile ONL to 18 July 2017 version where I
found ofdpa_3.0 EA5 that works on the that version. A blog by Phil Huang
shows that.
BTW, what do you mean by "White commercial NOS"?
…On Sat, Oct 3, 2020, 10:30 AM hantekno ***@***.***> wrote:
@kitinon <https://github.com/kitinon> actually im quite new in this field
too. I know several NOS name like stratum, danos, cord besides of sonic.
Currently im running on white commercial NOS. But I suggest you to search
for this:
https://docs.trellisfabric.org/1.12/supported-hardware.html
As in there ONOS control plane support 5812-54X. But its a part of CORD
Node, where you can find the material at
https://www.opennetworking.org/cord
And
https://guide.opencord.org
For stratum you can found out in here:
https://github.com/stratum/stratum
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#562 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGD3FTKM4V2IHEW6BSRD5LSI2LGHANCNFSM4KXG3JRQ>
.
|
Yup stratum doesnt support 5812. For ONL I havent tested it yet. |
|
The latest Edgecore SONiC build appears to support the AS5812-54X: The latest Git master image ( |
|
@toreanderson is correct - installing that particular build from EdgeCore got SONiC working on these switches again. I had to sign up for access to their support site to get access to it, but it seems to work well. I'm not sure if they contribute support back to the main project, but it would be great if mainline had this same support. |
|
Hello @brent-blood |
|
Comulus linux is the right choice
…On Sat, Feb 18, 2023, 09:09 vishone ***@***.***> wrote:
Hello @brent-blood <https://github.com/brent-blood>
I am also facing this problem at the moment, can you please share the
correct software, thank you very much。
—
Reply to this email directly, view it on GitHub
<#562 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3HWAMUIFSSEHLIF3HPIN3WYBYTFANCNFSM4KXG3JRQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We have limited funds, so we can't pay the license fee for Cumulus. |
|
As I also mentioned in https://github.com/Broadcom-Switch/SAI/issues/15#issuecomment-1435529612, Edge-Core's SONiC distribution supports the AS5812-54X. It's free, but you need to create an account in Edge-Core's support portal and request access to be able to download it. Instructions are found here: https://support.edge-core.com/hc/en-us/articles/900003896906-Get-authorization-and-download-Enterprise-SONiC-Distribution-by-Edgecore |
I've installed SONiC into Accton AS5812-54X, but I am unable to see any interfaces in the CLI.
How can I fix the issue? Any help would be much appreciated.
root@sonic:~# show version
SONiC Software Version: SONiC.HEAD.202-dirty-20200217.042028
Distribution: Debian 9.12
Kernel: 4.9.0-11-2-amd64
Build commit: 4afb56da
Build date: Mon Feb 17 04:27:49 UTC 2020
Built by: johnar@jenkins-worker-8
Platform: x86_64-accton_as5812_54x-r0
HwSKU: Accton-AS5812-54X
ASIC: broadcom
Serial Number: 581254X1742123
Uptime: 17:12:31 up 3:35, 1 user, load average: 0.25, 0.36, 0.41
Docker images:
REPOSITORY TAG IMAGE ID SIZE
docker-syncd-brcm HEAD.202-dirty-20200217.042028 31ce59cc6906 435MB
docker-syncd-brcm latest 31ce59cc6906 435MB
docker-router-advertiser HEAD.202-dirty-20200217.042028 e6b6d25fa92b 288MB
docker-router-advertiser latest e6b6d25fa92b 288MB
docker-sonic-mgmt-framework HEAD.202-dirty-20200217.042028 03099a75cdd4 425MB
docker-sonic-mgmt-framework latest 03099a75cdd4 425MB
docker-platform-monitor HEAD.202-dirty-20200217.042028 fe925968d890 339MB
docker-platform-monitor latest fe925968d890 339MB
docker-fpm-frr HEAD.202-dirty-20200217.042028 67072a8c53d9 332MB
docker-fpm-frr latest 67072a8c53d9 332MB
docker-sflow HEAD.202-dirty-20200217.042028 9a452b4f58e8 312MB
docker-sflow latest 9a452b4f58e8 312MB
docker-lldp-sv2 HEAD.202-dirty-20200217.042028 cdef8ef7c801 309MB
docker-lldp-sv2 latest cdef8ef7c801 309MB
docker-dhcp-relay HEAD.202-dirty-20200217.042028 44550b864134 298MB
docker-dhcp-relay latest 44550b864134 298MB
docker-database HEAD.202-dirty-20200217.042028 da41026bbf79 288MB
docker-database latest da41026bbf79 288MB
docker-teamd HEAD.202-dirty-20200217.042028 155dda55f2f0 312MB
docker-teamd latest 155dda55f2f0 312MB
docker-snmp-sv2 HEAD.202-dirty-20200217.042028 e7431be2e281 345MB
docker-snmp-sv2 latest e7431be2e281 345MB
docker-orchagent HEAD.202-dirty-20200217.042028 d441b1eb4856 330MB
docker-orchagent latest d441b1eb4856 330MB
docker-nat HEAD.202-dirty-20200217.042028 d43e89cd4deb 314MB
docker-nat latest d43e89cd4deb 314MB
docker-sonic-telemetry HEAD.202-dirty-20200217.042028 894b34614127 349MB
docker-sonic-telemetry latest 894b34614127 349MB
accton_as5812_util.py sff 1
/sys/bus/i2c/devices/2-0050/eeprom:
00000000 03 04 00 00 00 00 08 00 00 00 00 01 0d 00 00 00 |................|
00000010 00 00 64 00 4f 45 4d 20 20 20 20 20 20 20 20 20 |..d.OEM |
00000020 20 20 20 20 00 00 00 00 53 46 50 2d 54 20 20 20 | ....SFP-T |
00000030 20 20 20 20 20 20 20 20 31 2e 30 20 00 00 00 7b | 1.0 ...{|
00000040 00 1a 00 00 4d 38 30 54 30 31 39 36 20 20 20 20 |....M80T0196 |
00000050 20 20 20 20 31 39 31 30 33 30 20 20 00 00 00 61 | 191030 ...a|
00000060 00 00 11 7b 44 a3 a3 0c cb bc 57 93 70 22 2e 0b |...{D.....W.p"..|
00000070 45 fa f5 00 00 00 00 00 00 00 00 00 59 8a 7a fd |E...........Y.z.|
00000080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000100
root@sonic:~# show interfaces transceiver eeprom Ethernet1
Ethernet1: SFP EEPROM Not detected
root@sonic:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether a8:2b:b5:bd:25:49 brd ff:ff:ff:ff:ff:ff
3: bcm0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 02:10:18:0f:86:70 brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether d2:85:a5:9e:28:68 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:b5:8d:8b:bc brd ff:ff:ff:ff:ff:ff
7: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 12:f7:3e:06:15:bb brd ff:ff:ff:ff:ff:ff
10: Bridge: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether fa:7e:3a:46:aa:ad brd ff:ff:ff:ff:ff:ff
11: dummy: <BROADCAST,NOARP> mtu 1500 qdisc noop master Bridge state DOWN mode DEFAULT group default qlen 1000
link/ether fa:7e:3a:46:aa:ad brd ff:ff:ff:ff:ff:ff
12: Loopback0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 12:39:ed:1d:92:2e brd ff:ff:ff:ff:ff:ff
The text was updated successfully, but these errors were encountered: