2015년 12월 14일 월요일

Amazon to Launch Cloud Data Center in Korea



Amazon’s announcement, which the company’s chief cloud evangelist Jeff Barr made in a blog post Wednesday, is yet another example of US-based cloud giants going aggressively after Asia’s rapidly growing cloud services market.
Other recent examples are IBM’s deal with Chinese data center provider 21Vianet to provide its Bluemix Platform-as-a-Service to customers in China and the launch of IBM’s first SoftLayer data center in India. Microsoft launched three cloud data centers in India earlier this year.
Asian cloud service providers are expanding data center capacity in the region too. Chinese e-commerce and cloud giant Alibaba recently brought online a new data center in the Zhejiang Province.
Barr listed existing Korean customers that will be able to take advantage of Amazon’s new cloud data center capacity when it comes online. They include startups, gaming companies, and enterprises, the latter category including the electronics giant Samsung.
“These customers (and many others) have asked us for a local region,” Barr wrote. “We are looking forward to making it available to them and to many other enterprises, startups, partners, government agencies, and educators in Korea.”

http://www.datacenterknowledge.com/archives/2015/11/05/amazon-to-launch-cloud-data-center-in-korea/

Dedicated Servers

2015년 12월 7일 월요일

Amazon brings Microsoft users into AWS with Active Directory service


 Netdedi


Amazon has launched an AWS Directory Service for Active Directory, a fully managed implementation of Microsoft's authentication and user management service.
Using Active Directory in Amazon's cloud will enable companies to bring applications including SQL Server, SharePoint and custom applications built with .NET onto AWS. That's useful for businesses trying to move into the cloud from an on-premises deployment of Microsoft's software. 
When companies start using the service, it creates a pair of domain controllers connected to a user's virtual private cloud running Windows Server 2012 R2. Each domain controller runs in a different availability zone of a user's choosing inside a single region, and Amazon will handle the nuts-and-bolts of managing things like host monitoring, data replication and snapshots.
Administrators will be able to configure a trust relationship between their on-premises Active Directory and the AD in Amazon's cloud, so that users can sign in to both systems using one login. 


Companies can try the service for free for one month or 750 hours, whichever comes first. After that, the service costs US$0.40 per hour. 
It's an interesting move for Amazon, since one of the key products Microsoft uses to push its cloud services into large enterprises is Azure Active Directory -- a fully managed, cloud-based implementation of Microsoft's authentication and user management service with a whole bunch of other services and integrations baked in. It's an easy way to get one part of a business into Azure, which Microsoft can then use to try and upsell companies on other cloud services. 
How Amazon plans to expand this service to better compete against Azure AD remains to be seen, especially as it continues to fight with Microsoft to pursue dominance in the public cloud market.

2015년 11월 26일 목요일

My Local Probe is constantly "disconnected". What can I do?

Change Mac Scan Setting

By default, on services startup, PRTG tries to detect all available network adapters on the system running a probe (this includes, for example, the PRTG core server).
On few systems, this might lead to an exception so that the probe cannot fully connect to the core server. In this case, please try to disable the initial detection of available network cards.
Caution: Please backup your system before manipulating the Windows registry!

Step 1

  • On the system running the PRTG core server, open the registry editor.
  • For a 64-Bit Windows system, go toHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Probe\
  • For a 32-Bit Windows system, go toHKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\Probe\
Note: For PRTG 8 you might see the values in the additional sub-key V7 or V8.

Step 2

  • Add a new DWORD value with the name NoMacScan.
  • Set this to 1 to disable the initial search for network adapters.

2015년 11월 23일 월요일

Top 5 Web Hosting Talk Threads – Nov. 20, 2015



Every week our colleagues at Web Hosting Talk compile the top 5 most popular forum threads. Want to join in the conversation? Leave your thoughts in the comments and visitWeb Hosting Talk to sign up and learn more.
Is Shared hosting secure and safe?
Is shared hosting a good option for an ecommerce site? A small seller and new WHT member wants to know what type of hosting to use on a budget.
How risky is hosting from cheap hosting?
This WHTer wants to know the risks associated with hosting plans that cost $5 or $10 per year. Do you have any exerpience with extremely cheap hosting and insights you can share?
How can we start selling cloud hosting
In this thread a WHT member wants to know how to start selling cloud hosting and whether there is any such thing as a cloud dedicated server.
Someone offered to buy my domain (is it legit?)
A WHTer is looking for some advice around an offer on his domain that may be too good to be true.
Chargeback ~ How do you respond?
How do hosting companies respond toPayPal when customers look for chargeback? That’s the question in this WHT thread, still hot from last week.

2015년 11월 22일 일요일

Virtual Machine in XenServer Will Not Shut Down or Start; Stuck/Frozen Starting/Stopping


Virtual Machine in XenServer Will Not Shut Down or Start; Stuck/Frozen Starting/Stopping

If you’ve worked with XenServer for any length of time, you have no doubt experienced having a VM turn “orange” or “amber” or otherwise become unmanageable.  Here are couple of similar problem scenarios and solutions that might help.

Problem Scenario #1:
You notice that a VM has numerous lifecycle events on a XenServer.  It has continuously attempted to shutdown, but remains in the green/on state.  The VM will not display a console, or POST information.   Manual shutdowns in XenCenter do not work (Shutdown or Force Shutdown).
Solution:
You may have success trying some of these ideas, or it may take a combination of these to obtain control of the stuck VM.
  1. Start by trying an ‘xe-toolstack-restart’ on the pool master server.   This is the easiest fix, and will work a majority of the time.   You will lose connection to your pool momentarily.  If this doesn't work, go onto the next steps listed below.
  2. If this is a XenDesktop hosted VM, put the VM in maintenance mode, if you cannot force a Start/Shutdown from the DDC
  3. From the XenServer console, try the following command to force a shutdown:  ‘xe vm-shutdown –force vm=VMNAME’.  If VM does not shutdown with this command, proceed to next step
  4. In XenCenter, once the above two items are done, attempt to "Reboot" the VM. It may restart now.
Related Issue:
I experienced a similar issue where all members were down in a XenServer pool, but the pool Master remained up and functional.  The 'toolstack' processes were not running on pool members. An ‘xe-toolstack-restart’ was required on each pool member XenServer before the server would appear functional and participate in the XenServer Pool.

Problem Scenario #2:
This is the most common scenario you will see.  A virtual machine will go into an “amber” or “orange” state and you are unable to shutdown, reboot, or even forcefully reset the VM.

Solution:
  1. Find the UUID of the hung VM.
    You can do this via the command line with ‘xe vm-list’ or via XenCenter.
  2. Find the Domain ID of the hung VM.
    Run ‘list_domains’ from the command line, and match the UUID with the ID number
  3.  
    id |                                 uuid |  state
    0  | 2fe455fe-3185-4abc-bff6-a3e9a04680b0 |    R
    47 | 267227f3-a59e-dafe-b183-82210cf51ec4 |    B
    59 | 298817fb-8a3e-7501-11e0-045a8aa860ff |    B
    60 | 46e3d5aa-2f02-dfdc-b053-9a8ac56ec5d1 |    B
    61 | 16cf3204-eb17-5a12-e8d0-c72087bda690 |    B
    62 | 1f9053b5-c6ca-40bb-504e-3017c37e7281 |    H
    63 | ddaec491-097a-e271-362b-f2f985e26e4a |    R
    65 | 55f3b225-4f65-d1ea-aa19-add44c5acce7 |    B
    66 | 7adef6fd-9171-5426-b333-6fb1b57b8e60 |    B H
    67 | 6046dc13-f70b-8398-56fb-069c22440a7c |    B
    68 | f201cd94-a501-00c2-d21e-8c2f03ea167b |    B H
  4. Run destroy_domain on the Domain ID.
     
    # /opt/xensource/debug/destroy_domain -domid 62
  5. The VM will still show itself as running, so now, we need to reboot it.
     
    # xe vm-reboot name-label='name of the VM' –force
  6. The VM is now rebooted, and you can bring it up as if you had just pulled the plug.  That is, check for some disk corruption, etc.

2015년 11월 17일 화요일

Holiday event !!

 Netdedi



Microsoft hones focus on enterprise mobility and security with Azure

http://www.zdnet.com/article/microsoft-hones-focus-in-on-enterprise-mobility-and-security-with-azure/


2015년 11월 8일 일요일

What's the best cloud storage for you?

http://www.zdnet.com/article/whats-the-best-cloud-storage-for-you/

​Vodafone Foundation's DreamLab app to aid cancer research

