Create RAID10 array in Centos 6.6

Create RAID10 array in Centos 6.6

(Revised 04/18/2015)

I built my own NAS. This consisted of a Centos 6.6 box (i5 CPU, 4GB DDR3 1600 RAM, Samsung Pro 120GB SSD for boot and OS, and four 3TB WD RED SATA3 Hard Drives, 1GB Ethernet). I use NFS and samba as a means of sharing files and doing backups. I used RADI10 so I get the speed of striping and the redundancy of mirrored drives. The reason for the hardware, a bit much for just storage purposes, is I will also be installing Plex on it for video streaming. Oh ya, also putting asterisk on it with a SIP Trunk to CLEC for some small usage home stuff (no big requirements for the asterisk at this scale)

I am still out on file systems. I am looking at ext4 and ZFS though. More on that in later post. For now I am using ext4, as you will see later in this post.

I used a post by Babin Lonston · November 19, 2014 as a starting point located at:

http://www.tecmint.com/create-raid-10-in-linux/

But added/removed items as it pertained to me.

First thing I did was check and set my WD drives idle time to park heads. In the /root directory I download and. NOTE** /dev/sda is my SSD boot and OS drive so I won’t be touching this one :)


#  tar -xzf idle3-tools-0.9.1.tgz
#  cd /root/idle3-tools-0.9.1

# ./idle3ctl -g /dev/sdb
Idle3 timer set to 138 (0x8a)


# ./idle3ctl -g /dev/sdc
Idle3 timer set to 138 (0x8a)

# ./idle3ctl -g /dev/sdd
Idle3 timer set to 138 (0x8a)

# ./idle3ctl -g /dev/sde
Idle3 timer set to 138 (0x8a)
  
As you can see the timer is set to 138. Not Good. this will make the parks 100's of thousands of times each year. Premature wear. So I turned them off.

# ./idle3ctl -d /dev/sdb
Idle3 timer disabled
Please power cycle your drive off and on for the new setting to be taken into account. A reboot will not be enough!


# ./idle3ctl -d /dev/sdc
Idle3 timer disabled
Please power cycle your drive off and on for the new setting to be taken into account. A reboot will not be enough!

# ./idle3ctl -d /dev/sdd
Idle3 timer disabled
Please power cycle your drive off and on for the new setting to be taken into account. A reboot will not be enough!

# ./idle3ctl -d /dev/sde
Idle3 timer disabled
Please power cycle your drive off and on for the new setting to be taken into account. A reboot will not be enough! 
 

Now power off system

# poweroff

After powering back on verify they are disabled 

# ./idle3ctl -g /dev/sdb
Idle3 timer is disabled
 
# ./idle3ctl -g /dev/sdc
Idle3 timer is disabled
 
# ./idle3ctl -g /dev/sdd
Idle3 timer is disabled
 
# ./idle3ctl -g /dev/sde
Idle3 timer is disabled
 
It’s time to check the drives whether there is already any raid existed before creating a new one. NOTE** /dev/sda is my SSD boot and OS drive so I won’t be touching this one :)

# mdadm -E /dev/sd[b-e]
# mdadm --examine /dev/sdb /dev/sdc /dev/sdd /dev/sde

**If any of the disk have a prior setup or MBR records then use this to clean them. Do this for each drive

             How to remove an mdadm Raid Array

Find out your arrays (md0, md1, etc..) using

# fdisk -l

Query your arrays to find out what disks are contained using

# mdadm --detail /dev/md0

Shut down the array using

# umount -l /dev/md0

# mdadm --stop /dev/md0

zero the superblock FOR EACH drive

# mdadm --zero-superblock /dev/sdb

# mdadm --zero-superblock /dev/sdc

# mdadm --zero-superblock /dev/sdd

# mdadm --zero-superblock /dev/sde

 

If you have to remove the MBR and partition use

dd if=/dev/zero of=/dev/sdb bs=1M count=1

You may also need to remove the mdadm.conf if there was a raid on there already.

# cat /etc/mdadm.conf

# rm /etc/mdadm.conf

Now create a new partition on all 4 disks (/dev/sdb, /dev/sdc, /dev/sdd and /dev/sde) using parted. NOTE** fdisk will not work with partitions over 2TB.

