Compaq ProLiant 6500 Compaq Parallel Database Cluster Model PDC/O1000 for Orac - Page 66

Planning the Client LAN, Planning Cluster Configurations for NonRedundant Fibre Channel Fabrics

Get Compaq ProLiant 6500 PDF manuals and user guides View all Compaq ProLiant 6500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 66 highlights

Cluster Planning 4-7 Planning the Client LAN Every client/server application requires a local area network (LAN) over which client machines and servers communicate. In the case of a cluster, the hardware components of the client LAN are no different than in a stand-alone server configuration. In keeping with the redundant architecture of a redundant cluster interconnect, you may choose to install a redundant client LAN, with redundant Ethernet adapters and redundant Ethernet switches or hubs. Planning Cluster Configurations for Non-Redundant Fibre Channel Fabrics Once you have investigated your requirements with respect to particular parts of the cluster (ProLiant servers, shared storage components, cluster interconnect components, client LAN components), you need to plan the configuration of the entire PDC/O1000 cluster. This section describes sample configurations for midsize and larger clusters that use non-redundant Fibre Channel Fabrics. IMPORTANT: Use the Oracle documentation identified in the front matter of this guide to obtain detailed information about planning for the Oracle software. Once the required level of performance, the size of the database, and the type of database have been determined, use this Oracle documentation to continue the planning of the cluster's physical components.

  • 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
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
Cluster Planning
4-7
Planning the Client LAN
Every client/server application requires a local area network (LAN) over
which client machines and servers communicate. In the case of a cluster, the
hardware components of the client LAN are no different than in a stand-alone
server configuration.
In keeping with the redundant architecture of a redundant cluster interconnect,
you may choose to install a redundant client LAN, with redundant Ethernet
adapters and redundant Ethernet switches or hubs.
Planning Cluster Configurations for
Non-Redundant Fibre Channel Fabrics
Once you have investigated your requirements with respect to particular parts
of the cluster (ProLiant servers, shared storage components, cluster
interconnect components, client LAN components), you need to plan the
configuration of the entire PDC/O1000 cluster. This section describes sample
configurations for midsize and larger clusters that use non-redundant Fibre
Channel Fabrics.
IMPORTANT:
Use the Oracle documentation identified in the front matter of this guide to
obtain detailed information about planning for the Oracle software. Once the required level
of performance, the size of the database, and the type of database have been determined,
use this Oracle documentation to continue the planning of the cluster’s physical
components.