TetraWiki - User contributions [en]

Punjab samba architectural change

2014-02-19T10:45:11Z

Abhinav:

[[category:Punjab's IFMS-IWDMS Project]]

== Samba Cluster for Punjab's IFMS-IWDMS project ==

Abhinav Sharma
Tetra Information Services

==Introduction==

The client wanted a Domain Controller, with a centralized authentication mechanism. To ensure this,
Samba 3.5 was installed with 389-Directory server at the backend.

This document has been divided into two parts, one detailing the installation of the Samba ;
and the other showing the steps taken to integrate it with the ldap server,
389-DS and configuring it as a Primary Domain Controller (PDC).

==Prerequisites:==

1) Installation of RHEL 6.3
2) yum must be configured to ensure Samba and other dependencies can be downloaded
3) 389-DS must already be setup prior to this installation

==Servers==
Two servers have been set up as follows:
pbifmsntp1.pbifmsiwdms.pjb - 192.168.10.81
pbifmsntp2.pbifmsiwdms.pjb - 192.168.10.82

Active node: pbifmsntp1.pbifmsiwdms.pjb
Standby node: pbifmsntp2.pbifmsiwdms.pjb
Mounted HDD: /dev/mapper/csmb_vg-csmb_lv ;

==Required Packages==

• samba
• samba-common
• samba-winbind-clients

==Configuration Of LAM:==

vim /var/lib/ldap-account-manager/config/admin.conf

# LDAP Account Manager configuration
#
# Please do not modify this file manually. The configuration can be done completely by the LAM GUI.
#
###################################################################################################

# server address (e.g. ldap://localhost:389 or ldaps://localhost:636)
ServerURL: ldap://192.168.10.98:389

# list of users who are allowed to use LDAP Account Manager
# names have to be seperated by semicolons
# e.g. admins: cn=admin,dc=yourdomain,dc=org;cn=root,dc=yourdomain,dc=org
Admins: cn=Directory manager

# password to change these preferences via webfrontend (default: lam)
Passwd: {SSHA}cjKUoXZejBFB1BWzv7htxcVfKeg= P/mJQQ==

# suffix of tree view
# e.g. dc=yourdomain,dc=org
treesuffix: dc=pbifmsiwdms,dc=pjb

# default language (a line from config/language)
defaultLanguage: en_GB.utf8:UTF-8:English (Great Britain)

# Path to external Script
scriptPath:

# Server of external Script
scriptServer:

# Access rights for home directories
scriptRights: 750

# Number of minutes LAM caches LDAP searches.
cachetimeout: 5

# LDAP search limit.
searchLimit: 0

# Module settings

modules: posixAccount_minUID: 10000
modules: posixAccount_maxUID: 30000
modules: posixAccount_minMachine: 50000
modules: posixAccount_maxMachine: 60000
modules: posixGroup_minGID: 10000
modules: posixGroup_maxGID: 20000
modules: posixGroup_pwdHash: SSHA
modules: posixAccount_pwdHash: SSHA

# List of active account types.
activeTypes: user,group,host,smbDomain

types: suffix_user: ou=People,dc=pbifmsiwdms,dc=pjb
types: attr_user: #uid;#givenName;#sn;#uidNumber;#gidNumber
types: modules_user: inetOrgPerson,posixAccount,shadowAccount,sambaSamAccount

types: suffix_group: ou=Groups,dc=pbifmsiwdms,dc=pjb
types: attr_group: #cn;#gidNumber;#memberUID;#description
types: modules_group: posixGroup,sambaGroupMapping

types: suffix_host: ou=computers,dc=pbifmsiwdms,dc=pjb
types: attr_host: #cn;#description;#uidNumber;#gidNumber
types: modules_host: account,posixAccount,sambaSamAccount

types: suffix_smbDomain: dc=pbifmsiwdms,dc=pjb
types: attr_smbDomain: sambaDomainName:Domain name;sambaSID:Domain SID
types: modules_smbDomain: sambaDomain

# Password mail subject
lamProMailSubject: Your password was reset

# Password mail text
lamProMailText: Dear @@givenName@@ @@sn@@,+::++::+your password was reset to:
@@newPassword@@+::++::++::+Best regards+::++::+deskside support+::+

# enable TLS encryption
useTLS: no

# Access level for this profile.
accessLevel: 100

# Login method.
loginMethod: list

# Search suffix for LAM login.
loginSearchSuffix: dc=yourdomain,dc=org

# Search filter for LAM login.
loginSearchFilter: uid=%USER%

# Bind DN for login search.
loginSearchDN:

# Bind password for login search.
loginSearchPassword: asd1234f

# HTTP authentication for LAM login.
httpAuthentication: false

# Password mail from
lamProMailFrom:

# Password mail reply-to
lamProMailReplyTo:

# Password mail is HTML
lamProMailIsHTML: false
modules: sambaSamAccount_timeZone: 0
modules: sambaSamAccount_lmHash: yes
modules: sambaSamAccount_hideHomeDrive: false
modules: sambaSamAccount_hideHomePath: false
modules: sambaSamAccount_hideProfilePath: false
modules: sambaSamAccount_hideLogonScript: false
modules: sambaSamAccount_hideWorkstations: false
modules: sambaSamAccount_hideLogonHours: false
modules: sambaSamAccount_hideTerminalServer: false
modules: posixAccount_primaryGroupAsSecondary: false
modules: inetOrgPerson_hideDescription: false
modules: inetOrgPerson_hideStreet: false
modules: inetOrgPerson_hidePostOfficeBox: false
modules: inetOrgPerson_hidePostalCode: false
modules: inetOrgPerson_hideLocation: false
modules: inetOrgPerson_hideState: false
modules: inetOrgPerson_hidePostalAddress: false
modules: inetOrgPerson_hideRegisteredAddress: false
modules: inetOrgPerson_hideOfficeName: false
modules: inetOrgPerson_hideRoomNumber: false
modules: inetOrgPerson_hideTelephoneNumber: false
modules: inetOrgPerson_hideHomeTelephoneNumber: false
modules: inetOrgPerson_hideMobileNumber: false
modules: inetOrgPerson_hideFaxNumber: false
modules: inetOrgPerson_hideEMailAddress: false
modules: inetOrgPerson_hideJobTitle: false
modules: inetOrgPerson_hideCarLicense: false
modules: inetOrgPerson_hideEmployeeType: false
modules: inetOrgPerson_hideBusinessCategory: false
modules: inetOrgPerson_hideDepartments: false
modules: inetOrgPerson_hideManager: false
modules: inetOrgPerson_hideO: false
modules: inetOrgPerson_hideEmployeeNumber: false
modules: inetOrgPerson_hideInitials: false
modules: inetOrgPerson_hideLabeledURI: false
tools: tool_hide_toolPDFEditor: false
tools: tool_hide_toolProfileEditor: false
tools: tool_hide_toolFileUpload: false
tools: tool_hide_toolSchemaBrowser: false
tools: tool_hide_toolServerInformation: false
tools: tool_hide_toolOUEditor: false
tools: tool_hide_toolTests: false
==PAM Configuration==

Chack if nss_ldap is installed with:

# rpm -qa|grep -i nss-ldap

otherwise:

# yum install nss-pam-ldapd

On both the samba nodes, run this:

authconfig --enableldap --enableldapauth --disablenis \
--enablecache –ldapserver=ldap1.pbifmsiwdms.pjb\
--ldapbasedn=dc=pbifmsiwdms,dc=pjb --updateall

Then ensure ldap.conf has the following settings:
URI ldap://ldap1.pbifmsiwdms.pjb/ ldap://ldap2.pbifmsiwdms.pjb/
TLS_CACERTDIR /etc/openldap/cacerts
TLS_REQCERT allow
TLS_CACERT /etc/openldap/cacerts/cacert.asc
BASE dc=pbifmsiwdms,dc=pjb
HOST pbifmsntp1.pbifmsiwdms.pjb
binddn "cn=Directory manager"
bindpw asd1234f
rootbinddn "cn=Directory manager"
port 389
bind_policy soft
nss_reconnect_tries 2
nss_base_passwd ou=People,dc=pbifmsiwdms,dc=pjb?one
nss_base_passwd ou=Computers,dc=pbifmsiwdms,dc=pjb?one
nss_base_shadow ou=People,dc=pbifmsiwdms,dc=pjb?one
nss_base_group ou=Groups,dc=pbifmsiwdms,dc=pjb?one

Without configuring ldap.conf, samba will not search posix accounts into ldap. Also, ensure that DNS has been setup.
Architecture Diagram

==Samba Configuration:==

[global]
workgroup = PUNJABGOVT
netbios name= PUNJABGOVT1
security = user
passdb backend = ldapsam:ldap://ldap1.pbifmsiwdms.pjb/
hosts allow = 127.0.0.1 192.168.10.0/24 192.168.20.0/24 192.168.70.0/24 10.10.20.0/24 10.10.22.0/24 172.22.0.0/16
smb ports = 139
ldap admin dn = cn=Directory Manager
ldap suffix = dc=pbifmsiwdms,dc=pjb
ldap user suffix = ou=People
ldap machine suffix = ou=Computers
ldap group suffix = ou=Groups
lanman auth = yes
client lanman auth = yes
log file = /var/log/samba/%m.log
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
#obey pam restrictions = no
ldap passwd sync = yes
os level = 65
domain logons = yes
domain master = yes
local master = yes
preferred master = yes
ldap ssl= off
wins support = yes
wins proxy = yes
logon path = \\%L\profiles\%U
logon home = \\%L\%U

logon drive = H:
map to guest = bad user
logon script = logon.cmd
template shell = /bin/false
winbind use default domain = no
map to guest = bad user
map untrusted to domain = Yes
enable privileges = yes
lm announce = yes
pam password change = yes
passwd program = /usr/sbin/smbldap-passwd %u

log level = 3
max log size = 1000
syslog only = no
syslog = 3

name resolve order = wins lmhosts hosts bcast
username map = /etc/samba/smbusers
add user script = /usr/sbin/smbldap-useradd -a %u
add machine script = /usr/sbin/smbldap-useradd -w %u
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
set primary group script = /usr/sbin/smbldap-usermod -g '%g' '%u'
delete user from group script = /usr/sbin/smbldap-groupmod -x '%u' '%g'
admin users = root
winbind enum groups = No
winbind trusted domains only = yes

[netlogon]
path = /mnt/gfs2/samba/netlogon
read only = yes
browsable = no
guest ok = yes

[profiles]
path = /mnt/gfs2/samba/profiles
read only = no
create mask = 0600
directory mask = 0700

#[profiles.V2]
#copy = profiles
#browseable = no

[homes]
browsable = no
writable = yes
path = /mnt/gfs2/share/%u

[csmb]
comment = Samba
public = yes
path = /mnt/gfs2/share
writeable = yes
ea support = yes

[nitrobit]
path = /mnt/gfs2/samba/nitrobit
read only = no
public = yes
browsable = yes
writable = yes
guest ok = yes

Create appropriate directories/permissions for the Samba shares defined in your configuration :

# mkdir -p /mnt/gfs2/samba
# mkdir /mnt/gfs2/samba/{netlogon,profiles}
# chown root:root -R /mnt/gfs2/samba
# chmod 0755 /mnt/gfs2/samba/netlogon
# chmod 1755 /mnt/gfs2/samba/profiles
# mkdir -p /mnt/gfs2/nitrobit