I had to enable my EPEL repo to get gparted (parted for the cli). I then installed the package

# yum -y install gparted

# parted /dev/sdb

GNU Parted 2.1

Using /dev/sdb

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

Error: /dev/sdb: unrecognised disk label

(parted) mklabel gpt

(parted) print

Model: Unknown (unknown)

Disk /dev/sdb: 3001GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number  Start  End  Size  File system  Name  Flags

(parted) mkpart primary 0GB 3001GB

(parted) print

Model: Unknown (unknown)

Disk /dev/sdb: 5909GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags

 1      1049kB  5909GB  3001GB               primary

(parted)

Now do this for the other three disk (/dev/sdc, /dev/sdd and /dev/sde)

After creating all 4 partitions, again I examined the drives for any already existing raid using the following command.

# mdadm -E /dev/sd[b-e]
 

# mdadm -E /dev/sd[b-e]1

OR

# mdadm --examine /dev/sdb /dev/sdc /dev/sdd /dev/sde
 

# mdadm --examine /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1

Now it’s time to create a ‘md’ (i.e. /dev/md0) device, using ‘mdadm’ raid management tool. Before, creating device your system must have ‘mdadm’ tool installed. NOTE** I turn off all EPEL repos before doing this to insure I get the one from Centos.

# yum -y install mdadm

Once ‘mdadm’ tool installed, you can now create a ‘md’ raid device using the following command.

# mdadm --create /dev/md0 --level=10 --raid-devices=4 /dev/sd[b-e]1

Next verify the newly created raid device using the ‘cat’ command.

# cat /proc/mdstat

Next, examine all the 4 drives, partition 1, using the below command. The output of the below command will be long as it displays the information of all 4 disks.

# mdadm --examine /dev/sd[b-e]1

Next, check the details of Raid Array with the help of following command.

# mdadm –detail /dev/md0

Create a file system using ext4 for md0. Here I used ext4, but you can use any filesystem type if you want.

# mkfs.ext4 /dev/md0

After creating filesystem, mount the created file-system under ‘/mnt/raid10‘ and list the contents of the mount point using ‘ls -l’ command.

# mkdir /mnt/raid10
 

# mount /dev/md0 /mnt/raid10/
 

# ls -l /mnt/raid10/

For automounting, open the ‘/etc/fstab‘ file and append the below entry in fstab, may be mount point will differ according to your environment. Save and quit using :w and :q

# vi /etc/fstab 

/dev/md0 /mnt/raid10 ext4 defaults 0 0

Next, verify the ‘/etc/fstab‘ file for any errors before restarting the system using ‘mount -a‘ command.

# mount -av

By default the raid array does not have a config file, so we need to save it manually after making all the above steps, to preserve these settings during system boot.

# mdadm --detail --scan --verbose >> /etc/mdadm.conf

Now reboot and make sure the array is still in place and mounted

# reboot

After you log back in

# mdadm --detail /dev/md0 

I have done articles for install/setup of NFS and samba as well. Now I will apply those to this array and share the data on it.

http://glenewhittenberg.blogspot.com/2015/04/setting-up-nfs-server-and-client.html

http://glenewhittenberg.blogspot.com/2015/04/samba-setup-on-centos-66.html

End.



 

Setting Up the NFS Server and Client on Centos 6.6

Setting Up the NFS Server

Server IP is 192.168.10.110
Client IP is 192.168.10.20

Download the Required Software on the NFS Server

# yum -y install nfs-utils nfs-utils-lib

Start services now and start on reboot as well

# chkconfig nfs on
# chkconfig rpcbind on
# service rpcbind start
# service nfs start

Make the NFS exported/shared directory of /nfsexports/home/

# mkdir -p /nfsexports/home/

Now set the shared directory for export

# vi /etc/exports

Add the following to the file

/nfsexports/home          192.168.10.20(rw,sync,no_root_squash,no_subtree_check)

The above settings accomplish:

* rw: This option allows the client server to both read and write within the shared directory
 
* sync: Sync confirms requests to the shared directory only once the changes have been committed.
 
* no_subtree_check: This option prevents the subtree checking. When a shared directory is the subdirectory of a larger filesystem, nfs performs scans of every directory above it, in order to verify its permissions and details. Disabling the subtree check may increase the reliability of NFS, but reduce security.
 
* no_root_squash: This phrase allows root to connect to the designated directory
   
Now export them within

# exportfs -a

Now create a file in your /nfsexports/home/ directory called testfile

# touch /nfsexports/home/testfile

Now verify the file is there

ls -lsa /nfsexports/home
4 drwxr-xr-x 2 root root 4096 Apr  5 18:37 .
4 drwxr-xr-x 3 root root 4096 Apr  5 18:05 ..
0 -rw-r--r-- 1 root root    0 Apr  5 18:37 testfile


Setting Up the NFS Client

Download the Required Software on the Client Server

# yum -y install nfs-utils nfs-utils-lib

Create the directory that will contain the mount from the Server

# mkdir -p /mnt/nfs/home

Now mount it

# mount 192.168.10.110:/nfsexports/home /mnt/nfs/home

See if it is mounted

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_whittenberg-lv_root
                       18G  2.5G   14G  16% /
tmpfs                 1.9G     0  1.9G   0% /dev/shm
/dev/sda1             477M   48M  405M  11% /boot
192.168.10.110:/nfsexports/home
                       18G  909M   16G   6% /mnt/nfs/home

                      
As you can see above we have a successful mount from 192.168.10.110:/nfsexports/home in our Client Server under /mnt/nfs/home. Now anything we save in the /mnt/nfs/home directory on our client is actually written on the NFS Server.

Now you can make sure the mount on the client server is active after reboot by

# vi /etc/fstab

And add the following to the file

192.168.10.110:/nfsexports/home  /mnt/nfs/home   nfs      auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0

Commands to show/work with mounts

# man nfs
# mount -a
# df -h
# mount
# umount

The end!

Samba Setup on Centos 6.6

Samba Setup on Centos 6.6

Since I am behind a firewall in my local LAN I have disabled SELINUX and turned firewall off. i am also fully up to date on packages as of 4/1/2015.

Disable SELinux

# vi /etc/selinux/config
And change to SELINUX=disabled

Turn off firewall

# service iptables stop
# chkconfig iptables off
# reboot

NOTE** I fought with this for day so beware! I am on Centos 6.6 I have the epel repo active in my repo list. When I used yum for the install of samaba, I think it got it from there. All worked well with using \\ip_addr_of_samba_server\ but I could never get my samba server to show up in windows network browser. I discovered nmb was NOT running on the samba server. Not good if you want windows to discover it automatically. So I completely removed samba using “yum –y remove samba*” (notice the * at the end of samba. And leave out the quotes). I then removed the epel repo with “rpm -e your-epel-package-name-here” Now you can install samba with the steps below and have it work 100%.

Install samba

# yum -y install samba

Create user and set password for samba share use

# useradd samba -s /sbin/nologin
# smbpasswd -a samba
            Supply a password
            Retype the password

mkdir for the shared files and set permissions

# mkdir /share
# chown -R samba:root /share/

Now config samba for the share and share user

# vi /etc/samba/smb.conf

Add/edit this under the [global] section

[global]
workgroup = WORKGROUP ;use name of your workgroup here
server string = Samba Server Version %v
netbios name = SAMBA

Add this to botton of /etc/samba/smb.conf file

[share]
comment = Share
path = /share
writable = yes
valid users = shareuser

Now start samaba and make sure it is on after boot

# service smb start
# chkconfig smb on
# service nmb start
# chkconfig nmb on

Now test your setup with

# testparm

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[share]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
server string = Samba Server Version %v
log file = /var/log/samba/log.%m
max log size = 50
cups options = raw
[homes]
comment = Home Directories
read only = No
browseable = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[share]
comment = Share
path = /share
valid users = shareuser
read only = No


NOTE** make sure your workgroup =  is the actual name of your Windows workgroup, smb service is running, and nmb service is running, or you won’t see your samba server when windows machines browse the network.

Note: ** when accessing your samba server from windows 8.1 there is a problem with accessing the same server with two sets of credentials. Meaning if you login to a samba share as one user you will not be able to login to another share as another user. If you need to change users you can relogin into Windows OS (not cool) or use:

C:\> net use * /DELETE

Say yes to remove the connection(s) you already have, thus saving a reboot :) 

