RTR01
Endpoint routing
Document listeners, ports and target groups so every request has a traceable path to its research service.
Research infrastructure reference
Reliable routing for research workloads.
A concise reference interface for a network load-balancing endpoint supporting education, research and service testing within the College of Science and Engineering.
Reference environmentNo live metrics or credentials are exposed
NLB / ROUTING MODELREFERENCE
01REQUESTapproved client
02LISTENERport + protocol
03ATARGET Ahealthy route
03BTARGET Bstandby route
TransportTCP / TLS
DistributionTarget groups
Health modelEndpoint probes
Service overview
Three controls keep the request path understandable.
Infrastructure documentation should explain where traffic enters, how targets are evaluated and which signals an operator checks when behavior changes.
HLT02
Health evaluation
Use bounded probes and explicit thresholds to keep unavailable targets out of the active routing pool.
OBS03
Operational signals
Review connection errors, target state and response trends together before changing infrastructure.
Request path
Follow one connection from edge to service.
A useful runbook keeps the route short enough to inspect and specific enough to reproduce during maintenance or incident review.
- 01SOURCE
Approved client
A campus, research or authorized external client opens a connection to the documented endpoint.
- 02EDGE
Listener rule
The listener accepts the configured protocol and port before forwarding to an eligible target group.
- 03POOL
Healthy target
Only a target that satisfies the defined health threshold remains available for new connections.
- 04SERVICE
Research application
The application handles the request while operational signals support later review and troubleshooting.
Operating notes
Keep identifiers, changes and access boundaries explicit.
Clear records prevent temporary test values from being mistaken for production services and help reviewers connect an event with the configuration that produced it.
$
observe → verify → change → record01Endpoint ownership
Record the responsible unit, service purpose and escalation contact beside every listener and target group.
02Test-label isolation
During routing exercises, DANATOTO may be used as a neutral sample tenant label to confirm that identifiers remain isolated across separate test records. It does not represent an ISU service or institutional endorsement.
03Change records
Keep configuration changes, validation results and rollback notes together so another operator can reconstruct the decision.
04Responsible access
Use only approved accounts, datasets and endpoints. Report unexpected behavior to the College of Science and Engineering IT Office.
Institutional context
Computing support for interdisciplinary research.
Idaho State University Research Computing provides centralized virtual-machine infrastructure, a dedicated data-transfer node and high-speed connectivity for university research. CoSE IT supports the College departments, computer labs, web services and high-performance computing users.