IC88580: SSP CONFIGURATION MANAGER NOT BINDING TO A SPECIFIC NIC

3.4.1.8-SterlingSecureProxy-Windows-if0009
3.4.1.8-SterlingSecureProxy-SolarisSPARC-if0009
3.4.1.8-SterlingSecureProxy-Linux-if0009
3.4.1.8-SterlingSecureProxy-Linux_S390-if0009
3.4.1.8-SterlingSecureProxy-HP-if0009
3.4.1.8-SterlingSecureProxy-HP-IA-if0009
3.4.1.8-SterlingSecureProxy-AIX-if0009

APAR status

• Closed as program error.

Error description

• The SSP Configuration manager is utilizing the incorrect
  communications path when accessing the Engine.  Need the
  ability to bind to a specific communication path.
  

Local fix

• adding static route to redirect traffic temporarily.
  

Problem summary

• Allow SSP Configuration Manager to bind to a specific NIC
  The Customer runs the CM on a dual-homed system with 2 network
  interface cards (NICs). Their firewall is configured to only
  allow traffic out from the secure zone on one of the NICs, but
  the CM defaults to the other.  The Customer needed a way to have
  the CM bind to the alternate NIC when connecting out to the
  engine to push a configuration.
  

Problem conclusion

• Added a field to the CM "SSP Engine Configuration" screen called
  "Local bind address", which allows the administrator to specify
  the local IP address to bind to when making the connection to
  the Engine host and port.  This optional field allows the local
  IP address as either a hostname or IP address value. When the
  screen is saved, the address is checked to make sure it is local
  to the machine and that it can be connected to.  If not, an
  error message is posted and the configuration is not saved.
  
  Delivered In:
  3.4.1.7
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels

• R341 PSY

     UP