- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Monthly config report caused vmunix messages??
Operating System - HP-UX
1753562
Members
6430
Online
108796
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО08-01-2008 08:36 AM
тАО08-01-2008 08:36 AM
I have been running a system config report on our production HP-UX box for several years. This morning for some reason it caused several vmunix messages to appear in the syslog, that hasn't happened before. Everything on the system seems to be functioning normally, and there's no EMS alerts logged.
Here's the report. I think the ioscan -fn is what triggered the messages.
TODAY=`date`
echo 'Maintenance log for' $TODAY
ioscan -fn -Cdisk
vgdisplay -v
ioscan -fn
lvlnboot -v
cat /etc/fstab
bdf
swapinfo
ioscan -f
ioscan -kf
/opt/ignite/bin/print_manifest
Here's the messages from the syslog. The device at that address is a VTL, attached fibre channel.
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0.1 schgr
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0.1 schgr
Aug 1 06:17:22 saifprod LVM[6449]: lvlnboot -v
Can you think of any reason this would happen? Do you think I have a genuine problem here?
Thanks,
Tim
Here's the report. I think the ioscan -fn is what triggered the messages.
TODAY=`date`
echo 'Maintenance log for' $TODAY
ioscan -fn -Cdisk
vgdisplay -v
ioscan -fn
lvlnboot -v
cat /etc/fstab
bdf
swapinfo
ioscan -f
ioscan -kf
/opt/ignite/bin/print_manifest
Here's the messages from the syslog. The device at that address is a VTL, attached fibre channel.
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.3.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/0.2.4.255.0.0.1 schgr
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0 fcd_vbus
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.3.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0 tgt
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0.0 stape
Aug 1 06:15:23 saifprod vmunix: 0/2/1/1.2.4.255.0.0.1 schgr
Aug 1 06:17:22 saifprod LVM[6449]: lvlnboot -v
Can you think of any reason this would happen? Do you think I have a genuine problem here?
Thanks,
Tim
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2008 11:42 PM
тАО08-01-2008 11:42 PM
Solution
Hi,
these messages may be due to ioscan.
Some tape drive (may be fc tape library) attached to your server & you are not run ioscan for long time. now you are running ioscan in your monthly report, so it is scanning & detecting the new device.
Pls check ioscan -fnC tape
these messages may be due to ioscan.
Some tape drive (may be fc tape library) attached to your server & you are not run ioscan for long time. now you are running ioscan in your monthly report, so it is scanning & detecting the new device.
Pls check ioscan -fnC tape
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2008 11:59 PM
тАО08-01-2008 11:59 PM
Re: Monthly config report caused vmunix messages??
Hi Tim,
The message says device (library,0/2/1/0.2.3.255.0) was not maped before to the OS and the last ioscan has been maped the devices and updated /etc/ioconfig file
Confirm whether the device files are existing for the libraries if not create using insf.
Aneesh
The message says device (library,0/2/1/0.2.3.255.0) was not maped before to the OS and the last ioscan has been maped the devices and updated /etc/ioconfig file
Confirm whether the device files are existing for the libraries if not create using insf.
Aneesh
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP