Archive

Posts Tagged ‘ubuntu’

Ubuntu TomCat install from scratch

I am working on a fresh install of Ubuntu 10.04 TLS. Here are my notes for the install…

I wanted to see what is available for my version of Ubuntu

apt-cache search tomcat

I found the complete install of the TomCat6 system

apt-get install tomcat6

I did not want the following packages:

apt-get install tomcat6-admin
apt-get install tomcat6-user

Since I am going to use the Apache mod pass through here is my apache install notes.

Install apache 2.2.x

apt-get install apache2

I then installed the Apache Mod JK

apt-get install libapache2-mod-jk

I went ahead and installed mysql 5.1, this is NOT necessary for most people:

apt-get install mysql-server-5.1

NOTE: This blog post is a work in progress and is not completed, stay tuned.

Linux iSCSI Target Setup

December 9th, 2009 Arthur Gressick 1 comment

I am working on setting our NAS device with iSCSI so that I can run VMware hosts externally. Here are my notes for setting up the iSCSI target and initiator. I am using Ubuntu 9.10 (latest version at the time.) I will be using a 160GB drive and dedicating it solely to run the mount points.

The iSCSI protocol is a storage area network (SAN) protocol which allows iSCSI initiators to use storage devices on the (remote) iSCSI target using normal ethernet cabling. To the iSCSI initiator, the remote storage looks like a normal, locally-attached hard drive.

server1.example.com (Initiator): IP address 192.168.1.100
server2.example.com (Target): IP address 192.168.1.101

Setting up the target [server2]

Installing the software

apt-get install iscsitarget

Modify the config file for iscsitarget

nano /etc/default/iscsitarget

Now enable the ISCSITARGET

ISCSITARGET_ENABLE=true

NOTE: You can use logical volumes, image files, hard drives [/dev/sdb], partitions [/dev/sdb1] or RAID devices [/dev/md0] for storage.

I am going to use the entire 160GB HDD for iSCSI located at sdb1

Edit ietd.conf

nano /etc/ietd.conf

Make sure everything is commented out except what is below

Target iqn.2001-04.com.example:storage.lun1
        # Users, who can access this target. The same rules as for discovery
        # users apply here.
        # Leave them alone if you don't want to use authentication.
        IncomingUser
        OutgoingUser
        # Logical Unit definition
        # You must define one logical unit at least.
        # Block devices, regular files, LVM, and RAID can be offered
        # to the initiators as a block device.
        Lun 0 Path=/dev/sdb,Type=fileio
        # Alias name for this target
        Alias LUN1

NOTE: The target name must be a globally unique name, the iSCSI standard defines the “iSCSI Qualified Name” as follows: iqn.yyyy-mm.[:identifier]; yyyy-mm is the date at which the domain is valid; the identifier is freely selectable. The IncomingUser line contains a username and a password so that only the initiators (clients) that provide this username and password can log in and use the storage device; if you don’t need authentication, don’t specify a username and password in the IncomingUser line. In the Lun line, we must specify the full path to the storage device (e.g. /dev/vg0/storage_lun1, /storage/lun1.img, /dev/sdb, etc.).

Now you can limit the access by IP address

nano /etc/initiators.allow

Add this into the editor

iqn.2001-04.com.example:storage.lun1 192.168.1.19

Now start the service

/etc/init.d/iscsitarget start

I will post an article about connecting to the target from another Linux, Mac or Windows Host in the near future. From VMware ESXi and vSphere 4 just add the vKernel and then in the administration section for storage just type in the IP address of the target. I installed 4 VM Guests on vSphere to test and it worked great.

Network Repair when switching NIC

June 30th, 2009 Arthur Gressick No comments

So recently I have a VMware image go down and needed to move it to another machine. I had problems with the NIC when it was moved. Here I what I did.

In terminal under root I typed

dmesg | grep eth0

You will probably get an error that the eth0 was changed. Take the new name for the eth0 and edit the..

nano /etc/networking/interfaces

I changed the 0 to 1 and then rebooted the machine and everything seemed to work fine.

Other command that I did where

modprobe e1000

or

modprobe pcnet32

Categories: Networking Tags: ,