Tech Advisor

2017년 11월 6일 월요일

40% 할인 쿠폰

NAS 해놀로지(Xenology) 서비스 제공
NAS 40% 할인 쿠폰: D82JJOR0FVG2 11월30일까지

https://kr.netdedi.com

2017년 9월 18일 월요일

업데이트는 하지 마세요. !!!

1. 내 서비스 -> 개인NAS를 선택합니다.

2. 아래와 같이 지금 사용중인 제품/서비스를 선택합니다.

3. 아래와 같이 해당 장비에 대한 컨트롤 패널이 보입니다.

4. 본인 NAS 장비의 IP를 확인 하기위해, 위 화면의 콘솔 버튼을 누릅니다.
그러면 해당 장비의 ID와 PW를 입력하라는 메세지가 나옵니다. ifconfig를 누르면 IP 정보가 출력됩니다.
Login: admin
Password: @fmspxm_2017
>ifconfig

5. 해당 IP를 확인 후 웹 브라우저의 IP를 입력합니다.
로그인 정보는 Login Info 버튼을 클릭하면 알 수 있습니다.

6. 로그인 후에 디스크 볼륨을 설정하고, 사용하고자 하는 서비스를 설치하여 사용하 실 수 있습니다. 또한, 모바일 기기에서 앱을 설치하여, 언제어디서든 자유롭게 사용하실 수 있습니다.

관련 페이지: https://kr.netdedi.com/index.php?/page/langaddservice/

다운로드 및 설명서

https://www.synology.com/ko-kr/knowledgebase/Mobile/help/DSget
https://www.synology.com/ko-kr/knowledgebase/Mobile/help/DSfile
https://www.synology.com/ko-kr/knowledgebase/Mobile/help/DSphoto
https://www.synology.com/ko-kr/knowledgebase/Mobile/help/DSvideo

2017년 2월 20일 월요일

netdedi.com
Only for new users
Now, 20% off Coupon is available until 28th Feb, 2017
Applies to All products:

A2WBYA2OWU3XAV

Please, visit and take advantage of your right.

Thanks,

2016년 10월 24일 월요일

How to reset Windows Server 2012 administrator password

To reset the password on your Windows 2012 server, simply complete the following steps:

Boot from the Micrsoft Windows Server 2012 DVD
From the Windows Setup menu, click “Next”.
Select “Repair your computer”
Under Choose and option, click on “Troubleshoot”.
Under Advanced options, click “Command Prompt”.
At the command prompt, run the following commands:
d: cd windows\system32
ren Utilman.exe Utilman.exe.old
copy cmd.exe Utilman.exe
Close the command prompt and then click “Continue”.
The server should now boot and present the logon screen. Here click Windows Key + U.
At the prompt you can now change the password, by typing the following command: net user administrator Password123 This will set the password for the Administrator user to be Password123 (case sensitive).

To join the affiliate program, visit at https://www.netdedi.com

2016년 9월 6일 화요일

Installation

First, you should Install and configure DHCP server on your PXE server. To install and configure DHCP server, refer the following link:

Now, install the following packages for setting up PXE environment:

# yum install httpd xinetd syslinux tftp-server -y

Configure PXE Server

# tree /var/lib/tftpboot/
├── CentOS6.5
│   ├── initrd.img
│   └── vmlinuz
├── centos6_5_x86_64
│   └── CentOS-6.5-x86_64-bin-DVD1.iso
├── CentOS7.0
│   ├── initrd.img
│   └── vmlinuz
├── centos_7_x86_64
│   └── CentOS-7-x86_64-DVD-1511.iso
├── chain.c32
├── images
│   ├── centos-6.5-64
│   ├── initrd.img
│   └── vmlinuz
├── initrd.img
├── mboot.c32
├── memdisk
├── menu.c32
├── pxelinux.0
├── pxelinux.cfg
│   └── default
├── Ubuntu14.04
├── ubuntu14.04_64
│   └── ubuntu-14.04.4-server-amd64.iso
├── Ubuntu16.04
├── ubuntu16.04_64
│   └── ubuntu-16.04-server-amd64.iso
└── vmlinuz

Copy the following TFTP configuration files to the /var/lib/tftpboot/ directory.

#cd /usr/share/syslinux/
#cp pxelinux.0 menu.c32 memdisk mboot.c32 chain.c32 /var/lib/tftpboot/

Edit file /etc/xinetd.d/tftp

#vi /etc/xinetd.d/tftp

Enable TFTP server. To d this, change “disable=yes” to “no”.

 # default: off
 # description: The tftp server serves files using the trivial file transfer \
 #       protocol.  The tftp protocol is often used to boot diskless \
 #       workstations, download configuration files to network-aware printers, \
 #       and to start the installation process for some operating systems.
 service tftp
 {
 socket_type             = dgram
 protocol                = udp
 wait                    = yes
 user                    = root
 server                  = /usr/sbin/in.tftpd
 server_args             = -s /var/lib/tftpboot
 disable                 = no
 per_source              = 11
 cps                     = 100 2
 flags                   = IPv4
}

