Tuesday, March 26, 2013

Telnet Automation using Python: Copy CISCO configs to TFTP server


Scenario:
Enterprise is using TELNET for CISCO management. It wants to design an automated script that will copy config (either startup-config or running-config) of the CISCO routers and switches to the TFTP server. TFTP server has separate folder for each routers.
There are the times when a network engineer forgets to copy router config to the TFTP server after he/she makes changes to CISCO config. This little python script can be scheduled to copy configs periodically saving network engineers from possible unforeseen havoc because they don't have backup copy of the router config and router has crashed.

Note: This Python script is based on  Python version 3.3. You can execute this script on both windows and linux/unix environment. You can download python from http://www.python.org/getit/. When you install python make sure that python is added to your system environment variables.


#File name: telnetautomation.py
#!/usr/bin/python
#Script starts here
import getpass
import sys
import telnetlib
import time

pwd1 = "user_exec_mode_password"
pwd2 = "privilege_exec_mode_password"
config = "startup-config"

#Create a list of router IP address, folder location and router hostname  

hostlist= [ ("router1_ip_address","plano","planoRouter1"),
            ("router2_ip_address","dallas","dallasRouter1"),
        ]

#Use for loop to telnet into each routers and execute commands
for host in hostlist:
    
    cmd1 = "en"
    cmd2 = "copy "+config+" tftp://tftp_server/cisco/"+host[1]+"/"+host[2]+".txt"
#copy startup-config  tftp://tftp_server/plano/planoRouter1.txt

    tn = telnetlib.Telnet(host[0])
    tn.set_debuglevel(5)

    time.sleep(2)
    tn.write(pwd1.encode('ascii') + b"\n")
    time.sleep(2)
    tn.write(cmd1.encode('ascii') + b"\n")
    time.sleep(2)
    tn.write(pwd2.encode('ascii') + b"\n")
    time.sleep(2)
    tn.write(cmd2.encode('ascii') + b"\n")
    time.sleep(2)
    tn.write(b"\n")
    time.sleep(2)
    tn.write(b"\n")
    time.sleep(2)
    tn.close()

sys.exit("operation completed")

#script ends here

[Note: TELNET is not my favorite protocol as it is very insecure. Communication is done in plain text. However, there are many enterprises still running this insecure protocol in their environment. Upgrade to SSH and disable TELNET in your environment if possible.]

Friday, February 1, 2013

How to host multiple SSL enabled sites on a single IP address using Apache?

In the past, only one SSL enabled website could be hosted on a single IP address and default port 443 due to the limitation of TLS negotiation. With an addition of SNI(Server Name Identification) extension to TLS, server can now host multiple SSL enables sites using VirtualHost directive.

Apache ( 2.2.12 or later ) using OpenSSL(0.9.8 or later)  incorporates SNI. Today many browsers with the latest updates support SNI too. However, there could be many users still using older version of browsers that don't support SNI. Thus,  you may run into an issue where those customers may only be able to access your default website not the others.

Apache Configuration :

    Listen 443
    NameVirtualHost *:443
    SSLStrictSNIVHostCheck off

<VirtualHost *:443>
        ServerName  website1.yourdomain.com
        DocumentRoot /usr/local/your-website1/
----
----
</VirutalHost>

<VirtualHost *:443>
        ServerName  website2.yourdomain.com
        DocumentRoot /usr/local/your-website2/
----
----
</VirutalHost>


  • NameVirtualHost  apache directive is required if you want to configure name-based virtual hosts.
  • If SSLStrictSNIVHostCheck is off, then the request will be handled as if the server did not have SNI support.



Note: In Ubuntu, make changes appropriately to ports.conf and sites-enabled/your-ssl-websites  configuration files. In SLES, make changes appropriately  to listen.conf and vhosts.d/your-ssl-websites configuration files.


Additional Info:
Q: How to create SSL self signed certificate?
Ans: You can follow 4 basic steps:
    Step1: Generate no pass-phrase server private key; Note you can use any name for the key and certs. I prefer to use website URL as it is easier to track.
            #openssl genrsa -out website1.yourdomain.com.key 2048
    Step2: Generate CSR(Certificate Signing Request) using server private key
           #openssl req -new -key website1.yourdomain.com.key -out website1.yourdomain.com.csr
   Step3: Generate certificate using CSR and server private key.
           #openssl x509 -req -days 730 -in website1.yourdomain.com.csr  
