美文网首页
ncclient通过NetConf对接Juniper虚拟交换机

ncclient通过NetConf对接Juniper虚拟交换机

作者: ljyfree | 来源:发表于2020-03-30 17:56 被阅读0次

    其实主要目的是验证Juniper的虚拟交换机netconf是否ready

    Testbed搭建

    • 基于EVE-NG平台
    • Juniper的虚拟交换机vmx使用vmx-14.1.R1来启动
    • 一台CentOS主机通过EVE上的net与vmx的em0连通

    交换机配置

    • 启动交换机后，通过点击Web图标串口登录
    • 初始密码是root/root123
    • 进入配置模式
    root@vMX-1% cli
root@vMX-1> configure 
Entering configuration mode

[edit]
root@vMX-1#
    • 下发配置
    set interfaces em0 unit 0 family inet address 192.168.122.102/24 
set system login user netops uid 203
set system login user netops class super-user
set system login user netops authentication plain-text-password
 > 要求输入密码:Test123
 > 要求再次输入同样的密码:Test123
set system services ftp
set system services ssh root-login allow
set system services ssh protocol-version v2
set system services netconf ssh port 830
    • 关于Juniper JUNOS plain-text-password vs. encrypted-password的区别，可以看这里

    CentOS主机

    • 接口IP为:192.168.122.211/24，与vmx的带外管理口在同一个网段
    • 尝试使用netops/Testing来登录
    [root@deployer juniper]# ssh netops@192.168.122.102
Password:
--- JUNOS 14.1R1.10 built 2014-06-07 09:37:07 UTC
netops@vMX-1> exit 

Connection to 192.168.122.102 closed.
[root@deployer juniper]#
    • 安装ncclient这个python包
    pip install ncclient
    • 获取GitHub上的相关代码
    [root@deployer ~]# git clone https://github.com/ncclient/ncclient
...
[root@deployer ~]# cd /root/ncclient/examples/juniper
[root@deployer juniper]#

    对接

    • 该文件夹下已经有很多适配Juniper交换机的脚本

    通过netconf获取信息

    • 选取一个获取端口状态的脚本get-interface-status.py，修改最后一行
    connect('192.168.122.102', 830, 'netops', 'Test123')
    • 运行脚本,可以获取到vmx的所有接口状态
    [root@deployer juniper]# python get-interface-status.py
