NOTE: This post is not intended for the regular audience of Sector 930. It is intended to be crawled by Google, and save a lot of some other poor schmuck’s time.
I have been spending a lot of time with CIsco’s train wreck of a network management suite, Ciscoworks. It’s currently installed on a Windows server, along with Kiwi, a widely used syslog server. While these two products normally could work well together, they were both trying to listen on the same port for syslog traffic (the industry default of 514.) Ciscoworks won the battle, and Kiwi wasn’t getting any traffic. After futzing for hours over this, I found the easiest solution would be to change the port Ciscoworks was listening on. Nowhere in the Ciscoworks GUI could I find how to change this, so after more digging, I found the registry key:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/crmlog/Paramaters/CrmLogPort/
The value is stored in hex, so to change the port from 514 to 515, change the registry value from 202 to 203.
Usually making changes in the registry is a bad idea, especially on a production server, so make sure you know what you’re doing when you do this. I assume no liability for anything. Also, I am aware that this solution is a hackjob, and am open to other ideas.