-signkey website1.yourdomain.com.key -out website1.yourdomain.com.crt
   Step4: Copy certs and keys to appropriate location. In Linux, you can copy private keys to /etc/ssl/private and certificates to /etc/ssl/certs/

Q: How can I view the details of a certificate?
Ans: You can use the following command 
 #openssl x509 -in website1.yourdomain.com.crt -text

You can see that Certificate contains the reference to the issuer, the public key of the owner of this certificate, the dates of validity of this certificate and the signature of the certificate to ensure this certificate hasn't been tampered with. The certificate does not contain the private key as it should never be transmitted in any form whatsoever. This certificate has all the elements to send an encrypted message to the owner (using the public key) or to verify a message signed by the author of this certificate.

Q: How can I deploy SSL key and certificate in Apache?
Ans: You can follow 2 basic steps:
  Step1: Update VirtualHost configuration with the information of  SSL key and certificate you created.

    <VirtualHost *:443>
        ServerName  website1.yourdomain.com
        DocumentRoot /usr/local/your-website1/   
        SSLCertificateFile    /etc/ssl/certs/website1.yourdomain.com.crt
        SSLCertificateKeyFile /etc/ssl/private/website1.yourdomain.com.key
   </VirutalHost>


  Step2: Reload apache
         #service apache2 reload

Q: How SSL works?
Ans: 
Read notes from Symantec.com , tldp.org and luxsci.com

