Dell PowerEdge MX7000 EMC OpenManage Enterprise-Modular Edition Version 1.20.0 - Page 43

Configuring OME–Modular web server, Configuring session inactivity timeout, Device Management Info

Get Dell PowerEdge MX7000 PDF manuals and user guides View all Dell PowerEdge MX7000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

2. Ensure that the Enable NIC option is selected. 3. Enable the required IP version-IPv4 or IPv6. NOTE: The IOM and OME-Modular must be registered in the DNS. Else, the message, "Warning: Unit file of rsyslog.service changed on disk, 'systemctl daemon-reload' recommended.", is displayed. NOTE: After rebooting OME-Modular, the public interface with the OME-Modular IP is available after 12 minutes approximately. 4. Enable the DHCP option, and enter the IP address and other details. Configuring OME-Modular web server 1. Click Application Settings > Network > Web Server Configuration. 2. Ensure that the Enable Web Server option is selected. 3. Enter the timeout value in minutes. 4. Enter the port number for the web server. You can enter a port number in the 10-65535 range. The default port number is 443. When the web server https port settings from the lead chassis are applied to member chassis as part of the add or join member task, refresh the inventory for the lead chassis manually to see the correct https port for the member chassis, on the Hardware > Device Management Info page. Launch the member chassis from the lead chassis to see the port number. If you customize the https port, OME-Modular tries to redirect to the new port automatically. However, the redirection may not work owing to security limitations of the browser. In such cases, open a new window or tab of the browser and enter the OME-Modular URL using the customized port. For example, https://10.0.0.1:1443 NOTE: Disabling the OME-Modular web server does not affect the launching of OME-Modular GUI on the phonebook page while using Chassis USB Direct. NOTE: To update the webservice timeout and session configuration timeout, use the same chassis profile. Using the same chassis profile ensures that the webservice timeout and the session configuration timeout are synchronized. Else, when the webservice timeout is updated and the session configuration is processed, the session configuration overwrites the web service settings. Configuring session inactivity timeout 1. In the Universal Timeout section, select the Enable check box and enter the time in minutes after which all the sessions must end. The duration can be in 1-1440 minutes. If you enter the universal inactivity timeout duration, the inactivity options for the API, web interface, SSH, and Serial sessions are disabled. 2. In the API, Web Interface, SSH, and Serial sections, enter the time in minutes after the sessions must end and the maximum number of sessions you want to enable. The timeout duration can be 1-1440 minutes, and the maximum number of sessions can be between one and 100. The inactivity timeout duration can be 1-100 minutes for API and Serial sessions, 1-120 minutes for web interface sessions, and 1-180 minutes for SSH sessions. The maximum number of sessions for the interfaces are as follows: ● API-1-100 ● Web interface-1-6 ● SSH-1-4 ● Serial-1 When you downgrade from the current version of OME-Modular to an earlier version, maximum number of API sessions supported is 32. However, if you upgrade OME-Modular to the latest version that supports 100 sessions, but the API Session attribute value that is displayed is 32. You can manually set the attribute value to 100 sessions. Logging in to OME-Modular 43

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
2.
Ensure that the
Enable NIC
option is selected.
3.
Enable the required IP version-IPv4 or IPv6.
NOTE:
The IOM and OME–Modular must be registered in the DNS. Else, the message, "Warning: Unit file of
rsyslog.service changed on disk, 'systemctl daemon-reload' recommended.", is displayed.
NOTE:
After rebooting OME–Modular, the public interface with the OME–Modular IP is available after 12 minutes
approximately.
4.
Enable the DHCP option, and enter the IP address and other details.
Configuring OME–Modular web server
1.
Click
Application Settings
>
Network
>
Web Server Configuration
.
2.
Ensure that the
Enable Web Server
option is selected.
3.
Enter the timeout value in minutes.
4.
Enter the port number for the web server.
You can enter a port number in the 10-65535 range. The default port number is 443.
When the web server https port settings from the lead chassis are applied to member chassis as part of the add or join
member task, refresh the inventory for the lead chassis manually to see the correct https port for the member chassis, on
the
Hardware
>
Device Management Info
page. Launch the member chassis from the lead chassis to see the port
number.
If you customize the https port, OME-Modular tries to redirect to the new port automatically. However, the redirection may
not work owing to security limitations of the browser. In such cases, open a new window or tab of the browser and enter the
OME-Modular URL using the customized port. For example,
NOTE:
Disabling the OME-Modular web server does not affect the launching of OME-Modular GUI on the phonebook
page while using Chassis USB Direct.
NOTE:
To update the webservice timeout and session configuration timeout, use the same chassis profile. Using the
same chassis profile ensures that the webservice timeout and the session configuration timeout are synchronized. Else,
when the webservice timeout is updated and the session configuration is processed, the session configuration
overwrites the web service settings.
Configuring session inactivity timeout
1.
In the
Universal Timeout
section, select the
Enable
check box and enter the time in minutes after which all the sessions
must end. The duration can be in 1-1440 minutes.
If you enter the universal inactivity timeout duration, the inactivity options for the API, web interface, SSH, and Serial
sessions are disabled.
2.
In the
API
,
Web Interface
,
SSH
, and
Serial
sections, enter the time in minutes after the sessions must end and the
maximum number of sessions you want to enable.
The timeout duration can be 1-1440 minutes, and the maximum number of sessions can be between one and 100. The
inactivity timeout duration can be 1-100 minutes for API and Serial sessions, 1-120 minutes for web interface sessions, and
1-180 minutes for SSH sessions.
The maximum number of sessions for the interfaces are as follows:
●
API—1-100
●
Web interface—1-6
●
SSH—1-4
●
Serial—1
When you downgrade from the current version of OME-Modular to an earlier version, maximum number of API sessions
supported is 32. However, if you upgrade OME-Modular to the latest version that supports 100 sessions, but the API Session
attribute value that is displayed is 32. You can manually set the attribute value to 100 sessions.
Logging in to OME-Modular
43