- 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
- Backup your existing Database
- Install New Version of Controller on new server
- On Launch for the first time, Restore the Backup file to the new server
- Migrate AP’s to new Controller using SSH defined here ( Usually same as controller )
SSH login Username : ubnt
After login run :
This was due to a misconfiguration on the vsf
type "JL255A" mac-address xxxxxx
link 1 2/23-2/24
link 1 name "I-Link2_1"
link 2 name "I-Link2_2"
Should of been :
type "JL255A" mac-address xxxxxxxxx
link 1 2/23
link 1 name "I-Link2_1"
link 2 2/24
link 2 name "I-Link2_2"
Commands to run to remove a link from a vsf member :
no vsf member 2 link 1 2/24
vsf member 2 link 2 2/24
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 184.108.40.206 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!
Find the Firmware using : https://h10145.www1.hpe.com/support/SupportLookUp.aspx (Search for JL Model of Device )
Issue write memory to save running config
Make sure you login to webportal as Manager
Update the Primary using the File
Once Uploaded issue reboot
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.
- Make sure the WDS is routable from the Vlan ( Create a route enable firewall)
- 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.
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
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
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
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
diagnose vpn ike gateway
Lists all the current VPNS
diagnose vpn tunnel stat
Check how many are up
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>
enable stpd s0
save config primary
The unit was an Elitedesk 800 G3
Download the driver bundle from here : http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html
Extract the Drivers then Import them into Out of Box Drivers on your MDT Share
Once done Update Deployment Share
Once done , replace image on the Microsoft Deployment Services
WIM’s will be installed to
Create a new Interface under a port or an existing virtual switch where the Aruba switch uplinks to
Enter Vlan ID and Interface IP
Next you will need to setup Allow Policies to allow traffic from the Vlan to the normal lan as well as internet
Create a New Vlan with the Same ID
Add a trunk to the Uplink
Tag all the Ports with Vlan 2 that will have a phone plugged into them, Including the Trunk
Untag any ports the phone system or VOIP card might use
Attach the “voice” to the Vlan which will assign the right vlans for the phones that use LLDP