Purpose of crsctl pin css

[sivakumarocp]

Hi Tim,

I would like to know the purpose of crsctl pin css command in 11g gird.
what is the use of this command.

Actually we had and issue in our 11g RAC cluster (R2), ASM diskgroups was unaccessable so we reaise SR with oracle that time they asked us to run below command.


$GRID_HOME/bin/crsctl pin css -n <racnode1> <racnode2> <racnode3>
olsnodes -n -t

after this issue got resolved the output look like this.

Code: Select all

oracle:@lnxracfd1a /oracle > sudo crsctl pin css -n lnxracfd1a lnxracfd1b lnxracfd1c
CRS-4664: Node lnxracfd1a successfully pinned.
CRS-4664: Node lnxracfd1b successfully pinned.
CRS-4664: Node lnxracfd1c successfully pinned.

oracle:@lnxracfd1a /oracle > olsnodes -t -n
lnxracfd1a       1       Pinned
lnxracfd1b       2       Pinned
lnxracfd1c       3       Pinned

Here my question is, pinning node means what.

what will happen if any one of the node in the cluster was unable to ping.

[peterx]

From :
http://docs.oracle.com/cd/E14072_01/rac ... m#CHDJHHFH

Code: Select all

crsctl pin css

Use the crsctl pin css command to pin many specific nodes. Pinning a node means that the association of a node name with a node number is fixed. If a node is not pinned, its node number may change if the lease expires while it is down. The lease of a pinned node never expires.

[peterx]

From :
http://docs.oracle.com/cd/E14072_01/rac ... m#CHDJHHFH

Code: Select all

crsctl pin css

Use the crsctl pin css command to pin many specific nodes. Pinning a node means that the association of a node name with a node number is fixed. If a node is not pinned, its node number may change if the lease expires while it is down. The lease of a pinned node never expires.

I think this command only make your nodes name and the nodes number will not be changed.
Maybe for chase log, or bug fix, they don't want the nodes name and nodes
number change!

[enricoluciano]

As the doc says, pinning is just fixing a value.
In the latest Oracle versions normally nodes are not pinned. In this way there is a certain degree of independence among node name and number. Think about it like DHCP.
This is to make policy-based server management work as it does.

If you're running pre-Oracle 11gR2 database (or if you add such to Grid infrastructure) rhos versions cannot tolerate this dynamic nome node number assignment. So you "pin" it.