Lost and moved interfaces on a 1000A

[ncmreynolds]

Sorry to make my first post a question, I used to be registered on the old forum some time back but haven't used this new one. I've done a little search but can't see anything.

We have some old 1000As and they make a good test environment for FortiOS 4, which most of our estate runs. Just yesterday I updated to 4.0MR3 patch 18 on one of these and afterwards lost connectivity to it.

It would seem that two of the ports have stopped working. Port 1 as far as the device is concerned now appears on physical port 5, port 2 physical port 6. Ports 7-10 are as per normal and ports 3 & 4 seem to have stopped working completely. Prior to the update this was a 100% functional device.

Doing a 'diagnose hardware lspci' shows only eight network devices, not ten like our other 1000A. Completely wiping the system and reinstalling from TFTP was done, mostly as a last guess and it didn't help.

This is really weird, any ideas? I'm unconvinced it is a hardware fault as ports 1 & 2 worked prior to the update. I connected via port 1 to factory reset and update it.

This feels like an issue with PCI misconfiguration that can be resolved by messing with 'diagnose hardware setpci' but I really would be groping about in the dark there.

[ncmreynolds]

Here's the lspci from both devices, with the second one missing a couple of interfaces. Interesting to note the revision differences in the components...

vpn # diagnose hardware lspci -G

Trying method 1......cannot open /sys/bus/pci...No.

Trying method 2......using /proc/bus/pci...OK

Decided to use Linux-proc

00:00.0 Host bridge: Intel Corporation Unknown device 3590 (rev 0c)

00:00.1 Class ff00: Intel Corporation Unknown device 3591 (rev 0c)

00:02.0 PCI bridge: Intel Corporation Unknown device 3595 (rev 0c)

00:03.0 PCI bridge: Intel Corporation Unknown device 3596 (rev 0c)

00:04.0 PCI bridge: Intel Corporation Unknown device 3597 (rev 0c)

00:05.0 PCI bridge: Intel Corporation Unknown device 3598 (rev 0c)

00:06.0 PCI bridge: Intel Corporation Unknown device 3599 (rev 0c)

00:07.0 PCI bridge: Intel Corporation Unknown device 359a (rev 0c)

00:1c.0 PCI bridge: Intel Corporation Unknown device 25ae (rev 02)

00:1d.0 USB Controller: Intel Corporation Unknown device 25a9 (rev 02)

00:1d.1 USB Controller: Intel Corporation Unknown device 25aa (rev 02)

00:1d.4 System peripheral: Intel Corporation Unknown device 25ab (rev 02)

00:1d.5 PIC: Intel Corporation Unknown device 25ac (rev 02)

00:1d.7 USB Controller: Intel Corporation Unknown device 25ad (rev 02)

00:1e.0 PCI bridge: Intel Corporation Unknown device 244e (rev 0a)

00:1f.0 ISA bridge: Intel Corporation Unknown device 25a1 (rev 02)

00:1f.1 IDE interface: Intel Corporation Unknown device 25a2 (rev 02)

00:1f.2 IDE interface: Intel Corporation Unknown device 25a3 (rev 02)

00:1f.3 SMBus: Intel Corporation Unknown device 25a4 (rev 02)

00:1f.7 SMBus: Intel Corporation Unknown device 25a8 (rev 02)

01:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b3)

02:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

02:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

02:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b3)

04:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b3)

05:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

05:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

05:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b3)

07:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b3)

08:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

08:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

08:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b3)

0a:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b3)

0b:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

0b:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

0b:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b3)

0d:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b3)

0e:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

0e:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev 01)

0e:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b3)

10:00.0 PCI bridge: Intel Corporation Unknown device 0329 (rev 09)

10:00.1 PIC: Intel Corporation Unknown device 0326 (rev 09)

10:00.2 PCI bridge: Intel Corporation Unknown device 032a (rev 09)

10:00.3 PIC: Intel Corporation Unknown device 0327 (rev 09)

