Changing IP address PBX to CMS remote link

[Esmerelda]

I have been struggling with the seemingly simple task of changing the IP address for our Spokane CMS Link to our CMS server located in our OB2 building in another city. I believe that I understand the process quite well, but, have not been able to successfully make the change. The new link just simply will not come up. Changing back was a bit of a challenge, too, until I realized that it will come back if I busy, reset, and release the CLAN board. Also, it appeared that the CMS hosts file needs to have the link not being used "commented out". Our customer has a dual connection set up, and, I am able to ping and traceroute from the CMS to the CLAN when in the new IP configuration (xxx.xxx.200.241/24/gateway .1).

Status on the link looks good. The only thing that looks out of place is that it shows "0" (zero) for the number of channels. This should be "1".

I believe that I may need to add a route:
route add host xxx.xxx.200.241 198.238.127.203 -hme0:1
but, I'm concerned, because I haven't seen that solution mentioned anywhere in IP address posts in this forum. I guess I just need some confidence support.

For security reasons, the first two octets have been "x"d out. ***************************************************************************************************
This IP-Route shows the destination node as "cms", which is the OB2 CMS server.
The Gateway is shown as "ethernet", which is our CLAN:

Route Destination Gateway/ C-LAN Metric/ Accepted
Number Node Subnet Mask Port Network Bits by C-LAN
1 cms ethernet 02A1517 0 accepted
255.255.255.0 24

****************************************************************************************************
IP NODE NAMES
Name IP Address
CLAN-YAK-04C20 xxx.xxx.15 .31
CLAN2 xxx.xxx.247.220
CLAN2-YAK-04C14 xxx.xxx.15 .32
Clan-a3 xxx.xxx.247.222
IP-Ann.-02B15 xxx.xxx.247.221
Telecount xxx.xxx.118.6
VAL-YAK-04C15 xxx.xxx.15 .33
cms xxx.xxx.127.203 (this is the CMS in OB2)
default 0 .0 .0 .0
ethernet xxx.xxx.247.219 (new is xxx.xxx.247.241....this is the CLAN)
gateway xxx.xxx.247.217 (new is xxx.xxx.200.1)
printer xxx.xxx.250.64

*******************************************************************************************************
IP INTERFACES
Net
ON Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn VLAN
y C-LAN 02A15 TN799 D ethernet 255.255.255.248 xxx.xxx.247.217 5 n (new is xxx.xxx.200.1/24)
y C-LAN 02B03 TN799 D CLAN2 255.255.255.248 xxx.xxx.247.217 4 n
y VAL 02B15 TN2501 IP-Ann.-02B15 255.255.255.248 xxx.xxx.247.217 1
y C-LAN 04C20 TN799 D CLAN-YAK-04C20 255.255.255.0 xxx.xxx.15 .1 2 n
y C-LAN 01D12 TN799 D Clan-a3 255.255.255.248 xxx.xxx.247.217 1 n
y C-LAN 04C14 TN799 D CLAN2-YAK-04C14 255.255.255.0 xxx.xxx.15 .1 2 n
y VAL 04C15 TN2501 VAL-YAK-04C15 255.255.255.0 xxx.xxx.15 .1 3

****************************************************************************************
PROCESSOR CHANNEL ASSIGNMENT
Proc Gtwy Interface Destination Session Mach
Chan Enable Appl. To Mode Link/Chan Node Port Local/Remote ID
1: n 0
2: n 0
3: n 0
4: n 0
5: n 0
6: n 0
7: n 0
8: n 0
9: n 0
10: y mis s 1 5001 cms 0 1 1
**********************************************************************************************************
Data Extension: 1989 Name: Ethernet LAN Data Module
Type: ethernet
Port: 02A1517
Link: 1
*********************************************************************************************************
CMS Hosts file: Changing the comment from the old CLAN Address to the new.
(Presently this shows the CMS using the old IP address for this link):

