MaxRep: MaxRep Synchronous and Asynchronous Protection with Application Consistency License Expired After Installing

Asset ID:	1-72-2099979.1
Update Date:	2016-09-28
Keywords:

Solution Type Problem Resolution Sure

Solution 2099979.1 : MaxRep: MaxRep Synchronous and Asynchronous Protection with Application Consistency License Expired After Installing

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 3.0 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Symptoms

After installing the MaxRep Synchronous and Asynchronous Protection with Application Consistency license, UI shows licenses as "Expired" with an expiration date of December 31st 1969.

license_expired

Changes

Installed the MaxRep Synchronous and Asynchronous Protection with Application Consistency license.

Cause

MaxRep does not dynamically recognize the newly installed license.

Solution

There are three options to resolve the issue. (All disruptive to I/O)

1. Restart the MaxRep services in UI by pointing a browser at FQN/IP address of the MaxRep engine followed by /support:

Example: http://10.0.0.1/support

Default UI login is "admin". The password can be found in <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System.

Under "Management Tasks", select "Shut Down and Restart Services", then select "Restart Replication Services" and click Save Task.

support_ui

CAUTION: Stopping the replication services stops all data replication services. In some circumstances, a resynchronization might be required when the services are restarted. To avoid the resynchronization, use the stop command when the Replication Engine is not replicating data.

stop_replication

2. Login to the MaxRep Engine via ssh as user "root". The root password can be found in <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System. Run the following commands:

# service tmanagerd stop
# service vxagent stop
# service svagent stop
# service cxpsctl stop

# service tmanagerd start
# service vxagent start
# service svagent start
# service cxpsctl start

3. If this does not work, a reboot may be required which can be done via ssh root prompt by typing "reboot" or via the UI method by selecting "reboot".

reboot_ui

Attachments

This solution has no attachment