1. Upgrade your existing controller to the latest version ( Download from here https://www.ui.com/download/unifi/ ) run through setup and install over the top which will upgrade it
  2. Backup your existing Database
  3. Install New Version of Controller on new server
  4. On Launch for the first time, Restore the Backup file to the new server
  5. Migrate AP’s to new Controller using SSH defined here ( Usually same as controller )



    SSH login Username : ubnt
    Password : 

    After login run : 

    set-inform http://dnsnameofnewcontroller.domain.local:8080/inform
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

This was due to a misconfiguration on the vsf  

  member 2

      type "JL255A" mac-address xxxxxx

      priority 128

      link 1 2/23-2/24

      link 1 name "I-Link2_1"

      link 2 name "I-Link2_2"

Should of been :

  member 2

      type "JL255A" mac-address xxxxxxxxx

      priority 128

      link 1 2/23

      link 1 name "I-Link2_1"

      link 2 2/24

      link 2 name "I-Link2_2"

      exit

   port-speed

 

Commands to run to remove a link from a vsf member : 

no vsf member 2 link 1 2/24

then

vsf member 2 link 2 2/24

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently on setting up a new internet connection, I ran a speed test via ( speedtest.net ) with produced the following error

Latency Test Error – Could not connect to the test server A firewall could be blocking the connection or the server might be having some issues

Pinging Google DNS Server 8.8.8.8 came up with a sold under 15m response , strange?

I tried playing around with the MTU to no avail either

Turns out this is actually a DNS issue, the local DNS servers had forwarders set to their Old ISP , so change the DNS to the new ISP or Google fixed this!

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

I had a segment a network recently into a few Vlans. This meant the new Vlan was on a different subnet to the WDS server so machines were not getting the PXE Traffic.

  1. Make sure the WDS is routable from the Vlan ( Create a route enable firewall) 
  2. Enable a second IP Helper Address with the WDS server. You might already have an IP Address if your DHCP server is on a different Subnet, but you can have multiple.

PXE does not come with a dedicated boot protocol. It is simply DHCP packets extended with additional DHCP options. It’s formerly known as the bootstrap protocol. If a PXE-enabled network card sends out an DHCP discover package, it will add DHCP option 60, which includes the string “PXEClient:Arch:xxxxx:UNDI:yyyzzz”. Then it waits for DHCP offers.

It will only respond if it gets a DHCP offer including option 60 which means: I am PXE capable and able to send out boot server and boot file information.

The DHCP offer can be splitted into two independent packages, coming from different servers. The DHCP server can send out the DHCP offer containing the clients IP address and the PXE server can send out the DHCP offer containing the option 60.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I had to tag some Access points to a new Vlan on a Cisco switch , the cisco support website is the worst readability so notes for future reference

Find the Port of the Access point by getting the Mac address then listing all the Macs on the switch via

show mac address-table

Tagging port

Ok next we change the port from an access port on the default Vlan ( 1 ) to a trunk to it can carry multiple Vlans in this case 1,5. Warning this will drop the network device for a few pings

conf t

int gi1/0/21

Switchport mode trunk
Switchport trunk allowed vlan 1,5 

If it doesn’t work you can always wipe the config via

default interface gi1/0/21

To untag a port on vlan 5

 switchport access vlan 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

To access the Secondary unit without changing HA Primary unit , which I would advise against if you are not sure of the VPN status run the following

execute ha manage 1

Login with the credentials

Then run 

diagnose vpn ike gateway

Lists all the current VPNS

diagnose vpn tunnel stat

Check how many are up

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
configure mstp revision 3
##Sets STPD Mode (MSTP)
configure stpd s0 mode mstp cist
##Binds all Vlans to STPD
enable s0 auto-bind vlan 1-4094
##Enable below for all ports APART from Uplinks
configure s0 ports auto-edge on #<ports>
##Enables STPD
enable stpd s0
##SAVE config
save config primary
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)