[Quick Tips: Centos/ RedHat7]: How to Configure PPPOE in Centos 7/RHEL 7

How to Configure PPPOE in Centos 7/RHEL 7

The Point-to-Point Protocol over Ethernet (pppoe or PPPOE) is a network protocol for encapsulating PPP frames inside Ethernet frames. It appeared shortly after the year 2000, in the context of the boom of DSL as the solution for tunneling packets over the DSL connection to the ISP’s IP network, and from there to the rest of the Internet.
A PPPoE session is initiated by using connection software on the client machine or router. PPPoE session initiation involves the identification of the Media Access Control (MAC) address of the remote device.When a PPPoE session is initiated, the destination IP address is only used when the session is active. The IP address is released after the session is closed, allowing for efficient re-use of IP addresses.

Configuring PPPOE connection in CENTOS 7
Check the package rp-pppoe installed or not by using command
#rpm -qa rp-pppoe
By Default the package is not installed in RHEL7/CentOS 7 install the Package by using the command.

#yum install rp-pppoe -y
Login as root user and Type pppoe-setup in terminal.
It prompts for user name (input the user name provided by ISP)
Then it Prompts for Interface input the interface name(check the interface name by using the nmcli con show command) and press Enter.

INTERFACE

Enter the Ethernet interface connected to the PPPoE modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethX, where 'X' is a number.
(default eth0): enp3s0

It Prompts like Do you want the link to come up on demand, or stay up continuously?

Do you want the link to come up on demand, or stay up continuously?
If you want it to come up on demand, enter the idle time in seconds
after which the link should be dropped.  If you want the link to
stay up permanently, enter 'no' (two letters, lower-case.)
NOTE: Demand-activated links do not interact well with dynamic IP
addresses.  You may have some problems with demand-activated links.
Enter the demand value (default no): no

Give the DNS server address1(8.8.8.8)  and  DNS server address2(4.2.2.2)  and press Enter.

Please enter the IP address of your ISP's primary DNS server.
If your ISP claims that 'the server will provide dynamic DNS addresses',
enter 'server' (all lower-case) here.
If you just press enter, I will assume you know what you are
doing and not modify your DNS setup.
Enter the DNS information here: 8.8.8.8
Please enter the IP address of your ISP's secondary DNS server.
If you just press enter, I will assume there is only one DNS server.
Enter the secondary DNS server address here: 4.2.2.2

Type your password carefully and press Enter and  Retype your password.

USERCTRL

Please enter 'yes' (three letters, lower-case.) if you want to allow
normal user to start or stop DSL connection (default yes): yes

Choose the firewall type 0.

FIREWALLING

Please choose the firewall rules to use.  Note that these rules are
very basic.  You are strongly encouraged to use a more sophisticated
firewall setup; however, these will provide basic security.  If you
are running any servers on your machine, you must choose 'NONE' and
set up firewalling yourself.  Otherwise, the firewall rules will deny
access to all standard servers like Web, e-mail, ftp, etc.  If you
are using SSH, the rules will block outgoing SSH connections which
allocate a privileged source port.

The firewall choices are:
0 - NONE: This script will not set any firewall rules.  You are responsible
          for ensuring the security of your machine.  You are STRONGLY
          recommended to use some kind of firewall rules.
1 - STANDALONE: Appropriate for a basic stand-alone web-surfing workstation
2 - MASQUERADE: Appropriate for a machine acting as an Internet gateway
                for a LAN
Choose a type of firewall (0-2): 0

If you want this connection at boot time type Yes or don’t want to connect at boot time type no and press Enter. After completed you will the settings

summary report

After it ask to Accept these settings and adjust configuration files (y/n)? input y and press enter.Reboot the system.

check pppoe connection ststus by using ip address show command or check configuration by using ifconfig ppp0 command
To enable the connection manually edit the  file /etc/sysconfig/network-scripts/ifcfg-ppp0 and set DEMAND=yes
To connect  it manually type #ifup ppp0
To disconnect it manually type #ifdown pppo

 

