Skip to main content

Installing Intel Raid Web Console 2 on Ubuntu

Intel has a linux compiled version for RedHat based systems in the download center, but it can be installed on Debian based systems too.

First download the linux version for your architecture using the link above and unzip the zip file to a specific folder.

$ mkdir raid_web_console
$ unzip -d ir3_Linux_x86_RWC2_v13.04.03.01_r2.zip -d raid_web_console

Now, we are going to install alien tool to convert rpm packages to deb packages.

$ sudo apt-get install alien

cd into raid_web_console directory and convert rpm files to deb.

$ alien --scripts Lib_Utils2-1.00-02.noarch.rpm
$ alien --scripts RAID_Web_Console_2-13.04.03-01.noarch.rpm
$ alien --scripts sas_ir_snmp-13.04-0301.i386.rpm
$ alien --scripts sas_snmp-13.04-0301.i386.rpm

And finally install new deb files

$ sudo dpkg -i *.deb

And that’s all, now, you can launch the console using this command:

$ /usr/local/RAID\ Web\ Console\ 2/startupui.sh &

slapd[20001]: <= bdb_equality_candidates: (mail) not indexed

This message is showed because the ldap server does not have mail attribute indexed.
To create an index for that attribute create a file with this content:

file mail_add_index.ldif

dn: olcDatabase={1}hdb,cn=config
add: olcDbIndex
olcDbIndex: mail eq,sub

Now, simply add the index with the following command:

# ldapmodify -Y EXTERNAL -H ldapi:/// -f mail_add_index_ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={1}hdb,cn=config"

Postfix virtual users with Dovecot

This is a little tutorial for setting up Postfix with dovecot authentication and LDA. With dovecot LDA you can use sieve scripts for mail filter and vacation messages.

Postfix Configuration:

First create vmail user for virtual delivery:

# useradd vmail
# id vmail 
uid=1002(vmail) gid=1003(vmail) grupos=1003(vmail)

We are going to deliver mails for user@domain.com to /var/mail/domain.com/user
For virtual transport we set dovecot. virtual_mailbox_domains are domains that we host in this server and virtual_mailbox_maps is a table to look for valid mailboxes in the server.

main.cf

# delivery
virtual_mailbox_domains = domain1.com, domain2.com
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
mail_spool_directory = /var/mail
virtual_mailbox_base = /var/mail
mailbox_size_limit = 0
recipient_delimiter = +
virtual_minimum_uid = 100
virtual_alias_maps = hash:/etc/postfix/virtual_alias
virtual_mailbox_maps = hash:/etc/postfix/virtual_mailbox

/etc/postfix/virtual_alias

postmaster@domain1.com	postmaster@otherdomain.com
postmaster@domain2.com	postmaster@otherdomain.com

Rebuild table with:

# postmap /etc/postfix/virtual_alias

/etc/postfix/virtual_mailbox
This fiile is only listing mailboxes that are going to accept for local delivery.

user1@domain1.com  OK
user2@domain1.com  OK
user1@domain2.com  OK
user3@domain2.com  OK

Rebuild table with:

# postmap /etc/postfix/virtual_mailbox

master.cf

In postfix master.cf file we set for submission service dovecot authentication. In this way only authenticated users are allowed to relay mails to external domains.

In the last line we configure dovecot for local delivery agent.

submission inet n       -       -       -       -       smtpd
  -o smtpd_tls_security_level=encrypt
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_sasl_type=dovecot
  -o smtpd_sasl_path=private/auth
  -o smtpd_sasl_security_options=noanonymous
  -o smtpd_sasl_local_domain=$myhostname
  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
  -o smtpd_recipient_restrictions=permit_sasl_authenticated,reject_unauth_destination

[...]
dovecot   unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop}

Dovecot configuration:

/etc/dovecot/vusers.conf
We use this file for authentication as a users database. You can use too a mysql db or ldap for this, but the simplest way is to use a plain file for storing users an its passwords.

info@domain1.com:{SHA256}gSGn1f3fg0lTRDezXhC7uJqp3XapE8uT7W42PKDDLyY=
admin@domain2.com:{SHA256}PtkqLjF6lRo3h6WAQOVbuZQ/2d7hupW5BCv0Vx/q7gY=

To generate the passwords we use doveadm command.

$ doveadm pw -s sha256
Enter new password: 
Retype new password: 
{SHA256}SKqtTLTAct6agUe7MQDvTgOtYyjtxJWWTQXiATus88w=

The following settings are the files I have to change in dovecot to configure the authentication through vusers.conf file and the socket for postfix authentication for mail submission service.

10-auth.conf

auth_mechanisms = plain
!include auth-static.conf.ext

auth-static.conf.ext

passdb {
  driver = passwd-file
  args = username_format=%u /etc/dovecot/vusers.conf
}

userdb {
  driver = static
  args = uid=vmail gid=vmail home=/var/mail/%d/%n
}

10-mail.conf

mail_home = /var/mail/%d/%n
mail_location = maildir:/var/mail/%d/%n
mail_uid = 1002
mail_gid = 1003
mail_privileged_group = vmail

10-master.conf

under “service auth” configure the auth-userdb socket with user/group vmail and the socket for postfix authentication with user/group postfix.

unix_listener auth-userdb {
    #mode = 0666
    user = vmail
    group = vmail
  }

  # Postfix smtp-auth
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
    user = postfix
    group = postfix
  }

15-lda.conf

lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes

And that’s all, we have a postfix server using dovecot authentication and dovecot LDA. Now, you can install the sieve plugin for dovecot and use for mail filtering and vacations messages.

Proxmox two node cluster

Although a two node cluster is not recomended for HA due to split brain problem (see Two-Node_High_Availability_Cluster in Proxmox wiki for more info with this config), you can set it up in Proxmox for a basic cluster usage. A two node cluster has an special cman configuration in order to maintain the quorum when one node is not available.

To configure a two node cluster in proxmox, copy /etc/pve/cluster.conf to /etc/pve/cluster.conf.new and edit the new file changing the following line:

<cman keyfile="/var/lib/pve-cluster/corosync.authkey"/>

to:

<cman keyfile="/var/lib/pve-cluster/corosync.authkey" two_node="1" expected_votes="1"/>

Now, you can activate it through the proxmox web interface in datacenter -> HA, review the changes and activate them for the two nodes. Now you can restart one node without losing cluster quorum.