ProgrammableFlow Controller Trial Reference Guide. Set up instructions

Transcription

1 ProgrammableFlow Controller Trial Reference Guide Thank you for evaluating NEC ProgrammableFlow Controller (PFC). This document provides information specific to the set up and operation of PFC trial version and provides information on the differences between the trial and the production version of PFC. Set up instructions 1. Importing PFC VM into hypervisor There is a possibility that PFC fails to start when you downgrade the spec of PFC VM or when you run PFC VM in a large scale environment where many flows are generated. In such a case, please restore or upgrade the spec of PFC VM to resolve the issue.

2 2. Logging into PFC with the following credential - For CLI User ID: root, Password: pfcpfc User ID: pfcadmin, Password: pfcadmin - For WEB-GUI Address>:8082/nwviewer User: Administrator, Password: nwpass When you are using Firefox (after v39), Chrome(after v ), or Internet Explorer(with KB ), your browser declines connecting to PFC. In that case, please add the encryption ciphers to the configuration file on PFC as follows. 1. Open the configuration file /opt/nec/pfc/agent/bin/nwviewer/tomcat/conf/server.xml and specify ciphers. [root@pfc ~]# vi /opt/nec/pfc/agent/bin/nwviewer/tomcat/conf/server.xml <!-- Define a SSL HTTP/1.1 Connector on port 8443 This connector uses the JSSE configuration, when using APR, the connector should be using the OpenSSL style configuration described in the APR documentation --> <Connector port="8082" protocol="http/1.1" SSLEnabled="true" maxthreads="150" scheme="https" secure="true" keystorefile="/opt/nec/pfc/agent/sg/nwviewer/keystore_test" keystorepass="pfcpfcpfc12" keyalias="nwviewer" ciphers="tls_rsa_with_aes_256_cbc_sha256,tls_rsa_with_aes_256_cbc_sha, TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_ WITH_3DES_EDE_CBC_SHA" Add this line clientauth="false" sslprotocols="tlsv1,tlsv1.1,tlsv1.2,sslv2hello" /> <!-- Define an AJP 1.3 Connector on port > 2. Reboot PFC [root@pfc ~]# reboot

3 3. Before you use this software, you have to install an initial license. Refer to Chapter 4.1 of Command Reference Manual to install the license. This license will expire 90 days after installation. 1. Issue the command pfc_licmgt install. Example: ~]# pfc_licmgt install <file path to the license> license has been successfully installed. You will see following message before the license is expired. Notice: Trial license will expire on YYYY-MM-DD. Please contact your local sales representative for an official edition. When an OpenFlow enabled switch communicates with the PFC before you install the license, PFC rejects the connection with the switch. You can check the situation as follows. [root@pfc ~]# pfcshell PFC# cm real-network [real-network] PFC# show license ofs rejected-ofs Date: :50:24 PST License Type:OFS DPID License checked :49:22 1 OFS is rejected Total count: 1 License Type:OFvS DPID License checked :49:22 1 OFvS is rejected Total count: 1 In such a case, after installing the license, you have to clear this information from PFC using "clear license rejected-ofs" with specifying the appropriate license type. Please refer to both chapter of configuration guide and chapter of command reference to check the detail. [root@pfc ~]# pfcshell PFC# cm real-network [real-network] PFC# clear license rejected-ofs license-type ofvs Clear rejected OFvS information PFC# clear license rejected-ofs license-type ofs Clear rejected OFS information

