I too ran into the issue of expecting an IOS switch and got this SBE type switch. Basically what I did was use the GUI to try and configure everything as I wanted first, then compared the default config to the updated one to see what needed to be done via CLI for future devices. Enabling SSH access is 'ip ssh server', but there are also commands to connect it to your preferred authentication method. Here is ours which is still using RADIUS (some are variable strings for our generating script):
radius-server host $(RadiusIP1) key $($RadiusKey) priority 1
radius-server host $(RadiusIP2) key $($RadiusKey) priority 2
radius-server host source-interface vlan $(RadiusVlan)
radius-server timeout 5
radius-server deadtime 3
aaa authentication login SSH radius local
aaa authentication enable SSH radius enable
aaa authentication login Console radius local
aaa authentication enable Console radius enable
aaa authentication login default radius local
line ssh
login authentication SSH
enable authentication SSH
exit
line console
login authentication Console
enable authentication Console
exit
ip ssh server
The 'Index' for the CLI guide is a good place to skim through and see what commands are available (same one Deepak posted) - https://www.cisco.com/c/en/us/td/docs/switches/campus-lan-switches-access/Catalyst-1200-and-1300-Switches/cli/C1300-cli/C1300-cli_CLT_chapter.html
As for the specs, at least based on what they posted on the website, it seems to have similar capability compared to the C1000. I wasn't *too* concerned about it as I'm usually just placing these in closets to connect a building here and there. Of course the big advantage is that it's significantly cheaper than the C9200CX model (which is pretty much the only true 'Catalyst' model that's compact) and doesn't require DNA licensing either, just like the C1000.
