HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- HP Gbe2 syslog header format
Switches, Hubs, and Modems
1833883
Members
1839
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
12-20-2010 05:47 AM
12-20-2010 05:47 AM
HP Gbe2 syslog header format
I have recently configured a Gbe2 chassis switch to log to a syslog-ng server. The syslog-ng config uses filters with the IP addresses of the devices which are then used as the logfile names, e.g. 10.0.0.1.log.
No logfiles are being generated for the Gbe2 log messages. The traffic arrives but after running syslog-ng in debug mode it is not matching the filter.
After looking at some tcpdumps in more detail I can see that the switch IP address is not being supplied in the syslog header as normal.
Here is a normal syslog header received from a Procurve 2810 which logs with no problems:
Syslog message: USER.INFO: Dev 20 12:31:37 10.0.0.1 mgr: SME TELNET
Here is a syslog header received from a Gbe2:
Syslog message: LOCAL1.NOTICE: Dec 20 13:07:28 NOTICE Gbe2 Switch OS
The Gbe2 puts the severity type ('notice' in this case) where the hostname / IP should be.
Has anyone ever experienced this? Is there a way to make the Gbe2 supply its IP address in the syslog headers it sends?
Thanks.
No logfiles are being generated for the Gbe2 log messages. The traffic arrives but after running syslog-ng in debug mode it is not matching the filter.
After looking at some tcpdumps in more detail I can see that the switch IP address is not being supplied in the syslog header as normal.
Here is a normal syslog header received from a Procurve 2810 which logs with no problems:
Syslog message: USER.INFO: Dev 20 12:31:37 10.0.0.1 mgr: SME TELNET
Here is a syslog header received from a Gbe2:
Syslog message: LOCAL1.NOTICE: Dec 20 13:07:28 NOTICE Gbe2 Switch OS
The Gbe2 puts the severity type ('notice' in this case) where the hostname / IP should be.
Has anyone ever experienced this? Is there a way to make the Gbe2 supply its IP address in the syslog headers it sends?
Thanks.
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