@travisdh1 said in RAID on SSD's:
@ccwtech said in RAID on SSD's:
For some reason I recall that booting to a RAID 5 was unreliable (shouldn't do), but it's been so long since I have worked with RAID 5 I'm not sure where I heard that.
RAID 5 on HDD is unreliable today, and shouldn't ever be used. SSD drives don't have the same issues. That might be what you're remembering.
I believe so as well.
For some reason I recall that booting to a RAID 5 was unreliable (shouldn't do), but it's been so long since I have worked with RAID 5 I'm not sure where I heard that.
... But I do have another question... For SSD's...
If you are doing RAID 5, would you ever use that as a boot volume? Or do a RAID 1 for boot and RAID 5 for data?
@jaredbusch
Do I need to do multiple Virtual NIC's for that? (1 for each Vmachine?)
I've been teaming my NIC's recently but notice when you team you get 2 GB (expected) but then the VEthernet connection is only 1 GB.
Is there any real value if the hyper-v NIC only shows 1 GB?
I have it up and running. (DNS)
Even my guest WIFI on a VLan is now getting DHCP addresses. Everything is working great now.
Works after FW upgrade.
I SSH'ed into the AP
typed:
mca-cli
set-inform http://xx.xx.xx.xx:8080/inform
Then
info
I get "Unable to resolve (http://unifi:8080/inform)"
@dbeato
Thought I was okay, but can't log in using http, just https.
It's causing a problem when I try to set the AP's to look to the vultr IP for the controller.
Also, in creating a DNS entry to point to my Vultr server, is that best done on my DNS for my domain name on GoDaddy or locally on my DC?
@dashrender
Is this a config I need to do on my Netgear switch?
@dbeato Working great now! Thanks.
root@UBNT_Controller:~# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:27117 0.0.0.0:* LISTEN 16476/bin/mongod
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 334/sshd
tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 13860/mongod
tcp6 0 0 :::8843 :::* LISTEN 15628/java
tcp6 0 0 :::8880 :::* LISTEN 15628/java
tcp6 0 0 :::8080 :::* LISTEN 15628/java
tcp6 0 0 :::22 :::* LISTEN 334/sshd
tcp6 0 0 :::8443 :::* LISTEN 15628/java
tcp6 0 0 :::6789 :::* LISTEN 15628/java
root@UBNT_Controller:~#
Looking at the firewall now.
@dbeato said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
netstat -ano | grep listening
No output from that command.
root@UBNT_Controller:~# service unifi status
● unifi.service - unifi
Loaded: loaded (/lib/systemd/system/unifi.service; enabled; vendor preset: en
Active: active (running) since Sun 2017-12-17 19:56:30 UTC; 1h 45min ago
Main PID: 15614 (jsvc)
CGroup: /system.slice/unifi.service
├─15614 unifi -cwd /usr/lib/unifi -home /usr/lib/jvm/java-8-openjdk-a
├─15616 unifi -cwd /usr/lib/unifi -home /usr/lib/jvm/java-8-openjdk-a
├─15617 unifi -cwd /usr/lib/unifi -home /usr/lib/jvm/java-8-openjdk-a
├─15628 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx1024M -XX:
└─16476 bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117 --uni
Dec 17 19:56:29 UBNT_Controller systemd[1]: Starting unifi...
Dec 17 19:56:30 UBNT_Controller unifi.init[15558]: Starting Ubiquiti UniFi Contr
Dec 17 19:56:30 UBNT_Controller systemd[1]: Started unifi.
Ok, in the meantime I'm trying https://unifi.xx.xx.xx.xx:8443 and not getting anything. Shouldn't that work?
When using Vultr is it just https://unifi.hostname.vultr.com:8443 ?
This is how I have the Meraki setup. When I use the Wifi on the Meraki, things work as they should.
