I cant Backup anymore. is it posible that the diverent WWnnumber in inquire are
the reason?
Hi
We habe a Networker 7.4.4 and 2 Falconstor VTL 4.0 We upgrade yesterday 1 to Version 5.1 The problem is now all Red Hat Linux and Solaris cant Backup anymore. Windows work normaly. The Networker give the Message Nov 11 08:28:01 bwbckse1zhh logger: NetWorker media: (alert) device "/dev/nst2": serial number mismatch, check system device ordering. Expected "Serial Numbers:WWNN=500630323141AAA A:ATNN=HP Ultrium 3-SCSI 8AU5S0021A:8AU5S0021A", found ":WWNN=4850202020202020:8AU640023J"
So i checked the WWN and the Serial Number. The Serial Number is OK. But the WWN is wrong. Example: The VTL has WWN 50:06:0b:00:00:64:5c:52 is i do a inquire on the Linux Server i see [root@zhhsubnp-apst01 dev]# inquire scsidev@0.0.0:HP Ultrium 3-SCSI G27D|Tape, /dev/nst0 S/N: 8AU5S0020M ATNN=HP Ultrium 3-SCSI 8AU5S0020M WWNN=50063032304DAAAA WW2N=50060B000029AAAA scsidev@0.0.1:HP Ultrium 3-SCSI G27D|Tape, /dev/nst1 S/N: 8AU5S0020N ATNN=HP Ultrium 3-SCSI 8AU5S0020N WWNN=50063032304EAAAA WW2N=50060B000029AAAA scsidev@0.0.2:HP Ultrium 3-SCSI G27D|Tape, /dev/nst2 S/N: 8AU5S0021E ATNN=HP Ultrium 3-SCSI 8AU5S0021E WWNN=500630323145AAAA WW2N=50060B000029AAAA scsidev@0.0.3:HP Ultrium 3-SCSI G27D|Tape, /dev/nst3 S/N: 8AU5S0021F ATNN=HP Ultrium 3-SCSI 8AU5S0021F WWNN=500630323146AAAA WW2N=50060B000029AAAA
Complitly diverent WWN number. is that normal?
Then i checked a Windows. We habe HBanyware installed. In HBanyware the WWN is correct. but if i do a inquire the get the same strange WWN number as on a Linux. So i have no idee way Windows is working and Linux not.
I see better now what you are dealing with based on the combination of this thread and your later one.
I would urge you a little stronger now to contact Support or your EMC Account rep as there is some internal documentation that they have available which may be quite helpful to you in regards to this issue.
Feel free to have them contact me if they have any questions.
NW keeps a track of WWNN and if they change it will complain. What worse, it may indicate drive order has changed too. If not too complex for you, I believe the easiest way to fix this is to delete jukebox and drive definition and to reconfigure it again. Apart from that, there is I believe known issue where these serial numbers are not updated correctly thus if your problem would persist it would be wise to involve support.
sweller1
78 Posts
308
0
Posted November 11th, 2009 09:00
Hello Stephan,
I see better now what you are dealing with based on the combination of this thread and your later one.
I would urge you a little stronger now to contact Support or your EMC Account rep as there is some internal documentation that they have available which may be quite helpful to you in regards to this issue.
Feel free to have them contact me if they have any questions.
Cheers!
Steve