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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

upgrading from 2.0 to 3.1 and keeping S3400 hardware ( MSS Store )

Status
Not open for further replies.

ayavauser

Technical User
Sep 22, 2005
388
US
I have gone through all the jumps and hoops with regards to using backup verification tools - no errors on either MSS or MAS - used DCTtool ( 3.1 ) to Analyze system before reloading MAS

* reloaded MSS and restored data - no trouble
doubled checked trusted severs , network settings on Private LAN and Corp LAN , MAS Host setup , COS values are all there

* reloaded MAS with 3.1 , entered NEW product key
(differs as the old version was Windows 200 server)
loaded DCTtool.exe (3.1) and DCT file ( the one from the Analyze ) to Avaya_support folder as noted if its an upgrade

run setup - reboots MAS - browse to Avaya_Support and chose the DCT file - gets all the way through to

re-trying to AddEveryone ( 1 ) goes through and them comes back with re-trying to AddEveryone ( 2 )........

up to re-trying to AddEveryone ( 30 )

I can ping to either side on the private LANs - nothing has changed on the file once it was created via the Analyze fucntion


first time doing an upgrade just looks as if it in a looping condition

FYI - this system only had 10 Subscribers ( this was one we had in the LAB - so its not Earth Shattering if I had to do it all over again - just wanted to it here before the real world )

cheers : )


ayavauser
 
Have you tried to restart the gvconfig.exe manually ? It may show you where it is hanging.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
tried to run the gvconfig.exe and it fails when connecting to LDAP Trusted Server - verified private IP Address for both MAS 192.168.1.10 / MSS 192.168.1.1 / I am able to ping both from each other - also checked LDAP password in MSS Trusted Server - even re-entered via MSS - also tried to remove and re-enter via MSS Trusted Server

still fails

running through wizard

* MSS1 is the Peer Store
* first server in the domain
* Please enter the LDAP password , confirm password
* comes back with error

" could not Authenticate using the supplied password
The Trusted Server Configuration for this Message
Application Server may not have the correct IP Address "

really not sure where the mismatch or error is , as all seems to be right I have seen issues where LDAP password is in correct but it gives a different error when running the DCT tool - but the gvconfig does shows its not able to connect to the trusted server








ayavauser
 
are you sure the MAS is 192.168.1.10 and not 192.168.1.250 ?

Look at the trusted server in the MSS and make sure it has the right IP

Also look at the admin log in the MSS and the MAint log to see if it is kicking errors. The other thing i have seen it the name of the servers are case sensitive. I copied the name right from a MAS and it rejected it as it showed caps and it was all lower case.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
looking at the DCT tool -
private address

mss 192.168.1.1
mas1 192.168.1.10
mas2 192.168.1.249
mas3 192.168.1.248
mas4 192.168.1.247
mas5 192.168.1.246
mas6 192.168.1.245

__________________________________________________________

did a ipconfig /all from MAS

Ethernet adapter Local Area Connection 2:

IP Address. . . . . . . . . . . . : 192.168.1.10

___________________________________________________________

I will check the name as it is in caps and not lower case





ayavauser
 
If it was using the 172.31.x.x private LAN scheme the mas1 would be 172.31.1.250 amd MSS would be 172.31.1.1



ayavauser
 
Very odd the host file is hard coded for 192.168.1.250 for mas 1 so i would chge it in the MAS and the MSS and see if that will do it. The MSS is rejecting the connection and i think it is the IP. I have never seen one use a 192.168.1.10 or anything else but 192.168.1.250 for the IP of MAS one using 192.x.x.x

What is in your host file?

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top