I have a school with an old Meru AP320, AP300 and MC3200 setup. The usual story, they have no money to replace the system and are desperate to get back up and running. The CF card in the 3200 has failed. It won't even show the linux recovery option on boot. I have connected over serial, etc, etc.
I have a new 4GB CF card which I just tried to flash the recovery image onto it (meru-7.0-10-0-MC3200_recovery_root.img), but this did not work. After doing a bit of digging I think this recovery image is designed to be used not with a blank CF card but when the original CF card is still functional and will at least boot into the linux recovery partition?
Does an image exist that is suitable for flashing onto a brand new card, please?
Any assistance would be greatly appreciated. They are hoping to replace the system next year and any goodwill from Fortinet will go a long way, I'm sure!
Just to let you know, I found another thread detailing a similar issue on an MC4200. I thought I'd give that image a go and do I downloaded it and then dd'd it to a new CF card. I installed it into the MC3200 and booted into linux recovery and then ftp'd the regular meru-7.0-10-0-MC3200_recovery_root.img.gz image down and that seemed to unpack and now the MC3200 is booting up fine. I've upgraded to meru-7.0-15build-0-MC3200-rpm.tar and the school's access points are hopefully just minutes away from being back online.
Thank you for posting the recovery image, which appears to have done the trick for me.
Where did you get the recovery image, I had exactly the same issue on a MC3200, We had to replace the Box but I would still like to get the original up and running
Please advise which recovery images are required and I will post updated download links for you.
If you are looking for 7.0.13 recovery image for MC3200, you can download it from below infosite link. Hope you have access to infosite, if not let me know will upload in egnyte and share you the link.
If you need a different version, let me know will share the link for that.
If you are going to use a new card, you don't need a recovery image. You can directly burn the full image of the version you require.
I have shared the links for 7.0.13 and 8.4.4GA Image files for 3200. You can use the version you want.
You can use any free tool like Win32diskimager to burn the new image to the compact flash. Please let me know if you have any queries regarding burning the image.
Although I have now solved my issue with the help of the MC4200 image, I thought I would try and download your kindly provided links for the MC3200 images to flash onto new cards. However, when I try either of the links it takes me to a sign in page. I have entered both my details for support.fortinet.com and the forum details for fusecommunity.fortinet.com but both are rejected. How should I log in to info.fortinet.com please?
I used the link that John provided in a similar thread about the MC4200:
Password: z2jU39hS https://fortinet.egnyte.com/dl/LSj9kKJeHh
Note that I simply used this image to get the MC3200 to boot into the recovery console from where I was able to ftp the correct MC3200 recovery image onto it. Now working like a charm. I assume that the recovery partition is the same for all Meru controllers. It would be good to have a proper MC3200 cf image and so once it's available from here I will download a copy for safekeeping.
Hope that helps
Hi DustinI was given this by Chami Please see attached images below for the MC1550. I hope this helps you.meru-7.0-8-0-MC1550.img.zipPassword: c2Yfr33pfortinet.egnyte.com/dl/Vk5QPly4nrmeru-8.5-0build-2-MC1550-rpm.tarPassword: 9ZfxMNw8fortinet.egnyte.com/dl/mo4w3GeW44it seems to work but I was having trouble telnetting into the device. This seems to be a reoccurring issue with these devices. We replaced it but I am still working on ours although with no big urgencyTony --
I was given this by Chami Please see attached images below for the MC1550. I hope this helps you.
it seems to work but I was having trouble telnetting into the device. This seems to be a reoccurring issue with these devices. We replaced it but I am still working on ours although with no big urgency