Assure UI users who are subscribed to an instance may receive an email from the Assure UI portal indicating that the instance cannot be monitored by the portal. The “Instance cannot be monitored” event email is triggered because of a problem with a portal connection used by the instance specified in the subscription. One of the following occurred:
The connection to the instance ended and was not re-established within the allowed time. Users who are subscribed to the instance and do not own the subscription or the instance can attempt to reconnect to the instance on behalf of the instance owner.
There is a problem with the password specified for the primary portal connection in the instance. Only the owner of the instance can resolve this problem by changing the password specified in the portal connection.
Reconnecting to an instance
Any subscriber to the instance identified in the “Instance cannot be monitored” event email who has Manage authority to the Assure UI portal can attempt to reconnect the instance by doing the following:
Select the Home folder, then select the Subscriptions page.
From the Subscriptions portlet, select the Reconnect action for the subscription that identifies the instance indicated in the email and has your User ID listed as a subscriber.
The Reconnect Instance dialog opens. Click OK.
Resolving password issues that prevent monitoring an instance
The “Instance cannot be monitored” event can be triggered because of a problem with the password specified within the primary portal connection for the instance. The User ID and password used to connect to the instance within the subscription are those of the instance owner. Either the password option specified in the portal connection is not correct, or the stored password in the portal connection is no longer valid.
A stored password may become not valid because the password for the User ID on the host node expired, was disabled, or was changed but not updated in the portal connection.
The owner of the instance must correct this problem by doing the following:
From the Instances portlet on the Home page, identify the portal connection used by the instance identified in the email.
Select the Details action for the portal connection from the Portal Connections portlet.
Select Specify from the Password options list. Then specify a password in the Password and Confirm Password fields.
Click OK.