Designed by B2Cloud, DreamLab -- initially available for download on Android with plans already underway for launch on iOS -- has been built to transform any smartphone into a supercomputer, Vodafone has claimed.
When a smartphone is plugged in and is fully charged, the DreamLab app automatically downloads a small part of the genetic sequencing profiles that the Garvan Institute stores on Amazon Web Services' locally hosted cloud. The information is then processed, and the results are sent back to Garvan researchers, which they can use as part of their research.
Within the free app, users are able to choose which cancer research they wish to support -- breast, ovarian, prostate, and pancreatic -- before selecting how much mobile data they want to use per month, starting at 50 megabytes. Vodafone has committed to waiving fees for the data on behalf of its five million prepaid and postpaid customers.
The launch of the app comes after two years in the making, which also included the trial of a desktop version.
Vodafone Australia CEO Inaki Berroeta told ZDNet the company is always looking at new ways of how it can best use its existing network.
"When we heard about the challenges that the Garvan Institute were having when it came to buying computing power to do all this data-intensive research, that's when we thought about what if we connected millions of smartphones that are idle at night, and we create this supercomputer.
"We could have [used computers] but given the millions of smartphones that are connected to our network, there is much more computing power than any computer. Also, you can see nowadays a smartphone has a computing power that is almost equivalent to a PC."
Andrew Giles, CEO of The Garvan Institute of Medical Research, explained that the initial goal will be to see 100,000 smartphone users power up the DreamLab app, which is expected to help crunch data 3,000 times faster than the current rate, and help address the institute's largest challenge.
"Crunching numbers is our biggest challenge at the moment -- so this will speed up unbelievably. The more we get, the quicker we'll go because there is so much data. The full human genome is an amazing file by itself, but at the moment we focus on things we know ... but there are other genes we're not allocating time to yet, but this means people can do that while it's sleeping," he said.

dreamlab.png
DreamLab app will turn any smartphone into a supercomputer. (Image: Supplied)

According to John Mattick, executive director of The Garvan Institute of Medical Research, the institute is currently generating between one to two petabytes of data per year.
"[This is] just coming from the machines before we get to analysis. The data on individual genos has to be matched by data from their medical data in order to make sense of their genetic sequencing," he said.
"The future of medical research, the future of healthcare is going to be about the use of data, and initially we have to understand this data and the differences in the genetic profile ... and we need enormous processing power."
Giles added that the institute expects to make additional savings, given that this program will mean it won't need to purchase a supercomputer.
"It's more about what we won't have to spend. We've been doing some forward planning [based on] our budget; our IT bills are huge, our storage bills are huge, so if this really gets off it could be tens of thousands [of dollars], or hundreds of thousands if things go really well. We're owned by the University of New South Wales, so obviously we're part of that but it's still expensive," he said.
In addition, Vodafone announced that it will commit AU$400,000 over three years to The Garvan Institute of Medical Research to further help with cancer research.
During its half-year results for 2015, Vodafone continued to record a net loss of AU$183.6 million, up 13.3 percent from the AU$158.6 million loss in the same period last year.
Vodafone Australia's James Marsh at the time attributed the company's loss to acquisition costs, the offer of cheaper international calling and data options for customers, a higher debt due to a number of its liabilities being held in unhedged US dollars, and increased competition.
"We have seen a step up in competition across both the mobile network operators and the MVNOs, particularly in prepaid," he said.
"Our seasonal decline, though, has been at its lowest levels for many years, and we're in a good position for growth in H2.
"We see that [customer base] growing going forward.

2015년 10월 19일 월요일

How to Configure High Availability Feature in XenServer





Instructions


Complete the following procedure to enable and disable HA on your XenServer pool:
  1. To enable HA for your XenServer pool (with three or more hosts), select the Pool Name/Resource Icon:
    User-added image
  2. Right-click the Pool Name/Resource icon and select High Availability...
    User-added image
  3. Alternatively, with the Pool Name/Resource icon highlighted, select the HA tab and select Configure HA…
    User-added image
  4. The Configure HA dialog box appears. Read the requirements before selecting Next.
    User-added image
  5. The configuration wizard scans the pool for a Hearbeat SR. If no suitable SR is found, the wizard will exit and one must establish the High Availability Heartbeat Storage Repository (per requirements).
    User-added image
  6. When an appropriate SR is found, select it and press Next.
    User-added image
  7. The configuration will present all VMs that are currently in the pool. It is from this configuration dialog will allow one or multiple VMs to be selected as to specify:
    1. The HA restart priority that defines if VMs should be – with enough resources available in the pool – Restarted, Restarted if Possible, and Do Not Restart
    2. The Restart Order - 0 being the highest - that specifies the priority of a VM (or VMs) to be started under a fail-over condition
    3. The Attempt to start next VM delay that specifies how much time should pass before starting the next priority-based VM (or group of VMs).  This is to ensure pool resources are not overwhelmed when recovering from a fail-over condition
