HPE Network Protector SDN Application Part 6 - Demo of Physical Switch configuration

Key Takeaways

so on the controller let's have a look at one of the switches again so I'll have a look at this 3500 when we look at flows we can see once again that DNS traffic is being intercepted and sent to the controller for further processing what does it look like on the switch so I'll log into the switch as you can see here this is a 3500 while switch running 15 17 version of software I'll tap Show run you can see that most interfaces are disabled on the switch this is the important piece you need to enable SNMP on the switch because Network protector configures some options on the switches using SNMP and notice here under OpenFlow we have various controllers configured but the only controller that's being used for the demonstration is controller 12 with IP address 192168 5612 that's the network protector controller so we've enabled OpenFlow globally on the switch we've created two instances the instance that we're using for this demonstration is instance VLAN 40 which has a member VLAN of 40 so the host in VLAN 40 is having its traffic intercepted and sent to controller with IP address 1 192168 5612 we're using OpenFlow 1.3 and we've enabled the OpenFlow instance that configuration is very similar to the configuration of other switches in this example here I'll type show OpenFlow instance of VLAN 40 and in the output we can see that the negotiated version of openflows 1.3 the VLAN that OpenFlow is enabled on is VLAN 40 we can see the data path identifier of the switch on provision switches least significant 48 bits is the MAC address most significant 16 bits is the VLAN number and importantly at the bottom here we can see that we are connected to the controller and the connection is active show OpenFlow instance VLAN 40 flows this shows us the OpenFlow table or tables on the switch and if we scroll down we can see this flow in tree ether type is IP version 4 IP protocol is UDP destination Port is 53 Mac addresses and other information are set to wild cards in other words they're not used the controller ID that we're sending traffic to is controller 12 notice apply actions controller Port traffic that is matched by this flow entry in other words DNS is going to be forwarded to the controller for processing