Interfaces not available on as7712

Hello,

I'm very new to the world of open networking so I apologize in advance for my ignorance.

I've freshly installed SONiC onto an AS7712-32X but am unable to get any of the interfaces to be detected. I haven't performed any configuration but would expect things to work out of the box. I also haven't been able to find much helpful documentation related to initial configuration aside from the install, so if there's additional documentation I could be pointed towards, that would be appreciated.

Here's the environment:

admin@sonic:~$ show version

SONiC Software Version: SONiC.HEAD.112-dirty-20191027.052816
Distribution: Debian 9.11
Kernel: 4.9.0-9-2-amd64
Build commit: 040672c9
Build date: Sun Oct 27 05:39:49 UTC 2019
Built by: johnar@jenkins-worker-4

Platform: x86_64-accton_as7712_32x-r0
HwSKU: Accton-AS7712-32X
ASIC: broadcom
Serial Number: 771232X1633015
Uptime: 16:05:31 up 54 min,  1 user,  load average: 0.08, 0.04, 0.04

Docker images:
REPOSITORY                 TAG                              IMAGE ID            SIZE
docker-syncd-brcm          HEAD.112-dirty-20191027.052816   a19acaa971c8        391MB
docker-syncd-brcm          latest                           a19acaa971c8        391MB
docker-fpm-frr             HEAD.112-dirty-20191027.052816   5f15aa490872        319MB
docker-fpm-frr             latest                           5f15aa490872        319MB
docker-sflow               HEAD.112-dirty-20191027.052816   e8430c36ac3f        303MB
docker-sflow               latest                           e8430c36ac3f        303MB
docker-lldp-sv2            HEAD.112-dirty-20191027.052816   e8084636e9c0        298MB
docker-lldp-sv2            latest                           e8084636e9c0        298MB
docker-dhcp-relay          HEAD.112-dirty-20191027.052816   f173b3468d77        288MB
docker-dhcp-relay          latest                           f173b3468d77        288MB
docker-database            HEAD.112-dirty-20191027.052816   699ef9af44cc        280MB
docker-database            latest                           699ef9af44cc        280MB
docker-snmp-sv2            HEAD.112-dirty-20191027.052816   b9b721f55d8d        334MB
docker-snmp-sv2            latest                           b9b721f55d8d        334MB
docker-orchagent           HEAD.112-dirty-20191027.052816   6025721bfdff        320MB
docker-orchagent           latest                           6025721bfdff        320MB
docker-teamd               HEAD.112-dirty-20191027.052816   c860d03ae221        302MB
docker-teamd               latest                           c860d03ae221        302MB
docker-sonic-telemetry     HEAD.112-dirty-20191027.052816   83d9881e22a8        303MB
docker-sonic-telemetry     latest                           83d9881e22a8        303MB
docker-router-advertiser   HEAD.112-dirty-20191027.052816   a68d4760e593        280MB
docker-router-advertiser   latest                           a68d4760e593        280MB
docker-platform-monitor    HEAD.112-dirty-20191027.052816   e3658025cdc5        328MB
docker-platform-monitor    latest                           e3658025cdc5        328MB

The output of show interfaces status is empty and I can't figure out why. I've noticed about half of the docker containers have exited but I'm not sure if this is expected or not. As you can see, the snmp container has a non-zero exit code which seems suspect.

admin@sonic:~$ docker ps -a
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS                           PORTS               NAMES
1b788eb4bafb        docker-dhcp-relay:latest          "/usr/bin/docker_ini…"   59 minutes ago      Exited (0) About an hour ago                         dhcp_relay
db28afd7d3bc        docker-syncd-brcm:latest          "/usr/bin/supervisord"   59 minutes ago      Exited (0) About an hour ago                         syncd
c5c349cfc0c9        docker-router-advertiser:latest   "/usr/bin/supervisord"   59 minutes ago      Exited (0) About an hour ago                         radv
c485a2d0ed28        docker-snmp-sv2:latest            "/usr/bin/supervisord"   59 minutes ago      Exited (137) About an hour ago                       snmp
9a8167a589de        docker-teamd:latest               "/usr/bin/supervisord"   59 minutes ago      Up About an hour                                     teamd
13da60a6806b        docker-sflow:latest               "/usr/bin/supervisord"   59 minutes ago      Exited (0) About an hour ago                         sflow
7959e0b688c4        docker-orchagent:latest           "/usr/bin/supervisord"   59 minutes ago      Exited (0) About an hour ago                         swss
c6a656c806a1        docker-platform-monitor:latest    "/usr/bin/docker_ini…"   59 minutes ago      Up About an hour                                     pmon
0053647f5fe7        docker-fpm-frr:latest             "/usr/bin/supervisord"   About an hour ago   Up About an hour                                     bgp
c1e163ccf3d4        docker-lldp-sv2:latest            "/usr/bin/supervisord"   About an hour ago   Up About an hour                                     lldp
23efef69d648        docker-sonic-telemetry:latest     "/usr/bin/supervisord"   About an hour ago   Up About an hour                                     telemetry
438f3bf3c6fd        docker-database:latest            "/usr/local/bin/dock…"   About an hour ago   Up About an hour