2020-03-30 17:38:17,083 INFO transport.py:1819 Connected (version 2.0, client OpenSSH_6.4)
2020-03-30 17:38:17,255 INFO transport.py:1819 Authentication (publickey) failed.
2020-03-30 17:38:17,281 INFO transport.py:1819 Authentication (password) successful!
2020-03-30 17:38:17,422 INFO ssh.py:506 [host 192.168.122.102 session 0x7f0e4c5bce90] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:hello xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:capabilities><nc:capability>urn:ietf:params:netconf:capability:writable-running:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:with-defaults:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</nc:capability><nc:capability>urn:liberouter:params:netconf:capability:power-control:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:validate:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file,https,sftp</nc:capability><nc:capability>urn:ietf:params:netconf:base:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:base:1.1</nc:capability><nc:capability>urn:ietf:params:netconf:capability:candidate:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:notification:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:xpath:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:startup:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:interleave:1.0</nc:capability></nc:capabilities></nc:hello>]]>]]>
2020-03-30 17:38:18,060 INFO ssh.py:125 [host 192.168.122.102 session 0x7f0e4c5bce90] Received message from host
2020-03-30 17:38:18,094 INFO session.py:125 [host 192.168.122.102 session-id 7303] initialized: session-id=7303 | server_capabilities=<dictionary-keyiterator object at 0x7f0e4c569cb0>
2020-03-30 17:38:18,097 INFO rpc.py:325 [host 192.168.122.102 session-id 7303] Requesting 'ExecuteRpc'
2020-03-30 17:38:18,165 INFO ssh.py:506 [host 192.168.122.102 session-id 7303] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:864fe5a3-7b2b-47a7-b165-ba7ba9b49169"><get-interface-information><terse/></get-interface-information></nc:rpc>]]>]]>
2020-03-30 17:38:19,155 INFO ssh.py:125 [host 192.168.122.102 session-id 7303] Received message from host
2020-03-30 17:38:19,223 INFO get-interface-status.py:26 ge-0/0/0 - up
2020-03-30 17:38:19,224 INFO get-interface-status.py:26 lc-0/0/0 - up
2020-03-30 17:38:19,226 INFO get-interface-status.py:26 pfe-0/0/0 - up
2020-03-30 17:38:19,227 INFO get-interface-status.py:26 pfh-0/0/0 - up
2020-03-30 17:38:19,227 INFO get-interface-status.py:26 ge-0/0/1 - up
2020-03-30 17:38:19,228 INFO get-interface-status.py:26 ge-0/0/2 - up
2020-03-30 17:38:19,228 INFO get-interface-status.py:26 ge-0/0/3 - up
2020-03-30 17:38:19,229 INFO get-interface-status.py:26 ge-0/0/4 - up
2020-03-30 17:38:19,230 INFO get-interface-status.py:26 ge-0/0/5 - up
2020-03-30 17:38:19,230 INFO get-interface-status.py:26 ge-0/0/6 - up
2020-03-30 17:38:19,231 INFO get-interface-status.py:26 ge-0/0/7 - up
2020-03-30 17:38:19,231 INFO get-interface-status.py:26 ge-0/0/8 - up
2020-03-30 17:38:19,232 INFO get-interface-status.py:26 ge-0/0/9 - up
2020-03-30 17:38:19,232 INFO get-interface-status.py:26 cbp0 - up
2020-03-30 17:38:19,233 INFO get-interface-status.py:26 demux0 - up
2020-03-30 17:38:19,234 INFO get-interface-status.py:26 dsc - up
2020-03-30 17:38:19,234 INFO get-interface-status.py:26 em0 - up
2020-03-30 17:38:19,234 INFO get-interface-status.py:26 em1 - up
2020-03-30 17:38:19,235 INFO get-interface-status.py:26 em2 - up
2020-03-30 17:38:19,235 INFO get-interface-status.py:26 em3 - up
2020-03-30 17:38:19,235 INFO get-interface-status.py:26 em4 - up
2020-03-30 17:38:19,236 INFO get-interface-status.py:26 em5 - up
2020-03-30 17:38:19,236 INFO get-interface-status.py:26 gre - up
2020-03-30 17:38:19,236 INFO get-interface-status.py:26 ipip - up
2020-03-30 17:38:19,236 INFO get-interface-status.py:26 irb - up
2020-03-30 17:38:19,237 INFO get-interface-status.py:26 lo0 - up
2020-03-30 17:38:19,237 INFO get-interface-status.py:26 lsi - up
2020-03-30 17:38:19,237 INFO get-interface-status.py:26 mtun - up
2020-03-30 17:38:19,237 INFO get-interface-status.py:26 pimd - up
2020-03-30 17:38:19,238 INFO get-interface-status.py:26 pime - up
2020-03-30 17:38:19,238 INFO get-interface-status.py:26 pip0 - up
2020-03-30 17:38:19,238 INFO get-interface-status.py:26 pp0 - up
2020-03-30 17:38:19,238 INFO get-interface-status.py:26 tap - up
2020-03-30 17:38:19,239 INFO get-interface-status.py:26 vtep - up
[root@deployer juniper]#

    通过netconf设置

    • 选取一个获取端口状态的脚本set-description.py，修改最后一行
    connect('192.168.122.102', 830, 'netops', 'Test123', 'set interfaces %s description example' % interface)
    • 运行
    [root@deployer juniper]# python set-description.py
