- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Number of Trap destinations for trap forwarding
Server Management - Remote Server Management
1757003
Members
2256
Online
108858
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
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
04-12-2004 04:38 AM
04-12-2004 04:38 AM
Number of Trap destinations for trap forwarding
I have looked through RIloe and Riloe II manuals for trap Destination limitations. We are running an environment with all models of Lights Out. Please confirm Riloe can do only one trap forwarding destination. Riloe II can do three but what is the seperator (comma ?)? And ILO ?
Also a previous post quotes a manual that the LO's need to be on the same subnet or network as SIM box. True or general rule ? Thank You.
Also a previous post quotes a manual that the LO's need to be on the same subnet or network as SIM box. True or general rule ? Thank You.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2004 01:38 AM
04-16-2004 01:38 AM
Re: Number of Trap destinations for trap forwarding
John,
Riloe I supports one trap destination.
The iLO definitely supports 3 trap destinations per the xml script file. As far as what needs to separate them, I'm not sure since I usually script the values. Try a comma and see if that works.
Also,
Many companies I deal with put their iLOs and Riloes on a separate management network (i.e. a 192.168.x.x type subnet) than their servers (including SIM)are on, so putting your iLOs and Riloes on a different subnet shouldn't be an issue. These companies are still able to discover and receive traps through IM 7 or SIM as long as IM 7 or SIM have access to the management network.
Don't know if any of this helps...
Good luck,
Ed
Riloe I supports one trap destination.
The iLO definitely supports 3 trap destinations per the xml script file. As far as what needs to separate them, I'm not sure since I usually script the values. Try a comma and see if that works.
Also,
Many companies I deal with put their iLOs and Riloes on a separate management network (i.e. a 192.168.x.x type subnet) than their servers (including SIM)are on, so putting your iLOs and Riloes on a different subnet shouldn't be an issue. These companies are still able to discover and receive traps through IM 7 or SIM as long as IM 7 or SIM have access to the management network.
Don't know if any of this helps...
Good luck,
Ed
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP