proxmox
Stackable ’90s Intel Network Gear
Stackable ’90s Intel Network Gear
#Stackable #90s #Intel #Network #Gear
“clabretro”
Diving into the Intel Express 500 and 200 series of enterprise networking gear from the late 1990s. We’ll take a look at an Intel Express 510T switch and an Express 220T hub. We’ll look at the Intel Device View Windows 9x software used to manage this equipment, and do a comparison against a…
source
To see the full content, share this page by clicking one of the buttons below |
10/100 speeds are based on thigh size
I loved these switches "Back in the day". Super reliable. Installed tons of them (was an IT consultant working in a sweat shop at the time)
Not sure whats up with your FX module. It does look like its not seating nicely. IIRC they would push all the way in before having to use the screws.
23:56 need a crossover cable lmao auto.mdi wasn't a thing on 100
crazy, i bought one of these from a thrift store when i was a kid and used it for my home lab for a while
I used to love these!
The variation in IOS commands was a problem for Cisco in its large Merger and Acquisition days. Most of the products were brought in through acquisition and having been built by independent companies – who could not violate Cisco Patents – their command structures were different. And you are comparing an in-house built router with an acquired switch and at a time when the standards for VLAN and QOS etc were really going full mainstream. Jump forward a few updates and things not only coalesce to being consistent but also start to work as a unified system. IE you setup a VLAN on the router and the LAN switch will immediately know about it and is ready to join with less effort. I can recall a period where every network node you bought had its only config headaches. It was nice when things implicitly started to sense and cooperate with eachother right out of the box.
Vacuum cleaner + brush job.
wow, a serial port with the data you need for it right on the device, how revolutionary! /s
Cool stuff, and excellent quality production! I'm procrastinating some PC repair work, and this was a nice break before getting back to that.
Why don't you use software that unlock the password
32:54 "Tank, I'm gonna need an operations program for Cisco C2900 series." 5 seconds later… "Let's go."
Very Matrix – I love it!
Okay first of all, subscribed.
Dont touch that thing start it with the compressor outside 😂
the thing i love about(and sad about)is how easily repairable/servicable it is
Seeing you hit differences between IOS on different hardware, I think it's a lot like the fragmentation of the Android ecosystem, but all within one company. My understanding of Cisco development practice is that they copy/paste the entire IOS source tree for each hardware model then customize it for that hardware platform, as classic IOS is the kernel and drivers and services and CLI all-in-one, so to share changes between code trains they need to be applied to each platform fork of IOS individually by each maintenance team. Classic IOS internally wasn't modular in a way that allowed for a shared CLI environment AFAIK, it's one firmware blob, unlike how so many Android functions were moved to Google Play Services so they could be updated independently of the base OS. Unfortunately this allowed Cisco to ship quickly as they could just hack stuff together until it worked without worrying about maintainability, but I'm sure it makes their software more expensive to develop in the long run, since it seemed to be made entirely out of technical debt.
Modern IOS-XE runs the descendants of original IOS services on a Linux kernel, so they can share a lot more code between hardware platforms, and the hardware itself is far less custom, running on standard intel Xeon CPUs with internals much like any other PC server and only the network ports having customization rather than the whole thing being a custom design. Nexus is not IOS but it finally has even more consolidation where there is one firmware image for a whole range of devices with different port configurations
Still watching video, but when the slots off the riser didn't work, I wonder if your attempt to remove the riser when cleaning caused a bad connection and if re-seating and cleaning contacts on the riser would fix the Intel 510T
Wow, pre-auto MDIX!
As far as configuring the Cisco, We used to just pull he config as a txt file and make our edits. then paste it back into the terminal. this made it much easier and the reason why cisco was preferred by most of network engineers i worked with including myself.
I had a few 510Ts in a client back in the day. I don't remember them being anywhere near that expensive, they were significantly cheaper than the other options like CISCO at the time. The client was a school and they were super price sensitive which is why I went Intel with them. I was really disappointed when Intel announced they were existing the network game.
The first cisco switch I ever bought was cisco 2924xl 12 port 10/100 and few years later I bought a cisco 2950 24 port 10/100 then cisco 1721 isr modular router rack version then a cisco 1751 stackable modular
2:03
Is there an advantage in using fibre over a normal connection if both provide a max. speed of 100Mbit/s? I noticed in the video that fibre cables seem to have a smaller diameter, but is there anything else?
I had bought a cisco nexus 5020 and Have not seen int range cmd