08-04-2023 12:28 PM
So I'm trying to figure out configuring an x620 (my first extreme switch). Basically I'm just wondering is EXOS suppose to be configured CLI or is there a tool for it. The CLI layout is worse than a firewall, just trying to make sure I'm not making things harder than they need to be.
(I opened the http web ui and there are many things missing from what I need to do so that won't work)
Solved! Go to Solution.
08-05-2023 09:13 AM
Most people use the CLI I think. There is a web GUI as well as you mention, but I never use it. Here is how to activate the GUI:
https://extremeportal.force.com/ExtrArticleDetail?an=000083015
The CLI is unstructured as opposed to other CLIs and you really have to know what you're looking for in the config in order to find it easily. Some commands use enable, some configure, create or set, so it can be confusing. EXOS is not on top of my list either, but that's what you get with EXOS. Live with it or change your gear.
There used to be a Cisco CLI helper module so you could configure most things using a Cisco syntax. I'm not sure if it's available any more.
https://extremeportal.force.com/ExtrArticleDetail?an=000082514&q=cisco%20module
Perhaps you have gotten used to the CLI by now, but some things to remember:
You add ports to a VLAN rather than configuring a VLAN on a port.
You often "enable" a feature in order to the "configure" details of that feature.
A VLAN is "create"d and then you "configure" the properties of it, including when adding ports to it (untagged or tagged).
"Worse than a firewall" 🙂 Which firewall do you refer to?
08-07-2023 08:52 AM
I was referring to the CLI being worse than a firewall as in organized structure for implementing more advanced configs. The commands to actually configure the device are pretty straight forward you just need to do more planning of the config vs configuring on the go. I was mostly making sure extreme did things their own way vs being designed to be implemented with a tool.
08-08-2023 12:13 PM
Yeah I see that, I guess that's where it comes down to being XML based. It has structure in that relevant commands are grouped together, IE if you do a show config, all your port related config will be together, your vlan config will be together. It's not more or less structured than a Palo Alto if I'm honest.
If you're looking for a config tool, I would be looking at ExtremeCloudIQ, we have 20-ish customers using it now for both switching and wireless config who love it.
08-06-2023 01:20 AM
I would have to disagree with the CLI being worse than a firewall, having used every firewall you could think off in the last 20 years, they are all a hell of a lot more awful than anything Extreme put out. I actually started using Extreme 15 years ago because of how easy the CLI is vs my Cisco and Juniper days.
I guess you need to revisit the way the CLI works. The Extreme CLI was designed to be run in real world english rather than technical randomness.
Extreme has no concept of "trunks" or "access" port. Every port just is a general port.
Create your vlan (Name it, add it's tag) : create vlan "MyName" tag 12
Want to add an untagged vlan to 5 ports (Ports 1 through 5)? "add ports 1-5 vlan MyName"
Want to tag your new vlan? "Add ports 1-5 vlan MyName tagged"
It's that easy. Honestly though, look into ExtremeCloudIQ, I've got my team using it and they love it.
08-05-2023 09:13 AM
Most people use the CLI I think. There is a web GUI as well as you mention, but I never use it. Here is how to activate the GUI:
https://extremeportal.force.com/ExtrArticleDetail?an=000083015
The CLI is unstructured as opposed to other CLIs and you really have to know what you're looking for in the config in order to find it easily. Some commands use enable, some configure, create or set, so it can be confusing. EXOS is not on top of my list either, but that's what you get with EXOS. Live with it or change your gear.
There used to be a Cisco CLI helper module so you could configure most things using a Cisco syntax. I'm not sure if it's available any more.
https://extremeportal.force.com/ExtrArticleDetail?an=000082514&q=cisco%20module
Perhaps you have gotten used to the CLI by now, but some things to remember:
You add ports to a VLAN rather than configuring a VLAN on a port.
You often "enable" a feature in order to the "configure" details of that feature.
A VLAN is "create"d and then you "configure" the properties of it, including when adding ports to it (untagged or tagged).
"Worse than a firewall" 🙂 Which firewall do you refer to?