Realm: shft.nhs.uk Full
shft.nhs.uk/shft-nhs-uk-0/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Bad Client Shared Secret
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-0/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 4.81 ms
- Last State Change
- Tue Jun 2 07:51:24 2026
- Last Check
- Sat Jun 6 02:11:14 2026
- Next Check
- Sat Jun 6 02:21:14 2026
shft.nhs.uk/shft-nhs-uk-0/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 07:49:08 2026
- Last Check
- Sat Jun 6 02:09:06 2026
- Next Check
- Sat Jun 6 02:19:06 2026
shft.nhs.uk/shft-nhs-uk-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 07:51:17 2026
- Last Check
- Sat Jun 6 02:11:16 2026
- Next Check
- Sat Jun 6 02:21:16 2026
shft.nhs.uk/shft-nhs-uk-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 02:12:47 2026
- Last Check
- Sat Jun 6 02:12:44 2026
- Next Check
- Sat Jun 6 02:16:44 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-0/roaming0.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Wed Jun 3 15:39:41 2026
- Last Check
- Sat Jun 6 02:09:39 2026
- Next Check
- Sat Jun 6 02:19:39 2026
shft.nhs.uk/shft-nhs-uk-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Dropping Auth Requests
/
Bad Client Shared Secret
/
Unknown Client
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-0/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 4.74 ms
- Last State Change
- Tue Jun 2 07:10:33 2026
- Last Check
- Sat Jun 6 02:10:21 2026
- Next Check
- Sat Jun 6 02:20:21 2026
shft.nhs.uk/shft-nhs-uk-0/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 08:06:08 2026
- Last Check
- Sat Jun 6 02:06:07 2026
- Next Check
- Sat Jun 6 02:16:07 2026
shft.nhs.uk/shft-nhs-uk-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 07:07:06 2026
- Last Check
- Sat Jun 6 02:07:04 2026
- Next Check
- Sat Jun 6 02:17:03 2026
shft.nhs.uk/shft-nhs-uk-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 02:07:02 2026
- Last Check
- Sat Jun 6 02:10:58 2026
- Next Check
- Sat Jun 6 02:14:58 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-0/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Fri Jun 5 12:29:07 2026
- Last Check
- Sat Jun 6 02:09:07 2026
- Next Check
- Sat Jun 6 02:19:06 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
shft.nhs.uk/shft-nhs-uk-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Bad Client Shared Secret
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-0/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 10.21 ms
- Last State Change
- Tue Jun 2 06:58:25 2026
- Last Check
- Sat Jun 6 02:08:15 2026
- Next Check
- Sat Jun 6 02:18:15 2026
shft.nhs.uk/shft-nhs-uk-0/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 08:06:10 2026
- Last Check
- Sat Jun 6 02:06:09 2026
- Next Check
- Sat Jun 6 02:16:09 2026
shft.nhs.uk/shft-nhs-uk-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 06:59:19 2026
- Last Check
- Sat Jun 6 02:09:19 2026
- Next Check
- Sat Jun 6 02:19:18 2026
shft.nhs.uk/shft-nhs-uk-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 01:26:43 2026
- Last Check
- Sat Jun 6 02:04:41 2026
- Next Check
- Sat Jun 6 02:14:39 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-0/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Jun 4 11:56:26 2026
- Last Check
- Sat Jun 6 02:06:24 2026
- Next Check
- Sat Jun 6 02:16:24 2026
shft.nhs.uk/shft-nhs-uk-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Dropping Auth Requests
/
Bad Client Shared Secret
/
Unknown Client
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-0/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 10.35 ms
- Last State Change
- Tue Jun 2 06:55:00 2026
- Last Check
- Sat Jun 6 02:04:49 2026
- Next Check
- Sat Jun 6 02:14:49 2026
shft.nhs.uk/shft-nhs-uk-0/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 06:51:01 2026
- Last Check
- Sat Jun 6 02:11:00 2026
- Next Check
- Sat Jun 6 02:21:00 2026
shft.nhs.uk/shft-nhs-uk-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 06:52:33 2026
- Last Check
- Sat Jun 6 02:12:32 2026
- Next Check
- Sat Jun 6 02:22:32 2026
shft.nhs.uk/shft-nhs-uk-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 01:31:08 2026
- Last Check
- Sat Jun 6 02:09:04 2026
- Next Check
- Sat Jun 6 02:19:04 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-0/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Fri Jun 5 07:09:38 2026
- Last Check
- Sat Jun 6 02:09:38 2026
- Next Check
- Sat Jun 6 02:19:37 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
shft.nhs.uk/shft-nhs-uk-1/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Dropping Auth Requests
/
Bad Client Shared Secret
/
Unknown Client
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-1/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 4.75 ms
- Last State Change
- Tue Jun 2 07:51:51 2026
- Last Check
- Sat Jun 6 02:11:42 2026
- Next Check
- Sat Jun 6 02:21:41 2026
shft.nhs.uk/shft-nhs-uk-1/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 07:48:55 2026
- Last Check
- Sat Jun 6 02:08:53 2026
- Next Check
- Sat Jun 6 02:18:53 2026
shft.nhs.uk/shft-nhs-uk-1/roaming0.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 07:52:16 2026
- Last Check
- Sat Jun 6 02:12:14 2026
- Next Check
- Sat Jun 6 02:22:14 2026
shft.nhs.uk/shft-nhs-uk-1/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 01:49:42 2026
- Last Check
- Sat Jun 6 02:07:38 2026
- Next Check
- Sat Jun 6 02:17:38 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-1/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Tue Jun 2 14:09:04 2026
- Last Check
- Sat Jun 6 02:09:01 2026
- Next Check
- Sat Jun 6 02:19:01 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
shft.nhs.uk/shft-nhs-uk-1/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 4.76 ms
- Last State Change
- Tue Jun 2 07:09:06 2026
- Last Check
- Sat Jun 6 02:08:56 2026
- Next Check
- Sat Jun 6 02:18:56 2026
shft.nhs.uk/shft-nhs-uk-1/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 07:10:26 2026
- Last Check
- Sat Jun 6 02:10:24 2026
- Next Check
- Sat Jun 6 02:20:24 2026
shft.nhs.uk/shft-nhs-uk-1/roaming1.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 07:07:14 2026
- Last Check
- Sat Jun 6 02:07:12 2026
- Next Check
- Sat Jun 6 02:17:12 2026
shft.nhs.uk/shft-nhs-uk-1/roaming1.govroam.uk/
Simple Authentication
- Output
- OK: Got a response but the Message Authenticator is bad
- Last State Change
- Sat Jun 6 01:40:31 2026
- Last Check
- Sat Jun 6 02:10:29 2026
- Next Check
- Sat Jun 6 02:20:29 2026
shft.nhs.uk/shft-nhs-uk-1/roaming1.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Fri Jun 5 10:46:02 2026
- Last Check
- Sat Jun 6 02:06:01 2026
- Next Check
- Sat Jun 6 02:16:01 2026
shft.nhs.uk/shft-nhs-uk-1/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Dropping Auth Requests
/
Bad Client Shared Secret
/
Unknown Client
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-1/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 10.20 ms
- Last State Change
- Tue Jun 2 06:59:07 2026
- Last Check
- Sat Jun 6 02:08:57 2026
- Next Check
- Sat Jun 6 02:18:57 2026
shft.nhs.uk/shft-nhs-uk-1/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 06:57:04 2026
- Last Check
- Sat Jun 6 02:07:02 2026
- Next Check
- Sat Jun 6 02:17:02 2026
shft.nhs.uk/shft-nhs-uk-1/roaming2.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 07:01:38 2026
- Last Check
- Sat Jun 6 02:11:36 2026
- Next Check
- Sat Jun 6 02:21:36 2026
shft.nhs.uk/shft-nhs-uk-1/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 00:23:40 2026
- Last Check
- Sat Jun 6 02:11:36 2026
- Next Check
- Sat Jun 6 02:21:35 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-1/roaming2.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Jun 4 16:55:10 2026
- Last Check
- Sat Jun 6 02:05:09 2026
- Next Check
- Sat Jun 6 02:15:08 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
shft.nhs.uk/shft-nhs-uk-1/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Dropping Auth Requests
/
Bad Client Shared Secret
/
Unknown Client
/
Port 1812 Drop
/
shft.nhs.uk/shft-nhs-uk-1/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 10.17 ms
- Last State Change
- Tue Jun 2 06:55:14 2026
- Last Check
- Sat Jun 6 02:05:04 2026
- Next Check
- Sat Jun 6 02:15:04 2026
shft.nhs.uk/shft-nhs-uk-1/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jun 2 06:51:07 2026
- Last Check
- Sat Jun 6 02:11:06 2026
- Next Check
- Sat Jun 6 02:21:06 2026
shft.nhs.uk/shft-nhs-uk-1/roaming3.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Tue Jun 2 06:50:58 2026
- Last Check
- Sat Jun 6 02:10:56 2026
- Next Check
- Sat Jun 6 02:20:56 2026
shft.nhs.uk/shft-nhs-uk-1/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Sat Jun 6 02:09:30 2026
- Last Check
- Sat Jun 6 02:13:27 2026
- Next Check
- Sat Jun 6 02:17:27 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
shft.nhs.uk/shft-nhs-uk-1/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Fri Jun 5 21:59:13 2026
- Last Check
- Sat Jun 6 02:09:11 2026
- Next Check
- Sat Jun 6 02:19:11 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
Called Station ID Check
- Output
- WARNING: 46% Lower case characters in MAC (last: 2026-06-06 01:51:32). 39% Missing SSID, as of 2026-06-06 01:51:32. 81% MAC format wrong - should use a '-' to separate hex pairs (last: 2026-06-06 01:51:32)
- Last State Change
- Tue Jun 2 06:25:14 2026
- Last Check
- Sat Jun 6 02:05:12 2026
- Next Check
- Sat Jun 6 02:20:12 2026
- Meaning:
-
The Called-Station-ID contains the MAC address of the device the client
connects to as well as, potentially, the SSID of the wireless network it
connected to. The format of the MAC address is specified in RFC
3580 as
'XX-XX-XX-XX-XX-XX:SSID' with '-' being the only valid separator and all
upper case. The SSID should be appended.
Having the Called-Station-ID included in proxied requests makes it possible to ensure that the SSID being broadcast matches the service requirements. - Solution:
- Configure your wireless system to provide the CSI in the RFC3580 format.
Calling Station ID Check
- Output
- WARNING: 81% MAC format wrong, missing separator (last: 2026-06-06 01:51:32). 46% MAC format wrong, contains lower case (last: 2026-06-06 01:51:32)
- Last State Change
- Tue Jun 2 06:27:22 2026
- Last Check
- Sat Jun 6 02:07:20 2026
- Next Check
- Sat Jun 6 02:22:19 2026
- Meaning:
- Calling Station ID identifies the device making the connection and RFC 3580 states that the format should be XX-XX-XX-XX-XX-XX (i.e. '-' separated and upper case).
- Solution:
- Configure your wireless system to use upper case and '-' separated pairs.
Operator Check
- Output
- WARNING: 37% Missing Operator-Name (last: 2026-06-05 22:04:10)
- Last State Change
- Tue Jun 2 06:24:41 2026
- Last Check
- Sat Jun 6 02:04:40 2026
- Next Check
- Sat Jun 6 02:19:39 2026
- Meaning:
- Operator-Name is missing from RADIUS requests. Operator-Name identifies the site sending the requests and is used by home sites in audit trails and in cases of mis-use.
- Solution:
- Where possible (FreeRADIUS, radsecproxy, RADIATOR) Operator-Name should be configured to send the site identifier (in the format 1realm.name e.g. 1holby.nhs.uk).
Realm Syntax Check
- Output
- CRITICAL: 1.2% Non word (a-zA-Z0-9.-) chars in realm (last: 2026-06-06 01:29:52)
- Last State Change
- Fri Jun 5 22:22:26 2026
- Last Check
- Sat Jun 6 02:07:23 2026
- Next Check
- Sat Jun 6 02:22:23 2026
- Meaning:
- The syntax of a realm proxied does not match what's acceptable. A realm should be in the format of 'realm.tld' or 'something.site.tld' and shouldn't have '..' or start or end with '.', shouldn't contain characters other than '0-9a-zA-Z-.', shouldn't be empty or missing. Since these realms are entered by end-users typos are possible. Obviously the NRPS should never see the site's own realm proxied as that could cause loops.
- Solution:
- Filter out syntactically invalid realms, don't proxy them.
VLAN Check
- Output
- OK: 100% No VLAN attr present (last: 2026-06-06 02:10:20)
- Last State Change
- Fri Jun 5 05:10:23 2026
- Last Check
- Sat Jun 6 02:10:21 2026
- Next Check
- Sat Jun 6 02:25:20 2026