CMDB Discovery of Linux Servers using TCP 22 and a second port.

[Ron D_]

CMDB Discovery uses the industry standard TCP 22 for Linux servers.  We use TCP 22, but also use a second port for SSH on Linux servers. Is there a way of adding this additional port as a second avenue for the Discovery of Linux servers? We want Linux to be recognized over two ports.

[doug_schulze]

You can add an additional IP service, take a look at the vmapp port probe for an example...not sure it will actually run on the second port but I've never tried it. Let us know what you find out..

[Ron D_]

Thanks for responding as you helped point me in correct direction.  In Discovery Definitions>IP Services, "ssh" was configured for TCP 22.  This was changed to our custom port and voila, the fields populate.

The doc has a "Caution:" pertaining to custom ports.

https://docs.servicenow.com/bundle/london-it-operations-management/page/product/credentials/task/t_C...

Attempted to get it working with two rules, one rule for TCP 22 and one for our custom port, but that didn't work.  End result, one that has the custom port configured.

Will continue to research getting things to Discover with both ports, respectively.

Thanks.

Ron

[Pravin17]

Hi Ron,

Is this issue fixed? I am also facing similar issue for SNMP where we using two ports 161 & 5161 but discovery works for any one port even if we add two. Any suggestion. 

Regards,

Pravin

[Ron D_]

Go into Discovery Definition.  You will be working with IP Services and Port Probes.  In IP Services you already have a service for snmp.  Create a new one named snmp2 and configure with 5161.

In Port Probes, open snmp. To the right is "triggered by services".  Click the lock to open,,,,browse and add snmp2, Update.

That should do it.

Ron