{section}
{column:width=25%}
{livesearch:spaceKey=SunCluster}
h5. Contents
{children:all=true}
h5. [Index]
{column}
{column:width=75%}
This page contains the following information:
----
{toc:type=list|style=none|minLevel=5|maxLevel=5|indent=0px}
----
h5. Cluster Configuration Repository (CCR)
{{/etc/cluster/ccr}} (directory)
h5. Important Files
{{/etc/cluster/ccr/infrastructure}}
h5. Global Services
One node is to specific global services. All other nodes communicate with the global services (devices, filesystems) via the Cluster interconnect.
h5. Global Naming (DID Devices)
{{/dev/did/dsk and /dev/did/rdsk}}
* DID used only for naming globally — not access
* DID device names cannot/are not used in VxVM
* DID device names are used in Sun/Solaris Volume Manager
h5. Global Devices
* provide global access to devices irrespective of there physical location.
* most commonly SDS/SVM/VxVM devices are used as global devices. LVM software is unaware of the implementation of global nature on these devices.
{{/global/.devices/node@_nodeID_}}
{{_nodeID_}} is an integer representing the node in the cluster
h5. Global Filesystems
{panel}
{{# *mount \-o global, logging /dev/vx/dsk/nfsdg/vol01 /global/nfs*}}
{panel}
or edit the {{/etc/vfstab}} file to contain the following:
{panel}
{{/dev/vx/dsk/nfsdg/vol01 /dev/vx/rdsk/nfsdg/vol01 /global/nfs ufs 2 yes global,logging}}
{panel}
Global Filesystem is also known as (aka) Cluster Filesystem (CFS) or PxFS (Proxy File system)
{info:title=Note} Local failover filesystems (i.e. directly attached to a storage device) cannot be used for scalable services — one would have to use global filesystems for it.{info}
h5. Console Software
{{SUNWccon}}
There are three wariants of the cluster console software:
* {{cconsole}} (access the node consoles through the TC or other remote console access method)
* {{crlogin}} (uses {{rlogin}} as underlying transport)
* {{ctelnet}} (uses {{telnet}} as underlying transport)
{{/opt/SUNWcluster/bin/ &}}
h6. Cluster Control Panel
{{*/opt/SUNWcluster/bin/ccp \[ clustername \] &*}}
All necessary info for cluster admin is stored in the following two files:
* {{/etc/clusters}} e.g. {{sc-cluster sc-node1 sc-node2}}
* {{/etc/serialports}}\\
\\
{noformat}
sc-node1 sc-tc 5002 # Connect via TCP port on TC
sc-node2 sc-tc 5003
sc-10knode1 sc10k-ssp 23 # connect via E10K SSP
sc-10knode2 sc10k-ssp 23
sc-15knode1 sf15k-mainsc 23 # Connect via 15K Main SC
e250node1 RSCIPnode1 23 # Connect via LAN RSC on a E250
node1 sc-tp-ws 23 # Connect via a tip launchpad
sf1_node1 sf1_mainsc 5001 # Connect via passthru on midframe
{noformat}
{column}
{section}
{column:width=25%}
{livesearch:spaceKey=SunCluster}
h5. Contents
{children:all=true}
h5. [Index]
{column}
{column:width=75%}
This page contains the following information:
----
{toc:type=list|style=none|minLevel=5|maxLevel=5|indent=0px}
----
h5. Cluster Configuration Repository (CCR)
{{/etc/cluster/ccr}} (directory)
h5. Important Files
{{/etc/cluster/ccr/infrastructure}}
h5. Global Services
One node is to specific global services. All other nodes communicate with the global services (devices, filesystems) via the Cluster interconnect.
h5. Global Naming (DID Devices)
{{/dev/did/dsk and /dev/did/rdsk}}
* DID used only for naming globally — not access
* DID device names cannot/are not used in VxVM
* DID device names are used in Sun/Solaris Volume Manager
h5. Global Devices
* provide global access to devices irrespective of there physical location.
* most commonly SDS/SVM/VxVM devices are used as global devices. LVM software is unaware of the implementation of global nature on these devices.
{{/global/.devices/node@_nodeID_}}
{{_nodeID_}} is an integer representing the node in the cluster
h5. Global Filesystems
{panel}
{{# *mount \-o global, logging /dev/vx/dsk/nfsdg/vol01 /global/nfs*}}
{panel}
or edit the {{/etc/vfstab}} file to contain the following:
{panel}
{{/dev/vx/dsk/nfsdg/vol01 /dev/vx/rdsk/nfsdg/vol01 /global/nfs ufs 2 yes global,logging}}
{panel}
Global Filesystem is also known as (aka) Cluster Filesystem (CFS) or PxFS (Proxy File system)
{info:title=Note} Local failover filesystems (i.e. directly attached to a storage device) cannot be used for scalable services — one would have to use global filesystems for it.{info}
h5. Console Software
{{SUNWccon}}
There are three wariants of the cluster console software:
* {{cconsole}} (access the node consoles through the TC or other remote console access method)
* {{crlogin}} (uses {{rlogin}} as underlying transport)
* {{ctelnet}} (uses {{telnet}} as underlying transport)
{{/opt/SUNWcluster/bin/ &}}
h6. Cluster Control Panel
{{*/opt/SUNWcluster/bin/ccp \[ clustername \] &*}}
All necessary info for cluster admin is stored in the following two files:
* {{/etc/clusters}} e.g. {{sc-cluster sc-node1 sc-node2}}
* {{/etc/serialports}}\\
\\
{noformat}
sc-node1 sc-tc 5002 # Connect via TCP port on TC
sc-node2 sc-tc 5003
sc-10knode1 sc10k-ssp 23 # connect via E10K SSP
sc-10knode2 sc10k-ssp 23
sc-15knode1 sf15k-mainsc 23 # Connect via 15K Main SC
e250node1 RSCIPnode1 23 # Connect via LAN RSC on a E250
node1 sc-tp-ws 23 # Connect via a tip launchpad
sf1_node1 sf1_mainsc 5001 # Connect via passthru on midframe
{noformat}
{column}
{section}