11:01.0 Network and computing encryption device: Fujitsu Microelectr., Inc. Unknown device 4005 (rev 01)

FGT1KA3607502811 # diagnose hardware lspci -G

Trying method 1......cannot open /sys/bus/pci...No.

Trying method 2......using /proc/bus/pci...OK

Decided to use Linux-proc

00:00.0 Host bridge: Intel Corporation Unknown device 3590 (rev 0c)

00:00.1 Class ff00: Intel Corporation Unknown device 3591 (rev 0c)

00:02.0 PCI bridge: Intel Corporation Unknown device 3595 (rev 0c)

00:03.0 PCI bridge: Intel Corporation Unknown device 3596 (rev 0c)

00:04.0 PCI bridge: Intel Corporation Unknown device 3597 (rev 0c)

00:05.0 PCI bridge: Intel Corporation Unknown device 3598 (rev 0c)

00:06.0 PCI bridge: Intel Corporation Unknown device 3599 (rev 0c)

00:07.0 PCI bridge: Intel Corporation Unknown device 359a (rev 0c)

00:1c.0 PCI bridge: Intel Corporation Unknown device 25ae (rev 02)

00:1d.0 USB Controller: Intel Corporation Unknown device 25a9 (rev 02)

00:1d.1 USB Controller: Intel Corporation Unknown device 25aa (rev 02)

00:1d.4 System peripheral: Intel Corporation Unknown device 25ab (rev 02)

00:1d.5 PIC: Intel Corporation Unknown device 25ac (rev 02)

00:1d.7 USB Controller: Intel Corporation Unknown device 25ad (rev 02)

00:1e.0 PCI bridge: Intel Corporation Unknown device 244e (rev 0a)

00:1f.0 ISA bridge: Intel Corporation Unknown device 25a1 (rev 02)

00:1f.1 IDE interface: Intel Corporation Unknown device 25a2 (rev 02)

00:1f.2 IDE interface: Intel Corporation Unknown device 25a3 (rev 02)

00:1f.3 SMBus: Intel Corporation Unknown device 25a4 (rev 02)

00:1f.7 SMBus: Intel Corporation Unknown device 25a8 (rev 02)

01:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

02:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

02:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

02:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

04:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

05:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

05:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

05:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

0a:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

0b:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0b:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0b:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

0d:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

0e:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0e:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0e:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

10:00.0 PCI bridge: Intel Corporation Unknown device 0329 (rev 09)

10:00.1 PIC: Intel Corporation Unknown device 0326 (rev 09)

10:00.2 PCI bridge: Intel Corporation Unknown device 032a (rev 09)

10:00.3 PIC: Intel Corporation Unknown device 0327 (rev 09)

11:01.0 Network and computing encryption device: Fujitsu Microelectr., Inc. Unknown device 4005 (rev 01)

[rwpatterson]

Sorry, but my device shows as your working one does. I have no clue what the deal may be...

Trying method 1......cannot open /sys/bus/pci...No.

Trying method 2......using /proc/bus/pci...OK

Decided to use Linux-proc

00:00.0 Host bridge: Intel Corporation Unknown device 3590 (rev 0c)

00:00.1 Class ff00: Intel Corporation Unknown device 3591 (rev 0c)

00:02.0 PCI bridge: Intel Corporation Unknown device 3595 (rev 0c)

00:03.0 PCI bridge: Intel Corporation Unknown device 3596 (rev 0c)

00:04.0 PCI bridge: Intel Corporation Unknown device 3597 (rev 0c)

00:05.0 PCI bridge: Intel Corporation Unknown device 3598 (rev 0c)

00:06.0 PCI bridge: Intel Corporation Unknown device 3599 (rev 0c)

00:07.0 PCI bridge: Intel Corporation Unknown device 359a (rev 0c)

00:1c.0 PCI bridge: Intel Corporation Unknown device 25ae (rev 02)

00:1d.0 USB Controller: Intel Corporation Unknown device 25a9 (rev 02)

