Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies Remote Port Security Device Users Guide
Lucent Technologies Remote Port Security Device Users Guide
Have a look at the manual Lucent Technologies Remote Port Security Device Users Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-11 Command Functions 3 AH—Access History Syntax and Parameters ah [-] [ALL] Description Use the Access History command to display details on the last 500 incoming or outgoing calls attempts using the RMATS channel. The details include the date, time, user ID, device number, and duration of the call. To protect the integrity of the Access History, a Message Authentication Code is generated and shown with each Access History entry. The Message Authentication Code is followed by a period (“.”) and the sequence number of the message, for example, “CC85.000,” where “CC85” is the Message Authentication Code and “000” is the message sequence number. If the [-] and [ALL] parameters are not used, the messages are displayed in ascending order by message sequence number, 20 to a page. “- More to Come -” appears at the bottom of the each page except the last page, and “- End of List -” appears at the bottom of the last page. Press to move from page to page. When you reach the last page (indicated by “- End of List -”), press to return to the menu of commands. When you want to capture a long Access History to a file on a computer, include the [ALL] parameter. Page breaks are removed and the entire Access History is listed. To pause the report shown on the screen, press . To resume the report on the screen, press again.Parameter Description ahAccess History command [-]Include this parameter to list the Access History in descending order by message sequence number. If this parameter is not used, the Access History is listed in ascending order. [ALL]Use this parameter to remove the page breaks and list the entire Access History buffer. Press to pause and resume the report on the screen. If this parameter is not used, the report is listed 20 messages to a page. ENTER ENTER ENTER ENTER ENTER ENTER
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-12 Command Functions 3 To capture an Access History, use a communications software package (such as ProComm). After you save the Access History as a file, you can open it in a word processing application and print it. To show the Access History in descending order by message sequence number, include the [-] parameter. Sample Command and Response > ah --- Access History --- Seq Date Time User ID Device # Duration E2C1.000 08/16/96 13:08:51 ATT-INADS1 12345 0: 0:20 B1A3.001 08/16/96 13:09:42 ATT-INADS1 12345 1:20:33 CC34.002 08/16/96 15:12:06 0: 5:08 D4E2.003 08/16/96 15:20:51 0: 2:14 12BB.004 08/16/96 15:24:19 ATT-INADS2 72333 0: 8:46 7EF4.005 08/16/96 15:48:01 ATT-INADS2 72333 0: 1:59 BE31.006 08/16/96 15:58:23 KEY11 82545 0: 7:22 A3F3.007 08/16/96 16:08:51 KEY11 82545 0: 3:20 4C23.008 08/17/96 08:08:18 0: 9:49 DD52.009 08/17/96 08:28:13 ATT-INADS1 12345 0:28:11 21CC.010 08/17/96 08:58:37 ATT-INADS1 12345 0: 1:02 66D3.011 08/17/96 14:03:32 0: 6:15 B1A3.012 08/17/96 14:09:53 ATT-INADS1 12345 0: 3:38 D311.013 08/17/96 14:18:10 KEY16 96549 0:24:22 C453.014 08/17/96 14:44:44 KEY16 96549 0: 0:58 F67A.015 08/18/96 09:18:51 KEY12 37827 0:10:04 55E5.016 08/18/96 09:21:48 KEY12 37827 0: 0:47 E7A1.017 08/18/96 11:31:25 0:13:03 BA14.018 08/18/96 11:48:11 0:29:34 BC03.019 08/18/96 13:28:31 ATT-INADS1 12345 2:56:05 -- End of List --
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-13 Command Functions 3 The fields of the Access History screen are: SeqThe Message Authentication Code and message sequence number generated for each Access History entry. The code is generated to protect the integrity of the Access History. The Message Authentication Code is followed by a period (“.”) and the sequence number of each status message. The messages are numbered in sequence from 000 to 999 and then restart at 000. DateThe date that the access took place TimeThe time that the access call came in User IDThe user ID of the Key used to access the RMATS channel. If the call was an outgoing call on the channel, no user ID is displayed but the call is identified as . Device #The device number of the Key used to access the RMATS channel. The device number is a number assigned to the Key by the Key user at initialization. No device number appears for an outgoing call. DurationThe length of time that the call was connected in hours, minutes, and seconds
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-14 Command Functions 3 AA—Administrative Access History Syntax and Parameters aa [-] [ALL] Description Use the Administrative Access History command to display details on the last 100 administrative access attempts. The details include the date, time, user ID, and duration of the call. To protect the integrity of the Administrative Access History, a Message Authentication Code is generated and shown with each Administrative Access History entry. The Message Authentication Code is followed by a period (“.”) and the sequence number of the message, for example, “CC85.000,” where “CC85” is the Message Authentication Code and “000” is the message sequence number. If the [-] and [ALL] parameters are not used, the messages are displayed in ascending order by message sequence number, 20 to a page. “- More to Come -” appears at the bottom of the each page except the last page, and “- End of List -” appears at the bottom of the last page. Press to move from page to page. When you reach the last page (indicated by “- End of List -”), press to return to the menu of commands. When you want to capture a long Administrative Access History to a file on a computer, include the [ALL] parameter. Page breaks are removed and the entire Administrative Access History is listed. To pause the report shown on the screen, press . To resume the report on the screen, press again.Parameter Description aaAdministrative Access History command [-]Include this parameter to list the Administrative Access History in descending order by message sequence number. If this parameter is not used, the Administrative Access History is listed in ascending order. [ALL]Use this parameter to remove the page breaks and list the entire Administrative Access History buffer. Press to pause and resume the report on the screen. If this parameter is not used, the report is listed 20 messages to a page. ENTER ENTER ENTER ENTER ENTERENTER
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-15 Command Functions 3 To capture an Administrative Access History, use a communications software package (such as ProComm). After you save the Administrative Access History as a file, you can open it in a word processing application and print it. To show the Administrative Access History in descending order by message sequence number, include the [-] parameter. Sample Command and Response > ah --- Admin. Access History --- Seq Date Time User ID Duration E2C1.000 08/16/96 13:08:51 KEY20 0: 0:20 B1A3.001 08/16/96 13:09:42 KEY11 1:20:33 CC34.002 08/16/96 15:12:06 KEY20 0: 5:08 D4E2.003 08/16/96 15:20:51 KEY20 0: 2:14 12BB.004 08/16/96 15:24:19 ATT-INADS2 0: 8:46 7EF4.005 08/16/96 15:48:01 ATT-INADS2 0: 1:59 BE31.006 08/16/96 15:58:23 KEY11 0: 7:22 A3F3.007 08/16/96 16:08:51 KEY11 0: 3:20 4C23.008 08/17/96 08:08:18 KEY20 0: 9:49 DD52.009 08/17/96 08:28:13 ATT-INADS1 0:28:11 21CC.010 08/17/96 08:58:37 ATT-INADS1 0: 1:02 66D3.011 08/17/96 14:03:32 KEY11 0: 6:15 B1A3.012 08/17/96 14:09:53 ATT-INADS1 0: 3:38 D311.013 08/17/96 14:18:10 KEY11 0:24:22 C453.014 08/17/96 14:44:44 KEY20 0: 0:58 F67A.015 08/18/96 09:18:51 KEY20 0:10:04 55E5.016 08/18/96 09:21:48 KEY11 0: 0:47 E7A1.017 08/18/96 11:31:25 KEY20 0:13:03 BA14.018 08/18/96 11:48:11 KEY20 0:29:34 BC03.019 08/18/96 13:28:31 ATT-INADS1 2:56:05 -- End of List --
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-16 Command Functions 3 The fields of the Administrative Access History screen are: SeqThe Message Authentication Code and message sequence number generated for each Administrative Access History entry. The code is generated to protect the integrity of the Administrative Access History. The Message Authentication Code is followed by a period (“.”) and the sequence number of each status message. The messages are numbered in sequence from 000 to 999 and then restart at 000. DateThe date that the access took place TimeThe time that the access call came in User IDThe user ID of the administrative Key used to access the RPSD/Lock system DurationThe length of time that the call was connected in hours, minutes, and seconds
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-17 Command Functions 3 AF—Administrative Failure History Syntax and Parameters af [-] [ALL] Description Use the Administrative Failure History command to display a log of the last 100 failed administrative access attempts. The details include the date, time, user ID, and a failure reason code. To protect the integrity of the Administrative Failure History, a Message Authentication Code is generated and shown with each Administrative Failure History entry. The Message Authentication Code is followed by a period (“.”) and the sequence number of the message, for example, “CC85.000,” where “CC85” is the Message Authentication Code and “000” is the message sequence number. If the [-] and [ALL] parameters are not used, the messages are displayed in ascending order by message sequence number, 20 to a page. “- More to Come -” appears at the bottom of the each page except the last page, and “- End of List -” appears at the bottom of the last page. Press to move from page to page. When you reach the last page (indicated by “- End of List -”) page, press to return to the menu of commands. When you want to capture a long Administrative Failure History to a file on a computer, include the [ALL] parameter. Page breaks are removed and the entire Administrative Failure History is listed. To pause the report shown on the screen, press . To resume the report on the screen, press again.Parameter Description afAdministrative Failure History command [-]Include this parameter to list the Administrative Failure History in descending order by message sequence number. If this parameter is not used, the Administrative Failure History is listed in ascending order. [ALL]Use this parameter to remove the page breaks and list the entire Administrative Failure History buffer. Press to pause and resume the report on the screen. If this parameter is not used, the report is listed 20 messages to a page. ENTER ENTER ENTER ENTER ENTERENTER
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-18 Command Functions 3 To capture an Administrative Failure History, use a communications software package (such as ProComm). After you save the Administrative Failure History as a file, you can open it in a word processing application and print it. To show the Administrative Failure History in descending order by message sequence number, include the [-] parameter. Sample Command and Response The fields of the Failure History screen are: SeqThe Message Authentication Code and message sequence number generated for each Failure History entry. The code is generated to protect the integrity of the Failure History. The Message Authentication Code is followed by a period (“.”) and the sequence number of each status message. The messages are numbered in sequence from 000 to 999 and then restart at 000. DateThe date of the access failure TimeThe time of the access failure User IDThe user ID of the RPSD Key used to attempt to access the channel Device #The device number of the Key used to access the channel. The device number is a number assigned to the Key by the Key user at initialization. ReasonThe call access failure code. The codes and their explanations are provided in Table 3-2 on page 3-43 . The List Statistics command can also be used to get a very brief description for each code (see instructions on page 3-34). > af --- Admin. Failure History --- Seq. Date Time User ID Reason CC85.000 08/16/96 13:08:51 KEY22 3 -- End of List --
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-19 Command Functions 3 AS—AUX Security Syntax and Parameters To determine AUX Port status: as To enable AUX Security: as on To disable AUX Security: as off Description Use the AUX Security command to determine AUX (administrative) port status and to enable and disable security on the AUX port. !Security Alert: AUX Security should not be enabled until administrative users are added. If AUX Security is ON and no administrative users have been added, an appropriate warning message will be displayed when the RPSD system is powered up. When AUX Port security is disabled, administrative access to the RPSD system is allowed without authentication by any terminal connected to the AUX port. When AUX Port security is enabled, the administrative user must press twice to activate an administrative session and make changes to the RPSD system or to view status reports. The administrative user must use a password or passkey to authenticate access permissions and begin the administrative session.Parameter Description asAUX Security command onEnables AUX Security offDisables AUX Security ENTER ENTER ENTER ENTER
![](/img/blank.gif)
Remote Port Security Device User’s Guide 555-024-402 Issue 1 October 1996 RPSD System Administration Page 3-20 Command Functions 3 When the administrative session is complete, use the Quit command to terminate the session (see instructions on page 3-40). If AUX security is enabled and no administrative session is activated, log messages are sent to the AUX port only if the Data Terminal Ready (DTR) is high. When the administrative session is terminated, the Carrier Detect Signal (CD) goes low for one second. If DTR goes low during an administrative session, the session is terminated. Sample Command and Response Determining AUX port status (AUX Security command with no arguments): Enabling AUX Security: Disabling AUX Security: NOTE: When the current administrative session is completed by using the Quit command, AUX port security is enabled when a new session is started. > as AUX Port Security is OFF > > as on 013 07/18/96 04:19:40 AUX Port Security is ON > > as off 014 07/18/96 04:20:53 AUX Port Security is OFF >