Unsolved
This post is more than 5 years old
26 Posts
0
520672
October 29th, 2012 10:00
TCP/UDP Port Requirements for OME
Hi,
The list of essential ports I have down for OME and a Managed Windows/Linux PE (11G/12G) Server for inventory and driver/firmware installing are:..
- TCP 22 - Linux file transfer and remote commands
- TCP 135 - Windows file transfer and RMI
- UDP 161 - SNMP
- UDP 162 - SNMPTRAP
- TCP 1311 - OMSA (HTTPS)
Could someone please explain to me:
- What the impact of UDP 162 (SNMPTRAP) being unavailable would be? Would it just mean that alerts would not appear in OME until the device was inventory scanned? Would functionality such as patch installation be affected?
- How the file transfer and installation process works for Windows clients (assuming 11G Server with lifecycle controller). Does the driver binary get transferred using SMB through port 135 and remotely invoked somehow? Or are other ports/methods used?
The second question I ask as I am hoping our Riberbed WAN appliances would be able to cache packages that may be going to multiple windows servers at byte level, preserving precious WAN bandwidth (we are yet to test this). I realise this will not be the case with Linux based patches being applied via SSH.
No Events found!
DELL-Raj S
327 Posts
0
October 29th, 2012 15:00
Thanks for the post.
If UDP 162 port is not enabled on the management station, OME will not be able to receive incoming traps and on-demand health status poll will not run. Health status may be stale until the next scheduled status poll runs. Patch should not be impacted by this port setting.
For patching Windows servers, WMI protocol is used and needs port 135 enabled. For Linux clients, you need to enable port 22 (default).
In OME 1.1 release, users can deploy BIOS, firmware updates on 11G and 12G systems Agent free, using iDRAC (LifeCycle controller). LifeCycle controller uses port 443 for transferring DUP (Dell update packages) from Windows server where OME is installed to iDRAC.
You can also refer to OME user guide (Page 161: Supported Protocols and Ports in OpenManage Essentials): en.community.dell.com/.../20061466.aspx
Thanks,
Raj Shresta
reestr
26 Posts
0
October 30th, 2012 03:00
Hi Raj, thanks for the reply.
Could you please elaborate on how patching is achieved using WMI? Is the package to be installed copied to the server being managed (and if so, is it copied using SMB?) and then remotely executed? Or does the package stay resident on the OME server and remotely executed? If its the latter and there was an installation failure would a second install attempt mean the package would have to be resubmitted to the managed server?
I can't find information to this detail in any of the guides or whitepapers.
txolson
15 Posts
0
February 5th, 2013 08:00
So, for an ESXi host .. .Is it using SSH to the OS or 443 to the DRAC?
Is patching of ESXi hosts supported? So far, have been unable to get to work
reestr
26 Posts
0
February 6th, 2013 00:00
For the updating of an ESXi host it (at least ours) uses the following (on the iDRAC connected interface):..
443 - HTTPS for interfacing with the lifecycle controller
1278 - HTTP for downloading the packages to the lifecycle controller (this may be configurable)
I am not a Dell Server expert but firmware patching of ESXi hosts is only possible if the server has a lifecycle controller, I believe these are fitted to 11th Generation and 12th Generation PE. Patches can then only be pushed of course through the iDRAC from OME.
txolson
15 Posts
0
February 7th, 2013 08:00
Thanks reestr! I had missed port 1278 - Working now.