Drag to reposition cover

Brocade ICX Series (cheap & powerful 10gbE/40gbE switching)

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

mstgkillr

New Member
Sep 3, 2023
15
0
1
To add a little more information... I have a Quantum Fiber C6500XK NID/Modem/Router with their Plume WiFi 360 setup. Honestly, I'm not sure what is doing the routing.... came as a bundle.
 

klui

༺༻
Feb 3, 2019
991
581
93
Thank you for the reply! Just to clarify, I should ping the switch and get what for a result?
You should see
Code:
> ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
instead of
Code:
> ping 128.0.0.1

Pinging 128.0.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 128.0.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 

mstgkillr

New Member
Sep 3, 2023
15
0
1
You should see
Code:
> ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
instead of
Code:
> ping 128.0.0.1

Pinging 128.0.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 128.0.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ok, I pinged /private/tftpboot at 127.0.0.1 and got a bunch of responses, similar to the above. Tried again. Now, I'm getting "gatewayip needed but not set"

I've tried many many ip address for the switch.
 

klui

༺༻
Feb 3, 2019
991
581
93
Don't use the IPs I used. They are for example only because I can't read your mind and find out what IP you assigned your switch.

Instead of providing bullet points, it would help more if you pasted commands and their output.
 

LodeRunner

Active Member
Apr 27, 2019
557
237
43
I did... I disabled the firewall.
Sorry missed that you did. What ports on the 6450 are connected? TFTP only works via the regular switch ports when the switch OS boots; TFTP only works via the management port when in the boot loader.
 

mstgkillr

New Member
Sep 3, 2023
15
0
1
Don't use the IPs I used. They are for example only because I can't read your mind and find out what IP you assigned your switch.

Instead of providing bullet points, it would help more if you pasted commands and their output.
I assigned the switch an IP of 192.168.40.118 but didn't receive a response. For the TFTPd it was using a 192.168.40.79 and received a response. See attached.
 

Attachments

mstgkillr

New Member
Sep 3, 2023
15
0
1
Sorry missed that you did. What ports on the 6450 are connected? TFTP only works via the regular switch ports when the switch OS boots; TFTP only works via the management port when in the boot loader.
I am connected to the console port... top left.
 

klui

༺༻
Feb 3, 2019
991
581
93
Per @LodeRunner
TFTP only works via the regular switch ports when the switch OS boots; TFTP only works via the management port when in the boot loader.
When you're in the bootloader, ICX64XX-boot>> you need to connect your ethernet cable to the management port.
 

mstgkillr

New Member
Sep 3, 2023
15
0
1
Per @LodeRunner


When you're in the bootloader, ICX64XX-boot>> you need to connect your ethernet cable to the management port.
Wait... I have been connecting from my laptop's USB-C to the switch's console port via OIKWAN USB-C to RJ45 Serial Adapter. I am assuming the console port is the same as the management port (top left) on the switch. Is the management port different?
 

bwahaha

Active Member
Jun 9, 2023
127
97
28
Wait... I have been connecting from my laptop's USB-C to the switch's console port via OIKWAN USB-C to RJ45 Serial Adapter. I am
Attach files
=21107&hash=c6a0fcbf62c45ce7d7473d943281da9c']

assuming the console port is the same as the management port (top left) on the switch. Is the management port different?
The management nic port is below that, on the bottom left. The tftp stuff is done over Ethernet, typically plugged into the Ethernet port of the PC you're working with, just like the serial.
 

mstgkillr

New Member
Sep 3, 2023
15
0
1
I tried the port on the bottom left, but it didn't make any type of connection to the switch (see attached). Also, disregard the ethernet cable plugged into Port #1, I wasn't using it. I've also attached the cable that I am using to connect the computer to the switch.

I'm beginning to wonder if it's something that I'm doing wrong or if the switch is bad. I'm just about to give up on it.
 

Attachments

mstgkillr

New Member
Sep 3, 2023
15
0
1
You also need an ethernet (network) cable to get the tftp connection to the server, over the network.
Should the (network) cable be connected directly to the computer that I'm using with the (serial) cable, and which port should the (network) cable be connected to?
 

bwahaha

Active Member
Jun 9, 2023
127
97
28
So there needs to be two cables (well, three if you include power).

Top Port is console serial connection. Uses the usb adapter you posted. Leave that in this port until done.

Bottom port is Network Management. This plugs into your network for the firmware steps. You want to plug this into your existing network. At this point, you should be able to ping 40.118
 
  • Love
Reactions: mstgkillr

mstgkillr

New Member
Sep 3, 2023
15
0
1
So there needs to be two cables (well, three if you include power).

Top Port is console serial connection. Uses the usb adapter you posted. Leave that in this port until done.

Bottom port is Network Management. This plugs into your network for the firmware steps. You want to plug this into your existing network. At this point, you should be able to ping 40.118
That is what I needed! Finally, got it! Thanks everyone! Figures it was something simple, but that I would have never figured out on my own.

Now, I'm stuck on the last step... the licensing "flash copy stack error: tftp timeout." Any suggestion on cables or other issues.
 

Attachments

bwahaha

Active Member
Jun 9, 2023
127
97
28
1) make sure the tftp server is running. What OS is it on?
2) can you ping both IP addresses, for the switch, 118 and the server, 79?
 
  • Like
Reactions: mstgkillr