Realm: nwas.nhs.uk Full
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
Dropping Auth Requests
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.93 ms
- Last State Change
- Thu Jul 3 11:55:59 2025
- Last Check
- Sun Jul 13 14:25:48 2025
- Next Check
- Sun Jul 13 14:35:48 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:54:46 2025
- Last Check
- Sun Jul 13 14:24:46 2025
- Next Check
- Sun Jul 13 14:34:45 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:54:32 2025
- Last Check
- Sun Jul 13 14:22:31 2025
- Next Check
- Sun Jul 13 14:32:31 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:53:20 2025
- Last Check
- Sun Jul 13 14:31:16 2025
- Next Check
- Sun Jul 13 14:41:16 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Jul 3 11:52:27 2025
- Last Check
- Sun Jul 13 14:30:25 2025
- Next Check
- Sun Jul 13 14:40:24 2025
- 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.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
Dropping Auth Requests
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.90 ms
- Last State Change
- Thu Jul 3 11:54:34 2025
- Last Check
- Sun Jul 13 14:24:24 2025
- Next Check
- Sun Jul 13 14:34:24 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:57:41 2025
- Last Check
- Sun Jul 13 14:27:40 2025
- Next Check
- Sun Jul 13 14:37:40 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:56:07 2025
- Last Check
- Sun Jul 13 14:24:06 2025
- Next Check
- Sun Jul 13 14:34:06 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:54:13 2025
- Last Check
- Sun Jul 13 14:22:11 2025
- Next Check
- Sun Jul 13 14:32:10 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Jul 3 11:55:52 2025
- Last Check
- Sun Jul 13 14:23:50 2025
- Next Check
- Sun Jul 13 14:33:50 2025
- 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.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
Dropping Auth Requests
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 8.55 ms
- Last State Change
- Wed Jul 9 02:23:01 2025
- Last Check
- Sun Jul 13 14:22:51 2025
- Next Check
- Sun Jul 13 14:32:51 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:55:10 2025
- Last Check
- Sun Jul 13 14:25:09 2025
- Next Check
- Sun Jul 13 14:35:08 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:55:35 2025
- Last Check
- Sun Jul 13 14:23:33 2025
- Next Check
- Sun Jul 13 14:33:33 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:55:39 2025
- Last Check
- Sun Jul 13 14:23:35 2025
- Next Check
- Sun Jul 13 14:33:35 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Sat Jul 12 21:44:43 2025
- Last Check
- Sun Jul 13 14:24:41 2025
- Next Check
- Sun Jul 13 14:34:41 2025
- 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.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
Dropping Auth Requests
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 8.32 ms
- Last State Change
- Thu Jul 3 12:00:16 2025
- Last Check
- Sun Jul 13 14:30:07 2025
- Next Check
- Sun Jul 13 14:40:07 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:57:12 2025
- Last Check
- Sun Jul 13 14:27:11 2025
- Next Check
- Sun Jul 13 14:37:11 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:56:38 2025
- Last Check
- Sun Jul 13 14:24:37 2025
- Next Check
- Sun Jul 13 14:34:37 2025
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:56:52 2025
- Last Check
- Sun Jul 13 14:24:48 2025
- Next Check
- Sun Jul 13 14:34:48 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Jul 3 11:57:03 2025
- Last Check
- Sun Jul 13 14:25:01 2025
- Next Check
- Sun Jul 13 14:35:01 2025
- 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.
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.73 ms
- Last State Change
- Thu Jul 3 11:56:09 2025
- Last Check
- Sun Jul 13 14:25:59 2025
- Next Check
- Sun Jul 13 14:35:58 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:51:53 2025
- Last Check
- Sun Jul 13 14:21:52 2025
- Next Check
- Sun Jul 13 14:31:52 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:53:55 2025
- Last Check
- Sun Jul 13 14:21:54 2025
- Next Check
- Sun Jul 13 14:31:54 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:56:28 2025
- Last Check
- Sun Jul 13 14:24:25 2025
- Next Check
- Sun Jul 13 14:34:25 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Jul 10 15:40:16 2025
- Last Check
- Sun Jul 13 14:30:14 2025
- Next Check
- Sun Jul 13 14:40:14 2025
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 3.01 ms
- Last State Change
- Thu Jul 3 11:54:49 2025
- Last Check
- Sun Jul 13 14:24:39 2025
- Next Check
- Sun Jul 13 14:34:39 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:58:04 2025
- Last Check
- Sun Jul 13 14:28:03 2025
- Next Check
- Sun Jul 13 14:38:03 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:56:05 2025
- Last Check
- Sun Jul 13 14:24:06 2025
- Next Check
- Sun Jul 13 14:34:04 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:56:08 2025
- Last Check
- Sun Jul 13 14:24:05 2025
- Next Check
- Sun Jul 13 14:34:05 2025
- 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).
nwas.nhs.uk/nwas-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
- Thu Jul 3 11:55:25 2025
- Last Check
- Sun Jul 13 14:23:24 2025
- Next Check
- Sun Jul 13 14:33:24 2025
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 7.15 ms
- Last State Change
- Thu Jul 3 11:58:29 2025
- Last Check
- Sun Jul 13 14:28:19 2025
- Next Check
- Sun Jul 13 14:38:19 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Fri Jul 11 22:40:34 2025
- Last Check
- Sun Jul 13 14:30:32 2025
- Next Check
- Sun Jul 13 14:40:32 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:56:30 2025
- Last Check
- Sun Jul 13 14:24:28 2025
- Next Check
- Sun Jul 13 14:34:28 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 11:57:42 2025
- Last Check
- Sun Jul 13 14:25:39 2025
- Next Check
- Sun Jul 13 14:35:39 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Jul 3 11:59:19 2025
- Last Check
- Sun Jul 13 14:27:17 2025
- Next Check
- Sun Jul 13 14:37:17 2025
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Port 1812 Drop
/
Bad Client Shared Secret
/
Unknown Client
/
Dropping Auth Requests
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 7.63 ms
- Last State Change
- Thu Jul 3 11:59:03 2025
- Last Check
- Sun Jul 13 14:28:53 2025
- Next Check
- Sun Jul 13 14:38:53 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Jul 3 11:59:04 2025
- Last Check
- Sun Jul 13 14:29:03 2025
- Next Check
- Sun Jul 13 14:39:03 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Jul 3 11:58:49 2025
- Last Check
- Sun Jul 13 14:26:47 2025
- Next Check
- Sun Jul 13 14:36:47 2025
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Jul 3 12:00:41 2025
- Last Check
- Sun Jul 13 14:28:37 2025
- Next Check
- Sun Jul 13 14:38:37 2025
- 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).
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Jul 3 11:57:23 2025
- Last Check
- Sun Jul 13 14:25:21 2025
- Next Check
- Sun Jul 13 14:35:21 2025
- 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
- UNKNOWN: No Data
- Last State Change
- Tue Jul 1 19:58:42 2025
- Last Check
- Sun Jul 13 14:28:42 2025
- Next Check
- Sun Jul 13 14:43:41 2025
Calling Station ID Check
- Output
- UNKNOWN: No Data
- Last State Change
- Fri Jun 13 10:32:07 2025
- Last Check
- Sun Jul 13 14:27:04 2025
- Next Check
- Sun Jul 13 14:42:04 2025
Operator Check
- Output
- UNKNOWN: No data
- Last State Change
- Fri Jun 13 10:31:12 2025
- Last Check
- Sun Jul 13 14:26:10 2025
- Next Check
- Sun Jul 13 14:41:09 2025
Realm Syntax Check
- Output
- UNKNOWN: No data
- Last State Change
- Tue Jul 1 19:57:17 2025
- Last Check
- Sun Jul 13 14:27:16 2025
- Next Check
- Sun Jul 13 14:42:14 2025
VLAN Check
- Output
- UNKNOWN: No Data
- Last State Change
- Fri Jun 13 10:30:06 2025
- Last Check
- Sun Jul 13 14:25:04 2025
- Next Check
- Sun Jul 13 14:40:04 2025