15 7 月, 2019
TRex based on DPDK, have high performance for traffics generator scenario. TRex has two deployment scenarios, one is Stateless mode, another is Server/client mode. How different for them? As follow pic. Btw, TRex has a GUI tool that can easy config traffic pattern, but that only support in Stateless mode. For Server/Client mode, only CLI (you can reference “Linux SRv6实战 （第三篇） 多云环境下Overlay(VPP) 和Underlay整合测试 ” that use Server/Client mode). For the article, only focus on stateless mode and GUI tool.
完整阅读
28 6 月, 2019
My VPS(Bandwagon) include OpenVPN script, but only support Centos6.x that version not good for docker (my blog deploy by docker Blog顺利完成搬家之Bandwagonhost VPS), so need to do by other scripts. OpenWRT config OpenVPN client has some different, so summary the info to the article for review.
But due to GFW, OpenVPN couldn’t establish at last, reset happened between server and client, but the setup should workable.
Deploy OpenVPN at Server
Don’t know why couldn’t find OpenVPN pacakage by yum, even if have epel source
[root@frank ~]# rpm -qa |grep epel
epel-release-7-11.noarch
[root@frank ~]# yum install openvpn
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.usc.edu
* extras: repos.lax.quadranet.com
* updates: mirror.fileplanet.com
No package openvpn available.
Error: Nothing to do
完整阅读
2 4 月, 2019
For detail info, please refer to following Akshat’s article, for my article only simply summary step to build openr on ncs5500. Thanks Akshat’s help for the openr set up 🙂
https://xrdocs.io/cisco-service-layer/blogs/2018-02-16-xr-s-journey-to-the-we-b-st-open-r-integration-with-ios-xr/
1. Set up the private insecure registry on your server
Refer as follow:
https://docs.docker.com/registry/deploying/
https://xrdocs.io/application-hosting/tutorials/2017-02-26-running-docker-containers-on-ios-xr-6-1-2/#private-insecure-registry
[root@nso ~]# nano /etc/yum.repos.d/docker.repo
[root@nso ~]# yum install docker-engine
[root@nso ~]# systemctl start docker
[root@nso ~]# docker run -d -p 5000:5000 --restart=always --name registry registry:2
[root@nso ~]# docker pull akshshar/openr-xr
[root@nso ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c4636568f48a registry:2 "/entrypoint.sh /e..." 6 minutes ago Up 6 minutes 0.0.0.0:5000->5000/tcp registry
[root@nso ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry 2 f32a97de94e1 13 days ago 25.8MB
akshshar/openr-xr latest b51c260b060e 2 months ago 1.76GB
[root@nso ~]# docker tag akshshar/openr-xr 10.75.58.72:5000/openr-xr
[root@nso ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry 2 f32a97de94e1 13 days ago 25.8MB
akshshar/openr-xr latest b51c260b060e 2 months ago 1.76GB
10.75.58.72:5000/openr-xr latest b51c260b060e 2 months ago 1.76GB
[root@nso ~]# docker push 10.75.58.72:5000/openr-xr
The push refers to a repository [10.75.58.72:5000/openr-xr]
Get https://10.75.58.72:5000/v1/_ping: http: server gave HTTP response to HTTPS client
[root@nso ~]#
2. Add follow at “/etc/sysconfig/docker”
After changing the docker opts, please wait some seconds, docker will auto restart.
DOCKER_OPTS=" --insecure-registry 10.75.58.72:5000"
完整阅读
22 2 月, 2019
When we want to collect some show information by Telemetry, we will face the 1st question that how to find the correct/resolved sensor path. The first step often traps us. Is there any good way to easily find the sensor path? The answer is “Yes”. I had summarized a way that can help you quickly find the sensor path.
Before read the article，there is a file that mapping between YANG and Sensor Path in XR, you can check by keyword(e.g fan, cpu and so on) first, if not found, then check my article.
RP/0/RP0/CPU0:XTC#run
Tue Jan 22 06:58:56.512 UTC
[xr-vm_node0_RP0_CPU0:~]$cd /pkg/telemetry/mdt/protogen
[xr-vm_node0_RP0_CPU0:/pkg/telemetry/mdt/protogen]$ls
yang_to_schema.txt
[xr-vm_node0_RP0_CPU0:/pkg/telemetry/mdt/protogen]$
yang_to_Schema.txt has all yang path to xml schema path maps. https://github.com/AlexFengCisco/Telemetry_Receiver
完整阅读
25 1 月, 2019
The article only summary config and test client just now. Will include more info later.
Version: 661
Platform: NCS-5501-SE
Client: twampy , for the new version, please check original Github: https://github.com/nokia/twampy
NCS 5501 config:
RP/0/RP0/CPU0:test#sh run ipsla
Fri Jan 25 23:33:41.467 UTC
ipsla
responder
twamp
!
twamp-light test-session 1
local-ip 6.6.6.6 local-port 862 remote-ip 100.100.200.200 remote-port 123 vrf default
!
!
server twamp
!
!
Client
[root@localhost opt]# ./twampy.py controller 6.6.6.6
===============================================================================
Direction Min Max Avg Jitter Loss
-------------------------------------------------------------------------------
Outbound: 480.0min 480.0min 480.0min 36us 0.0%
Inbound: 0us 0us 0us 0us 0.0%
Roundtrip: 159us 477us 287us 79us 0.0%
-------------------------------------------------------------------------------
Jitter Algorithm [RFC1889]
===============================================================================
[root@localhost opt]#
[root@localhost opt]#
[root@localhost opt]#
[root@localhost opt]# ./twampy.py sender 6.6.6.6:862 100.100.200.200:123
===============================================================================
Direction Min Max Avg Jitter Loss
-------------------------------------------------------------------------------
Outbound: 480.0min 480.0min 480.0min 40us 0.0%
Inbound: 0us 0us 0us 0us 0.0%
Roundtrip: 126us 456us 252us 59us 0.0%
-------------------------------------------------------------------------------
Jitter Algorithm [RFC1889]
===============================================================================
