We all know that TLSv1.0 & 1.1 are no longer recommended and not secure to be used in production environments. Specially, if you are working in a secure environment you will be asked to disable insecure protocols. So, let’s look at the steps. The steps are so simple and straightforward. [Note: all the commands are in Bold Italics]
Step 01: SSH into the Nimble management controller (use the admin account)
Step 02: Check whether TLSv1.0 & 1.1 are enabled using the command
group – – info | grep -i tlsv
Step 03: If enabled, try to disable those
group – – edit – – tlsv1_enabled
You may enter either Yes or No based on your requirement. If you type Yes, both TLSv1.0 & 1.1 would be disabled.
Step 04: Verify whether TLSv1.0 & 1.1 are disabled
You can set network port IP addresses manually using the command-line interface port and cable. If you have not done so already, you need to enable your system for using the command-line interface port.
Network ports on controller module A and controller module B are configured with the following factory-default IP settings:
Management Port IP Address: 10.0.0.2 (controller A), 10.0.0.3 (controller B)
Start and configure a terminal emulator, such as Hyper Terminal or VT-100, using the display settings / connection settings in Table.
Terminal emulation mode
VT-100 or ANSI (for color support)
In the terminal emulator, connect to controller A. Press Enter to display the CLI prompt (#).At the login prompt, enter the default user manage.Enter the default password !manage.
At the prompt, type the following command to set the values you obtained in step 1 for each network port, first for controller A and then for controller B:set network-parameters ip address netmask netmask gateway gateway controller a|bFor example:
# set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway 192.168.0.1 controller a
# set network-parameters ip 192.168.0.11 netmask 255.255.255.0 gateway 192.168.0.1 controller b
Type the following command to verify the new IP addresses:show network-parameters
Use the ping command to verify network connectivity.For example:# ping 192.168.0.1 (gateway)
In the host computer’s command window, type the following command to verify connectivity, first for controller A and then for controller B:
If you cannot access your system for at least three minutes after changing the IP address, your network might require you to restart the Management Controller(s) using the CLI. When you restart a Management Controller, communication with it is temporarily lost until it successfully restarts.Type the following command to restart the management controller on both controllers:restart mc both
When you are done using the CLI, exit the emulator.
[source: HP Documentation]
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.