Afternoon,
Having an issue with one of our 7048's. Has been working fine for quite sometime however after a power outage it now boots with the following:
Arista Networks Inc...
Aboot 2.0.9-1287509
Press Control-C now to enter Aboot shell
Booting flash:EOS.swi
[ 7.683625] Starting new kernel
Switching rootfs
Welcome to Arista Networks EOS 4.15.10M
Mounting filesystems: [ OK ]
Starting udev: [ OK ]
Setting hostname localhost: [ OK ]
Entering non-interactive startup
Starting TimeAgent: [ OK ]
Starting ProcMgr: [ OK ]
Starting EOS initialization stage 1: [ OK ]
ip6tables: Applying firewall rules: [ OK ]
iptables: Applying firewall rules: [ OK ]
iptables: Loading additional modules: nf_conntrack_tftp [ OK ]
Starting system logger: [ OK ]
Starting NorCal initialization:
System fpga miwok is unprogrammed and cannot be accessed,
possibly due to an interrupted or failed attempt at upgrading
the fpga. Attempted recovery in progress.
-----------------------------------------------------
Upgrading the miwok system fpga.
This process can take several minutes.
Please do not reboot your switch.
-----------------------------------------------------
Upgrade of the miwok system fpga completed successfully.
Power cycling the system after successfully upgrading all system fpgas.
Restarting system [ OK ]
[11:03:13] watchdog punch .
[11:03:15] watchdog punch .
[ 169.497190] SysRq : Remount R/O
[11:03:16] watchdog punch .
[11:03:16] watchdog punch .
[11:03:17] watchdog punch .
No scd device found on this machine
Arista Networks Inc...
Aboot 2.0.9-1287509
Press Control-C now to enter Aboot shell
Booting flash:EOS.swi
[ 7.783095] Starting new kernel
Switching rootfs
Welcome to Arista Networks EOS 4.15.10M
Mounting filesystems: [ OK ]
Starting udev: [ OK ]
Setting hostname localhost: [ OK ]
Entering non-interactive startup
Starting TimeAgent: [ OK ]
Starting ProcMgr: [ OK ]
Starting EOS initialization stage 1: [ OK ]
ip6tables: Applying firewall rules: [ OK ]
iptables: Applying firewall rules: [ OK ]
iptables: Loading additional modules: nf_conntrack_tftp [ OK ]
Starting system logger: [ OK ]
Starting NorCal initialization:
System fpga miwok is unprogrammed and cannot be accessed.
System functionality will be severely limited.
[ OK ]
Retrigger failed udev events[ OK ]
cat: /etc/slotid: No such file or directory
Starting mcelog daemon
Starting EOS initialization stage 2: [ OK ]
Starting Power On Self Test (POST): [ OK ]
Starting crond: [ OK ]
Completing EOS initialization (press ESC to skip): [ OK ]
Model and Serial Number: unknown
System RAM: 3978072 kB
Flash Memory size: 1.7G
It doesn't seem to know what model it is and will only show the management port also:
localhost>sh inv
System information
Model Description
------------------------ ----------------------------------------------------
HW Version Serial Number Mfg Date
----------- -------------- ----------
System has 1 port
Type Count
---------------- ----
Management 1
I've had a look around the web for some advice but most say it required a ticket into arista - which is not so helpful now as it is end of life.
Has anyone seen this before or had any success in rectifying the issue? I've tried reloading it from scratch however this alos doesn't appear to work.
Any help will be greatly appreciated!
Thanks.
Having an issue with one of our 7048's. Has been working fine for quite sometime however after a power outage it now boots with the following:
Arista Networks Inc...
Aboot 2.0.9-1287509
Press Control-C now to enter Aboot shell
Booting flash:EOS.swi
[ 7.683625] Starting new kernel
Switching rootfs
Welcome to Arista Networks EOS 4.15.10M
Mounting filesystems: [ OK ]
Starting udev: [ OK ]
Setting hostname localhost: [ OK ]
Entering non-interactive startup
Starting TimeAgent: [ OK ]
Starting ProcMgr: [ OK ]
Starting EOS initialization stage 1: [ OK ]
ip6tables: Applying firewall rules: [ OK ]
iptables: Applying firewall rules: [ OK ]
iptables: Loading additional modules: nf_conntrack_tftp [ OK ]
Starting system logger: [ OK ]
Starting NorCal initialization:
System fpga miwok is unprogrammed and cannot be accessed,
possibly due to an interrupted or failed attempt at upgrading
the fpga. Attempted recovery in progress.
-----------------------------------------------------
Upgrading the miwok system fpga.
This process can take several minutes.
Please do not reboot your switch.
-----------------------------------------------------
Upgrade of the miwok system fpga completed successfully.
Power cycling the system after successfully upgrading all system fpgas.
Restarting system [ OK ]
[11:03:13] watchdog punch .
[11:03:15] watchdog punch .
[ 169.497190] SysRq : Remount R/O
[11:03:16] watchdog punch .
[11:03:16] watchdog punch .
[11:03:17] watchdog punch .
No scd device found on this machine
Arista Networks Inc...
Aboot 2.0.9-1287509
Press Control-C now to enter Aboot shell
Booting flash:EOS.swi
[ 7.783095] Starting new kernel
Switching rootfs
Welcome to Arista Networks EOS 4.15.10M
Mounting filesystems: [ OK ]
Starting udev: [ OK ]
Setting hostname localhost: [ OK ]
Entering non-interactive startup
Starting TimeAgent: [ OK ]
Starting ProcMgr: [ OK ]
Starting EOS initialization stage 1: [ OK ]
ip6tables: Applying firewall rules: [ OK ]
iptables: Applying firewall rules: [ OK ]
iptables: Loading additional modules: nf_conntrack_tftp [ OK ]
Starting system logger: [ OK ]
Starting NorCal initialization:
System fpga miwok is unprogrammed and cannot be accessed.
System functionality will be severely limited.
[ OK ]
Retrigger failed udev events[ OK ]
cat: /etc/slotid: No such file or directory
Starting mcelog daemon
Starting EOS initialization stage 2: [ OK ]
Starting Power On Self Test (POST): [ OK ]
Starting crond: [ OK ]
Completing EOS initialization (press ESC to skip): [ OK ]
Model and Serial Number: unknown
System RAM: 3978072 kB
Flash Memory size: 1.7G
It doesn't seem to know what model it is and will only show the management port also:
localhost>sh inv
System information
Model Description
------------------------ ----------------------------------------------------
HW Version Serial Number Mfg Date
----------- -------------- ----------
System has 1 port
Type Count
---------------- ----
Management 1
I've had a look around the web for some advice but most say it required a ticket into arista - which is not so helpful now as it is end of life.
Has anyone seen this before or had any success in rectifying the issue? I've tried reloading it from scratch however this alos doesn't appear to work.
Any help will be greatly appreciated!
Thanks.
