HP ProLiant ML10 HP Smart Update Manager 6.0.0 User Guide - Page 63

Advanced topics, Configuring IPv6 networks, Network ports used by HP SUM

Page 63 highlights

5 Advanced topics Configuring IPv6 networks You can deploy to remote nodes in IPv6-based networks for Windows and Linux node servers. Using HP SUM with IPv6 networks presents challenges for IT administrators. For Windows-based servers, to communicate with remote node servers, HP SUM uses either existing credentials or the user-provided user name and password to connect to the admin$ share. This share is an automatic share provided by Windows Server. After HP SUM connects to the admin$ share, it copies a small service to the node server for the duration of the installation. After this service starts, HP SUM uses this service to communicate between the local and remote node server. During this process, HP SUM opens ports in the Windows firewall to enable HP SUM to communicate with the HP SUM engine on the node over SSL to pass data among local and remote systems. For more information about the ports used, see "Network ports used by HP SUM" (page 63). After the installation is completed or canceled, HP SUM stops the remote service, removes it from the node, closes the port on the Windows firewall, and then releases the share to the node server admin$ share. For Linux-based servers, to communicate to remote node servers, HP SUM starts by using the user-provided user name and password to create a SSH connection to the node server. After it connects, HP SUM copies a small service to the node server for the duration of the installation. After this service starts, HP SUM uses this service to communicate between the local and remote node server. During this process, HP SUM opens ports in the iptables firewall to enable HP SUM to communicate with the HP SUM engine over SSL to pass data between the local and remote systems. For more information about the ports used, see "Network ports used by HP SUM" (page 63). When the installation is completed or canceled, HP SUM stops the remote service, removes it from the target server, closes the port in the iptables firewall, and then closes the SSH connection to the node server. To set up IPv6 networking, refer the documentation for your operating system. Network ports used by HP SUM HP SUM requires that certain network ports are available for proper operation. If you lock down network ports, make sure that the ports listed in the network port tables are open so that HP SUM works correctly when connecting to remote node servers and hosts. If you are unable to unlock these network ports, the only option is to run HP SUM locally and update network-based hosts, such as the OA, iLO, and VC modules, through their web interfaces. Updates for most node types require network traffic in both directions between the server running HP SUM and the node. The server running HP SUM creates a local HTTP server, which is used to serve firmware binaries to the node and to communicate node status. The remote node issues HTTP requests and posts status updates to the server running HP SUM during the update process. If there is a routing problem or firewall blocking traffic back from the remote node to the system running HP SUM, firmware updates might be blocked, status updates blocked or delayed, or both. Table 2 HP SUM Windows network ports Ports Port 22 Port 443 Ports 445 and 137/138/139 (Port 137 is used only if you are using NetBIOS naming service.) Description Establishes a connection to a remote node via SSH to perform node inventory. A secure data port used to transfer information. Connects to the remote ADMIN$ share on node servers. These are the standard ports Windows servers use to connect to the remote file shares. If you can connect remotely to a remote Windows file share on the node server, you have the correct ports open. Configuring IPv6 networks 63

  • 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

5 Advanced topics
Configuring IPv6 networks
You can deploy to remote nodes in IPv6-based networks for Windows and Linux node servers.
Using HP SUM with IPv6 networks presents challenges for IT administrators.
For Windows-based servers, to communicate with remote node servers, HP SUM uses either existing
credentials or the user-provided user name and password to connect to the admin$ share. This
share is an automatic share provided by Windows Server. After HP SUM connects to the admin$
share, it copies a small service to the node server for the duration of the installation. After this
service starts, HP SUM uses this service to communicate between the local and remote node server.
During this process, HP SUM opens ports in the Windows firewall to enable HP SUM to communicate
with the HP SUM engine on the node over SSL to pass data among local and remote systems. For
more information about the ports used, see
“Network ports used by HP SUM” (page 63)
. After the
installation is completed or canceled, HP SUM stops the remote service, removes it from the node,
closes the port on the Windows firewall, and then releases the share to the node server admin$
share.
For Linux-based servers, to communicate to remote node servers, HP SUM starts by using the
user-provided user name and password to create a SSH connection to the node server. After it
connects, HP SUM copies a small service to the node server for the duration of the installation.
After this service starts, HP SUM uses this service to communicate between the local and remote
node server. During this process, HP SUM opens ports in the iptables firewall to enable HP SUM
to communicate with the HP SUM engine over SSL to pass data between the local and remote
systems. For more information about the ports used, see
“Network ports used by HP SUM” (page
63)
. When the installation is completed or canceled, HP SUM stops the remote service, removes
it from the target server, closes the port in the iptables firewall, and then closes the SSH connection
to the node server.
To set up IPv6 networking, refer the documentation for your operating system.
Network ports used by HP SUM
HP SUM requires that certain network ports are available for proper operation. If you lock down
network ports, make sure that the ports listed in the network port tables are open so that HP SUM
works correctly when connecting to remote node servers and hosts. If you are unable to unlock
these network ports, the only option is to run HP SUM locally and update network-based hosts,
such as the OA, iLO, and VC modules, through their web interfaces.
Updates for most node types require network traffic in both directions between the server running
HP SUM and the node. The server running HP SUM creates a local HTTP server, which is used to
serve firmware binaries to the node and to communicate node status. The remote node issues HTTP
requests and posts status updates to the server running HP SUM during the update process. If there
is a routing problem or firewall blocking traffic back from the remote node to the system running
HP SUM, firmware updates might be blocked, status updates blocked or delayed, or both.
Table 2 HP SUM Windows network ports
Description
Ports
Establishes a connection to a remote node via SSH to perform node inventory.
Port 22
A secure data port used to transfer information.
Port 443
Connects to the remote ADMIN$ share on node servers. These are the standard
ports Windows servers use to connect to the remote file shares. If you can
Ports 445 and 137/138/139 (Port
137 is used only if you are using
NetBIOS naming service.)
connect remotely to a remote Windows file share on the node server, you
have the correct ports open.
Configuring IPv6 networks
63