Create a password for the ldap admin dn (the Directory Manager's Password) in Samba's secret file:

# smbpasswd -w <ldap-admin-password>
Setting stored passnword for "cn=Directory Manager" in secrets.tdb

net getlocalsid
SID for domain PUNJABGOVT is: S-1-5-21-4070117540-217532476-2757550252

If sid is not coming then you can Set manually by
# Net setlocalsid S-1-5-21-4070117540-217532476-2757550252

Then Ckeck Groups of ldpa server is coming or not by

# net groupmap list
PUNJABGOVT\Domain Users (S-1-5-21-4070117540-217532476-2757550252-513) -> Domain Users
Domain Guests (S-1-5-21-4070117540-217532476-2757550252-514) -> Domain Guests
Domain Computers (S-1-5-21-4070117540-217532476-2757550252-515) -> Domain Computers
Administrators (S-1-5-32-544) -> Administrators
Account Operators (S-1-5-32-548) -> Account Operators
Print Operators (S-1-5-32-550) -> Print Operators
Backup Operators (S-1-5-32-551) -> Backup Operators
Replicators (S-1-5-32-552) -> Replicators
Power Users (S-1-5-21-4070117540-217532476-2757550252-2912) -> Power Users
PUNJABGOVT\Domain Admins (S-1-5-21-4070117540-217532476-2757550252-512) -> Domain Admins
PUNJABGOVT\TCSDC (S-1-5-21-4070117540-217532476-2757550252-39001) -> TCSDC
PUNJAB-USERS (S-1-5-21-4070117540-217532476-2757550252-39003) -> PUNJAB-USERS
Datacenter Administrator (S-1-5-21-4070117540-217532476-2757550252-39005) -> data_admin

==Samba troubleshooting==

If the client computers get the error that they cannot contact the Domain Controller specified,
then check if nmb is running. If not, start it.
# service nmb start

To check if an account can connect:
# smbclient -L samba.pbifmsiwdms.pjb -U <username>

To check if a user is read from the ldap server:
# getent passwd <username>
For example:
# getent passwd admin
admin:*:11071:5122:System User:/home/admin:/bin/bash

This will show the user's POSIX details, as stored on the 389-DS server.

It can be similarly used for groups, as follows:
# getent group 'Domain Admins'
Domain Admins:*:5122:admin

'net' commands:

To see the group mappings:
# net groupmap list

To add a group:
# net groupmap add rid=513 \
ntgroup='PUNJABGOVT\Domain Users' \
unixgroup='Domain Users'

To see a group's members:
# net rpc group members "Domain Admins”

To see a members's groups:
# net rpc user info admin

To get the SID:
# net getdomainsid

If Samba root/administrator users are blocked
# pdbedit –c=’[]’ –-user=root
# pdbedit –c=’[U]’ –-user=root

==Test Join==

# Net rpc testjoin
To join server in domain by admin user
# net join –U admin

==Manual Swich Over:==

We have Done the manual Swich Over instead of Cluster Because any updation and upgradation
of packages and operation System effect Cluster directly or indirectly. Due to which whole architecture
get disturbe. So after Analysis and discussion We proceed with Manual swich over.

1. Node1:
# /etc/init.d/network restart
#/etc/init.d/smb stop
#/etc/init.d/nmb stop

Node2:

# ifconfig eth0:0 192.168.10.93 netmask 255.255.255.0
# /etc/init.d/smb start;
#/etc/init.d/nmb start

Punjab samba architectural change

2014-02-19T10:44:11Z

Abhinav: Created page with " == Samba Cluster for Punjab's IFMS-IWDMS project == Abhinav Sharma Tetra Information Services ==Introduction== The client wanted a Domain Controller, wit..."

== Samba Cluster for Punjab's IFMS-IWDMS project ==

Abhinav Sharma
Tetra Information Services

==Introduction==

The client wanted a Domain Controller, with a centralized authentication mechanism. To ensure this,
Samba 3.5 was installed with 389-Directory server at the backend.

This document has been divided into two parts, one detailing the installation of the Samba ;
and the other showing the steps taken to integrate it with the ldap server,
389-DS and configuring it as a Primary Domain Controller (PDC).

==Prerequisites:==

1) Installation of RHEL 6.3
2) yum must be configured to ensure Samba and other dependencies can be downloaded
3) 389-DS must already be setup prior to this installation

==Servers==
Two servers have been set up as follows:
pbifmsntp1.pbifmsiwdms.pjb - 192.168.10.81
pbifmsntp2.pbifmsiwdms.pjb - 192.168.10.82

Active node: pbifmsntp1.pbifmsiwdms.pjb
Standby node: pbifmsntp2.pbifmsiwdms.pjb
Mounted HDD: /dev/mapper/csmb_vg-csmb_lv ;

==Required Packages==

• samba
• samba-common
• samba-winbind-clients

==Configuration Of LAM:==

vim /var/lib/ldap-account-manager/config/admin.conf

# LDAP Account Manager configuration
#
# Please do not modify this file manually. The configuration can be done completely by the LAM GUI.
#
###################################################################################################

# server address (e.g. ldap://localhost:389 or ldaps://localhost:636)
ServerURL: ldap://192.168.10.98:389

# list of users who are allowed to use LDAP Account Manager
# names have to be seperated by semicolons
# e.g. admins: cn=admin,dc=yourdomain,dc=org;cn=root,dc=yourdomain,dc=org
Admins: cn=Directory manager

# password to change these preferences via webfrontend (default: lam)
Passwd: {SSHA}cjKUoXZejBFB1BWzv7htxcVfKeg= P/mJQQ==

# suffix of tree view
# e.g. dc=yourdomain,dc=org
treesuffix: dc=pbifmsiwdms,dc=pjb

# default language (a line from config/language)
defaultLanguage: en_GB.utf8:UTF-8:English (Great Britain)

# Path to external Script
scriptPath:

# Server of external Script
scriptServer:

# Access rights for home directories
scriptRights: 750

# Number of minutes LAM caches LDAP searches.
cachetimeout: 5

# LDAP search limit.
searchLimit: 0

# Module settings

modules: posixAccount_minUID: 10000
modules: posixAccount_maxUID: 30000
modules: posixAccount_minMachine: 50000
modules: posixAccount_maxMachine: 60000
modules: posixGroup_minGID: 10000
modules: posixGroup_maxGID: 20000
modules: posixGroup_pwdHash: SSHA
modules: posixAccount_pwdHash: SSHA

# List of active account types.
activeTypes: user,group,host,smbDomain

types: suffix_user: ou=People,dc=pbifmsiwdms,dc=pjb
types: attr_user: #uid;#givenName;#sn;#uidNumber;#gidNumber
types: modules_user: inetOrgPerson,posixAccount,shadowAccount,sambaSamAccount

types: suffix_group: ou=Groups,dc=pbifmsiwdms,dc=pjb
types: attr_group: #cn;#gidNumber;#memberUID;#description
types: modules_group: posixGroup,sambaGroupMapping

types: suffix_host: ou=computers,dc=pbifmsiwdms,dc=pjb
types: attr_host: #cn;#description;#uidNumber;#gidNumber
types: modules_host: account,posixAccount,sambaSamAccount

types: suffix_smbDomain: dc=pbifmsiwdms,dc=pjb
types: attr_smbDomain: sambaDomainName:Domain name;sambaSID:Domain SID
types: modules_smbDomain: sambaDomain

# Password mail subject
lamProMailSubject: Your password was reset

# Password mail text
lamProMailText: Dear @@givenName@@ @@sn@@,+::++::+your password was reset to:
@@newPassword@@+::++::++::+Best regards+::++::+deskside support+::+

# enable TLS encryption
useTLS: no

# Access level for this profile.
accessLevel: 100

# Login method.
loginMethod: list

# Search suffix for LAM login.
loginSearchSuffix: dc=yourdomain,dc=org

# Search filter for LAM login.
loginSearchFilter: uid=%USER%

# Bind DN for login search.
loginSearchDN:

# Bind password for login search.
loginSearchPassword: asd1234f

# HTTP authentication for LAM login.
httpAuthentication: false

# Password mail from
lamProMailFrom:

# Password mail reply-to
lamProMailReplyTo:

# Password mail is HTML
lamProMailIsHTML: false
modules: sambaSamAccount_timeZone: 0
modules: sambaSamAccount_lmHash: yes
modules: sambaSamAccount_hideHomeDrive: false
modules: sambaSamAccount_hideHomePath: false
modules: sambaSamAccount_hideProfilePath: false
modules: sambaSamAccount_hideLogonScript: false
modules: sambaSamAccount_hideWorkstations: false
modules: sambaSamAccount_hideLogonHours: false
modules: sambaSamAccount_hideTerminalServer: false
modules: posixAccount_primaryGroupAsSecondary: false
modules: inetOrgPerson_hideDescription: false
modules: inetOrgPerson_hideStreet: false
modules: inetOrgPerson_hidePostOfficeBox: false
modules: inetOrgPerson_hidePostalCode: false
modules: inetOrgPerson_hideLocation: false
modules: inetOrgPerson_hideState: false
modules: inetOrgPerson_hidePostalAddress: false
modules: inetOrgPerson_hideRegisteredAddress: false
modules: inetOrgPerson_hideOfficeName: false
modules: inetOrgPerson_hideRoomNumber: false
modules: inetOrgPerson_hideTelephoneNumber: false
modules: inetOrgPerson_hideHomeTelephoneNumber: false
modules: inetOrgPerson_hideMobileNumber: false
modules: inetOrgPerson_hideFaxNumber: false
modules: inetOrgPerson_hideEMailAddress: false
modules: inetOrgPerson_hideJobTitle: false
modules: inetOrgPerson_hideCarLicense: false
modules: inetOrgPerson_hideEmployeeType: false
modules: inetOrgPerson_hideBusinessCategory: false
modules: inetOrgPerson_hideDepartments: false
modules: inetOrgPerson_hideManager: false
modules: inetOrgPerson_hideO: false
modules: inetOrgPerson_hideEmployeeNumber: false
modules: inetOrgPerson_hideInitials: false
modules: inetOrgPerson_hideLabeledURI: false
tools: tool_hide_toolPDFEditor: false
tools: tool_hide_toolProfileEditor: false
tools: tool_hide_toolFileUpload: false
tools: tool_hide_toolSchemaBrowser: false
tools: tool_hide_toolServerInformation: false
tools: tool_hide_toolOUEditor: false
tools: tool_hide_toolTests: false
==PAM Configuration==

Chack if nss_ldap is installed with:

# rpm -qa|grep -i nss-ldap

otherwise:

# yum install nss-pam-ldapd

On both the samba nodes, run this:

authconfig --enableldap --enableldapauth --disablenis \
--enablecache –ldapserver=ldap1.pbifmsiwdms.pjb\
--ldapbasedn=dc=pbifmsiwdms,dc=pjb --updateall

Then ensure ldap.conf has the following settings:
URI ldap://ldap1.pbifmsiwdms.pjb/ ldap://ldap2.pbifmsiwdms.pjb/
TLS_CACERTDIR /etc/openldap/cacerts
TLS_REQCERT allow
TLS_CACERT /etc/openldap/cacerts/cacert.asc
BASE dc=pbifmsiwdms,dc=pjb
HOST pbifmsntp1.pbifmsiwdms.pjb
binddn "cn=Directory manager"
bindpw asd1234f
rootbinddn "cn=Directory manager"
port 389
bind_policy soft
nss_reconnect_tries 2
nss_base_passwd ou=People,dc=pbifmsiwdms,dc=pjb?one
nss_base_passwd ou=Computers,dc=pbifmsiwdms,dc=pjb?one
nss_base_shadow ou=People,dc=pbifmsiwdms,dc=pjb?one
nss_base_group ou=Groups,dc=pbifmsiwdms,dc=pjb?one

Without configuring ldap.conf, samba will not search posix accounts into ldap. Also, ensure that DNS has been setup.
Architecture Diagram

==Samba Configuration:==

[global]
workgroup = PUNJABGOVT
netbios name= PUNJABGOVT1
security = user
passdb backend = ldapsam:ldap://ldap1.pbifmsiwdms.pjb/
hosts allow = 127.0.0.1 192.168.10.0/24 192.168.20.0/24 192.168.70.0/24 10.10.20.0/24 10.10.22.0/24 172.22.0.0/16
smb ports = 139
ldap admin dn = cn=Directory Manager
ldap suffix = dc=pbifmsiwdms,dc=pjb
ldap user suffix = ou=People
ldap machine suffix = ou=Computers
ldap group suffix = ou=Groups
lanman auth = yes
client lanman auth = yes
log file = /var/log/samba/%m.log
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
#obey pam restrictions = no
ldap passwd sync = yes
os level = 65
domain logons = yes
domain master = yes
local master = yes
preferred master = yes
ldap ssl= off
wins support = yes
wins proxy = yes
logon path = \\%L\profiles\%U
logon home = \\%L\%U

logon drive = H:
map to guest = bad user
logon script = logon.cmd
template shell = /bin/false
winbind use default domain = no
map to guest = bad user
map untrusted to domain = Yes
enable privileges = yes
lm announce = yes
pam password change = yes
passwd program = /usr/sbin/smbldap-passwd %u

log level = 3
max log size = 1000
syslog only = no
syslog = 3

name resolve order = wins lmhosts hosts bcast
username map = /etc/samba/smbusers
add user script = /usr/sbin/smbldap-useradd -a %u
add machine script = /usr/sbin/smbldap-useradd -w %u
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
set primary group script = /usr/sbin/smbldap-usermod -g '%g' '%u'
delete user from group script = /usr/sbin/smbldap-groupmod -x '%u' '%g'
admin users = root
winbind enum groups = No
winbind trusted domains only = yes

[netlogon]
path = /mnt/gfs2/samba/netlogon
read only = yes
browsable = no
guest ok = yes

[profiles]
path = /mnt/gfs2/samba/profiles
read only = no
create mask = 0600
directory mask = 0700

#[profiles.V2]
#copy = profiles
#browseable = no

[homes]
browsable = no
writable = yes
path = /mnt/gfs2/share/%u

[csmb]
comment = Samba
public = yes
path = /mnt/gfs2/share
writeable = yes
ea support = yes

[nitrobit]
path = /mnt/gfs2/samba/nitrobit
read only = no
public = yes
browsable = yes
writable = yes
guest ok = yes

Create appropriate directories/permissions for the Samba shares defined in your configuration :

