1)tftp server is running. Windows 11.
2) I can ping the server but not the switch?
In the Foheesda Docs, I read the following "Now we need to assign that virtual interface an address. Choose an IP that is unused in your subnet, and out of your DHCP server range (ping it first to be sure it's unused)." Do I really need to change the IP address that is out of the DHCP server range? Wouldn't reserving it be the same?
1)tftp server is running. Windows 11.
2) I can ping the server but not the switch?
In the Foheesda Docs, I read the following "Now we need to assign that virtual interface an address. Choose an IP that is unused in your subnet, and out of your DHCP server range (ping it first to be sure it's unused)." Do I really need to change the IP address that is out of the DHCP server range? Wouldn't reserving it be the same?
HELLO I'M HERE BECAUSE I NEED A LITTLE HELP. I HAVE A BROCADE, ALSO KNOWN AS A RUCKUS ICX7250. I HAVE RESET IT BACK TO FACTORY AND I INSTALLED 08.0.95K UEFI FIRMWARE. I'M TRYING TO INSTALL VERISON 09.0.10F. HOW I UPDATED THE 08 VERSION WAS WITH TFTP, AND I THINK THE COMMAND IS 'COPY TFTP FLASH XXX.XXX.X.X ICX7XXX/SPR09010FUFI PRIMARY', WHICH DIDN'T WORK. I ALSO TRIED 'COPY TFTP FLASH XXX.XXX.X.X ICX7XXX/SPR09010FUFI.BIN SECONDARY. I WAS WONDERING IF SOMEONE HAS EVER PLAYED WITH ONE OF THESE. This IS MY FIRST TIME PLAYING WITH ONE OF THESE. how i flashed it was i used the Setup / Config / Licensing Guide v2 ---- on this form and i used the im sure im missing something here
Load The Latest UFI Image
Now that the switch has an IP address & is booted into v08090 (which is capable of flashing the new UFI format images), we can flash the latest stable FastIron version. First, move your ethernet cable from the dedicated management port to any of the regular switch ports. Then run the following to flash the new UFI image. Like previous commands, replace the IP with the IP of your own TFTP server:
i put the New uefi file in the TFPT -content in hopes i could flash from there, just like when i flashed copy tftp flash 192.168.1.8 ICX7xxx/SPR08095kufi.bin primary only diffrence is the UFI.bin is diffrent i didnt think that would matter as long as it could see it
My goal with this switch was for it to do switching things, have a really cool web UI, and have 10 GB. I mean, I don't think I'm asking too much here, maybe even a few extra things, but nothing that I would expect to be a challenge with this thing.
Well, because primary wasn't working, I was like, Fxx it, let's see ifthe funny part is, I was in the process of flashing, so I had everything in a notepad to make sure the commands were right, so all I had to do was copy and hit enter, and I was in the TFPT server. It would not allow me to flash SPR09010fufi.bin, but as soon as I typed SPR08095kufi.bin in per the directions, 95k flashed right away.
i thought i had it but i guess that didnt work i type in the command enable than put in the command but it wont even allow me to accress the gui and i have to do the whole thing over again
Well, that didnt work at all It installed and I can see it on putty but it wont fully boot i get alot of random debug errors for some reason i tryed to up date with the copy tftp flash and the manifest text both work i can see it on sh ver but will not load.
Been using an ICX6610 for a while I set up with the docs from Fohdeesha (huge thanks BTW), but recently trying to split my kids off onto a separate vlan and I can't seem to get it working. I was wondering if anyone had a minute to help. I've never set up vlans before, so this has been quite the learning experience for me.
Running pfSense virtualized with ESXi, Unifi AP's, and an ICX6610.
ISP--->AT&T Fiber Modem (hardware passthrough, 1GB intel NIC)-->Virtualized pfSense vmx0 -->Vmware vSwitch--> (ConnectX3 40GBE) ICX6610
Main network is 10.0.0.0/22 default vlan
Kids network planned to be 10.10.0.0/24 on vlan10
Unifi AP's are on 1/1/46 and 1/1/48 via 1GBE using POE
ESXi vSwitch is on 1/2/1 and 1/2/6 via ConnextX3 40GBE
pfSense connects to the vSwitch via vmx0
Right now, kids are all wireless, but I'll eventually be adding 1/1/23 and 1/1/24 to the kids vlan10 for desktops.
I've already set up a vlan10 network in Unifi, and a unique SSID.
pfSense already has a vlan10 set up on vmx0, and the interface assigned and enabled
pfSense WAN is igb1 via hardware passthrough to my AT&T fiber modem
I set up a DHCP server on pfSense for vlan10 for 10.10.0.50 to 10.10.0.200
I can't seem to get traffic passing through the ICX6610 switch, and I can't figure out what I'm doing wrong. I created a vlan10, tried adding the switch ports to it and putting them in dual mode, but then no traffic seems to pass, even from the untagged vlan. I know I need to set up 1/1/46, 1/1/48, 1/2/1 and 1/2/6 as trunks to pass all traffic, but I don't understand the command line syntax for it and I can't seem to get it right, or am I completely off base and misunderstanding the correct vlan topology?
I cleaned most of my experimentation and went back to a relatively clean show run for the ICX6610. Output below:
Code:
SSH@ICX6610-48P#show run
Current configuration:
!
ver 08.0.30uT7f3
!
stack unit 1
module 1 icx6610-48p-poe-port-management-module
module 2 icx6610-qsfp-10-port-160g-module
module 3 icx6610-8-port-10g-dual-mode-module
stack disable
!
global-stp
!
!
!
vlan 1 name DEFAULT-VLAN by port
router-interface ve 1
spanning-tree
!
vlan 10 name KidsofChaos by port
router-interface ve 10
spanning-tree
!
!
!
!
!
aaa authentication web-server default local
aaa authentication enable default local
aaa authentication login default local
jumbo
enable aaa console
hostname ICX6610-48P
ip dhcp-client disable
ip dns domain-list chaos.lan
ip dns server-address 10.0.1.20 10.0.1.21
ip route 0.0.0.0/0 10.0.0.1
!
no telnet server
username root password .....
!
!
clock summer-time
clock timezone us Eastern
!
!
ntp
disable serve
server 10.0.0.1 minpoll 10
!
!
web-management https
web-management session-timeout 600
!
!
router rip
!
!
!
!
!
!
!
interface ethernet 1/1/1
inline power
!
interface ethernet 1/1/2
inline power
!
interface ethernet 1/1/3
inline power
!
interface ethernet 1/1/4
inline power
!
interface ethernet 1/1/5
inline power
!
interface ethernet 1/1/6
inline power
!
interface ethernet 1/1/7
inline power
!
interface ethernet 1/1/8
inline power
!
interface ethernet 1/1/9
inline power
!
interface ethernet 1/1/10
inline power
!
interface ethernet 1/1/11
inline power
!
interface ethernet 1/1/12
inline power
!
interface ethernet 1/1/13
inline power
!
interface ethernet 1/1/14
inline power
!
interface ethernet 1/1/15
inline power
!
interface ethernet 1/1/16
inline power
!
interface ethernet 1/1/17
inline power
!
interface ethernet 1/1/18
inline power
!
interface ethernet 1/1/19
inline power
!
interface ethernet 1/1/20
inline power
!
interface ethernet 1/1/21
inline power
!
interface ethernet 1/1/22
inline power
!
interface ethernet 1/1/23
inline power
!
interface ethernet 1/1/24
inline power
!
interface ethernet 1/1/25
inline power
!
interface ethernet 1/1/26
inline power
!
interface ethernet 1/1/27
inline power
!
interface ethernet 1/1/28
inline power
!
interface ethernet 1/1/29
inline power
!
interface ethernet 1/1/30
inline power
!
interface ethernet 1/1/31
inline power
!
interface ethernet 1/1/32
inline power
!
interface ethernet 1/1/33
inline power
!
interface ethernet 1/1/34
inline power
!
interface ethernet 1/1/35
inline power
!
interface ethernet 1/1/36
inline power
!
interface ethernet 1/1/37
inline power
!
interface ethernet 1/1/38
inline power
!
interface ethernet 1/1/39
inline power
!
interface ethernet 1/1/40
inline power
!
interface ethernet 1/1/41
inline power
!
interface ethernet 1/1/42
inline power
!
interface ethernet 1/1/43
inline power
!
interface ethernet 1/1/44
inline power
!
interface ethernet 1/1/45
inline power
!
interface ethernet 1/1/46
inline power
!
interface ethernet 1/1/47
inline power
!
interface ethernet 1/1/48
inline power
!
interface ethernet 1/3/1
speed-duplex 10G-full
!
interface ethernet 1/3/2
speed-duplex 10G-full
!
interface ethernet 1/3/3
speed-duplex 10G-full
!
interface ethernet 1/3/4
speed-duplex 10G-full
!
interface ethernet 1/3/5
speed-duplex 10G-full
!
interface ethernet 1/3/6
speed-duplex 10G-full
!
interface ethernet 1/3/7
speed-duplex 10G-full
!
interface ethernet 1/3/8
speed-duplex 10G-full
!
interface ve 1
ip address 10.0.0.2 255.255.252.0
!
interface ve 10
!
!
!
!
!
!
!
!
!
end
Been using an ICX6610 for a while I set up with the docs from Fohdeesha (huge thanks BTW), but recently trying to split my kids off onto a separate vlan and I can't seem to get it working. I was wondering if anyone had a minute to help. I've never set up vlans before, so this has been quite the learning experience for me.
Running pfSense virtualized with ESXi, Unifi AP's, and an ICX6610.
ISP--->AT&T Fiber Modem (hardware passthrough, 1GB intel NIC)-->Virtualized pfSense vmx0 -->Vmware vSwitch--> (ConnectX3 40GBE) ICX6610
Main network is 10.0.0.0/22 default vlan
Kids network planned to be 10.10.0.0/24 on vlan10
Unifi AP's are on 1/1/46 and 1/1/48 via 1GBE using POE
ESXi vSwitch is on 1/2/1 and 1/2/6 via ConnextX3 40GBE
pfSense connects to the vSwitch via vmx0
Right now, kids are all wireless, but I'll eventually be adding 1/1/23 and 1/1/24 to the kids vlan10 for desktops.
I've already set up a vlan10 network in Unifi, and a unique SSID.
pfSense already has a vlan10 set up on vmx0, and the interface assigned and enabled
pfSense WAN is igb1 via hardware passthrough to my AT&T fiber modem
I set up a DHCP server on pfSense for vlan10 for 10.10.0.50 to 10.10.0.200
I can't seem to get traffic passing through the ICX6610 switch, and I can't figure out what I'm doing wrong. I created a vlan10, tried adding the switch ports to it and putting them in dual mode, but then no traffic seems to pass, even from the untagged vlan. I know I need to set up 1/1/46, 1/1/48, 1/2/1 and 1/2/6 as trunks to pass all traffic, but I don't understand the command line syntax for it and I can't seem to get it right, or am I completely off base and misunderstanding the correct vlan topology?
I cleaned most of my experimentation and went back to a relatively clean show run for the ICX6610. Output below:
Code:
SSH@ICX6610-48P#show run
Current configuration:
!
ver 08.0.30uT7f3
!
stack unit 1
module 1 icx6610-48p-poe-port-management-module
module 2 icx6610-qsfp-10-port-160g-module
module 3 icx6610-8-port-10g-dual-mode-module
stack disable
!
global-stp
!
!
!
vlan 1 name DEFAULT-VLAN by port
router-interface ve 1
spanning-tree
!
vlan 10 name KidsofChaos by port
router-interface ve 10
spanning-tree
!
!
!
!
!
aaa authentication web-server default local
aaa authentication enable default local
aaa authentication login default local
jumbo
enable aaa console
hostname ICX6610-48P
ip dhcp-client disable
ip dns domain-list chaos.lan
ip dns server-address 10.0.1.20 10.0.1.21
ip route 0.0.0.0/0 10.0.0.1
!
no telnet server
username root password .....
!
!
clock summer-time
clock timezone us Eastern
!
!
ntp
disable serve
server 10.0.0.1 minpoll 10
!
!
web-management https
web-management session-timeout 600
!
!
router rip
!
!
!
!
!
!
!
interface ethernet 1/1/1
inline power
!
interface ethernet 1/1/2
inline power
!
interface ethernet 1/1/3
inline power
!
interface ethernet 1/1/4
inline power
!
interface ethernet 1/1/5
inline power
!
interface ethernet 1/1/6
inline power
!
interface ethernet 1/1/7
inline power
!
interface ethernet 1/1/8
inline power
!
interface ethernet 1/1/9
inline power
!
interface ethernet 1/1/10
inline power
!
interface ethernet 1/1/11
inline power
!
interface ethernet 1/1/12
inline power
!
interface ethernet 1/1/13
inline power
!
interface ethernet 1/1/14
inline power
!
interface ethernet 1/1/15
inline power
!
interface ethernet 1/1/16
inline power
!
interface ethernet 1/1/17
inline power
!
interface ethernet 1/1/18
inline power
!
interface ethernet 1/1/19
inline power
!
interface ethernet 1/1/20
inline power
!
interface ethernet 1/1/21
inline power
!
interface ethernet 1/1/22
inline power
!
interface ethernet 1/1/23
inline power
!
interface ethernet 1/1/24
inline power
!
interface ethernet 1/1/25
inline power
!
interface ethernet 1/1/26
inline power
!
interface ethernet 1/1/27
inline power
!
interface ethernet 1/1/28
inline power
!
interface ethernet 1/1/29
inline power
!
interface ethernet 1/1/30
inline power
!
interface ethernet 1/1/31
inline power
!
interface ethernet 1/1/32
inline power
!
interface ethernet 1/1/33
inline power
!
interface ethernet 1/1/34
inline power
!
interface ethernet 1/1/35
inline power
!
interface ethernet 1/1/36
inline power
!
interface ethernet 1/1/37
inline power
!
interface ethernet 1/1/38
inline power
!
interface ethernet 1/1/39
inline power
!
interface ethernet 1/1/40
inline power
!
interface ethernet 1/1/41
inline power
!
interface ethernet 1/1/42
inline power
!
interface ethernet 1/1/43
inline power
!
interface ethernet 1/1/44
inline power
!
interface ethernet 1/1/45
inline power
!
interface ethernet 1/1/46
inline power
!
interface ethernet 1/1/47
inline power
!
interface ethernet 1/1/48
inline power
!
interface ethernet 1/3/1
speed-duplex 10G-full
!
interface ethernet 1/3/2
speed-duplex 10G-full
!
interface ethernet 1/3/3
speed-duplex 10G-full
!
interface ethernet 1/3/4
speed-duplex 10G-full
!
interface ethernet 1/3/5
speed-duplex 10G-full
!
interface ethernet 1/3/6
speed-duplex 10G-full
!
interface ethernet 1/3/7
speed-duplex 10G-full
!
interface ethernet 1/3/8
speed-duplex 10G-full
!
interface ve 1
ip address 10.0.0.2 255.255.252.0
!
interface ve 10
!
!
!
!
!
!
!
!
!
end
Looking at what you pasted, I don't see that you've added any ports to the VLAN as either tagged or untagged. I only have 7k series units, so my syntax is slightly different for trunking, but for a pure trunk port where you have may not need a default/native/untagged VLAN, the command should be similar to:
Code:
SSH@office-sw(config-vlan-4)#tag e 1/3/1
Issued inside the VLAN context.
Edge ports to workstations would be untagged, like:
Code:
SSH@office-sw(config-vlan-4)#untag e 1/1/1
If you're coming from any Cisco experience, ICX does it in reverse. Where you go into a port and add VLANs to the port(Cisco style), ICX does what HPE switches do: you go to a VLAN and add the ports to the VLAN.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.