问题

在使用NE40e后，SSH Session中通过“上”、”下”回滚长命令总会遇到显示问题，必须多按几个回车才能刷掉显示乱的屏幕，如下所示：

此问题困扰我很长时间了，一直没仔细研究过，这次趁着有些时间想彻底把这个问题解决下。下面是整个ssh的过程：

SCRT ----- 1st 跳板机 ----- 2nd 跳板机 ----- NE40E

解决

通过对比发现只有当通过脚本登录NE40E时才会有此问题，如果直接SSH登录NE40E就不会有问题，那么问题跟脚本相关么？

在此篇文章里，简单总结下通过SRTE调度EVPN ELAN的流量，然后通过show信息，来查看引流及相关内容，并熟悉EVPN，EVPN基础部分，可以参考之前的文章，里面包含Route Type的信息：EVPN Summary

另外对于ELAN的引流，有很多种选择，常见的是通过对RT1打Color，调用单播流量；对RT3打Color，调用多播流量；对于RT1我们可以看成L3VPN中的“VRF”，也就是基于“VRF”颗粒度进行引流，这么理解可能更好理解

物理拓扑

In the article, only show as follow (because easy to show how to work):

Protocol: UDP; Port: 5234

Encoding: KV-GPB

For more detailed information, you can reference my colleague’s GitHub, which includes more examples, e.g GRPC.

AlexFengCisco / Telemetry_Receiver

GRPC Update Info:

If use GRPC not TCP/UDP, that will have standard function, you will not need to write “DECODE_FN_MAP…”, function will auto generate, direct to use. Simple list steps:

1. Get GRPC protobuf (e.g “mdt_grpc_dialout”) from cisco / bigmuddy-network-telemetry-proto
2. Install/use compile tools, suggest install python virtual env, you can reference 在MacOS中部署Python虚拟开发环境

(telemetry-protocol) [[email protected] telemetry-protocol]# python -V
Python 3.6.8
(telemetry-protocol) [[email protected] telemetry-protocol]# easy_install pip
(telemetry-protocol) [[email protected] telemetry-protocol]# pip install grpcio
(telemetry-protocol) [[email protected] telemetry-protocol]# pip install protobuf
(telemetry-protocol) [[email protected] telemetry-protocol]# pip install grpcio_tools
(telemetry-protocol) [[email protected] telemetry-protocol]# python -m grpc_tools.protoc -I. --python_out=. --grpc_python_out=. cisco_grpc_dialout.proto
(telemetry-protocol) [[email protected] telemetry-protocol]# ls -l|grep cisco
-rw-r--r--.  1 root    root       2695 Aug 10 16:16 cisco_grpc_dialout_pb2_grpc.py   #generated
-rw-r--r--.  1 root    root       3805 Aug 10 16:16 cisco_grpc_dialout_pb2.py   #generated
-rw-r--r--.  1 root    root        485 Aug 10 16:15 cisco_grpc_dialout.proto   #proto file  

Follow all file if you need grpc protocol:

[[email protected] grpc-dailout]# ls -l
total 36
-rw-r--r--. 1 root root  2695 Aug 10 16:16 cisco_grpc_dialout_pb2_grpc.py #Contains the server Stub class and the client Stub class, as well as the service RPC interface to be implemented.
-rw-r--r--. 1 root root  3805 Aug 10 16:16 cisco_grpc_dialout_pb2.py #message serialization classes
-rw-r--r--. 1 root root   484 Aug 10 15:36 mdt_grpc_dialout.proto 
-rw-r--r--. 1 root root  3722 Aug 10 16:11 service_grpc_dialout_no_tls.py #service python
-rw-r--r--. 1 root root 19220 Aug 10 15:58 telemetry_pb2.py  #decode gpb-kv messages, generate as below

grpc-dailout.zip

Install Protobuf of python version

完整阅读

Thanks @JianJian‘s sharing how to import global route in IXIA. The article have two part, 1st part was done by IxNetwork original way. 2nd part will done by IXNetwork Scenario (later updste).

Before import, we must have global route table file, we can download from follow lnik:

http://bgp.potaroo.net/as2.0/bgptable.txt

http://bgp.potaroo.net/v6/as2.0/bgptable.txt

完整阅读

• Choose 2-3 router for FAD, but not all router
• Config follows configuration at FAD router:

router isis srte
affinity-map red bit-position 23
flex-algo 128
 priority 200
 metric-type delay
 advertise-definition
 affinity exclude-any red

• Config follows configuration at exclude/include function router:

router isis srte
affinity-map red bit-position 23
flex-algo 128
 metric-type delay <-- define in FAD
 affinity exclude-any red
!
inter gix/x/x/x
 affinity flex-algo red

• Config follows configuration at normal router:

router isis srte
flex-algo 128
  metric-type delay <-- define in FAD