HP 1032 ClusterPack V2.4 Tutorial - Page 153

ClusterPack, NAT/IPFilter Overview

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 153 highlights

NAT/IPFilter Overview ClusterPack NAT/IPFilter Overview Index | Administrators Guide | Users Guide | Tool Overview | Related Documents | Dictionary 3.6.1 Introduction to NAT (Network Address Translation) 3.6.1 Introduction to NAT (Network Address Translation) Network Address Translation (NAT) or IP Aliasing provides a mechanism to configure multiple IP addresses in the cluster to present a single image view with a single external IP address. The importance of this is two-fold: (1) Single point of "controlled" access to the cluster Compute Nodes. Network Address Translation allows communications from inside the cluster to get out, without allowing connections from outside to get in. NAT rewrites the IP headers of internal packets going out, making it appear that they all came from a single IP address (which is the external IP address of the entire cluster). Reply packets coming back are translated back, and forwarded to the appropriate Compute Node. Thus, the Compute Nodes are allowed to connect to the outside world, if needed. However, outside machines cannot initiate any connection to individual Compute Nodes, since they are exposed only to the "translated" IP address of the entire cluster. (2) Simplified network administration. The administrator can add or delete nodes to from the cluster compute cloud without any impact to the external world. Further, the administrator can have the entire compute cloud in a private IP sub-net (10.x.y.z range, 192.168.p.q range), and this also alleviates the problem of a shortage of IP addresses. IP Aliasing or Network Address Translation (NAT)

  • 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
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
NAT/IPFilter Overview
ClusterPack
NAT/IPFilter Overview
Index
|
Administrators Guide
|
Users Guide
|
Tool Overview
|
Related Documents
|
Dictionary
3.6.1 Introduction to NAT (Network Address Translation)
3.6.1 Introduction to NAT (Network Address Translation)
Network Address Translation (NAT) or IP Aliasing provides a mechanism to configure
multiple IP addresses in the cluster to present a single image view with a single external IP
address.
The importance of this is two-fold:
(1) Single point of "controlled" access to the cluster Compute Nodes.
Network Address Translation allows communications from inside the cluster to get out,
without allowing connections from outside to get in. NAT rewrites the IP headers of internal
packets going out, making it appear that they all came from a single IP address (which is the
external IP address of the entire cluster). Reply packets coming back are translated back, and
forwarded to the appropriate Compute Node. Thus, the Compute Nodes are allowed to connect
to the outside world, if needed. However, outside machines cannot initiate any connection to
individual Compute Nodes, since they are exposed only to the "translated" IP address of the
entire cluster.
(2) Simplified network administration.
The administrator can add or delete nodes to from the cluster compute cloud without any
impact to the external world. Further, the administrator can have the entire compute cloud in a
private IP sub-net (10.x.y.z range, 192.168.p.q range), and this also alleviates the problem of a
shortage of IP addresses.
IP Aliasing or Network Address Translation (NAT)