Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

changing IP for SV9100 NetLink Connection

zen83

Systems Engineer
Apr 23, 2022
21
SY
Hi All

I have SV9100 connected to the NetLink and linked to the secondary system at the same location and same switch.

I would like to change the IP addresses for both the primary and secondary systems.
In the past, I attempted this on another system and encountered issues such as CPU lock and no response.
Could you please provide guidance on how to change the IP addresses without encountering these problems?
 
Hi All

I have SV9100 connected to the NetLink and linked to the secondary system at the same location and same switch.

I would like to change the IP addresses for both the primary and secondary systems.
In the past, I attempted this on another system and encountered issues such as CPU lock and no response.
Could you please provide guidance on how to change the IP addresses without encountering these problems?
Attached is a Netlink cheat sheet that should walk you through changing IP addresses.
 
Changing IP details on a Netlink is fairly simple.

10-12, update IP details in here, new IP/Gateway etc
84-26, update IP details in here, to ensure your RTP traffic continues routing

This is your base IP information on each system, once you have this setup

51-03 - Update IPs for each other system in your netlink (eg. System 1, put System 2's IP in here, for System 2, put System 1's IP in here)
51-04 - System 1 IP should be present in this field

In theory, this should be all the changes required to change IPs for Netlink, all the other programming should remain the same. so being as you have 2 systems on 1 network, I would assume:

System 1 - 192.168.0.10 - 10-12-09
System 1 - 192.168.0.11 - 84-26-01
System 1 - 192.168.0.20 - 53-01
System 1 - 192.168.0.10 - 54-01-01

System 2 - 192.168.0.20 - 10-12-09
System 2 - 192.168.0.21 - 84-26-01
System 2 - 192.168.0.10 - 53-01
System 2 - 192.168.0.10 - 54-01-01
 
Changing IP details on a Netlink is fairly simple.

10-12, update IP details in here, new IP/Gateway etc
84-26, update IP details in here, to ensure your RTP traffic continues routing

This is your base IP information on each system, once you have this setup

51-03 - Update IPs for each other system in your netlink (eg. System 1, put System 2's IP in here, for System 2, put System 1's IP in here)
51-04 - System 1 IP should be present in this field

In theory, this should be all the changes required to change IPs for Netlink, all the other programming should remain the same. so being as you have 2 systems on 1 network, I would assume:

System 1 - 192.168.0.10 - 10-12-09
System 1 - 192.168.0.11 - 84-26-01
System 1 - 192.168.0.20 - 53-01
System 1 - 192.168.0.10 - 54-01-01

System 2 - 192.168.0.20 - 10-12-09
System 2 - 192.168.0.21 - 84-26-01
System 2 - 192.168.0.10 - 53-01
System 2 - 192.168.0.10 - 54-01-01
Changing IP details on a Netlink is fairly simple.

10-12, update IP details in here, new IP/Gateway etc
84-26, update IP details in here, to ensure your RTP traffic continues routing

This is your base IP information on each system, once you have this setup

51-03 - Update IPs for each other system in your netlink (eg. System 1, put System 2's IP in here, for System 2, put System 1's IP in here)
51-04 - System 1 IP should be present in this field

In theory, this should be all the changes required to change IPs for Netlink, all the other programming should remain the same. so being as you have 2 systems on 1 network, I would assume:

System 1 - 192.168.0.10 - 10-12-09
System 1 - 192.168.0.11 - 84-26-01
System 1 - 192.168.0.20 - 53-01
System 1 - 192.168.0.10 - 54-01-01

System 2 - 192.168.0.20 - 10-12-09
System 2 - 192.168.0.21 - 84-26-01
System 2 - 192.168.0.10 - 53-01
System 2 - 192.168.0.10 - 54-01-01
Thank you, Daniel_RO, for your support.
Did you try that before?
I have some concerns about doing that because the CPU may be locked or unresponsive.

Shall I need to configure the backup using command 90-57 from a handset? This stores a copy of the individual PBX's CPU.
if you wish to 'default' the machine at a later date use command 90-58 to install the database from that time - you can store up to 5 back-ups I believe all stored under the date the backup was saved
 
I had a customer IT change the subnet of the network without any thought towards the devices on that network outside of what was in their control, so yeah, I have tried this before, and had to act quickly to get customer voice services back online.
 

Part and Inventory Search

Sponsor

Back
Top