If you get CUPS printer messages in your /var/log/messages file you can edit the smb.conf file to reflect the following:

        load printers = yes
        cups options = raw

;       printcap name = /etc/printcap
        # obtain a list of printers automatically on UNIX System V systems:
        printcap name = /dev/null
        printing = bsd


Thanks to:

http://www.if-not-true-then-false.com/2010/yum-remove-repo-repository-yum-disable-repo-repository/

http://www.krizna.com/centos/installing-configuring-samba-centos-6/

The end!

Mounting a remote nfs file system in Centos 6.6

Mounting a remote nfs file system in Centos 6.6

Playing with FreeNAS 9.3. After setting up the share on the NAS I had to do the following to get the share mounted under my cent server.

1. If not already installed:

# yum -y install nfs-utils nfs-utils-lib

2. Start rpcbind

# service rpcbind start

3. Make directory on local file sys for the remote nfs to be mounted

# mkdir /mnt/nas

4, Mount the nfs share in the /mnt/nas directory now

# mount -t nfs 192.168.1.2:/mnt/MyPool/FreeNASlinux /mnt/nas

Using Gmail as a SMTP relay

Using Gmail as a SMTP relay

1. From Email: youremail@gmail.com
2. Outgoing Mail Server: smtp.gmail.com
3. Port: 465
4. Security: SSL
5. Authentication: Check Enable SMTP Authentication
6. Username: youremail@gmail.com
7. Password: xxxxxxxx
8. Authentication Method: Login

Install LAMP on Centos 6.6

Install LAMP on Centos 6.6

LAMP stands for Linux, Apache, MySQL and PHP. Must haves if you are going to do web hosting.

My base install has selinux=disabled, iptables off, eth0 interface setup for static , and ntp working.

login as root

Install epel repo if not already done so

## RHEL/CentOS 6 64-Bit ## 
# wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 
# rpm -ivh epel-release-6-8.noarch.rpm


Install Apache

# yum -y install httpd
# service httpd start
# chkconfig httpd on
# service httpd status

Install PHP

# yum -y install php

Install MySQL

# yum -y install mysql-server mysql

# service mysqld start
# chkconfig mysqld on
# service mysqld status

Now run secure install. Be sure and supply root password if using this through phpMyAdmin

# mysql_secure_installation

The End..

Install phpMyAdmin on Centos 6.6

Install phpMyAdmin on Centos 6.6

My base install has selinux=disabled, iptables off, eth0 interface setup for static , ntp working, httpd installed, MariaDB (MySQL) installed, and PHP installed. All of those things have been verified as working 100%. I have how to do all those things in this blog.

login as root

Add the the repository that is for your OS. Do this in your home directory. if root then it should be /root

## RHEL/CentOS 6 64-Bit ## 
# wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 
# rpm -ivh epel-release-6-8.noarch.rpm

# yum -y install phpMyAdmin

phpMyAdmin by default allowed to access from localhost only. If you want to make it accessible from remote computers edit

/etc/httpd/conf.d/phpMyAdmin.conf 

and update all 127.0.0.1 with your network like below or enable phpMyAdmin access for everyone.

Like:

<Directory /usr/share/phpMyAdmin/>
    <IfModule !mod_authz_core.c>
     Order Deny,Allow
     Deny from All
     Allow from 192.168.1.0/24
     Allow from ::1
   </IfModule>
</Directory>

 Now restart httpd

 # service httpd restart

Now login into your phpMyAdmin console with your web browser with:

http://my_ip_address/phpMyAdmin

Of course that means use the IP address of the server you just installed phpMyAdmin on.

When I setup MySQL I allowed root login and gave it a password. You must use a MySQL account with a password when accessing your MySQL through phpMyAdmin.

If your still getting denied:

You need to follow the following steps: Find line that read follows Require ip 127.0.0.1 Replace with your workstation IP address: Require ip 10.1.3.53 Again find the following line: Allow from 127.0.0.1 Replace as follows: Allow from 10.1.3.53 Also find deny from all and comment it in the entire file. Save and close the file.Restart Apache httpd server

The End :)

Setting up NTP in Centos 6.6

Setting up NTP in Centos 6.6

 First we need to make sure we have the correct date, time, and timezone. You can verify with:

# cat /etc/localtime

Set your time zone with (for Phoenix AZ USA)

