To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
1. Log in to the active Virtualization Resource Management (VRM) node as user gandalf and run the su – root command to switch to user root.
Check the Tomcat logs of the VRM node to identify the IP addresses that repeatedly access the VRM Tomcat component to attempt to log in to the portal.
The following shows the location of the VRM Tomcat log.
According to the following example log content, the IP address 192.168.191.59 attempts to access the VRM Tomcat component.
POST /service/session indicates that a tool or component attempts to log in to the portal.
400 79 indicates that the login failed.
192.168.191.59 indicates the IP address of the tool or component that repeatedly attempts to access the VRM Tomcat component.
Log in to the devices using the identified IP addresses and confirm that the devices attempt to log in to the FusionCompute portal.
Configure a route to prevent the IP address from repeatedly attempting to access the VRM Tomcat component.
Before configuring the route, ensure that this operation has no adverse impact on VMs and customer services.
The following figure shows an example command that can be used to prevent the identified IP address from accessing the VRM Tomcat component.
The command discards all IP response sent from the identified IP addresses.
After the admin account is unlocked, you can run a command to allow the identified IP addresses to access the VRM Tomcat component. The command in the following figure is an example.
The following is an example command used to unlock the admin account on the VRM node.
(Perform this operation if you want to create another administrator account.) Log in to the FusionCompute portal and create an administrator user on the Rights Management page so that you can log in to the portal even when the admin account is locked out.
This fault occurs usually after a user has changed the password of the admin account.
If some tools or components still attempt to use the old password of the admin account to log in to the FusionCompute portal after the password is changed, the account will be locked out.
Therefore, the first thing to do is to identify the tools or components that attempt to log in to the FusionCompute portal using the old password and prevent them from attempting to log in to the portal.
Then, the account will be automatically unlocked after 5 minutes.
You can also create another administrator account so that you can log in to the FusionCompute portal even when the admin account is locked out.