[Quick Tips: Kill/ Pkill Users/ Process] :

Force / Kill Logout a User

You terminate a session by killing its parent process, called the session leader. Find out which process it is with:

# ps -dN|grep pts/3

And then kill that process using 

# kill -9 <processid>

Kill and Logout a User

# skill -KILL -u vivek

[CentOS - iSCSI Server / Client]: iSCSI Server installation Providing Remote block storage

iSCSI Server installation Providing Remote block storage

iSCSI Server installation and configuration RHEL7 Providing Remote Block Storage
iSCSI means Internet Small SCSI System Interface, We will use iSCSI connectivity because it is cost effective compare to FC connection. Fibre Connection required separate Hardware such as like FC switch (SAN Switch) FC switch is more cost compare to normal network switch. To provide iSCSI based storage we do not required any extra environment because we can make use of existing Network switches. Let’s see how this technology is going to work for us iscsi server installation and configuration RHEL 7 providing remote block storage.
We have different types of storage’s such as

1. DAS – Directly attache storage
2. NAS – Network Attached Storage
3. SAN – Storage Area Network

iSCSI protocol comes under SAN (Storage Area Network) To allocate remote block storage to clients below are the steps we have to follow

1. Create one Partition
2. Create LVM using that partition (Don’t format)
3. Install iSCSI Utilities if not available
4. Create LUN and Map to iSCSI client
5. iSCSI server = Target. iSCSI Client = Initiator.

Let’s see below is the process of creating and mapping the iSCSI LUN from iSCSI server to Client.
Environment
Server IP =192.168.4.27
Client IP = 192.168.4.13
By Installing and configuring this iSCSI Server, We are Turing Linux box as SAN.  

Creating Partition

Here i have new HDD called /dev/sdb 10GB with no partitions

[root@iSCSIServer ~]# fdisk -l /dev/sdb

Disk /dev/sdb: 10.7 GB, 10737418240 bytes, 20971520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xea9e3f19

Device Boot Start End Blocks Id System

Standard partition creation and converting standard to LVM

[root@iSCSIServer ~]# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): n
Partition type:
 p primary (0 primary, 0 extended, 4 free)
 e extended
Select (default p):↵
Using default response p
Partition number (1-4, default 1):↵
First sector (2048-20971519, default 2048): ↵
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-20971519, default 20971519): +2G
Partition 1 of type Linux and of size 2 GiB is set

Command (m for help): p

Disk /dev/sdb: 10.7 GB, 10737418240 bytes, 20971520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xea9e3f19

Device Boot Start End Blocks Id System
/dev/sdb1 2048 4196351 2097152 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list all codes): 8e
Changed type of partition 'Linux' to 'Linux LVM'

Command (m for help): p

Disk /dev/sdb: 10.7 GB, 10737418240 bytes, 20971520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xea9e3f19

Device Boot Start End Blocks Id System
/dev/sdb1 2048 4196351 2097152 8e Linux LVM

Command (m for help): wq
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

Update to Kernel when we create new partition, partition table should be up-to date other wise partition will not be listed, use below command to update

[root@iSCSIServer ~]# partprobe /dev/sdb

Creating Physical Volume, Volume Group and Logical Volume

[root@iSCSIServer ~]# pvcreate /dev/sdb1
 Physical volume "/dev/sdb1" successfully created

[root@iSCSIServer ~]# vgcreate VG0 /dev/sdb1
 Volume group "VG0" successfully created
[root@iSCSIServer ~]# vgs
 VG #PV #LV #SN Attr VSize VFree
 VG0 1 0 0 wz--n- 2.00g 2.00g
 rhel 1 2 0 wz--n- 39.51g 44.00m

[root@iSCSIServer ~]# lvcreate -l 100%FREE -n iscsilv VG0
WARNING: ext4 signature detected on /dev/VG0/iscsilv at offset 1080. Wipe it? [y/n]: y
 Wiping ext4 signature on /dev/VG0/iscsilv.
 Logical volume "iscsilv" created.

iSCSI Server Installation Providing Remote block storage

