The Link Is Up

A field procedure for restoring a failed route becomes a rescue story about what a green status light can’t tell you.

The Link Is Up

The Link Is Up

Field procedure 12-B: Restore interstation routing after a failed transfer

Applies to: paired relay stations separated by terrain, vacuum, or budgetary optimism.

Personnel: one network technician at each station, or one technician and one recorded voice.

Tools: console access, test set, insulated driver, current route table, patience.

1. Confirm the complaint

At 02:13 station Hush reported that the north relay was unreachable. At 02:14 station North answered a ping from Hush. At 02:15 the rescue capsule carrying Hush’s night crew began its return burn without clearance to dock.

The capsule had one pilot. Her name was Iven Sato. She was also the only person aboard who knew that Hush’s outer door had frozen half-open.

At North, technician Pell read the report twice.

“Reachable,” said the station computer.

“Then why can’t I reach it?” Pell asked.

The computer did not consider this a contradiction.

Enter the interface status command. Confirm that the serial interface reports up/up.

Do not interpret this result as proof that the network is working.

The first up indicates that a physical signal is present. The second indicates that the data-link protocol is communicating. Neither status certifies that the two stations agree on where the rest of the network is.

At 02:19 Hush’s link still reported up/up. Its small green indicator remained lit beside a strip of tape bearing the handwritten label NORTH—DO NOT RESET.

Pell called the capsule.

“I have your beacon,” she said.

“You have my ping,” Iven replied. “The dock never got the approach vector.”

“Can you hold position?”

“For a while.”

“How long is a while?”

“The manual kind or the actual kind?”

Pell looked at the status light. “I’ll call you back.”

3. Test the far interface

Send a test packet to the far-end address. If the test succeeds, record the result. Do not close the incident.

On a point-to-point link using PPP, a host route may allow each station to reach the other station’s interface address even when the two interface addresses are configured in different subnets. The test packet can succeed while routing protocols fail to exchange network routes.

A successful ping proves that a packet made a round trip. It does not prove that either station knows how to get anywhere else.

At 02:27 Hush answered five out of five packets. North had a route to Hush’s interface, and Hush had a route to North’s. Neither station had a route to the docking ring.

Pell opened the configuration archive. The current address on North was 172.19.6.1. Hush was configured as 172.19.7.2. Both carried a mask of 255.255.255.0.

The link was carrying two correct addresses that did not belong together.

4. Check route exchange

Compare the neighbor table and the advertised routes. Confirm that the routing protocol has established a neighbor relationship and is exchanging the required networks.

If the interface is up/up and the far-end ping succeeds but no routes appear, continue troubleshooting. Do not replace the cable solely because the network is failing. A cable may be innocent, a rare condition that should be documented.

At 02:31 the route table contained the two host routes and nothing beyond them. The docking ring’s approach network was absent.

Pell checked the change log. The subnet on North had been altered three months earlier during a maintenance window. The technician had tested the interface ping, received five exclamation marks, and closed the ticket.

In the margin someone had written: Looks good.

Pell recognized the handwriting. It was hers.

5. Identify the last known working configuration

Review saved configurations and change records. Confirm the correct network assignment with the responsible station before making changes.

Do not assume that a successful test at one layer validates a change at another layer.

Pell found the old plan in a directory named FINAL, beneath two directories named FINAL-NEW and FINAL-NEW-USE-THIS. The approved subnet was 172.19.6.0/24. The new address on Hush had been copied from a temporary test network.

She opened a voice channel.

“I made this change,” she told Iven.

“You made the address change?”

“I signed off on the test.”

“Did you know it was wrong?”

“No.”

“Do you know how to make it right?”

“Yes.”

“Good. The capsule’s getting cold.”

6. Correct the addressing mismatch

Coordinate both ends of the point-to-point link. Apply addresses from the same subnet. Verify the mask. Confirm encapsulation and authentication before restoring route exchange.

Pell set North to 172.19.6.1/24. Iven, reading from the maintenance card taped beside Hush’s console, set the far interface to 172.19.6.2/24.

For three seconds, the neighbor table remained empty.

Then a new line appeared.

NEIGHBOR 172.19.6.2: ESTABLISHED

The docking ring’s network arrived in the route table. The approach vector followed it. On the display, a thin green line extended from Hush to the ring, then out to the capsule, which was not a network device but had become the most important endpoint in the system.

Pell sent the route.

Iven read it back. “Received.”

“Can you dock?”

“I can try.”

7. Verify service end to end

Test the destination that matters, not merely the nearest device that answers.

At 02:46 the capsule aligned with the ring. At 02:49 Iven reported contact. At 02:52 the outer door sensor changed from OPEN—FROZEN to CLOSED.

Hush’s alarm cleared. The capsule’s docking indicator turned green.

Pell watched the route table settle. She waited for the computer to congratulate itself. It did not. It had already filed the event as a successful transmission.

8. Closeout

Record the root cause, corrective action, and final verification. Preserve the configuration archive. Do not erase the failed test simply because service has been restored.

At 03:07 Iven called from the capsule hatch.

“You still there, Pell?”

“Yes.”

“I’m writing the maintenance report.”

“Put down that the link was up.”

“It was.”

“Put down that the route was missing.”

“I will.”

“And put down that I answered.”

A pause. Then the faint scrape of a pen.

“Answered,” Iven said.

Pell left the incident open until morning. The status panel showed green on both ends. This time she knew what the green meant, and what it did not.

End of procedure.