Next, create a directory to store CentOS installation ISO image. and mount the image to that directory as shown below. I have CentOS 6.5 32bit ISO image on my /root directory.

#mkdir /var/lib/tftpboot/centos6.5

#mount -o loop /var/lib/tftpboot/CentOS-6.5-bin-DVD1.iso /mnt

#cp /mnt/images/pxeboot/vmlinuz, initrd.img /CentOS6.5

Create a apache configuration file for PXE server under /etc/httpd/conf.d/ directory:

#vi /etc/httpd/conf.d/pxeboot.conf

Add the following lines:

Alias /centos6_5 /mnt
<Directory /mnt>
Options Indexes FollowSymLinks
Order Deny,Allow
Deny from all
Allow from 58.x.x.0/26
</Directory>

Save and close the file.

Then, create a configuration directory for PXE server:

#mkdir /var/lib/tftpboot/pxelinux.cfg

Now, create PXE server configuration file under the pxelinux.cfg:

#vi /var/lib/tftpboot/pxelinux.cfg/default

Add the following lines:

default menu.c32
prompt 0
timeout 300
ONTIMEOUT local
Menu title ########## PXE Boot Menu ##########
LABEL CENTOS 6.5 Installation
MENU LABEL centos-6.5-64
KERNEL CentOS6.5/vmlinuz
APPEND initrd=CentOS6.5/initrd.img method=http://58.x.x.50

*Ubuntu
Make sure you are using the one from /install/netboot/ubuntu-installer/amd64

LABEL HardDisk
MENU LABEL ^Hard DIsk
LOCALBOOT 0x80

Configure DHCP Server

Now, we have to configure the DHCP server to work with PXE server.

Edit file /etc/dhcp/dhcpd.conf,

#vi /etc/dhcp/dhcpd.conf

Add the following lines at the end:

allow booting;
allow bootp;
next-server 58.x.x.50;
filename "pxelinux.0";

Save and close the file.

Now, We have come to the end of PXE server configuration. Restart all the services to complete the configuration.

service xinetd restart
service httpd restart
service dhcpd restart

Configure HTTPD Server

DocumentRoot "/var/www/html"

ServerName 58.x.x.50

#cp /mnt/* /var/www/html/

Installation with Kickstart File

#vi /var/lib/tftpboot/pxelinux.cfg/default

default menu.c32
prompt 0
timeout 300
ONTIMEOUT local
menu title ########## PXE Boot Menu ##########
LABEL CENTOS 6.5 Installation
MENU LABEL centos-6.5-64
KERNEL CentOS6.5/vmlinuz ksdevice=eth0
APPEND initrd=CentOS6.5/initrd.img ks=http://IP Address/ks.cfg

LABEL CENTOS 7.0 Installation
MENU LABEL centos-7.0-64
KERNEL CentOS7.0/vmlinuz
APPEND initrd=CentOS7.0/initrd.img ks=http://IP Address/centos7/ks.cfg

LABEL Ubuntu 14.04 Installation
MENU LABEL Ubuntu 14.04
KERNEL
APPEND

LABEL HardDisk
MENU LABEL ^Hard DIsk
LOCALBOOT 0x80

CentOS 6.5

#vi ks.cfg
# Kickstart file automatically generated by anaconda.
#version=DEVEL
install
url --url=http://IP Address/
lang en_US.UTF-8
keyboard us
network --onboot yes --device eth0 --bootproto dhcp
rootpw --iscrypted $6$VW.mEEJY9d2fKaNb$3fPvVgdrgrKVwYNVmtU5sWzB3BbiCo.1W5gO4FVE3/6vU.gBZCDtrJ4Urf.f2T3c87gSlPqQYqkKU39tzVsCN1
firewall --service=ssh
authconfig --enableshadow --passalgo=sha512
selinux --enforcing
timezone --utc Asia/Seoul
bootloader --location=mbr --driveorder=sda --append="crashkernel=auto rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --drives=sda

#volgroup VolGroup --pesize=4096 pv.008002
#logvol /home --fstype=ext4 --name=lv_home --vgname=VolGroup --grow --size=100
#logvol / --fstype=ext4 --name=lv_root --vgname=VolGroup --grow --size=1024 --maxsize=51200
#logvol swap --name=lv_swap --vgname=VolGroup --grow --size=7968 --maxsize=7968

part /boot --fstype=ext4 --size=500
part swap --fstype=swap --recommended
part / --fstype=ext4 --size=940000

#part pv.008002 --grow --size=1

repo --name="CentOS" --baseurl=http://IP Address --cost=100

reboot

%packages
@core
@server-policy
@workstation-policy
%end

CentOS 7.0

#vi ks.cfg

#version=DEVEL
# System authorization information
auth --enableshadow --passalgo=sha512
# Use network installation
url --url="http://IP Address/centos7"
# Use graphical install
graphical
# Run the Setup Agent on first boot
firstboot --enable
ignoredisk --only-use=sda
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us'
# System language
lang en_US.UTF-8

