Cisco

Intel Express Stacks

Intel Express Stacks

#Intel #Express #Stacks

“clabretro”

Stacking some Intel Express 510T Switches and 220T hubs with special cables to combine multiple physical units into logical ones for easier management. All of this can be done with the Intel Device View software running on Windows XP. We’ll also try to get a 1gigabit fiber link going to a Cisco…

source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

30 Comments

  1. A patron named Luke pointed out I need to switch the media-type of the gigabit interface on the 7200 to gbic (that's why the RJ45 en light was always on). Sure enough — both link lights on the fiber modules are on now. Still more troubleshooting to do, but fiber videos coming in the future!

  2. I had some nbase switch that had some "pre-ieee-standard" gigabit ports. There was some compatibility issues, but your intel seems newer. So main thing is that back then for multimode you didnt have 50mn but 62.5mn cables. So you might be right you might need an older OM1 cable, though i have never seen an issue like that.
    And you can check the tx outlets with your phone camera, itll normally pick up the light. Dont look in, especially on the 1310nm stuff – since you can never know how strong that laser is😂

  3. Device view uses SNMP communities to manage the switch, bypassing the username and password.
    As long as the SNMP write community is default "public" you can do the reset and whatever you want.

  4. Great stuff brother. It's super cool to see you check out these old network components. Also, I've noticed you're accumulating a whole lot "new" rack-mountable network gear. Any plans to add a second rack and REALLY get a stack going? Love your stuff dude. Keep it going!

  5. i have a 510 t with the fibre module and i used to to connect to a netgear swicth with a fibre modlue it worked well at the time and this was very nostalgic for me .

  6. Weird little shortcut you may find handy with Cisco IOS. When you're in conf t changing attributes of an interface, you don't actually have to exit to switch to another interface. Example, you can do:
    conf t
    int gi1/0/8
    switchport access vlan 1003
    shut
    no shut
    int gi1/0/10
    switchport access vlan 1004
    shut
    no shut
    exit

    Doesn't save you a TON of time, unless you're configuring more than a few interfaces at a time.

  7. I wish I had known about your channel at the time. If I had, I would have filled that 7200 up for you.

    Looks like you figured it out, but for future reference, did you clean the optics on the Intel switch?

  8. Also check the cables, with those old SX optics you'll likely need a mode conditioning OM1 patch cord (62.5/125) for a run that short. Check out Cisco's installation note for the WS-G5484 for more info. I'm not sure what Inte's side would require, but I dealt with tons of those 1000Base-SX optics in 3550s back in the day.

  9. I'm not sure if this is the actual reason for the kilobit/megabit vs kilobyte/megabyte for network speed, but networks talk about transmission rates, i.e. data per-unit time, whereas computers deal volumes of data, i.e. words of data.

    In terms of the OSI model, the transmission rate comes from layer 1, the physical layer. It has no concept of bytes because as far as it's concerned, the bits come in, it encodes them into an electrical signal, optical signal, or radio signal, and transmits them at a given rate. Layer 2, the data link layer, is the first place we see bytes, and that's relating to how much data we can transmit at a time, or the size of the frame, known as the Maximum Transmission Unit or MTU.

    It's no coincidence that it's also the first time we talk about a volume of data, which is always measured in bytes. As we all know, bytes are always counted in powers of two, i.e. 2^10 = 1024 or 1KB (SI can f**k right off, the IEC definition, and the IEC itself, came first!), and volumes are always discussed in bytes, KB, MB, etc.. Whereas speed is always discussed in terms of transmission rates, i.e. bits per-second, which isn't counted in powers of two, but powers of ten, i.e. 1Kbps != 2^10, it's equal to 10^3.

    In other words, it's the difference between the transmission rate, and the volume of data to be transmitted.

  10. It's hilarious you can't reset the password with physical access to the switch but if it's on the network anyone can just load up that Intel software and reset it. They obviously didn't think too much about security back then.

  11. networks can only (in general) push one bit down a wire at a time. That is why its measured in bits. You are measuring physically how much data can transfer.
    The packets being sent may or may not confine to the 8bits = bytes. Some mainframes for example had words of 1024bits 0.o

  12. Bytes are usually used for block storage. Networking has always used bits for data transfer. Great vids. Wish I still had my Intel 550 8-port “layer 2/3” switch to send to you.

  13. I've been busy all day, so I'm late, but I bet this is as exciting as I imagine! +1 for Intel using db9 rather than rj45 things. at least it's "common" (unlike before the 90s)

  14. Enterprise networking gear (especially old stuff) is notorious to not fully leading on how much of the ecosystem you need to buy into. It looks like you can just dip your toe in, then you find out you need x to do y over and over and over again, until you’ve spent 3x than you were initially prepared to spend 🙂

  15. Networks talk about speed in bits because it is fundamentally a serial transmission medium, one bit at a time. Busses and hard drive interfaces are typically parallel so they talk in bytes/second. USB (universal SERIAL bus) is the obvious exception; now there are many serial peripheral interfaces like SATA for hard drive storage and USB for slower peripherals. Mice and keyboards typically talk serial (there are parallel interfaces for keyboards).

Leave a Reply