四月 2nd, 2019,由 frank撰写
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"
完整阅读
二月 22nd, 2019,由 frank撰写
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
完整阅读
一月 25th, 2019,由 frank撰写
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]
===============================================================================
一月 13th, 2019,由 frank撰写
去年年初，为了体验4k的“塞尔达传说-旷野之息”，我升级了我的电脑，并在18年不断完善，目前经过optane加速的4T硬盘，速度提升非常显著，很是喜欢。但电脑里有些录音，以及家庭照片，想随时观看，而不想开电脑，另外也起到备份的作用（数据无价），所以一直在考虑采购一台NAS，但感觉现在的NAS及配件（硬盘）功能比较弱（其实就是没米。。。），所以就考虑利用现有资源，把1T的闲置移动硬盘挂载到 WRT1200路由器下，这样 Win/Mac/手机 通过sshfs/samba远程挂载目录，这样可以体验简易NAS，等时机成熟了再考虑NAS，此篇主要总结如何挂载移动硬盘，由于环境版本的不同，总结中的内容可能跟读者遇到的会有少许差异，如遇到问题，可自行google或baidu
有时候通过LEDE的luci直接挂载不起作用，也弄不明白为啥，所以还是CLI最靠谱。另外在openwrt里，移动硬盘的格式最好是ext3或ext4，这样效果高，问题少。另外就是最开始我想用sshfs，但后来发现windows访问sshfs效果非常不好，所以对于windows，就换回了samba服务器，速度不错，可以达到平均60MB/s 上下
另外Samba配置，可以参考我之前的文章 Deploy Samba on OpenWRT
1. 国内更新源，这样就可以随便更新软件了
src/gz arm_core https://mirrors.ustc.edu.cn/lede/releases/17.01.6/targets/mvebu/generic/packages
src/gz arm_base https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/base
src/gz arm_luci https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/luci
src/gz arm_packages https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/packages
src/gz arm_routing https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/routing
src/gz arm_telephony https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/telephony
完整阅读
十二月 17th, 2018,由 frank撰写
Install
docker pull dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest
docker run -it -p 8480:8480 \
--mount type=bind,source=/xxx/Documents/Yangsuite_data,target=/home/docker/data \
dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest
Detail info:
完整阅读