HPE GreenLake Administration
- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- SAN switch events to SPOP via OSEM ?
Insight Remote Support
1833770
Members
2427
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
08-22-2005 08:51 PM
08-22-2005 08:51 PM
SAN switch events to SPOP via OSEM ?
Hi,
I am trying to think of a way to monitor some Mcdata switches and get any events & failures sent to the ISEE SPOP and onto HP. Someone has said that I can use OSEM to send any events from the switch to the SPOP ..is that possible and what is the configuration required ?..We use HAFM to configure and monitor the switches on the SAN fabrics but would like to get automatic messages sent to the SPOP ..any help would be appreciated.
cheers
Richard
I am trying to think of a way to monitor some Mcdata switches and get any events & failures sent to the ISEE SPOP and onto HP. Someone has said that I can use OSEM to send any events from the switch to the SPOP ..is that possible and what is the configuration required ?..We use HAFM to configure and monitor the switches on the SAN fabrics but would like to get automatic messages sent to the SPOP ..any help would be appreciated.
cheers
Richard
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2005 03:46 AM
08-24-2005 03:46 AM
Re: SAN switch events to SPOP via OSEM ?
Richard,
The information you are looking for is in OSEM Setup Guide: http://h18023.www1.hp.com/support/svctools/OSEM/osem_setup.pdf
6.7 McData Switch Systems
The HAFM server is a notebook PC with the HAFM application installed. The application
provides an interface for operating and managing the McData switch, and can forward switch event data to OSEM via HTTP.
Follow these steps to point the HAFM server to the OSEM host. The procedure includes a
restart of the HAFM server.
1. From the HAFM server, ensure that there is a working network connection to the OSEM
host.
2. Open the C:\Program Files\HAFM\rns.properties file in a text editor.
3. Look for the lines shown below:
RnsDataDir=c:\HAFMData\RnsData
RnsEventDir=c:\HAFMData\RnsData
RnsLogDir=c:\HAFMData\Rnsdata
CSGIpAddress=
CSGPort=2069
CSGExePath=/ms/eventAsync
4. Make the following changes:
CSGIpAddressâ Enter the name or IP address of the OSEM host, for example:
osemhost.abc.xyzcompany.com.
CSGPortâ Leave the default of 2069, unless you know that the OSEM host has been
reconfigured to receive messages on another port.
5. Save and close the C:\Program Files\HAFM\rns.properties file.
6. To apply the changes, restart the HAFM server. Restarting the HAFM server does not
adversely affect the operation of the director or fabric.
NOTE: OSEM uses port 2069 to communicate with a browser or 3rd party problem report generators such as MCDATA, WEBES and ENP. If a local firewall is installed (Windows XP service pack 2) and access to OSEM is desired, this port must be opened.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;308127
Hope this helps,
The information you are looking for is in OSEM Setup Guide: http://h18023.www1.hp.com/support/svctools/OSEM/osem_setup.pdf
6.7 McData Switch Systems
The HAFM server is a notebook PC with the HAFM application installed. The application
provides an interface for operating and managing the McData switch, and can forward switch event data to OSEM via HTTP.
Follow these steps to point the HAFM server to the OSEM host. The procedure includes a
restart of the HAFM server.
1. From the HAFM server, ensure that there is a working network connection to the OSEM
host.
2. Open the C:\Program Files\HAFM\rns.properties file in a text editor.
3. Look for the lines shown below:
RnsDataDir=c:\HAFMData\RnsData
RnsEventDir=c:\HAFMData\RnsData
RnsLogDir=c:\HAFMData\Rnsdata
CSGIpAddress=
CSGPort=2069
CSGExePath=/ms/eventAsync
4. Make the following changes:
CSGIpAddressâ Enter the name or IP address of the OSEM host, for example:
osemhost.abc.xyzcompany.com.
CSGPortâ Leave the default of 2069, unless you know that the OSEM host has been
reconfigured to receive messages on another port.
5. Save and close the C:\Program Files\HAFM\rns.properties file.
6. To apply the changes, restart the HAFM server. Restarting the HAFM server does not
adversely affect the operation of the director or fabric.
NOTE: OSEM uses port 2069 to communicate with a browser or 3rd party problem report generators such as MCDATA, WEBES and ENP. If a local firewall is installed (Windows XP service pack 2) and access to OSEM is desired, this port must be opened.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;308127
Hope this helps,
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