Changing the APESU IP address

[jschnarkey]

I have recently moved an IPDA to a new subnet and am having some difficulty getting the APE to connect.
Dis-apesu shows the new iP address but no connection.
The IPDA shelf is on line with new addressing. STMI's are good. Only issue is APE not acting nicely.
I changed the IP addresses in the NCUI card with a serial cable and changed also in cha-apsu:21;
see below,
CURRENT SYSTEM TIME : 10-30-2015 15:23:23 |
+------------------------------------------------------------------------------+

+------------------------------------------------------------------------------+
| CC-AP: 21 IP ADDRESS: 10 .12 .1 .115 |
+------------------------------------------------------------------------------+
+------------------------------------------------------------------------------+
| AP EMERGENCY GROUP: 21 CC-AP: 21 NAME: CENTER DRIVE |
| THRSHLD: 100 SBMODE: AUTO |
| STABLE: 10 MIN SBBEGIN: 0 H SBENDE: 23 H SBOFFSET: 0 MIN |
+------------------------------------------------------------------------------+
| AP: 21 AP EMERGENCY GROUP: 21 CC-AP: 21 WEIGHT: 100 SWMODE: GROUP |
| CONTROL-UNIT: HOST-CC SIGNAL-PATH: LAN |
| LAST RECORDED CONNECTION STATUS CHANGE: |
| |
| HOST-CC: CONNECTED: YES CONNECTED SINCE : 2015-10-29 15:03 |
| CC-AP: CONNECTED: NO DISCONNECTED SINCE : 2015-10-22 14:58 |
+------------------------------------------------------------------------------+

REGEN-APESU:21;
H500: AMO APESU STARTED
ADD-APESUATA=CCAP,CCAPNO=21,IPADDR=10.12.1.115;
ADD-APESUATA=APEGRP,EGRPNO=21,CCAPNO=21,THRSHLD=100,SBMODE="AUTO",
NAME="CENTER DRIVE ",STABLE=10,SBBEGIN=0,SBEND=23,SBOFFSET=0;
ADD-APESUATA=AP,APNO=21,EGRPNO=21,WEIGHT=100,SWMODE="GROUP";

AMO-APESU-111 CONFIGURATION OF AP EMERGENCY DATA

 

[sbcsu]

Hi,
You also need to go to the actual APESU itself, log on via Atlantic and change the 'Customer LAN' IP address in the UW7

 

[sbcsu]

(That is the actual DSCXL Processor on the right hand side in the separate unit of the APESU)

 

[jschnarkey]

Atlantic...192.0.2.3 or 5? cross connect cable, comwin, etc...?

 

[sbcsu]

Use a normal LAN cable, set your Laptop to be 192.0.2.99 / 255.255.255.0
Connect to either the Service Port or Atlantic LAN port
Ping 192.0.2.5
Log on to 192.0.2.5 using Internet Explorer
If not already prepared then go through the 'Client Preparation' on the main page.
If that has completed successfully then log on to the UW7
Go to
Base Administration
Unix Base Administration
LAN Card
Delete the configured IP address and add in the new IP address/subnet mask & Broadcast address
Click on Routes
and change the default router
You might also need to change some addresses in the Firewall if used.

You will need to reset the UW7 for the address to go active.
To reset go to 'shutdown' and click on 'reboot'

 

[donb01]

You also need to make sure the "CCC" IP address in the NCUI is still the IP of it's associated APE processor. There would be a CCA in a simplex (one) processor system, and CCB would be the second processor in a duplex system. CCC is usually the IP of the APE - not the Assistant IP; I am stretching my mind, but I know it is different.



Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

Thanks Don, yes that would have to be added in to the NCUI card of the APESU so that in the event of not being able to contact the main processor it would know to contact the local backup APESU processor

 

[jschnarkey]

Yes, I have the NCUI all programmed. Addresses there look good.
I have the correct address in UCSU
APRT:apnet looks good
apesu:21 looks good.
I have been in portal in the APE and changed what I saw there in system and went to maintenance and reboot it.
And Viola!

I now have moved an IPDA and APE with success, not to mention the STMI's. I'll do it a few more times before it gets set in it's new permanent location. This was all just practice and familiarization. I may never get an IPDA to play with any time soon again.
You guys are wonderful.
My only remaining point is that the APE processor still has the old customer address when I toggle through the front panel little window black button, V7.
+------------------------------------------------------------------------------+
| CURRENT SYSTEM TIME : 11-02-2015 12:22:30 |
+------------------------------------------------------------------------------+

