Recently swapped out an S8300 server, CM 5.2.1. Installed the new S8300 server and loaded the existing license file that we've had. Same MG serial number no change. Getting a license error, error type 3391. Test the license long and it fails test number 19, error code 1. Also says, Platform type/server configuration mismatch. Don't understand why we are getting this license error, as we did not upgrade the server, just burned the replacement with the same CM release and restored the .xln, CMM and security files to bring back translations. Any ideas as to why this would happen? Thanks,
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
S8300 server swap out
- Thread starter SPSANT
- Start date
AvayaTier3
Technical User
you need to restore
os, security, xln, audix-tr-name-msg
Your mismatch is in ecs.conf file which is restored from the old os backup.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
os, security, xln, audix-tr-name-msg
Your mismatch is in ecs.conf file which is restored from the old os backup.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #3
We are trying to change the IP addresses of this server to put it on the network. When we restore the OS file, it crashes the CM messaging, after we change the IP addresses. This has happened several times. Any way around this when changing IP addresses?
AvayaTier3
Technical User
yes
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #5
I have opened a ticket up with Avaya. When we changed the IP addresses on the old server, it corrupted the CMM. It would show as down. You start the messaging and it never starts correctly. Our bench lab engineer told us to reload the server. Patch it. Then when it comes time to restore, only load the security, xln and Audix translation file. We were told not to load the OS as it would put the former IP addresses back in and then corrupt the messaging again when we go to change the IP's. We did this process, as instructed, and then we get the config/mismatch alarm. Quite confusing. Thanks...
AvayaTier3
Technical User
It is not that hard to fix. You need professional help. It can only be fixed with root access to Linux.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Status