mainframe.dev

Commonly when talking about Fibre Channel the assumption is that you are talking about attaching some sort of storage device to some resource that wants to use that storage. However, Fibre Channel itself does not care about the storage part. Fibre Channel only facilitates opening a channel between two devices, which is referred to as nodes in Fibre Channel lingo - then what you do after that is up to you. Most commonly you will use a protocol called FCP (protocol 0x08), which confusingly stands for Fibre Channel Protocol, which is the protocol responsible to moving SCSI commands over Fibre Channel. Another relatively new protocol is FC-NVMe (protocol 0x28) which is for, wll, NVMe over Fibre Channel without going through any SCSI layers. Another one is FICON which uses protocol 0x1B or 0x1C depending if the frame is from or to a control unit. A host bus adapter (HBA) is a device that enables a computer to access a network, more or less always some sort of storage network and most com

Fabric OS is what runs on the SAN switches I will be using for the mainframe. It has a bit of annoying upgrade path as the guldmyr blog can attest to. TL;DR is that you need to do minor upgrades (6.3 -> 6.4 -> 7.0 -> ... > 7.4) which requires you to get all  Fabric OS images for those versions. Not always easy. So, let's make it a bit easier. Hopefully this will not end up with the links being taken down, but at least it helped somebody I hope. These downloads worked for me and are hash-verified when I could find a hash to verify against. Use at your own risk etc. The URLs are: ftp://ftp.hp.com/pub/softlib/software13/COL59674/co-168954-1/v7.3.2a.zip ftp://ftp.hp.com/pub/softlib/software13/COL59674/co-157071-1/v7.2.1g.zip ftp://ftp.hp.com/pub/softlib/software13/COL59674/co-150357-1/v7.1.2b.zip ftp://ftp.hp.com/pub/softlib/software12/COL38684/co-133135-1/v7.0.2e.zip ftp://ftp.hp.com/pub/softlib/software13/COL22074/co-155018-1/v6.4.3h.zip ftp://ftp.hp.c

I am back in Switzerland. It has been a good two months away from work, and the first morning after coming back I rushed to the office to unpack and inspect the goods that will hopefully make the mainframe come alive. So far the equipment is: DLm2000 virtual tape system 1x Virtual Tape Engine (VTE) 1x Access Control Point (ACP) 2x Brocade 5100 SAN switch 1x Arista DCS 7050S-64-R 10/40 Gbps switch I am also eagerly awaiting 2x Brocade 7800 SAN switch which should help me connect with other mainframers in the world and share some storage with them. The Arista and the Brocade 5100 were really no surprises, booted up fine and had decently recent firmware. No worries there, so I'll skip the details. DLm2000 The DLm2000 is a component I am excited about and I think has great hack potential. It is more or less 2x FICON PCIe cards, and 1x 10 Gbit/s card. It presents itself as one or multiple tape drives and stores the drives as AWS tape files. Given the size of the

This is going to be a short update to share some good developments in the project. First of all: the mainframe has cleared customs and has been received by the datacenter. Customs caused a bit of a headache as eBay lists the sale price as the "Buy it now" price even if an agreement was put in place. This is usually fine as they values do not diverge a lot but in this case it was $300,000 vs $12,000 which would mean a significant difference in taxes to be paid. Thankfully the customs department listened to my arguments and they agreed that the accepted offer is what I should be taxed on. I must say that I am very pleased in the help UPS provided me with here, I assumed all logistics companies had gone sour but UPS redeemed themselves in my eyes with this delivery. Mainframe being unloaded in the Swiss Alps at datacenterlight . Photo by Ungleich. The next issue was that the datacenter told me they discovered the mainframe would not fit the elevator they had to take for