Avaya G350 - S8300 - IA770 VM ~ IP address Change 2

[HawkesNest]

I'm a Lan Admin Cisco guy and this phone system is all new to me. We are changing all of our IP address subnet ranges and I need some help with changing the IP addresses on the following.

We have a standalone Avaya G350 - S8300 - IA770 VM system that is currently connected to the network for admin access. each of the Avaya G350 - S8300 - IA770 VM currently has an IP address in the same subnet. I have the usernames and passwords for both the G350 and the S8300 and can get to the web interfaces on both. After loading the right version of Java, I can also get to the IA770, but it just asks for SNMP v1 or v3 password info that I don't have. The only place I have found ip information that I could possibly try to change so far is via the S8300 web interface.

Since this is my first experience with this equipment, I need some very detailed help as to how to change the IP addresses for these three components so that it can be successfully properly done. I can also go to and access the console port if needed to aid in making the changes. I don't have access to dialing in via the modem.

If versions or other info is needed for helping with this, let me know. Thanks a bunch.

Here is 3 photos of the equipment

http://s485.photobucket.com/albums/rr217/hawkesnest/Avaya/

If versions or other info is needed for helping with this, let me know. Thanks a bunch.

 

[wleong56]

Ask your voice team to look at the trunk group connected to the IA770...

ask them to do list trunk and look for the signalling group connect the Communication Manager and the IA770.
In the signaling group xx, there is a field located to mid way on the right called: Far-end Node Name: xxxxx
where xxx is the node name...
Take note of that node name.
Then ask them to display (or change) display node-names audix and change the IP address.
I am sure you will find that it is not what you have changed it. The Install Wizard does not take care of this. I hope your voice team will know how to backout the translation and change this to the new IP addess. If not let me know.

Below is AN EXAMPLE of my signaling group 99, connecting CM and AUDIX.
display signaling-group 99 Page 1 of 2
SIGNALING GROUP

Group Number: 99 Group Type: h.323
Remote Office? n Max number of NCA TSC: 10
SBS? n Max number of CA TSC: 10
IP Video? n Trunk Group for NCA TSC: 99
Trunk Group for Channel Selection: 99
TSC Supplementary Service Protocol: b
T303 Timer(sec): 10
H.245 DTMF Signal Tone Duration(msec):
Near-end Node Name: procr Far-end Node Name: xxxxx
Near-end Listen Port: 1720 Far-end Listen Port: 1720
Far-end Network Region: 1
LRQ Required? n Calls Share IP Signaling Connection? y
RRQ Required? n
Bypass If IP Threshold Exceeded? n
H.235 Annex H Required? n
DTMF over IP: out-of-band Direct IP-IP Audio Connections? n
Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n
Enable Layer 3 Test? n Interworking Message: PROGress
DCP/Analog Bearer Capability: 3.1kHz

 

[wleong56]

read the above and then this...

To answer your comment...
I'm not sure where to look to find out what isn't working right after the IP address change to these three components of the system. The proper default gateway and subnet mask was also used when manking the IP address changes via the Installation Wizard.

G350... SSH or telnet to your S350 (one using the root login and password)
when you get in... do a show run
This should be familiar to you.
If you want to activate telnet... do a ip telnet
and then a copy run start

S8300... access the WEB administration
and depending on CM release..., it is either in Maintenance Web or under Installation once you sign in.. look for Server Configuration and Configure Server... click on the FIRST TWO Continues... and select configure individual services and press the continue (3rd one), then select set identities and the select configure identities... (make sure you dont click on change).

 

[HawkesNest]

Thanks wleong56,
I will give these things a looking at in the morning.

In the meantime, we changed the IP addresses back to what they were with the Installation Wizard and the IA770 VM is working again.

 

[wleong56]

OK...
Note: change to the new IP address for voicemail can be done before or after you RE-IP... no matter which way, there is be some down time.

 

[HawkesNest]

You said....
Ask your voice team to look at the trunk group connected to the IA770...

ask them to do list trunk and look for the signalling group connect the Communication Manager and the IA770.
In the signaling group xx, there is a field located to mid way on the right called: Far-end Node Name: xxxxx
where xxx is the node name...
Take note of that node name.
Then ask them to display (or change) display node-names audix and change the IP address.
I am sure you will find that it is not what you have changed it. The Install Wizard does not take care of this. I hope your voice team will know how to backout the translation and change this to the new IP addess. If not let me know.

My Response....

I don't have any people to help with this part.
Do I need to be connected to the S8300 or IA770 to look at these commands? I have connected via telnet to both and have not found how to look at "list or display or change" commands.

 

[HawkesNest]