User-added image
  1. When the HA conditions are specified, selecting Next presents a review of the HA config. Pressing Finish confirms the configuration and apply it to the pool.
    User-added image
  2. With the successful application of the HA configuration across the pool, the HA tab should show the following:
    User-added image
  3. To begin the process of disabling HA for your XenServer pool (with three or more hosts), select the Pool Name/Resource icon:
    User-added image
  4. With the Pool Name/Resource icon highlighted, select the HA tab and select Disable HA…
    User-added image
  5. When prompted to disable HA, select YES.
    User-added image

    The HA is disabled across the pool (for each member).

2015년 10월 16일 금요일

How to set up management access for the N4000 switch


Table of Contents
1.    Setting a management IP address
2.    Setting Login access on the switch
3.    Choosing Telnet, HTTP, SSH, or HTTPS for management
4.    Saving configuration


Article description: This article explains how to set up different management options for the N series switches, and explains the recommended settings


Setting a management IP address
A reachable IP address is needed to manage the switch when not using a serial connection. To set an IP address, input the following commands.
This example uses VLAN 1, the default VLAN, and the IP 192.168.0.250 /24.
console>enable
console#configure
console(config)#interface vlan 1
console(config-if)#ip address 192.168.0.250 255.255.255.0
Note: On the N3000 and N4000 switches there is an out of band port that can be used for managing the switch.
Here is the same example but using the out-of-band (OOB) interface.
console(config)#interface out-of-band
console(config-if)#ip address 192.168.0.250 255.255.255.0
It is recommended to use the OOB interface to manage your switch when available. The OOB interface is separate from the switching silicon,
and reaches the CPU directly. If the production network is experiencing issues, you can still reach the switch through the OOB interface.
Note: Plug the OOB interface into a separate management network, and do not plug it back into the inbound ports on the switch.
It is recommended when using a VLAN to manage your network, to make a separate VLAN just for management.
This separates management traffic from your data traffic. This not only helps with performance, but also slightly increases security.
You can manage the switch through any reachable VLAN IP address.
If managing the switch from an external network, you must assign the switch a Default Gateway it can use to reach other networks.
The following command uses 192.168.0.1 as the Default Gateway address.
console(config)#ip default-gateway 192.168.0.1


Setting login access on the switch.
To manage the switch you will need a username and password. To manage the switch via telnet or SSH, you will require an enable password. Input the following commands to configure login access. This is an example with the username as Dell, and password as P@$$w0rd. The enable password example uses ENP@$$w0rd. These are just examples and you should use more complicated, hard to guess credentials to secure your switch.
console>enable
console#configure
console(config)#username Dell password P@$$w0rd level 15

console(config)#enable password ENP@$$w0rd
Note: You may make multiple users on the switch, as well as different levels/privilege level of access. 0 is no access, 1 in read only, and 15 is read and write.

How to use iSCSI Targets on a Windows Server

How to use iSCSI Targets on a Windows Server

http://www.netdedi.com

Overview