2020-03-30 17:52:34,827 INFO transport.py:1819 Connected (version 2.0, client OpenSSH_6.4)
2020-03-30 17:52:35,054 INFO transport.py:1819 Authentication (publickey) failed.
2020-03-30 17:52:35,095 INFO transport.py:1819 Authentication (password) successful!
2020-03-30 17:52:35,276 INFO ssh.py:506 [host 192.168.122.102 session 0x7f6b8e54cd10] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:hello xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:capabilities><nc:capability>urn:ietf:params:netconf:capability:writable-running:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:with-defaults:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</nc:capability><nc:capability>urn:liberouter:params:netconf:capability:power-control:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:validate:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file,https,sftp</nc:capability><nc:capability>urn:ietf:params:netconf:base:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:base:1.1</nc:capability><nc:capability>urn:ietf:params:netconf:capability:candidate:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:notification:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:xpath:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:startup:1.0</nc:capability><nc:capability>urn:ietf:params:netconf:capability:interleave:1.0</nc:capability></nc:capabilities></nc:hello>]]>]]>
2020-03-30 17:52:36,323 INFO ssh.py:125 [host 192.168.122.102 session 0x7f6b8e54cd10] Received message from host
2020-03-30 17:52:36,349 INFO session.py:125 [host 192.168.122.102 session-id 7522] initialized: session-id=7522 | server_capabilities=<dictionary-keyiterator object at 0x7f6b8e4f9cb0>
2020-03-30 17:52:36,350 INFO rpc.py:325 [host 192.168.122.102 session-id 7522] Requesting 'Lock'
2020-03-30 17:52:36,426 INFO ssh.py:506 [host 192.168.122.102 session-id 7522] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:65594085-b60e-4acb-b4fd-2f00c46cf530"><nc:lock><nc:target><nc:candidate/></nc:target></nc:lock></nc:rpc>]]>]]>
2020-03-30 17:52:36,434 INFO ssh.py:125 [host 192.168.122.102 session-id 7522] Received message from host
2020-03-30 17:52:36,469 INFO rpc.py:325 [host 192.168.122.102 session-id 7522] Requesting 'LoadConfiguration'
2020-03-30 17:52:36,536 INFO ssh.py:506 [host 192.168.122.102 session-id 7522] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:c4e117ec-466c-406a-8a6a-97b4b5627734"><nc:load-configuration action="set" format="text"><nc:configuration-set>set interfaces em0 description example</nc:configuration-set></nc:load-configuration></nc:rpc>]]>]]>
2020-03-30 17:52:36,550 INFO ssh.py:125 [host 192.168.122.102 session-id 7522] Received message from host
2020-03-30 17:52:36,585 INFO set-description.py:20 <rpc-reply message-id="urn:uuid:c4e117ec-466c-406a-8a6a-97b4b5627734">
  <load-configuration-results>
    <ok/>
  </load-configuration-results>
</rpc-reply>

2020-03-30 17:52:36,586 INFO rpc.py:325 [host 192.168.122.102 session-id 7522] Requesting 'Commit'
2020-03-30 17:52:36,652 INFO ssh.py:506 [host 192.168.122.102 session-id 7522] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7d525141-affc-4b11-b0d0-320c20eb9c88"><commit-configuration/></nc:rpc>]]>]]>
2020-03-30 17:52:37,873 INFO ssh.py:125 [host 192.168.122.102 session-id 7522] Received message from host
2020-03-30 17:52:37,911 INFO set-description.py:22 <rpc-reply message-id="urn:uuid:7d525141-affc-4b11-b0d0-320c20eb9c88">
  <ok/>
</rpc-reply>

2020-03-30 17:52:37,912 INFO rpc.py:325 [host 192.168.122.102 session-id 7522] Requesting 'Unlock'
2020-03-30 17:52:37,975 INFO ssh.py:506 [host 192.168.122.102 session-id 7522] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:04a87be2-50bd-4a0a-a864-3401514305f6"><nc:unlock><nc:target><nc:candidate/></nc:target></nc:unlock></nc:rpc>]]>]]>
2020-03-30 17:52:38,009 INFO ssh.py:125 [host 192.168.122.102 session-id 7522] Received message from host
2020-03-30 17:52:38,029 INFO rpc.py:325 [host 192.168.122.102 session-id 7522] Requesting 'CloseSession'
2020-03-30 17:52:38,110 INFO ssh.py:506 [host 192.168.122.102 session-id 7522] Sending:
<?xml version="1.0" encoding="UTF-8"?><nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:ffdeecf8-29d9-4a7b-a518-40e41b648d27"><nc:close-session/></nc:rpc>]]>]]>
2020-03-30 17:52:38,118 INFO ssh.py:125 [host 192.168.122.102 session-id 7522] Received message from host
[root@deployer juniper]#

    • 对比前后em0接口的配置，发现多了接口描述，和预期相同


      set_port_desc.png

    相关文章

      网友评论

          本文标题：ncclient通过NetConf对接Juniper虚拟交换机

          本文链接：https://www.haomeiwen.com/subject/yknvuhtx.html

          延伸阅读

          深度阅读

          • 您也可以注册成为美文阅读网的作者，发表您的原创作品、分享您的心情！

          栏目导航

          热点阅读

          关于我们|服务条款|联系我们|ncclient通过NetConf对接Juniper虚拟交换机|投稿指南|网站地图|RSS订阅|排版工具|手机版

          提供经典美文摘抄,优美散文欣赏,现代诗歌精选,短篇小说,心情随笔,表白情书范文,故事会在线阅读欣赏

          Copyright © 2014-2023 Haomeiwen.com All Rights Reserved. 好美文阅读网 版权所有

          备案信息：桂公网安备 45052102000051号 · 桂ICP备13007215号-3

          本站所收录作品、热点评论等信息部分来源互联网，目的只是为了系统归纳学习和传递资讯

          所有作品版权归原创作者所有，与本站立场无关，如不慎侵犯了你的权益，请联系我们告知，我们将做删除处理！