This document outlines a bunch of items/forum posts that I have used in the past for assisting in getting additional functionality/usage out of my Unifi Switches.
The obvious is the Edge Switch CLI Command Reference
Or for those that like it all shown out EdgeSwitch CLI Tree
And a simple walk through straight from UBNT.
Unifi Switch can be SCP'd into if needed. Credentials are typically under Settings -> Site -> Device Authentication.
Note: If you make any changes via the CLI using the Edge Switch subsection, it will be removed next time the switch gets provisioned from the Controller. (Reboot, or a physical change in the Controller). You can keep the changes using json files within the USG, but Unifi has not stated that they will add support to allow this within the Unifi Switches. If you are planning on doing any huge configuration via the CLI, your better buying an Edge Switch instead.
Commands:
US.v3.7.55# telnet localhost //This allows access into CLI of the Unifi Switch (similar config as the Edge Switch)
US.v3.7.55# mca-dump //This allows exportation of the json file to the screen which can be used to be captured if needed.
My First impressions of the Unifi Switch infrastructure is pretty sweet, it does 99% of the items that you will need to do, but I then ran into a configuration issue trying to establish trunks (L2 MPLS VPN) over a local provider and determined that the GUI was just simply not cutting the configuration properly. After logging into the CLI and issuing some Edge Switch show commands, I realized that some of the MTU size values, allowed trunks, and native vlans was not set proper, even though in the GUI it is expected/shown as being right.
The obvious is the Edge Switch CLI Command Reference
Or for those that like it all shown out EdgeSwitch CLI Tree
Unifi Switch can be SCP'd into if needed. Credentials are typically under Settings -> Site -> Device Authentication.
Note: If you make any changes via the CLI using the Edge Switch subsection, it will be removed next time the switch gets provisioned from the Controller. (Reboot, or a physical change in the Controller). You can keep the changes using json files within the USG, but Unifi has not stated that they will add support to allow this within the Unifi Switches. If you are planning on doing any huge configuration via the CLI, your better buying an Edge Switch instead.
Commands:
US.v3.7.55# telnet localhost //This allows access into CLI of the Unifi Switch (similar config as the Edge Switch)
US.v3.7.55# mca-dump //This allows exportation of the json file to the screen which can be used to be captured if needed.
My First impressions of the Unifi Switch infrastructure is pretty sweet, it does 99% of the items that you will need to do, but I then ran into a configuration issue trying to establish trunks (L2 MPLS VPN) over a local provider and determined that the GUI was just simply not cutting the configuration properly. After logging into the CLI and issuing some Edge Switch show commands, I realized that some of the MTU size values, allowed trunks, and native vlans was not set proper, even though in the GUI it is expected/shown as being right.
Comments
Post a Comment