제2의 비엔지니어 인생관을 꿈꾸며

Posted
Filed under Study
Zentyal을 한글로 선택해서 설치하거나 Active Directory 설정에서 한글명은 깨져서 나오는 문제로 인하여 영문이름으로 써야했었는데 아래와 같은 방법으로 폰트 설정으로 깨짐현상을 해결할수가 있습니다. 웹메일에서도 한글명이 제대로 출력되어서 불편함이 없어졌습니다.
Zentyal이 우분투기반에서 만들어졌기 때문에 동일합니다.

Add your locale to /var/lib/locales/supported.d/local, one per line. For instance, to add English language (en_US) append this line:
en_US.UTF-8 UTF-8
ko_KO.UTF-8 UTF-8
Regenerate locales package by running:
$ sudo dpkg-reconfigure locales


$sudo apt-get install fbterm

$sudo apt-get install ttf-nanum-coding //한글 폰트 설치 (14.04에서는 fonts-nanum-coding로 변경)

$sudo fbterm

사용자 삽입 이미지

2016/04/23 21:49 2016/04/23 21:49
Posted
Filed under Study


If you want to know the SMB version that Windows is using, connect a share, open an admin cmd window and run
powershell
Get-SmbConnection

 


OmiOS
Start with current LTS stable: 151014  LTS (long term stable) and optionally update to a newer release
what allows a go back to LTS



Manual Installation:


1. download OmniOS  stable

http://omnios.omniti.com/wiki.php/Installation

You can setup OmniOS from USB  (use .dd file, 1 GB+ USB stick) or CD (.iso)
You can use this imager www.napp-it.org/doc/downloads/usb image.zip
to transfer the usb image to your stick (Windows)

2. Install OmniOS
2a. Option: Install on ESXi, create a new VM (Solaris 10-64) with e1000 and/or  vmxnet3 vnic  (16 GB disk min, 25GB+ suggested)
use 2 GB min RAM (best is 8GB+  or 1/3 of available) and 2 cores
Read my manual about setup napp-in-one: http://www.napp-it.org/doc/downloads/napp-in-one.pdf

2b. Install on Hardware:
You can install Omni + napp-it onto Sata or fast USB sticks >=32 GB)
If you use USB, use reliable/fast sticks, best are USB enclosures with an 2,5" Sata SSD

You can also use one or two Sata DOMs for a boot mirror, see http://www.supermicro.com/products/nfo/SATADOM.cfm
(prefer this over USB)

Read my manual about setup napp-it: http://www.napp-it.org/doc/downloads/napp-it.pdf


Reboot now!

3. After installation, login as root (no pw)

4. setup network. Network is set to (per default): network/physical:default,
enter blue commands at console

4.1 create interface
- list available interfaces and use linkname ex e1000g0:

(optional: enable Jumbo Frames first: dladm set-linkprop -p mtu=9000 e1000go)

dladm show-link
ipadm create-if e1000g0


5. use DHCP (or skip to 6.0 to use a static adress)
ipadm create-addr -T dhcp e1000g0/dhcp


5.1 add nameserver
echo 'nameserver 8.8.8.8' >> /etc/resolv.conf

5.2  use dns (copy over DNS template)
cp /etc/nsswitch.dns /etc/nsswitch.conf

If something happens (typo error), retry, opt. delete interface ex ipadm delete-if e1000g0

5.3 install napp-it (newest free)
wget -O - www.napp-it.org/nappit | perl

5.4 l
start napp-it from your Desktop via Browser
http://serverip:81 (use real server-ip of your server)
You can check your ip at console with command ifconfig

reboot after installation of napp-it  (or check napp-it menu "snapshots - be" that current BE is default)
reboot (mostly not needed)




Next step 6. is an option to 5. (use either 5. dhcp or 6. manual setup)

6.0  add static IP address
  6.1 create static adress
  ipadm create-addr -T static -a 192.168.0.1/24 e1000g0/v4

  6..2 add default route
  route -p add default 192.168.0.254

If something happens (typo error), retry, opt. delete interface ex ipadm delete-if e1000g0

6.3 install napp-it (newest dafault for Free/Pro)
wget -O - www.napp-it.org/nappit | perl

6.4 login to napp-it via any web-browser
(you can request ip via ifconfig -a )
http://ip of your server:81

reboot after installation of napp-it  (or check napp-it menu "snapshots - be" that current BE is default)
reboot (mostly not needed)


Modify OS defaults

The OmniOS defaults are suboptimal regarding network settings (ip-buffer), NFS settings, AHCI Hotplug behaviour (disabled per default) or disk timeouts (up to 3 minutes on problems, way to high should be reduced to a TLER alike timeout of 7s).

On napp-it Pro, you can enable improved settings with the base tuning option in System > System Tuning




7. enable remote root access
Napp-it menu Services-SSH allow root

(Re) Enter a root pw at consoler: passwd root (this creates a SMB pw as well)
You are now able to connect via WinSCP (or putty) as root
passwd root

8. opt.  netatalk 3.1
Using the repo http://scott.mathematik.uni-ulm.de/
wget -O - www.napp-it.org/afp | perl 

9. opt. Update OmniOS to newest
pkg image-update (or pkg update)

10.  opt. install TLS email


Check OmniOS repos for other apps:

http://omnios.omniti.com/wiki.php/Packaging
http://pkg.omniti.com/omniti-ms/en/index.shtml and
http://pkg.omniti.com/omnios/release/en/index.shtml
http://pkg.thetube.ch:10001
http://scott.mathematik.uni-ulm.de/

