Security Compliance

Unable to access SEM using SSH

If you cannot access SEM using PuTTY or another SSH client, it can be caused by the following settings: incorrect port, firewall, or SEM service settings.

First published date

10/18/2018 7:57 PM

Last published date

10/18/2018 7:57 PM

Overview

When you cannot access Security Event Manager (formerly Log & Event Manager) using PuTTY or another SSH client, verify that you have opened the correct port, that the firewall does not block the access, and your SEM service settings.

If you do not know the cmc password, open a ticket with SEM Technical Support.

Product section

Security Event Manager

Cause

This can occur because of the following:

  • Incorrect Port
  • Firewall configuration
  • SEM service settings

Resolution

Verify that you have configured your environment correctly:

  • Incorrect Port: Verify that the port used for SSH in SEM is 32022 or 22 (if SEM is 6.2.1 or earlier, only port 32022 is open)
  • Firewall: Verify that your Firewall allows SSH communication to the SEM appliance on port 32022.
  • SEM Service settings: Make sure that SSH has not been disabled on the SEM appliance.
    This policy can be implemented for regulation compliance, Auditing and/or Security purposes.