IC88580: SSP CONFIGURATION MANAGER NOT BINDING TO A SPECIFIC NIC
Direct links to fixes
Closed as program error.
The SSP Configuration manager is utilizing the incorrect communications path when accessing the Engine. Need the ability to bind to a specific communication path.
adding static route to redirect traffic temporarily.
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.
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: 22.214.171.124
Reported component name
STR SECURE PROX
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR SECURE PROX
Fixed component ID
Applicable component levels
Translate this page: