Quantcast
Channel: All Simulator Discussions posts
Viewing all 1549 articles
Browse latest View live
↧

ONTAP 8.3.1 licenses owner are set to "none"

March 3, 2016, 11:06 am
$
0
0

Cannot enable any license on 8.3.1 in cluster mode.

 

netapptest3::> version
NetApp Release 8.3.1: Mon Aug 31 08:49:20 UTC 2015

netapptest3::> license show
(system license show)

Serial Number: 1-80-000008
Owner: netapptest3
Package Type Description Expiration
----------------- ------- --------------------- --------------------
Base license Cluster Base License -

Serial Number: 1-81-0000000000000004082368511
Owner: none
Package Type Description Expiration
----------------- ------- --------------------- --------------------
NFS license NFS License -
CIFS license CIFS License -
FCP license FCP License -
4 entries were displayed.

 

----------

 

The working licenses on 8.3.2RC1:

 

netapptest2::> version
NetApp Release 8.3.2RC1: Thu Nov 05 09:26:12 UTC 2015

netapptest2::> license show
(system license show)

Serial Number: 1-80-000008
Owner: netapptest2
Package Type Description Expiration
----------------- ------- --------------------- --------------------
Base license Cluster Base License -

Serial Number: 1-81-0000000000000004082368511
Owner: netapptest2-02
Package Type Description Expiration
----------------- ------- --------------------- --------------------
NFS license NFS License -
CIFS license CIFS License -
SnapMirror license SnapMirror License -
4 entries were displayed.

 

 

↧
Search

Re: ONTAP 8.3.1 licenses owner are set to "none"

March 3, 2016, 3:18 pm
$
0
0

You've added licenses to the database, but perhaps they do not correpsond to a serial number of any node in the cluster.

 

Try this:

node show -fields serialnumber,systemid

The serial number in the license need to match the value of the serialnumber field of one of the nodes.

 

 

↧
↧

Re: ONTAP 8.3.1 licenses owner are set to "none"

March 3, 2016, 6:09 pm
$
0
0

I finally figured it out that you need to change both nodes for serial number and system ID to match the license key.

After that, licenses are working and right owner is set to the node.

↧

Re: ONTAP 8.3.1 licenses owner are set to "none"

March 3, 2016, 8:53 pm
$
0
0

Can you please post the output after resolving the issue?

↧

Re: ONTAP 8.3.1 licenses owner are set to "none"

March 4, 2016, 9:59 am
$
0
0

Here is some sample output from a new vsim.

 

Here my licenses are loaded but they are not owned by any node.  I bolded/colored the key fields.

test823::system license> show

Serial Number: 1-80-000008
Owner: test823
Package           Type    Description           Expiration
----------------- ------- --------------------- --------------------
Base              license Cluster Base License  -

Serial Number: 1-81-0000000000000004082368511Owner: none
Package           Type    Description           Expiration
----------------- ------- --------------------- --------------------
NFS               license NFS License           -
CIFS              license CIFS License          -
iSCSI             license iSCSI License         -
FCP               license FCP License           -
SnapRestore       license SnapRestore License   -
SnapMirror        license SnapMirror License    -
FlexClone         license FlexClone License     -
SnapVault         license SnapVault License     -
SnapLock          license SnapLock Compliance License -
SnapManagerSuite  license SnapManagerSuite License -
SnapProtectApps   license SnapProtectApp License -
SnapLock_Enterprise license SnapLock Enterprise License -
Insight_Balance   license OnCommand Balance     -
14 entries were displayed.

And thats because the serial number in the license doesn't match the serial number of my node:

test823::> node show -fields serialnumber,systemid 
node       serialnumber systemid   
---------- ------------ ---------- 
test823-01 4026532-14-4 4026532144

So I'll reboot to the loader and change my serial number to match the license:

VLOADER> printenv SYS_SERIAL_NUM
4026532-14-4
VLOADER> setenv SYS_SERIAL_NUM 4082368-51-1
VLOADER> printenv SYS_SERIAL_NUM
4082368-51-1
VLOADER> boot