As per above output we just created Logical Volume but we did no formatted, Means we did not created any file system in it.

[root@iSCSIServer ~]# yum install targetcli*

Installed:
 targetcli.noarch 0:2.1.fb37-3.el7

Dependency Installed:
 pyparsing.noarch 0:1.5.6-9.el7 python-configshell.noarch 1:1.1.fb14-1.el7 python-kmod.x86_64 0:0.9-4.el7 python-rtslib.noarch 0:2.1.fb50-1.el7 python-urwid.x86_64 0:1.1.1-3.el7

Complete!

Targetcli is the command to enter into iscsi console

targetcli command

Create Storage Object and Create IQN (iSCSI Qualified Name) to map LUN. This IQN we should take from iSCSI client machine, either we can create our own.

/> /backstores/block create LUN /dev/VG0/iscsilv

/> /iscsi create iqn.2017-03.com.arkit:iSCSIClient1

Creating Storage Object

Go to iSCSI Client Side

Client side we have to install iscsi utilities to connect iscsi server. 
Install iscsi-initiator-utils-iscsiuio-6.2.0.873-29.el7.x86_64 rpm in iSCSI client

[root@iSCSIClient ~]# yum install iscsi*

Get IQN number from Client machine and add to server for mapping disk from server.

[root@iSCSIClient ~]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:ba1abe3b1a4

Enable and Start iscsid service

[root@iSCSIClient ~]# systemctl enable iscsid.service
ln -s '/usr/lib/systemd/system/iscsid.service' '/etc/systemd/system/multi-user.target.wants/iscsid.service'
[root@iSCSIClient ~]# systemctl start iscsid.service

[root@iSCSIClient ~]# systemctl status iscsid.service
iscsid.service - Open-iSCSI
 Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled)
 Active: active (running) since Sun 2016-10-23 19:19:49 IST; 11s ago
 Docs: man:iscsid(8)
 man:iscsiadm(8)
 Process: 4144 ExecStart=/usr/sbin/iscsid (code=exited, status=0/SUCCESS)
 Main PID: 4146 (iscsid)
 CGroup: /system.slice/iscsid.service
 ├─4145 /usr/sbin/iscsid
 └─4146 /usr/sbin/iscsid

Oct 23 19:19:49 iSCSIClient iscsid[4145]: iSCSI daemon with pid=4146 started!
Oct 23 19:19:49 iSCSIClient systemd[1]: Started Open-iSCSI.

Come Back to iSCSI Server side

Now add client IQN in server so that we can map LUN

/> /iscsi create iqn.1994-05.com.redhat:ba1abe3b1a4
Created target iqn.1994-05.com.redhat:ba1abe3b1a4.
Created TPG 1.
Global pref auto_add_default_portal=true
Created default portal listening on all IPs (0.0.0.0), port 3260.
/> /iscsi/iqn.1994-05.com.redhat:ba1abe3b1a4/tpg1/acls create iqn.1994-05.com.redhat:ba1abe3b1a4
Created Node ACL for iqn.1994-05.com.redhat:ba1abe3b1a4

Create New LUN using existing LVM and map to client

/> /iscsi/iqn.1994-05.com.redhat:ba1abe3b1a4/tpg1/luns create /backstores/block/LUN
Created LUN 0.
Created LUN 0->0 mapping in node ACL iqn.1994-05.com.redhat:ba1abe3b1a4

Portal Creation in Server to map

/> /iscsi/iqn.1994-05.com.redhat:ba1abe3b1a4/tpg1/portals create 192.168.4.14
Using default IP port 3260
Could not create NetworkPortal in configFS.

If your able to see above error while creating portal then do delete default port 0.0.0.0 then create new

/> /iscsi/iqn.2017-03.com.arkit:iscsiclient1/tpg1/portals delete 0.0.0.0 ip_port=3260
Deleted network portal 0.0.0.0:3260
/> /iscsi/iqn.1994-05.com.redhat:ba1abe3b1a4/tpg1/portals create 192.168.4.14
Using default IP port 3260
Created network portal 192.168.4.14:3260.

