VNX File Simulator Installation

Sorry its a bit more readable below!!

Hi All,

I am trying to install VNX simulator using the new 8.1.0-38015.ova. I am not using Vmware player or workstation.

I cannot set dns ntp etc as I keep getting the following error:

[nasadmin@TRI-LAB-VNX01 /]$ nas_cs -set -dns_domain dr.triangle.ie -search_domains dr.triangle.ie,triangle.ie  -dns_servers 10.100.0.57,10.100.0.50

Error 13690601492: usage: networkadmin -get\n             -set\n                 \n            -mib\n

First option must be a subcommand\n\n

[nasadmin@TRI-LAB-VNX01 /]$

Can anyone help me out here, I believe the networkadmin command is a Navisphere command for block systems!!

Also the ova comes with two datamovers but I can only access one as the other is not responding, I am not sure if this has any impact on the above but it might be related, see outputs below showing server_3, as an empty slot. It is also stopping me from using the file setup wizard as the wizard cannot communicate with datamover mover 2.

[nasadmin@TRI-LAB-VNX01 ~]$ /nasmcd/sbin/getreason

10 - slot_0 primary control station

5 - slot_2 contacted

[nasadmin@TRI-LAB-VNX01 ~]$ nas_server -l

id      type  acl  slot groupID  state  name

1        1    0    2              0     server_2

2        4    0    3              0    server_3

[nasadmin@TRI-LAB-VNX01 ~]$

[nasadmin@TRI-LAB-VNX01 ~]$ nas_server -info server_3

id        = 2

name      = server_3

acl      = 0

type      =

standby slot      = 3

member_of =

standbyfor= server_2

status    :

defined = enabled

actual = slot_empty

[nasadmin@TRI-LAB-VNX01 ~]$

[nasadmin@TRI-LAB-VNX01 /]$ nas_server -i -a

id        = 1

name      = server_2

acl      = 0

type      =

nas slot      = 2

member_of =

standby  = server_3,

policy=auto status    :

defined = enabled

actual = online,

ready id        = 2

name      = server_3

acl      = 0

type      =

standby slot      = 3

member_of =

standbyfor= server_2

status    :

defined = enabled

actual = slot_empty

[nasadmin@TRI-LAB-VNX01 /]$

[nasadmin@TRI-LAB-VNX01 ~]$ server_standby server_2 -verify mover

server_2 : Error 4000: server_2 : unable to connect to host

[nasadmin@TRI-LAB-VNX01 ~]$ server_standby server_2 -verify mover=server_3

server_2 : Error 4000: server_2 : unable to connect to host

[nasadmin@TRI-LAB-VNX01 ~]$

[nasadmin@TRI-LAB-VNX01 /]$ server_standby server_2 -activate mover

server_2 : Error 4002: server_2 : server_3 : unable to connect to host

[nasadmin@TRI-LAB-VNX01 /]$

[nasadmin@TRI-LAB-VNX01 tools]$ ./configure_nic ALL -l

---------------------------------------------------------------           

server_2: network devices:

Slot  Device Driver    Stub      Ifname    Irq    Id Vendor

---------------------------------------------------------------

3    cge0  bbnic  direct        eth0 0x0018 0x1645 0x14e4

4    cge1  bbnic  direct        eth1 0x0019 0x1645 0x14e4

--------------------------------------------------------------- ---------------------------------------------------------------           

server_3: network devices:

Slot  Device Driver    Stub      Ifname    Irq    Id Vendor

---------------------------------------------------------------

3    cge0  bbnic  direct        eth0 0x0018 0x1645 0x14e4

4    cge1  bbnic  direct        eth1 0x0019 0x1645 0x14e4

---------------------------------------------------------------

[nasadmin@TRI-LAB-VNX01 tools]

Sorry Rainer, I already have it in the Celerra forum but I wasn't sure it was the correct forum, so I tired the private space to check if it was working.

Not getting any replies or even views in the Celerra forum, and I have been battling with this a few days now

You created a discussion in a private space – please move to the forum

Hi gerdennehy,

Did you ever get a solution?  I'm having the same issue as you.

Hi ngynnhu,

No I rebuilt in a VMware workstation environment and got the exact same error, when trying to set ntp etc.

In the end I set ntp dns etc through editing the linux files and since then I have been able to create NFS and cifs shares and integrate with VIPR.

The second datamover comes alive when you provision greater than 8GB of memory to the VM.