Thank you for this detailed answer! This is exactly what I was trying to understand.
Also, that is FANTASTIC news, since I've gotten a bit wild with buying up all kinds of different "old but cheap AF" 20/25/40Gbe NICs and breakouts/DACs. I was starting to question my "buy" of this for a brief moment since getting the console up so kind of janky and weird. After 6+ unplug/replugs (power cycles) I finally "got it", and have been off to the races. I'll have to get the hang of making more of these tweaks/edits from the CLI, but once I got the web interface going I sorted out the 10Gbe ports.
This model (un?)fortunately is "all SFP+", and I don't have any 1Gbe DACs or spare Transceivers at the moment, so I'd interested in where I might find "10+ pack deals" on both 1/1.25 DACs and/or Transceivers that are compatible with Brocades, now that I have more confidence I can ditch all the 4, 5, and 8+ port switches I've collected over the years.
So pardon my Brocade/Ruckus noob brain, but I assume (or translate) that this:
"You can define a layer 3 interface and give it an IP address. That will be a gateway so all routing will occur inside the switch without relying on another device."
means that:
Even if I use a "basic retail" 1Gbe router (Linksys, Netgear, Ubiquity, Asus, TP-Link, etc), I could define said Layer 3 interface in the "router config of the switch" and not have the "speed limit" of the 1Gbe "retail router"?
Of course, assuming I use the Gateway Address of the said L3 interface IP as my configuration in my individual NICs and "upstream gateway" address of my vRouters (pfSense, OPNsense, etc)?
Am I understanding that correctly?
Ok so my next step is to "levelup" and work out how to get Wire Speed with a "transit VLAN" configuration
- As I'm coming from loosely knowing enough and Cisco gear, I understand from my initial readings and learnings that the ICX6610 "uses VLAN 1 differently"
- I haven't wrapped my head completely around that aspect yet, but its fine for the moment as I'm still in the "configure it to work, try to tune it, when it breaks, rest and repeat" phases.
But I'm seeing that without configuring a remote NTP server url / domain, I'm losing my clock settings on each "unplug" / poweroff.
I haven't tried to physically "open up" the chassis for the icx6610 (yet?) but I'd rather not, without a good reason.
Is there some kind of a CMOS battery that keeps the clock settings that is replaceable / accessible for the ICX6610 - or is it a "remote only NTP server settings if you want to keep your clock in sync" kind of a situation?
I could do my own NTP server, I guess, but I'd rather not. And I'd rather not have the external dependency, too (privacy, security, etc) - and hosting my own NTP server would potentially create a "chicken an egg problem" as I want to "host" nearly everything on the same network/VLAN/CIDR of the ICX6610. But maybe I could make some exceptions. I'd much prefer just sorting out how to keep the "manual settings" for the ICX6610 clock, for the moment though.
I know its rather trivial, but I'm still learning more about this shiny new ICX6610 / Brocade / 10+Gbe Enterprise gear. Has anyone ever had a similar experience? I'm searching for details on this and I don't see any definitive "there is no CMOS battery" information or any method for "clock/time retention" outside of "configure an external NTP service / url/IP" but "AI search tools" keep suggesting "its probably the CMOS battery-backed settings failing from a dead battery" (paraphrased).
So is it "necessary"for the Brocade ICX6610 to use external NTP? It just seems odd for an Enterprise Switch (given even the oldest Cisco's I've used don't have this issue). If its not a requirement for an external NTP source to be configured for the ICX6610 set on power-on for proper time settings, then what am I missing to retain the clock settings after a power cycle? Because manually setting the time and then writing to memory doesn't seem to be cutting it.