Rugged Operating System (ROS Ã‚Â® ) Software User ... - RuggedCom

More documents

Recommendations

Info

Chapter 1 Introduction RUGGEDCOM ROS User Guide The port state, whether it is always open and cannot be closed, or open only, but can be configured NOTE In certain cases, the service might be disabled, but the port can stil be open (e.g. TFTP) • Port Default The default state of the port (i.e. open or closed) • Access Authorized Denotes whether the ports/services are authenticated during access Services Port Number Port Open Port Default Access Authorized Telnet TCP/23 Open (configurable) Closed Yes HTTP TCP/80 Open, redirects to 443 Open — HTTPS TCP/443 Open Open Yes RSH TCP/512 Open (configurable) Closed Yes TFTP UDP/69 Open Open (service disabled) No SFTP TCP/22 Open Open Yes SNMP UDP/161 Open Open Yes SNTP UDP/123 Open - Always might acts as server Open No SSH TCP/22 Open Open Yes ICMP — Open Open No TACACS+ RADIUS Remote Syslog TCP/49 (configurable) UDP/1812 to send (configurable), opens random port to listen to UDP/514 (configurable) Open (configurable) Closed Yes Open (configurable) Closed Yes Open (configurable) Closed No TCP Modbus (Server) (including Management access) TCP/502 Open Open No TCP Modbus (Switch) (Management access) TCP/502 Open (configurable) Closed No DHCP, DHCP Agent DHCP Server (WLAN) UDP/67 sending msg if enabled - if received, always come to CPU, dropped if service not configured UDP/67 for listening UDP/68 for responding Open Open No Open Open No RCDP — Open (configurable) Closed Yes 12 Available Services by Port
RUGGEDCOM ROS User Guide Chapter 1 Introduction Section 1.5 ModBus Management Support and Memory Map ModBus management support in RUGGEDCOM devices provides a simple interface for retrieving basic status information. ModBus support simplifies the job of SCADA (Supervisory Control And Data Acquisition) system integrators by providing familiar protocol for the retrieval of RUGGEDCOM device information. ModBus provides mostly read-only status information, but there are also a few writable registers for operator commands. The ModBus protocol PDU (Protocol Data Unit) format is as follows: Function Code Data RUGGEDCOM devices support the following ModBus function codes for device management through ModBus: 1. Read Input Registers or Read Holding Registers – 0x04 or 0x03, for which the Modbus PDU looks like: Request Function code 1 Byte 0x04(0x03) Starting Address 2 Bytes 0x0000 to 0xFFFF Number of Input Registers 2 Bytes 0x0001 to 0x007D Response Function code 1 Byte 0x04(0x03) Byte Count 1 Byte 2 x N* Input Registers N*X2 Bytes *N = the number of Input Registers 2. Write Multiple Registers – 0x10: Request Function code 1 Byte 0x10 Starting Address 2 Bytes 0x0000 to 0xFFFF Number of Registers 2 Bytes 0x0001 to 0x0079 Byte Count 1 Byte 2 x N* Registers Value N* x 2 Bytes Value of the register *N = the number of Input Registers Response Function code 1 Byte 0x10 Starting Address 2 Bytes 0x0000 to 0xFFFF Number of Registers 2 Bytes 1 to 121 (0x79) Note that as RUGGEDCOM devices have a variable number of ports, not all registers and bits apply to all products. Registers that are not applicable to a particular product return a zero value. For example, registers referring to serial ports are not applicable to RUGGEDCOM products. ModBus Management Support and Memory Map 13
Page 1 and 2: Preface Introduction 1 RUGGEDCOM RO
Page 3 and 4: RUGGEDCOM ROS User Guide Table of C
Page 11 and 12: RUGGEDCOM ROS User Guide Preface Pr
Page 13 and 14: RUGGEDCOM ROS User Guide Preface Ac
Page 15 and 16: RUGGEDCOM ROS User Guide Chapter 1
Page 25: RUGGEDCOM ROS User Guide Chapter 1
Page 77 and 78:
RUGGEDCOM ROS User Guide Chapter 2
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
show all

Rugged Operating System &#40;ROS Ã‚Â® &#41; Software User ... - RuggedCom

Create successful ePaper yourself

Delete template?

Save as template?

Rugged Operating System (ROS Ã‚Â® ) Software User ... - RuggedCom