Additionally, I found that the orchagent within the swss container is being aborted which also seems suspect to me.

admin@sonic:~$ docker logs swss
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2019-10-28 15:15:22,714 CRIT Set uid to user 0
2019-10-28 15:15:22,714 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-10-28 15:15:22,738 INFO RPC interface 'supervisor' initialized
2019-10-28 15:15:22,738 INFO supervisord started with pid 1
2019-10-28 15:15:23,741 INFO spawned: 'supervisor-proc-exit-listener' with pid 28
2019-10-28 15:15:23,745 INFO spawned: 'start.sh' with pid 29
2019-10-28 15:15:24,878 INFO success: supervisor-proc-exit-listener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:24,879 INFO success: start.sh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:27,497 INFO spawned: 'rsyslogd' with pid 45
2019-10-28 15:15:28,503 INFO success: rsyslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:29,232 INFO spawned: 'orchagent' with pid 50
2019-10-28 15:15:30,235 INFO success: orchagent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:31,026 INFO spawned: 'restore_neighbors' with pid 61
2019-10-28 15:15:31,038 INFO success: restore_neighbors entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-10-28 15:15:32,353 INFO spawned: 'portsyncd' with pid 71
2019-10-28 15:15:33,340 INFO exited: restore_neighbors (exit status 0; expected)
2019-10-28 15:15:34,344 INFO success: portsyncd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:35,201 INFO spawned: 'neighsyncd' with pid 80
2019-10-28 15:15:36,235 INFO success: neighsyncd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:36,915 INFO spawned: 'swssconfig' with pid 83
2019-10-28 15:15:36,916 INFO success: swssconfig entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-10-28 15:15:37,606 INFO spawned: 'vrfmgrd' with pid 90
2019-10-28 15:15:38,611 INFO success: vrfmgrd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:39,234 INFO spawned: 'vlanmgrd' with pid 100
2019-10-28 15:15:40,238 INFO success: vlanmgrd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:40,859 INFO spawned: 'intfmgrd' with pid 117
2019-10-28 15:15:41,703 INFO exited: swssconfig (exit status 0; expected)
2019-10-28 15:15:42,707 INFO success: intfmgrd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:43,346 INFO spawned: 'portmgrd' with pid 120
2019-10-28 15:15:43,882 INFO exited: orchagent (terminated by SIGABRT (core dumped); not expected)
2019-10-28 15:15:43,885 WARN received SIGTERM indicating exit request
2019-10-28 15:15:43,886 INFO waiting for vrfmgrd, neighsyncd, intfmgrd, portmgrd, start.sh, portsyncd, vlanmgrd, supervisor-proc-exit-listener, rsyslogd to die
2019-10-28 15:15:44,887 INFO success: portmgrd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-28 15:15:44,896 INFO stopped: vrfmgrd (terminated by SIGTERM)
2019-10-28 15:15:45,496 INFO stopped: portmgrd (terminated by SIGTERM)
2019-10-28 15:15:45,509 INFO stopped: intfmgrd (terminated by SIGTERM)
2019-10-28 15:15:45,512 INFO stopped: vlanmgrd (terminated by SIGTERM)
2019-10-28 15:15:46,110 INFO stopped: neighsyncd (terminated by SIGTERM)
2019-10-28 15:15:46,112 INFO stopped: portsyncd (terminated by SIGTERM)
2019-10-28 15:15:46,117 INFO stopped: rsyslogd (exit status 0)
2019-10-28 15:15:46,118 INFO stopped: start.sh (terminated by SIGTERM)
2019-10-28 15:15:46,121 INFO stopped: supervisor-proc-exit-listener (terminated by SIGTERM)

I'm unfortunately not familiar enough with this project or open networking to successfully debug this and I haven't been able to find much documentation online. I'm also unsure if this is a bug or just a misconfiguration.

sonic-net / SONiC

Interfaces not available on as7712 #509

458