Search results

  1. V

    LB4M VLAN setup?

    woohoo! that worked, I included the participation to vlan 300 on port 0/48 and 0/47 and tagged them Thanks
  2. V

    LB4M VLAN setup?

    So, I have the VLAN all setup on the network and it was running. we replaced our DLink DWS-1248T with the LB4M. Now I need to get the VLAN setup on the new switch to get the guest network backup and running. I do need these ports to work on both VLAN 300 and default. Do I not have to tag the...
  3. V

    LB4M VLAN setup?

    I am trying to setup a vlan for a guest network. Our office has vlan 1 (default) and 300 (byod), a fiber connection to the datacenter where I need on the new LB4M a VLAN config to get 300 to the gateway What I did: Port 0/47 - Connection to Office Port 0/48 - Connection to Gateway (Switching)...
  4. V

    Quanta LB6M (10GbE) -- Discussion

    I Got it working. Turns out the 7024 that I got from Unix+ has custom firmware. We got a second one as a backup. I copied the firmware to a server and loaded it into the dead switch. now it is booting and good to go!
  5. V

    Quanta LB6M (10GbE) -- Discussion

    and if I load one of the lb6m.x.x.x.x.bin files, I get WARNING: adjusting available memory to 30000000 ## Booting kernel from Legacy Image at 08000074 ... Image Name: FASTPATH System for lb4m Image Type: PowerPC Linux Multi-File Image (gzip compressed) Data Size: 8133586 Bytes =...
  6. V

    Quanta LB6M (10GbE) -- Discussion

    => tftpboot PC8024v5.1.11.1.stk Enet starting in 1000BT/FD Speed: 1000, full duplex Using TSEC1 device TFTP from server 172.17.10.192; our IP address is 172.17.2.111 Filename 'PC8024v5.1.11.1.stk'. Load address: 0x8000000 Loading: #################################################################...
  7. V

    Quanta LB6M (10GbE) -- Discussion

    Hi I just got an ET-7024 switch off ebay and instead of wiping the configuration, I accidently wiped the flash. Now the switch boots to a "ERROR:can't get kernel image!" and leaves me at a basic linux . I have tried tftpboot <firmware.img> bootm which shows me firmware info and then hangs...