- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Remote syslog over TLS from ProCurve 5400zl series...
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
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
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
12-02-2016 12:31 PM
12-02-2016 12:31 PM
Remote syslog over TLS from ProCurve 5400zl series switch
I am having an issue finding documentation to resolve a setup issue I am having - trying to get remote syslog over TLS working from a ProCurve 5400zl switch.
I use the command: logging <ip address> tls <port>
but end up with log entries on the switch:
I 12/02/16 10:41:53 04331 mgr: syslog: Information logging started on the SYSLOG
server <ip address> over TLS protocol
W 12/02/16 10:47:51 00472 ssl: SSL Syslog TLS failed: no certificate present
The docs for that feature don't mention certificate requirements, so I tried adding the root CA and intermediate certs of the syslog receiver as ta-profiles, but that didn't help. I also tried with a self signed cert on the syslog receiver end, and added that cert through a ta-profile, but that didn't resolve the issue either.
I have an open support ticket, but so far, I don't think the tech understands the issue, so I'm reaching out to the community as well.
Thanks!
- Tags:
- syslog