Hey wleong56
I was finally able to figure out that I could telnet to the S8300 and then use the sat command to enter into the mode that lets me display the info you were asking me to look for, but the display node-name audix didn't have anything in the list.

Hoping you can see what I still need to do.

list trunk-group

TRUNK GROUPS

Grp No. Out Que
No. TAC Group Type Group Name Mem TN COR CDR Meas Dsp Len

1 101 isdn OUTSIDE CALL 23 1 91 y int n 0
99 109 isdn msgserver 12 1 91 y none n 0

display signaling-group 99
SIGNALING GROUP

Group Number: 99 Group Type: h.323
Remote Office? n Max number of NCA TSC: 10
SBS? n Max number of CA TSC: 10
IP Video? n Trunk Group for NCA TSC: 99
Trunk Group for Channel Selection: 99
TSC Supplementary Service Protocol: b
T303 Timer(sec): 10

Near-end Node Name: procr Far-end Node Name: msgserver
Near-end Listen Port: 1720 Far-end Listen Port: 1720
Far-end Network Region: 1
LRQ Required? n Calls Share IP Signaling Connection? y
RRQ Required? n
Media Encryption? n Bypass If IP Threshold Exceeded? n
H.235 Annex H Required? n
DTMF over IP: out-of-band Direct IP-IP Audio Connections? y
Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n
Enable Layer 3 Test? n Interworking Message: PROGress
H.323 Outgoing Direct Media? n DCP/Analog Bearer Capability: 3.1kHz

display node-names audix
AUDIX NODE NAMES

Audix Names IP Address
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .

 

[wleong56]

Yes, you can telent if properly setup, instaed of using SSH.

Your node name is entered as...
Far-end Node Name: msgserver

Since it is not in node-name audix
Try the command node-name IP
and look for msgserver.
These TWO commands is the equivalent as the telephony DNS table.


BTW, for RE IP, also take a look at your DHCP scope and for the Voice VLAN... there is an option 242 or option 176 string.
You will also need to change the IP address there.

 

[HawkesNest]

Sweet, that shows what we are looking for. Looks like I will need to change both of these entries to the new IP addresses.

What is the full command syntax to change the IP address.
Also, if I add a new node-name to test the command, how do you delete a node-name entry?

Note: I put xxx.xxx to replace the actual displayed IP address.

display node-names ip
IP NODE NAMES
Name IP Address
default 0.0.0.0
msgserver xxx.xxx.11.85
procr xxx.xxx.11.69

( 3 of 3 administered node-names were displayed )
Use 'list node-names' command to see all the administered node-names
Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name

 

[HawkesNest]

I keep getting into this screen as I test this command and don't know how to get out other than to kill my session and log back in.


change node-names ip

IP NODE NAMES
Name IP Address
default 0.0.0.0
msgserver xxx.xxx.11.85
procr xxx.xxx.11.69


( 3 of 3 administered node-names were displayed )
Use 'list node-names' command to see all the administered node-names
Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name

 

[HawkesNest]

Well, we found that using the Avaya ASA software we can get into the SAT mode and make the changes to the "node-name ip" fields to change the IPs to the new IP addresses. For some reason the emulation software I was using didn't have a way for me to "Save" after I had done the editing.

 

[wleong56]

To change the msgserver... that is going to be a bit involved. Standby for the next thread.

Not sure I understand your comment below. I am guessing, you want to add one for testing... it is like DNS. Enter a DNS name to your left and the IP address to your right. I hope this answer your question. AVAYA has this tendency were if you need to remove one thing, you might have first to remove a few things before you can get to what you want to remove. Like fixing cars. I suggest we discuss this first.
Your comment --> Also, if I add a new node-name to test the command, how do you delete a node-name entry?

and this? Are you using SAT. If so, that would be your function key F1. If you are using plain old telnet and emulating at W2KTT, then cancel is ESC Key and then x. Or i really don't know what you are asking.
Your comment... I keep getting into this screen as I test this command and don't know how to get out other than to kill my session and log back in.

 

[HawkesNest]

That pretty well answers my question. When I would attempt to use the Change command, and because I was using SecureCRT and the VT220 emulation, I couldn't seem to exit out of the change mode or save the changes. Once we started using the ASA software and the built in emulator, we could use the change node-names IP and add a test node-name to the list and save it. Apparently Avaya uses 4410 and/or 512 emulation according to a google search.

We now have all the info we need to be able to change the IP addresses and keep the voice mail working too.

A big thanks to you again wleong56 for staying with me and providing all of the key info we needed to figure all of this out.

 

[wleong56]

Thanks for the compliments.

