Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Vlan configuration

Pages: 1 2 3 4 5

Hello,

 

is it possible to create vlan interfaces for the 5 networks on two physical network cards?

 

Regards,

 

Peter.

Sorry, see an other thread about vlans now which states its not supported...

Are there plans to implement?

Best regards,

 

Peter.

Yes we have it in our feature list, but not scheduled yet.

Note that you can still map your 5 subnets to 2 interfaces in current version without vlans.. but all will be in one broadcast domain.

 

Thanks for the answer,

I have 10 proiant G5 servers with 8x600Gb storage each. I was hoping to use these with petasan without a virtualisation layer, but storage is not seen by petasan.

I guess a have to use an virtualiation layer like esxi to see the storage? This also solves the vlan config because i can use esxi to create 5 network adapters on 2 physical...

Best regards,

Peter.

The G5 server is quite old and uses the cciss block kernel driver, disks are presented like /dev/cciss/c0d0p1.

Many new distros like RH 7 do not support it, cciss is replaced by hpsa ( hp smart array) driver since G6 / 2009 as per

http://cciss.sourceforge.net/

hpsa is a scsi driver which works with PetaSAN. Some people report using hpsa with G5,  if you want to try and assuming you can install PetaSAN on a separate system disk., ssh into PetaSAN and:

1) remove cciss driver

rm /lib/modules/4.4.38-petasan/kernel/drivers/block/cciss.ko

2) add hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1 boot options to /boot/extlinux/extlinux.conf

example

APPEND root=/dev/disk/by-uuid/6b0991f0-9055-43a9-9b09-484a154c8fd7   initrd=/initrd.img-4.4.38-petasan net.ifnames=0 quiet

to

APPEND root=/dev/disk/by-uuid/6b0991f0-9055-43a9-9b09-484a154c8fd7   initrd=/initrd.img-4.4.38-petasan net.ifnames=0 quiet hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1

3) reboot

 

This may or may not work..good luck.

Thank you for your answer, this brings me to another question.

you state: "if you want to try and assuming you can install PetaSAN on a separate system disk., ssh into PetaSAN"

Is it possible to install petasan (OS) on a usb stick?

 

Regards

Peter

 

 

No you need a real drive for the system disk, it is used by the Ceph monitors to store cluster state data as well as PetaSAN to store cluster statistics.  i was hoping your hardware provided storage outside the raid controller

I have the same problem with the CCISS drivers on a whole bunch of DL385 servers that I wanted to turn into a ceph cluster.  Is there any way to load the driver on the fly during the boot process, or is there a way to roll up a new ISO with the correct driver installed?

As per my earlier post, the Proliant G5 is quite old and the cciss block driver has been replaced by the hpsa scsi driver since G6.  PetaSAN does not support the cciss driver, many distros such as RH/Centos 7 do not. There are howver some people who reported using the hpsa driver successfully with G5 as in:

https://askubuntu.com/questions/728317/maas-node-deployment-failing-on-hp-proliant-dl380-g5

so you can try it but i do not know for sure if it will work.

Also i do not know too much about the G5, but if you can get a system disk to install PetaSAN on outside of the RAID array and follow my earier post of things to try.

Else if you do not have a separate system disk then maybe you can try the following:

create an install USB from the iso ( using rufus or similar tool ), this makes it easier than re-creating the iso

edit /boot/isolinux/isolinux.cfg
we need to add the following kernel parameters at the end of the append line:
cciss.blacklist=yes modprobe.blacklist=cciss hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1
so original
append loglevel=3 cde vga=791 nomodeset
becomes
append loglevel=3 cde vga=791 nomodeset cciss.blacklist=yes modprobe.blacklist=cciss hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1

If you are lucky, the PetaSAN installer will recognize all the drives as scsi drives and should install.
Then afer installation you can add the same paramters to the boot file on the system hardrive at
/boot/extlinux/extlinux.conf

example

APPEND root=/dev/disk/by-uuid/6b0991f0-9055-43a9-9b09-484a154c8fd7 initrd=/initrd.img-4.4.38-petasan net.ifnames=0 quiet
to
APPEND root=/dev/disk/by-uuid/6b0991f0-9055-43a9-9b09-484a154c8fd7 initrd=/initrd.img-4.4.38-petasan net.ifnames=0 quiet cciss.blacklist=yes modprobe.blacklist=cciss hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1
then reboot
then you can run the Deployment Wizard application and hopefully your drives would be seen.

There is no way for me to check if this will work and it may need some luck to do so.

Good luck 🙂

Thank you! I can confirm that this worked. There's still some life left in these old machines 🙂

Pages: 1 2 3 4 5