Re: [Project Clearwater] Lost the IPs of clearwater node

[Nagendra Kumar]

Hi Sunil,    You can configure one of your VM interface as 
"Host-only Adaptor" option and configure static IP address as below(example in 
Oracle VM VIrtualBox Manager):
vi /etc/network/interfaces# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
   address 192.168.56.100
   netmask 255.255.255.0
   network 192.168.56.1
   gateway 192.168.56.1
   dns-nameservers 8.8.8.8

When you reboot the machine, it will always have this IP address, use this IP 
address as private address on your nodes.
Thanks-Nagu
 

On Tuesday, 10 April, 2018, 4:30:45 PM IST, Sunil Kumar 
 wrote:  
 
 Hi,Now I am using NAT mode for networking, but i have some dooubts:1) Should 
public_ip is the ip of the host on which virtualbox is installed?2) Should all 
nodes having the same public_ip in NAT mode?
3) Instead of doing port forwarding for particular node, I have left blank host 
ip field that means it is opens for world, or do I need to open for particular 
node?
Thanks,Sunil  ___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Lost the IPs of clearwater node

[Sunil Kumar]

Hi,
thanks for replying,
How can i find the ip of interface of the vm?

one more thing, after poweroff ,the ip of vm is changed, so in which places
i need to update the changed IP. I have update in following places still it
did not works:

/etc/clearwater/local_config in all nodes
/etc/hosts
/etc/bind/db.ims.com

after that i stop the service like sudo service ellis etc.

where more do i need to update?

thanks,
sunil


On Tue, Apr 10, 2018 at 7:34 PM, tahir Masood 
wrote:

> No the public ip is the one which is assigned on the interface of that VM.
> No they will have different ip's public ip is only required on bono
> You need to assign that public ip to bono if you want it to be publicly
> accessible
>
> On Tue, 10 Apr 2018, 4:02 PM Sunil Kumar,  wrote:
>
>> Hi,
>> Now I am using NAT mode for networking, but i have some dooubts:
>> 1) Should public_ip is the ip of the host on which virtualbox is
>> installed?
>> 2) Should all nodes having the same public_ip in NAT mode?
>>
>> 3) Instead of doing port forwarding for particular node, I have left
>> blank host ip field that means it is opens for world, or do I need to open
>> for particular node?
>>
>> Thanks,
>> Sunil
>> ___
>> Clearwater mailing list
>> Clearwater@lists.projectclearwater.org
>> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.
>> projectclearwater.org
>>
>
> ___
> Clearwater mailing list
> Clearwater@lists.projectclearwater.org
> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.
> projectclearwater.org
>
>
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Lost the IPs of clearwater node

[tahir Masood]

No the public ip is the one which is assigned on the interface of that VM.
No they will have different ip's public ip is only required on bono
You need to assign that public ip to bono if you want it to be publicly
accessible

On Tue, 10 Apr 2018, 4:02 PM Sunil Kumar,  wrote:

> Hi,
> Now I am using NAT mode for networking, but i have some dooubts:
> 1) Should public_ip is the ip of the host on which virtualbox is installed?
> 2) Should all nodes having the same public_ip in NAT mode?
>
> 3) Instead of doing port forwarding for particular node, I have left blank
> host ip field that means it is opens for world, or do I need to open for
> particular node?
>
> Thanks,
> Sunil
> ___
> Clearwater mailing list
> Clearwater@lists.projectclearwater.org
>
> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
>
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Lost the IPs of clearwater node

[Sunil Kumar]

Hi,
Now I am using NAT mode for networking, but i have some dooubts:
1) Should public_ip is the ip of the host on which virtualbox is installed?
2) Should all nodes having the same public_ip in NAT mode?

3) Instead of doing port forwarding for particular node, I have left blank
host ip field that means it is opens for world, or do I need to open for
particular node?

Thanks,
Sunil
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Re: [Project Clearwater] Lost the IPs of clearwater node

[Nagendra Kumar]

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  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   2::1
;bono-2 IN   2::2
;
; Cluster A and  records - UEs that don't support RFC 3263 will simply
; resolve the A or  records and pick randomly from this set of addresses.
@  IN A 10.0.0.196
;@  IN A 2.0.0.2
;@  IN   2::1
;@  IN   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   3::1
;sprout-2   IN   3::2
;
; Cluster A and  records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or  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   3::1
;sprout IN   3::2
;
; Cluster A and  records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or  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   3::1
;scscf.sprout   IN   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  records - P-CSCFs that don't support RFC 3263 will simply
; resolve the A or  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   3::1
;icscf.sprout   IN   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   4::1
;dime-2

Re: [Project Clearwater] Lost the IPs of clearwater node

[tahir Masood]

Assign IP's again and update the hosts/DNS.

Regards,

Tahir

On Fri, Apr 6, 2018 at 11:15 AM, Sunil Kumar  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
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org