Save the configuration 

/> saveconfig
Last 10 configs saved in /etc/target/backup.
Configuration saved to /etc/target/saveconfig.json

Exit from the Console

/> exit
Global pref auto_save_on_exit=true
Last 10 configs saved in /etc/target/backup.
Configuration saved to /etc/target/saveconfig.json

Allow Firewall Port to communicate with iSCSI Client

3260 iscsi default port 

[root@iSCSIServer ~]# firewall-cmd --permanent --add-port=3260/tcp
success
[root@iSCSIServer ~]# firewall-cmd --permanent --add-port=3260/udp
success
[root@iSCSIServer ~]# firewall-cmd --reload
success

Client Side to connect iSCSI LUN

[root@desktop4 ~]# iscsiadm -m discovery -t st -p 192.168.4.27
192.168.4.27:3260,1 iqn.1994-05.com.redhat:ba1abe3b1a4

[root@desktop4 ~]# iscsiadm -m node -T iqn.1994-05.com.redhat:ba1abe3b1a4 -p 192.168.4.27 -l
Logging in to [iface: default, target: iqn.1994-05.com.redhat:ba1abe3b1a4, portal: 192.168.4.27,3260] (multiple)
Login to [iface: default, target: iqn.1994-05.com.redhat:ba1abe3b1a4, portal: 192.168.4.27,3260] successful.

After successful mapping of LUN now you can create file system on LUN, To Create file system repeat Step 1 (Creating Partition)

[root@iSCSIClient ~]# partprobe /dev/sda
[root@iSCSIClient ~]# mkfs.ext4 /dev/sda1
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=1024 blocks
327680 inodes, 1308672 blocks
65433 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1340080128
40 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
 32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done 
Writing inode tables: done 
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

[root@iSCSIClient ~]# mkdir /ravi


[root@iSCSIClient ~]# vim /etc/fstab 
[root@iSCSIClient ~]# cat /etc/fstab |grep sda
/dev/sda1 /ravi ext4 _netdev 0 0
[root@iSCSIClient ~]# mount -a
[root@iSCSIClient ~]# df -h |grep ravi
/dev/sda1 2.0G 20M 2.0G 1% /ravi

Enjoy…………….

Mail Server - Install Zimbra Collaboration Suite 8.7 in Ubuntu 14.04 LTS

Install Zimbra Collaboration Suite 8.7 in Ubuntu 14.04 LTS

Zimbra collaboration suite, shortly ZCS, is a free, open source software suite that can be used for messaging and collaboration. It comes with two editions, open source edition which is free to use, and network edition which is commercial version, consists of some closed-source components. Zimbra supports Emails, Calendar, and contacts, and document sharing. For ore details, visit the official website, link given at the end of this article, to know more about Zimbra.

This tutorial describes how to install Zimbra collaboration suite in Ubuntu 14.04 LTS server. For the purpose of this guide, I will be using the two test boxes, running with Ubuntu 16.04 LTS and Ubuntu 14.04 LTS. Here is the details of each test box.

Zimbra server:

• Operating System : Ubuntu 14.04 LTS
• Hostname : zimbra.ostechnix.lan
• IP address : 192.168.1.105/24

DNS server:

• Operating system : Ubuntu 16.04 LTS
• Hostname : pri.ostechnix.lan
• IP address : 192.168.1.200/24

You should use separate systems for Zimbra and DNS servers. Here is the minimum requirement for Zimbra deployment.

• Quad core or higher configuration CPU
• 8GB RAM or more
• 50GB hard disk
• Fast Internet connectivity
• A perfect DNS configuration
• Firewall should be disabled

Let us get started.

First things first

Before installing Zimbra, you need to do the following prerequisites steps.

First of all, update the Ubuntu server:

sudo apt-get update

sudo apt-get upgrade

sudo apt-get dist-upgrade

Install necessary dependencies:

sudo apt-get install build-essential

Edit /etc/hosts/ file, and add FQDN (fully qualified domain name) of your Ubuntu server as shown below.

