Does the ICX6450 support OSPF v3 (IPv6)? I thought it'd have identical routing features to the ICX6610 (fully licensed thanks to @fohdeesha ), but the 6450 doesn't show the ipv6 router global config option.
nope, only ipv4 ospf, and no bgp or tunnels. it's a cut down version of the 6610Does the ICX6450 support OSPF v3 (IPv6)? I thought it'd have identical routing features to the ICX6610 (fully licensed thanks to @fohdeesha ), but the 6450 doesn't show the ipv6 router global config option.
That's how LAGs work in versions above 8030 (icx7xxx series). When you make a LAG, it's treated like its own interface so you don't have to worry about the individual port members anymore. If you want it in a vlan, you just add the LAG interface and it takes care of the restInteresting behavior when adding two LAG interfaces to a new VLAN. I can't add the individual ports already in the LAG, so I look around a bit more, and see that I can add lg4 and lg5 (the 2 LAGs). The odd part: after the VLAN is created, not only do the 2 LAGs show up, but the 4 ports comprising them do also. This seems by intent, as: 1) I can't add ports already in a LAG to a VLAN - they don't show as available, and 2) if I do 'modify vlan' and remove individual port(s), the LAG is removed as well. Kinda strange, but ok...
Yea but on the 6xxx lineup you can edit only the "master" or primary interface of the group (can't remember now on top of my head the exact nomenclature of the primary interface, but still...), the other interfaces are "read only".That's how LAGs work in versions above 8030 (icx7xxx series). When you make a LAG, it's treated like its own interface so you don't have to worry about the individual port members anymore. If you want it in a vlan, you just add the LAG interface and it takes care of the rest
It seemed kind of non-intuitive to me. It can't make sense to have N-1 members of a LAG in the VLAN, no? Maybe this is supposed to be self-documenting? e.g. showing you which individual ports are involved?Yea but on the 6xxx lineup you can edit only the "master" or primary interface of the group (can't remember now on top of my head the exact nomenclature of the primary interface, but still...), the other interfaces are "read only".
In either case, it's plainly wrong adding VLANs on member interfaces, how can it be that on a LAG only one interface can accept packets of a VLAN and others can't?
The problem is I have pfSense on Proxmox. Configured for a transit vlan, since i guess pfsense cant do dhcp on non-direct connected vlans? so im gonna need the switch to do it... gateway configured on pfsense at 192.168.3.1 and a static route for 192.168.3.0/24. So on the switch, its an FCX648S fodeesha flashed, two vlans configured, vlan 3 is transit, vlan 10 is whatever. The switch is configured with a virtual router interface at 192.168.3.2, default route of 0.0.0.0/0 192.168.3.1. show mac even shows the interfaces tagged in their proper vlans, but i cant get them to ping eachotherWhy don't you tell us what the problem is and we can help you. It's really not that hard: create the vlan and tag or untag the ports. You could even do it from the web gui if CLI is really that hard.
if the "transit subnet" interface you made on pfsense is new, it won't have any rules on it under firewall > rules, so it won't even allow icmp (ping). you need to add rules to allow traffic. You need to also make sure you have routes on both pfsense and the icx, so pfsense knows how to get back to the subnets you've set up on the fcx on other VE'sThe problem is I have pfSense on Proxmox. Configured for a transit vlan, since i guess pfsense cant do dhcp on non-direct connected vlans? so im gonna need the switch to do it... gateway configured on pfsense at 192.168.3.1 and a static route for 192.168.3.0/24. So on the switch, its an FCX648S fodeesha flashed, two vlans configured, vlan 3 is transit, vlan 10 is whatever. The switch is configured with a virtual router interface at 192.168.3.2, default route of 0.0.0.0/0 192.168.3.1. show mac even shows the interfaces tagged in their proper vlans, but i cant get them to ping eachother
i suspect the issue is with pfsense virtualized on proxmox somewhere, maybe pfsense doesnt like the physical nics in that machine?
hope this makes sense, im trying to be quick since ive already put hours into this thing and tbh the thing just isnt worth any more of my time and ive yet to see a successful L3 routed ping from it. Ive had this thing for like i said, 6 months, ive put weekends into playing around trying to get it to work for me.
Now that I think more on this, I think it does makes sense. Actual data will come in/go out via the LAG, but LACP packets are sent/received on the individual ports?It seemed kind of non-intuitive to me. It can't make sense to have N-1 members of a LAG in the VLAN, no? Maybe this is supposed to be self-documenting? e.g. showing you which individual ports are involved?
I am using a USG-3, I know there are some differences between USG and UDM...Have a question that hopefully someone can answer though it is related more to unifi gear. I have a 6450 that I have watched the videos on and gone through and set up 3 of my vlan's so far with poe power etc and I have it working BUT I have my UDMP doing the routing through the SFP+ port. I tried to leverage DHCP on the switch at first and after reading even more figured out why I was having issues. Seems some of my devices would not take the DHCP address.
Before going through and changing everything I read that pfSense does not handle DHCP duties unless the subnet is listed. Does anyone know if the Unifi USG or UDMP act the same way? I only ask because I would hate to restart setting the switch up as this is already my 3rd attempt and everything else is working well.
If this is the wrong place to ask I can also check on the Unifi forums.
put a name here as PSA for people know what sellers to watch for/potentially avoidSo, the eBay seller was good, got my refund, and since they were quick about things, I went ahead and ordered the last one....and same problems. This time, it is only the POE led for port 21 that is stuck on, but same, 24 of those "BCM_ERR: while 'bcm_port_mdix_set' is Feature unavailable" errors on boot and plugging anything into ports 1 thru 24 does not activate a link, but plugging in ports 25 thru 48 will bring up a link.
This, after he said they tested all the ports.
I loaded SPR08080f firmware and factory set-default, just to be sure and that didn't change anything.
Am I doing something wrong, or is this just another bad switch that failed the same exact way? I figured I'd check here before I send yet another one back. I am now hesitant to get another 7250.
ICX7250-48P
arp is a layer 3 concept, the switch will not see or have any ARP entries for VLANs where it does not have an IP interface in said vlan (no VE). for layer 2 vlans where it's not doing IP routing, all it needs to know is MAC addresses for MAC to port mapping (layer 2 switching) which is why you see MAC entries for those vlansCurious behavior from the 7250-24. The command to display the ARP table only ever seems to show entries in the default VLAN. I have two others, and nothing shows for them, although entries from VLAN 2 and 3 are present in the mac address table. Is this a bug? A feature? If the latter, it sure seems odd...