Hi Sunil, I am not aware of your setup details, but its better to
use static IPs for all the nodes as private IPs, so that when it comes up, it
holds those IPs and you needn't make any changes in DNS. The public IP of nodes
will change after reboot(because of DHCP), but it doesn't make any difference
if you want to make a simple call except that public IP of bono is needed as
you may have to access it from any remote node from SIP agent like
Zoiper,Sipdroid, etc.
So, configure all the nodes local_config as below for a simple call setup(6
nodes + 1 DNS node):
sudo vi /etc/clearwater/local_config
local_ip=10.0.0.173
public_ip=13.127.138.201
public_hostname=ip-10-0-0-173
etcd_cluster="10.0.0.83,10.0.0.196,10.0.0.249,10.0.0.225,10.0.0.195,10.0.0.173"
Above, local_ip is private IP (you can have static), public IP can be any
thing. etcd_cluster should have private IPs(static IPs)
Also, if you are using bind9 DNS server then, you can configure db.domain (e.g.
db.nags.hd) file as below(configure private IPs(static):
$TTL 5m ; Default TTL
; SOA, NS and A record for DNS server itself
@ 3600 IN SOA ns admin ( 2014010800 ; Serial
3600 ; Refresh
3600 ; Retry
3600 ; Expire
300 ) ; Minimum TTL
@ 3600 IN NS ns
ns 3600 IN A 10.0.0.178 ; IPv4 address of BIND server
;ns 3600 IN AAAA 1::1 ; IPv6 address of BIND server
; bono
; ====
;
; Per-node records - not required to have both IPv4 and IPv6 records
bono-1 IN A 10.0.0.196
;bono-2 IN A 2.0.0.2
;bono-1 IN AAAA 2::1
;bono-2 IN AAAA 2::2
;
; Cluster A and AAAA records - UEs that don't support RFC 3263 will simply
; resolve the A or AAAA records and pick randomly from this set of addresses.
@ IN A 10.0.0.196
;@ IN A 2.0.0.2
;@ IN AAAA 2::1
;@ IN AAAA 2::2
;
; NAPTR and SRV records - these indicate a preference for TCP and then resolve
; to port 5060 on the per-node records defined above.
@ IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp
@ IN NAPTR 2 1 "S" "SIP+D2U" "" _sip._udp
_sip._tcp IN SRV 0 0 5060 bono-1
;_sip._tcp IN SRV 0 0 5060 bono-2
_sip._udp IN SRV 0 0 5060 bono-1
;_sip._udp IN SRV 0 0 5060 bono-2
; sprout
; ======
;
; Per-node records - not required to have both IPv4 and IPv6 records
sprout-1 IN A 10.0.0.249
;sprout-2 IN A 3.0.0.2
;sprout-1 IN AAAA 3::1
;sprout-2 IN AAAA 3::2
;
; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or AAAA records and pick randomly from this set of addresses.
sprout IN A 10.0.0.249
;sprout IN A 3.0.0.2
;sprout IN AAAA 3::1
;sprout IN AAAA 3::2
;
; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or AAAA records and pick randomly from this set of addresses.
scscf.sprout IN A 10.0.0.249
;scscf.sprout IN A 3.0.0.2
;scscf.sprout IN AAAA 3::1
;scscf.sprout IN AAAA 3::2
;
; NAPTR and SRV records - these indicate TCP support only and then resolve
; to port 5054 on the per-node records defined above.
sprout IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.sprout
_sip._tcp.sprout IN SRV 0 0 5054 sprout-1
;_sip._tcp.sprout IN SRV 0 0 5054 sprout-2
;
; NAPTR and SRV records for S-CSCF - these indicate TCP support only and
; then resolve to port 5054 on the per-node records defined above.
scscf.sprout IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.scscf.sprout
_sip._tcp.scscf.sprout IN SRV 0 0 5054 sprout-1
;_sip._tcp.scscf.sprout IN SRV 0 0 5054 sprout-2
;
; Cluster A and AAAA records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or AAAA records and pick randomly from this set of addresses.
icscf.sprout IN A 10.0.0.249
;icscf.sprout IN A 3.0.0.2
;icscf.sprout IN AAAA 3::1
;icscf.sprout IN AAAA 3::2
;
; NAPTR and SRV records for I-CSCF - these indicate TCP support only and
; then resolve to port 5052 on the per-node records defined above.
icscf.sprout IN NAPTR 1 1 "S" "SIP+D2T" "" _sip._tcp.icscf.sprout
_sip._tcp.icscf.sprout IN SRV 0 0 5052 sprout-1
;_sip._tcp.icscf.sprout IN SRV 0 0 5052 sprout-2
; dime
; =========
;
; Per-node records - not required to have both IPv4 and IPv6 records
dime-1 IN A 10.0.0.195
;dime-2 IN A 4.0.0.2
;dime-1 IN AAAA 4::1
;dime-2 IN AAAA 4::2
;
; Cluster A and AAAA records - sprout, bono and ellis pick randomly from these.
hs IN A 10.0.0.195
;hs IN A 4.0.0.2
;hs IN AAAA 4::1
;hs IN AAAA 4::2
ralf IN A 10.0.0.195
;ralf IN A 4.0.0.2
;ralf IN AAAA 4::1
;ralf IN AAAA 4::2
;
; (No need for NAPTR or SRV records as dime doesn't handle SIP traffic.)
; homer
; =====
;
; Per-node records - not required to have both IPv4 and IPv6 records
homer-1 IN A 10.0.0.225
;homer-2 IN A 5.0.0.2
;homer-1 IN AAAA 5::1
;homer-2 IN AAAA 5::2
;
; Cluster A and AAAA records - sprout picks randomly from these.
homer IN A 10.0.0.225
;homer IN A 5.0.0.2
;homer IN AAAA 5::1
;homer IN AAAA 5::2
;
; (No need for NAPTR or SRV records as homer doesn't handle SIP traffic.)
; vellum
; =====
;
; Per-node records - not required to have both IPv4 and IPv6 records
vellum-1 IN A 10.0.0.173
;vellum-2 IN A 6.0.0.2
;vellum-1 IN AAAA 6::1
;vellum-2 IN AAAA 6::2
;
; Cluster A and AAAA records - sprout, homer and dime pick randomly from these.
vellum IN A 10.0.0.173
;vellum IN A 6.0.0.2
;vellum IN AAAA 6::1
;vellum IN AAAA 6::2
;
; (No need for NAPTR or SRV records as vellum doesn't handle SIP traffic.)
; ellis
; =====
;
; ellis is not clustered, so there's only ever one node.
;
; Per-node record - not required to have both IPv4 and IPv6 records
ellis-1 IN A 10.0.0.83
;ellis-1 IN AAAA 7::1
;
; "Cluster"/access A and AAAA record
ellis IN A 10.0.0.83
;ellis IN AAAA 7::1
This will make your cluster reboot safe.
Thanks-Nagu
On Friday, 6 April, 2018, 6:07:24 PM IST, tahir Masood
<[email protected]> wrote:
Assign IP's again and update the hosts/DNS.
Regards,
Tahir
On Fri, Apr 6, 2018 at 11:15 AM, Sunil Kumar <[email protected]> wrote:
Hi all,I have installed the clearwater using manual installation. I used
briidge adapter and ip is assigned by DHCP. Some how the machine is power off
and all the clearwater nodes are aborted (power off), in result some nodes have
lost their ip and some of them are interchange (IPs). Do i need to assign IP
manually same as earlier? everything is lost that is not connected. What I need
to do please let me know.
Thanks,sunil
______________________________ _________________
Clearwater mailing list
Clearwater@lists. projectclearwater.org
http://lists. projectclearwater.org/mailman/ listinfo/clearwater_lists.
projectclearwater.org
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
