INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Jobs from Indeed

Experience in migrating an existing 500v2 to server edition as an expansion
2

Experience in migrating an existing 500v2 to server edition as an expansion

Experience in migrating an existing 500v2 to server edition as an expansion

(OP)
Anyone willing to share their experience doing this?

RE: Experience in migrating an existing 500v2 to server edition as an expansion

I have migrated from ip500 V2 9.0 to a Server Edition 9.1. I had to export the config as an .exp and then import it into the Server Edition. From there I had to tweak a few settings that didn't follow through like the IP addresses of the LANs and a few Telephony settings. The passwords will need to be changed so make sure to write them down. Good luck!

RE: Experience in migrating an existing 500v2 to server edition as an expansion

Random thoughts I've jotted down from doing several migration of mult-site 500's in an SCN to a SE and retaining the 500's for the PRI's

Start by making sure that none of the line groups are 0, and are unique from line groups on the SE or any other expansion
If you had to change line group ID's, be sure to change them in the ARS tables too
Make a copy of the 50:Main ARS, and change the 9N shortcode to go to the new one (the 50:Main gets changed automatically when brought into the solution)
If you had to change the line group ID's, change them in the ICR as well
I like to reset the security settings to match the SE
Change the Reject Action to Log to Audit Trail (for now, because I usually screw up logging in a few times, change it back later)
While you're in Security Settings, check the Unsecured Interfaces
If the 500 has any SCN lines, remove them

When you start the process to add the expansion unit, CHECK THE BOX TO RETAIN CONFIGURATION on the 500
You have to put in a password for Web Socket, use something consistent, so you know what it is down the road

After the 500 has been added, check the VM destination, the License Server, and uncheck Allow Direct Media path on the IP line between the SE and the 500 (both ends)

RE: Experience in migrating an existing 500v2 to server edition as an expansion

(OP)
Thank you both for your responses. Both are helpful. My big fear is that the current IP address setting in the 500 will be lost. I will check off retain configuration after making the changes.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close