xxx.xxx.211.195 switch1 # Clan Link to Acd-1
#xxx.xxx.200.241 spokanecms.dshs.wa.gov # Clan Link to Acd-2 (new with DNS)
#xxx.xxx.200.241 switch2 # Clan Link to Acd-2 (new)
xxx.xxx.247.219 switch2 # Clan Link to Acd-2
xxx.xxx.211.196 switch3 # Clan Link to Acd-3
xxx.xxx.216.243 switch4 # Clan Link to Acd-4
xxx.xxx.207.244 switch5 # Clan Link to Acd-5
xxx.xxx.196.29 switch6 # Clan Link to Acd-6
xxx.xxx.207.247 switch7 # Clan Link to Acd-7
**********************************************************************************************************

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
switch4 r3sowwa_1 UH 1 190 hme0
switch2 r3sowwa_1 UH 1 192 hme0
switch6 r3sowwa_1 UH 1 190 hme0
switch5 r3sowwa_1 UH 1 192 hme0
switch7 r3sowwa_1 UH 1 191 hme0
switch1 r3sowwa_1 UH 1 190 hme0
switch3 r3sowwa_1 UH 1 190 hme0
xxx.xxx.127.200 r3sowwa_1 U 1 0 hme0
xxx.xxx.211.176 r3sowwa U 1 385 eri0
224.0.0.0 r3sowwa U 1 0 eri0
default router UG 1 7417

**********************************************************************

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
xxx.xxx.216.243 xxx.xxx.127.203 UH 1 166 hme0
xxx.xxx.247.219 xxx.xxx.127.203 UH 1 168 hme0
xxx.xxx.196.29 xxx.xxx.127.203 UH 1 166 hme0
xxx.xxx.207.244 xxx.xxx.127.203 UH 1 168 hme0
xxx.xxx.207.247 xxx.xxx.127.203 UH 1 167 hme0
xxx.xxx.211.195 xxx.xxx.127.203 UH 1 166 hme0
xxx.xxx.211.196 xxx.xxx.127.203 UH 1 166 hme0
xxx.xxx.127.200 xxx.xxx.127.203 U 1 0 hme0
xxx.xxx.211.176 xxx.xxx.211.183 U 1 335 eri0
224.0.0.0 xxx.xxx.211.183 U 1 0 eri0
default xxx.xxx.211.177 UG 1 7011
127.0.0.1 127.0.0.1 UH 11 113 lo0
*******************************************************************
r3sowwa# route get 198.239.247.219
route to: switch2
destination: switch2
mask: 255.255.255.255
interface: hme0
flags: <UP,HOST,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire
0 0 0 0 0 0 1500 0

 

[wildcard100001]

My first thought is your firewall, if you have one in the mix... allows pings but needs a rule for the new ip address???


Thanks,

Wildcard

 

[Esmerelda]

Based on what I know about the trust environment between the two networks, I'm inclined to think that it isn't a firewall issue. But, I can sure bring it up. Also, traceroute works both directions, and, the link is up and connected. THere are no alarms or errors. The only difference I see when I status the link is that the channels: = 0, instead of 1. The only thing I could think of was to add the route to the routing table, but, I'm confused as to why nobody has mentioned it in any of the previous threads.

 

[wildcard100001]

I would say add it... you could always remove it...

Thanks,

Wildcard

 

[Esmerelda]

Will do. Thanks.

 

[Esmerelda]

It didn't work..it appears that the routing table is dynamically populated. When it was down, the whole thing went away, and, when I cut it back, it came back. I'm out of tricks, and, will ask for professional help (in more ways than one!).

 

[Esmerelda]

OK, the problem has been solved. It was in the routing table. I had to remove the route, and, add it back in, in order for the system to rebuilt the routing table correctly:

94 route delete host switch2 r3sowwa_1
95 route add host switch2 r3sowwa_1 0

switch2 is the name of the ACD link
r3sowwa_1 is the name of the NIC interface
0 is the metric, and, must be used when adding a route

I'm so happy to have finally resolved this.

 

[RageCEO]

Sorry I did not see your posts before, if you run into any similar issues ping me directly.

robert@ragecommunication.com