# mkdir -p /mnt/gfs2/samba
# mkdir /mnt/gfs2/samba/{netlogon,profiles}
# chown root:root -R /mnt/gfs2/samba
# chmod 0755 /mnt/gfs2/samba/netlogon
# chmod 1755 /mnt/gfs2/samba/profiles
# mkdir -p /mnt/gfs2/nitrobit

Create a password for the ldap admin dn (the Directory Manager's Password) in Samba's secret file:

# smbpasswd -w <ldap-admin-password>
Setting stored passnword for "cn=Directory Manager" in secrets.tdb

net getlocalsid
SID for domain PUNJABGOVT is: S-1-5-21-4070117540-217532476-2757550252

If sid is not coming then you can Set manually by
# Net setlocalsid S-1-5-21-4070117540-217532476-2757550252

Then Ckeck Groups of ldpa server is coming or not by

# net groupmap list
PUNJABGOVT\Domain Users (S-1-5-21-4070117540-217532476-2757550252-513) -> Domain Users
Domain Guests (S-1-5-21-4070117540-217532476-2757550252-514) -> Domain Guests
Domain Computers (S-1-5-21-4070117540-217532476-2757550252-515) -> Domain Computers
Administrators (S-1-5-32-544) -> Administrators
Account Operators (S-1-5-32-548) -> Account Operators
Print Operators (S-1-5-32-550) -> Print Operators
Backup Operators (S-1-5-32-551) -> Backup Operators
Replicators (S-1-5-32-552) -> Replicators
Power Users (S-1-5-21-4070117540-217532476-2757550252-2912) -> Power Users
PUNJABGOVT\Domain Admins (S-1-5-21-4070117540-217532476-2757550252-512) -> Domain Admins
PUNJABGOVT\TCSDC (S-1-5-21-4070117540-217532476-2757550252-39001) -> TCSDC
PUNJAB-USERS (S-1-5-21-4070117540-217532476-2757550252-39003) -> PUNJAB-USERS
Datacenter Administrator (S-1-5-21-4070117540-217532476-2757550252-39005) -> data_admin

==Samba troubleshooting==

If the client computers get the error that they cannot contact the Domain Controller specified,
then check if nmb is running. If not, start it.
# service nmb start

To check if an account can connect:
# smbclient -L samba.pbifmsiwdms.pjb -U <username>

To check if a user is read from the ldap server:
# getent passwd <username>
For example:
# getent passwd admin
admin:*:11071:5122:System User:/home/admin:/bin/bash

This will show the user's POSIX details, as stored on the 389-DS server.

It can be similarly used for groups, as follows:
# getent group 'Domain Admins'
Domain Admins:*:5122:admin

'net' commands:

To see the group mappings:
# net groupmap list

To add a group:
# net groupmap add rid=513 \
ntgroup='PUNJABGOVT\Domain Users' \
unixgroup='Domain Users'

To see a group's members:
# net rpc group members "Domain Admins”

To see a members's groups:
# net rpc user info admin

To get the SID:
# net getdomainsid

If Samba root/administrator users are blocked
# pdbedit –c=’[]’ –-user=root
# pdbedit –c=’[U]’ –-user=root

==Test Join==

# Net rpc testjoin
To join server in domain by admin user
# net join –U admin

==Manual Swich Over:==

We have Done the manual Swich Over instead of Cluster Because any updation and upgradation
of packages and operation System effect Cluster directly or indirectly. Due to which whole architecture
get disturbe. So after Analysis and discussion We proceed with Manual swich over.

1. Node1:
# /etc/init.d/network restart
#/etc/init.d/smb stop
#/etc/init.d/nmb stop

Node2:

# ifconfig eth0:0 192.168.10.93 netmask 255.255.255.0
# /etc/init.d/smb start;
#/etc/init.d/nmb start

Zimbra Archive Server

2013-11-22T12:14:49Z

Abhinav: /* Introduction */

[[Category:Zimbra]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.

In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.

==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist

The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/postfix/conf/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/postfix/conf/archivelist
$ postfix reload
==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
#
#
#
#
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
#
#
#
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17

# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist

# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv

# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST

# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra

# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST

# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"

if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist

# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp

# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'

# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra

else
exit
fi

Made By
Abhinav Sharma

Zimbra Archive Server

2013-11-22T11:16:49Z

Abhinav: /* Postfix */

[[Category:Zimbra]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.
In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.
==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist

The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/postfix/conf/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/postfix/conf/archivelist
$ postfix reload
==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
#
#
#
#
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
#
#
#
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17

# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist

# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv

# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST

# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra

# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST

# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"

if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist

# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp

# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'

# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra

else
exit
fi

Made By
Abhinav Sharma

Zimbra Archive Server

2013-11-22T11:15:23Z

Abhinav: Created page with "Category:Zimbra ==Simple archival server for Zimbra OSE== ==Introduction== This document shows how to create a simple arch..."

[[Category:Zimbra]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.
In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.
==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf
sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/postfix/conf/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/postfix/conf/archivelist
$ postfix reload
==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
#
#
#
#
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
#
#
#
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17

# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist

# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv

# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST

# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra

# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST

# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"

if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist

# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp

# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'

# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra

else
exit
fi

Made By
Abhinav Sharma

Muthoot Cluster

2013-11-19T11:46:36Z

Abhinav:

--[[User:Abhinav|Abhinav]] 15:20, 4 July 2013 (IST)[[category:Muthoot group]]
'''Cluster Of Muthoot'''
== Postgresql Cluster ==

==IP Details:==

1. Live Server ip: 192.168.1.133
2. Secondary Server ip: 192.168.1.132
3. Cluster Ip: 192.168.1.140
4. Mgmt port ip: 192.168.1.126 (liveserver)
5. Mgmt port ip: 192.168.1.127( Secondary)
6. Ip for heartbeat : 10.0.0.1 (node1)
7. Node 2: 10.0.0.2

==Configuration:==

133# vim /etc/hosts
192.168.1.133 liveserver.muthootco.com liveserver
192.168.1.132 liveserver1.muthootco.com liveserver1
10.0.0.1 node1.muthootco.com node1
10.0.0.2 node2.muthootco.com node2
192.168.1.127 node2-imm.muthootco.com node2-imm
192.168.1.126 node1-imm.muthootco.com node1-imm

Give 10.0.0.1 ip in eth1 in liveserver And 10.0.0.2 ip in eth1 in secondary server.

Note : Give Ip to Management port Steps are follow:

Step1: On boot Time go to bios
Step2: System Settings-->Integrated Management Module --> Network-->Give Ip

133# yum install cman rgmanager ricci luci

Note: luci package is only on one system

Then open web interface :
https://192.168.1.133:8084
User: Same as system root details
Then Go to Service Group Tab
Then Press add button
Service Name : Cluster-Service
Failover Domain: None
Recovery Policy : relocate
IP Address: 192.168.1.140 \\ don’t give netmask for this IP

133# yum remove libvirt \\ Due to this package node can’t be add it’s give error

==Then Go To Node Tab==

Add-->
Node Name: node1
Password: same as system
Port: 11111
Same Do for node 2

==Then Go To Fence Device Tab:==
Press Add
Fence Type: IPMI LAN
Name : node2-imm
Ip add- 192.168.1.127
Login: USERID
Password:xyz
Authentication Type: None
Privileges Level: default

==Then Again Press add==
Configure same
Name – node1-imm
Ip – 192.168.1.126
Apply

==Then Go To node TAB==

Click on node 1--> Add fence method-->Fence_Method-->then Add fence instance -->node1-imm(IPMI LAN)-->Submit

Same do with node 2 configuration and add node2-imm

==Then Go To Service Group TAB==

Failover Domain: Failover
Apply

'''Note''': Make two LVM Volumes
Vol Name: DB , Logical Vol : test
Vol Name: LogsSpace , Logical Vol : LogSystem

Then Go To Resources Tab:
Add--> HA LVM-->
Name : HA
VG Name : DB
Add-->Filesystem-->
Name: DB File
File System Type: ext4
Mount point: /home/pgsql/data/base \\path must be exist
Device Name: /dev/mapper/DB-test
Force Unmount : check mark
Apply

==Add -->HA LVM==
Name : Logs
Vol Grp Name: LogsSpace

==Add--> Filesystem==
Name: Logs_Details
File System Type: ext4
Mount point: /Logs
Device Name: /dev/mapper/LogsSpace-logSystem

Add-->script
Name: Sql-Script
Full Path to script File: /etc/init.d/postgresql
Apply

Muthoot Cluster

2013-11-19T11:45:57Z

Abhinav: /* Then Go To Node Tab */

--[[User:Abhinav|Abhinav]] 15:20, 4 July 2013 (IST)[[category:Muthoot group]]
'''Cluster Of Muthoot'''
== Postgresql Cluster ==

==IP Details:==

1. Live Server ip: 192.168.1.133
2. Secondary Server ip: 192.168.1.132
3. Cluster Ip: 192.168.1.140
4. Mgmt port ip: 192.168.1.126 (liveserver)
5. Mgmt port ip: 192.168.1.127( Secondary)
6. Ip for heartbeat : 10.0.0.1 (node1)
7. Node 2: 10.0.0.2

==Configuration:==

133# vim /etc/hosts
192.168.1.133 liveserver.muthootco.com liveserver
192.168.1.132 liveserver1.muthootco.com liveserver1
10.0.0.1 node1.muthootco.com node1
10.0.0.2 node2.muthootco.com node2
192.168.1.127 node2-imm.muthootco.com node2-imm
192.168.1.126 node1-imm.muthootco.com node1-imm

Give 10.0.0.1 ip in eth1 in liveserver And 10.0.0.2 ip in eth1 in secondary server.

Note : Give Ip to Management port Steps are follow:

Step1: On boot Time go to bios
Step2: System Settings-->Integrated Management Module --> Network-->Give Ip

133# yum install cman rgmanager ricci luci

Note: luci package is only on one system

Then open web interface :
https://192.168.1.133:8084
User: Same as system root details
Then Go to Service Group Tab
Then Press add button
Service Name : Cluster-Service
Failover Domain: None
Recovery Policy : relocate
IP Address: 192.168.1.140 \\ don’t give netmask for this IP

133# yum remove libvirt \\ Due to this package node can’t be add it’s give error

==Then Go To Node Tab==

Add-->
Node Name: node1
Password: same as system
Port: 11111
Same Do for node 2
==Then Go To Fence Device Tab:==
Press Add
Fence Type: IPMI LAN
Name : node2-imm
Ip add- 192.168.1.127
Login: USERID
Password:xyz
Authentication Type: None
Privileges Level: default

==Then Again Press add==
Configure same
Name – node1-imm
Ip – 192.168.1.126
Apply

==Then Go To node TAB==

Click on node 1--> Add fence method-->Fence_Method-->then Add fence instance -->node1-imm(IPMI LAN)-->Submit

Same do with node 2 configuration and add node2-imm

==Then Go To Service Group TAB==

Failover Domain: Failover
Apply

'''Note''': Make two LVM Volumes
Vol Name: DB , Logical Vol : test
Vol Name: LogsSpace , Logical Vol : LogSystem

Then Go To Resources Tab:
Add--> HA LVM-->
Name : HA
VG Name : DB
Add-->Filesystem-->
Name: DB File
File System Type: ext4
Mount point: /home/pgsql/data/base \\path must be exist
Device Name: /dev/mapper/DB-test
Force Unmount : check mark
Apply

==Add -->HA LVM==
Name : Logs
Vol Grp Name: LogsSpace

==Add--> Filesystem==
Name: Logs_Details
File System Type: ext4
Mount point: /Logs
Device Name: /dev/mapper/LogsSpace-logSystem

Add-->script
Name: Sql-Script
Full Path to script File: /etc/init.d/postgresql
Apply

Sender recipient restriction in zimbra

2013-11-19T05:18:58Z

Abhinav:

[[Category:Zimbra]]

Restrict Recipient In Zimbra

This will show how you can modify postfix to restrict who can send and receive to certain addresses in your domain

Steps

Create a 'permitted senders' list (as user zimbra) - This is your list of domains and/or users who can email your protected email addresses:

vi /opt/zimbra/postfix/conf/permitted_senders

localhost OK
rockmanindustries.com OK
zimbramail.rockmanindustries.com OK

Create a 'protected recipients' list (as user zimbra) - This is your list of email addresses that may only receive email from 'permitted senders'
vi /opt/zimbra/postfix/conf/protected_recipients
test-dist-list@rockmanindustries.com permitted_senders_list
protected-user@rockmanindustries.com permitted_senders_list

Create a simple bash script to create postfix DB files (as user zimbra):
vi /opt/zimbra/postfix/conf/update_protected_recipients
#!/bin/bash
echo "rebuild permitted_senders..."
postmap /opt/zimbra/postfix/conf/permitted_senders
echo "rebuild protected_recipients..."
postmap /opt/zimbra/postfix/conf/protected_recipients

Make new script executable,
chmod 755 /opt/zimbra/postfix/conf/update_protected_recipients

then run it...
/opt/zimbra/postfix/conf/update_protected_recipients

You should now see permitted_senders.db and protected_recipients.db in the directory

� Add necessary settings to /opt/zimbra/postfix/conf/main.cf
vi /opt/zimbra/postfix/conf/main.cf
[add these items to the file - note permitted_senders_list must match value in protected_recipients
permitted_senders_list = check_sender_access hash:/opt/zimbra/postfix/conf/permitted_senders, reject
smtpd_restriction_classes = permitted_senders_list

**Note this change to the main.cf won't survive upgrades. Be sure to save a copy of your main.cf file**

While in /opt/zimbra/postfix/conf/main.cf: You must also add the following snippet to smtpd_recipient_restrictions (first is preferred, otherwise anywhere before the last "permit", THE ORDER IN WHICH ITEMS APPEAR HERE IS IMPORTANT (if it appears after the "permit", mail will always be accepted for the restricted recipient):

smtpd_recipient_restrictions = check_recipient_access hash:/opt/zimbra/postfix/conf/protected_recipients, (rest of line here)

Now add your new restriction to the top of smtpd_recipient_restrictions.cf

vi /opt/zimbra/conf/zmconfigd/smtpd_recipient_restrictions.cf

[paste this into the first line of the file, above any other settings]

check_recipient_access hash:/opt/zimbra/postfix/conf/protected_recipients

Edit /opt/zimbra/conf/zmconfigd.cf and then remove the following line;

# POSTCONF smtpd_recipient_restrictions FILE postfix_recipient_restrictions.cf

postfix reload

Note: Test It on one user that only localdomain mails is deliver to user mailbox

� Restricting users to send mails to certain domains

Vi /opt/zimbra/conf/zmconfigd/smtpd_recipient_restrictions.cf

check_sender_access hash:/opt/zimbra/postfix/conf/restricted_senders

vi /opt/zimbra/conf/zmconfigd.cf

Find the section labeled SECTION mta and enter the following two lines directly below
POSTCONF smtpd_restriction_classes local_only , permitted_sender_list
POSTCONF local_only FILE postfix_check_recipient_access.cf

Create a file "/opt/zimbra/conf/postfix_check_recipient_access.cf"

vi /opt/zimbra/conf/postfix_check_recipient_access.cf

check_recipient_access hash:/opt/zimbra/postfix/conf/local_domains, reject

Create a file "/opt/zimbra/postfix/conf/restricted_senders" and list all the users, whom you want to restrict. Follow this syntax:

vi /opt/zimbra/postfix/conf/restricted_senders

user@rockmanindustries.com local_only

Create a file "/opt/zimbra/postfix/conf/local_domains" and list all the domains where "restricted users" allowed to sent mails. Please follow this syntax:
vi /opt/zimbra/postfix/conf/local_domains

rockmanindustries.com OK
otheralloweddomain.com OK

Run following commands:
postmap /opt/zimbra/postfix/conf/restricted_senders

postmap /opt/zimbra/postfix/conf/local_domains

vim /opt/zimbra/conf/zmconfigd/smtpd_sender_restrictions.cf
check_sender_access hash:/opt/zimbra/postfix/conf/restricted_senders

zmmtactl stop
zmmtactl start

�

Sender recipient restriction in zimbra

2013-11-19T05:11:26Z

Abhinav: Created page with "Category:Zimbra Restrict Recipient In Zimbra This will show how you can modify postfix to restrict who can send and receive to ce..."

Jboss Multi Instance

2013-10-07T11:30:30Z

Abhinav:

[[category:JBOSS Related‏‎]]

== To create new instance Of Jboss In Single Server ==

1:- create a new folder in jboss-6.0.0.Final/server/ .
Example /jboss-6.0.0.Final/server/franco here frenco is new folder

2:-copy all the files and folders of other /jboss-6.0.0.Final/server/default(server) in this new created folder Example copy all folders and
files in /jboss-6.0.0.Final/server/franco (Main server).

3:- Go /jboss-6.0.0.Final/server/franco/conf/bindingservice.beans/META-INF/ folder an open file bindings-jboss-beans.xml change
“<parameter>${jboss.service.binding.set:default}</parameter> ” with “ <parameter>${jboss.service.binding.set:ports-02}</parameter> ” and
for this change the port will be 8280.

4:-Go /usr/bin/jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF edit web.xml
change path of dbConfigFile.

Example <param-name>dbConfigFile</param-name>
<param-value>/usr/bin/jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF/Constants.props</param-value>

5:-Change respective setting for database in jboss-6.0.0.Final/server/franco/deploy /postgres-ds.xml

6:- Open jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF folder and edit Constant.prop update the ports of ejbproviderurl , providerurl and other relative details .
Example in case of franco we put ejbproviderurl=1299,providerurl=1299 in place of 1099.

7 :- Change the database detail in jboss-6.0.0.Final/server/franco/conf/login-config.xml

8:-To manual server start, go usr/bin/jboss-6.0.0.Final/bin/
type ./run.sh -c franco -b 0.0.0.0 to run franco server.

Jboss Multi Instance

2013-10-07T11:25:54Z

Abhinav: Created page with "category:JBOSS Related‏‎ == To create new instance Of Jboss In Single Server == 1:- create a new folder in jboss-6.0.0.Final/server/ . Example /jboss-6.0.0.F..."

[[category:JBOSS Related‏‎]]

== To create new instance Of Jboss In Single Server ==

1:- create a new folder in jboss-6.0.0.Final/server/ .
Example /jboss-6.0.0.Final/server/franco here frenco is new folder

2:-copy all the files and folders of other /jboss-6.0.0.Final/server/default(server) in this new created folder Example copy all folders and files in /jboss-6.0.0.Final/server/franco (Main server).
3:- Go /jboss-6.0.0.Final/server/franco/conf/bindingservice.beans/META-INF/ folder an open file bindings-jboss-beans.xml change
“<parameter>${jboss.service.binding.set:default}</parameter> ” with “ <parameter>${jboss.service.binding.set:ports-02}</parameter> ” for this change the port will be 8280.

4:-Go /usr/bin/jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF edit web.xml
change path of dbConfigFile.

Example <param-name>dbConfigFile</param-name>
<param-value>/usr/bin/jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF/Constants.props</param-value>

5:-Change respective setting for database in jboss-6.0.0.Final/server/franco/deploy /postgres-ds.xml

6:- Open jboss-6.0.0.Final/server/franco/deploy/sdnetWeb.war/WEB-INF folder and edit Constant.prop update the ports of ejbproviderurl , providerurl and other relative details .
Example in case of franco we put ejbproviderurl=1299,providerurl=1299 in place of 1099.

7 :- Change the database detail in jboss-6.0.0.Final/server/franco/conf/login-config.xml

8:-To manual server start, go usr/bin/jboss-6.0.0.Final/bin/
type ./run.sh -c franco -b 0.0.0.0 to run franco server.

Postgresql Backup via Barman backup at Muthoot group

2013-09-09T06:33:08Z

Abhinav: /* Restoration */

[[category:Tetra Clients]]
[[category:Installation]]
[[category:Muthoot group]]

== Backup Implemenation at Muthoot Group 's Live PostgreSql Server (RHEL 6) ==

==Environment==

1.Live PG server - 192.168.1.133

2.Backup Server - 192.168.1.132

==Software Used==

Barman Backup Software for PostgreSql - http://www.pgbarman.org/

Document Refered - http://docs.pgbarman.org/

==Installation process==

please install barman on backup server i.e 192.168.1.132
Download the Rpm pakages from Sourceforge
wget http://downloads.sourceforge.net/project/pgbarman/1.1.1/barman-1.1.1-1.rhel6.noarch.rpm
wget http://downloads.sourceforge.net/project/pgbarman/rhel6-deps/python-argh-0.15.0-1.rhel6.noarch.rpm

Satisfy it dependecies
yum install python-argh
yum install python-argparse
yum install python-psycopg2
Install the Rpms
rpm -Uvh python-argh-0.15.0-1.rhel6.noarch.rpm barman-1.1.1-1.rhel6.noarch.rpm

Build Password less setup

SSH Password less bi-direction setup for postgres ( 192.168.1.133 ) and barman( 192.168.1.132 ) user
You should be able to login on ssh from .133 with user postgres to .132 on barman user without password and Visa-Versa

Set the following in /etc/barman.conf

[barman]
; Main directory
barman_home = /var/lib/barman
; System user
barman_user = barman
; Log location
log_file = /var/log/barman/barman.log
; Default compression level: possible values are None (default), bzip2, gzip or custom
compression = gzip
; Pre/post backup hook scripts
;pre_backup_script = env | grep ^BARMAN
;post_backup_script = env | grep ^BARMAN
;; ; 'main' PostgreSQL Server configuration
[main]
;; ; Human readable description
description = "Main PostgreSQL Database"
;;
;; ; SSH options
ssh_command = ssh postgres@192.168.1.133
;;
;; ; PostgreSQL connection string
conninfo = host=192.168.1.133 user=postgres

Also Ensure that .132 is trusted on main postgresql server .133 by adding the line in pg_hba.conf

host all all 192.168.1.132/32 trust

and Reload the config via

pg_ctl reload

Make archieve on postgres server (.133) in postgresql.conf

archive_mode = on
archive_command = 'rsync -a %p barman@backup:INCOMING_WALS_DIRECTORY/%f'

Make sure you change the INCOMING_WALS_DIRECTORY placeholder with the value returned by the ''barman show-server main'' command (.132 via barman user) above.

In Our case it is /var/lib/barman/main/incoming/

Restart the Postgresql Server ( reloading will not help )

Now Check the status on barman server (.132)
barman show-server main

It should show something like below
Server main:
active: true
description: Main PostgreSQL Database
ssh_command: ssh postgres@192.168.1.133
conninfo: host=192.168.1.133 user=postgres
backup_directory: /var/lib/barman/main
basebackups_directory: /var/lib/barman/main/base
wals_directory: /var/lib/barman/main/wals
incoming_wals_directory: /var/lib/barman/main/incoming
lock_file: /var/lib/barman/main/main.lock
compression: gzip
custom_compression_filter: None
custom_decompression_filter: None
retention_policy: None
wal_retention_policy: None
pre_backup_script: None
post_backup_script: None
current_xlog: 00000001000000010000000E
last_shipped_wal: None
archive_command: rsync -a %p barman@192.168.1.132:/var/lib/barman/main/incoming/%f
server_txt_version: 8.4.13
data_directory: /var/lib/pgsql/data
archive_mode: on
config_file: /var/lib/pgsql/data/postgresql.conf
hba_file: /var/lib/pgsql/data/pg_hba.conf
ident_file: /var/lib/pgsql/data/pg_ident.conf

Checking the barman server
barman check main
Server main:
ssh: OK
PostgreSQL: OK
archive_mode: OK
archive_command: OK
directories: OK
compression settings: OK

In our case we have linked the main diecrtory of /var/lib/barman to /home/postreg_barman_backup/main as the home partion is very big to hold the backups

ln -s /home/postreg_barman_backup/main /var/lib/barman/

==Backup Process==
As barman User on .132 server , running following command will take the backup

barman backup main

==Crontab entry==
To have backup at 1:00 , please have cron entry done via barman user for ''barman backup main'' command

==Restoration==
To restore a whole server issue the following command:

barman@backup$ barman recover main 20110920T185953 /path/to/recover/directory

where 20110920T185953 is the ID of the backup to be restored. When this command completes succesfully, /path/to/recover/directory contains a complete data directory ready to be started as a PostgreSQL database server.

For Remote Recovery

#barman recover main 20110920T185953 --remote-ssh-command postgres@server-ip:/tmp/recover

Here is an example of a command that starts the server:

barman@backup$ pg_ctl -D /path/to/recover/directory start

#pg_ctl Stop
#pg_ctl -D /tmp/recover start

==Important Commands ==

You can display the list of active servers that have been configured for your backup system with:

barman list-server

You can show the configuration parameters for a given server with: we are using ''main'' as the server name , you can have multiple servers too .

barman show-server main

You can list the catalogue of available backups for a given server with:

barman list-backup main

You can check if the connection to a given server is properly working with:

barman check main

==Checking of the barman postgresql Backup==

Login in 192.168.1.132 (the backup server of Muthoot)

su - barman
barman list-backup main

main 20121225T010001 - Tue Dec 25 01:04:37 2012 - Size: 2.0 GiB - WAL Size: 6.0 MiB
main 20121224T010001 - Mon Dec 24 01:04:34 2012 - Size: 2.0 GiB - WAL Size: 52.0 MiB
main 20121223T010002 - Sun Dec 23 01:04:35 2012 - Size: 2.0 GiB - WAL Size: 12.0 MiB
main 20121222T010001 - Sat Dec 22 01:04:33 2012 - Size: 2.0 GiB - WAL Size: 68.0 MiB
main 20121221T010002 - Fri Dec 21 01:04:33 2012 - Size: 2.0 GiB - WAL Size: 47.0 MiB
main 20121220T010001 - Thu Dec 20 01:04:31 2012 - Size: 2.0 GiB - WAL Size: 43.0 MiB
main 20121219T010001 - Wed Dec 19 01:04:31 2012 - Size: 2.0 GiB - WAL Size: 58.0 MiB
main 20121218T010001 - Tue Dec 18 01:04:31 2012 - Size: 2.0 GiB - WAL Size: 27.0 MiB

it should show the last few backups , else raise the alarm

==Delete Last Barman Backup ( as barman user)==

Script for auto deletion (delete-last-backup.sh)
#!/bin/bash
VALUE=`barman list-backup main | tail -1 | cut -d" " -f 2`
barman delete main $VALUE
exit

Make cron entry as barman user

Crontab -l

0 1 * * * barman backup main
0 6 * * * /var/lib/barman/delete-last-backup.sh

Bbf mailbox Migration

2013-08-31T15:23:48Z

Abhinav: Created page with " category:BBF Group '''Migration Mailbox and COS From Mailserver2 To Mailserver .''' ==Check Users in particular COS== 1.#zmprov gc bbf_users | grep zimbr..."

[[category:BBF Group]]

[['''Migration Mailbox and COS From Mailserver2 To Mailserver .''']]

==Check Users in particular COS==

1.#zmprov gc bbf_users | grep zimbraId
2.# zmprov sa zimbraId > /tmp/bbf_user.txt

==Set another COS==

1.zmprov setAccountCos test123@bbfgroup.com bbf_management

==Migrate Mailbox==

1.zmmailboxmove -a test234@bbfgroup.com -t mailserver.bbfgroup.com –force –po
-t = target
-po= purge old

Category:Spi Nagios

2013-07-27T06:19:36Z

Abhinav: Created page with "category: Spi Nagios == Spi Nagios Client Configuration == == Client Configuration == Install Rpmforge Epelrepo #mkdir /downloads #cd /downloads #w..."

[[category: Spi Nagios ]]

== Spi Nagios Client Configuration ==

== Client Configuration ==

Install Rpmforge Epelrepo

#mkdir /downloads

#cd /downloads

#wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

#rpm -Uvh rpmforge-release-0.5.2-2.el6.rf.x86_64.rp

#wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

#wget http://rpms.famillecollet.com/enterprise/remi-release-6.rpm

#rpm -Uvh remi-release-6*.rpm epel-release-6*.rpm

# vim /etc/yum.repos.d/remi.repo
enable 1

#yum install nrpe nagios-plugins-all

#vim /etc/nagios/nrpe.cfg
allowed_hosts=127.0.0.1, your nagios server ip

command[check_users]=/usr/lib64/nagios/plugins/check_users -w 5 -c 10
command[check_load]=/usr/lib64/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
command[check_disk_space]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -X tmpfs
command[check_zombie_procs]=/usr/lib64/nagios/plugins/check_procs -w 5 -c 10 -s Z
command[check_cpu]=/usr/lib64/nagios/plugins/check_cpu.sh -w 20 -c 60
command[check_zimbra_queue]=/usr/lib64/nagios/plugins/check_zimbra_queue -w 30 -c 60
command[check_mem_avail]=/usr/lib64/nagios/plugins/check_mem_avail -w 20 -c 10
command[check_pop]=/usr/lib64/nagios/plugins/check_pop -w 10 -c 20
command[check_smtp]=/usr/lib64/nagios/plugins/check_smtp -w 10 -c 20
command[check_imap]=/usr/lib64/nagios/plugins/check_imap -w 10 -c 20
command[check_zimbra_lmtp]=/usr/lib64/nagios/plugins/check_smtp -H localhost -p 7025 -e '220 spimail.spi.com Zimbra LMTP server ready'

Note: define all plugin in above given path.

# chmod nagios.nagios /usr/lib64/nagios/plugins -R

Now restart nrpe service

== Server configuration ==

#vim /usr/local/nagios/etc/objects/linux-box.cfg

== Define client details ==

define host{
use linux-server
host_name spimail.spi.com
alias Spi Mail Server
address 64.128.141.50
hostgroups Tetra Clients ; Host groups
}

#cd ../services
#vim spimail.spi.com.cfg

define service{
use generic-service
host_name spimail.spi.com
service_description Current Users
check_command check_nrpe!check_users
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Cpu Load
check_command check_nrpe!check_load
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Cpu Utilization
check_command check_nrpe!check_cpu
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Memory Utilization
check_command check_nrpe!check_mem_avail
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Disk Check
check_command check_nrpe!check_disk_space
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Zombie Process
check_command check_nrpe!check_zombie_procs
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Mail Queue
check_command check_nrpe!check_zimbra_queue
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Pop
check_command check_nrpe!check_pop
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Smtp
check_command check_nrpe!check_smtp
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Imap
check_command check_nrpe!check_imap
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Http
check_command check_http_spi // this is not define in client side , check in command.cfg
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Lmtp
check_command check_nrpe!check_zimbra_lmtp
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

== Configuration Of Warning and Critical Mail send by Nagios: ==

#Vim /usr/local/nagios/etc/objects/contacts.cfg

DEFINE CONTACT

define contact{
contact_name mailtest ; Short name of user
use generic-contact ; Inherit default values from generic-contact template (defined above)
alias Nagios Admin ; Full name of user

email test@tetrain.com ; <<***** CHANGE THIS TO YOUR EMAIL ADDRESS ******

define contactgroup{
contactgroup_name client-group
alias Nagios Administrators
members mailtest
}

Note : Now the client have to see only there services not all clients services for that we made new contact group i.e mailtest and now we want that they can wacth there services but do not change any thing for that we do one entry in below :

# vim /usr/local/nagios/etc/cgi.cfg
#authorized_for_read_only=user1,user2
authorized_for_read_only=mailtest

Note : Set password for user mailtest

# htpasswd htpasswd.users mailtest

Then check your mail.

TROUBLESHOOTING----------------

1. Check nagios port is open on client server
#nc -z client ip 5666

2. check client server is connected or not
#./usr/local/nagios/libexec/check_nrpe -n -H spimail.spi.com

3. check service
#/usr/local/nagios/libexec/check_nrpe -n -t 50 -H spimail.spi.com -c check_mem_avail

Spi-nagiosclient

2013-07-27T06:18:38Z

Abhinav:

Spi-nagiosclient

2013-07-27T06:17:13Z

Abhinav: Created page with "category: Spi Nagios == Spi Nagios Client Configuration == == Client Configuration == Install Rpmforge Epelrepo #mkdir /downloads #cd /downloads #wg..."

[[category: Spi Nagios ]]
== Spi Nagios Client Configuration ==

== Client Configuration ==

Install Rpmforge Epelrepo

#mkdir /downloads

#cd /downloads

#wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

#rpm -Uvh rpmforge-release-0.5.2-2.el6.rf.x86_64.rp

#wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

#wget http://rpms.famillecollet.com/enterprise/remi-release-6.rpm

#rpm -Uvh remi-release-6*.rpm epel-release-6*.rpm

# vim /etc/yum.repos.d/remi.repo
enable 1

#yum install nrpe nagios-plugins-all

#vim /etc/nagios/nrpe.cfg
allowed_hosts=127.0.0.1, your nagios server ip

command[check_users]=/usr/lib64/nagios/plugins/check_users -w 5 -c 10
command[check_load]=/usr/lib64/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
command[check_disk_space]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -X tmpfs
command[check_zombie_procs]=/usr/lib64/nagios/plugins/check_procs -w 5 -c 10 -s Z
command[check_cpu]=/usr/lib64/nagios/plugins/check_cpu.sh -w 20 -c 60
command[check_zimbra_queue]=/usr/lib64/nagios/plugins/check_zimbra_queue -w 30 -c 60
command[check_mem_avail]=/usr/lib64/nagios/plugins/check_mem_avail -w 20 -c 10
command[check_pop]=/usr/lib64/nagios/plugins/check_pop -w 10 -c 20
command[check_smtp]=/usr/lib64/nagios/plugins/check_smtp -w 10 -c 20
command[check_imap]=/usr/lib64/nagios/plugins/check_imap -w 10 -c 20
command[check_zimbra_lmtp]=/usr/lib64/nagios/plugins/check_smtp -H localhost -p 7025 -e '220 spimail.spi.com Zimbra LMTP server ready'

Note: define all plugin in above given path.

# chmod nagios.nagios /usr/lib64/nagios/plugins -R

Now restart nrpe service

== Server configuration ==

#vim /usr/local/nagios/etc/objects/linux-box.cfg

== Define client details ==

define host{
use linux-server
host_name spimail.spi.com
alias Spi Mail Server
address 64.128.141.50
hostgroups Tetra Clients ; Host groups
}

#cd ../services
#vim spimail.spi.com.cfg

define service{
use generic-service
host_name spimail.spi.com
service_description Current Users
check_command check_nrpe!check_users
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Cpu Load
check_command check_nrpe!check_load
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Cpu Utilization
check_command check_nrpe!check_cpu
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Memory Utilization
check_command check_nrpe!check_mem_avail
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Disk Check
check_command check_nrpe!check_disk_space
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Zombie Process
check_command check_nrpe!check_zombie_procs
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Mail Queue
check_command check_nrpe!check_zimbra_queue
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Pop
check_command check_nrpe!check_pop
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Smtp
check_command check_nrpe!check_smtp
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}
define service{
use generic-service
host_name spimail.spi.com
service_description Imap
check_command check_nrpe!check_imap
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Http
check_command check_http_spi // this is not define in client side , check in command.cfg
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

define service{
use generic-service
host_name spimail.spi.com
service_description Lmtp
check_command check_nrpe!check_zimbra_lmtp
contact_groups mailtest
notification_options w,u,c,r
normal_check_interval 3
}

== Configuration Of Warning and Critical Mail send by Nagios: ==

#Vim /usr/local/nagios/etc/objects/contacts.cfg

DEFINE CONTACT

define contact{
contact_name mailtest ; Short name of user
use generic-contact ; Inherit default values from generic-contact template (defined above)
alias Nagios Admin ; Full name of user

email test@tetrain.com ; <<***** CHANGE THIS TO YOUR EMAIL ADDRESS ******

define contactgroup{
contactgroup_name client-group
alias Nagios Administrators
members mailtest
}

Note : Now the client have to see only there services not all clients services for that we made new contact group i.e mailtest and now we want that they can wacth there services but do not change any thing for that we do one entry in below :

# vim /usr/local/nagios/etc/cgi.cfg
#authorized_for_read_only=user1,user2
authorized_for_read_only=mailtest

Note : Set password for user mailtest

# htpasswd htpasswd.users mailtest

Then check your mail.

TROUBLESHOOTING----------------

1. Check nagios port is open on client server
#nc -z client ip 5666

2. check client server is connected or not
#./usr/local/nagios/libexec/check_nrpe -n -H spimail.spi.com

3. check service
#/usr/local/nagios/libexec/check_nrpe -n -t 50 -H spimail.spi.com -c check_mem_avail

Muthoot Cluster

2013-07-04T09:51:06Z

Abhinav:

--[[User:Abhinav|Abhinav]] 15:20, 4 July 2013 (IST)[[category:Postgresql Cluster Muthoot]]
'''Cluster Of Muthoot'''
== Postgresql Cluster ==

==IP Details:==

1. Live Server ip: 192.168.1.133
2. Secondary Server ip: 192.168.1.132
3. Cluster Ip: 192.168.1.140
4. Mgmt port ip: 192.168.1.126 (liveserver)
5. Mgmt port ip: 192.168.1.127( Secondary)
6. Ip for heartbeat : 10.0.0.1 (node1)
7. Node 2: 10.0.0.2

==Configuration:==

133# vim /etc/hosts
192.168.1.133 liveserver.muthootco.com liveserver
192.168.1.132 liveserver1.muthootco.com liveserver1
10.0.0.1 node1.muthootco.com node1
10.0.0.2 node2.muthootco.com node2
192.168.1.127 node2-imm.muthootco.com node2-imm
192.168.1.126 node1-imm.muthootco.com node1-imm

Give 10.0.0.1 ip in eth1 in liveserver And 10.0.0.2 ip in eth1 in secondary server.

Note : Give Ip to Management port Steps are follow:

Step1: On boot Time go to bios
Step2: System Settings-->Integrated Management Module --> Network-->Give Ip

133# yum install cman rgmanager ricci luci

Note: luci package is only on one system

Then open web interface :
https://192.168.1.133:8084
User: Same as system root details
Then Go to Service Group Tab
Then Press add button
Service Name : Cluster-Service
Failover Domain: None
Recovery Policy : relocate
IP Address: 192.168.1.140 \\ don’t give netmask for this IP

133# yum remove libvirt \\ Due to this package node can’t be add it’s give error

==Then Go To Node Tab==

Add-->
Node Name: node1
Password: same as system
Port: 11111
Same Do for node 2
Then Go To Fence Device Tab:
Press Add
Fence Type: IPMI LAN
Name : node2-imm
Ip add- 192.168.1.127
Login: USERID
Password:xyz
Authentication Type: None
Privileges Level: default

==Then Again Press add==
Configure same
Name – node1-imm
Ip – 192.168.1.126
Apply

==Then Go To node TAB==

Click on node 1--> Add fence method-->Fence_Method-->then Add fence instance -->node1-imm(IPMI LAN)-->Submit

Same do with node 2 configuration and add node2-imm

==Then Go To Service Group TAB==

Failover Domain: Failover
Apply

'''Note''': Make two LVM Volumes
Vol Name: DB , Logical Vol : test
Vol Name: LogsSpace , Logical Vol : LogSystem

Then Go To Resources Tab:
Add--> HA LVM-->
Name : HA
VG Name : DB
Add-->Filesystem-->
Name: DB File
File System Type: ext4
Mount point: /home/pgsql/data/base \\path must be exist
Device Name: /dev/mapper/DB-test
Force Unmount : check mark
Apply

==Add -->HA LVM==
Name : Logs
Vol Grp Name: LogsSpace

==Add--> Filesystem==
Name: Logs_Details
File System Type: ext4
Mount point: /Logs
Device Name: /dev/mapper/LogsSpace-logSystem

Add-->script
Name: Sql-Script
Full Path to script File: /etc/init.d/postgresql
Apply

Muthoot Cluster

2013-07-04T09:50:01Z

Abhinav: Created page with "--~~~~category:Postgresql Cluster Muthoot '''Cluster Of Muthoot''' == Postgresql Cluster == ==IP Details:== ..."

--[[User:Abhinav|Abhinav]] 15:20, 4 July 2013 (IST)[[category:Postgresql Cluster Muthoot]]
'''Cluster Of Muthoot'''
== Postgresql Cluster ==

==IP Details:==

1. Live Server ip: 192.168.1.133
2. Secondary Server ip: 192.168.1.132
3. Cluster Ip: 192.168.1.140
4. Mgmt port ip: 192.168.1.126 (liveserver)
5. Mgmt port ip: 192.168.1.127( Secondary)
6. Ip for heartbeat : 10.0.0.1 (node1)
7. Node 2: 10.0.0.2

==Configuration:==

133# vim /etc/hosts
192.168.1.133 liveserver.muthootco.com liveserver
192.168.1.132 liveserver1.muthootco.com liveserver1
10.0.0.1 node1.muthootco.com node1
10.0.0.2 node2.muthootco.com node2
192.168.1.127 node2-imm.muthootco.com node2-imm
192.168.1.126 node1-imm.muthootco.com node1-imm

Give 10.0.0.1 ip in eth1 in liveserver And 10.0.0.2 ip in eth1 in secondary server.

==Note== : Give Ip to Management port Steps are follow:

Step1: On boot Time go to bios
Step2: System Settings-->Integrated Management Module --> Network-->Give Ip

133# yum install cman rgmanager ricci luci

Note: luci package is only on one system

Then open web interface :
https://192.168.1.133:8084
User: Same as system root details
Then Go to Service Group Tab
Then Press add button
Service Name : Cluster-Service
Failover Domain: None
Recovery Policy : relocate
IP Address: 192.168.1.140 \\ don’t give netmask for this IP

133# yum remove libvirt \\ Due to this package node can’t be add it’s give error

==Then Go To Node Tab==

Add-->
Node Name: node1
Password: same as system
Port: 11111
Same Do for node 2
Then Go To Fence Device Tab:
Press Add
Fence Type: IPMI LAN
Name : node2-imm
Ip add- 192.168.1.127
Login: USERID
Password:xyz
Authentication Type: None
Privileges Level: default

==Then Again Press add==
Configure same
Name – node1-imm
Ip – 192.168.1.126
Apply

==Then Go To node TAB==

Click on node 1--> Add fence method-->Fence_Method-->then Add fence instance -->node1-imm(IPMI LAN)-->Submit

Same do with node 2 configuration and add node2-imm

==Then Go To Service Group TAB==

Failover Domain: Failover
Apply

'''Note''': Make two LVM Volumes
Vol Name: DB , Logical Vol : test
Vol Name: LogsSpace , Logical Vol : LogSystem

Then Go To Resources Tab:
Add--> HA LVM-->
Name : HA
VG Name : DB
Add-->Filesystem-->
Name: DB File
File System Type: ext4
Mount point: /home/pgsql/data/base \\path must be exist
Device Name: /dev/mapper/DB-test
Force Unmount : check mark
Apply

==Add -->HA LVM==
Name : Logs
Vol Grp Name: LogsSpace

==Add--> Filesystem==
Name: Logs_Details
File System Type: ext4
Mount point: /Logs
Device Name: /dev/mapper/LogsSpace-logSystem

Add-->script
Name: Sql-Script
Full Path to script File: /etc/init.d/postgresql
Apply

Category:Phdcci Migration

2013-05-30T09:57:53Z

Abhinav: Created page with "category:Phdcci Migration =='''Qmail With Vpopmail To Zimbra 7.2.3 Migration in CentOS 6.3'''== == ..."

[[category:Phdcci Migration]]
=='''Qmail With Vpopmail To Zimbra 7.2.3 Migration in CentOS 6.3'''==

== For PHDCCI==

Created by : Abhinav Sharma

TETRA INFORMATION SERVICES PVT. LTD.

SYSTEM CONFIGURATION

Vim /etc/hosts

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.3 webmail.phdcci.in webmail
Set Hostname To webmail.phdcci.in

# vi /etc/sysconfig/network
--------------------------------------------
HOSTNAME=webmail.phdcci.in
--------------------------------------------

Save & Close this file.

Make changes to hosts file.

Stop Apache and also make it off at boot time.

# /etc/init.d/httpd stop
# chkconfig httpd off

Configure DNS.

# Yum install bind*
Configure Bind in Jail Environment.

# vim /var/named/chroot/etc/named.conf
options {
listen-on port 53 { 127.0.0.1; 192.168.0.3; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
Allow-Query {localhost; 192.168.0.0;};
recursion yes;
};

zone "phdcci.in"{
type master;
file "forward.zone";
};

zone "0.168.192.in-addr.arpa" IN {
type master;
file "localhostrev.zone";
};

Then Do the Entries in Forward Zone
phdcci.in. IN MX 10 webmail.phdcci.in.
@ IN NS ns1.phdcci.in.
ns1.phdcci.in. IN A 192.168.0.3
webmail.phdcci.in. IN A 192.168.0.3
webmail. IN A 192.168.0.3
phdcci.in. IN A 207.106.22.8
cpanel IN A 68.233.251.20
www.phdcci.in. IN A 68.233.251.20
www2.phdcci.in. IN A 68.233.251.20

Reverse Zone

$TTL 86400
@ IN SOA webmail.phdcci.in. root.webmail.phdcci.in. (
20130503 ; serial
3600 ; refresh
1800 ; retry
604800 ; expire
86400 ) ; minimum
IN NS webmail.phdcci.in.

3 IN PTR webmail.phdcci.in.

Start named service.

# /etc/init.d/named Restart
Starting named: [ OK ]
# chkconfig named on
# vim /etc/resolv.conf
--------------------------------------
nameserver 127.0.0.1
nameserver 4.2.2.2

Install prerequisites of Zimbra
yum install sysstat compat-libstdc++-33 nc -y

Zimbra Installation
Mkdir /downloads
Cd /downloads
Extract Package
Cd zcs
./install.sh --platform-override
By This Zimbra Installed in Server.

Now Migration of Users

Step1: Extract User From vpopmail in one file And Cp into new Server tmp location
Step2: Arrange in Order Like
Vim User.txt
createAccount test@phdcci.in root123 displayName 'Test Account' givenName Test sn Account zimbraPasswordMustChange True

Step3: su – zimbra
Step4: zmprov < /tmp/user.txt
All User Are created by this command

Migration of mails of some user
Command
imapsync --nosyncacls --subscribe --syncinternaldates
--host1 192.168.0.1 --user1 yourAccount --password1 yourPassword
--host2 192.168.0.3 --user2 yourZimbraAccount --password2 yourZimbraPassword

View Mail Option In Admin Panal:
Step1: Download zimlet from
http://www.zimbra.com/forums/administrators/56332-view-mail-button.html
Step2: Go to Admin panal then Zimlet then deploy the zimlet.

Phdcci Migration

2013-05-30T09:40:49Z

Abhinav: Created page with "category:Phdcci Migration =='''Qmail With Vpopmail To Zimbra 7.2.3 Migration in CentOS 6.3'''== == ..."

Hero Moto Corp Mail Architecture

2013-01-22T13:11:48Z

Abhinav:

[[category:Heromotocorp]]

== Architecture ==

[[Image:Heromotocorp's_Mail_Architecture.png|700px]]

==Architecture In Brief:==

1. Qmail2 Introduce in both server. Becauese of Disclaimer i.e
a)Heromotocorp.com
b)Herofincorp.com

2. Now mails first go to qmail then if mails are local then it deliver And if mail are remote then forward to qmail2 i.e on 900 port.
For this check smtproute of
a)qmail point to :127.0.0.1:900
b)qmail2 point to :tetra ip:25

3. Qmail2 check automatically that whether it is heromotocorp.com or herofincorp.com . And then attach Diclaimer according to domain.

Eltek Mail-Deliver Problem

2013-01-18T14:57:41Z

Abhinav:

[[category:Tetra Clients]]

==Eltek==

==Issue==

MAils are not deliver to pop id(through jbindia server) , mail send from it@eltek.in to outer domian get deliver but when send mail to pop in
west@eltek.in (pop id).

==Observation==

Check the local mail server . qmail running properly. MAils are deliver as shown in logs but it actually not deliver. Then check the Jbindia in
which spamdyke(spam filter) is not allowed eltek ip to deliver mail at there local pop user.

==Resolution:==

Whitelist eltek domain

Path: /var/qmail/spamdyke/rdns-whitelist

Eltek Mail-Deliver Problem

2013-01-18T14:54:05Z

Abhinav: Created page with "category:Tetra Clients ==Eltek== ==Issue== MAils are not deliver to pop id(through jbindia server) , mail send from it@eltek.in to outer domian get deliver but when s..."

[[category:Tetra Clients]]

==Eltek==

==Issue==

MAils are not deliver to pop id(through jbindia server) , mail send from it@eltek.in to outer domian get deliver but when send mail to pop id west@eltek.in (pop id).

==Observation==

Check the local mail server . qmail running properly. MAils are deliver as shown in logs but it actually not deliver. Then check the Jbindia in which spamdyke(spam filter) is not allowed eltek ip to deliver mail at there local pop user.

==Resolution:==

Whitelist eltek domain

Path: /var/qmail/spamdyke/rdns-whitelist

Create VM By Running Vmimage

2013-01-03T14:55:08Z

Abhinav: Created page with "category:Tetra Local ==Create VM Through Running VM Image: == 1. Let suppose running VM is Centos And creating Vm name is Centos-1 2. xm list 3. If Vm is running t..."

[[category:Tetra Local]]

==Create VM Through Running VM Image: ==

1. Let suppose running VM is Centos And creating Vm name is Centos-1

2. xm list

3. If Vm is running then it's ok Otherwise use this command to up Centos

4. # xm create Centos

5. # xm restore Centos

6. # xm list

7. Once a vm running then use this command

8. # xm shutdown Centos

9. cp -pvr /data/Centos /data/centos-1

vim /etc/xen/Centos-1

name = "Centos-1"

uuid = "967b2dd3-15b5-f72d-0527-046e30e209ba"

maxmem = 512

memory = 512

vcpus = 1

bootloader = "/usr/bin/pygrub"

on_poweroff = "destroy"

on_reboot = "restart"

on_crash = "restart"

vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]

disk = [ "tap:aio:/data/centos6.img,xvda,w" ]

vif = [ "mac=00:16:36:2b:bb:9e,bridge=xenbr0,script=vif-bridge" ]

11. # xm create Centos-1

12. # xm list

13. virt-manager

14. open Cenos-1 vm

15. And add NIC card in it.

16. Login with Centos details.

17. Change ip and see the updated Hardware address

Witalsee details

2013-01-01T11:35:40Z

Abhinav:

[[category:Tetra Clients]]

== Witalsee Mail Server Details(PACL): ==

== Server Details: ==

There has two leased lines:

Reliance – 124.124.221.167/26 , 5mbps line.

Tata – 115.112.96.103/26 , Backup leased line,5mbps line
-----------------------------------------------------------------------------------
Global Ip: 115.112.96.103 (active), eth0 port

Local Ip: 192.168.7.19 (active), eth0 port

Backup Sever : 192.168.7.16

Achive Sever : 192.168.7.18

Archive Backup Server: 192.168.7.17

Hardware Firewall : 192.168.7.15

== Architecture Of Mail Server: ==

1. There is one Zimbra mail Server, Where one main domain called groupmailadmin.com (with shorewall server(Iptables) configured )

2. Subdomain of groupmailadmin is witasee.com

3. There is one backup server Which is 24/7 Sync of zimbra server.

4. One Achive Server.

5. One Backup server of Archive server.

== Flow of witalsee mail server ==

Step1. Mails Directly land to there mail server. One Copy of mail is go to Achive Server.

Step2. One mail backup server which is 24/7 Synchronize.

Step3. One More backup server of archive server.

Witalsee details

2013-01-01T11:26:46Z

Abhinav:

Witalsee details

2013-01-01T11:19:55Z

Abhinav: Created page with "category:Tetra Clients == Witalsee Mail Server Details(PACL): == == Server Details: == There has two leased lines: Reliance – 124.124.221.167/26 , 5mbps line. ..."

[[category:Tetra Clients]]

== Witalsee Mail Server Details(PACL): ==

== Server Details: ==

There has two leased lines:

Reliance – 124.124.221.167/26 , 5mbps line.

Tata – 115.112.96.103/26 , Backup leased line,5mbps line
-----------------------------------------------------------------------------------
Global Ip: 115.112.96.103 (active), eth0 port

Local Ip: 192.168.7.19 (active), eth0 port

Backup Sever : 192.168.7.16

Achive Sever : 192.168.7.18

Archive Backup Server: 192.168.7.17

== Architecture Of Mail Server: ==

1. There is one Zimbra mail Server, Where one main domain called groupmailadmin.com

2. Subdomain of groupmailadmin is witasee.com

3. There is one backup server Which is 24/7 Sync of zimbra server.

4. One Achive Server.

5. One Backup server of Archive server.

6. One shorewall server.

== Flow of witalsee mail server ==

Step1. Mails Directly land to there mail server. One Copy of mail is go to Achive Server.

Step2. One mail backup server which is 24/7 Synchronize.

Step3. One More backup server of archive server.

INDORAMA BACKUP PROCESS

2012-12-29T15:11:07Z

Abhinav:

[[category:Tetra Clients‏‎]]

==Indorama Backup Process==

I) '''Gurgaon:'''

Log on to Gurgaon
# tar cvzf etc_16_04_11.tar.gz /etc
# tar cvzf named_16_04_11.tar.gz /var/named/
# tar cvzf trend_16_04_11.tar.gz /opt/trend/
# tar cvzf momsbin_16_04_11.tar.gz /usr/.momsbin

II) '''Mumbai:'''

From Gurgaon,
# ssh mumbai
# tar cvzf etc_16_04_11.tar.gz /etc
# tar cvzf named_16_04_11.tar.gz /var/named/
# tar cvzf trend_16_04_11.tar.gz /opt/trend/
# tar cvzf momsbin_16_04_11.tar.gz /usr/.momsbin

From Mumbai,
#ssh mumproxy
# tar cvzf etc_16_04_11.tar.gz /etc
# tar cvzf named_16_04_11.tar.gz /var/named/
# tar cvzf trend_16_04_11.tar.gz /opt/trend/
Scp to mumbai then mumbai to gurgaon

III) '''Nagpur:'''

From Gurgaon,
# ssh nagpur
# tar cvzf etc_16_04_11.tar.gz /etc
# tar cvzf named_16_04_11.tar.gz /var/named/
# tar cvzf trend_16_04_11.tar.gz /opt/trend/
# tar cvzf momsbin_16_04_11.tar.gz /usr/.momsbin

Nagpur Proxy Server,
#ssh 192.128.91.13
#tar cvzf etc_16_04_11.tar.gz /etc
#tar cvzf named_16_04_11.tar.gz /var/named/

#ssh 192.168.94.13
#tar cvzf etc_16_04_11.tar.gz /etc
#tar cvzf named_16_04_11.tar.gz /var/named/

IV) '''Surat:'''

From Gurgaon,
# ssh surat
# tar cvzf etc_16_04_11.tar.gz /etc
# tar cvzf named_16_04_11.tar.gz /var/named/
# tar cvzf trend_16_04_11.tar.gz /opt/trend/
# tar cvzf momsbin_16_04_11.tar.gz /usr/.momsbin

V) '''Transferring files:'''

scp files from Mumbai, Surat and Nagpur onto Gurgaon server.

CCAT DOCS

2012-12-22T11:24:14Z

Abhinav:

[[category:Tetra Clients]]

== CCAT DETAILS:==

== DNS Servers Details ==

Primary Server:
1. Server Ip / Global Ip: 58.64.162.10
2. Server Name: CCATSRV1.ccatgroup.com
3. Active Port: eth0
4. Local Ip : None

Secondary Server:
1. Server Ip: 58.64.162.11
2. Server Name: CCATSRV2.ccatgroup.com
3. Active Port: eth0

Summary About Dns Server Of CCAT:

1. In these Two server One is Primary Dns server( Tiny Dns). And second One is Secondary server.
2. When Primary server is busy or traffic is more then Secondary server handle the Queries.

== Zimbra Server Detail: ==

Server Ip: 58.64.162.12
Server Name: CCATSRV3.ccatgroup.com
Active Port: eth0

Zimbra Admin Panal- https://58.64.162.12:7071/zimbraAdmin/

== Qmail With Vpopmail Server: ==

Server Ip: 58.64.162.13
Server Name: CCATINDIA.IN
Active Port: eth0
Hostname: beedeemcsrv1

1. In this server 5 domain are hosted And mails of that Domain Users Exist Here:
A) beedeemc.com
B) candy-king.net
C) ccatindia.in
D) pasha.hk
E) supriltd.com

