1-- ***************************************************************** 2-- CISCO-ASPP-MIB.my: Asynchronous Security Poll Protocols. 3-- 4-- May 1996, Andrew R. Rothwell. 5-- October 2002, Michael Belscher 6-- 7-- Copyright (c) 1996-1997, 2003 by cisco Systems, Inc. 8-- All rights reserved. 9-- 10-- ***************************************************************** 11CISCO-ASPP-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY, OBJECT-TYPE, Integer32 15 FROM SNMPv2-SMI 16 MODULE-COMPLIANCE, OBJECT-GROUP 17 FROM SNMPv2-CONF 18 ifIndex 19 FROM IF-MIB 20 TruthValue 21 FROM SNMPv2-TC 22 ciscoMgmt 23 FROM CISCO-SMI; 24 25 26ciscoAsppMIB MODULE-IDENTITY 27 LAST-UPDATED "200302100000Z" 28 ORGANIZATION "Cisco Systems, Inc." 29 CONTACT-INFO 30 "Cisco Systems 31 Customer Service 32 33 Postal: 170 W. Tasman Drive 34 San Jose, CA 95134 35 USA 36 37 Tel: +1 800 553-NETS 38 E-mail: cs-poll-async@cisco.com" 39 DESCRIPTION 40 41 "The ASPP MIB provides the configuration and operational 42 information on asynchronous polled protocols such as the 43 asynchronous security protocols that alarm monitoring 44 companies use. The protocols are handled in passthrough 45 mode. ASPP will handle the receiving and sending of the 46 asychronous blocks. It will not perform any error 47 checking. It is the responsibilty of the end-station to 48 perform any required error recovery. A generic protocol 49 has been created to support asychronous protocols. In 50 some situations this doesn't work for all types since 51 there is no alarm protocol standard. Specific vendor 52 support has been included for the following vendor's 53 alarm equipment and protocols: 54 * adplex 55 * adt 56 - PollSelect 57 - VariPoll 58 * diebold 59 * mdi 60 * mosec (mosler) 61 * gddb (Guang Dong Development Bank) 62 - This protocol is similar to Burroughs Poll/Select 63 64 The following example configuration shows how the 65 ASPP MIB returns ASPP information, from either CISCO A 66 or CISCO B. 67 68 Security == ASP == Cisco == IP == Cisco == ASP == Alarm 69 control A Network B Panel 70 station 71 72 The following entities are managed: 73 74 1) ASPP ports (serial interfaces) 75 76 The ASPP ports are identified by the interface index, 77 and additional information about this interface can be 78 obtained from the Cisco Serial Interface MIB." 79 80 REVISION "200302100000Z" 81 DESCRIPTION 82 "Added Asynchronous Point of Sale(POS) to IP conversion 83 support. 84 85 The APOS protocol utilizes asynchrounous communications 86 with 1 start, 1 stop and 7 data bits with even 87 parity. The connection to the POS terminal will always 88 be an asynchronous leased line. The protocol has many 89 characteristics of BSC except it is simplified to 90 minimize overhead on the point to point connection. 91 92 The added APOS traffic will be locally acknowledged 93 unlike the other polled asynchronous protocol which 94 function in passthrough mode. 95 96 The LRC/VRC will be verified and any necessary recovery 97 will be done by the router. 98 99 This is necessary since we are converting the protocol 100 so the data can be passed to an IP attached host." 101 102 REVISION "9508210000Z" 103 DESCRIPTION 104 "Initial mib for async security polled protocols." 105 106 ::= { ciscoMgmt 55 } 107 108asppObjects OBJECT IDENTIFIER ::= { ciscoAsppMIB 1} 109asppPorts OBJECT IDENTIFIER ::= { asppObjects 1} 110 111-- ********************************************************************* 112-- * Aspp Port Table 113-- ********************************************************************* 114 115asppPortTable OBJECT-TYPE 116 SYNTAX SEQUENCE OF AsppPortEntry 117 MAX-ACCESS not-accessible 118 STATUS current 119 DESCRIPTION 120 "A list of asynchronous interfaces which have been 121 configured to support an asynchronous security protocol 122 (ASP) BSTUN group." 123 ::= { asppPorts 1 } 124 125asppPortEntry OBJECT-TYPE 126 SYNTAX AsppPortEntry 127 MAX-ACCESS not-accessible 128 STATUS current 129 DESCRIPTION 130 "Current ASP configuration settings for an asynchronous 131 port." 132 INDEX { ifIndex } 133 ::= { asppPortTable 1 } 134 135AsppPortEntry ::= 136 SEQUENCE { 137 asppPortProtocol INTEGER, 138 asppPortRole INTEGER, 139 asppPortReceiveInterFrameTimeout Integer32, 140 asppPortDeviceAddressOffset Integer32, 141 asppPortEOFCharacter Integer32, 142 asppPortSOFCharacter Integer32, 143 asppPortIgnoreSequenceNumber TruthValue, 144 asppPortRspTimer Integer32, 145 asppPortRxTimer Integer32, 146 asppPortHostTimer Integer32, 147 asppPortConnectTimer Integer32, 148 asppPortRetryCount Integer32, 149 asppPortDelayEnq Integer32, 150 asppPortDisableEnq TruthValue, 151 asppPortSendAck TruthValue, 152 asppPortDirect TruthValue, 153 asppPortDCDAlways TruthValue 154 } 155 156asppPortProtocol OBJECT-TYPE 157 SYNTAX INTEGER { 158 adplex(1), 159 adtPollSelect(2), 160 adtVariPoll(3), 161 diebold(4), 162 asyncGeneric(5), 163 mdi(6), 164 mosec(7), 165 gddb(8), 166 apos(9) 167 } 168 MAX-ACCESS read-only 169 STATUS current 170 DESCRIPTION 171 "Specifies type of asynchronous security protocol being 172 used. These protocols are implemented by individual 173 security alarm manufacturers. There is no standard 174 protocol for alarm communications over RS-232 175 interfaces. 176 177 asyncGeneric(5)- provides generic polled asynchronous 178 support 179 180 Specific vendor support has been included for the 181 following vendor's alarm equipment and protocols: 182 * adplex(1) 183 * ADT 184 - adtPollSelect(2) 185 - adtVariPoll(3) 186 * diebold(4) 187 * mdi(6) 188 * mosec(7) 189 - mosler equipment 190 * gddb(8) 191 - Guang Dong Development Bank 192 The protocol is similar to Burroughs 193 Poll/Select. 194 195 apos(9) - Protocol support for asynchronous POS 196 devices for provide credit and debit card 197 authorizations to an IP attached host." 198 ::= { asppPortEntry 1 } 199 200asppPortRole OBJECT-TYPE 201 SYNTAX INTEGER { primary(1), secondary(2) } 202 MAX-ACCESS read-only 203 STATUS current 204 DESCRIPTION 205 "Specifies the router's protocol role. 206 primary(1) - Indicates we are attaching to the terminal 207 or alarm panel. 208 secondary(2) - Indicates we are attaching to the host 209 or alarm console.." 210 ::= { asppPortEntry 2 } 211 212asppPortReceiveInterFrameTimeout OBJECT-TYPE 213 SYNTAX Integer32 (0..1000) 214 UNITS "milliseconds" 215 MAX-ACCESS read-only 216 STATUS current 217 DESCRIPTION 218 "Specifies the receive inter-frame-timeout period, used 219 to delimit frames. Since all the protocols are 220 implemented over RS-232 3-wire circuits (ie TX, RX and 221 GND), the only general method for start-end frame 222 detection is to monitor the time between received 223 characters. If this time period exceeds the inter-frame 224 timeout value, then frame end-start is detected." 225 ::= { asppPortEntry 3 } 226 227asppPortDeviceAddressOffset OBJECT-TYPE 228 SYNTAX Integer32 (0..255) 229 UNITS "bytes" 230 MAX-ACCESS read-only 231 STATUS current 232 DESCRIPTION 233 "Specifies the byte offset within a frame, which 234 contains the device address. This is used when the 235 asynchronous interface is configured to use the async 236 generic protocol handler. Because no knowledge of the 237 protocol is built-in to the IOS, it must be told where 238 the address field lives within the frame. That way IOS 239 can correctly route the frames for this protocol." 240 REFERENCE 241 "CISCO-BSTUN-MIB" 242 ::= { asppPortEntry 4 } 243 244asppPortEOFCharacter OBJECT-TYPE 245 SYNTAX Integer32 (0..256) 246 MAX-ACCESS read-only 247 STATUS current 248 DESCRIPTION 249 "Specifies the protocol character to use to delimit 250 the end of a frame. The valid character is 0-255 and 251 256 indicates the object is not configured." 252 ::= { asppPortEntry 5 } 253 254asppPortSOFCharacter OBJECT-TYPE 255 SYNTAX Integer32 (0..256) 256 MAX-ACCESS read-only 257 STATUS current 258 DESCRIPTION 259 "Specifies the protocol character to use to delimit 260 the beginning of a frame. The valid character is 0-255 261 and 256 indicates the object is not configured." 262 ::= { asppPortEntry 6 } 263 264asppPortIgnoreSequenceNumber OBJECT-TYPE 265 SYNTAX TruthValue 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "Specifies whether the asp sequence numbers used to 270 synchronize aspp traffic between head-end and tail-end 271 routers should be ignored. This is enabled if there 272 isn't a one to one correlation between commands and 273 responses between the two routers." 274 DEFVAL { false } 275 ::= { asppPortEntry 7 } 276 277asppPortRspTimer OBJECT-TYPE 278 SYNTAX Integer32 (1..30) 279 UNITS "seconds" 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "Specifies the amount of time the router will wait for a 284 response to a packet before retransmission." 285 ::= { asppPortEntry 8 } 286 287asppPortRxTimer OBJECT-TYPE 288 SYNTAX Integer32 (10..60) 289 UNITS "seconds" 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "Specifies the maximum amount of time the router will 294 wait for a complete packet to be received. It starts 295 when an STX character is received." 296 ::= { asppPortEntry 9 } 297 298asppPortHostTimer OBJECT-TYPE 299 SYNTAX Integer32 (10..120) 300 UNITS "seconds" 301 MAX-ACCESS read-only 302 STATUS current 303 DESCRIPTION 304 "Specifies the maximum amount of time the router will 305 wait for a response to a terminal request from the 306 host. It starts when a terminal request is forwarded 307 to the host." 308 ::= { asppPortEntry 10 } 309 310asppPortConnectTimer OBJECT-TYPE 311 SYNTAX Integer32 (1..30) 312 UNITS "seconds" 313 MAX-ACCESS read-only 314 STATUS current 315 DESCRIPTION 316 "Specifies the maximum amount of time the router will 317 wait for the activation of the tunnel connection to the 318 host to complete. It starts when a terminal requests a 319 session with host." 320 ::= { asppPortEntry 11 } 321 322asppPortRetryCount OBJECT-TYPE 323 SYNTAX Integer32 (1..10) 324 MAX-ACCESS read-only 325 STATUS current 326 DESCRIPTION 327 "Specifies the maximum number of timers a packet will be 328 retransmitted before the connection with the terminal 329 will be disconnected." 330 ::= { asppPortEntry 12 } 331 332asppPortDelayEnq OBJECT-TYPE 333 SYNTAX Integer32 (1..1000) 334 UNITS "milliseconds" 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "Specifies the amount of time to wait after sending a 339 connect packet to the the terminal before sending the 340 ENQ to initiate a session" 341 ::= { asppPortEntry 13 } 342 343asppPortDisableEnq OBJECT-TYPE 344 SYNTAX TruthValue 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "Specifies whether sending of ENQ to initiate a session 349 with the terminal is disabled." 350 DEFVAL { false } 351 ::= { asppPortEntry 14 } 352 353asppPortSendAck OBJECT-TYPE 354 SYNTAX TruthValue 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "Specifies whether the router will send an ACK to 359 acknowledge packets." 360 DEFVAL { false } 361 ::= { asppPortEntry 15 } 362 363asppPortDirect OBJECT-TYPE 364 SYNTAX TruthValue 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "Specifies whether the line mode is direct or dialed. 369 If in direct the router will immediately send ENQ 370 without waiting for AT commands" 371 DEFVAL { false } 372 ::= { asppPortEntry 16 } 373 374asppPortDCDAlways OBJECT-TYPE 375 SYNTAX TruthValue 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "Specifies whether DCD should always be asserted or 380 asserted only when the connection is active." 381 DEFVAL { false } 382 ::= { asppPortEntry 17 } 383-- ************************************************************************* 384-- * Conformance Information 385-- ************************************************************************* 386 387asppMibConformance OBJECT IDENTIFIER ::= { ciscoAsppMIB 3 } 388asppMibCompliances OBJECT IDENTIFIER ::= { asppMibConformance 1 } 389asppMibGroups OBJECT IDENTIFIER ::= { asppMibConformance 2 } 390-- 391-- ************************************************************************* 392-- * Compliance Statements 393-- ************************************************************************* 394asppMibCompliance MODULE-COMPLIANCE 395 STATUS deprecated 396 DESCRIPTION 397 "The compliance statement for ASP." 398 MODULE -- this module 399 MANDATORY-GROUPS { 400 asppPortsGroup 401 } 402 ::= { asppMibCompliances 1 } 403 404asppMibComplianceRev1 MODULE-COMPLIANCE 405 STATUS current 406 DESCRIPTION 407 "The compliance statement for ASP." 408 MODULE -- this module 409 MANDATORY-GROUPS { 410 asppPortsGroup 411 } 412 GROUP asppPortsGenericGroup 413 DESCRIPTION 414 "This group is mandatory when implementing 415 asyncGeneric protocol." 416 GROUP asppPortsAposGroup 417 DESCRIPTION 418 "This group is mandatory when implementing 419 the apos protocol." 420 421 ::= { asppMibCompliances 2 } 422 423asppPortsGroup OBJECT-GROUP 424 OBJECTS { 425 asppPortProtocol, 426 asppPortRole, 427 asppPortReceiveInterFrameTimeout, 428 asppPortDeviceAddressOffset 429 } 430 STATUS current 431 DESCRIPTION 432 "A collection of objects providing information about 433 interfaces that run asynchronous security protocols." 434 ::= { asppMibGroups 1} 435 436asppPortsGenericGroup OBJECT-GROUP 437 OBJECTS { 438 asppPortEOFCharacter, 439 asppPortSOFCharacter, 440 asppPortIgnoreSequenceNumber 441 } 442 STATUS current 443 DESCRIPTION 444 "A collection of objects providing information about 445 interfaces that run asynchronous generic protocols." 446 ::= { asppMibGroups 2} 447 448asppPortsAposGroup OBJECT-GROUP 449 OBJECTS { 450 asppPortRspTimer, 451 asppPortRxTimer, 452 asppPortHostTimer, 453 asppPortConnectTimer, 454 asppPortRetryCount, 455 asppPortDelayEnq, 456 asppPortDisableEnq, 457 asppPortSendAck, 458 asppPortDirect, 459 asppPortDCDAlways 460 } 461 STATUS current 462 DESCRIPTION 463 "A collection of objects providing information about 464 interfaces that run asynchronous protocol to communicate 465 to Point of Sale protocols." 466 ::= { asppMibGroups 3} 467END 468