The BGP yellow highlight flashed one last time: %BGP-5-ADJCHANGE: neighbor 10.88.22.5 Up
The NOC went quiet. His boss looked over. "Fixed?" xshell highlight sets cisco
Then, two seconds later—red: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to down The BGP yellow highlight flashed one last time:
He called it "Cisco_Filter."
Simon smiled. That wasn't a routing policy error. That was a tunnel interface dropping. He jumped on the Jakarta out-of-band, issued no shut on Tunnel14, and watched his Xshell screen erupt in —his custom highlight for %LINK-3-UPDOWN and %LINEPROTO-5-UPDOWN: up . That wasn't a routing policy error
Simon leaned back, pointing at his screen—a calm sea of gray, punctuated only by quiet green lines. "The highlight set found it in four seconds. Cisco's logs are noise. Xshell makes them music."
He saved the session log, named it Jakarta_BGP_Fix.log , and closed his laptop. Another night, another flap—killed by a few clever regex rules in a terminal emulator that knew exactly what a network engineer needed to see.