Loading...
Loading...
The VNX array generates alerts that are similar to the following examples. Note: In the following alerts, IP, USER, SERIAL NUMBER, and ARRAY NAME represents values that are specific to each environment. Date:2017-01-01 Time:09:30:30 Event Code:0x7d0 Description:Client is not allowed to login trial because login failure time exceeded the limits from client 'IP' with username ' USER' Subsystem: SERIAL NUMBER Device:N/A SP:N/A Host: ARRAY NAME Date:2017-01-01 Time:09:30:31 Event Code:0x4640 Description:Access is denied called by 'USER' . Application Accessed: ManagementServer. Result: Failure. Subsystem: SERIAL NUMBER Device:N/A SP:N/A Host: ARRAY NAME The following conditions apply in this scenario: An unknown user attempts to communicate with SPA or SPB of the array from a host. The "nslookup" result for the IP address in the alerts identifies the host as a ViPR SRM Collector host. The Collector host does not have a Collector-Manager module installed for the array. Another Collector host successfully discovers the array by using the default user account sysadmin . The user account in the alerts is an LDAP user account. Third-party software is installed on the Collector host in addition to ViPR SRM. Any of the third-party applications might initiate the connections.
In one reported environment, a ViPR SRM test environment was mistakenly deployed with the same IP address as the Collector host. The test environment was configured to collect data from the array by using the user account in the alerts.
If a test environment uses the same IP address as the Collector host, the test environment is the source of the connections. The test environment must be reconfigured. To identify the source of the connections in a vApp environment, run the following commands on the Collector host. Run the following command to list all incoming and outgoing connections and services netstat -aone The command output shows the owner user Number for each connection and service. Run the following command to list all running processes that the specified user owns. Replace USER with the user name in the alerts. ps -ef | grep -i *USER* Run the following command to view the login history of the specified user on the Collector host. Replace USER with the user name in the alerts. last 'USER' ViPR SRM services cannot initiate the connections, because the Collector host does not have data collection modules installed for the array. Assistance from the system administrator might be required to identify the source of the connections.
Click on a version to see all relevant bugs