- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Server CIMS error report
Operating System - HP-UX
1820478
Members
2989
Online
109624
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
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
06-09-2006 05:17 AM
06-09-2006 05:17 AM
Server CIMS error report
CIMS Report: Please check the arsap_nightly.logCIMS diagnostics menu
Please Select:
1. Ping a server to see if it is up
2. See if cims is still running on a server (blank if no processes found)
3. View the CIMS log (arsap_nightly.log) press enter for next page
4. Check space on a server /cims dir
5. Check latest cims history dates (should be an *.ftp.log for today)
6. Review files transfered to collector, should be 2 for today
0. Exit
Select by pressing a number and then ENTER
1
Which server to ping hostname
PING hostname.company.com: 64 byte packets
64 bytes from 170.120.6.14: icmp_seq=0. time=0. ms
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
Press Enter
Fri Jun 9 07:20:13 CDT 2006
Select by pressing a number and then ENTER
2
Which server to check cims processes on hostname
Password:
Could not chdir to home directory /ahome/tape_op: No such file or directory
Press Enter
Select by pressing a number and then ENTER
3
please suggest?
Please Select:
1. Ping a server to see if it is up
2. See if cims is still running on a server (blank if no processes found)
3. View the CIMS log (arsap_nightly.log) press enter for next page
4. Check space on a server /cims dir
5. Check latest cims history dates (should be an *.ftp.log for today)
6. Review files transfered to collector, should be 2 for today
0. Exit
Select by pressing a number and then ENTER
1
Which server to ping hostname
PING hostname.company.com: 64 byte packets
64 bytes from 170.120.6.14: icmp_seq=0. time=0. ms
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
Press Enter
Fri Jun 9 07:20:13 CDT 2006
Select by pressing a number and then ENTER
2
Which server to check cims processes on hostname
Password:
Could not chdir to home directory /ahome/tape_op: No such file or directory
Press Enter
Select by pressing a number and then ENTER
3
please suggest?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2006 06:05 AM
06-09-2006 06:05 AM
Re: Server CIMS error report
This is our Daily CIMS REPORT .
The following was this morning message: Please check the arsap_nightly.logCIMS diagnostics menu
The following listed below is through our CIMS REPORT TROUBLESHOOTING PROCEDURES.
This is ran through the CIMS diagnostic menu.
The following was this morning message: Please check the arsap_nightly.logCIMS diagnostics menu
The following listed below is through our CIMS REPORT TROUBLESHOOTING PROCEDURES.
This is ran through the CIMS diagnostic menu.
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP