Operational Defect Database
BugZero found this defect 1098 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1017029
SASP monitor does not identify specific cause of failed SASP Registration attempt
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP LTM
Affected releases:
13.1.0
13.1.0.1
13.1.0.2
13.1.0.3
13.1.0.4
13.1.0.5
13.1.0.6
13.1.0.7
13.1.0.8
13.1.1
13.1.1.2
13.1.1.3
Fixed releases:
No fixed releases provided.
Description:
On affected BIG-IP versions, upon startup, the SASP monitor sends a single Registration Request to the SASP GWM (Group Workload Manager) to initiate monitoring of configured LTM pool members. ... This Registration Request contains all configured LTM pools (SASP Groups) and members (SASP Group Members). ... If an error is encountered by the SASP GWM with one of the SASP Groups in the request, the registration of all groups fails. ... However, the GWM does not provide any indication of *which* Group or member does not match the GWM configuration, hindering troubleshooting efforts. ... The current BIG-IP behavior does not allow identification of the specific pool/member or monitor that is misconfigured and thus responsible for the failed SASP Registration attempt. ... This behavior is defined by the SASP protocol and SASP GWM implementation. ... As a result, the SASP monitor will mark all pool members DOWN that are monitored by the SASP monitor, halting traffic from flowing to all pool...