sudo nano /etc/hosts

192.168.1.105 zimbra.ostechnix.lan zimbra

Save and close the file.

Then, we must add the DNS server IP address in your Ubuntu server’s network configuration file.

To do so, edit /etc/network/interfaces file:

sudo nano /etc/network/interfaces

Add DNS server IP address as shown below.

dns-nameservers 192.168.1.200

Then, edit /etc/resolv.conf file, and add DNS server IP address.

sudo nano /etc/resolv.conf

nameserver 192.168.1.200

Then, add the proper MX records in your DNS server. Go to your DNS server and add the Ubuntu server details as shown below. Please note that a separate DNS server is mandatory. You shouldn’t use single system for both DNS and Zimbra servers.

Reboot your system once to take effect the saved changes.

Edit the forward and reverse zone files, and add your Zimbra server’s details.

sudo nano /etc/bind/for.ostechnix.lan

Add the following lines. Replace the IP address and FQDN with your own values.

@ IN A 192.168.1.105
zimbra.ostechnix.lan. A 192.168.1.105
zimbra.ostechnix.lan. MX 0 zimbra.ostechnix.lan.
ostechnix.lan. MX 0 zimbra.ostechnix.lan.

Then, open the reverse zone files and add the same lines.

sudo nano /etc/bind/rev.ostechnix.lan

@ IN A 192.168.1.105
zimbra.ostechnix.lan. A 192.168.1.105
zimbra.ostechnix.lan. MX 0 zimbra.ostechnix.lan.
ostechnix.lan. MX 0 zimbra.ostechnix.lan.

Save and close the file. Restart DNS service to take effect the changes.

sudo systemctl restart bind9

Go back to your Zimbra server and test the DNS server settings using command:

nslookup zimbra.ostechnix.lan

Sample output:

Server: 192.168.1.200
Address: 192.168.1.200#53

Name: zimbra.ostechnix.lan
Address: 192.168.1.105

If you an output something like above, it’s good to go.

Install Zimbra

Go to the Zimbra download page and download the latest version using command:

As of writing this, Zimbra 8.7.0 stable version is not yet available for Ubuntu 16.04 LTS. Installing beta version in production would be a bad idea. If you still want to deploy Zimbra in Ubuntu 16.04 LTS, you can go ahead. The installation instructions are same for all versions.

Download the latest ZCS from the following location depending upon the distribution you use. As of writing this guide, the latest stable version was 8.7.

 Download Zimbra Collaboration suite 8.7

wget https://files.zimbra.com/downloads/8.7.0_GA/zcs-8.7.0_GA_1659.UBUNTU14_64.20160628202701.tgz

Once downloaded, extract it suing command:

tar xvfz zcs-*

Go to the extracted folder:

cd zcs-*

Now, start the deploying Zimbra collaboration suite using command:

sudo ./install.sh

Type “Y” and press ENTER to accept the license agreement.

Operations logged to /tmp/install.log.2JeUNWmH
Checking for existing installation...
 zimbra-ldap...NOT FOUND
 zimbra-logger...NOT FOUND
 zimbra-mta...NOT FOUND
 zimbra-dnscache...NOT FOUND
 zimbra-snmp...NOT FOUND
 zimbra-store...NOT FOUND
 zimbra-apache...NOT FOUND
 zimbra-spell...NOT FOUND
 zimbra-convertd...NOT FOUND
 zimbra-memcached...NOT FOUND
 zimbra-proxy...NOT FOUND
 zimbra-archiving...NOT FOUND
 zimbra-core...NOT FOUND


----------------------------------------------------------------------
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
SYNACOR, INC. ("SYNACOR") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.

License Terms for this Zimbra Collaboration Suite Software:
https://www.zimbra.com/license/zimbra-public-eula-2-6.html
----------------------------------------------------------------------



Do you agree with the terms of the software license agreement? [N]

Install Zimbra

Zimbra installer will ask you a series of yes or no type questions throughout the installation. Just read and answer them accordingly.

Press Y to add Zimbra package repository.