# Network information
network  --bootproto=dhcp --device=eno1 --onboot=on --ipv6=auto
network  --bootproto=dhcp --device=eno2 --onboot=on  --ipv6=auto
network  --hostname=localhost.localdomain

# Root password
rootpw --iscrypted $6$b.HgyW9b6uH9fHvQ$mjPxiumdpTatP3GXL9ziIaUpxUVcreGFjG0Vb8iEU9nJuXISLnlAzcGnFQB1I2svRvdodz8zWw4qqeCzYnkH50
# System timezone
timezone Asia/Seoul --isUtc
# System bootloader configuration
bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda
# Partition clearing information
clearpart --all --initlabel --drives=sda
# Disk partitioning information
part /boot --fstype="xfs" --ondisk=sda --size=500
part pv.369 --fstype="lvmpv" --ondisk=sda --size=953368
volgroup centos --pesize=4096 pv.369
logvol /  --fstype="xfs" --grow --maxsize=51200 --size=1024 --name=root --vgname=centos
logvol swap  --fstype="swap" --size=8064 --name=swap --vgname=centos
logvol /home  --fstype="xfs" --grow --size=500 --name=home --vgname=centos

reboot

%packages
@^minimal
@core
kexec-tools
wget
net-tools
%end

%addon com_redhat_kdump --enable --reserve-mb='auto'

%end

2016년 8월 23일 화요일

How to Assign SR-IOV Enabled NICs with XenServer 6.x

Objective

This article describes how to assign SR-IOV enabled Network Interface Cards (NICs) to Virtual Machines (VMs) for maximum performance by using the Single Route I/O Virtualization (SR-IOV) capabilities of XenServer 6.1.0.
Note: SR-IOV is supported only with SR-IOV enabled NICs listed on the XenServer Hardware Compatibility List (HCL) and only when used in conjunction with a Windows Server 2008 guest operating system.

Single Root I/O Virtualization (SR-IOV) is a PCI device virtualization technology that allows a single PCI device to appear as multiple PCI devices on the physical PCI bus. The actual physical device is known as a Physical Function (PF) while the others are known as Virtual Functions (VF). The purpose of this is for the hypervisor to directly assign one or more of these VFs to a VM using SR-IOV technology: the guest can then use the VF as any other directly assigned PCI device.
Assigning one or more VFs to a VM allows the VM to directly exploit the hardware. When configured, each VM behaves as though it is using the NIC directly, reducing processing overhead and improving performance.

WARNING! If your VM has an SR-IOV VF, functions that require VM mobility are not possible. For example, Live Migration, Workload Balancing, Rolling Pool Upgrade, High Availability and Disaster Recovery, cannot be used. This is because the VM is directly tied to the physical SR-IOV enabled NIC VF. In addition, VM network traffic sent via an SR-IOV VF bypasses the vSwitch, so it is not possible to create Access Control Lists (ACL) or view Quality of Service (Qos).

Instructions

To enable SR-IOV on Intel NICs:

WARNING! Customers must not attempt to boot a SR-IOV enabled VM before carrying out the following steps.

For Intel 1GBe NICs edit /etc/modprobe.d/igb and uncomment the line that includes:
#options igb max_vfs=7,7,7,7
For Intel 10GBe NICs edit /etc/modprobe.d/ixgbe and uncomment the line that includes:
#options ixgbe max_vfs=40,40

To assign an SR-IOV enabled NIC VF to a Virtual Machine on XenServer 6.1.0:

Open a local command shell on your XenServer host.
Run the command lspci to display a list of the Virtual Functions (VF).
For example:
07:10.0 Ethernet controller: Intel Corporation 82559 Ethernet Controller Virtual Function (rev 01)
In this example, 07:10.0 is the bus:device.function address of the VF.
Assign the required VF to the target VM by running the following commands:
xe vm-param-set other-config:pci=0/0000:<bus:device.function> uuid=<vm-uuid>
Start the VM, and install the appropriate VF driver for your specific hardware.
Note: You can assign multiple VFs to a single VM, however the same VF cannot be shared across multiple VMs.

2016년 7월 29일 금요일

XenServer 7.0: Release Notes Welcome to XenServer 7.0.

XenServer 7.0: Release NotesWelcome to XenServer 7.0.
This document provides important information about the XenServer 7.0 release. For frequently asked questions about XenServer, refer to the XenServer 7.0 Technical FAQ. Documentation may be updated or changed after the initial release. Citrix suggests regularly visiting the XenServer 7.0 page on Citrix Product Documentation to learn about updates. Customers can download the latest version of the XenServer 7.0.0 Base Installation ISO from the XenServer Product Download page.

Note: The XenServer 7.0.0 Base Installation ISO has been reissued on 6 July 2016 to include hotfix XS70E004. The reissued ISO also contains an updated version of the XenCenter Management Console (v7.0.1). This version of XenCenter is same as the version available to download on the XenServer 7.0 Download page and hotfix XS70E001.