Default Gateway Ip: 58.64.162.1

== MySql Database Login Detail ==

myslq -uroot for 10(NO PASSWORD)

==CCAT Group ==

we used the below links for webmail access.
https://rathsworld.com:8889
https://pibl.com.hk:8889

for the domain piblhk.com they are using exchange server hosting outside.
Admin panel for Zimbra is as below.
https://113.28.42.81:7071
OR
https://rathsworld.com:7071

Zimbra tetratesting account:
e-mail id: tetratest@rathsworld.com

Other 2 server details i will send you soon. For all the servers and
domains 210.17.247.96 & 97 is the name server.

We dont have any standrad control panel. We use the below link for domain
controls.

http://ccatsrv1.ccatgroup.com/vhsadmin
http://ccatsrv2.ccatgroup.com/vhsadmin

look into this ticket: 2011090110001174 ] CCAT : Need to configure domain pacificexcel.net in CCATSRV1[..]

domain added in

cd /service/tinydns/root/
578 ls
579 ls -l
580 ./add-ns e-lflash.com 210.17.247.96
581 ./add-ns e-lflash.com 210.17.247.97
582 cat data
583 ls -l
584 cat data
585 ls -l
586 cat data
587 ls
588 ./add-mx e-lflash.com 210.17.247.96
589 ./add-mx e-lflash.com 210.17.247.97
590 ./add-alias www.e-lflash.com 210.17.247.96
592 ./add-alias pop.e-lflash.com 210.17.247.96
593 ./add-alias e-lflash.com 210.17.247.96
594 ./add-alias mailadmin.e-lflash.com 210.17.247.96