Checking for installable packages

Found zimbra-core
Found zimbra-ldap
Found zimbra-logger
Found zimbra-mta
Found zimbra-dnscache
Found zimbra-snmp
Found zimbra-store
Found zimbra-apache
Found zimbra-spell
Found zimbra-memcached
Found zimbra-proxy

Use Zimbra's package repository [Y] ## Press ENTER

Next, you need to select Zimbra Packages you want to install. The installer will display the packages one by one. Just press ENTER to install the package of your choice.

For the purpose of this tutorial, I am going to install all components.

Select the packages to install

Install zimbra-ldap [Y]

Install zimbra-logger [Y]

Install zimbra-mta [Y]

Install zimbra-dnscache [Y]

Install zimbra-snmp [Y]

Install zimbra-store [Y]

Install zimbra-apache [Y]

Install zimbra-spell [Y]

Install zimbra-memcached [Y]

Type “Y” and press ENTER to install the selected packages.

Installing:
 zimbra-core
 zimbra-ldap
 zimbra-logger
 zimbra-mta
 zimbra-dnscache
 zimbra-snmp
 zimbra-store
 zimbra-apache
 zimbra-spell
 zimbra-memcached
 zimbra-proxy

The system will be modified. Continue? [N] Y ##Type Y to install the selected packages

The installer will start to download and install the packages .

After few minutes, the Zimbra main menu will appear.

 Main menu

 1) Common Configuration: 
 2) zimbra-ldap: Enabled 
 3) zimbra-logger: Enabled 
 4) zimbra-mta: Enabled 
 5) zimbra-dnscache: Enabled 
 6) zimbra-snmp: Enabled 
 7) zimbra-store: Enabled 
  +Create Admin User: yes 
  +Admin user to create: admin@zimbra.ostechnix.lan 
  ******* +Admin Password UNSET 
  +Anti-virus quarantine user: virus-quarantine.mz4gvqg5@zimbra.ostechnix.lan
  +Enable automated spam training: yes 
  +Spam training user: spam.xc6cq3n8fv@zimbra.ostechnix.lan
  +Non-spam(Ham) training user: ham.3gmvpkc8w@zimbra.ostechnix.lan
  +SMTP host: zimbra.ostechnix.lan 
  +Web server HTTP port: 8080 
  +Web server HTTPS port: 8443 
  +Web server mode: https 
  +IMAP server port: 7143 
  +IMAP server SSL port: 7993 
  +POP server port: 7110 
  +POP server SSL port: 7995 
  +Use spell check server: yes 
  +Spell server URL: http://zimbra.ostechnix.lan:7780/aspell.php
  +Enable version update checks: TRUE 
  +Enable version update notifications: TRUE 
  +Version update notification email: admin@zimbra.ostechnix.lan 
  +Version update source email: admin@zimbra.ostechnix.lan 
  +Install mailstore (service webapp): yes 
  +Install UI (zimbra,zimbraAdmin webapps): yes

 8) zimbra-spell: Enabled 
 9) zimbra-proxy: Enabled 
 10) Default Class of Service Configuration: 
 s) Save config to file 
 x) Expand menu 
 q) Quit

Address unconfigured (**) items (? - help)

As you can see in the above output, It is obvious that I didn’t set password for the Zimbra admin account. So let us configure the unconfigured items. In this case, the unconfigured item (Admin password) is available under 7thsection, i.e under Zimbra Store section. So just type number 7 to configure this item.

Address unconfigured (**) items  (? - help) 7

A sub-menu will appear which shows the unconfigured item. As you see here, the unconfigured item no is 4. So, let us 4 to address this item.

Store configuration

 1) Status: Enabled 
 2) Create Admin User: yes 
 3) Admin user to create: admin@zimbra.ostechnix.lan 