Note in this case I am only changing the serial number.  I only have one node, so I don't need to worry about having unique sysids within my cluster.  Changing the sysid is more effort.

 

After it boots into cDOT, I can see my new serial number:

test823::> node show -fields serialnumber,systemid 
node       serialnumber systemid   
---------- ------------ ---------- 
test823-01 4082368-51-1 4026532144 

test823::>

And I can see that my licenses are now owned by my node:

test823::> license show
  (system license show)

Serial Number: 1-80-000008
Owner: test823
Package           Type    Description           Expiration
----------------- ------- --------------------- --------------------
Base              license Cluster Base License  -

Serial Number: 1-81-0000000000000004082368511Owner: test823-01
Package           Type    Description           Expiration
----------------- ------- --------------------- --------------------
NFS               license NFS License           -
CIFS              license CIFS License          -
iSCSI             license iSCSI License         -
FCP               license FCP License           -
SnapRestore       license SnapRestore License   -
SnapMirror        license SnapMirror License    -
FlexClone         license FlexClone License     -
SnapVault         license SnapVault License     -
SnapLock          license SnapLock Compliance License -
SnapManagerSuite  license SnapManagerSuite License -
SnapProtectApps   license SnapProtectApp License -
SnapLock_Enterprise license SnapLock Enterprise License -
Insight_Balance   license OnCommand Balance     -
14 entries were displayed.

test823::>

The other, better, option is to just install the correct licenses.  But in this case my serial number wasn't covered by the published license keys so I changed the SYS_SERIAL_NUM to match the keys on hand.

 

↧
↧

Root volume is damaged

March 7, 2016, 2:27 am
$
0
0

Hi,

 

I have two node cluster (vsim 8.3) running on VMware Fusion. Doing some exercise I changed the MTU on my cluster ports using network port broadcas.... after few minutes one of the nodes went down and when it came back again, the following message appeared.

 

***********************
** SYSTEM MESSAGES **
***********************

The contents of the root volume may have changed and the local management
configuration may be inconsistent and/or the local management databases may be
out of sync with the replicated databases. This node is not fully operational.
Contact support personnel for the root volume recovery procedures

 

After a while the other node also showed same message.

 

I can not see my root volume in clustershell and I cannot use any of the subcommands of vol/volume....

 

Anyone who had a similar problem with VSIM 8.3? 

How can I recover my root volumes or repair it in clustershell?

 

If I enter a nodeshell, I have no option creating additional volumes using the vol command...

 

I'm stuck..

 

Thank you

Bash

↧

Re: Root volume is damaged

March 7, 2016, 6:58 am
$
0
0

you can connect to the node management ip and run 

::> node run local

 

This will drop you down the node shell and you should be able to manager the volumes 7-mode style.

 

cmemile01::*> node run local
Type 'exit' or 'Ctrl-D' to return to the CLI
cmemile01-01> vol status
Volume State Status Options
vol0_n1 online raid4, flex root, nosnap=on, nvfail=on 64-bit

 

What do you get running "::> cluster show" from the cluster shell?

If you get RPC errors and the cluster can not communicate over the interconnect the RDB is out of sync, you try and undo the changes that you have made on the MTU.

 

::> net port modify -node cmemile01-01 -port e0a -mtu 1500

 

Another option is to redeploy the sims and start fresh.

 

 

↧

Re: Root volume is damaged

March 7, 2016, 12:20 pm
$
0
0

 

I can access the nodeshell  and the output looks ok

 

n2> vol status vol0
Volume State Status Options
vol0 online raid_dp, flex root, nvfail=on
64-bit
Volume UUID: b450b0c7-fe1f-4d49-adf5-160776524770
Containing aggregate: 'aggr0_n2'

 

The vol0 has no space issues

n2> df -g vol0
Filesystem total used avail capacity Mounted on
/vol/vol0/ 7GB 1GB 5GB 19% /vol/vol0/

 

n2> vol
The following commands are available; for more information
type "vol help <command>"
autosize lang options size
container offline restrict status
destroy online

 

I cannot create new volumes inside nodeshell

 

clu1::> aggr show -fields has-mroot
aggregate has-mroot
--------- ---------

