CONFIGURATION AND INSTALLATION. 13.1. The Product and/or infrastructure shall be installed and/or configurated by Proximus if this is expressly provided for in the Contractual Service Description or Order Form.
CONFIGURATION AND INSTALLATION. (a) Subject to Licensee fulfilling its obligations as set out in Section 5(b), Licensor shall provide the INTERLINX PLATFORM via Interlinx hosted and managed software service via https at the Designated Site and configure the INTERLINX PLATFORM to render it compatible with such computer. Licensor shall also deliver to Licensee one copy of the Documentation. Licensee will provide co-operation and assistance through its IT, diagnostic imaging, business process and operations personnel, as reasonably required by Licensor in order to provide the configuration and installation services hereunder. Licensor shall make reasonable efforts to meet the targeted date set out in Schedule “A” for completion of initial configuration and installation but shall not be liable for its failure to do so. Licensor shall provide prompt notice to Licensee if it determines at any time that there will be any delay in completing the configuration and installation.
CONFIGURATION AND INSTALLATION. 13.1. The Product and/or infrastructure shall be installed and/or configurated by PROXIMUS ICT if this is expressly provided for in the Contractual Service Description or Order Form.
CONFIGURATION AND INSTALLATION. 13.1. The Product and/or infrastructure shall be installed and/or configurated by Interbyte if this is expressly provided for in the Contractual Service Description or Order Form.
CONFIGURATION AND INSTALLATION. Save the monitoring branch under folder /opt/xxxxx: mkdir -p /opt/xxxxx/ git clone xxxxx://xxxxxx.xxx/xxxx-i2cat/xxxxx.git /opt/xxxxx/ git checkout monitoring cd /opt/xxxxx/modules/monitoring/public/src Configuration of the application contains a list of RM location/credentials, partitioned by island. Normally, the monitor application will show status for all resources that have been reported at least once by an RM, but single resources such as SDN links can also be listed explicitly in the configuration file. This allows the monitor application to know about these links even if they have never been reported (since application start), and to display such resources as down or unavailable. The configuration details are found in localsettings.py. The repository contains a localsettings.py.EXAMPLE file. New resources or RMs can be added to this file as they become available. The file provided contains the configuration for available XXXXX resources. The island pages are based on web.py templates found in the templates/ subdirectory. To add a specific layout or style to the public monitoring pages, the templates/island.html can be changed. Static content such as the island description must be added to the static/ subdirectory, where <island>.png is the island topology shown on the respective island page. Additional static files (such as .css) can be added here as well, if for example they are needed aGer changes to the templates.
CONFIGURATION AND INSTALLATION. As part of the Fixed Price, software subscription services, underlying software, database resources and/or database interfaces shall be configured by Vendor for TSLAC’s use and Authorized Users’ use in accordance with the Specifications, as defined and detailed in the TSLAC Solicitation and/or Vendor’s Response (“Configured Service(s)”).
CONFIGURATION AND INSTALLATION. 6.1 The Software may only be installed on a computer at the Site.
CONFIGURATION AND INSTALLATION. There is no separate installation except for the java library. The source code is available from the git repository: $ git clone xxxxx://xxxxxx.xxx/xxxx-i2cat/xxxxx/tree/aist The library of the required java is the following. $ ls -l ${CXF_HOME} lrwxrwxrwx 1 root root 17 Jun 12 2014 /opt/cxf -> apache-cxf-2.7.11 LIBS=$LIBS:${NSI_HOME}/clientapi/build/jar/nsi2_ client.jar LIBS=$LIBS:${NSI_HOME}/nrm/lib/commons-logging-1.1.1.jar LIBS=$LIBS:${NSI_HOME}/nrm/lib/log4j-1.2.13.jar for f in ${CXF_HOME}/lib /*.jar do LIBS = $LIBS:$f done Please note that to access the TN-RM you need Provider Agent or Aggregator of NSIv2 running. Now this is configured in nsi2interface.py and the following change must be made in order to make the connection. AIST-NRM: pURL = 'xxxxx://000.0.0.0:00000/xxxx_xxx/Xxxxxxxx/XxxxxxxxxxXxxxxxxx' AIST-DUMMY-NRM: pURL = 'xxxx://000.0.0.0:00000/xxxxxxxx/xxxxxxxx/XxxxxxxxxxXxxxxxxx' proxy: $ cd ${eiSoil_HOME}/src/vendor /tnrm; ./xxxxx.xx CH: $ cd ${GCF_HOME}; python src/gcf-ch.py --host=000.000.00.xxx --port 8000 eiSoil: $ cd ${eiSoil_HOME}/src; python main.py
CONFIGURATION AND INSTALLATION. The initdb.py script is used to create a database and/or schema for the MS. The localsettings.py file is used to configure the MS application. Its settings include: • IP address and port for the REST API. • Public IP address and port (in case the MS runs in a private address range and is forwarded through a firewall). • IP address, port and url of a higher level MS or MMS where data is to be forwarded. • Address, port and basic auth credentials (user:password) of the database. • Community name for the SNMP manager.
CONFIGURATION AND INSTALLATION. This section explains the configuration of SNMP for hardware switches, and the installation and configuration for Open vSwitch and host resources. To test SNMP on a device, use: snmpwalk -v2c -c <community_name> <switch_IP> The snmpwalk command is available on the Debian snmp package. <community_name> is the name of the SNMP community, which is previously chosen by the switch admin- istrator. Default community names are typically public or private. Community names are local to island and not passed through the monitoring framework. Likewise, access to the SNMP agent is local to island and not available to other XXXXX partners (i.e., firewalled or on a different network). When using persistent monitoring of any kind (including SNMP) as well as creating slices on Open vSwitch, it is important for consistency to make sure that the network ports (e.g., tap, eth1, xxxx etc.) added to a switch are always assigned the same OpenFlow port number. Older versions of Open vSwitch do not allow to fix an OpenFlow port number for interfaces added to a switch. This means that upon rebooting the machine, interfaces may be assigned random port numbers, which is problematic since flowspaces are constructed using these port numbers (not interface names), and SNMP reports port names, not OpenFlow port numbers. At least version 1.10.0-1 of Open vSwitch must be used. To add a port with a certain fixed OF port number (e.g., interface tap2 as OF port number 2 on switch myswitch): ovs-vsctl add-port myswitch tap2 -- set Interface tap2 ofport_request=2 The ofport_request is kept in a separate column in the Open vSwitch database and is persistent (unlike the ofport column). Note that the add-port and set command must be on the same line to be effective. NEC 3640-xx/8800 You may want to set the hostname of the switch so it appears as sysName in SNMP MIB. SNMP is always running. To enable access for an SNMP manager to retrieve MIB from the agent on the switch, create a SNMP community (in enable, config context). # snmp-server community <community_name> ro # save To restrict access not just by community, but also by IP address (of the SNMP manager), a generic access-list (with ID=1 in the example below) can be created, and then the community is restricted to this list: # access-list 1 permit 10.216.132.12 0.0.0.0 # snmp-server community <community_name> ro <1> # save Open vSwitch Open vSwitch does not support SNMP. Instead, it uses the Linux SNMP [7] daemon to run an agent t...