** 4) Admin Password UNSET 
 5) Anti-virus quarantine user: virus-quarantine.mz4gvqg5@zimbra.ostechnix.lan
 6) Enable automated spam training: yes 
 7) Spam training user: spam.xc6cq3n8fv@zimbra.ostechnix.lan
 8) Non-spam(Ham) training user: ham.3gmvpkc8w@zimbra.ostechnix.lan
 9) SMTP host: zimbra.ostechnix.lan 
 10) Web server HTTP port: 8080 
 11) Web server HTTPS port: 8443 
 12) Web server mode: https 
 13) IMAP server port: 7143 
 14) IMAP server SSL port: 7993 
 15) POP server port: 7110 
 16) POP server SSL port: 7995 
 17) Use spell check server: yes 
 18) Spell server URL: http://zimbra.ostechnix.lan:7780/aspell.php
 19) Enable version update checks: TRUE 
 20) Enable version update notifications: TRUE 
 21) Version update notification email: admin@zimbra.ostechnix.lan 
 22) Version update source email: admin@zimbra.ostechnix.lan 
 23) Install mailstore (service webapp): yes 
 24) Install UI (zimbra,zimbraAdmin webapps): yes

 Select, or 'r' for previous menu [r] 4

Next, enter a password to the Zimbra admin account. Make sure the password is very strong.

Set password for the admin user. Use any strong password. Press enter to update the password.

Password for admin@zimbra.ostechnix.lan (min 6 characters): [vduf1n6p]

Then, type “r” to return back to main menu.

Select, or 'r' for previous menu [r] r

The unconfigured item is addressed and configured now.

Type a to apply the changes, and press ENTER to save the configuration file. Finally, type yes to continue and finish the installation.

*** CONFIGURATION COMPLETE - press 'a' to apply
Select from menu, or press 'a' to apply config (? - help) a ##Type 'a' and press ENTER
Save configuration data to a file? [Yes] ## Press ENTER 
Save config in file: [/opt/zimbra/config.15814] 
Saving config in /opt/zimbra/config.15814...done.
The system will be modified - continue? [No] yes ##Type yes and press ENTER.

Congratulations!

At this stage, you will have a working Zimbra collaboration suite in your Ubuntu server.

Log in to Zimbra Admin dashboard

Open your web browser and the URL: https://IP-Address:7071/ or https://domain-name:7071

Enter the user name and password. The default username is admin, and the password is the one that you created earlier while installing Zimbra.

Here it is how Zimbra admin dashboard looks like.

From here, you can do all kind of administration tasks, such as creating, editing and deleting users, domains, monitoring the zimbra server, managing Email accounts, and so on.

Creating new domain

Let us create a new domain. To do so, click on the Configure -> Domain button on the left menu bar. The list of available domains, including the default domain, will be found in this section.

To create a new domain, just click on the gear button on the top right side and click New.

Fill up the domain details and click Finish.

Creating new users

Click Manage button on the left menu bar. Then, click on the gear button on the top right corner and select New.

In the next screen, Enter the user details, such as first name, last name, and click Finish.

Similarly, you can create as many users as you want. Also, you can edit the user details, or delete them from here.

Log in to Zimbra Web client

Zimbra web client is the user’s personal mailbox where users can send, receive, delete mails, organize taks, manage their calendars etc.

To access, the Zimbra web console, just type https://IP-address or https://domain-name in the address bar.

The following screen should appear. Enter the user name and its password that we created earlier from the Admin console.

Here it is how each user’s mailbox looks like.

From here, the user can send, receive mails to the other users.

Remove Zimbra Collaboration Suite

Not happy with ZCS? I hope you will like it. In case you don’t want to use ZCS remove it from your Ubuntu server as shown below.

Go the Zimbra directory:

cd zcs-*

Enter the following command to completely remove it:

sudo ./install.sh -u

Finally, delete Zimbra directory:

cd ..

sudo rm -rf zcs-*

That’s all for now guys. ZCS is one of the cool and worthy collaboration platform ever I have I tested. ZCS installation, configuration, and usage is absolutely easy. Anyone can easily install it with little Linux knowledge. If you ever wanted to setup a messaging and collaboration platform for your office, give ZCS a try. You will find it worth.

Further reading:

• Zimbra Documentation
• Zimbra blog