Remote Access Connections into T/Mon Platform: T/Mon NOC Remote Access connections refer to being about to see what T/Mon is doing while in Monitor Mode. With certain software, you can control and edit the database while T/Mon is out of Monitor Mode (database editing mode.) Keep in mind that monitoring and database access limitations can be defined in T/Mon System Users. This Techno Knowledge Paper assumes that the user has full administrative access to T/Mon. This techno knowledge paper can help you if: You want to setup remote access connections over LAN. Quick Reference Chart (for more details, review the Troubleshooting Checklist, starting on page 2 of this guide) Start Here Establish Remote Access Server for T/Windows Setup Remote Access Connection for this server Create Remote Access Pool Setup HTTP Server Setup Remote Access Connections to HTTP Server
Troubleshooting Checklist BEFORE GETTING STARTED About T/Access: The T/Access software program offers the same control as having a keyboard and monitor directly connected to T/Mon. For this reason, T/Access should be used by network administrators for monitoring and making all database edits in the T/Mon. T/Access remote connection via LAN is pre-defined in T/Mon using TCP port 9990. You can also connect using T/Access software through the back COM port serially, or through the modem port on the back, labeled T/Link Modem. About T/Windows and Web Browser: T/Windows and the HTTP web-browser are programs that can only be used while the T/Mon is in Monitor mode. and is used to Monitor alarms and various statistics about your Network. For a complete list of what monitor mode includes, see section 16-1 in the T/MonXM user manual titled Monitor Mode Tutorial. About T/Mon: Typically, most remote access connections are used over LAN. However, T/Mon has the ability of setting up physical ports 1-24 as a T/Windows connection (either serially or via dialup). If T/Mon is populated with 232 ports on the back panel, then you can connect T/Windows serially or via an external modem to dial in. Also, if the T/Mon populated with a 212-dialup modem cartridge, you can use T/Windows to connect via the dialup modem. Most Port/Job assignments in T/Mon are user-definable - however, some are permanent to perform specific functions. The table below shows the DPS recommended port assignments. The permanent port assignments are marked with an asterisk (*). Note: The word port here does not refer to the IP port. Throughout this document, the terms port and job will be used interchangeably. Recommended Job/Port Assignments in T/Mon: Job IP Port Application Connection Type 1-24 - Physical ports 28* - Ethernet 30-46 User-definable Remote Access Jobs Remote Access Pool TCP HTTP Pool 47 User-definable Remote Access Server Job TCP 80 80 HTTP Server TCP 110 110 Incoming POP3 Telnet Raw 161 161 SNMP Agent (Responder) UDP 162 162 Trap Processor UDP (typical) TCP (rare) 420 20 FTP Transfer Telnet Raw 421 21 FTP Server TCP 425 25 Mail-Out SMTP Telnet Raw 443 443 HTTPS (SSL) TCP 444 444 SNPP (Paging) Telnet Raw 500* - Hard Drive Mirroring -
BEFORE GETTING STARTED (CONT.) You are limited to 17 LAN T/Windows sessions OR 17 HTTP sessions OR some combination of the two adding up to 17 total connections. You ll notice that jobs 30-47 are user-definable, because they are LAN-based ports. However, they are the only LAN-based jobs that can be used for Remote Access. This means you could set up job 30 as a port to poll your NetGuardians remotes, but that would be one less port you have for remote access. Jobs 48-499 are available to set up for polling your NetGuardians or other LAN-based RTUs, so it s recommended that you save ports 30-47 for remote access. This Techno Knowledge Paper will walk you through the steps for setting up a Remote Access Server for T/Windows, the web-browser, 9 T/Windows connections, and 8 HTTP connections. Establish a Remote Access Server 1. From the Master Menu, select Parameters > Remote Ports. This is where all jobs/ports will be setup within the T/Mon. Let s create a remote access server for T/Windows. 2. Hit F for Find and enter job number 47. Press Enter.
3. Hit E for Edit, then Tab over to the Port Type select box on the right. Scroll down to hit Enter to select the Remote Access Server. Once you enter a description, you will notice the words No Data Connection blinking at the top. 4. Hit F6 (circled in red above) for the Data Connection Assignment screen. Hit F1 for TCP Ports. 5. Scroll down to the next available entry (in this case entry 1), and hit Tab. Scroll down to select TCP Protocol. (Make sure caps lock is off.) 6. Enter the port number allowed by your IT department. I will use port 3000 in this example. Enter a description, and when your cursor is at the beginning of the next line, hit F8 to save.
7. When back at the Data Connection Assignment screen, hit Tab and scroll down to select your Remote Access Server connection. Hit Enter. 8. You should now see job 47 set up as a Remote Access Server.
Setup Remote Access Connections for this Server 1. Now we need to setup the actual Remote Access Connections that will use this server. Hit F for Find, enter job number 30, and select it by hitting Enter. 2. It will be nearly the same process as before to setup this job, only this time we will select Remote Access instead of Remote Access Server. 3. Hit E for Edit and select Remote Access. The terminal type will be T/Windows for this example, but you could also select HTTP for adding another access option via the web-browser. (I will show this step later.) I will not be doing printer Logging (outputting to a printer ever time a user logs onto the T/Mon with T/Windows) or auto logon with my initials. 4. Hit F6 for Data connection. Instead of creating another data connection, this time I will select Remote Access Pool.
How a Remote Access Pool Works: When you log into T/Mon using T/Windows, it will connect with the port you assigned in the Remote Access Server. (Port 3000 was used in this example.) The next person logging in with T/Windows will use Remote Access Pool 3000+1=3001 etc. This makes it very easy for each user to install T/Windows on their computer. They will setup the software under the Options / Connection Settings and enter the port number (3000). When T/Windows connects, it will try to use port 3000, but it will see that it s already in use. In this case, it will try 3001 instead. If you do not want to use the Pool option, do not select Remote Access Pool in the Data Connection assignment screen. Instead, you would continue to use the Ethernet TCP port definition screen. Here, you would scroll down to the next available entry and hit Tab, select TCP again, then enter the next port you want to use for T/Windows. Keep in mind that each person connecting with T/Windows needs to remember which port they should connect to, but this method does makes it easier to control port usage.
5. Remember that in this example, I ll be setting up 10 sessions of T/Windows Remote Access Connections. To do this, repeat steps 3 and 4 for jobs 30-39. I will be reserving Jobs 40-46 for my 7 HTTP connections. Setting up the HTTP Server is a little different.
Setup the HTTP Server 1. This job will be set up on port 80. Hit F for Find (from the Remote Parameters screen) and select 80. 2. Tab over to select HTTP Server and enter the number of connections to be used (3-30). Hit N to choose not to use SSL. 3. This job for port 80 will be use a Non-Secure HTTP connection. [NOTE: These same steps should be followed on job 443 if you wish to create a secure (HTTPS) web browser connection. In this case, the data connection is assigned for you because it will always use port 80. (The same is true with HTTPS on port 443). If you wish to edit this, hit F6, then F1 and enter the port you wish your browser to appear.] 4. To continue setting up the HTTP Remote Access Connections, go to the next available remote access connection. In this example, we left off on job 40. Hit F for find and go to job 40.
5. Hit E for Edit and scroll down to Remote Access. The terminal type this time will be HTTP. The data connection will once again be established for you. If you experience problems setting up Remote Access Connections on T/Mon, please contact DPS Telecom Tech Support at (559) 454-1600, or send an email to support@dpstele.com.