#cp /usr/share/zoneinfo/America/Phoenix /etc/localtime


Now check date

# date
Sun Mar 29 01:10:44 MST 2015

You can verify this at the hardware level with:

# hwclock -r
Sun 29 Mar 2015 01:13:51 AM MST  -0.156631 seconds

If  these are incorrect then we can set the OS first and then update the hardware with the date command. The syntax is: date "day month year hh:mm:ss" So if we wanted to change this to March 2 2015 at 1:00pm we would use:

# date -s "2 MAR 2015 13:00:00"

When we have the date correct in the OS we can update the hardware with:

# hwclock -w

Now that we have the correct date and time lets install and setup ntp. First lets install ntp if not already installed.

# yum -y install ntp

Next edit the the ntp.conf file so we are using the correct time servers.

# vi /etc/ntp.conf

I usually use the public servers from the pool.ntp.org project of:
server 0.centos.pool.ntp.org iburst
server 1.centos.pool.ntp.org iburst
server 2.centos.pool.ntp.org iburst
server 3.centos.pool.ntp.org iburst

After you have those in lets start the service and make sure it is on in startup.

# service ntpd start
Starting ntpd:                                             [  OK  ]
# chkconfig ntpd on

Now lets verify the setup by looking at our peers.

# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*deekayen.net    209.51.161.238   2 u   43   64    3   75.257  -22.456   3.017
 origin.towfowi. 204.9.54.119     2 u   43   64    3   31.405  -14.629   2.683
 NTP2.playallian 129.6.15.30      2 u   43   64    3   50.576  -14.090   3.465
 sola-dal-09.ser 10.0.77.54       4 u   42   64    3   59.879   -1.507   2.629
 

Yum htop install from EPEL Extra Packages for Enterprise Linux

Yum htop install from EPEL 

(Extra Packages for Enterprise Linux)

Add the the repository that is for your OS. Do this in your home directory. if root then it should be /root

## RHEL/CentOS 6 32-Bit ## 
# wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm 
# rpm -ivh epel-release-6-8.noarch.rpm 

## RHEL/CentOS 6 64-Bit ## 
# wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 
# rpm -ivh epel-release-6-8.noarch.rpm


Now install htop

# yum -y install htop

Setting up Voice Mail in Asterisk 11.15.0

Setting up Voice Mail in Asterisk 11.15.0

If your going to use email notifications then make sure sendmail is installed

# yum -y install sendmail

Edit your /etc/asterisk/voicemail.conf file. After the [general] and [zonemessages] sections, any other bracketed section is a voice mail context. Within each context, you can define one or more mailbox. To define a mailbox, we set a mailbox number, a PIN, the mailbox owner's name, the primary email address, a secondary email address, and a list of mailbox options (separated by the pipe character), as shown below:

[context]

mailbox=>pin,full name,email address,short email address,mailbox options

By way of explanation, the short email address is an email address that will receive shorter email notifications suitable for mobile devices such as cell phones and pagers. It will never receive attachments, even if attach=yes. If you don’t want to use the email, or short, email address just put nothing in it. Be sure to use the comma though for a place holder.

An example of this I use in my lab is:

[internal]

6026356915 => 9999, Glen whittenberg,glen.whittenberg@cableone.biz,,attach=yes|maxmsg=100

My context is internal and extension is 6026356915 as defined in my sip.conf and extensions.conf files. 9999 will be my password. Glen Whittenberg is my full name. glen.whittenberg@cableone.biz is my email address. I am not using a short email addr so I just put in the comma. My options, separated by pipe symbol, are voicemail attachments will be sent to email, attach=yes, and maximum messages will be 100, maxmsg=100.

Now let’s edit the /etc/asterisk/extensions.conf file. We will add 9999 to get to voicemal system and also add to our extensions, and DID’s, to enable voicemail for them.

To make 9999 your access number to the voicemail system add the flowing under the [internal] context:

;used 9999 to access voicemail

exten => 9999,1,Answer(500)

exten => 9999,n,VoiceMailMain(@internal)

Now for my extension of 6026356915 I added the following, still in my [internal] context:

exten => 100,n,VoiceMail(6026356915@internal,u)

My entire entry so far for this extensions is:

;used to pass extension dialed, 100, to registered phone of 6026356915

