- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: EMS lan monitoring problem
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
05-11-2005 10:13 PM
05-11-2005 10:13 PM
EMS lan monitoring problem
I'm experiencing a problem with EMS monitoring tool.
When I try to add a monitoring resource such as a lan card I get following messages(via sam-->Other Resources or via emscli command):
------------------------
emscli -a /net/interfaces/lan/status
Adding request ...
Error : /net/interfaces/lan/status is not a valid resource instance.
Error : failed to register request.
------------------------
Attached my server network configuration.
Anyone know how can I solve that issue?
Thank you very much to everybody.
I.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 10:26 PM
05-11-2005 10:26 PM
Re: EMS lan monitoring problem
Did you try using monconfig to add the device??
Regards,
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 10:29 PM
05-11-2005 10:29 PM
Re: EMS lan monitoring problem
Regards,
I.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 10:57 PM
05-11-2005 10:57 PM
Re: EMS lan monitoring problem
Do you have the latest Online Diag/ HW Enablement patches (HWEnable11i)installed?
Regards,
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2005 02:13 AM
05-12-2005 02:13 AM
Re: EMS lan monitoring problem
If so, there are specific steps to get the EMS stuff going again.
2 documents to get and read.
DocID UXEMSKBRC00003120
Cannot Create a LAN monitor - "no resources configured"
DocID KBRC00012590
Resource /system/numUsers not available
These are available in the Knowledge base.
Don't let the titles throw you, there are many additional resources that are probably affected by the change as well.
My guess is that the get community name is changed from the default of public.
You need to tell the monitors what the new name is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2005 01:55 AM
05-16-2005 01:55 AM
Re: EMS lan monitoring problem
The name you have given is incomplete. You need to select an instance of the path. E.g. on my machine I need to do:
emscli -a /net/interfaces/lan/status/HP
otherwise I get the same result as you.
Note that 'emscli -r' will list all the resource instances available for monitoring.
You can also specify a wild-card.
'man emscli' gives the full details.
Andrew