+------------------------------------------------------------------------------+
| CC-AP: 21 IP ADDRESS: 10 .12 .1 .115 |
+------------------------------------------------------------------------------+
+------------------------------------------------------------------------------+
| AP EMERGENCY GROUP: 21 CC-AP: 21 NAME: CENTER DRIVE |
| THRSHLD: 100 SBMODE: AUTO |
| STABLE: 10 MIN SBBEGIN: 0 H SBENDE: 23 H SBOFFSET: 0 MIN |
+------------------------------------------------------------------------------+
| AP: 21 AP EMERGENCY GROUP: 21 CC-AP: 21 WEIGHT: 100 SWMODE: GROUP |
| CONTROL-UNIT: HOST-CC SIGNAL-PATH: LAN |
| LAST RECORDED CONNECTION STATUS CHANGE: |
| |
| HOST-CC: CONNECTED: YES CONNECTED SINCE : 2015-10-29 15:03 |
| CC-AP: CONNECTED: YES CONNECTED SINCE : 2015-11-02 12:20 |
+------------------------------------------------------------------------------+

 

[sbcsu]

Didn't know it was V6 or V7
You probably need to go back into the 192.0.2.5
Get into the Portal there and ensure that the CCC / APESU address is set correctly there as well.
That should change the front panel window - again only available on V6/V7

 

[jschnarkey]

Yea, sorry. I did not mention that. It all seems to be working.
Later this week I'll change all the addresses again. See how fast I can do it and bring it back up.
Thanks guys.

 

[jschnarkey]

Ok, I'll admit to not doing quite well with the move. I cannot get the Apsu to connect in it's new subnet.
This is V7. Let me know what outputs you would like to see and what I should be looking at.
Jake

 

[donb01]

Things I'll throw out there -

Is your new subnet set up on a VLAN that can communicate with all your other VOIP equipment??

Compare the port settings on the ethernet switch you were previously plugged into to the port settings on the one you are plugged in now. Look at DHCP and other settings that might need to be changed. All of my switch ports that have "VOIP Equipment" plugged into them have to have different port configurations on the network than the ports that phones and stuff are plugged into. It is also best to set all port settings to fixed 100Mbps rather than autonegiotiate for all "VOIP Equipment" - at least that has been the recommendation in the past.

What are the firewall settings at the previous location compared to the new location? Are there any differences?

There's a start. If everything was working right before and you didn't make any typos or forget to save your config changes then I would start with a difference in network settings.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

Make up a list of IP addresses if not already done.

Assistant on Main Site
Assistant on APESU
Customer LAN on APESU (eth0)

Unplug eth0 from APESU
Setup Laptop using eth0 IP address

Ping to Assistant on Main Site

From Main Site Ping to Laptop

If successful then APESU backups should work.

The Transferring task is in two steps

Setup Main Site to transfer to itself
Setup APESU Processor to get backup from Main Site

 

[jschnarkey]

I will try all of this but..
The shelf is alive and well on the new subnet. APE not Connected though. I have phones built on two STMI's, 4 SLMO's and a SLMA. I have double checked switch port vlan settings.
The subnet and all routing is good. Telephony Vlan and phone vlans alive and well.
I think my problem is in programming somewhere but I feel I am going in circles trying to find it. I am not at the site right now but can be in a few hours to get NCUI and APE configs directly from them.
Another set of eyes and some experience is always of great help and very welcome.

IP addresses would be
10.18.0.0/26 255.255.255.192 network
10.18.0.1 - NCUI4
10.18.0.2 - tap
10.18.0.3 - APE
10.18.0.4 - Portal
10.18.0.5 - Assistant
10.18.0.6 - STMI
10.18.0.7 - STMI


