Vertiv™ NetSure™ Control Unit (NCU) User Manual
TA-NWT-000199
TA-NWT-000200
TA-NWT-001360
2.12.2 NCU TL1 Feature
The NCU can send and receive TL1 messages and responses between itself and a customer client application. This includes
autonomous messages sent by the NCU to notify the customer client application of alarms.
TL1 messages contain parameter values that indicate attributes and the state associated to signals. The NCU provides configuration
parameters for all signals as needed to specify values of the TL1 attributes and states that are required in the TL1 messages.
Configuration of TL1 attribute parameters is accessed through the WEB interface.
NCU TL1 Port
The NCU TL1 port transports TL1 messages between the NCU and a customer network operations center or client. Access through
this interface is restricted to a User who logs on with the TL1 ‘ACTIVATE-USER’ request message.
The NCU TL1 port uses the telnet protocol (not SSH) over the NCU’s Ethernet connection and has requirements for specific
operational settings. The NCU supports TL1 telnet operation over IPV4 and IPV6 networks. The NCU TL1 port is enabled and
configured through the WEB interface.
Only one telnet connection through the NCU TL1 port is allowed at any time. The telnet connection is disabled when the TL1
interface is not selected by the customer. The telnet connection is considered disabled when all telnet ports indicate closed during a
network scan of the Ethernet connection.
NCU TL1 Configuration
Webpages are provided in the NCU Web interface to configure signal parameters and settings that specify the signal’s TL1 attributes.
See “Setting TL1 Parameters” on page 34.
2.13 Machine-to-Machine HTTP Interface
2.13.1 Description
This interface option must be specified when the system is ordered. It is enabled or disabled at the factory.
The Machine-to-Machine HTTP Interface option provides the ability for a machine to poll the NCU controller using a special URL for a
pre-configured packet of information using HTTP-GET.
The URL requests are sent to the controller using the same port as HTTP. Note this function is not available over HTTPS. This
interface assumes that the customer is on a secured network.
The interface can be used to retrieve data using third-party programs such as WGET and CURL.
The interface works with IPv4 and IPv6.
The interface is available from the controller when the controller uses a fixed IP address or a DHCP address.
The interface only supports one request/query at a time.
2.13.2 Using the Machine-to-Machine HTTP Interface Option
Refer to the following.
Request
The request consists of the scheme (http), authority (the IP address of the controller), the path (/data), and the query. The end of the
query can be specified by # or by the end of the URL. Fragments are not supported.
To Next Page
Loading...
Need help?
General