RCA .

rcpthosts.cdb was created on both the server by \

/var/qmail/bin/qmail-cdb rcpthosts.cdb rcpthost.tmp < rcpthosts

CCAT CONFIGURE NEW DOMAIN IN CCAT SERVER 1 FOR MAIL SERVER:
===============================================================================
QUERY:
Need to configure the domain e-lflash.com in ccatsrv1. Pls do the
necessery setting for this doman in the server and send us the details. We
will change the name server setting in the register.
===============================================================================

SOLUTION:

RCA:

********************************************************************************************
Note:Firstly take backup of all files which you want to edit.

1. Create directory "www.e-lflash.com" in "/var/www/vhosts/"

2. Add domain alias "e-lflash.com" in /etc/squirrelmail/apache.conf on ccatsrv1
add this line in file:
"ServerAlias pop.e-lflash.com"

for website

cd /etc/apache2/sites-available/
create file domain.com
<VirtualHost *:80>
ServerName blmintl.com
ServerAlias www.blmintl.com
DocumentRoot /var/www/vhosts/www.blmintl.com/www
CustomLog /var/log/apache2/vhosts/blmintl.com.log combined
ErrorLog /var/log/apache2/vhosts/blmintl.com-error
</VirtualHost>

ln -s /etc/apache2/sites-available/blmintl.com /etc/apache2/sites-enabled/blmintl.com