BCSU:
LTG 1 LTU 21 SRCGRP 21 ALARMNO-LTU 0
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
1 | Q2226-X200 DIUT2-T1 3 0| | Q2226-X200 | 1 -07 - | READY
2 | Q2327-X100 TMANI 0| | Q2327-X100 | 1 -11 - | READY
3 | Q2168-X SLMO24 1 0| | Q2168-X | 1 -11 - | READY
4 | Q2168-X SLMO24 1 0| | Q2168-X | 1 -11 - | READY
5 | Q2324-X500 STMI4 1 0| | Q2324-X500 | 1 -11 - | READY
+--------------------------------+-+------------+------------+------------
| IP ADDRESS : 10. 18. 0. 6 B-CHANNELS : 60 BCHLCNT : 60
| IP MODE : IPV4 DHCP V4 : NO DHCP V6 : NO
| BLOCK NO : 3 PRERESERVED LINES ASSIGNED : NO
| 1. FUNCT : HG3530 120 LINES B-CHANNELS : 60 BCHLCNT : 60
+--------------------------------+-+------------+------------+------------
6 | Q2324-X NCUI4 1 0| | Q2324-X | 1 -13 - | READY
+--------------------------------+-+------------+------------+------------
| IP ADDRESS : 10. 18. 0. 1 B-CHANNELS : 60 BCHLCNT : 50
| IP MODE : IPV4 DHCP V4 : NO DHCP V6 : NO
+--------------------------------+-+------------+------------+------------
7 | Q2324-X500 STMI4 1 0| | Q2324-X500 | 1 -11 - | READY
+--------------------------------+-+------------+------------+------------
| IP ADDRESS : 10. 18. 0. 7 B-CHANNELS : 60 BCHLCNT : 60
| IP MODE : IPV4 DHCP V4 : NO DHCP V6 : NO
| BLOCK NO : 3 PRERESERVED LINES ASSIGNED : NO
| 1. FUNCT : HG3530 120 LINES B-CHANNELS : 60 BCHLCNT : 60
+--------------------------------+-+------------+------------+------------
8 | Q2168-X SLMO24 1 0| | Q2168-X | 1 -11 - | READY
9 | Q2168-X SLMO24 1 0| | Q2168-X | 1 -11 - | READY
10 | Q2225-X SLMAE 0| | Q2225-X | 1 -08 - | READY

+----+----+---------------------------+-+------------+------------+--------+
| NO SECURITY STATUS AVAILABLE, SINCE FEATURE SPE IS NOT ACTIVATED |
+---------+----------------------------------------------------------------+
AMO-BCSU -111 BOARD CONFIGURATION, SWITCHING UNIT
all good here.

APRT:apnet;

DIS-APRT:APNET;
H500: AMO APRT STARTED
+------+-------------------+-------------------+-------------------|
| LTU | APIPADDR | NETMASK | TAIPADDR |
+------+-------------------+-------------------+-------------------|
| 17 | 10 .12 .1 .8 | 255.255.255.0 | 10 .12 .1 .11 |
| 18 | 10 .12 .1 .13 | 255.255.255.0 | 10 .12 .1 .14 |
| 19 | 10 .12 .1 .16 | 255.255.255.0 | 10 .12 .1 .17 |
| 20 | 10 .12 .1 .18 | 255.255.255.0 | 10 .12 .1 .19 |
| 21 | 10 .18 .0 .1 | 255.255.255.192 | 10 .18 .0 .2
| 22 | 192.168.0 .200 | 255.255.255.0 | 0 .0 .0 .0 |
+------+-------------------+-------------------+-------------------|

21 looks good here.

UCSU:

+---------+-------------------+---------+--------------+----------+--------+
|AP 1.21|ADDED |READY |Q2324-X |AP37009 |AP37009 |
| +-------------------+---------+--------------+----------+--------+
| |APNW 007 CENTER DRIVE 21 |
| |PHONE: FAX: |
| |010.011.001.126 010.018.000.062 60 50 NO LAN |
| | IPV4 NO NO AP REDUNDANCY TO AP |
| | NO HOST-CC 0 0 |
| |K HSRTCP |
+---------+-------------------+---------+--------------+----------+--------+
Looks good here.

APESU:

| CC-AP: 21 IP ADDRESS: 10 .18 .0 .3 |
+------------------------------------------------------------------------------+
+------------------------------------------------------------------------------+
| AP EMERGENCY GROUP: 21 CC-AP: 21 NAME: CENTER DRIVE |
| THRSHLD: 100 SBMODE: AUTO |
| STABLE: 10 MIN SBBEGIN: 0 H SBENDE: 23 H SBOFFSET: 0 MIN |
+------------------------------------------------------------------------------+
| AP: 21 AP EMERGENCY GROUP: 21 CC-AP: 21 WEIGHT: 100 SWMODE: GROUP |
| CONTROL-UNIT: HOST-CC SIGNAL-PATH: LAN |
| LAST RECORDED CONNECTION STATUS CHANGE: |
| |
| HOST-CC: CONNECTED: YES CONNECTED SINCE : 2016-01-22 07:42 |
| CC-AP: CONNECTED: NO DISCONNECTED SINCE : 2015-12-23 08:12 |
+------------------------------------------------------------------------------+

Proper IP here.