The business-level Synology NAS servers are Microsoft® Windows certified, which means by using the iSCSI Target Service, a Synology NAS seamlessly acts as dedicated storage server to provide iSCSI Target storage for your Hyper-V environment, which will be seen virtually as a local hard drive for as many clients as need be; only they are all stored in a centralized Synology server. Advanced management functions such as Thin Provisioning, iSCSI LUN Backup, MC/S (Multiple Connections per Session) and MPIO (Multipath I/O) are available on Synology NAS to strengthen the usability and stability of a network storage environment. As fully compliant with SPC-3 PR standard, Synology NAS supports Microsoft Windows® Server Failover Clustering as well.
This article will guide you through the process of setting up iSCSI target connection from a Windows Server to your Synology NAS.
What is iSCSI?
iSCSI is an Internet Protocol based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI can facilitate data transfers over local area networks (LANs), wide area networks (WANs), or the Internet. Through iSCSI, the space on storage server will be regarded as local disks by client's operation system. In reality, all data transferred to the disk are actually transferred over network to the storage server.
What is iSCSI Target and LUN?
In SCSI terminology, a LUN (logical unit number) represents an individually addressable (logical) SCSI device that is part of a physical SCSI device (called "Target"). An iSCSI environment emulates the connection to a SCSI hard disk. An iSCSI Target is like a connection interface, and LUNs are essentially numbered disk drives. When an iSCSI Target is connected by an iSCSI initiator (a client), all the LUNs mapped to the iSCSI Target are virtually attached to the client's operation system. Therefore, Initiators can establish and manage file systems on iSCSI LUNs, as they would a raw SCSI or IDE hard drive.

Contents

  1. Before You Start
  2. Create an iSCSI Target
  3. Format iSCSI Target for Use on Windows


1. Before You Start

This article assumes you have performed the following tasks:
  • Hardware installation for Synology NAS.
  • Create iSCSI LUNs and Targets on your Synology NAS.
After the setting above is finished,  you can refer to this article to know how to connect your iSCSI target with Multipath (MPIO).
Refer to Quick Installation Guide for more information about hardware and software installation. You can also see Synology NAS User's Guide (available at Synology's Download Center) for a general idea about topics related to this article.

2. Create an iSCSI Target

This section will guide you through the process of setting up an iSCSI target on a Windows Server.
  1. Open iSCSI Initiator in Windows under Control Panel > Administrative tools.
  2. Nas
  3. Go to Discovery tab and click on Discover Portal.
  4. Nas
  5. Enter the IP Address or the DNS Name of the Synology NAS, which is hosting the iSCSI Target, then click on OK.
  6. Nas
  7. Go to Targets tab.
  8. Select the desired iSCSI target.
  9. Click on Connect.
  10. Nas
  11. Click on OK if no advanced options are enabled on the iSCSI target on the Synology NAS.
  12. Nas
  13. Click on Advanced button if CHAP or any of the Advanced settings are enabled on the iSCSI Target on the Synology NAS.
  14. Nas
  15. Enter the name for CHAP.
  16. Enter the target secret for CHAP.
  17. Click on OK.
  18. The iSCSI target is now connected to the Windows PC.
  19. Nas

3. Format iSCSI Target for Use on Windows

After an iSCSI Target has been connected on a Windows computer, it will have to be formatted before it can be used.
  1. Open Computer Management under Control Panel > Administrative tools.
  2. Nas
  3. Select Disk Management on the left panel. Right click on the iSCSI Target (Disk1) and choose Online.
  4. Nas
  5. Right click on the iSCSI Target (Disk1) again and choose Initialize Disk.
  6. Nas
  7. A prompt will be displayed to initialize the newly added virtual drive. Please select a partition style most appropriate for the disk to be used then click on OK.
  8. Nas
  9. After the disk has been initialized, right click on the new disk (indicated by the black field), and select New Simple Volume.
  10. Nas
  11. Proceed forward with the Simple Volume Wizard.
  12. Nas
  13. Specify the volume size to use for the new hard drive, then click on Next.
  14. Nas
  15. Assign a drive letter for the new hard drive then click on Next.
  16. Nas
  17. Now your Windows Server has an additional drive E: created by Synology iSCSI target.
  18. Nas
Note:
If you want to use Multipath I/O (MPIO) for the iSCSI targets on your Synology NAS, please do the following first:
  1. Go to Storage Manager > iSCSI Target.
  2. Find the desired iSCSI target, and click Edit > Advanced.
  3. Tick Allow multiple sessions from one or more iSCSI initiators.
  4. Click OK.

Linux CPU Info

Linux CPU Info


# cat /proc/cpuinfo

http://www.netdedi.com

2015년 8월 24일 월요일

How to reset the root password in CentOS 6.6

Introduction

Booting straight up to GRUB is not the default boot method for CentOS 5 & 6.
This How-To was written to show you step by step the process of resetting the root password on your CentOS 5/6 installation.

Steps (7 total)

1

Boot or Reboot your CentOS installation

From the console ATL+CTRL+DEL will get you headed in the right direction.
2

Press Any Key

