- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE test email syntax
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
тАО01-19-2005 07:40 AM
тАО01-19-2005 07:40 AM
What is the correct syntax or method for sending a test?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 08:16 AM
тАО01-19-2005 08:16 AM
Re: ISEE test email syntax
This must be the test syntax.
/opt/resmon/bin/send_test_event disk_em
tail of callout.log shows entry as below for this test at 4:10pm on 1/19. But I don't see anything in my isee open cases when I log on to
#tail callout.log
Getting maximum callout log file size
Maximum callout log file size is 100000
Determining length of current Log File
Length of current Log File is 17800
Returned from trimCalloutLog
Attempting to load the list of allowed scripts
Loading the list of allowed scripts
RemoteSupport script firstSync will be allowed to run when called
PreSync: contactIDsBONNIETEMPLEBTEMPLE@abc.COMISEE.AMERICAS.HP.COM=BONNIETEM
PLEBTEMPLE@abc.COMISEE.AMERICAS.HP.COM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 08:40 AM
тАО01-19-2005 08:40 AM
Re: ISEE test email syntax
190105 16:27:50.550 ERROR,[WebServer] WebServer exception:
190105 16:27:50.551 ERROR,[WebServer] NetworkException (1): socket.cpp:374 (232)
Connection reset by peer Socket::read(): recv() failed [[172.30.14.46]]
190105 16:27:52.019 ERROR,[WebServer] WebServer exception:
190105 16:27:52.019 ERROR,[WebServer] NetworkException (15): unexpected eof
Where do I go from here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 09:28 AM
тАО01-19-2005 09:28 AM
Re: ISEE test email syntax
1. You cannot send mail for testing, ISEE doesn't send mail to HP, it only sends the incidents to HP through port 80 (http).
2. You can send /opt/resmon/bin/send_test_event disk_em, but in your case, it doesn't seem to work. Could this be a firewall issue?
When you logon to
If you don't see this, then
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2005 10:54 PM
тАО01-19-2005 10:54 PM
Re: ISEE test email syntax
Forgive me if you have already verified this, but as a first step to diagnose the issue I would suggest that you browse to the ISEE content server directly from the HP9000 host.
The URL would be:
http://isee.
Where region is: americas, europe, or asiapac.
Note: If the host does not support a browser then you can use a browser on a pc located on the SAME subnet as the host.
If you can't reach the content server the next thing to do is try nslookup -- again from the host. Frequently, the issue can be traced to name resolution. If the name doesn't resolve make an entry in the /etc/hosts file.
If nslookup succeeds I would suspect proxy issues.
Take care,
frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 01:26 AM
тАО01-20-2005 01:26 AM
Re: ISEE test email syntax
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 03:21 AM
тАО01-20-2005 03:21 AM
Re: ISEE test email syntax
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 03:25 AM
тАО01-20-2005 03:25 AM
Re: ISEE test email syntax
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 05:42 AM
тАО01-20-2005 05:42 AM
SolutionThe next thing to do is test the ISEE client software itself. Use the following test script, which should generate a "Testing connectivity" incident:
# /opt/hpservices/RemoteSupport/bin/iseeConnectivityTest.sh
1545807970.6@rtcuss
Note: If the command generated a test incident you should see an incident key similar to 1545807970.6@yourhostname
Browse back to the server and verify you can see the incident in ISEE.
If not I would return to the server and do an nslookup on isee.americas.hp.com.
Also a ps -ef | grep mad to establish the client software is running.
Take care,
frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2005 06:35 AM
тАО01-20-2005 06:35 AM
Re: ISEE test email syntax
I guess I was running the wrong test with the opt/resmon/...teset_disk_em ?
Thanks Frank!
Bonnie