API tools faq
paste
Advertisement
mbuil

sfc104 vpp logs

mbuil
Nov 16th, 2016
224
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 26.97 KB | None | 0 0
raw download clone embed print report
  1. root@v-env-ebs57:~/sfc/sfc-demo/sfc104# ./run_demo.sh vpp
  2. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  3. Password authentication
  4. Install and wait for sfc features: odl-sfc-ui odl-sfc-vpp-renderer
  5. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  6. Password authentication
  7. Error executing command: No installed feature matching odl-sfc-openflow-renderer
  8. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  9. Password authentication
  10. Connection to 127.0.0.1 closed by remote host.
  11. ssh: connect to host 127.0.0.1 port 8101: Connection refused
  12. Installed features:
  13. Expected features: odl-sfc-ui odl-sfc-vpp-renderer
  14. Waiting for odl-sfc-ui odl-sfc-vpp-renderer installed...
  15. ssh: connect to host 127.0.0.1 port 8101: Connection refused
  16. Installed features:
  17. Expected features: odl-sfc-ui odl-sfc-vpp-renderer
  18. Waiting for odl-sfc-ui odl-sfc-vpp-renderer installed...
  19. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  20. Password authentication
  21. Installed features: odl-sfc-model
  22. odl-sfc-provider
  23. odl-sfc-provider-rest
  24. odl-sfc-vpp-renderer
  25. odl-sfc-ui
  26. Expected features: odl-sfc-ui odl-sfc-vpp-renderer
  27. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  28. Password authentication
  29. 127.0.0.1
  30. Warning: Permanently added '[127.0.0.1]:8101' (RSA) to the list of known hosts.
  31. Password authentication
  32. About to enter ./common/cleanup_sfc.py
  33. About to execute sudo /vagrant/common/cleanup_classifier.sh
  34. VM must be running to open SSH connection. Run `vagrant up`
  35. to start the virtual machine.
  36. About to execute sudo /vagrant/common/cleanup_sff.sh
  37. VM must be running to open SSH connection. Run `vagrant up`
  38. to start the virtual machine.
  39. About to execute sudo /vagrant/common/cleanup_sf.sh
  40. VM must be running to open SSH connection. Run `vagrant up`
  41. to start the virtual machine.
  42. About to execute sudo /vagrant/common/cleanup_sf.sh
  43. VM must be running to open SSH connection. Run `vagrant up`
  44. to start the virtual machine.
  45. About to execute sudo /vagrant/common/cleanup_sff.sh
  46. VM must be running to open SSH connection. Run `vagrant up`
  47. to start the virtual machine.
  48. About to execute sudo /vagrant/common/cleanup_classifier.sh
  49. VM must be running to open SSH connection. Run `vagrant up`
  50. to start the virtual machine.
  51. Bringing machine 'classifier1' up with 'virtualbox' provider...
  52. ==> classifier1: Clearing any previously set forwarded ports...
  53. ==> classifier1: Clearing any previously set network interfaces...
  54. ==> classifier1: Preparing network interfaces based on configuration...
  55. classifier1: Adapter 1: nat
  56. classifier1: Adapter 2: hostonly
  57. ==> classifier1: Forwarding ports...
  58. classifier1: 22 (guest) => 2222 (host) (adapter 1)
  59. ==> classifier1: Running 'pre-boot' VM customizations...
  60. ==> classifier1: Booting VM...
  61. ==> classifier1: Waiting for machine to boot. This may take a few minutes...
  62. classifier1: SSH address: 127.0.0.1:2222
  63. classifier1: SSH username: vagrant
  64. classifier1: SSH auth method: private key
  65. ==> classifier1: Machine booted and ready!
  66. ==> classifier1: Checking for guest additions in VM...
  67. classifier1: The guest additions on this VM do not match the installed version of
  68. classifier1: VirtualBox! In most cases this is fine, but in rare cases it can
  69. classifier1: prevent things such as shared folders from working properly. If you see
  70. classifier1: shared folder errors, please make sure the guest additions within the
  71. classifier1: virtual machine match the version of VirtualBox you have installed on
  72. classifier1: your host and reload your VM.
  73. classifier1:
  74. classifier1: Guest Additions Version: 4.3.36
  75. classifier1: VirtualBox Version: 5.0
  76. ==> classifier1: Setting hostname...
  77. ==> classifier1: Configuring and enabling network interfaces...
  78. ==> classifier1: Mounting shared folders...
  79. classifier1: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  80. ==> classifier1: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  81. ==> classifier1: flag to force provisioning. Provisioners marked to run always will still run.
  82. Connection to 127.0.0.1 closed.
  83. Bringing machine 'classifier1' up with 'virtualbox' provider...
  84. Bringing machine 'sff1' up with 'virtualbox' provider...
  85. Bringing machine 'sf1' up with 'virtualbox' provider...
  86. Bringing machine 'sf2' up with 'virtualbox' provider...
  87. Bringing machine 'sff2' up with 'virtualbox' provider...
  88. Bringing machine 'classifier2' up with 'virtualbox' provider...
  89. ==> classifier1: VirtualBox VM is already running.
  90. ==> sff1: Clearing any previously set forwarded ports...
  91. ==> sff1: Fixed port collision for 22 => 2222. Now on port 2200.
  92. ==> sff1: Clearing any previously set network interfaces...
  93. ==> sff1: Preparing network interfaces based on configuration...
  94. sff1: Adapter 1: nat
  95. sff1: Adapter 2: hostonly
  96. ==> sff1: Forwarding ports...
  97. sff1: 22 (guest) => 2200 (host) (adapter 1)
  98. ==> sff1: Running 'pre-boot' VM customizations...
  99. ==> sff1: Booting VM...
  100. ==> sff1: Waiting for machine to boot. This may take a few minutes...
  101. sff1: SSH address: 127.0.0.1:2200
  102. sff1: SSH username: vagrant
  103. sff1: SSH auth method: private key
  104. ==> sff1: Machine booted and ready!
  105. ==> sff1: Checking for guest additions in VM...
  106. sff1: The guest additions on this VM do not match the installed version of
  107. sff1: VirtualBox! In most cases this is fine, but in rare cases it can
  108. sff1: prevent things such as shared folders from working properly. If you see
  109. sff1: shared folder errors, please make sure the guest additions within the
  110. sff1: virtual machine match the version of VirtualBox you have installed on
  111. sff1: your host and reload your VM.
  112. sff1:
  113. sff1: Guest Additions Version: 4.3.36
  114. sff1: VirtualBox Version: 5.0
  115. ==> sff1: Setting hostname...
  116. ==> sff1: Configuring and enabling network interfaces...
  117. ==> sff1: Mounting shared folders...
  118. sff1: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  119. ==> sff1: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  120. ==> sff1: flag to force provisioning. Provisioners marked to run always will still run.
  121. ==> sf1: Clearing any previously set forwarded ports...
  122. ==> sf1: Fixed port collision for 22 => 2222. Now on port 2201.
  123. ==> sf1: Clearing any previously set network interfaces...
  124. ==> sf1: Preparing network interfaces based on configuration...
  125. sf1: Adapter 1: nat
  126. sf1: Adapter 2: hostonly
  127. ==> sf1: Forwarding ports...
  128. sf1: 22 (guest) => 2201 (host) (adapter 1)
  129. ==> sf1: Running 'pre-boot' VM customizations...
  130. ==> sf1: Booting VM...
  131. ==> sf1: Waiting for machine to boot. This may take a few minutes...
  132. sf1: SSH address: 127.0.0.1:2201
  133. sf1: SSH username: vagrant
  134. sf1: SSH auth method: private key
  135. ==> sf1: Machine booted and ready!
  136. ==> sf1: Checking for guest additions in VM...
  137. sf1: The guest additions on this VM do not match the installed version of
  138. sf1: VirtualBox! In most cases this is fine, but in rare cases it can
  139. sf1: prevent things such as shared folders from working properly. If you see
  140. sf1: shared folder errors, please make sure the guest additions within the
  141. sf1: virtual machine match the version of VirtualBox you have installed on
  142. sf1: your host and reload your VM.
  143. sf1:
  144. sf1: Guest Additions Version: 4.3.36
  145. sf1: VirtualBox Version: 5.0
  146. ==> sf1: Setting hostname...
  147. ==> sf1: Configuring and enabling network interfaces...
  148. ==> sf1: Mounting shared folders...
  149. sf1: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  150. ==> sf1: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  151. ==> sf1: flag to force provisioning. Provisioners marked to run always will still run.
  152. ==> sf2: Clearing any previously set forwarded ports...
  153. ==> sf2: Fixed port collision for 22 => 2222. Now on port 2202.
  154. ==> sf2: Clearing any previously set network interfaces...
  155. ==> sf2: Preparing network interfaces based on configuration...
  156. sf2: Adapter 1: nat
  157. sf2: Adapter 2: hostonly
  158. ==> sf2: Forwarding ports...
  159. sf2: 22 (guest) => 2202 (host) (adapter 1)
  160. ==> sf2: Running 'pre-boot' VM customizations...
  161. ==> sf2: Booting VM...
  162. ==> sf2: Waiting for machine to boot. This may take a few minutes...
  163. sf2: SSH address: 127.0.0.1:2202
  164. sf2: SSH username: vagrant
  165. sf2: SSH auth method: private key
  166. ==> sf2: Machine booted and ready!
  167. ==> sf2: Checking for guest additions in VM...
  168. sf2: The guest additions on this VM do not match the installed version of
  169. sf2: VirtualBox! In most cases this is fine, but in rare cases it can
  170. sf2: prevent things such as shared folders from working properly. If you see
  171. sf2: shared folder errors, please make sure the guest additions within the
  172. sf2: virtual machine match the version of VirtualBox you have installed on
  173. sf2: your host and reload your VM.
  174. sf2:
  175. sf2: Guest Additions Version: 4.3.36
  176. sf2: VirtualBox Version: 5.0
  177. ==> sf2: Setting hostname...
  178. ==> sf2: Configuring and enabling network interfaces...
  179. ==> sf2: Mounting shared folders...
  180. sf2: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  181. ==> sf2: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  182. ==> sf2: flag to force provisioning. Provisioners marked to run always will still run.
  183. ==> sff2: Clearing any previously set forwarded ports...
  184. ==> sff2: Fixed port collision for 22 => 2222. Now on port 2203.
  185. ==> sff2: Clearing any previously set network interfaces...
  186. ==> sff2: Preparing network interfaces based on configuration...
  187. sff2: Adapter 1: nat
  188. sff2: Adapter 2: hostonly
  189. ==> sff2: Forwarding ports...
  190. sff2: 22 (guest) => 2203 (host) (adapter 1)
  191. ==> sff2: Running 'pre-boot' VM customizations...
  192. ==> sff2: Booting VM...
  193. ==> sff2: Waiting for machine to boot. This may take a few minutes...
  194. sff2: SSH address: 127.0.0.1:2203
  195. sff2: SSH username: vagrant
  196. sff2: SSH auth method: private key
  197. ==> sff2: Machine booted and ready!
  198. ==> sff2: Checking for guest additions in VM...
  199. sff2: The guest additions on this VM do not match the installed version of
  200. sff2: VirtualBox! In most cases this is fine, but in rare cases it can
  201. sff2: prevent things such as shared folders from working properly. If you see
  202. sff2: shared folder errors, please make sure the guest additions within the
  203. sff2: virtual machine match the version of VirtualBox you have installed on
  204. sff2: your host and reload your VM.
  205. sff2:
  206. sff2: Guest Additions Version: 4.3.36
  207. sff2: VirtualBox Version: 5.0
  208. ==> sff2: Setting hostname...
  209. ==> sff2: Configuring and enabling network interfaces...
  210. ==> sff2: Mounting shared folders...
  211. sff2: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  212. ==> sff2: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  213. ==> sff2: flag to force provisioning. Provisioners marked to run always will still run.
  214. ==> classifier2: Clearing any previously set forwarded ports...
  215. ==> classifier2: Fixed port collision for 22 => 2222. Now on port 2204.
  216. ==> classifier2: Clearing any previously set network interfaces...
  217. ==> classifier2: Preparing network interfaces based on configuration...
  218. classifier2: Adapter 1: nat
  219. classifier2: Adapter 2: hostonly
  220. ==> classifier2: Forwarding ports...
  221. classifier2: 22 (guest) => 2204 (host) (adapter 1)
  222. ==> classifier2: Running 'pre-boot' VM customizations...
  223. ==> classifier2: Booting VM...
  224. ==> classifier2: Waiting for machine to boot. This may take a few minutes...
  225. classifier2: SSH address: 127.0.0.1:2204
  226. classifier2: SSH username: vagrant
  227. classifier2: SSH auth method: private key
  228. ==> classifier2: Machine booted and ready!
  229. ==> classifier2: Checking for guest additions in VM...
  230. classifier2: The guest additions on this VM do not match the installed version of
  231. classifier2: VirtualBox! In most cases this is fine, but in rare cases it can
  232. classifier2: prevent things such as shared folders from working properly. If you see
  233. classifier2: shared folder errors, please make sure the guest additions within the
  234. classifier2: virtual machine match the version of VirtualBox you have installed on
  235. classifier2: your host and reload your VM.
  236. classifier2:
  237. classifier2: Guest Additions Version: 4.3.36
  238. classifier2: VirtualBox Version: 5.0
  239. ==> classifier2: Setting hostname...
  240. ==> classifier2: Configuring and enabling network interfaces...
  241. ==> classifier2: Mounting shared folders...
  242. classifier2: /vagrant => /home/cloudci/sfc/sfc-demo/sfc104
  243. ==> classifier2: Machine already provisioned. Run `vagrant provision` or use the `--provision`
  244. ==> classifier2: flag to force provisioning. Provisioners marked to run always will still run.
  245. Connection to 127.0.0.1 closed.
  246. Connection to 127.0.0.1 closed.
  247. Connection to 127.0.0.1 closed.
  248. Connection to 127.0.0.1 closed.
  249. Cannot open network namespace "app": No such file or directory
  250. Cannot open network namespace "app": No such file or directory
  251. Cannot open network namespace "app": No such file or directory
  252. Cannot find device "veth-br"
  253. Cannot find device "veth-app"
  254. Cannot remove namespace file "/var/run/netns/app": No such file or directory
  255. OK
  256. Warning - no supported modules(DPDK driver) are loaded
  257. Routing table indicates that interface 0000:00:08.0 is active. Not modifying
  258. Warning - no supported modules(DPDK driver) are loaded
  259. 0000:00:09.0 already bound to driver e1000, skipping
  260.  
  261. start ovs
  262. * Inserting openvswitch module
  263. * Starting ovsdb-server
  264. * Configuring Open vSwitch system IDs
  265. * Starting ovs-vswitchd
  266. * Enabling remote OVSDB managers
  267. 2016-11-16T08:12:38Z|00001|dpdk|INFO|No -vhost_sock_dir provided - defaulting to //var/run/openvswitch
  268. EAL: Detected lcore 0 as core 0 on socket 0
  269. EAL: Detected lcore 1 as core 1 on socket 0
  270. EAL: Detected lcore 2 as core 2 on socket 0
  271. EAL: Detected lcore 3 as core 3 on socket 0
  272. EAL: Support maximum 128 logical core(s) by configuration.
  273. EAL: Detected 4 lcore(s)
  274. EAL: VFIO modules not all loaded, skip VFIO support...
  275. EAL: Setting up physically contiguous memory...
  276. EAL: Ask a virtual area of 0x71c00000 bytes
  277. EAL: Virtual area found at 0x7f43e0200000 (size = 0x71c00000)
  278. EAL: Ask a virtual area of 0x200000 bytes
  279. EAL: Virtual area found at 0x7f43dfe00000 (size = 0x200000)
  280. EAL: Ask a virtual area of 0xe000000 bytes
  281. EAL: Virtual area found at 0x7f43d1c00000 (size = 0xe000000)
  282. EAL: Ask a virtual area of 0x200000 bytes
  283. EAL: Virtual area found at 0x7f43d1800000 (size = 0x200000)
  284. EAL: Requesting 512 pages of size 2MB from socket 0
  285. EAL: TSC frequency is ~2400008 KHz
  286. EAL: Master lcore 0 is ready (tid=53752b80;cpuset=[0])
  287. EAL: PCI device 0000:00:03.0 on NUMA socket -1
  288. EAL: probe driver: 8086:100e rte_em_pmd
  289. EAL: Not managed by a supported kernel driver, skipped
  290. EAL: PCI device 0000:00:08.0 on NUMA socket -1
  291. EAL: probe driver: 8086:100e rte_em_pmd
  292. EAL: Not managed by a supported kernel driver, skipped
  293. EAL: PCI device 0000:00:09.0 on NUMA socket -1
  294. EAL: probe driver: 8086:100e rte_em_pmd
  295. EAL: PCI memory mapped at 0x7f4420200000
  296. PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x100e
  297. Zone 0: name:<RG_MP_log_history>, phys:0xa77fdec0, len:0x2080, virt:0x7f44201fdec0, socket_id:0, flags:0
  298. Zone 1: name:<MP_log_history>, phys:0xa7573d40, len:0x28a0c0, virt:0x7f441ff73d40, socket_id:0, flags:0
  299. Zone 2: name:<rte_eth_dev_data>, phys:0xa7543400, len:0x2f700, virt:0x7f441ff43400, socket_id:0, flags:0
  300. 2016-11-16T08:12:39Z|00002|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log
  301. 2016-11-16T08:12:39Z|00003|ovs_numa|INFO|Discovered 4 CPU cores on NUMA node 0
  302. 2016-11-16T08:12:39Z|00004|ovs_numa|INFO|Discovered 1 NUMA nodes and 4 CPU cores
  303. 2016-11-16T08:12:39Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
  304. 2016-11-16T08:12:39Z|00006|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
  305. OK
  306. OK
  307. nohup: appending output to ‘nohup.out’
  308. Connection to 127.0.0.1 closed.
  309. stop: Unknown instance:
  310. stop: Unknown instance:
  311. Warning - no supported modules(DPDK driver) are loaded
  312. 0000:00:09.0 already bound to driver e1000, skipping
  313.  
  314. OK
  315. Warning - no supported modules(DPDK driver) are loaded
  316. Routing table indicates that interface 0000:00:08.0 is active. Not modifying
  317. Warning - no supported modules(DPDK driver) are loaded
  318. 0000:00:09.0 already bound to driver e1000, skipping
  319.  
  320. umount: /run/hugepages/kvm: not mounted
  321. vpp start/running, process 2103
  322. honeycomb start/running, process 2106
  323. Connection to 127.0.0.1 closed.
  324. nohup: appending output to ‘nohup.out’
  325. Connection to 127.0.0.1 closed.
  326. nohup: appending output to ‘nohup.out’
  327. Connection to 127.0.0.1 closed.
  328. stop: Unknown instance:
  329. stop: Unknown instance:
  330. Warning - no supported modules(DPDK driver) are loaded
  331. 0000:00:09.0 already bound to driver e1000, skipping
  332.  
  333. OK
  334. Warning - no supported modules(DPDK driver) are loaded
  335. Routing table indicates that interface 0000:00:08.0 is active. Not modifying
  336. Warning - no supported modules(DPDK driver) are loaded
  337. 0000:00:09.0 already bound to driver e1000, skipping
  338.  
  339. umount: /run/hugepages/kvm: not mounted
  340. vpp start/running, process 2100
  341. honeycomb start/running, process 2103
  342. Connection to 127.0.0.1 closed.
  343. Cannot open network namespace "app": No such file or directory
  344. Cannot open network namespace "app": No such file or directory
  345. Cannot open network namespace "app": No such file or directory
  346. Cannot find device "veth-br"
  347. Cannot find device "veth-app"
  348. Cannot remove namespace file "/var/run/netns/app": No such file or directory
  349. OK
  350. Warning - no supported modules(DPDK driver) are loaded
  351. Routing table indicates that interface 0000:00:08.0 is active. Not modifying
  352. Warning - no supported modules(DPDK driver) are loaded
  353. 0000:00:09.0 already bound to driver e1000, skipping
  354.  
  355. start ovs
  356. * Inserting openvswitch module
  357. * Starting ovsdb-server
  358. * Configuring Open vSwitch system IDs
  359. * Starting ovs-vswitchd
  360. * Enabling remote OVSDB managers
  361. 2016-11-16T08:13:06Z|00001|dpdk|INFO|No -vhost_sock_dir provided - defaulting to //var/run/openvswitch
  362. EAL: Detected lcore 0 as core 0 on socket 0
  363. EAL: Detected lcore 1 as core 1 on socket 0
  364. EAL: Detected lcore 2 as core 2 on socket 0
  365. EAL: Detected lcore 3 as core 3 on socket 0
  366. EAL: Support maximum 128 logical core(s) by configuration.
  367. EAL: Detected 4 lcore(s)
  368. EAL: VFIO modules not all loaded, skip VFIO support...
  369. EAL: Setting up physically contiguous memory...
  370. EAL: Ask a virtual area of 0x71800000 bytes
  371. EAL: Virtual area found at 0x7fcc3fc00000 (size = 0x71800000)
  372. EAL: Ask a virtual area of 0x200000 bytes
  373. EAL: Virtual area found at 0x7fcc3f800000 (size = 0x200000)
  374. EAL: Ask a virtual area of 0x200000 bytes
  375. EAL: Virtual area found at 0x7fcc3f400000 (size = 0x200000)
  376. EAL: Ask a virtual area of 0xe000000 bytes
  377. EAL: Virtual area found at 0x7fcc31200000 (size = 0xe000000)
  378. EAL: Ask a virtual area of 0x200000 bytes
  379. EAL: Virtual area found at 0x7fcc30e00000 (size = 0x200000)
  380. EAL: Ask a virtual area of 0x200000 bytes
  381. EAL: Virtual area found at 0x7fcc30a00000 (size = 0x200000)
  382. EAL: Requesting 512 pages of size 2MB from socket 0
  383. EAL: TSC frequency is ~2400004 KHz
  384. EAL: Master lcore 0 is ready (tid=b2dc4b80;cpuset=[0])
  385. EAL: PCI device 0000:00:03.0 on NUMA socket -1
  386. EAL: probe driver: 8086:100e rte_em_pmd
  387. EAL: Not managed by a supported kernel driver, skipped
  388. EAL: PCI device 0000:00:08.0 on NUMA socket -1
  389. EAL: probe driver: 8086:100e rte_em_pmd
  390. EAL: Not managed by a supported kernel driver, skipped
  391. EAL: PCI device 0000:00:09.0 on NUMA socket -1
  392. EAL: probe driver: 8086:100e rte_em_pmd
  393. EAL: PCI memory mapped at 0x7fcc7fc00000
  394. PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x100e
  395. Zone 0: name:<RG_MP_log_history>, phys:0xa7bfdec0, len:0x2080, virt:0x7fcc7fbfdec0, socket_id:0, flags:0
  396. Zone 1: name:<MP_log_history>, phys:0xa7973d40, len:0x28a0c0, virt:0x7fcc7f973d40, socket_id:0, flags:0
  397. Zone 2: name:<rte_eth_dev_data>, phys:0xa7943400, len:0x2f700, virt:0x7fcc7f943400, socket_id:0, flags:0
  398. 2016-11-16T08:13:08Z|00002|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log
  399. 2016-11-16T08:13:08Z|00003|ovs_numa|INFO|Discovered 4 CPU cores on NUMA node 0
  400. 2016-11-16T08:13:08Z|00004|ovs_numa|INFO|Discovered 1 NUMA nodes and 4 CPU cores
  401. 2016-11-16T08:13:08Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
  402. 2016-11-16T08:13:08Z|00006|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
  403. OK
  404. OK
  405. nohup: appending output to ‘nohup.out’
  406. Connection to 127.0.0.1 closed.
  407. sending service nodes
  408. PUT http://192.168.60.1:8181/restconf/config/service-node:service-nodes
  409. {
  410. "service-nodes": {
  411. "service-node": [
  412. {
  413. "ip-mgmt-address": "192.168.60.20",
  414. "name": "sff1",
  415. "service-function": []
  416. },
  417. {
  418. "ip-mgmt-address": "192.168.60.30",
  419. "name": "sf1",
  420. "service-function": [
  421. "dpi-1"
  422. ]
  423. },
  424. {
  425. "ip-mgmt-address": "192.168.60.40",
  426. "name": "sf2",
  427. "service-function": [
  428. "firewall-1"
  429. ]
  430. },
  431. {
  432. "ip-mgmt-address": "192.168.60.50",
  433. "name": "sff2",
  434. "service-function": []
  435. }
  436. ]
  437. }
  438. }
  439.  
  440. sending service functions
  441. PUT http://192.168.60.1:8181/restconf/config/service-function:service-functions
  442. {
  443. "service-functions": {
  444. "service-function": [
  445. {
  446. "ip-mgmt-address": "192.168.60.30",
  447. "name": "dpi-1",
  448. "nsh-aware": "true",
  449. "sf-data-plane-locator": [
  450. {
  451. "ip": "192.168.70.30",
  452. "name": "dpi-1-dpl",
  453. "port": 4790,
  454. "service-function-forwarder": "SFF1",
  455. "transport": "service-locator:vxlan-gpe"
  456. }
  457. ],
  458. "type": "dpi"
  459. },
  460. {
  461. "ip-mgmt-address": "192.168.60.40",
  462. "name": "firewall-1",
  463. "nsh-aware": "true",
  464. "sf-data-plane-locator": [
  465. {
  466. "ip": "192.168.70.40",
  467. "name": "firewall-1-dpl",
  468. "port": 4790,
  469. "service-function-forwarder": "SFF2",
  470. "transport": "service-locator:vxlan-gpe"
  471. }
  472. ],
  473. "type": "firewall"
  474. }
  475. ]
  476. }
  477. }
  478.  
  479. sending service function forwarders
  480. PUT http://192.168.60.1:8181/restconf/config/service-function-forwarder:service-function-forwarders
  481. {
  482. "service-function-forwarders": {
  483. "service-function-forwarder": [
  484. {
  485. "ip-mgmt-address": "192.168.60.20",
  486. "name": "SFF1",
  487. "service-function-dictionary": [
  488. {
  489. "name": "dpi-1",
  490. "sff-sf-data-plane-locator": {
  491. "sf-dpl-name": "dpi-1-dpl",
  492. "sff-dpl-name": "sff1-dpl"
  493. }
  494. }
  495. ],
  496. "service-function-forwarder-vpp:sff-netconf-node-type": "netconf-node-type-honeycomb",
  497. "service-node": "sff1",
  498. "sff-data-plane-locator": [
  499. {
  500. "data-plane-locator": {
  501. "ip": "192.168.70.20",
  502. "port": 4790,
  503. "transport": "service-locator:vxlan-gpe"
  504. },
  505. "name": "sff1-dpl"
  506. }
  507. ]
  508. },
  509. {
  510. "ip-mgmt-address": "192.168.60.50",
  511. "name": "SFF2",
  512. "service-function-dictionary": [
  513. {
  514. "name": "firewall-1",
  515. "sff-sf-data-plane-locator": {
  516. "sf-dpl-name": "firewall-1-dpl",
  517. "sff-dpl-name": "sff2-dpl"
  518. }
  519. }
  520. ],
  521. "service-function-forwarder-vpp:sff-netconf-node-type": "netconf-node-type-honeycomb",
  522. "service-node": "sff2",
  523. "sff-data-plane-locator": [
  524. {
  525. "data-plane-locator": {
  526. "ip": "192.168.70.50",
  527. "port": 4790,
  528. "transport": "service-locator:vxlan-gpe"
  529. },
  530. "name": "sff2-dpl"
  531. }
  532. ]
  533. }
  534. ]
  535. }
  536. }
  537.  
  538. sending service function chains
  539. PUT http://192.168.60.1:8181/restconf/config/service-function-chain:service-function-chains/
  540. {
  541. "service-function-chains": {
  542. "service-function-chain": [
  543. {
  544. "name": "SFC1",
  545. "sfc-service-function": [
  546. {
  547. "name": "dpi-abstract1",
  548. "type": "dpi"
  549. },
  550. {
  551. "name": "firewall-abstract1",
  552. "type": "firewall"
  553. }
  554. ],
  555. "symmetric": "true"
  556. }
  557. ]
  558. }
  559. }
  560.  
  561. sending service function paths
  562. PUT http://192.168.60.1:8181/restconf/config/service-function-path:service-function-paths/
  563. {
  564. "service-function-paths": {
  565. "service-function-path": [
  566. {
  567. "context-metadata": "NSH1",
  568. "name": "SFP1",
  569. "service-chain-name": "SFC1",
  570. "starting-index": 255,
  571. "symmetric": "true"
  572. }
  573. ]
  574. }
  575. }
  576.  
  577. sending rendered service path
  578. POST http://192.168.60.1:8181/restconf/operations/rendered-service-path:create-rendered-path/
  579. {
  580. "input": {
  581. "name": "RSP1",
  582. "parent-service-function-path": "SFP1",
  583. "symmetric": "true"
  584. }
  585. }
  586. {"output":{"name":"RSP1"}}
  587. Connection to 127.0.0.1 closed.
  588. Connection to 127.0.0.1 closed.
  589. vxlan_gpe_tunnel0
  590. set interface l2 bridge: unknown interface `vxlan_gpe_tunnel2 1 1'
  591. Connection to 127.0.0.1 closed.
  592. vxlan_gpe_tunnel0
  593. set interface l2 bridge: unknown interface `vxlan_gpe_tunnel2 1 1'
  594. Connection to 127.0.0.1 closed.
  595. PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
  596.  
  597. --- 192.168.2.2 ping statistics ---
  598. 5 packets transmitted, 0 received, 100% packet loss, time 4033ms
  599.  
  600. Connection to 127.0.0.1 closed.
  601. PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
  602.  
  603. --- 192.168.2.2 ping statistics ---
  604. 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
  605.  
  606. Connection to 127.0.0.1 closed.
  607. --2016-11-16 08:14:25-- http://192.168.2.2/
  608. Connecting to 192.168.2.2:80... failed: Connection timed out.
  609. Retrying.
  610.  
  611. --2016-11-16 08:16:33-- (try: 2) http://192.168.2.2/
  612. Connecting to 192.168.2.2:80...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!