VNX File Simulator

Sorry a bity more readable below:

I am trying to install VNX simulator using the new 8.1.0-38015.ova. The install guide stated that I should set the ip on eth0 and eth1 those will be used as the virtual control station ports.

It stated not to manually set the eth2 port ip address, as this port should already have an IP address starting with 192.168.xxx.1. This is the the virtual ip address of the VNX file simulator, so the address that you should point your browser at to start unisphere.

This address was not set automatically so I had to manually set it. I'm not sure if this is part of the problem below but has anyone seen this issue??

The main problem is that 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!!

I've tried through the command line and through Unisphere but nothing has worked.

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.

[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]