exten => 100,1,Dial(SIP/6026356915,20)

exten => 100,n,VoiceMail(6026356915@internal,u)

exten => 100,n,Playback(vm-goodbye)

exten => 100,n,Hangup

You can see I am using 100 to associate to 6026356915. This allows me to dial 100 from inside the system instead the entire 6026356915 number to call this phone/extension.

Now we need to edit our context concerning outside calls into the system. So when an outside caller calls my DID of 6026356915 they can also leave a voice message.

Again edit the /etc/asterisk/extensions.conf file under the correct context for inbound calls. In my case this context is called [from-test]. This was defined in my /etc/asterisk/dahdi-channels.conf file. Add the following for the DID 6026356915.

exten => 6026356915,n,VoiceMail(6026356915@internal,u)

My entire entry under the [from-test] context for DID 6026356915 is:

exten => 6026356915,1,Dial(SIP/6026356915,20)

exten => 6026356915,n,VoiceMail(6026356915@internal,u)

exten => 6026356915,n,Playback(vm-goodbye)

exten => 6026356915,n,Hangup

Now reload voicemail and extensions in asterisk with:

# asterisk –x ‘core reload’

Enjoy!

Asterisk SIP Trunk to Vitelity

Asterisk SIP Trunk to Vitelity

To get your Asterisk server up with Centos 6.6 see my post at:

CENTOS 6.6 and Asterisk 11.15.0 Install

After you have your server up you will need to get an account at Vitelity:

Vitelity 

Its is a pretty simple process from there. Login into Vitelity site, under support, click Asterisk Support. They will give you two links personalized for your account.

Asterisk via Registration: sip.conf - extensions.conf 

 

All you do is enter the information in the sip.conf and extensions.conf as they state. Simple copy/paste action.

They give you the bare bones to register the inbound and outbound peers. They also give you an exten=> for your phone numbers. I was using three digit extensions and simply changed there defaults. The default they gave me was:

[inbound]
exten => 4803861111,1,Answer

I changed this to:

exten => 4803861111,1,Dial(SIP/100)
exten => 4803861111,n,Hangup

This allows me to register my phone as extension 100 and receive inbound calls from 4803861111 on extension 100.

Edgewater Edgemarc Edgemarc 4550 General Setup

cli default login / password = root / @#$%^&*!()
I used the craft cable and issued passwd command for this change

NOTE: 192.168.1.1 is default LAN address

webui default login / password = root / default

set up DHCP server for options and address pool

WAN interface is: your_ip_address/255.255.255.0
LAN interface is: 192.168.1.1/255.255.255.0

Security/firewall allow SSH, HTTP, HTTPS on WAN interface

Set up users/MOTD if wanted

I enabled firewall logging

Setup phone on LAN side of edgemarc. Point to your BRS system.
you should be able to make calls now..

Use port forwarding on your Edgemarc to get to management of phones if wanted. Like: set WAN port 8081 to forward to phone1 IP port 80. Use 8082 for phone2, etc. I am also testing a IP PBX behind this Edgemarc and use a port forward of 2222 on the WAN and forward to port 22 of IP of PBX so i can get SSH access to it. I am already using ports 80 and 22 for Edgemark access, hence why the use of additional ports and the forwarding. I will make another post on the asterisk SIP trunking to brs while asterisk is behind the Edgemark when i am finished testing.

Capture an EdgeMarc protocol trace
1. SSH into the EdgeMarc CLI
2. Type: tcpdump -ni iface -s 0 [port port_number]
    - Ex: tcpdump -ni eth0 -s 0 port 5060
    Decode SIP traffic from the LAN interface (VLANs not in use)
    - Ex: tcpdump -ni eth0.500
    Decode all traffic from VLAN ID 500
    - Ex: tcpdump -ni hdlc0 -s 0 port 5060
    Decode SIP traffic from an HDLC WAN interface

Xlite to BRS

In xlite go to sip acct settings
Display name = Your TN for the user
Username = Your TN for the user
Password = Password you set-up for auth settings in brs AS for this user
Auth user name = Name you set-up for auth settings in brs AS for this user
domain = your_domain.net
Check Register with Domain to send/receive calls
check proxy and use xxx.xxx.xxx.xxx. This will use the SBC/proxy if you have one and need to use it.