HMC

HMC & CMC

Connect, learn, share, and engage with IBM Power.

 View Only

  • 1.  syslog to other than default port 514

    Posted Thu September 08, 2016 04:38 PM

    Originally posted by: The_Doctor


    Is there a syntax problem with (for example): 

    • chhmc -c syslog -s add -a 172.96.96.57:537

    • chhmc -c syslog -s add -a 172.96.96.57:514

    Documentation at http://www.ibm.com/support/knowledgecenter/8286-42A/p8edm/chhmc.html 

    shows the [:port] as being valid yet the :537 or :514 (above) seems to be rejected.

    FWIW, this works ok... 

    • chhmc -c syslog -s add -a 172.96.96.57

    This test was run on HMC at v8.8.4.0.1

     

    Functioning as designed, defect, or a typo on my part ?  Thx.



  • 2.  Re: syslog to other than default port 514

    Posted Tue September 13, 2016 01:21 AM

    Originally posted by: D.R.Saravanan


    Thanks for reporting this issue. Recently one another customer also reported the same issue & the development team is working on to fix this issue.

    This is a defect & you will be receiving a fix for the same in the future update. 

     



  • 3.  Re: syslog to other than default port 514

    Posted Tue September 13, 2016 03:05 AM

    Originally posted by: D.R.Saravanan


    Based on further discussion, the function behaves as expected and the documentation need to be updated to ensure that option of specifying port number will be removed.

    At the same time I would like to understand from you whether you have a need to specify custom port (other than the default port number), if yes kindly let me know the usecase. 

     



  • 4.  Re: syslog to other than default port 514

    Posted Wed September 14, 2016 03:14 PM

    Originally posted by: The_Doctor


    Recently one another customer also reported the same issue

    lol, chances are I'm that customer, as I do have a PMR open on this.

     

    Let's just say I'm disappointed that development has chosen to change the documentation to reflect the reduced function..... particularly when the underlying product "rsyslog" is documented as supporting the syntax of xx.xx.xx.xx:PPP.  If the end user (me) could only edit the files in /etc/rsyslog.d/ we'd be done :) 

     

    Anyway, moving on:

    • my peers & I agreed to a workaround..... we'll use a firewall & port forwarding to change the port # from 514 to what we are looking for.

    With respect to a use case:

    • our HMC is forwarding syslog records to a 3rd party that does monitoring for us, 24/7
    • the 3rd party asked us to use a port # other than the default # 514, since (I assume) they wanted our traffic isolated in some way (sorry, I'm not privy to the exact details)
    • the workaround, using a firewall and port forwarding accomplishes the same thing

    Thanks for considering and for taking the time to respond.

     



Related Content