- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Problem seeing tu1 network id
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
01-18-2005 07:39 AM
01-18-2005 07:39 AM
Problem seeing tu1 network id
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2005 08:41 AM
01-18-2005 08:41 AM
Re: Problem seeing tu1 network id
doconfig -c XXXX
mv /vmunix /vmunix.orig
mv XXXX/vmunix /
or something close to that...
Hein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2005 06:02 PM
01-18-2005 06:02 PM
Re: Problem seeing tu1 network id
Rebuild the kernel (doconfig),if this doesn't work, update the patch kit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2005 09:10 PM
01-18-2005 09:10 PM
Re: Problem seeing tu1 network id
What means network ID? Network ID is hostname or IP/Mac address, do you mean device name? (tu)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2005 09:56 PM
01-18-2005 09:56 PM
Re: Problem seeing tu1 network id
Mark was specific enough. It can only be the srm console since the card is not seen when os is running and he refers to a system state before booting. ;-)
do the boot with genvmunix!
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2005 01:50 AM
01-19-2005 01:50 AM
Re: Problem seeing tu1 network id
I had a similar problem when I updated one of my ES40 servers from 4.0G to 5.1
Probably, when booting the system you might see a message like
PCI card in slot # not recognized vendor id .......something like that.
For me it was a copper NIC card DEGPA-TA. When I regenerated the kernel, it could't see it either, I kept on trying to find the differences in the /etc/sysconfigtab files before and after upgrade.
Installing patch kit 5 for Tru64 UNIX V 5.1 and regenerating a new kernel (done by patch instal process) fixed the problem and the card was seen.
In summary, Installing the latest patch kit might solve it
HTH
Mohamed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2005 05:22 AM
01-20-2005 05:22 AM
Re: Problem seeing tu1 network id
As some folks already said try booting genvmunix first and rebuilding the kernel, before you go installing patches.
From SRM:
>>> b -fl 1 -fi genvmunix
# bcheckrc
# doconfig -c NODE_NAME
(or doconfig -a)
save your old kernel
# cp -p /sys/NODE_NAME/vmunix /
#reboot
If that doesn't help, try applying the latest patches and upgrade the firmware to the latest.
HTH,
Ross