reload apache2

3. This steps applies on ccatsrv1 and ccatsrv2:
cd /service/tinydns/root/
./add-ns e-lflash.com 210.17.247.96
./add-ns e-lflash.com 210.17.247.97
./add-mx e-lflash.com 210.17.247.96
./add-mx e-lflash.com 210.17.247.97
./add-alias www.e-lflash.com 210.17.247.96
./add-alias pop.e-lflash.com 210.17.247.96
./add-alias e-lflash.com 210.17.247.96
./add-alias mailadmin.e-lflash.com 210.17.247.96

after this step execute "make" command to compile "data" file.

4. rcpthosts.cdb was created on both servers:
add domain "e-lflash.com" in /var/qmail/control/rcpthosts
#/var/qmail/bin/qmail-cdb rcpthosts.cdb rcpthost.tmp < rcpthosts

add into locals files in which server mailbox is exist.
#/var/qmail/bin/qmail-cdb locals.cdb locals.tmp < locals

5. add domain in "/var/qmail/control/smtproutes" file: (check mail box of e-lflash.com on both server before this step.)
e-lflash.com:210.17.247.96:25

6. Restart apache2 service.
#/etc/init.d/apache2 restart|reload
********************************************************

./add-ns indiadesk.com.hk 210.17.247.96
./add-ns galaxymarine.com.hk 210.17.247.97

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

