COMPARACION DE METODOS DE ENSAYO AASHTO Y SHRP
MÓDULO RESILIENTE DE SUELOS DE SUBRASANTE
3. TLOV = Transductores lineales Diferenciales, Variables,
Device Attributes
The TunnelAgent Control Module will add or replace entries into the device Registry to set various Device Attributes to reflect the use of an instance of the Motorola Tunnel Service. Table 3 below details the Device Attributes that can be reported by the TunnelAgent Control Module.
Chapter 4 – Control Modules -- 29
Table 3 – Device Attributes
Attribute Name Explanation
UserAttribute.TunnelService.ConnectionType
This Device Attribute is reported as having a value of “0” when the Tunnel Agent is turned off so that direct connection from Workstation PC to device is allowed.
This Device Attribute is reported as having a value of “1” when the Tunnel Agent is configured for “Workstation PC contacts Tunnel Service which contacts device” (i.e. Indirect Contact, Inbound Mode).
This Device Attribute is reported as having a value of “2” when the Tunnel Agent is configured for “Workstation PC contacts Tunnel Service which is contacted by device” (i.e. Indirect Contact, Outbound Mode).
UserAttribute.TunnelService.TunnelAgentPort This Device Attribute is reported only if the
Device Attribute
“UserAttribute.TunnelService.ConnectionType” is reported as having a value of “1”.
This Device Attribute reports the Port on which the Tunnel Agent is listening and at which it should be contacted by a Tunnel Service when the Tunnel Agent is configured for “Workstation PC contacts Tunnel Service which contacts device” (i.e. Indirect Contact, Inbound Mode).
UserAttribute.TunnelService.TunnelIpAddr This Device Attribute is reported only if the
Device Attribute
“UserAttribute.TunnelService.ConnectionType” is reported as having a value of “1” or “2”.
This Device Attribute reports the IP address or Network Name at which the Workstation PC should contact the Tunnel Service.
UserAttribute.TunnelService.TunnelPort This Device Attribute is reported only if the
Device Attribute
“UserAttribute.TunnelService.ConnectionType” is reported as having a value of “1” or “2”.
This Device Attribute reports the TCP Port at which the Workstation PC should contact the Tunnel Service.
Related Control Modules
GetAdapters
As described in Understanding MSP – Understanding Control Modules, the GetAdapters Control Module acquires and delivers information about all networks adapters that are active and connected in a device and what it considers to be the “best” adapter to be used to contact the device.
The TunnelAgent Control Module does not duplicate the functionality of the GetAdapters Control Module. In particular, since the GetAdapters Control Module already reports the IP Address via which the device can be contacted, the TunnelAgent Control Module leverages this information for use in Indirect Contact Inbound Mode.
Chapter 5 – Installation and
Configuration
Overview
This chapter discusses the installation and configuration of instances of the Tunnel Service.
Motorola Tunnel Service Target Hardware
An instance of the Motorola Tunnel Service software should be installed on one or more Windows PCs within an Enterprise when the need for enhanced contactability of devices is required. Instances of the Motorola Tunnel Service software could be installed on any dedicated or shared Windows PC or Windows Virtual Machine that is running a supported Windows Operating System.
Motorola Tunnel Service Pre-requisites
Important:
Because each instance of the Motorola Tunnel Service requires a Control Edition License, the
Motorola Tunnel Service can only be used with MSP Control Edition.
Instances of the Motorola Tunnel Service must always be installed using MSP onto a Windows
PC that is already being Directly Managed by MSP via the Windows PC Client. Note:
For information on the Windows PC Client and how to get a Windows PC to be Directly Managed by MSP, refer to the MSP Client Software Guide.
In addition to the Windows PC Client, the Motorola Tunnel Service requires that the following pre- requisites be present on the Windows PC before the Motorola Tunnel Service can be successfully installed onto that Windows PC:
Java Runtime Environment
The MSP recommended Java Runtime can be installed via the TunnelService_Prerequisite Package.
Motorola Tunnel Service Prerequisites can be manually installed onto a Windows PC or can be deployed to a Windows PC using MSP via a Package that adds all the necessary pre-requisites onto a Windows PC. Once a given Windows PC has been discovered by MSP and is shown as having a Device Class of “Windows PC”, the Tunnel Service Pre-requisites Package can be installed onto that Windows PC by deploying the Package “TunnelService_Prerequisites.apf” to that Windows PC.
Note:
Installing the Motorola Tunnel Service Pre-requisites Package will install all the Motorola Tunnel Service Pre-requisites, but uninstalling the Motorola Tunnel Service Pre-requisites Package will not remove those pre-requisites. In particular, uninstalling the Motorola Tunnel Service Pre- requisites Package will not prevent the Motorola Tunnel Service, if it has been installed, from continuing to operate.
If the previous version of Java is already installed on the machine and is being used by any of the process then installation of pre-requisite will fail. This is because during java upgrade instead of doing the silent installation it throws up the error message on the server saying Java is being used by one of the process. Always make sure no program is using the Java before installing the pre-requisite
During the un-installation of Tunnel Service make sure that Tunnel Service Status viewer and Tunnel Service Configuration Wizard is closed. This is important because these two components are part of Tunnel Service package and will be removed during the un-installation process. If these file being used then Tunnel Service un-installation will fail.
Motorola Tunnel Service Deployment
An instance of the Motorola Tunnel Service is deployed using MSP via a Package that adds Tunnel Service support into the Windows PC Client running on a Windows PC. Once a given Windows PC has been discovered by MSP and is shown as having a Device Class of “Windows PC”, the Tunnel Service can be installed onto that Windows PC by deploying the Package “TunnelService_Setup.apf” to that Windows PC. If any of the Motorola Tunnel Service Pre- requisites are not met on that Windows PC, then the installation of that Package will fail. Once the Motorola Tunnel Service Package is successfully installed on the Windows PC, the instance of the Motorola Tunnel Service on that Windows PC will get discovered by MSP and will be shown as having a Device Class of “TunnelServiceProxy”. This will be an indication that the instance of the Motorola Tunnel Service on that Windows PC is active and ready to be
Chapter 5 – Installation and Configuration -- 33
Motorola Tunnel Service Configuration
Each instance of the Motorola Tunnel Service is initially configured with defaults that may allow it to be used right away. In some cases, however, the default configuration may not be suitable and re-configuration may be required. An instance of the Motorola Tunnel Service software can be configured in any of the following ways:
TunnelService.Configuration Settings Object
Once an instance of the Motorola Tunnel Service is installed on a Windows PC and discovered as a managed device, then it is ready to be configured. One or more instances of the Motorola Tunnel Service can be configured by creating and deploying a Settings Object of Settings Class TunnelService.Configuration.
Important:
TunnelService.Configuration Settings Objects can only be deployed to managed devices of
Device Class “TunnelServiceProxy”. If a TunnelService.Configuration Settings Object is
deployed to any other Device Class, such as to a Windows PC, then it will fail. This is true even though the managed device of Device Class “TunnelServiceProxy” is running on the Windows PC.
If multiple instances of the Motorola Tunnel Service are installed on multiple Windows PCs, they could all be configured using a single TunnelService.Configuration Settings Object. Whether this is appropriate to do would depend on whether the desired configuration is the same for all instances. Sending the same Settings Object to multiple instances could easily be accomplished by using a Provisioning Policy with an Applicability Rule that includes a test for the Device Class “TunnelServiceProxy”,
The following Settings can be used to configure the operation of an instance of the Motorola Tunnel Service.
Description
This Setting specifies an optional overall description which can be used to enter comments or other information about this Settings Object.
Workstation to Tunnel Service Port:
This Setting specifies the Port that should be used by Workstation PCs to contact the instance of the Motorola Tunnel Service.
This Setting is applicable for Indirect Contact Inbound Mode (i.e. when Connection Type is set to “Workstation PC contacts Tunnel Service which contacts device”) or Indirect Contact Outbound Mode (i.e. when Connection Type is set to “Workstation PC contacts Tunnel Service which is contacted by device”).
Default Value: 7778 Note:
If the default port is changed for an instance of the Motorola Tunnel Service, then a
corresponding change will need to be made to the configuration of the Motorola Tunnel Agent for all devices that will be used with that instance of the Motorola Tunnel Service.
Device to Tunnel Service Port:
This Setting specifies the Port that should be used by the Motorola Tunnel Agent running on devices to contact the instance of the Motorola Tunnel Service when Outbound Mode is used. This Setting is applicable only for Indirect Contact Outbound Mode (i.e. when Connection Type is set to “Workstation PC contacts Tunnel Service which is contacted by device”).
Default Value: 7779 Note:
If the default port is changed for an instance of the Motorola Tunnel Service, then a
corresponding change will need to be made to the configuration of the Motorola Tunnel Agent for all devices that will be used in Outbound Mode with that instance of the Motorola Tunnel Service.
Log Level:
This Setting specifies the level of logging to be generated by the instance of the Motorola Tunnel Service.
The following values are possible: SEVERE
This is the lowest level of logging available. Only the occurrence of Errors will be logged. WARNING
The occurrence of Errors and Warnings will be logged. INFO
The occurrence of Errors, Warnings, and Informational Messages will be logged. DEBUG
This is the highest level of logging available. The occurrence of Errors, Warnings, Informational Messages, and Debug Messages will be logged.
Note:
The higher the level of logging configured, the larger and faster the Log file can grow in the Tunnel Service. Logging should be configured as low as appropriate under normal
circumstances. If problems are encountered, then logging may be increased until the problem is found, but should be lowered again when no longer needed. There will be a maximum of 3 log files created with 10MB size. After this first file will be deleted
Chapter 5 – Installation and Configuration -- 35
Default Value: INFO
Configuration Wizard
Once an instance of the Motorola Tunnel Service has been installed on a Windows PC, that single instance can be re-configured using the Motorola Tunnel Service Configuration Wizard. This is not recommended way for changing the configuration
Note:
If multiple instances of the Motorola Tunnel Service need to be identically configured, then a using a TunnelService.Configuration Settings Object, as described in the prior section, would likely be a more efficient approach.
The Motorola Tunnel Service Configuration Wizard can be launched using the Tunnel Service Configuration shortcut that can be found in the Start Menu of the Windows PC at Programs > Motorola MSP > Tunnel Service Configuration.
Important:
Running the Motorola Tunnel Service Configuration Wizard requires access to the Windows Console of the Windows PC on which the Motorola Tunnel Service has been installed. This would generally require physical access to that Windows PC or the ability to remotely login to the Windows Console of that Windows PC (e.g. using the Microsoft Remote Desktop Protocol or some similar mechanism).
Figure 4 below shows the Motorola Tunnel Service Configuration Wizard Dialog that will be displayed when the Motorola Tunnel Service Configuration Wizard is launched using the shortcut.
Figure 4 – Tunnel Service Configuration Wizard Dialog Note:
If the Tunnel Service is installed on Windows Vista and above user must login as Administrator to make any changes to the configuration using Wizard.
Changes made to the configuration of an instance of the Motorola Tunnel Service while it is running may not take effect until the instance is restarted or the Windows PC is rebooted.
Tunnel Service Workstation Port
This option specifies the Port that should be used by Workstation PCs to contact the instance of the Motorola Tunnel Service.
Note:
If the default port is changed for an instance of the Motorola Tunnel Service, then a
corresponding change will need to be made to the configuration of the Motorola Tunnel Agent for all devices that will be used with that instance of the Motorola Tunnel Service.
Tunnel Service Device Port
This option specifies the Port that should be used by the Motorola Tunnel Agent running on devices to contact the instance of the Motorola Tunnel Service when Outbound Mode is used. Note:
If the default port is changed for an instance of the Motorola Tunnel Service, then a
corresponding change will need to be made to the configuration of the Motorola Tunnel Agent for all devices that will be used in Outbound Mode with that instance of the Motorola Tunnel Service.
Log Level
The Tunnel Service Log Level can be adjusted, if needed. This might be changed if there is a need to debug the operation of the Tunnel Service.
Chapter 6 – Using the Motorola Tunnel
Service
Overview
This chapter discusses how to use the Tunnel Service
Usage Transparency
The Tunnel Service is designed to enhance the contactability of devices from Workstation PCs, when used in conjunction with Tunnel Agent Patrons, such as the Motorola Remote Control Solution or the Motorola Real-Time Management Solution, while providing a high degree of Usage Transparency. By this is meant that once the Tunnel Services are appropriately installed and configured and once devices are appropriately configured, the usage of the Tunnel Agent Patrons is the same as if no Tunnel Service were used.
In fact, to meet the potentially varying needs of a complex Enterprise network, some devices might need to be contacted directly (without an intermediary Tunnel Service), some devices might need to be contacted via a Tunnel Service using Inbound Mode, and some devices might need to be contacted via a Tunnel Service using Outbound Mode. Once such a system is properly deployed, an MSP Console UI User can use the Tunnel Agent Patrons without needing to worry how devices will be contacted.
NAT Traversal
For Indirect Contact Modes to be used, Workstation PCs must be able to directly contact
instances of the Motorola Tunnel Service. If an instance of the Motorola Tunnel Service is inside the inner network of a NAT and Workstation PCs are in the outer network, then it may be the case that the instance of the Motorola Tunnel Service will not be directly contactable from some or all Workstation PCs. When such a situation exists, NAT Traversal may be used or the instance of the Motorola Tunnel Service will need to be relocated.
It may seem somewhat strange to set up a network in this way, since one key reason for using an instance of the Motorola Tunnel Service is to avoid the need for NAT Traversal. But in fact, this can be a very reasonable approach.
Configuring NAT Traversal for a large number of devices can be quite complicated since it must take into account the mappings required to reach each and every device. If an instance of the Motorola Tunnel Service is placed with the devices in the inner network, then NAT Traversal need only be configured to reach the instance of the Motorola Tunnel Service and the instance of the Motorola Tunnel Service will handle reaching the devices. In addition, traffic to the instance of the Motorola Tunnel Service may be the only traffic for which NAT Traversal must be configured. This can make the configuration of the NAT Router much simpler since there is only one IP Address and one port to be dealt with.
NAT Traversal Operation
The most automatic way for a node in an inner network to learn the IP Address of a node in an inner network is to have the node in the inner network send it to the node in the outer network. . But this does not help much for NAT Traversal since a node in the inner network generally does not know its public IP Address, and hence cannot tell a node in the outer network about it. While traffic from the node in the inner network may be identified as coming from its public IP Address, the public IP Address generally cannot be included as data sent by the node.
The key task in NAT Traversal is determining the proper IP Address and possibly Port Number (if NAPT is used) required to contact nodes in the inner network from nodes in the outer network. This requires understanding and leveraging knowledge about configuration of the NAT Router. There are two primary NAT IP Address Mapping modes: One-to-One NAT IP Address Mapping and One-to-Many NAT IP Address Mapping. These modes have different requirements for successfully accomplishing NAT Traversal.
One-to-One NAT IP Address Mapping
When One-to-One NAT IP Address Mapping is used, the NAT Traversal must somehow determine the proper public IP Address to use to contact the desired node in the inner network from a node in the outer network. This process can be relatively simple since there is a unique public IP Address for each node.
NAT Traversal must be accomplished by maintaining a table mapping private IP Addresses to public IP Addresses. Since a node in an inner network can know its private IP Address, it can report that. A node in the outer network can then use that private IP Address to look up the proper public IP Address required to reach that node.
As mentioned earlier, implementing NAT Traversal for instances of the Motorola Tunnel Service can often be significantly less work than implementing NAT Traversal for devices. This is because there are generally far fewer instances of the Motorola Tunnel Service than there are devices, since a single instance of the Motorola Tunnel Service generally services many devices.