Reset Search
 

 

Article

Cannot Telnet From a XOS Switch to a Created VRF on an EOS Switch

« Go Back

Information

 
TitleCannot Telnet From a XOS Switch to a Created VRF on an EOS Switch
Symptoms
  • Created VRF on XOS switch replies to ping from EOS created VRF
  • Telnet from EOS switch created VRF to created VRF on XOS times out

PING 192.168.66.21 (192.168.66.21) 64 bytes of data.
64 bytes from 192.168.66.21: icmp_seq=0 ttl=64 time=2.61 ms
64 bytes from 192.168.66.21: icmp_seq=1 ttl=64 time=2.12 ms
64 bytes from 192.168.66.21: icmp_seq=2 ttl=64 time=3.10 ms
64 bytes from 192.168.66.21: icmp_seq=3 ttl=64 time=1.86 ms

--- 192.168.66.21 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3007 ms
rtt min/avg/max = 1/2/3 ms
global(su-bgp2)->telnet 192.168. .66.21
Trying 192.168.66.21...
Unable to connect to remote host: Operation timed out
Environment
  • Summit
  • S-Series
  • BlackDiamond
Cause
The EOS switch will not source the telnet from the IP of the interface on the created VRF because that VRF cannot be managed, by design.  
Resolution
Take a trace to determine from which IP the EOS switch is sourcing the telnet, and configure a static route on the XOS switch pointing to that subnet with the EOS switch created VRF IP local to the XOS switch as the next hop.
BD-8806.6 # conf ipr add default 192.168.66.1 vr "vrf-Prod"
 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255