Here are some tips to chage that msgserver... as promised in 3 threads back.
You should perform this after you re IP.

Your voicemail trunk group is 99.

1.
change trunk-group 99
and page over to the trunk members and it shows you have 12 members. Take note of the information on the screen, as you will need it to put it back.

2.
change node-name ip
Add a psudo node name and IP address.
Lets call that vmail xx.xx.xx.xx

3. change signaling-group 99
and go to the field Far-end Node Name and replace that with vmail and Enter F3 in SAT/ASA.

4.
change node-name ip
Now go back and change the msgserver IP to the new one.

5.
change signaling-group 99
And replace the vmail to msgserver

6.
change trunk-group 99
and add all the members back in... it is member and signaling group at the right end of the form.

 

[HawkesNest]

Hey wleong56,
I understand now how to do the 6 steps you have shown in the previous post, but I don't understand the purpose of the 6 step process.

This was what I was planning to do.
Since a reboot is required after the re-ip using the Installation Wizard, I was planning to just change the two IPs of the two names in the "node-name ip" list prior to to using the Installation Wizard via the service port to re-ip, and then reboot by a power cycle.

Would I run into a problem by doing it that way.

 

[wleong56]

You cannot just change the TWO IP addresses.
You must first remove all the associated configuration before you can even get to change the TWO IP address, which is your intent.
AVAYA does this intentionally as a fail safe mechanism to ensure nothing is accidential.

For example, with your system running at the moment, if you try and change the IP address, it will say... must busyout facility or object in use and would not allow you to complete the change. Thus, the above steps will be required. In some cases, you must busyout the signalling groups, boards before changes can be made. Hope this helps.

 

[wleong56]

I see, you want to do the node-name ip change first before the Install Wizard... I guess that would be OK. There is no right or wrong here. But I would have done it the other way doing the RE-IP first and making sure that everything is up and running. You see, to us telephony people, our thinking is that the overall functionality and operatability of the PBX system is first priority. We consider voiceamil as an adjunct... or prepherial systems as secondary. So, I was a little surprised when you reverted back.

 

[HawkesNest]

Interesting, This is all good to know. I now see the point to your 6 step instructions.

How would I find where the procr name is used, and would I need to do the same 6 step process to change it's IP address?

change node-names ip

IP NODE NAMES
Name IP Address
default 0.0.0.0
msgserver xxx.xxx.11.85
procr xxx.xxx.11.69

 

[wleong56]

The procr in node-name ip...
procr is your S8300... media module (blade) in slot 1.
If you look at how it is configured today (like right now), the IP address in the node-name ip table, it is the IP address to your current configuration. If you telnet to it (or SSH), you will see something that looks like this...
Red Hat Enterprise Linux ES release 4 (Nahant)
Kernel 2.6.18-128.AV07smp on an i686
login:

Note: telnet (port23) is possible, if you to go the AVAYA WEB administration. On the left, look for Security --> Firewall and Server Access and have that activated. Otherwise, SSH (port22) is your only option.

There is nothing you need to do with procr, as that will be change as part of the Install Wizard procedures. Here is another example, where voicemail is considered secondary.
BTW, when you do a change node-name ip, you will notice that this is "grayed" out from editing.

 

[HawkesNest]

Sweet Sweet success.[BIGSMILE]

And another big big thanks to wleong56

wleong56 we hope you are getting your fair share of favors too. This was a grand favor for us and we really really appreciate it a bunch.

We were able to RE-IP the system today using the Installation Wizard and then following the steps outlined, (using the Avaya ASA software to connect to the new IP address of the S8300), with a couple of extra steps that we found we needed to do during the process. We had to busyout signaling-group 99 before we could change the Far-end Node Name.

1.
change trunk-group 99
and page over to the trunk members and it shows you have 12 members. Take note of the information on the screen, as you will need it to put it back.

2.
change node-name ip
Add a psudo node name and IP address.
Lets call that vmail xx.xx.xx.xx
save

2-A.
busyout signaling-group 99

3. change signaling-group 99
and go to the field Far-end Node Name and replace that with vmail and Enter F3 in SAT/ASA.
save

4.
change node-name ip
Now go back and change the msgserver IP to the new one.
save

5.
change signaling-group 99
And replace the vmail to msgserver
save

5-A.
We then issued this command.
release signaling-group 99

At this point the voice mail was back online.

6. as we compaired the info we had captured previously we found that this step didn't need anything added back in.
change trunk-group 99
and add all the members back in... it is member and signaling group at the right end of the form.

7.
change node-name ip
Remove the psudo node name and IP address.
vmail xx.xx.xx.xx
save