Netbackup 7.6.0.1 device configuration wizard fails while discovering VTL on media server

[Igor_Im]

Hi to everyone!

Have Symantec Netbackup 7.6.0.1

Master server installed on VM (Win Server 2008 R2).

Media server installed on physical host (Win Server 2008 R2).

Huawei VTL6900 emulating MSL4048 connected to media server via SAN switch.

VTL is detected on media server's OS as MSL autoloader and 4 tape drives (installed drivers from HP on media server).

Symantec Device configuration wizard fails to discover tape library.

Any ideas? What should I check first?

[RamNagalla]

what is output of scan and tpautocont -t commands from Media servers? does it showing any Drives?

when you say VLT is detected on Media servers is that shoiwng the tape drives in Device Manager? 

[Marianne]

Please show us output of 'scan' command on the media server.

This will show devices responding to scsi_commands and should report the robot and drives.

scan command is in <install-path>\veritas\volmgr\bin

PS: 
Have you confirmed device compatibility in NBU 7.x HCL? 

[Igor_Im]

On master server

On media server

C:\Users\Administrator>"C:\Program Files\Veritas\Volmgr\bin\scan.exe"
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 8; Bus: 0; Target: 9; LUN: 0
Inquiry    : "HP      MSL G3 Series   5.30"
Vendor ID  : "HP      "
Product ID : "MSL G3 Series   "
Product Rev: "5.30"
Serial Number: "9PD7W0130W"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      MSL G3 Series   9PD7W0130W"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 4
Number of Slots  : 48
Number of Media Access Ports: 3
Drive 1 Serial Number      : "9PD7W0130X"
Drive 2 Serial Number      : "9PD7W0130Y"
Drive 3 Serial Number      : "9PD7W0130Z"
Drive 4 Serial Number      : "9PD7W01310"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 8; Bus: 0; Target: 9; LUN: 1
Inquiry    : "HP      Ultrium 5-SCSI  I3BW"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "I3BW"
Serial Number: "9PD7W0130X"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 8; Bus: 0; Target: 9; LUN: 2
Inquiry    : "HP      Ultrium 5-SCSI  I3BW"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "I3BW"
Serial Number: "9PD7W0130Y"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 9; Bus: 0; Target: 8; LUN: 3
Inquiry    : "HP      Ultrium 5-SCSI  I3BW"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "I3BW"
Serial Number: "9PD7W0130Z"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 9; Bus: 0; Target: 8; LUN: 4
Inquiry    : "HP      Ultrium 5-SCSI  I3BW"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "I3BW"
Serial Number: "9PD7W01310"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0

C:\Users\Administrator>"C:\Program Files\Veritas\Volmgr\bin\tpautoconf.exe" -t
EMM interface initialization failed, status = 77

[Igor_Im]

Solution was simple.

Turned off windows firewall on master server.

How I could forget this.

Thanks to everyone for assistance.

[sdo]

Igor - IMO, I think it best to have a firewall enabled on a principal production server.

...setup separate logs for each FW profile, so that you know which FW profile is dropping connections, and enable logging of dropped connections...

...first, a quick look in the default Windows firewall logging area:

dir %systemroot%\system32\LogFiles\Firewall\

...perhaps place the logs somewhere more easily accessible:

mkdir C:\FIREWALL-LOG
netsh advfirewall set domainprofile  logging filename C:\FIREWALL-LOG\firewall-domain.log
netsh advfirewall set privateprofile logging filename C:\FIREWALL-LOG\firewall-private.log
netsh advfirewall set publicprofile  logging filename C:\FIREWALL-LOG\firewall-public.log

...or, to reset to default folder and file names:

netsh advfirewall set domainprofile  logging filename %systemroot%\system32\LogFiles\Firewall\firewall-domain.log
netsh advfirewall set privateprofile logging filename %systemroot%\system32\LogFiles\Firewall\firewall-private.log
netsh advfirewall set publicprofile  logging filename %systemroot%\system32\LogFiles\Firewall\firewall-public.log

...set the max log size...

netsh advfirewall set domainprofile  logging maxfilesize 32767
netsh advfirewall set privateprofile logging maxfilesize 32767
netsh advfirewall set publicprofile  logging maxfilesize 32767

...log dropped connections...

netsh advfirewall set domainprofile  logging droppedconnections enable
netsh advfirewall set privateprofile logging droppedconnections enable
netsh advfirewall set publicprofile  logging droppedconnections enable

...check for updated logs:

dir C:\FIREWALL-LOG

...check your firewall profiles:

netsh advfirewall show allprofiles

...and then...

1) Test your previous problem again to make sure it is working before re-enabling firewall.

2) Then re-enable firewall.

3) Test again, which should now fail.

4) View the FW logs to see check ports are being blocked and for which FW profile - and create allow rules accordingly.

5) Re-test again, and now should be working - but with a working Windows server firewall config.

N.B:  Unfortunately the Windows FW logs do not list the 'program name' for dropped connections - and so you'll have to have open ports system wide (which are not tied to a specific executable).  I wish the NetBackup Network Port Guide also listed the program names and which ports they use - and/or - I wish the Windows FW would log the program executable names.

HTH.

[Igor_Im]

Thanks for useful info.

In current case I have test environment, so firewall is not necessary.