cc/td/doc/product/wanbu/access/aprod
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Management Access Point (MAP) Management Function

Management Access Point (MAP) Management Function

Principle

The calling of a Management Function (MF) of an equipment requires the use of a virtual circuit (VC). Successive calls to several MFs leads to a series of opening and closing of VCs which increases their access time.

The "Management Access Point" (MAP) makes it possible to establish a single VC with an internal subscriber of the equipment. This VC is designed to call the MF(s) in place of the user.

To accomplish this, the user establishes a call with the MAP and then accesses one of the MFs via a menu. When the MF is cleared, the VC cleared is no longer the one existing between the user and the MF but the one which links the MAP to the MF.

A call between the user and the AP can open only a single MAP/MF session. The MAP is transparent to the data which transits in both directions; the "called" MAP is located on the module which the call reaches.

When the MAP observes that the maximum number of MAPs is reached, any further access request will be rejected.

The MAP may be called with a CUG; the opening of all the sessions then takes place with the user of this CUG.


Note The possibility of call several MAP (Management Access Points) on the same equipment is not implemented at present.

The calling of two MAP on the same equipment causes a fatal error.

In the case of multimode equipment, it is possible to call a MAP on each module of the equipment.

Access

The syntax of the access code is as follows:

  DNIC ZO 99 D SI No. PASSWORD

Note Refer to § 2 for a detailed breakdown of this code.

· SI No. 18:

Clear-language mode

· PASSWORD:

Exists if it configured (PP by default)


Validation of the MAP management function access code leads to the display of the following welcome page:

MAP ADDR =

< DNIC ZO of equipment >

MF ADDR =

< DNIC ZO by default of equipment to be called >

EQUIPMENT ADDRESS?

(DNICZOAB?FAC?VAL?FAC?VAL?...?CALL DATA)

The user can enter the following information on a command line:

  SI No. PASSWORD (-ACO).

The calling format is identical to that used for the MMI management function when entering parameters: address, facilities, call data.

Example:

Calling of "Statistics" management function of equipment 900000 with the facility of code 02 and the value 05:

  90000099,0205,14SS

Calling of "Telemaintenance" management function of the equipment 593210 with the facilities of respective codes 02 and 01 and of respective values 05 and 04:

  59321099,02050104,14MM

The MAP saves the address of the last equipment called; for this reason, as long as the MF is located on the same equipment, it is not necessary to enter a new equipment address.

Example:

Calling of "Statistics" MF: 900000:

90000099,,14SS

Clearing of session

Calling of "Exchange observation" MF:

,,04OO04

of line 4 of 90000

Messages delivered by the MAP

After validation of the command line, if the syntax is correct and the call successful, the following messages appear:

  CONNECTION IN PROGRESS...
  SESSION OPEN

When the syntax of the command is not correct and the call data are not entered, the following message is displayed:

  COMMAND ERROR

When the call is cleared (MF busy, call data incorrect, clearing coming from routing, etc.), the following message is displayed:

  CONNECTION REFUSED BY REMOTE: <Cause/Diagnostic>

The menu of the MAP is displayed again and the user can again enter the command.

Clearing during a session leads to the display of the following messages:

Clearing by remote:
  SESSION CLEARED BY REMOTE: <Cause/Diagnostic>
Clearing by the user:
  END OF SESSION

The key "<" is used to quit the management function and clear the MAP/MF VC.

IMPORTANT

The "^P LIB" command causes the clearing of the MAP/MF and User/MAP VCs.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jan 25 14:06:59 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.