HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- no LAN interfaces available in EMS
Operating System - HP-UX
1833770
Members
2638
Online
110063
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
Forums
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
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
03-14-2007 03:06 AM
03-14-2007 03:06 AM
no LAN interfaces available in EMS
Hi,
I have got a new superdome being configured; recently it was found out that LAN interfaces monitoring is not available;
it's not possible to list the lan interfaces on the host (resls - as shown below - does not give proper information; there are 4 interfaces on the host btw).
I have the following ver of ems installed (on hpux 11.11):
:/etc/opt/resmon/log#swlist -l product |grep -i ems
EMS-Config A.04.20.11 EMS Config
EMS-Core A.04.20.11 EMS Core Product
EMS-DiskMonitor A.04.20.11 EMS Disk Resource Monitor
EMS-KRMonitor A.11.11.05 EMS Kernel Resource Monitor
EMS-MIBMonitor A.04.20.11 EMS MIB Resource Monitor Product
EMS-RdbmsMon A.04.20.11 EMS Database Monitor
I found in /etc/opt/resmon/log/api.log:
-------------------Start Event--------------------
User event occurred at Wed Mar 14 14:04:23.817734 2007
Process ID: 19867 (/etc/opt/resmon/lbin/lanmond) Log Level: Error
Problem initializing resource tree
-------------------End Event----------------------
and in /etc/opt/resmon/log/registrar.log
-------------------Start Event--------------------
Event 2961 occurred at Wed Mar 14 14:04:19.005080 2007
Process ID: 19305 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired contact object for monitor /etc/opt/resmon/lbin/lanmond
-------------------End Event----------------------
#########################################
:/root#resls /net/interfaces/lan/status
Contacting Registrar on
NAME: /net/interfaces/lan/status
DESCRIPTION: LAN Interface Status
The current operational state of the interface. Possible values are:
UP The LAN interface is sending and receiving packets.
DOWN The LAN interface is not passing operational packets.
TYPE: /net/interfaces/lan/status is a Resource Class.
There are no resources configured below /net/interfaces/lan/status.
Resource Instance
#########################################
any ideas what's wrong here..? ;)
points are waiting
regards, Mariusz
I have got a new superdome being configured; recently it was found out that LAN interfaces monitoring is not available;
it's not possible to list the lan interfaces on the host (resls - as shown below - does not give proper information; there are 4 interfaces on the host btw).
I have the following ver of ems installed (on hpux 11.11):
EMS-Config A.04.20.11 EMS Config
EMS-Core A.04.20.11 EMS Core Product
EMS-DiskMonitor A.04.20.11 EMS Disk Resource Monitor
EMS-KRMonitor A.11.11.05 EMS Kernel Resource Monitor
EMS-MIBMonitor A.04.20.11 EMS MIB Resource Monitor Product
EMS-RdbmsMon A.04.20.11 EMS Database Monitor
I found in /etc/opt/resmon/log/api.log:
-------------------Start Event--------------------
User event occurred at Wed Mar 14 14:04:23.817734 2007
Process ID: 19867 (/etc/opt/resmon/lbin/lanmond) Log Level: Error
Problem initializing resource tree
-------------------End Event----------------------
and in /etc/opt/resmon/log/registrar.log
-------------------Start Event--------------------
Event 2961 occurred at Wed Mar 14 14:04:19.005080 2007
Process ID: 19305 (/etc/opt/resmon/lbin/registrar) Log Level: Error
process_time_event: Expired contact object for monitor /etc/opt/resmon/lbin/lanmond
-------------------End Event----------------------
#########################################
Contacting Registrar on
NAME: /net/interfaces/lan/status
DESCRIPTION: LAN Interface Status
The current operational state of the interface. Possible values are:
UP The LAN interface is sending and receiving packets.
DOWN The LAN interface is not passing operational packets.
TYPE: /net/interfaces/lan/status is a Resource Class.
There are no resources configured below /net/interfaces/lan/status.
Resource Instance
#########################################
any ideas what's wrong here..? ;)
points are waiting
regards, Mariusz
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP