- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Trouble with A5158A and loop mode
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
Forums
Discussions
Discussions
Discussions
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
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
03-03-2004 01:57 PM
03-03-2004 01:57 PM
Trouble with A5158A and loop mode
We are seeing problems with connecting to our san with the A5158. It keeps reporting loop mode instead of in fabric. I have put the latest fc patch on PHKL_27751 and updated my system to december version on hardware and software patches. We have tried changing cables, gbic's reinstalling the FibrChan00 driver and patch again. Please help !
Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Previous Topology = UNINITIALIZED
Local N_Port_id is = 0x000000
Local Loop_id is = 126
N_Port Node World Wide Name = 0x50060b00000a5225
N_Port Port World Wide Name = 0x50060b00000a5224
Driver state = AWAITING_LINK_UP
Hardware Path is = 7/0/3/0/0
Number of Assisted IOs = 0
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 960
Driver Version = @(#) PATCH_11.11: libtd.a : Jun 28 2002, 11:08:35, PHSS_26799
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 02:23 PM
03-03-2004 02:23 PM
Re: Trouble with A5158A and loop mode
I think you have a hardware problem and need to replace the card.
Even if its a recently replaced card and changed the world wide name on the lun assignment then this card seems bad.
I suppose someone could have crushed the fiber cable. That happened to us once.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 02:34 PM
03-03-2004 02:34 PM
Re: Trouble with A5158A and loop mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 02:43 PM
03-03-2004 02:43 PM
Re: Trouble with A5158A and loop mode
Actually there are no lun's assigned to it right now, due to it is not in fabric mode yet. But anyway it should be able to make a like to the switch without havning any disks zoned to it ! The cards we are seeing it on a actually 2 pices, which has been moved from one server to another, so I don't think that it is the issue. And we have tried with 3 cabels. Regarding the switch then it is auto sense, and we are not able to lock it to fabric.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 02:56 PM
03-03-2004 02:56 PM
Re: Trouble with A5158A and loop mode
if you swverify the patches, its probably not that. If the cable worked before, its probably not that.
This is a zoneing issue and I don't see a way around that.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 03:03 PM
03-03-2004 03:03 PM
Re: Trouble with A5158A and loop mode
Thanks for your respons. I can some of your point, but we are not able to see on the swithces that it tries logging in, when we connecting the cables or rebooting the machine. ! It seems very strange. Normally you are able to see that.
Normally we connect out hba's to the san, so you are able to see them and the WWN, to issure correct zoning. Could it be something about it has another place in the SAN ealiere, and are recorded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2004 03:10 PM
03-03-2004 03:10 PM
Re: Trouble with A5158A and loop mode
root@lepus[ / ]#swverify FibrChanl-00
======= 03/04/04 05:04:20 MET BEGIN swverify SESSION
(non-interactive) (jobid=lepus-0150)
* Session started for user "root@lepus".
* Beginning Selection
* Target connection succeeded for "lepus:/".
* Software selections:
FibrChanl-00,r=B.11.11.09,a=HP-UX_B.11.11_32/64,v=HP
FC-TACHYON-TL.FC-TL-KRN,l=/,r=B.11.11.09,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11.09,fa=HP-UX_B.11.11_64
FC-TACHYON-TL.FC-TL-RUN,l=/,r=B.11.11.09,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11.09,fa=HP-UX_B.11.11_32/64
+ FCMassStorage.FCMS-INIT,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_32/64
+ FCMassStorage.FCMS-KRN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_64
+ FCMassStorage.FCMS-RUN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_32/64
+ OS-Core.C-KRN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_32/64
+ OS-Core.CORE-KRN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_32/64
+ OS-Core.CORE2-KRN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_64
+ OS-Core.KERN-RUN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_32/64
+ OS-Core.KERN2-RUN,l=/,r=B.11.11,a=HP-UX_B.11.11_32/64,v=HP,fr=B.11.11,fa=HP-UX_B.11.11_64
+ PHKL_28984.FCMS-KRN,l=/,r=1.0,a=HP-UX_B.11.11_32/64,v=HP,fr=1.0,fa=HP-UX_B.11.11_64
+ PHKL_28984.FCMS-RUN,l=/,r=1.0,a=HP-UX_B.11.11_32/64,v=HP,fr=1.0,fa=HP-UX_B.11.11_32/64
* A "+" indicates an automatic selection due to dependency or
the automatic selection of a patch or reference bundle.
* Selection succeeded.
* Beginning Analysis
* Session selections have been saved in the file
"/.sw/sessions/swverify.last".
WARNING: "lepus:/": 1 check scripts had warnings.
WARNING: "lepus:/": 1 files had warnings during this operation.
* Verification succeeded.
NOTE: More information may be found in the agent logfile using the
command "swjob -a log lepus-0150 @ lepus:/".
======= 03/04/04 05:04:35 MET END swverify SESSION (non-interactive)
(jobid=lepus-0150)
root@lepus[ / ]#swjob -a log lepus-0150 @ lepus:/
======= 03/04/04 05:04:21 MET BEGIN verify AGENT SESSION (pid=3734)
(jobid=lepus-0150)
* Agent session started for user "root@lepus.gsm.orange.dk".
(pid=3734)
* Beginning Analysis Phase.
* Target: lepus:/
* Target logfile: lepus:/var/adm/sw/swagent.log
* Reading source for file information.
* Configured OS-Core.C-KRN,l=/,r=B.11.11
* Configured OS-Core.KERN2-RUN,l=/,r=B.11.11
* Configured OS-Core.KERN-RUN,l=/,r=B.11.11
* Configured OS-Core.CORE2-KRN,l=/,r=B.11.11
* Configured OS-Core.CORE-KRN,l=/,r=B.11.11
* Configured FCMassStorage.FCMS-RUN,l=/,r=B.11.11
* Configured FCMassStorage.FCMS-INIT,l=/,r=B.11.11
* Configured FCMassStorage.FCMS-KRN,l=/,r=B.11.11
* Configured FC-TACHYON-TL.FC-TL-KRN,l=/,r=B.11.11.09
* Configured FC-TACHYON-TL.FC-TL-RUN,l=/,r=B.11.11.09
* Configured PHKL_28984.FCMS-KRN,l=/,r=1.0
* Configured PHKL_28984.FCMS-RUN,l=/,r=1.0
WARNING: fcT1 is configured into "/stand/vmunix",
but a FCMS interface card has not been detected.
WARNING: fcT1_fcp is configured into "/stand/vmunix",
but a FCMS interface card has not been detected.
WARNING: fcT1_cntl is configured into "/stand/vmunix",
but a FCMS interface card has not been detected.
WARNING: fcp is configured into "/stand/vmunix",
but a FCMS interface card has not been detected.
WARNING: fcpmux is configured into "/stand/vmunix",
but a FCMS interface card has not been detected.
WARNING: The "verify" script for "FCMassStorage.FCMS-KRN" had a warning
(exit code "2"). The script location was
"/var/adm/sw/products/FCMassStorage/FCMS-KRN/verify".
* This script had warnings but the execution of this fileset
will still proceed. Check the above output from the script
for further details.
WARNING: Fileset "FCMassStorage.FCMS-KRN,l=/,r=B.11.11" had file
warnings.
* Summary of Analysis Phase:
Verified FibrChanl-00,l=/,r=B.11.11.09
+ Verified OS-Core.C-KRN,l=/,r=B.11.11
+ Verified OS-Core.KERN2-RUN,l=/,r=B.11.11
+ Verified OS-Core.KERN-RUN,l=/,r=B.11.11
+ Verified OS-Core.CORE2-KRN,l=/,r=B.11.11
+ Verified OS-Core.CORE-KRN,l=/,r=B.11.11
+ Verified FCMassStorage.FCMS-RUN,l=/,r=B.11.11
+ Verified FCMassStorage.FCMS-INIT,l=/,r=B.11.11
WARNING: + Verified with warnings FCMassStorage.FCMS-KRN,l=/,r=B.11.11
Verified FC-TACHYON-TL.FC-TL-KRN,l=/,r=B.11.11.09
Verified FC-TACHYON-TL.FC-TL-RUN,l=/,r=B.11.11.09
+ Verified PHKL_28984.FCMS-KRN,l=/,r=1.0
+ Verified PHKL_28984.FCMS-RUN,l=/,r=1.0
WARNING: 1 of 12 filesets had Warnings.
* 11 of 12 filesets had no Errors or Warnings.
WARNING: The Analysis Phase had warnings. See the above output for
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2004 09:33 PM
03-04-2004 09:33 PM
Re: Trouble with A5158A and loop mode
The other one needed to reboot the entire switch.