Troubles setting up Visualizer with 3810

[juuso]

Hi!

We're having some troble getting Network Visualizer work with 3810 switches. We have this really simple setup; two hosts connected to the switch and a HP VAN controller using oobm.

When we try to deploy a capture session, we get the following error: "Deploy failed, reattempt in progress". According to the manual, we should wait till the switch to recovers, but we have already waited days without any improvement. We also tried the same setup with OpenvSwitch and mininet and both worked just fine, so I guess we have some configuration issues with our 3810, but can't pinpoint the exact mistakes...  

I've included relevant lines from the log file as well as our switch configuration. 

[2017-01-16 09:31:22.203] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 Session name Test_Capture ,operation attempted START  
[2017-01-16 09:31:22.216] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 Advanced capture creation 
[2017-01-16 09:31:22.231] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 valid switch selection case..add to map 
[2017-01-16 09:31:22.233] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 valid switch selection case..add to map 
[2017-01-16 09:31:22.234] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 synthesized DeviceCaptureSessionConfig [RawDeviceMonitorConfig [id=null]] 
[2017-01-16 09:31:22.235] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 devConfigList size:1 
[2017-01-16 09:31:22.235] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              switch IP  20.0.0.102  
[2017-01-16 09:31:22.236] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              Device object  { Device:name=3810M-24G-1-slot Switch,ip=20.0.0.102,dpid=00:14:70:10:6f:8e:d9:00,vendor=HP,firmware=KB.16.01.0004,snmp-details=adminuser,ports=[],,vlan=0  
[2017-01-16 09:31:22.253] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              inside create Service Insertion capture session 
[2017-01-16 09:31:22.280] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              SNMP error:RESPONSE_PDU_VARBIND_ERROR cause:null  
[2017-01-16 09:31:22.280] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              tunnel does not exists ...snmp... .create a new one 
[2017-01-16 09:31:22.330] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              SNMP write error:RESPONSE_PDU_ERROR cause:null  
[2017-01-16 09:31:22.342] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              Tunnel creation on switch failed SNMP Exception:{} com.hp.mvisor.common.exception.dm.SnmpException: null
[2017-01-16 09:31:22.441] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              inside create Service Insertion capture session 
[2017-01-16 09:31:22.469] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              SNMP error:RESPONSE_PDU_VARBIND_ERROR cause:null  
[2017-01-16 09:31:22.469] INFO  http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              tunnel does not exists ...snmp... .create a new one 
[2017-01-16 09:31:22.515] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              SNMP write error:RESPONSE_PDU_ERROR cause:null  
[2017-01-16 09:31:22.517] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              Tunnel creation on switch failed SNMP Exception:{} com.hp.mvisor.common.exception.dm.SnmpException: null
[2017-01-16 09:31:22.521] ERROR http-bio-8443-exec-2         hp.sdn.mv.deviceMgmt                                              SNMP error:RESPONSE_PDU_ERROR cause:null configError:null  
[2017-01-16 09:31:22.521] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 DEVICE_FAILED_CREATE 
[2017-01-16 09:31:22.522] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 Updating filter status 
[2017-01-16 09:31:22.555] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 Calculated state : FAILED 
[2017-01-16 09:31:22.571] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 updateCaptureConfigStatus -state updated deploy:true, state:FAILED 
[2017-01-16 09:31:22.579] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 DEVICE_AVAILABILITY_CHANGED failed 20.0.0.102 size 1 
[2017-01-16 09:31:22.579] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 DEVICE_AVAILABILITY_CHANGED failed 20.0.0.102 size 1 
[2017-01-16 09:31:22.583] INFO  http-bio-8443-exec-2         hp.sdn.mv.monitor                                                 DAL completed the Capture Session activation process. 
[2017-01-16 09:31:22.596] ERROR http-bio-8443-exec-2         hp.sdn.rs                                                         Capture sesson start failed: com.hp.mvisor.common.config.MonitorOperationException: Activate:Failed 
[2017-01-16 09:31:22.599] ERROR http-bio-8443-exec-2         hp.sdn.rs                                                         Capture sesson Activate:Failed 
[2017-01-16 09:31:22.783] INFO  http-bio-8443-exec-11        hp.sdn.mv.monitor                                                 Fetching filter table for CaptureSessionid:3c0b5032-d9e2-4764-8425-121bdfb1c25e 
[2017-01-16 09:31:22.789] INFO  http-bio-8443-exec-11        hp.sdn.mv.monitor                                                 Fetching filters for CaptureSession id:3c0b5032-d9e2-4764-8425-121bdfb1c25e 

Running configuration:

; JL071A Configuration Editor; Created on release #KB.16.01.0004
; Ver #0c:01.7c.59.f4.7b.ff.ff.fc.ff.ff.3f.ef:

hostname "Aruba-Y"
module 1 type jl071x
flexible-module A type JL083A
fault-finder broadcast-storm sensitivity high
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-hdx sensitivity high
fault-finder duplex-mismatch-fdx sensitivity high
fault-finder link-flap sensitivity high
snmp-server community "public" unrestricted
snmpv3 enable
snmpv3 group managerauth user "adminuser" sec-model ver3
snmpv3 user "adminuser"
snmpv3 user "initial"
openflow
   controller-id 11 ip 20.0.0.11 controller-interface oobm
   instance "testi20"
      member vlan 20
      controller-id 11
      version 1.3 only
      enable
      exit
   enable
   exit
oobm
   ip address 20.0.0.102 255.255.255.0
   exit
vlan 1
   name "DEFAULT_VLAN"
   no untagged 1-8,19-24
   untagged 9-18,A1-A4
   ip address 192.168.1.102 255.255.255.0
   exit
vlan 10
   name "vlan10"
   untagged 1-8
   no ip address
   exit
vlan 20
   name "vlan20"
   untagged 19-24
   no ip address
   exit

 BR,
Juuso

[Scott_Koster · Accepted solution]

Hi Juuso,

Network Visualizer will not work with the OOBM connection due to the underlying Service Insertion technology used to enable the solution.  Please create another VLAN, assign a single port to it, and use it instead of OOBM for management in your environment.

example:

vlan 350

untagged <port num>  (that connects to controller network with Visualizer)

ip address 20.0.0.102

controller-id 11 ip 20.0.0.11 controller-interface vlan 350

Hope that helps.  (SNMP is another component needed to make Visualizer work, but I suspect your configuration is correct there)

Best Regards,

-Scott

[juuso]

Excellent!

No wonder every single example I have seen, had vlan instead of OOBM :)

We also had Network Protector complaining that the switch does not support Service Insertion tunnels and changing the OOBM to vlan also fixed this issue. 

Thank you,
Juuso