210.17.247.39

Bee.Dee#@!mc
beedeemc.com

Please find the vqadmin login Details.

URL: <http://ccatindia.in/cgi-bin/vqadmin/vqadmin.cgi>
http://beedeemc.com/cgi-bin/vqadmin/vqadmin.cgi

<http://ccatindia.in/cgi-bin/qmailadmin>
http://beedeemc.com/cgi-bin/qmailadmin

Domain: <http://beedeemc.com/> beedeemc.com

----------------------------------------------------------
SKYPE DETAILS
tetra.service
sysop0603
--[[User:Subhash|Subhash]] 16:15, 29 September 2012 (IST)

CCAT DOCS

2012-12-22T11:23:17Z

Abhinav:

CCAT DOCS

2012-12-22T10:54:34Z

Abhinav:

[[category:Tetra Clients]]

== CCAT DETAILS:==

== DNS Servers Details ==

Primary Server:
1. Server Ip / Global Ip: 58.64.162.10
2. Server Name: CCATSRV1.ccatgroup.com
3. Active Port: eth0
4. Local Ip : None

Secondary Server:
1. Server Ip: 58.64.162.11
2. Server Name: CCATSRV2.ccatgroup.com
3. Active Port: eth0

Summary About Dns Server Of CCAT:

1. In these Two server One is Primary Dns server( Tiny Dns). And second One is Secondary server.
2. When Primary server is busy or traffic is more then Secondary server handle the Queries.

== Zimbra Server Detail: ==

Server Ip: 58.64.162.12
Server Name: CCATSRV3.ccatgroup.com
Active Port: eth0

Zimbra Admin Panal- https://58.64.162.12:7071/zimbraAdmin/

== Qmail With Vpopmail Server: ==

Server Ip: 58.64.162.13
Server Name: CCATINDIA.IN
Active Port: eth0
Hostname: beedeemcsrv1

1. In this server 5 domain are hosted And mails of that Domain Users Exist Here:
A) beedeemc.com
B) candy-king.net
C) ccatindia.in
D) pasha.hk
E) supriltd.com

Default Gateway Ip: 58.64.162.1

==CCAT Group ==

Pls see our server login and ip details as below.

myslq -uroot for 96(NO PASSWORD)
2 Main servers and 1 Zimbra server.

1) Zimbra Server details.
IP : 210.17.247.36
ssh port: 22

Server name Old IP New IP

CCATSRV1.ccatgroup.com 210.17.247.96 58.64.162.10

CCATSRV2.ccatgroup.com 210.17.247.97 58.64.162.11

CCATSRV3.ccatgroup.com 210.17.247.36 58.64.162.12

CCATINDIA.IN 210.17.247.39 58.64.162.13

3) Second Zimbra Server details.
ip : 113.28.42.81

we used the below links for webmail access.
https://rathsworld.com:8889
https://pibl.com.hk:8889

for the domain piblhk.com they are using exchange server hosting outside.
Admin panel for Zimbra is as below.
https://113.28.42.81:7071
OR
https://rathsworld.com:7071

