ServiceNow discovery and service mapping

Hello,

F5 introduced additional security controls for REST tokens in newer releases. One common issue is that a token becomes tied to the client IP that created it. If a token is generated from one source and reused from another, BIG-IP can return 401 Unauthorized. I've seen integrations break after upgrades because of this behavior change. If ServiceNow/MID is tokenizing credentials and then reusing tokens unexpectedly, this is worth investigating in the BIG-IP logs.

Useful logs:

Shell

1

/var/log/restjavad.*

2

/var/log/httpd/httpd_errors

Show more lines

Look for authentication failures or token client mismatch messages, if all ok try to restart below services .

bigstart status restjavad

bigstart status restnoded

Also please add service now IPs in httpd allow, if you have any blocking in management IP.