SAN Client not listed in GUI

[Fr_d_ric_RIGAL]

Hi all,

I'm front of a strange behavior with NetBackup 7.1 and AIX 5.3 SAN Client :

I've configured and tested several others SAN Clients (Windows, Linux, AIX, Solaris, ...) with success but here, with a new physical AIX 5.3 SAN CLient, it doesn't appears in the SAN Client List from the GUI.

This client see Archive Python devices and services are started as well.

We have tried to restart all services (Master, Media Server and Client) : idem.

We have tried upgrading the maximum FT connections to 16 : idem.

Somebody has an idea?

Thank you.

Regards

[Nicolai]

Does a "nbemmcmd -listhosts" list the host as a client ?.

Try running nbftclnt in console mode. It shoud show more info about the doing of the client:

nbftclnt -monitor -console
 

[Fr_d_ric_RIGAL]

The client (6.5.6) is listed well with nbemmcmd -listhosts

The nbftclnt command doesn't say anything.

We have another AIX 5.3 which is working very fine with the same media server and the same version.

And devices are discovered correctly so the FT pipe is good.

It's very very strange

[Nicolai]

don't the "nbftclnt -console  -monitor" on the client ouput anything at all ?

You should see a message like this below where the FTL devices are found.

02/07/11 17:35:32.054 [PrintDevices] /dev/sctl/c20t0l0
 Inquiry "SYMANTECFATPIPE 0.0     tamar.acme.com"
 TargetHBA:LUN:InitiatorHBA = 0:0:0 State = 1 RefCount = 0
02/07/11 17:35:32.054 [PrintDevices] /dev/sctl/c20t0l1
 Inquiry "SYMANTECFATPIPE 0.1     tamar.acme.com"
 TargetHBA:LUN:InitiatorHBA = 0:1:0 State = 1 RefCount = 0

You may find these two commands usefull as well :

nbftconfig -listtargets -verbose

nbftconfig -listclients -verbose

Update:

Sorry - you nedd to increase logging before the nbftclnt -console -Monitor will work.

vxlogcfg -a -p 51216 -o 200 -s DebugLevel=6 -s DiagnosticLevel=6

[Fr_d_ric_RIGAL]

I think it's normal I've no nformation since the SAN client is not listed in SAN Client GUI.

Even if I try to add it manually it doesn't work (time out), even if it sees Archive Python Devices.

And now the nbftclnt service doesn't want to start (this morning I could start it)

Licenses are OK. 

Client is installed in SAN Client only.

Client is configured as SAN Client.

There is no SERVER=Client_Name entry in the bp.conf of Master Server.

PBX is installed and running well.

Now we will try to uninstall and reinstall Client Binaries.

[Fr_d_ric_RIGAL]

After reinstalling NetBackup Client the problem is still the same.

nbftclnt -console  -monitor gives :

isSANClient:Client Name: uxeaufr147.eau.cgeaux.fr SANClient = 1
FATClientMgrService::hasSANClientLicense:Found SAN Client License
Segmentation fault(coredump)

Not very good :(

[Anton_Panyushki]

Just a suggestion- in 6.5 SAN clients appear in Device Configuration wizard.

Try to launch wizard and see if a new SAN client pops up.

[Nicolai]

But you now know what you are up against. Does a core file get generated ?. What does a "file" on the core file say ?

[Fr_d_ric_RIGAL]

We are going to look at this dump so as to try to find something.

But one thing I don't understand : this SAN Client was a SAN Media Server before and all was working well. I don't understand why with less binaries a Segmentation Fault and Memory Fault is generated.

[Fr_d_ric_RIGAL]

Hi all,

We have opened a case with Symantec Support.

The have sent us an EEB but we don't have tested yet.

I will say you if this EEB works fine.

[Nicolai]

OK - There was properly a very good reason for the core dump then :D