VMware NSX-T has a preconfigured password expiration policy of 90 days.
Attention you lower your security standards if you never change your password.
Same procedure for nsx-t edge nodes the same.
clear user admin password-expiration
clear user root password-expiration
clear user audit password-expiration
I think it is better you change your password once a year
set user admin password-expiration 365
set user root password-expiration 365
set user audit password-expiration 365You can use Office Online Server with Seafile. How to install OOS you can read it here.
https://docs.microsoft.com/en-us/officeonlineserver/deploy-office-online-server
Config File for Seafile
vim /opt/seafile/conf/seahub_settings.py
# Enable Office Online Server
ENABLE_OFFICE_WEB_APP = True
# Url of Office Online Server's discovery page
# The discovery page tells Seafile how to interact with Office Online Server when view file online
# You should change `http://example.office-web-app.com` to your actual Office Online Server server address
OFFICE_WEB_APP_BASE_URL = 'http://192.168.2.131/hosting/discovery'
# Expiration of WOPI access token
# WOPI access token is a string used by Seafile to determine the file's
# identity and permissions when use Office Online Server view it online
# And for security reason, this token should expire after a set time period
WOPI_ACCESS_TOKEN_EXPIRATION = 30 * 60
# List of file formats that you want to view through Office Online Server
# You can change this value according to your preferences
# And of course you should make sure your Office Online Server supports to preview
# the files with the specified extensions
OFFICE_WEB_APP_FILE_EXTENSION = ('ods', 'xls', 'xlsb', 'xlsm', 'xlsx',
'ppsx', 'ppt','pptm', 'pptx', 'doc', 'docm', 'docx')
# Enable edit files through Office Online Server
ENABLE_OFFICE_WEB_APP_EDIT = True
# types of files should be editable through Office Online Server
# Note, Office Online Server 2016 is needed for editing docx
OFFICE_WEB_APP_EDIT_FILE_EXTENSION = ('xlsx', 'pptx', 'docx')
restart seahub service
found here
https://blog.csdn.net/weixin_43136674/article/details/103484972
Here we go, I have to put these card on to my server with C620 chipset. I need fast local storage.
The card is not very expensive but i need 4×4 TB SSD on these server. So we started with a simple test. I bought 4x 16 GB Optane SSD for under 14 $ per piece. When it runs with this SSD so it will run also with the big ones.
That this runs we need a chipset that supports bifurcation with PCIe. With bifurcation you can split your 16x PCIe lane into 2×8, 4x4x4x4x or 8x4x4x. We need 4x4x4x4x every SSD needs 4x PCIe lanes. Would you read more about this topic look here https://blog.donbowman.ca/2017/10/06/pci-e-bifurcation-explained/
I have not really enough space. On this server there are also 4x 2080 TI graphics cards. It was very close that the card fit in it.
Next step was to configure the BIOS(UEFI) to talk correctly to this card. The automatic mode is not working. In automatic mode it detect only one SSD, the first one on the Asus card.
I used on the motherboard slot 10, this information is important to configured PE3 on CPU2 correct. We look in the manual of the motherboard to see which slot is connected with the CPU. Slot11 is not working there is not enough PCIe lanes only 4x. We need 16x to split into 4x4x4x4x
Let´s jump in to the BIOS.
On the BIOS follow the rabbit pictures.
We have to choose the right CPU. We use PE3 on CPU2
Change the IOU2 from Auto to 4x4x4x4, every SSD should runs with 4x PCIe lanes.
That was it.
Check under Linux with the command dmidecode -t 9
What a pain in the ass. If you use mount.cifs under Ubuntu 20.04 and now you have stale file handle to edit files and more.
We look in to the manpage from mount.cifs and there is a option to solve this issue.
noserverino Client generates inode numbers itself rather than using the actual ones from the server.
See section INODE NUMBERS for more information.
Today I have startet some release upgrades for some Ubuntu 16.04 VM machines. Sometimes I am strungling with this error.
error processing archive /var/cache/apt/archives/lxd_1%3a0.9_all.deb (--unpack):
apt purge lxd lxd-client
Attention if you need snap you should reinstall it
Found here
https://askubuntu.com/questions/1280499/upgrade-from-18-04-lts-to-20-04-lts-fails
Today I had a request from our user for add a PCIe SSD card to a server. One option is you walk to this server and open it. This not the best option to check if it a PCIe slot available.
Another option is use your Linux commandline.
You need your server mainboard manual to see which slot is labeled.
You have only to check under current usage is in use or available.
Current Usage: Available
dmidecode -t 9
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.
Handle 0x000B, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT2 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Long
ID: 2
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:18:00.0
Handle 0x000C, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT4 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 4
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:3b:00.0
Handle 0x000D, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT6 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 6
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:86:00.0
Handle 0x000E, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT8 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 8
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:af:00.0
Handle 0x000F, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT9 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: Available
Length: Short
ID: 9
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0010, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT10 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: Available
Length: Short
ID: 10
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0011, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT11 PCI-E 3.0 X4(IN X8)
Type: x4 PCI Express 3 x8
Current Usage: Available
Length: Short
ID: 11
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0012, DMI type 9, 17 bytes
System Slot Information
Designation: M.2 CONNECTOR
Type: x4 M.2 Socket 2
Current Usage: In Use
Length: Short
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:02:00.0A very long time I used ha-proxy for lb to publish Exchange OWA/Active-Sync in to the WWW. After the installation with NSX-T. I have the opportunity to replace my old ha-proxy configuration with the integrated LB from NSX-T. I would like to replace the ha-proxy for internal MAPI namespace. Normally that will be used often KEMP LB or ha-proxy. With NSX-T you can also replace this product. To Replace MAPI Namespace lb is very simple that will be used only TCP for lb.
I will not write how to deploy the LB that can you read here.
https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-D39660D9-278B-4D08-89DF-B42C5400FEB2.html
I will show you some configuration where not included in the knowledge base.
To protect your Administrator interface from external access. In my old ha-proxy configuration I had a ACL to protect ecp from external.
For the OWA rule you must add a forwarding rule with this options.
For your SSL configuration you need your domain certificate and intermediate certificates also.
You need Client SSL and Server SSL. You can use twice the same certificate,.
Before you can assign the certificates you have to import the certificates for your domain and the intermediate certificates under System = >Certificates
After importing the certificates you can assign this to your Virtual Servers HTTP 7 rule.
Trusted CA Certificates means your intermediate certificate.
VM wil not power-on and throws the following error:
Object type requires hosted I/O
SSH into the ESX-host that’s hosting the VM.
Browse to the VM-folder containing the disk files.
Run the following command in ESXI CLI:
vmkfstools -x check “disk.vmdk”
Disk needs repaired
vmkfstools -x repair “disk.vmdk”
Disk was successfully repaired.
Start VM from vCenter
found here
https://tklaassens.wordpress.com/2019/05/13/object-type-requires-hosted-i-o/
What a incredible e-mail from Atlassian, cloud first. Not everyone wants to use the cloud. I worked with Confluence and Jira over ten years now. Time for alternative Wikis. I am a little bit sad about the cloud first strategy. Confluence and Jira are pretty cool tools.
Time for alternative Wiki´s
This Wiki very close to Confluence. But one feature is missing
https://wiki.js.org/feedback/p/multi-sites
Multi Sites
BlueSpice based on MediaWiki but it have a lot more features and a good Editor.
bluespice.com
Multi Sites only available in the enterprise version.
Also look at tiki.org but is more than a wiki
For Jira alternative
I found
I had a heck of a time figuring out how to set this up. Cisco’s documentation related to LDAP authentication is all over the place and there isn’t one article that describes just this. If you want to use Microsoft Active Directory to authenticate users locally logging in to the ASA and give them privileged exec access based on a Group, here are the steps.
These steps assume you are using ASDM, but I have attached the CLI equivalents as well.
1. Log in to the ASA with ASDM (CLI steps below)
2. Go to Device…
View original post 1,113 more words
