- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Replacing HBA card in TRU64 4.0F
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
тАО12-09-2008 09:28 PM
тАО12-09-2008 09:28 PM
Replacing HBA card in TRU64 4.0F
I had to replace the fibre channel card in my ES40 server running TRU64 4.0F due to its failure. The card is in point to point topology. On replacing the card and booting the server the emxmgr shows the entry of the old card. I believe the old entry needs to be removed and there is a process to do so. Can anyone please tell me how to go about it. Below is the output of the emxmgr command:
root#diablo > emxmgr -d
The available adapter instances are:
emx0
root#diablo > emxmgr -t emx0
emx0 state information:
Link : connection is UP
Point to Point
Fabric attached
FC DID 0x011000
Link is SCSI bus 1 (e.g. scsi1)
SCSI target id 6
portname is 1000-0000-C926-75FC
nodename is 2000-0000-C926-75FC
N_Port at FC DID 0x011300 - SCSI tgt id 1 :
portname 5000-1FE1-001B-B671
nodename 5000-1FE1-001B-B670
Present, Logged in, FCP Target, FCP Logged in,
N_Port at FC DID 0x011400 - SCSI tgt id 0 :
portname 5000-1FE1-001B-B672
nodename 5000-1FE1-001B-B670
Present, Logged in, FCP Target, FCP Logged in,
N_Port at FC DID 0xfffffc - SCSI tgt id -1 :
portname 20FC-0060-69C0-2762
nodename 1000-0060-69C0-2762
Present, Logged in, Directory Server,
N_Port at FC DID 0xfffffe - SCSI tgt id -1 :
portname 2000-0060-69C0-2762
nodename 1000-0060-69C0-2762
Present, Logged in, F_PORT,
----------------------
The following N_PORTS have SCSI target ids assigned but have not been
seen in the topology...
SCSI tgt id 7 : portname 1000-0000-C92C-EDEB
nodename 2000-0000-C92C-EDEB
root#diablo > emxmgr -m emx0
emx0 SCSI target id assignments:
SCSI tgt id 0 : portname 5000-1FE1-001B-B672
nodename 5000-1FE1-001B-B670
SCSI tgt id 1 : portname 5000-1FE1-001B-B671
nodename 5000-1FE1-001B-B670
SCSI tgt id 6 : portname 1000-0000-C926-75FC (emx0)
nodename 2000-0000-C926-75FC
SCSI tgt id 7 : portname 1000-0000-C92C-EDEB
nodename 2000-0000-C92C-EDEB
root#diablo >
Card with tgt id 6 has replaced tgt id 7. I need to get rid of tgt id 7 card.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 06:00 AM
тАО12-10-2008 06:00 AM
Re: Replacing HBA card in TRU64 4.0F
See http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/V40F_HTML/MAN/MAN7/0018____.HTM et.al. for more information.
For example, emx_data.c might have:
{ 0, 6, 0x0010, 0x0000, 0x21c9, 0x4870, 0x0010, 0x0000, 0x21c9, 0x4870 }, >> new adapter
{ 0, 7, 0x0010, 0x0000, 0x21c9, 0x7c70, 0x0010, 0x0000, 0x21c9, 0x7c70 }, >> old adapter
You'd remove "0,7" entry and change the "0,6" to be the new "0,7" entry.
Its been a while since I've used V4 systems, so read the documentation but the key is getting the emx_data.c file updated and its content used.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 06:42 AM
тАО12-10-2008 06:42 AM
Re: Replacing HBA card in TRU64 4.0F
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 08:13 AM
тАО12-10-2008 08:13 AM
Re: Replacing HBA card in TRU64 4.0F
The link you have given above is the emx man page. I have gone through it on the server but it doesn't give much actionable information. I did try editing the /etc/emx.info file with the correct entries and then rebuild the kernel with doconfig command (this process is given in the man emx_data.c) but on rebooting the server I did not find any change in the configuration and my changes in the emx.info files were also lost. One strange thing I found about the emx.info file is as below:
root#diablo > ls -l /etc/emx.info
---------- 1 root system 1099 Dec 10 16:27 /etc/emx.info
root#diablo >
Even though it doesn't show any permission enabled, I am able to read it and even edit it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2008 07:52 AM
тАО12-18-2008 07:52 AM
Re: Replacing HBA card in TRU64 4.0F
The documentation indicates you should edit the emx_data.c file... the emx.info file is a view of what the kernel has for mapping information. Updating emx.info won't change anything. Re-read the documentation and follow the link to emx_data.c in the documentation to continue.
" emx_data.c - Configuration file for the emx device driver
SYNOPSIS
/sys/data/emx_data.c
DESCRIPTION
Refer to emx(7) for a general overview of the emx device driver.
This file is used to manipulate manipulate the emx driver's Fibre Channel
(FC) world wide name to Target Id mappings for each adapter. Device
deletion and/or replacement will commonly require modifications to the
Target Id mappings.
"
You need to change emx_data.c with the mappings desired and rebuild the kernel.