Warning: Only local entries can be displayed at this time.
aggr0_n2 true
n2aggr false
2 entries were displayed.

 

The Volume subcommands are not available

clu1::*> volume ?

Error: "" is not a recognized command

clu1::*> volume

 

Only the node lif is available

clu1::*> net int show
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
clu1
c1n2mgmt up/up 192.168.101.37/28 n2 e0c true

 

cluster show is not available

 

clu1::*> cluster setup

Error: command failed: Exiting the cluster setup wizard. The root volume is damaged. Contact support personnel for the
root volume recovery procedures. Run the "cluster setup" command after the recovery procedures are complete.

 

I changed the MTU on both nodes in the cluster but something caused cluster configuration lost, I cannot figure it out!

 

clu1::*> net port show
(network port show)
Speed (Mbps)
Node Port IPspace Broadcast Domain Link MTU Admin/Oper
------ --------- ------------ ---------------- ----- ------- ------------
n2
e0a Cluster - up 1500 auto/1000
e0b Cluster - up 1500 auto/1000
e0c Default - up 1500 auto/1000
e0d - - up 1500 auto/1000
e0e - - up 9000 auto/1000
5 entries were displayed.

 

In advanced or Diagnostic level, I cannot run cluster ring show. Its like cluster services are not available!.

Never seen this before.

 

 

↧
Search

Re: Root volume is damaged

March 7, 2016, 9:26 pm
$
0
0

I think you've hit on an interesting scenario.  Jumbo frames don't work on VMware Fusion, and by attempting to use jumbo frames for the cluster network something has gone wrong with the RDBs.

Did they panic and reboot?

Do you know which one had epsilon?  

 

↧
↧

IDE disk controler

March 8, 2016, 1:26 am
$
0
0

Hello,

 

I would like to know if it's possible to replace the IDE (1:1) disk controler on virtual disk 4 to a SCSI (1:0) controler on DataONTAP Simulator.

 

If it's possible, it's a good news, because, with this controler, VMware offers the possibility to shared a virtual disk between 2 virtual machines and, probably, the possibility to create a real HA pair or shared disks.

 

Thank you for your help.

↧

Re: Root volume is damaged

March 8, 2016, 3:58 am
$
0
0

That's what I have noticed. All 5 RDBs are gone but somehow the cluster shell remains!!!

No panic, but the node2 (the one with the epsilon role) rebooted.

 

 

 

 

↧

Re: Root volume is damaged

March 8, 2016, 7:59 am
$
0
0

I tried to break one on purpose last night, but its still up this morning.  Which version are you using specifically?  8.3GA, RC1?  My test box was 8.3.1.

I modified the MTU with:

network port broadcast-domain modify -broadcast-domain Cluster -ipspace Cluster -mtu 9000

Cluster ping identifies the MTU problem but operationally its all still working

cluster1::*> cluster ping -node tst831-02
Host is tst831-02
Getting addresses from network interface table...
Cluster tst831-02_clus1 tst831-02 e0a       169.254.181.27 
Cluster tst831-02_clus2 tst831-02 e0b       169.254.59.32  
Cluster tst831_clus1    tst831-01 e0a       169.254.115.129 
Cluster tst831_clus2    tst831-01 e0b       169.254.113.38 
Local = 169.254.181.27 169.254.59.32
Remote = 169.254.115.129 169.254.113.38
Cluster Vserver Id = 4294967293
Ping status:
.... 
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................ 
Detected 1500 byte MTU on 4 path(s):
    Local 169.254.181.27 to Remote 169.254.113.38
    Local 169.254.181.27 to Remote 169.254.115.129
    Local 169.254.59.32 to Remote 169.254.113.38
    Local 169.254.59.32 to Remote 169.254.115.129
Larger than PMTU communication fails on 4 path(s):
    Local 169.254.181.27 to Remote 169.254.113.38
    Local 169.254.181.27 to Remote 169.254.115.129
    Local 169.254.59.32 to Remote 169.254.113.38
    Local 169.254.59.32 to Remote 169.254.115.129
