post installation trouble - lack of documentation

[mgambetti]

hi,

i have installed the puredisk 5000 from console, the procedure went fine, but now i'm trying to connect to production ip (it is up and pingable) and it's saying that there is a web error (https://100.100.100.100/).

due to lack of documentation (the symantec puredisk 5000 appliance does not help very much) what i have to do after the initial https://192.168.1.1/Installer procedure?

i think that symantec must produce a custom 5000 puredisk version of the admin guide,not only that small paper inside the box and not rebound everybody to the old puredisk vm appliance manuals, which also lack for example about configuring bonding/eth failover...very bad.

[mgambetti]

the error is:

"

???it_IT.error.generic.exception.message???

For more help contact NetBackup PureDisk Support.

"

[teiva-boy]

Best to call support.  When you cobble a bunch of legacy Veritas products, something is bound to not work.  They usually are pretty good at figuring this stuff out.

[Altimate1]

Hi,

You say you have installed from console but for me the N5000 NetBackup appliance come pre-installed.

After being plugged to the network, just use the URL you gave to configure Network and storage settings.
Regarding Network, after you had quit (properly by using the LOGOUT link!!!! very important so that to avoid reconnexion time-out issue) the Installer page, Re-open it just to ensure settings are the one you expect.

from the console you should see someting like this:

Using username "root".
Using keyboard-interactive authentication.
Password:
Last login: Fri Apr  8 15:41:29 2011 from 10.7.2.20
nb5000:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 28:6E:D4:BF:4B:1A
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:fd960000-fd980000

eth1      Link encap:Ethernet  HWaddr 28:6E:D4:BF:4B:1B
          inet addr:10.7.1.1  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::2a6e:d4ff:febf:4b1b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2442757 errors:0 dropped:0 overruns:0 frame:0
          TX packets:438214 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:236029177 (225.0 Mb)  TX bytes:107470009 (102.4 Mb)
          Memory:fd9e0000-fda00000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4392265 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4392265 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1337545989 (1275.5 Mb)  TX bytes:1337545989 (1275.5 Mb)

where above 10.7.1.1 should be the replaced by 100.100.100.100 (assuming this is the address you configure)!

You can use rcnetwork status also:

nb5000:~ # rcnetwork status
Checking optional network interfaces:
    eth0      device: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    eth0      configuration: eth-id-28:6e:d4:bf:4b:1a
    eth0      IP address: 192.168.1.1/24                             running
    eth1      device: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    eth1      configuration: eth-id-28:6e:d4:bf:4b:1b
    eth1      IP address: 10.7.1.1/8                                 running
    eth2      device: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
              No configuration found for eth2                        unused
    eth3      device: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
              No configuration found for eth3                        unused
Checking mandatory network interfaces:
    lo
    lo        IP address: 127.0.0.1/8                                running
Checking service network .  .  .  .  .  .  .  .  .  .  .  .  .  .  . running
nb5000:~ #

ensure eth are seen as running.

finaly you can use yast2 (from console) to check dns and gateway settings (YOU SHOULDN'T DO ANY CHANGE FROM HERE!!!)

Regards

[mgambetti]

i have re-checked the dns and hostname, edited in dns and searchdomain, now works...testing more to come :)

[mgambetti]

ps:

all docs is under https://192.168.1.1/documentation