Zimbra tetratesting account:
e-mail id: tetratest@rathsworld.com

Other 2 server details i will send you soon. For all the servers and
domains 210.17.247.96 & 97 is the name server.

We dont have any standrad control panel. We use the below link for domain
controls.

http://ccatsrv1.ccatgroup.com/vhsadmin
http://ccatsrv2.ccatgroup.com/vhsadmin

look into this ticket: 2011090110001174 ] CCAT : Need to configure domain pacificexcel.net in CCATSRV1[..]

domain added in

cd /service/tinydns/root/
578 ls
579 ls -l
580 ./add-ns e-lflash.com 210.17.247.96
581 ./add-ns e-lflash.com 210.17.247.97
582 cat data
583 ls -l
584 cat data
585 ls -l
586 cat data
587 ls
588 ./add-mx e-lflash.com 210.17.247.96
589 ./add-mx e-lflash.com 210.17.247.97
590 ./add-alias www.e-lflash.com 210.17.247.96
592 ./add-alias pop.e-lflash.com 210.17.247.96
593 ./add-alias e-lflash.com 210.17.247.96
594 ./add-alias mailadmin.e-lflash.com 210.17.247.96

RCA .

rcpthosts.cdb was created on both the server by \

/var/qmail/bin/qmail-cdb rcpthosts.cdb rcpthost.tmp < rcpthosts

CCAT CONFIGURE NEW DOMAIN IN CCAT SERVER 1 FOR MAIL SERVER:
===============================================================================
QUERY:
Need to configure the domain e-lflash.com in ccatsrv1. Pls do the
necessery setting for this doman in the server and send us the details. We
will change the name server setting in the register.
===============================================================================

SOLUTION:

RCA:

********************************************************************************************
Note:Firstly take backup of all files which you want to edit.

1. Create directory "www.e-lflash.com" in "/var/www/vhosts/"

2. Add domain alias "e-lflash.com" in /etc/squirrelmail/apache.conf on ccatsrv1
add this line in file:
"ServerAlias pop.e-lflash.com"

for website

cd /etc/apache2/sites-available/
create file domain.com
<VirtualHost *:80>
ServerName blmintl.com
ServerAlias www.blmintl.com
DocumentRoot /var/www/vhosts/www.blmintl.com/www
CustomLog /var/log/apache2/vhosts/blmintl.com.log combined
ErrorLog /var/log/apache2/vhosts/blmintl.com-error
</VirtualHost>

ln -s /etc/apache2/sites-available/blmintl.com /etc/apache2/sites-enabled/blmintl.com

reload apache2

3. This steps applies on ccatsrv1 and ccatsrv2:
cd /service/tinydns/root/
./add-ns e-lflash.com 210.17.247.96
./add-ns e-lflash.com 210.17.247.97
./add-mx e-lflash.com 210.17.247.96
./add-mx e-lflash.com 210.17.247.97
./add-alias www.e-lflash.com 210.17.247.96
./add-alias pop.e-lflash.com 210.17.247.96
./add-alias e-lflash.com 210.17.247.96
./add-alias mailadmin.e-lflash.com 210.17.247.96

after this step execute "make" command to compile "data" file.

4. rcpthosts.cdb was created on both servers:
add domain "e-lflash.com" in /var/qmail/control/rcpthosts
#/var/qmail/bin/qmail-cdb rcpthosts.cdb rcpthost.tmp < rcpthosts

add into locals files in which server mailbox is exist.
#/var/qmail/bin/qmail-cdb locals.cdb locals.tmp < locals

5. add domain in "/var/qmail/control/smtproutes" file: (check mail box of e-lflash.com on both server before this step.)
e-lflash.com:210.17.247.96:25

6. Restart apache2 service.
#/etc/init.d/apache2 restart|reload
********************************************************

./add-ns indiadesk.com.hk 210.17.247.96
./add-ns galaxymarine.com.hk 210.17.247.97

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

210.17.247.39

Bee.Dee#@!mc
beedeemc.com

Please find the vqadmin login Details.

URL: <http://ccatindia.in/cgi-bin/vqadmin/vqadmin.cgi>
http://beedeemc.com/cgi-bin/vqadmin/vqadmin.cgi

<http://ccatindia.in/cgi-bin/qmailadmin>
http://beedeemc.com/cgi-bin/qmailadmin

Domain: <http://beedeemc.com/> beedeemc.com

----------------------------------------------------------
SKYPE DETAILS
tetra.service
sysop0603
--[[User:Subhash|Subhash]] 16:15, 29 September 2012 (IST)

Category:Tetra Clients

2012-12-18T11:19:17Z

Abhinav: Replaced content with "category:Phdcci "

[[category:Phdcci ]]

Category:Tetra Clients

2012-12-18T11:18:08Z

Abhinav:

[[category:Phdcci ]]

Phdcci Architecture And Details:

Server Details:

Global IP : 210.7.75.146 (active), eth0 port
Local Ip : 192.168.0.1 , eth1 port
In phdcci, one mail server contains :
a) Iptables
b)Squid
c)Qmail + 2 Instance

1. mails are directly land to the mail server.
2. When phdcci user send a mail then first check whether it is local or not this work is done by 1st instance and when user not exist then it passes to 2nd instance and 2nd instance of qmail attach a disclaimer in it and send it.

Category:Tetra Clients

2012-12-18T11:06:25Z

Abhinav: Blanked the page

Category:Tetra Clients

2012-12-18T11:05:52Z

Abhinav:

[[category:Tetra Clients]]

Phdcci Architecture And Details:

Server Details:

Global IP : 210.7.75.146 (active), eth0 port
Local Ip : 192.168.0.1 , eth1 port
In phdcci, one mail server contains :
a) Iptables
b)Squid
c)Qmail + 2 Instance

1. mails are directly land to the mail server.
2. When phdcci user send a mail then first check whether it is local or not this work is done by 1st instance and when user not exist then it passes to 2nd instance and 2nd instance of qmail attach a disclaimer in it and send it.

Category:Tetra Clients

2012-12-18T10:58:38Z

Abhinav: Blanked the page

Category:Tetra Clients

2012-12-18T10:57:35Z

Abhinav:

[[category:Phdcci Structure & Details]]
[[category:Tetra Clients]]

Phdcci Architecture And Details:

Server Details:

Global IP : 210.7.75.146 (active), eth0 port
Local Ip : 192.168.0.1 , eth1 port
In phdcci, one mail server contains :
a) Iptables
b)Squid
c)Qmail + 2 Instance

1. mails are directly land to the mail server.
2. When phdcci user send a mail then first check whether it is local or not this work is done by 1st instance and when user not exist then it passes to 2nd instance and 2nd instance of qmail attach a disclaimer in it and send it.

File:Training doc new.pdf

2012-12-04T08:59:44Z

Abhinav:

[[category:Tetra Training Doc PDF]]

Category:Tetra Clients/Web Hosting Of BJP In Godaddy Server

2012-12-04T08:57:31Z

Abhinav:

[[category:Tetra_Clients]]

------------------------------------------------------------------------------------------------------------------------------------------------------------
BJP WEB HOSTING ON GODADDY SERVER:

------------------------------------------------------------------------------------------------------------------------------------------------------------

1. Login to Godaddy server.

2. Open that given host file and paste it to:

# mv hostfile /home/public_html/hostfile

3.Go to configuration file of Apache server i.e :

#vim /etc/httpd/conf/httpd.conf

<VirtualHost ip:80>

DocumentRoot /home/public_ html/bjpinloksabha/
ServerName bjpls.tetra.in
ErrorLog logs/bjpinloksabha-error_log
CustomLog logs/bjpinloksabha-access_log "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
<Directory /home/public_html/bjpinloksabha>
DirectoryIndex index.php
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

# Go to sql command promt using :

1. mysql>mysql -u{username} -p{password}

2. mysql>show databases;

3. mysql>create database db_name;

4. mysql> CREATE USER 'tetra'@'localhost' IDENTIFIED BY 'some_pass';

5. mysql> GRANT ALL PRIVILEGES ON *.* TO 'tetra'@'localhost' WITH GRANT OPTION;

6. quit

# Store the dump that you have :

#mysql -u{username} -p{password} db_name < /path/db.sql

// GO TO FILE WHERE YOU CAN CONNECT DATABASE TO HOSTFILE //

1. vim /home/public_html/admin/connect.php
2. Where you can enter the created database user name and password.

3. When Website run then some Notices and Error are shown to you For that we make entry in one file:

# vim /etc/php.ini

4. Uncomment this line OR write this line

error_reporting = E_ALL & ~E_NOTICE

5. Comment this line
error_reporting = E_ALL & ~E_NOTICE | E_STRICT

6. Reload the apache server

/etc/init.d/httpd reload

7. Please check the site.

Category:Tetra Clients/Web Hosting Of BJP In Godaddy Server

2012-12-04T08:56:14Z

Abhinav:

[[category:BJP WEB HOSTING ON GODADDY SERVER]]

------------------------------------------------------------------------------------------------------------------------------------------------------------
BJP WEB HOSTING ON GODADDY SERVER:

------------------------------------------------------------------------------------------------------------------------------------------------------------

1. Login to Godaddy server.Tetra_Clients

2. Open that given host file and paste it to:

# mv hostfile /home/public_html/hostfile

3.Go to configuration file of Apache server i.e :

#vim /etc/httpd/conf/httpd.conf

<VirtualHost ip:80>

DocumentRoot /home/public_ html/bjpinloksabha/
ServerName bjpls.tetra.in
ErrorLog logs/bjpinloksabha-error_log
CustomLog logs/bjpinloksabha-access_log "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
<Directory /home/public_html/bjpinloksabha>
DirectoryIndex index.php
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

# Go to sql command promt using :

1. mysql>mysql -u{username} -p{password}

2. mysql>show databases;

3. mysql>create database db_name;

4. mysql> CREATE USER 'tetra'@'localhost' IDENTIFIED BY 'some_pass';

5. mysql> GRANT ALL PRIVILEGES ON *.* TO 'tetra'@'localhost' WITH GRANT OPTION;

6. quit

# Store the dump that you have :

#mysql -u{username} -p{password} db_name < /path/db.sql

// GO TO FILE WHERE YOU CAN CONNECT DATABASE TO HOSTFILE //

1. vim /home/public_html/admin/connect.php
2. Where you can enter the created database user name and password.

3. When Website run then some Notices and Error are shown to you For that we make entry in one file:

# vim /etc/php.ini

4. Uncomment this line OR write this line

error_reporting = E_ALL & ~E_NOTICE

5. Comment this line
error_reporting = E_ALL & ~E_NOTICE | E_STRICT

6. Reload the apache server

/etc/init.d/httpd reload

7. Please check the site.

Category:Tetra Clients/Web Hosting Of BJP In Godaddy Server

2012-12-04T08:39:30Z

Abhinav:

File:Training doc new.pdf

2012-12-04T07:54:39Z

Abhinav:

Category:Tetra Clients/Web Hosting Of BJP In Godaddy Server

2012-12-04T07:49:47Z

Abhinav: Created page with "------------------------------------------------------------------------------------------------------------------------------------------------------------ ..."

------------------------------------------------------------------------------------------------------------------------------------------------------------
BJP WEB HOSTING ON GODADDY SERVER:

------------------------------------------------------------------------------------------------------------------------------------------------------------

1. Login to Godaddy server.

2. Open that given host file and paste it to:

# mv hostfile /home/public_html/hostfile

3.Go to configuration file of Apache server i.e :

#vim /etc/httpd/conf/httpd.conf

<VirtualHost ip:80>

DocumentRoot /home/public_ html/bjpinloksabha/
ServerName bjpls.tetra.in
ErrorLog logs/bjpinloksabha-error_log
CustomLog logs/bjpinloksabha-access_log "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
<Directory /home/public_html/bjpinloksabha>
DirectoryIndex index.php
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

# Go to sql command promt using :

1. mysql>mysql -u{username} -p{password}

2. mysql>show databases;

3. mysql>create database db_name;

4. mysql> CREATE USER 'tetra'@'localhost' IDENTIFIED BY 'some_pass';

5. mysql> GRANT ALL PRIVILEGES ON *.* TO 'tetra'@'localhost' WITH GRANT OPTION;

6. quit

# Store the dump that you have :

#mysql -u{username} -p{password} db_name < /path/db.sql

// GO TO FILE WHERE YOU CAN CONNECT DATABASE TO HOSTFILE //

1. vim /home/public_html/admin/connect.php
2. Where you can enter the created database user name and password.

3. When Website run then some Notices and Error are shown to you For that we make entry in one file:

# vim /etc/php.ini

4. Uncomment this line OR write this line

error_reporting = E_ALL & ~E_NOTICE

5. Comment this line
error_reporting = E_ALL & ~E_NOTICE | E_STRICT

6. Reload the apache server

/etc/init.d/httpd reload

7. Please check the site.