Wedge 400 48-Port
- Thread starter tritron
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I know this is a pretty late reply but I've been bringing one back up to working state as well recently and may be able to shed some light on the connector type depending on one psu it has in it. I know from the information I've been able to dig up there are two different plug types.
So for the ac version as best I can tell is a SAF-D-GRID T-Latch connector. I do not know what type of connector the DC version is unfortunately and I'm still looking around for a matching cable. As for if it's a difference in connector type between ac and DC or it just being luck of the draw I am unsure of that as well at this point.
Out of curiosity what os were you planning to run on it?
Right now I am still looking for the BSM and will probably give celestica a call. The unit that I have right now seems to be almost completely intact aside from the BSM. Ill tear it down and photograph everything that it is in it as well as all of the part number sticker on it and probably start a thread with it all. I have cabling arriving tomorrow so Ill power it on and see where I stand on things and report back.
First initial power on test went well. Everything not tied to the bmc lit up like they should. The comm ports showed activity when hooked up though I couldn't access it yet. I'm thinking next step just to test things out is preload Sonic on an m.2 and see if that allows some functionality. When I get back from holiday I'll reach out to Celestica to see what assistance may be found or if they'd be open to something like a bulk order of the bsms so the community can start working with these switches.
Quite a bit of good info on here. Some outdated info too.
Memory is 2x16GB DDR4 ECC 1600 SODIMM, should be able to take up to 2133.
BSM electrical connections are listed in detail. Also some info about the card itself. But eMMC part in doc is EOL, EEPROM isn't really used, and flash chips are1Gbit and not(edit: can work on 256Mbit, needed some minor code alterations) 256Mbit. It's a Meta/Facebook part. It's removed and destroyed for security purposes. I doubt one will be available for purchase. You may need to fabricate your own.
Minilake and switch ASIC are held in off state until BMC boots.
github.com
You need to compile this and write it to the BSM's flash chips.
External console port is a standard cisco style RS232 on RJ45 at 9600 baud. Internal connection to Minilake is 57600 baud. Highly reccomended to SSH into BMC over ethernet where possible.
To get to minilake console, log into to BMC and use sol.sh.
This contains schematics, design docs, and some firmware for Minilake. You should not need the firmware, but its nice to have.
Micro USB port is not USB signals, D+/D- pins are 3.3v UART at 57600 baud, 5VSB on P+. You may need to use this if you change the Console Redirect settings, do yourself a favor just don't mess with them.
As for NOS, I don't know.
FBOSS is an option. It's a pain to compile, runs on CentOS 9, and requires "ASIC vendor SDK kmods built as per the instructions from ASIC vendor and installed on the HW switch " .
SONiC doesn't seem to have any direct support for this platform. Also, ONIE needs to support NVME to install anything.
All of the sensor polling is through REST-API calls to BMC at fe80::1. Info is available in the facebook/OpenBMC github.
Memory is 2x16GB DDR4 ECC 1600 SODIMM, should be able to take up to 2133.
BSM electrical connections are listed in detail. Also some info about the card itself. But eMMC part in doc is EOL, EEPROM isn't really used, and flash chips are
Minilake and switch ASIC are held in off state until BMC boots.
GitHub - facebook/openbmc: OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC).
OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC). - facebook/openbmc
github.com
You need to compile this and write it to the BSM's flash chips.
External console port is a standard cisco style RS232 on RJ45 at 9600 baud. Internal connection to Minilake is 57600 baud. Highly reccomended to SSH into BMC over ethernet where possible.
To get to minilake console, log into to BMC and use sol.sh.
http://files.opencompute.org/oc/public.php?service=files&t=55718014fbcec652ca6171b7d3d582d9&download
This contains schematics, design docs, and some firmware for Minilake. You should not need the firmware, but its nice to have.
Micro USB port is not USB signals, D+/D- pins are 3.3v UART at 57600 baud, 5VSB on P+. You may need to use this if you change the Console Redirect settings, do yourself a favor just don't mess with them.
As for NOS, I don't know.
FBOSS is an option. It's a pain to compile, runs on CentOS 9, and requires "ASIC vendor SDK kmods built as per the instructions from ASIC vendor and installed on the HW switch " .
SONiC doesn't seem to have any direct support for this platform. Also, ONIE needs to support NVME to install anything.
All of the sensor polling is through REST-API calls to BMC at fe80::1. Info is available in the facebook/OpenBMC github.
Last edited:
Thanks for providing all of this information. I know for the BSM it will be a huge long shot on whether there are any available for purchase. That being said over on another thread there was someone who had talked with a board mfg about making a run of them if better info could be obtained. Having the document above might help out a ton.Quite a bit of good info on here. Some outdated info too.
Memory is 2x16GB DDR4 ECC 1600 SODIMM, should be able to take up to 2133.
BSM electrical connections are listed in detail. Also some info about the card itself. But eMMC part in doc is EOL, EEPROM isn't really used, and flash chips are 1Gbit and not 256Mbit. It's a Meta/Facebook part. It's removed and destroyed for security purposes. I doubt one will be available for purchase. You may need to fabricate your own.
Minilake and switch ASIC are held in off state until BMC boots.
GitHub - facebook/openbmc: OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC).
OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC). - facebook/openbmc
You need to compile this and write it to the BSM's flash chips.
External console port is a standard cisco style RS232 on RJ45 at 9600 baud. Internal connection to Minilake is 57600 baud. Highly reccomended to SSH into BMC over ethernet where possible.
To get to minilake console, log into to BMC and use sol.sh.
http://files.opencompute.org/oc/public.php?service=files&t=55718014fbcec652ca6171b7d3d582d9&download
This contains schematics, design docs, and some firmware for Minilake. You should not need the firmware, but its nice to have.
Micro USB port is not USB signals, D+/D- pins are 3.3v UART at 57600 baud, 5VSB on P+. You may need to use this if you change the Console Redirect settings, do yourself a favor just don't mess with them.
As for NOS, I don't know.
FBOSS is an option. It's a pain to compile, runs on CentOS 9, and requires "ASIC vendor SDK kmods built as per the instructions from ASIC vendor and installed on the HW switch " .
SONiC doesn't seem to have any direct support for this platform. Also, ONIE needs to support NVME to install anything.
All of the sensor polling is through REST-API calls to BMC at fe80::1. Info is available in the facebook/OpenBMC github.
Thats good to know about the sequence on hardware booting as well. I do appreciate the tips on connecting to it as well that should prove useful if a bsm is tracked down by some means.
I will keep that in mind about changing console redirect settings. I wouldnt plan on doing anything too over the top with it after getting it up and running aside from trading out a cx5s&cx6s nics to cx7s on my servers and workstations. Worse comes to worst I dont have any significant amount of money in a fun project and I just go with a Z9332F-ON or something around there.
After waiting on the sidelines for a bit... i pulled the trigger and got the wedge 400. Thanks for this thread ordered the SAF-D-GRID T-Latch connectors. Wanted to check back on any further updates on BSM.
Last edited:
So far in for trying to track down a bsm I have been mostly unsuccessful. I talked with a few helpful people at celestica who unfortunately didn't directly have any information but did give the names of a few that might. Additionally, I reached out to the email I came across on some of the marketing material in case that was still monitored but as expected I don't think it is.
On the more practical side of things, I talked with a few friends that were electrical engineers and based on the documentation we should have enough information to manufacture a new one. I talked to a small run manufacturer as well and got their requirements for what they would need to produce something like that and it's well within the realm of possibility technically. I just need to now find a pcb designer that can build out the model they want in order to produce. Additionally, they offer a service for flashing firmware on to it in house which would eliminate an additional step on the end users side.
Where I am at currently on this project is slightly paused since I've gotten busy at work and am at a comfortable spot to pause temporarily. The next step that would be needed in this would be to either find here or hire a pcb designer to take the documents and make the necessary model the manufacturer needs. From there I can acquire all of the chips that would go along with it and make an initial validation testing unit to see if this whole thing works. Based on that the option for a larger run would be up for discussion to try and bring as many of these back into service as possible.
On the more practical side of things, I talked with a few friends that were electrical engineers and based on the documentation we should have enough information to manufacture a new one. I talked to a small run manufacturer as well and got their requirements for what they would need to produce something like that and it's well within the realm of possibility technically. I just need to now find a pcb designer that can build out the model they want in order to produce. Additionally, they offer a service for flashing firmware on to it in house which would eliminate an additional step on the end users side.
Where I am at currently on this project is slightly paused since I've gotten busy at work and am at a comfortable spot to pause temporarily. The next step that would be needed in this would be to either find here or hire a pcb designer to take the documents and make the necessary model the manufacturer needs. From there I can acquire all of the chips that would go along with it and make an initial validation testing unit to see if this whole thing works. Based on that the option for a larger run would be up for discussion to try and bring as many of these back into service as possible.
Really appreciate the update and would be happy to support in anyway I could.. i got a couple of wedge 400 switches... and would love to get them working for my homelab...
Quite welcome. Its definitely been a fun project. Any assistance with project is greatly appreciated. I'll check my emails later this evening and get the file type the manufacturer requested for production as well as the links to all of the subcomponents. The most helpful thing at this point would be someone with skill in pcb design so we can get a prototype made.
I started reaching out on my end to couple of folks who knows/works on pcb side... However, so far everyone indicated this might cost a bit... I will let you know... Can you share the type of files manufacturer asked for... For sharing the specs, i am using section 5.5.1 from the above OCP specification pdf
I think i found the required fabrication input files... However, I am not an expert here. So not sure what are relevant vs non-relevant for BSM fabrication. Due to size of these I cannot uplaod here.. But you can find them in https://www.opencompute.org/documents/meta-minipack3-design-package-v1-0-zip.
You need to pcik the BMC and BSM specific files from this. Would it be possible to run these with your fabricator to see if they have all they need... i will try to do the same with PCBWay as well to see what they quote for a 10 piece fabrication.
You need to pcik the BMC and BSM specific files from this. Would it be possible to run these with your fabricator to see if they have all they need... i will try to do the same with PCBWay as well to see what they quote for a 10 piece fabrication.
Minipack3 doesn't seem to have a BSM like the Wedge400. Looks to only be a single removable BMC card with all storage onboard.
Here are the links for all the different components needed for the BSM.
EMMC- The most expensive piece
https://www.flywing-tech.com/product-detail/memory-micron-technology-inc-mtfc8gacaalt-4m-it-ed304566
SPI Flash
FRU Eeprom- I am not sure if there is a difference between sub skus that we would need to take into consideration but it should be figured out prior to purchase.
As for the file type the requested, they are wanting it as a gerber file.
We will probably need to find someone (less there is someone here that would be interested helping) that can do pcb design and just have them do all the traces based on the Wedge400 OCP document that is shared above. Having the FBOSS git will be infinitely helpful since the manufacturer I have been talking to also offers software install services which could make things quite a bit easier if it turns the entire process into just needing to install the BSM and then install the switch os. As for the specs, section 5.5.1 is the correct section for the part needed. At least for my Wedge400 I have been digging through it and based on the documentation it seems the only thing I am missing at this point is just the BSM. Ill look through the zip file that you shared this weekend to see if the file is in there and if that is the case we should be able to proceed pretty easily. As to Forays comment I think that is correct as far as differences go. I will look further into it as well.
I don't believe the size and brand matter all that much with the eMMC. It doesn't look like it's used for much in openbmc besides the mterm log.
As for FRU EEPROM this one should work: https://www.digikey.com/en/products/detail/microchip-technology/AT24C64D-SSHM-B/2507877
As for FRU EEPROM this one should work: https://www.digikey.com/en/products/detail/microchip-technology/AT24C64D-SSHM-B/2507877
Agreed I dont think it would matter either. I think it might be worth making a second prototype with an in production eMMC so that in the event it does work, cost is able to be reduced rather significantly while we dont have to worry about availability.