00:1d.1 USB Controller: Intel Corporation Unknown device 25aa (rev 02)

00:1d.4 System peripheral: Intel Corporation Unknown device 25ab (rev 02)

00:1d.5 PIC: Intel Corporation Unknown device 25ac (rev 02)

00:1d.7 USB Controller: Intel Corporation Unknown device 25ad (rev 02)

00:1e.0 PCI bridge: Intel Corporation Unknown device 244e (rev 0a)

00:1f.0 ISA bridge: Intel Corporation Unknown device 25a1 (rev 02)

00:1f.1 IDE interface: Intel Corporation Unknown device 25a2 (rev 02)

00:1f.2 IDE interface: Intel Corporation Unknown device 25a3 (rev 02)

00:1f.3 SMBus: Intel Corporation Unknown device 25a4 (rev 02)

00:1f.7 SMBus: Intel Corporation Unknown device 25a8 (rev 02)

01:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

02:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

02:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

02:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

04:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

05:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

05:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

05:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

07:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

08:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

08:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

08:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

0a:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

0b:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0b:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0b:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

0d:00.0 PCI bridge: Relience Computer Unknown device 0103 (rev b5)

0e:04.0 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0e:04.1 Ethernet controller: BROADCOM Corporation Unknown device 1668 (rev a3)

0e:08.0 PCI bridge: Relience Computer Unknown device 0104 (rev b4)

10:00.0 PCI bridge: Intel Corporation Unknown device 0329 (rev 09)

10:00.1 PIC: Intel Corporation Unknown device 0326 (rev 09)

10:00.2 PCI bridge: Intel Corporation Unknown device 032a (rev 09)

10:00.3 PIC: Intel Corporation Unknown device 0327 (rev 09)

11:01.0 Network and computing encryption device: Fujitsu Microelectr., Inc. Unknown device 4005 (rev 01)

 

FGT $  

[Dave_Hall]

I'm curious to know if the correct firmware was loaded into the FGT? 

[ncmreynolds]

Dave Hall wrote:

I'm curious to know if the correct firmware was loaded into the FGT? 

Yes, I was quite careful to check I'd put the right image on. The first thing I did when it messed up was look at what was on my USB stick and make sure I'd not got confused. I've got to say I've never tried to burn the wrong image, does it even let you in the GUI?

The difficulty with these old devices is they're end of life and not on maintenance, so I can't get an HQIP image. I could swear we had one at one point when they were live systems, but we probably binned it.

[rwpatterson · Accepted solution]

Hit this link up...

http://173.77.211.250:519...ate-1000A_HQIP_059.img

[ncmreynolds]

rwpatterson wrote:

Hit this link up...

http://173.77.211.250:519...ate-1000A_HQIP_059.img

Thanks, although I fear I've now bricked it.

Being pressured to get this swapped out for another box tomorrow morning (and it's now 5:30pm UK time) I cleared the CMOS using the instructions screen printed on the motherboard. This seems to have nicely cleared the CMOS as it shows a date in 2006 when you power it on. However it now doesn't go past "Initialising RAM". I am guessing it's waiting for some input similar to the "Invalid date: press F1" you get if you clear the CMOS on a PC. Only I've got no obvious way to do this.

Annoying.

[rwpatterson]

It may have been heading down that road before you cleared out the CMOS...

[Dave_Hall]

rwpatterson wrote:

It may have been heading down that road before you cleared out the CMOS...

Funny coincidence -- we didn't bother renewing the subscription on our remaining 200As because we were planning to migrate them over to either 200B or 200D; well during the migrating we had 2 x 200As fail within hours of each other, then about 4 days later had another one fail.  These 200As were deployed at different sites.

[ncmreynolds]

rwpatterson wrote:

It may have been heading down that road before you cleared out the CMOS...

Possibly although it seems a big coincidence. When I've got some more time I may look to see if it can be resurrected but right now we've missed our window of opportunity to build the test environment we need this week. We'll have to soldier on without testing LACP/HA interaction as we've nothing else spare that will do LACP.