4 4. Setting the IP address (Optional) The default IP of this trial version is If you want to change the IP address of PFC trial version, complete the following procedure. 1. Stop the cluster function Issue the command "pfc_stop_cluster". Example: ~]# pfc_stop_cluster Cluster will be stopped. 2. Start the network setup tool Issue the command "pfc_netsetup" to run the network setup tool. Then you can change the IP address. Please refer to Chapter of configuration guide. 3. Changing the /etc/hosts file Please change the IP address information in this file. 4. Reboot There is a possibility that PFC fails to start when you missed one of the above steps. Please ensure that the interface settings is configured as you expected after the above steps by running the command pfc_show_if_status. Then, check the content of /etc/hosts file as well. For instance, you should get the following result after you changed host name and IP address to and pfc, respectively. [root@pfc ~]# pfc_show_if_status [Interface list] Interface IP address BPRT HW address ONB UP MTU eth /24 none 000C.298A.4329 yes UP 1500 Ensure IP address is correct [root@pfc ~]# cat /etc/hosts /24 pfc.localdomain pfc Ensure both IP address and host name are correct

5 5. Configuring L3 loopback (Optional) You do not need to do this step while you use the switches listed below. However, please read the following instruction well if you want to connect other switch to PFC and create L3 VTN on it. Open vswitch NEC PF5240/PF5248/PF5820 Dell S4810/S4820T/S5000/S6000 Alcatel-Lucent Enterprise OS6900-T20/T40/X20/X40 There are 2 types of OpenFlow switch in terms of the implementation for L3 loopback. Please add the required configuration to PFC as follows if your switch is the type that expects PFC to specify OFPP_IN_PORT instead of physical port as the output port. 1. Open the configuration file /opt/nec/pfc/agent/sg/pthctl/pfc_pthctl_sys.conf and incorporate the following lines right before [MIRROR_PACKET_IN]. [root@pfc pthctl]# vi /opt/nec/pfc/agent/sg/pthctl/pfc_pthctl_sys.conf [FLOW_ENTRY] Add this line support_action_ofpp_in_port=1 Add this line [MIRROR_PACKET_IN] 2. Reboot PFC. [root@pfc pthctl]# reboot

6 Differences between the trial and production versions 1. Untagged frames are not supported Trial version does not support untagged frame from outside. If you want to connect some host and device to the OpenFlow network, that host must send tagged frame to the OpenFlow network. 2. Number of server interfaces The production version of the ProgrammableFlow Controller requires 6 NIC ports on the PFC server. These NIC ports are used for OpenFlow control, management, and cluster interconnect between an active PFC and a standby PFC. The trial version of the Controller shares all traffic on one NIC Port. 3. Features for Redundancy in PFC Redundancy is a feature to increase the availability of PFC. For details, refer to the Chapter 6. Setting Up Redundancy in PFC in the Configuration Guide. PFC redundancy is unsupported in this trial version. For this reason, you do not need to execute the steps to set up the cluster that are described in 6.2 Setting Up the Cluster in the Configuration Guide. 4. The following functions do not work in the trial version: - Server redundancy configuration and cluster switchover for the availability improvement of PFC. - Operation monitoring, abnormality detection and fault handling (automatic recovery, failover and server shutdown) for each targets of monitoring. For details, refer to Redundancy Monitoring Function in the Configuration Guide. - Failure recovery by OS reboot based on "restart level". For details about "restart level", refer to pfc_clear_restart_level in the Command Reference. Please do not use the following commands related to setting up the cluster. For details about each commands, refer to 4.3 Cluster in the Command Reference. pfc_setup_cluster_config pfc_show_cluster_config pfc_setup_redundancy The following commands related to redundancy perform the same as when these are executed on PFC that is configured as "single configuration". pfc_switch_cluster pfc_show_cluster_status pfc_stop_cluster 5. GUI function The PFC production version has both Windows and Web based Graphical User Interfaces. Please use WEB base GUI for this trial version. This trial version has already setup the WEG-GUI configuration. You can use WEG GUI if you connect " Address>:8082/nwviewer" from web browser. The trial version of the PFC does not support the Windows UI. 6. Upgrading the PFC Software The version upgrade of PFC Software is unsupported in this trial version. Please do not use the pfc_migrate_shared_data command and the pfc_update command. These are used during upgrading.

7 7. Other Trial version may not provide some functions that are supported by production version. As a reference, you can check the function listed as interoperable with Open vswitch.