- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: WWN has changed at nport Id = 0x10700
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 02:02 AM
тАО11-10-2009 02:02 AM
we have S16K-A server with OS version as B11.11,frequently we are get following error.
Summary:
Adapter at hardware path 1/0/8/0/0: Target WWN no longer acceptable
Description of Error:
lbolt value: -1847383001
World wide name (unique identifier) for following device has
changed
nport Id = 0x10700
Probable Cause / Recommended Action:
Unlike paralled SCSI, Fibre Channel allows easy hot-swapping of disks
Due to address conflicts it is possible for disks to swap loop IDs
accidently when re-plugging them into a hub.
In order to reduce the chance of user data corruption or file system
panics, we normally require the world wide names for a particular device
to stay the same. Requiring the fcmsutil replace_dsk command ensures
that the replacement is intentional.
The driver has detected a new "world-wide name" unique identifier
at a loop position previously occupied by a device with a different
identifier.
If this is due to a deliberate replacement of the
previous device, use the fcmsutil replace_dsk command
to allow the new device to be used. If there has
been no intentional replacing of any devices, check
for conflicts in address assignments of devices on
the loop.
The fcmsutil output show /dev/td3 is fine.
fcmsutil /dev/td3
Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x010200
N_Port Node World Wide Name = 0x50060b000030dfd3
N_Port Port World Wide Name = 0x50060b000030dfd2
Driver state = ONLINE
Hardware Path is = 1/0/8/0/0
Number of Assisted IOs = 42748622
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Sep 5 2005, 10:14:40
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 02:52 AM
тАО11-10-2009 02:52 AM
Re: WWN has changed at nport Id = 0x10700
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 03:08 AM
тАО11-10-2009 03:08 AM
Re: WWN has changed at nport Id = 0x10700
check EMS / error messages in syslog.log....
ioscan -fn |grep NO_HW.....
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 04:05 AM
тАО11-10-2009 04:05 AM
Re: WWN has changed at nport Id = 0x10700
There is no hard disk failure nor fc failure.Every thing seem to be fine and in the log it show fcmsutil replace_dsk.
what does it mean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 04:11 AM
тАО11-10-2009 04:11 AM
Re: WWN has changed at nport Id = 0x10700
check this thread from ITRC :
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1257855076562+28353475&threadId=860891
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 04:34 AM
тАО11-10-2009 04:34 AM
Re: WWN has changed at nport Id = 0x10700
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 05:54 AM
тАО11-10-2009 05:54 AM
Re: WWN has changed at nport Id = 0x10700
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 12:06 PM
тАО11-10-2009 12:06 PM
Re: WWN has changed at nport Id = 0x10700
Run below command on the system,it will solve your problem.
#fcmsutil /dev/td3 replace_dsk 0x10700
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2009 04:27 AM
тАО11-11-2009 04:27 AM
Re: WWN has changed at nport Id = 0x10700
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2009 06:42 AM
тАО11-11-2009 06:42 AM
Re: WWN has changed at nport Id = 0x10700
Take a look at these commands and see if you get any additional details for the device at port 0x10700
fcmsutil /dev/td3 get remote all
fcmsutil /dev/td3 devstat all
You don't provide any feedback of what you have tried so far. Things like "it doesn't work" or "it's throwing an error" are not meaningful. Post exactly what you typed and what you got back as a response or error.