After the installation reboots, it will come up to a boot countdown. Here, you can press any key, I don't have one either, but any other key works also.
This will bring you to the GRUB menu.
3

GRUB Menu

From the GRUB menu, select the appropriate kernel version and press the 'e' key.
You will now be presented with the option menu for the kernel version.
4

Kernel Options Menu

From this menu, select the kernel /vmlinuz-... line and press the 'e' key.
You will now be presented with the kernel boot options.
5

Change Kernel Boot Options

Now we need to add to the end of this line one o the following:
1, s, or single
And now press Enter to save your changes.
6

Boot your temporary options

From this menu, you should already be on the kernel /vmlinuz... line.
Press the 'b' key to boot to these temporary options to allow you to recover your root account.
7

Set Root Password

Now you will boot up to the root shell and you can use passwd to set your new password.
You will be required to enter the password twice.
Once you have completed this, reboot and you have a new root password for your CentOS installation.

2015년 7월 9일 목요일

R610 서버 UEFI 모드 실행 시 멈춤 현상

OS 설치시 화면이 멈추는 현상이 발생



Keyboard 바꾸어 보거나 Front에 있는 USB 사용해보세요~~~~

Multiple IP Addresses to One Single Network Interface

ifcfg-eth0, the default interface for the Ethernet device. If you’ve attached second Ethernet device, then there would be an “ifcfg-eth1” device and so on for each device you’ve attached. These device network files are located in “/etc/sysconfig/network-scripts/” directory. Navigate to the directory and do “ls -l” to list all devices.
# cd /etc/sysconfig/network-scripts/
# ls -l
Sample Output
ifcfg-eth0   ifdown-isdn    ifup-aliases  ifup-plusb     init.ipv6-global
ifcfg-lo     ifdown-post    ifup-bnep     ifup-post      net.hotplug
ifdown       ifdown-ppp     ifup-eth      ifup-ppp       network-functions
ifdown-bnep  ifdown-routes  ifup-ippp     ifup-routes    network-functions-ipv6
ifdown-eth   ifdown-sit     ifup-ipv6     ifup-sit
ifdown-ippp  ifdown-tunnel  ifup-isdn     ifup-tunnel
ifdown-ipv6  ifup           ifup-plip     ifup-wireless
Let’s assume that we want to create three additional virtual interfaces to bind three IP addresses (172.16.16.126172.16.16.127, and 172.16.16.128) to the NIC. So, we need to create three additional alias files, while “ifcfg-eth0” keeps the same primary IP address. This is how we moving forward to setup three aliases to bind the following IP addresses.
Adapter            IP Address                Type
-------------------------------------------------
eth0              172.16.16.25            Primary
eth0:0            172.16.16.26            Alias 1
eth0:1            172.16.16.27            Alias 2
eth0:2            172.16.16.28            Alias 3
Where “:X” is the device (interface) number to create the aliases for interface eth0. For each alias you must assign a number sequentially. For example, we copying existing parameters of interface “ifcfg-eth0” in virtual interfaces called ifcfg-eth0:0ifcfg-eth0:1 and ifcfg-eth0:2. Go into the network directory and create the files as shown below.
# cd /etc/sysconfig/network-scripts/
# cp ifcfg-eth0 ifcfg-eth0:0
# cp ifcfg-eth0 ifcfg-eth0:1
# cp ifcfg-eth0 ifcfg-eth0:2
Open a file “ifcfg-eth0” and view the contents.
[root@tecmint network-scripts]# vi ifcfg-eth0

DEVICE="eth0"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.125
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
Here we only need two parameters (DEVICE and IPADDR). So, open each file with VI editor and rename theDEVICE name to its corresponding alias and change the IPADDR address. For example, open files “ifcfg-eth0:0“, “ifcfg-eth0:1” and “ifcfg-eth0:2” using VI editor and change both the parameters. Finally it will look similar to below.
ifcfg-eth0:0
DEVICE="eth0:0"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.126
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
ifcfg-eth0:1
DEVICE="eth0:1"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.127
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
ifcfg-eth0:2
DEVICE="eth0:2"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.128
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
Once, you’ve made all changes, save all your changes and restart/start the network service for the changes to reflect.
[root@tecmint network-scripts]# /etc/init.d/network restart
To verify all the aliases (virtual interface) are up and running, you can use “ifconfig” or “ip” command.