Clustered Ontap…NVRAM slot on a 60×0 part 2

So now I have moved the nvram card on kitt-01 to slot 1:

kitt::> system node run -node kitt-01 sysconfig -a 1

slot 1: NVRAM (NVRAM VI)
Revision: F0
Memory Size: 2048 MB
DIMM Size: 2048 MB
Battery1 Status: Battery sufficiently charged (3996 mV)
Charger1 Status: OFF
Battery2 Status: Battery sufficiently charged (3996 mV)
Charger2 Status: OFF
Running Firmware: 11 (4.8.940)
Cluster Interconnect Port 1: disconnected
Cluster Interconnect Port 2: 4x fiber
LIDs: 0x11dc[0x0000], 0x11dc[0x2460]

 

Verifying the same on kitt-02:

kitt::> system node run -node kitt-02 sysconfig -a 1

slot 1: NVRAM (NVRAM VI)
Revision: G0
Memory Size: 2048 MB
DIMM Size: 2048 MB
Battery1 Status: Battery sufficiently charged (3960 mV)
Charger1 Status: ON
Battery2 Status: Battery fully charged (4014 mV)
Charger2 Status: OFF
Running Firmware: 11 (4.8.940)
Cluster Interconnect Port 1: disconnected
Cluster Interconnect Port 2: 4x fiber
LIDs: 0x2460[0x0000], 0x2460[0x11dc]

 

Now we were verify the interconnect status:

kitt::> system node run -node kitt-02 ic status
kitt::> system node run -node kitt-01 ic status

So, we can’t use this command without being in advanced mode, same as 7G:
kitt::> set advanced

Warning: These advanced commands are potentially dangerous; use them only when
directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y

kitt::*> system node run -node kitt-01 ic status

Link 0: down
Link 1: up
cfo_rv connection state : CONNECTED
cfo_rv nic used : 0

kitt::*> system node run -node kitt-02 ic status

Link 0: down
Link 1: up
cfo_rv connection state : CONNECTED
cfo_rv nic used : 0

Our nodes can see each other.

kitt::*> storage failover show
Takeover
Node Partner Possible State
————– ————– ——– ————————————-
kitt-01 kitt-02 true Connected to kitt-02
kitt-02 kitt-01 true Connected to kitt-01
2 entries were displayed.

Our HA pair failover situation looks good.
kitt::*> cluster show
Node Health Eligibility Epsilon
——————– ——- ———— ————
kitt-01 true true true
kitt-02 true true false
2 entries were displayed.

kitt::*> node show
Node Health Eligibility Uptime Model Owner Location
——— —— ———– ————- ———– ——– —————
kitt-01 true true 00:52 FAS6070 lab1
kitt-02 true true 00:38 FAS6070 lab1
2 entries were displayed.

 

Our cluster still appears to be in good shape, although there is 1 thing interesting here.  One of the nodes has Epsilon even though we have a 2 node cluster.  It was discussed in a previous post what to do about this.  We’ll walk through this again in a future post.