Basic steps (reference: tldp.org):
  1. A browser requests a secure page (usually https://).
  2. The web server sends its public key with its certificate. Note: Usually Certificate is signed with a private key of trusted Certificate Authority (e.g Verisign, Thwate, GoDaddy,etc). You can self sign a cert as demonstrated above if you don't want to pay for CSR. 
  3. All the browser comes installed with public key of all trusted Certificate Authority. The browser uses the public key to verify that the certificate was issued by a trusted root CA and certificate is still valid and that the certificate is related to the site contacted. If certificate is not signed by trusted CA, browser will complain that "Site's certificate is not trusted!".
  4. The browser then uses web server's public key to encrypt a random symmetric encryption key and sends it to the server with the encrypted URL required as well as other encrypted http data.
  5. The web server decrypts the symmetric encryption key using its private key and uses the symmetric key to decrypt the URL and http data.
  6. The web server sends back the requested html document and http data encrypted with the symmetric key.
  7. The browser decrypts the http data and html document using the symmetric key and displays the information.




Reference:

Wednesday, January 30, 2013

SNMP ObjectID Hierarchy



SNMP MIB Object tree/name space is hierarchical in structure rooted at root(.). This structure allows each manageable object to have its own globally unique name. This structure made SNMP modular. Each name space can be expanded without interfering/consulting with other name space or internet authority.
For example: name space assigned to CISCO is .1.3.6.1.4.1.9 [ root.iso.org.dod.internet.private. enterprises.cisco ] which is defined in CISCO-SMI MIB file and CISCO has the authority to assign names to objects anywhere below that name space. Object Identifier(OID) is written as a sequence of sub-identifiers separated with a period, starting at the root and ending at the object.

For in-depth explanation, refer to RFCs for SMI(Structure of Management Information):  RFC1155 (SNMP-SMI) and RFC2578 (SNMPv2-SMI)

Use CISCO OID Translator and Object Tree browser for more insights.

You can also look into MIB files to understand each network/device management objects.
In Linux, you should be able to locate MIB files under /usr/local/share/snmp/mibs
In Windows, you should be able to locate MIB files under %systemroot%\system32

Click here for basic tutorial on SNMP.
Install net-snmp if your system doesn't have snmp commands like snmpwalk, snmpget, snmpbulkget, etc.

snmpwalk is the easiest command to start with.
#snmpwalk -v <version>  -c  <Community_String>  -m ALL  <IP_ADDRESS_or_Domain_Name>   <Object_Name_or_Object_ID>

OPTIONS:
  -v 1|2c|3             specifies SNMP version to use
  -c COMMUNITY          set the community string
  -m MIB[:...]          load given list of MIBs (ALL loads everything)

Example1: To retrieve all SNMP objects under ISO for a network device(myserver.com):
#snmpwalk -v 2c  -c public  -m ALL  myserver.com   .1
or
#snmpwalk -v 2c -c public -m ALL myserver.com  iso

Example2: To retrieve all CISCO specific SNMP objects of a network device(myciscorouter.com) [ Note: For human readable objects, download CISCO specific MIB files and copy those files to /usr/local/share/snmp/mibs ]
#snmpwalk -v 2c  -c public  -m ALL  myciscorouter.com  .1.3.6.1.4.1.9
or
#snmpwalk -v 2c  -c public  -m ALL  myciscorouter.com   cisco

Wednesday, November 21, 2012

How big is IPv6?

IPv6 uses 128-bit addressing allowing 2128 addresses.

Analogy 1: Size based analogy

Say 1 IP address is equivalent to 1 picometer ( 10-12 meter = 0.000000000001 meter )
IPv4 is the size of an ant:  232 picometer = 4.29mm  
IPv6 is ridiculously large: (2128) picometers = 35 Billion light years
Note: 1 light year = 9.4605284 × 1012 kilometers = 5.87849981 × 1012 miles


Analogy 2: Weight based analogy
Say 1 speck of dust weighs 1 microgram
Mass of the Earth = 5.98 x 1027 grams = 5.98 x 1033 microgram
(Ref: http://en.wikipedia.org/wiki/Earth_mass)

Say Earth is made up of the dust particles


Total amount of the dust particles in Earth = 5.98 x 1033 which is equivalent to 2112


Total number of IPv6 Addresses: 2128

IPv6 address space is good enough to assign an IP address to each dust particles in  2(128-112)=216= 65536 planets the size of the earth.



Conclusion:
IPv6 address space allocation looks wasteful but it is so beautiful that you don't have to worry about conserving IP addresses any more as you can get ridiculously huge amount of address space. Now you can focus more on managing network rather than managing network address space itself. With that being said, proper IPv6 address planning is crucial otherwise it can get ugly and become a nightmare.

Wise principle to follow while doing IPv6 Address planning: Forget about IPv4 thinking, like address conservation, subnets, legacy class concepts, subnet masks (simply remember how to use CIDR style notation), etc. 


IPv6 is 128 bits. Make life simple. Break it into two 64 bits. First 64 bits for network and second 64 bits for interface.You can break first 64 network bits into Global Unicast Prefix(48 bits) and Subnet(64 minus 48 = 16 bits).



More yet to come... 

Thursday, March 8, 2012

Shared Line Appearance/Bridged Line Appearance in Asterisk

1.    Design Overview:

When someone calls Boss’ line, it will ring Boss’ as well as Assistants’ phone (Asterisk SLA/conference function and Line Trunking allows this feature).
Assistants can see the presence of their Boss’ line (Presence feature on Polycom phone and Asterisk HINT allows this).  Assistants can pick up the call by pressing the line button. Boss can join the conversation by pressing the line button as well (Barge In function, Asterisk Conference and Line Trunking allows us to do this)
You can simply put a call on hold from one phone and pick it up from another. Also, if multiple phones press the key for the shared extension, they will all be bridged into the same call(Asterisk SLA/conference function allows this feature).

2.    Terminologies:
  • Asterisk Technologies/Channels/Devices: There are various technologies/channels/devices available in Asterisk.
                Local
                SIP
                Agent
                & more ….

           Examples:
                 device=Local/disa@SLA_Outbound
           Defined  Local channel that lands the call in ‘disa’ extension of context [SLA_Outbound] in extensions.conf
  • DISA:  DISA (Direct Inward System Access) allows someone calling in from outside the telephone switch(PBX) to obtain an “internal” system dialtone and dial calls as if from one of the extensions attached to the telephone switch.  Check more @ http://www.voip-info.org/wiki/view/Asterisk+cmd+DISA
  • SLA: Shared Line Appearance
  • BLA: Bridged Line Appearance
  • Station: It is any SIP phone that will be using SLA
  • Trunk:  It is a literal trunk or shared extension that will be appearing on two or more stations
  • SLAStation() : Shared Line Appearance Station application. It should be executed by an SLA station. The argument to this application depends on how the call was initiated. If the phone was just taken off hook, then the argument ‘station’ should be just the station name. If the call was initiated by pressing a line key, then the station name should be preceded by an underscore and the trunk name associated with that line button.
      exten =>20000, n,SLAStation(20000)
      exten => 20000_line1,1,SLAStation(20000_line1)
  •  SLATrunk(): Shared Line Appearance Trunk application. This application takes care of ringing of all the appropriate stations.   

exten => 20000,1,Verbose(1,### Dialing trunk line1)
        same => n,Goto(sla,1)

exten => sla,1,SLATrunk(line1)


3.    Implementation:
  • Check if all the required Asterisk applications are installed properly
SLA application uses two key technologies: Device State Processing and Conferencing. Conferencing uses MeetMe() application. MeetMe() application is offered by app_meetme module. App_meetme module requires DAHDI to be installed (even if you don’t use PRIs).
Warning!!!
You have to load dahdi and dahdi_dummy before you start asterisk. You can check if those are loaded or not.
# lsmod|grep dahdi
dahdi                 210879  0
crc_ccitt               1651  1 dahdi


If you don’t get output like above, you might want to load it manually
#modprobe dahdi
#modprobe dahdi_dummy

Now check if app_meetme module is loaded or not.
*CLI> module show like app_meetme.so
Module                         Description                              Use Count
app_meetme.so                  MeetMe conference bridge                 0
1 modules loaded


[If it says 0 modules loaded, double check if dahdi and dahdi_dummy are loaded successfully or not. You might also get “WARNING[15929]: app_meetme.c:1228 build_conf: Unable to open DAHDI pseudo device” for not having dahdi_dummy]
Check if SLAStation() and SLATrunk() applications are available
*CLI> core show applications like SLA
    -= Matching Asterisk Applications =-
            SLAStation:
              SLATrunk:
    -= 2 Applications Matching =-


  • Asterisk Configuration
You have to understand and edit sla.conf, extensions.conf and sip.conf.

Trunks and Stations are defined in sla.conf. Mapping of devices to trunks and stations are also done here.
Station: It is any SIP phone that will be using SLA
Trunk:  It is a literal trunk or shared extension that will be appearing on two or more stations

#sla.conf
[general]
attemptcallerid=yes

[line1]
type=trunk
device=Local/disa@SLA_Outbound

[line2]
type=trunk
device=Local/disa@SLA_Outbound

[station](!)  ;Template for stations 
type=station
trunk=line1
;trunk=line2

[20000](station)   ;Note:section name do not need to match SIP device name
device=SIP/20000

[20001](station)
device=SIP/20001


Warning!!!
Trunk must be tied up with a device. Otherwise it will crash asterisk.

Here, we defined
•    two trunks [line1] and [line2]
•    two stations [20000] and [20001]   

If you watch very closely on above configuration, you will see that
•    trunk [line1] is tied up with device=Local/disa@SLA_Outbound
•    stations [20000] and [20001] are tied up with  device=SIP/20000
and device=SIP/20001 and will use trunk [line1] as defined in [station](!)  template

In our current scenario, we will not be using trunk [line2] to simplify the demonstration.

You can verify those by executing ‘sla’ commands in asterisk
*CLI> sla show trunks

=============================================================
=== Configured SLA Trunks ===================================
=============================================================
===
=== ---------------------------------------------------------
=== Trunk Name:       line1
=== ==> Device:       Local/disa@SLA_Outbound
=== ==> AutoContext:  (none)
=== ==> RingTimeout:  (none)
=== ==> BargeAllowed: Yes
=== ==> HoldAccess:   Open
=== ==> Stations ...
===    ==> Station name: 20000
===    ==> Station name: 20001
===    ==> Station name: 20002
=== ---------------------------------------------------------
===
=== ---------------------------------------------------------
=== Trunk Name:       line2
=== ==> Device:       Local/disa@SLA_Outbound
=== ==> AutoContext:  (none)
=== ==> RingTimeout:  (none)
=== ==> BargeAllowed: Yes
=== ==> HoldAccess:   Open
=== ==> Stations ...
=== ---------------------------------------------------------
===
=============================================================



*CLI> sla show stations

=============================================================
=== Configured SLA Stations =================================
=============================================================
===
=== ---------------------------------------------------------
=== Station Name:    20000
=== ==> Device:      SIP/20000
=== ==> AutoContext: (none)
=== ==> RingTimeout: (none)
=== ==> RingDelay:   (none)
=== ==> HoldAccess:  Open
=== ==> Trunks ...
===    ==> Trunk Name: line1
===       ==> State:       SLA_TRUNK_STATE_IDLE
===       ==> RingTimeout: (none)
===       ==> RingDelay:   (none)
=== ---------------------------------------------------------
===
=== ---------------------------------------------------------
=== Station Name:    20001
=== ==> Device:      SIP/20001
=== ==> AutoContext: (none)
=== ==> RingTimeout: (none)
=== ==> RingDelay:   (none)
=== ==> HoldAccess:  Open
=== ==> Trunks ...
===    ==> Trunk Name: line1
===       ==> State:       SLA_TRUNK_STATE_IDLE
===       ==> RingTimeout: (none)
===       ==> RingDelay:   (none)
=== ---------------------------------------------------------
===

Asterisk dialplan (extensions.conf) allows to setup extension state hints and extensions that define how calls get into and out of an SLA setup.
#extensions.conf

[SLA_Stations]
exten => 20000,1,Verbose(1,### Incoming Call to extension${EXTEN})
        same => n, Dial(SIP/${EXTEN})

exten => 20000_line1,hint,SLA:20000_line1

exten => 20000_line1,1,SLAStation(20000_line1)) ;This puts the call thru' disa@SLA_Outbound as it forces the call thru' the trunk
    
exten => 20001,1,Verbose(1,### Incoming Call to SLAStation)
        same => n, Dial(SIP/${EXTEN})

exten => _X.,1,Verbose(1,### Incoming Call from ${CALLERID(name)} : ${CALLERID(num)}) 


CUSTOMIZE YOUR DIALPLAN ACCORDING TO YOUR ENVIRONMENT



[SLA_Outbound]
exten => disa,1,DISA(no-password,SLA_Outbound)

exten => _X.,1,Verbose(1,### Incoming Call from ${CALLERID(name)} : ${CALLERID(num)})
CUSTOMIZE YOUR DIALPLAN ACCORDING TO YOUR ENVIRONMENT
[External]
exten => 20000,1,Verbose(1,### Dialing trunk line1)
        same => n, SLATrunk(line1)

exten => _X.,1,Verbose(1,### Incoming Call from ${CALLERID(name)} : ${CALLERID(num)}) 


CUSTOMIZE YOUR DIALPLAN ACCORDING TO YOUR ENVIRONMENT

SIP users are defined in sip.conf. SIP users for SLA stations are assigned [SLA_Stations] context.

#sip.conf
context=External

[SLA-sip-phone](!) ;Template
type=friend
host=dynamic
secret=mysecretpassword
context=SLA_Stations

[20000](SLA-sip-phone)
callerid= "Boss" <20000>
mailbox=20000

[20001](SLA-sip-phone)
callerid= "Secretary" <20001>
mailbox=20001

[sip-phone](!) ;Template
type=friend
host=dynamic
secret=mysecretpassword
context=External

[20002](sip-phone)
callerid= "John Doe" <20002>
mailbox=20002




Here 20000 and 20001 are using SLA-sip-phone template, thus they land in [SLA_Stations] of dialplan
And 20002 is using sip-phone template and it lands in [External] context

  • Polycom phone configuration
For phone with extension 20001
Make sure that directories, buddies and presence features are enabled.
Then define the directory for the phone.

#[MAC-ADDRESS]-directory.xml

   
      
         
         Boss Line1
         20000_line1@mysipserver.phones
         1
         1
      
   


Similar configuration for phone with extension 20000

You can now start testing. Please remember that you have to customize your dialplan according to your environment. Good Luck!


Thursday, February 23, 2012

SIP Load Sharing/Balancing and Failover using DNS SRV records

Note: It is assumed that you know about SIP protocol and you know how to configure SIP clients and SIP servers. [You can also check out my blogs on SIP at http://irockasterisk.blogspot.com/search/label/SIP%20trunk  for more info on SIP clients and SIP server configuration]
 
Brief Introduction on DNS:
DNS(Domain Name System) is a hierarchical distributed naming system for computers, services or any resource connected to the internet or a private network. It translates queries for domain names into IP addresses for the purpose of locating computer services and devices worldwide. (Src:Wikipedia)

In layman term, it maps human-friendly name into IP addresses. For example, it is alot easier to remember www.google.com instead of remebering IP address of the www host of google.com.
DNS server stores the DNS records for a domain name, such as Address(A) records, Name Server(NS) records, Mail Exchanger(MX) records, Service (SRV) records and more. DNS server responds to the DNS queries made by it's clients against its databse.

For more info: http://en.wikipedia.org/wiki/Domain_Name_System

DNS Service(DNS SRV) record - RFC 2782: It is a type of DNS record/entry that specify the location of service available in a domain. It is typically used by clients to locate a service within a domain.

For example:
In Active Directory environment, PCs on domain rely on SRV records to locate domain controllers to authenticate to within their domain.

In SIP environment, SIP clients use SRV records to determine where to send an outgoing call.

Most importantly, DNS SRV records allow you to use domain name rather than full hostname of the server in the SIP address field of the client configuration.

SRV record is written in ZONE file as:

_service._proto.name TTL class SRV priority weight port target


Example:
_sip._udp.rapidtech.phones. 300 IN SRV 0 40 5060 sipserver1.rapidtech.phones.
_sip._udp.rapidtech.phones. 300 IN SRV 0 60 5060 sipserver2.rapidtech.phones.
_sip._udp.rapidtech.phones. 300 IN SRV 1 5 5060 sipserverbackup.rapidtech.phones.



service: name of the service e.g sip

proto: transport protocol of the service e.g tcp or udp

name: domain name that this record belongs to e.g rapidtech.phones

TTL: Time to Live value for this DNS record (Expiry time for the DNS record). Adjust this based on your environment. E.g If you set it to 300 seconds, client will make DNS query to the server every 5 minutes.

class: DNS class. This is always 'IN' here

Priority: Priority for the multiple hosts offering same service. This helps you to define failover serivce hosts. Lower value means more preferred. e.g sipserver1 and sipserver2 have priority 0 thus acts as primary servers and sipserverbackup has priority 1(greater than 0) thus acts as failover server.

Weight: A relative weight for records with the same priority. It is used for load sharing among the servers e.g. sipserver1 and sipserver2  sipserver1 will be used 40% of the time and sipserver2 will be used for 60% of the time.  If all the servers with priority 0 are unavailable, the record with the next highest priority value will be chosen, which is sipserverbackup.rapidtech.phones and it will be used 100% of time as it is not sharing load with another server.

port: TCP or UDP port on which the service is available e.g 5060 for SIP

target: the canonical hostname of the server providing the service e.g sipserver1.rapidtech.phones., sipserver2.rapidtech.phones., sipserverbackup.rapidtech.phones.



Ok great, now how do I implement it? Right!

Implementation:
DNS server:
Here I am going to use BIND/named (Linux based DNS server)
To run your own DNS: Install the bind, bind-devel, bind-utils, and caching-nameserver packages

Master Zone file:  rapidtech.phones

 #vi /var/lib/named/master/rapidtech.phones

$TTL 1800
@               IN SOA          dns1.dnsserver.phones.     root.dns1.dnsserver.phones. (
                                2012022302      ; serial
                                1800                    ; refresh time in seconds
                                600                      ; retry time in seconds
                                1w                        ; expiry time
                                1800 )                  ; minimum TTL

rapidtech.phones.        IN NS           dns1.dnsserver.phones.
sipserver1  IN A            192.168.1.11
sipserver2  IN A            192.168.2.11
NTP            IN A            192.168.1.20
FTP             IN A            192.168.1.21

_sip._udp.rapidtech.phones.   IN SRV 0 40 5060 sipserver1.rapidtech.phones.
_sip._udp.rapidtech.phones.   IN SRV 0 60 5060 sipserver2.rapidtech.phones.
 _sip._udp.rapidtech.phones.  IN SRV 1 5 5060 sipserverbackup.rapidtech.phones.


Define a zone in named.conf
#vi /etc/named.conf

logging {
        channel log_file {
                file "/var/log/bind.log" versions 3 size 100M; 
                severity dynamic;
                print-time yes;
                print-severity yes;
                print-category yes;
        };

        category statistics { log_file; };
        category queries { log_file; };
        category xfer-in { log_file; };
        category xfer-out { log_file; };
        category default { log_file; };
};
#all DNS category activities will be logged in /var/lib/named/var/log/bind.log [ Warning!! it will not log in /var/log/bind.log ]

zone "rapidtech.phones" in {
        allow-transfer { any; };
        file "master/rapidtech.phones";
        type master;
};


Now restart the DNS service

#service named restart 


SIP clients:
SIP Proxy server setting: rapidtech.phones
This setting will allow SIP clients to make call thru' the available SIP servers.

[ Did you notice that just using domain name, you are directed to the available server according to the rules of SRV record? In this case, simply using rapidtech.phones, SIP client will use sipserver1 or sipserver2 or sipserverbackup according to the SRV records rule ]

Good Luck!


Resources:
DNS SOA Header: http://support.microsoft.com/kb/163971
 DNS SRV Record: http://en.wikipedia.org/wiki/SRV_record

Monday, January 30, 2012

Windows not syncing with NTP server

NTP (Network Time Protocol) is widely used for computer clock synchronization in  internet. There are various versions of NTP. Latest version as of Jun 2010 is NTPv4 and is well described in RFC5905. NTP4 is modified to accommodate IPv6 and other improvement has been done over NTPv4.

Are you getting 'Peer Unreachable' when you try to syc with NTP server?
Usually there are various reasons behind the problem.

1. Firewall or port filter : Make sure that default UDP port 123 is open. You can test this real quick just by turning off Firewall.

2. Windows Time Service (w32time) not running on the appropriate mode
There are various modes of operation for Windows Time Service as NTP supports several different packet types.
Normally NTP client sends 'client' mode request packets to a NTP server
NTP server responds back with 'server' mode packet with timing information

By default some windows (esp. XP and earlier) sends 'symmetric active' mode packet instead of 'client' mode request packets. 'symmetric active' mode packets is for NTP's peering feature where a pool of computers(peers) are configured to sync their clocks among each others to agree upon a common 'network time', which then can be supplied to the client.

Usually NTP server drops 'symmetric active' mode packets, unless it is told to do so.

Q: How can I switch to 'client' mode of Windows Time Service?

Ans: You have to change the Windows registry and it can be done easily via command line

 w32tm  /config  /manualpeerlist:ntp.myserver.com,0x8  /syncfromflags:MANUAL

Here, ntp.myserver.com is my NTP server

The valid settings for the mode used with the /manualpeerlist switch include the following:
  • 0x01 - use special poll interval SpecialInterval
  • 0x02 - UseAsFallbackOnly
  • 0x04 - send request as SymmetricActive mode
  • 0x08 - send request as Client mode
The mode that Windows Time uses to send requests is set by the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer

0x8  enables 'client' mode for Windows Time Service
syncfromflags:MANUAL  forces Windows Time Service to use manualpeerlist for the time query. 

Make changes effective immediately
w32tm  /config  /update

To resync manually
w32tm /resync


Additional Tips: 
If you want to sync with time server everyday, you can create a new 'Scheduled Task' under Control Panel --> Scheduled Task to run  'w32tm  /resync' everyday at your specified time.

Good Luck!