RPC status:
2 paths up, 0 paths down (tcp check)
2 paths up, 0 paths down (udp check)
↧

Re: Root volume is damaged

March 8, 2016, 12:39 pm
$
0
0

Only node management lifs and a clustershell (via direct ssh to node) are abailable.

There are no cluster lifs available. I get a clustershell when I directly logon to node using ssh.

cluster show or cluster ring show are not available.

 

 

The nodeshell does not give me a possibility to create new volumes. I could reinstall a new two node cluster but would like to repair vol0 if there is a way.

 

Thank you

↧
↧

Re: Root volume is damaged

March 8, 2016, 4:43 pm
$
0
0

OK.  Need to try to revive the RDBs.  Shut down the non-epsilon node, halt the epsilon node and boot to the loader.  unset the boot_recovery bootarg and see if it will come back up.

 

unsetenv bootarg.init.boot_recovery

If the epsilon node comes back up, make sure the cluster ports are mtu1500, then try to bring up the other node.

 

 

↧

Re: Root volume is damaged

March 9, 2016, 2:51 am
$
0
0

Hi,

 

Removing the recovery flag "unsetenv bootarg.init.boot_recovery" did the trick.

 

I did first on the node with the epsilon role. When it came back online, RDBs started one after one starting with mgmt, vifmg, bcomd.... and so on... of course after view RPC connect errors... The vldb took a while to start but could fetch all info of my volumes again Smiley Happy

 

Then I ran on the other node..... Now my node management and cluster shell as well as OnCommand System Manager are fully functional again...

 

What I want to know if you can assist me

 

1)  What did the unsetenv bootarg.init.boot_recovery to the boot process and logs in order to bypass a set of configurations and try to launch the RDBs again?

2) What trigged the continuation of  "my cluster inconsistence" after I switched the MTU settings right after the node with the epsilon rebooted?

 

Thank you so much for your prof. help

 

// Bash

 

↧
Search

Re: Root volume is damaged

March 9, 2016, 6:58 pm
$
0
0

That flag gets set when a condition is detected that casts doubt on the state of the root volume.  In the simulator this usually happens when the root volume gets full, but I've also seen it after some kinds of panics.  Once set, it stays set until you unset it.  This makes sure that someone diagnoses the condition that lead to it getting set in the first place before the node is placed back into service.

 

This particular message seems to indicate the RDB and local management DBs didn't match at boot time, possibly from a pooly timed panic.  The simulated nvram has its limits.

 

If you encounter this in real life you should contact support.

 

↧

Re: Simulate ONTAP 8.3.1 with mounting /cfcard and panic

March 30, 2016, 11:18 am
$
0
0

So a few questions:

What is the host OS?

What version of virtual box?

Which method did you use to create the VM?

 

In my case, its OSX, vbox 5.0.16 r105871, and I use the ovf import method.

 

On mine, the IDE controllers are type PIIX4.  From your log output yours are type PIIX3. That may or may not be relevant.  The logs imply a problem writing to the virtual disk.

 

 

 

↧
↧

Re: Ontap Edge or Ontap-v Eval still available?

March 30, 2016, 1:15 pm
$
0
0

Thanks for your reply, I'll check with my SE.  I was actually hoping to get the 7 mode eval, so I can test upgrading my existing.   Maybe he will have it.

↧

Re: Simulate ONTAP 8.3.1 with mounting /cfcard and panic

March 30, 2016, 5:10 pm
$
0
0

My host is OS X El Capitan

Virtual Box is version 5.0.14 r105127

I just created the new virtual server with option you have on your output.

For the drives, I uncompressed with gunzip and point the storage to it.

I alos tried to import but I got "NS_ERROR_CALL FAILED" when it try to mount the disk1.

 

Thank you Sean for helping me with it.

↧

Re: Simulate ONTAP 8.3.1 with mounting /cfcard and panic

March 30, 2016, 6:52 pm
$
0
0

Try using the ovf import method.  I posted a sample ovf file in this thread. Over here. The 832 version shoould work for 831.  If not post back and I'll paste in the one from my 831 ovf.

 

↧
Viewing all 1549 articles
Browse latest View live
Search