or use the pkin repo from Joyent
see http://napp-it.org/downloads/binaries.html
http://pkgsrc.joyent.com/installing.html


10. Vmware-tools (ESXi 5.5) and OmniOS

If you want to install VMware tools in OmniOS, you can either mount the tools iso manually according to http://napp-it.org/doc/ESXi-OmniOS Installation HOWTO en.pdf within ESXi or

- open the Installer ESXi iso with 7Zip (file VMware-VMvisor-Installer-5.5.0-1331820.x86_64.iso)
- then open TOOLS.T00 and then the file TOOLS with 7zip

- Open the folder 5.5.0/vmtools
You can see all tool-isos now

- Open Solaris ISO
- Open vmware-solaris-tools.tar.gz
- Open vmware-solaris-tools.rar

- Copy the folder vmware-tools-distrib to your OmniOS /root folder (ex use WinSCP)
- change permissions of this folder to 777 recursively
- open a console on OmniOS (as root) and run perl /root/vmware-tools-distrib/vmware-install.pl

Be aware of problems with e1000 vnics on ESXi 5.5 (see http://napp-it.org/downloads/index en.html )
I suggest to use vmxnet3 vnics until this proble is solved by Vmware

Ensure that the Fibre Channel HBA is Detected

# prtconf -D | grep qlc
pci1077,15d, instance #0 (driver name: qlc)
pci1077,15d, instance #1 (driver name: qlc)

Determine the PCI Address of the Fibre Channel HBA

# mdb -k
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs sd ip hook neti arp usba uhci stmf stmf_sbd qlc fctl sockfs md lofs random idm crypto smbsrv nfs sppp ipc ptm fcp cpc fcip nsmb ufs logindmux ]
> ::devbindings -q qlc
ffffff01cb184040 pciex1077,2532, instance #0 (driver name: qlc)
ffffff01cb183d90 pciex1077,2532, instance #1 (driver name: qlc)
> $q

Now we will need this from the above output pciex1077,2532.

Deactivate the QLC Driver for the Fibre Channel HBA

Remove the default driver (qlc) from the adapter.

# update_drv -d -i 'pciex1077,2532' qlc

Activate the QLT Driver for the Fibre Channel HBA

Add the target driver (qlt) to the adapter.

# update_drv -a -i 'pciex1077,2532' qlt

Reboot the Machine

# reboot

Confirm the HBA is using the QLT Driver

# prtconf -D | grep qlt
pci1077,15d, instance #0 (driver name: qlt)
pci1077,15d, instance #1 (driver name: qlt)

# mdb -k
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs sd ip hook neti arp usba uhci stmf stmf_sbd fctl sockfs lofs random idm crypto cpc smbsrv nfs fcip sppp ufs ptm ipc ]
> ::devbindings -q qlc
> ::devbindings -q qlt
ffffff01cb184040 pciex1077,2532, instance #0 (driver name: qlt)
ffffff01cb183d90 pciex1077,2532, instance #1 (driver name: qlt)
> $q

Configure the SCSI Target Service

# svcs stmf
STATE          STIME    FMRI
disabled       13:27:08 svc:/system/stmf:default

# svcadm enable stmf

# svcs stmf
STATE          STIME    FMRI
online         13:29:54 svc:/system/stmf:default

Display the Status of the SCSI Target Service

The ALUA Status is what allows a LUN to be served via FC and iSCSI at the same time.  We do not require or want it.

# stmfadm list-state
Operational Status: online
Config Status     : initialized
ALUA Status       : disabled
ALUA Node         : 0
2016/04/20 21:51 2016/04/20 21:51
Posted
Filed under Study
Unable to add esxi host to vcenter Datacenter.QueryConnectionInfo
사용자 삽입 이미지
Cannot contact the specified host. The host may not be available on the network, a network configuration problem may exist, or the management service on this host is not responding
There are lots of actions you need to follow. In my case non of those action resolved my issue except one step no#5
Here are the quick steps you need to follow to find out why you are having Datacenter.QueryConnectionInfo error message while adding host to vcenter.
  1. Lockdown mode is enabled on the ESXi host
  2. Incorrect credentials are entered when adding the ESXi host.
  3. Try full fqdn and add again.
  4. Check DNS settings on vcenter and ESXi host
  5. Your vcenter does not support the ESXi host build number. This issue started to appear after recent upgrade on Esxi 5.5 servers. If your vcenter server is below  vCenter Server 5.5 Update 3b you cannot add host running ESXi 5.5 Update 3b. You need to upgrade your vCenter server to 5.5 U3b in order to add ESXi 5.5 U3b host.
ESXi Build number 3248547
vCenter Server 5.5 Update 3b Build No 3252642

필자는 5번째 이슈에 걸렸습니다. 똑같은 5.5 버젼인데 OS도 바꿔보고 지웠다 깔고 서비스 재시작하고 여러번을 반복해도 원인을 알수가 없었습니다.
구글에 검색해보니 5.5 버젼에서만 Update 빌드버젼이 다르면 호스트 추가 오류가 발생 한다는걸 알게되었습니다. 벰웨어도 잠깐 공부좀 해볼까 해서 설치하는데 이런데서 막히니까 그냥 포기할려다가 해결된 케이스였습니다. Hyper-V 에만 손에 익숙해서인지 보통 벰웨어가  구축 및 설정이 더 편하다고 인식되었는데 그냥 복불복 아닌가 생각이 들고 있습니다.
2016/03/06 22:54 2016/03/06 22:54