RE: Uniquely identifying a cluster, and cluster behavior - toasters

27 Aug 2001

      If you're willing to do some SNMP queries, there are some
pretty good ones.  Pay particular attention to 
cfSettings, cfPartnerName, cfPartnerSysid, etc.
BTW: This comes from /etc/mib/netapp.mib on your
filer.
-- Adam Fox
NetApp Professional Services, NC
adamfox@netapp.com
-- the Clustered Failover group
cfSettings		OBJECT-TYPE
    SYNTAX			INTEGER {
    				notConfigured(1),
    				enabled(2),
    				disabled(3),
    				takeoverByPartnerDisabled(4),
    				thisNodeDead(5)
    			}
    ACCESS			read-only
    STATUS			mandatory
    DESCRIPTION
"Clustered Failover configuration settings.
    			 The value notConfigured(1) indicates that the
    			 cluster is not licensed. The thisNodeDead(5)
    			 setting indicates that this node has been 
    			 taken over."
    ::= { cf 1 }
cfState			OBJECT-TYPE
    SYNTAX			INTEGER {
    				dead(1),
    				canTakeover(2),
    				cannotTakeover(3),
    				takeover(4)
    			}
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"Clustered Failover state."
    ::= { cf 2 }
cfCannotTakeoverCause	OBJECT-TYPE
    SYNTAX			INTEGER {
    				ok(1),
    				unknownReason(2),
    				disabledByOperator(3),
    				interconnectOffline(4),
    				disabledByPartner(5),
    				takeoverFailed(6)
    			}
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"The reason this node cannot takeover its
    			 partner"
    ::= { cf 3 }
cfPartnerStatus		OBJECT-TYPE
    SYNTAX			INTEGER {
    				maybeDown(1),
    				ok(2),
    				dead(3)
    			}
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"This is the status last returned by the
    			 Clustered Failover partner."
    ::= { cf 4 }
cfPartnerLastStatusUpdate	OBJECT-TYPE
    SYNTAX				TimeTicks
    ACCESS				read-only
    STATUS				optional
    DESCRIPTION
    			"If non-zero, the absolute time of the last
    			 update from the Clustered Failover partner."
    ::= { cf 5 }
cfPartnerName		OBJECT-TYPE
    SYNTAX			DisplayString
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"Hostname for Clustered Failover partner."
    ::= { cf 6 }
cfPartnerSysid		OBJECT-TYPE
    SYNTAX			INTEGER
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"System ID for Clustered Failover partner."
    ::= { cf 7 }

    cfInterconnectStatus	OBJECT-TYPE
    SYNTAX			INTEGER {
    				notPresent(1),
    				down(2),
    				partialFailure(3),
    				up(4)
    			}
    ACCESS			read-only
    STATUS			optional
    DESCRIPTION
    			"The current status of the interconnect.
    			 The partialFailure(3) status indicates that
    			 one of the links in the interconnect hardware
    			 is down." 
    ::= { cf 8 }
...
-----Original Message-----
From: Julius Talbot [mailto:jstalbot@mail.com]
Sent: Monday, August 27, 2001 4:56 PM
To: toasters@mathworks.com
Subject: Uniquely identifying a cluster, and cluster behavior
How does one uniquely identify a cluster?
I am trying to write some utilities that will tell me 
filesystem usage and the like, and would like to uniquely 
identify filers and clusters. I could use the system ids, but 
wouldn't it be impossible to determine the system id of a 
failed partner?
Ideally, I want a single text string that identifies the pair 
as a whole.
Anyone have an idea?

FREE Personalized E-mail at Mail.com 
http://www.mail.com/?sr=signup
Talk More, Pay Less with Net2Phone Direct(R), up to 1500 
minutes free! 
http://www.net2phone.com/cgi-bin/link.cgi?143