I am just about to setup new IOS XR devices (ASR 9901 and NCS 540) and I am encountering a silly problem : when connecting to the devices with SSH from a mac os x client, all the terminal keys are disabled and not recognized (arrow keys, cli completion, ...).
With the same terminal client and using the serial console, the problem is not present.
Also from the same terminal client, if I ssh to a linux host and then ssh to the XR device, the problem is not present.
So it seams that using a SSH session from a macos X client trigger something on the IOS XR side that disable all vt100 key recognition.
The problem is not present when accessing classical IOS devices.
Re: ssh from macos disable cli completion (Solved)
When I connect, I get the following errors :
mbagr:.ssh arichard$ ssh firstname.lastname@example.org Password: Warning: No xauth data; using fake authentication data for X11 forwarding. X11 forwarding request failed on channel 0 PTY allocation request failed on channel 0
So the problem here seam to be "PTY allocation request failed on channel 0".
Looking at my .ssh config file, I found out that I was using the following options :
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"
It's been a long standing ask for XR to support conditional route advertisements in BGP.
The expected option of using the
option in RPL currently can only be used at the default-inf...
On IOS-XR, Quality of Service has an extension to WRED (Weighted Random Early Detection) called Explicit Congestion Notification (ECN). ECN will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When c...
Technical Guide to Pre-Defined NAT.
In traditional NAT, due to the government regulations logging the CGN translations is mandatory and this is a huge cost incurrence. In Pre-defined NAT, the translations are known upfront, hence there is no nee...