OID reference

telNpInterfAsigValue

1.3.6.1.4.1.2007.4.1.1.6.2.1.1.3

Description

This variable allows associating a certain protocol type to the connector. In reading, this variable shows if the last allocation attempt were in success (2, ok), in error (3) or if still any attempt has not been carried out to assign a protocol to a connector (4, indefinite). In writing, it is only permitted to do a …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2007.4.1.1.6.2.1.1 (telProdNpInterfAsigEntry)
Node code
3
Node name
telNpInterfAsigValue
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2007.4.1.1.6.2.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.2007.4.1.1.6.2.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2007 4 1 1 6 2 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) teldat(2007) telproducts(4) telProductsNucleox(1) telProductsNpConfig(1) telProdNpConfInterfaceAsignation(6) telProdNpInterfAsig(2) telProdNpInterfAsigTable(1) telProdNpInterfAsigEntry(1) telNpInterfAsigValue(3)}
OID-IRI notation
  • /1/3/6/1/4/1/2007/4/1/1/6/2/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/2007/4/1/1/6/2/1/1/3
  • /ISO/3/6/1/4/1/2007/4/1/1/6/2/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/enterprise/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/enterprises/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/enterprises/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/enterprise/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/enterprise/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/enterprises/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/enterprises/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/ldap-enterprise/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/ldap-enterprise/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/vendor-objects/2007/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • /iso/org/dod/internet/private/vendor-objects/teldat/telproducts/telProductsNucleox/telProductsNpConfig/telProdNpConfInterfaceAsignation/telProdNpInterfAsig/telProdNpInterfAsigTable/telProdNpInterfAsigEntry/telNpInterfAsigValue
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
2ok
3error
4indefinite
11x28
31atppp-dial
40chb1-dial-fr
41chb1-dial-ppp
55pppas
59ppp
61fr
63sdlc
75ch-mppp
240chb2-dial-fr
241chb2-dial-ppp
61442chb1-dial-x25
61444x25
61445xst
61446int-270
261442chb2-dial-x25

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In TELDAT-CFG-CommonInfo-MIB, the row index telNpInterfAsigIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.2007.4.1.1.6.2.1.1.3.<telNpInterfAsigIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2007.4.1.1.6.2.1.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

telNpInterfAsigValue OBJECT-TYPE
        SYNTAX  INTEGER{
                ok(2),
                error(3),
                indefinite(4),
                fr(61),
                ppp(59),
                pppas(55),
                sdlc(63),
                x25(61444),
                x28(11),
                atppp-dial(31),
                chb1-dial-fr(40),
                chb1-dial-ppp(41),
                chb1-dial-x25(61442),
                chb2-dial-fr(240),
                chb2-dial-ppp(241),
                chb2-dial-x25(261442),
                ch-mppp(75),
                xst(61445),
                int-270(61446)
                }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
            "This variable allows associating a certain protocol type to the
            connector.
            In reading, this variable shows if the last allocation attempt were
            in success (2, ok), in error (3) or if still any attempt has not been
            carried out to assign a protocol to a connector (4, indefinite).
            In writing, it is only permitted to do a set to some of the values
            allowed like possible protocols associated to the connectors.
            To LAN lines, the protocol type is determined by the device hardware
            (Ethernet or TokenRing), reason why they do not admit Set operations
            that try to modify this protocol.
            Possible values for WAN lines are:
                fr (61),
                ppp (59),
                pppas (55),
                sdlc (63),
                x25 (61444),
                x28 (11),
                atppp-dial (31).
            ISDN lines can have two B channels, and its possible values are:
            B1 channel:
                chb1-dial-fr (40),
                chb1-dial-ppp (41),
                chb1-dial-x25 (61442)
            B2 channel:
                chb2-dial-fr (240),
                chb2-dial-ppp (241),
                chb2-dial-x25 (261442)
        An interface MultiLink PPP can also be assigned to ISDN lines, independently
        of the type of B channel, since these interfaces are not associated to any
        specific connector, nor physical line.
            ch-mppp (75)
        When doing the allocation, the dial-fr and dial-ppp will always go first
        and the MPPP after.

        The INTERNAL interface can take the value xst (61445), associated to index
        30.

        There can be another INTERNAL interface with the value int-270 (61446),
        associated to the index 33.

        This is the only way to assign the values, and any interrelation different
        from the associations above indicated cannot be done.

        When a atppp-dial (null, value 31) is assigned to one of the WAN lines
        by first time, two interfaces (one after the other) are added: one for the
        ATI of the B channel type: X.25(value 18), and another for the particular
        DIAL (PPP).

        The allocation of the DIAL interfaces (X25-DIAL, FR-DIAL, PPP-DIAL) is
        complex.
        In general, the allocation is done starting for the connector 1 and after
        with the connector 2.
        In general, chb1 will be assigned first and chb2 after.
        If it is tried to generate a chb2 in a connector which doesn't have chb1,
        it returns error.
        In case a same connector has FR-dial and/or PPP-dial in a B channel
        and X25-dial in the other B channel, FR-dial and / or PPP-dial will be
        assigned to chb1.

        I. If the device has an only basic access (ISDN) and can carry two B
        channels, then these will be chb1 and chb2. They are always present and
        are modified individually.

        II. If the device has two basic access and can carry two B channels, there
        are three possibilities: that they are associate one to each basic access,
        that two B channels are associate to one of the accesses and the other one
        is empty, and the inverse thing to the previous thing.

        A. CHB1 ALLOCATION:

        *If a chb1-x25 is assigned to a connector, two things can occur:

        - There is chb1 for that connector:

        If it is chb1-x25 nothing is done.

        If it is chb1-rdsi-base, it is changed to chb1-x25 and chb1-rdsi-base
        is eliminated. The PPP-DIAL or FR-DIAL which it has associate are
        eliminated if there is no another RDSI-BASE in that connector, otherwise
        they stay associated to that RDSI-BASE.

        - There isn't chb1 for that connector:

        In this case, the other connector has two B channels, chb1 and chb2.
        Therefore chb2 of the other connector is modified.

        If it is ch2-x25, it is associated to it to the chb1 of the initial connector.

        If it is chb2-rdsi-base, it is changed to chb1-x25 of the initial connector
        and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or
        FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE
        in its connector, otherwise they stay associated to that RDSI-BASE.

        *If a chb1-rdsi-base is assigned to a connector, two things can occur:

        - There is chb1 for that connector:

        If it is chb1-x25, it is changed to chb1-rdsi-base.

        If it is chb1-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb1-rdsi-base.

        - There isn't chb1 for that connector:

        In this case, the other connector has two B channels, chb1 and chb2.
        Therefore chb2 of the other connector is modified. If it is chb2-x25,
        it is changed to chb1-rdsi-base. of the initial connector.

        If it is chb2-rdsi-base, it is changed to chb1-rdsi-base of the initial connector
        and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or
        FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE
        in its connector, otherwise they stay associated to that RDSI-BASE.


        B. CHB2 ALLOCATION:

        *If a chb2-x25 is assigned to a connector (this is always done after having
        associated the chb1 to that connector), two things can occur:

        - There is chb2 for that connector:

        If it is chb2-x25 nothing is done.

        If it is chb2-rdsi-base, it is changed to chb2-x25 and chb2-rdsi-base
        is eliminated. The PPP-DIAL or FR-DIAL which it has associate are
        eliminated if there is no another RDSI-BASE in that connector, otherwise
        they stay associated to that RDSI-BASE.

        - There isn't chb2 for that connector:

        In this case, the other connector has a B channel (chb1), therefore chb1
        of the other connector is modified.

        If it is ch1-x25, it is associated to it to the chb2 of the initial connector.

        If it is chb1-rdsi-base, it is changed to chb2-x25 of the initial connector
        and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or
        FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE
        in its connector, otherwise they stay associated to that RDSI-BASE.

        *If a chb2-rdsi-base is assigned to a connector (this is always done
        after having associated the chb1 to that connector), two things can occur:

        - There is chb1 for that connector:

        If it is chb2-x25, it is changed to chb2-rdsi-base.

        If it is chb2-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb2-rdsi-base.

        - There isn't chb2 for that connector:

        In this case, the other connector has a B channel (chb1), therefore
        the chb1 of the other connector is modified.

        If it is chb1-x25, it is changed to chb2-rdsi-base. of the initial connector.

        If it is chb1-rdsi-base, it is changed to chb2-rdsi-base of the initial connector
        and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or
        FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE
        in its connector, otherwise they stay associated to that RDSI-BASE.

        III.  If the device has two basic accesses and can carry 4 B channels, they
        will be chb1 and chb2 for the RDSI1, and chb1 and chb2 for the RDSI2.
        They are always present and are modified individually.

        When a FR-DIAL or PPP-DIAL is assigned to one of the ISDN lines
        by first time, two interfaces are added: one for the ISDN and another
        for the particular DIAL (FR or PPP).

        A X25-DIAL by each ISDN basic access can only be assigned. There can
        be several FR-DIAL and PPP-DIAL in a same ISDN basic access.

        X25-dial cannot coexist with FR-dial nor PPP-dial in a same ISDN basic
        access. For that reason, when assigning a X25-dial to an ISDN connector,
        the ISDN-base is eliminated, and if there is no another RDSI-base associated
        to that connector, possible PPP-dial and FR-dial are also eliminated; the
        same happens if there is a X25-dial in a basic access and it is tried to
        add a FR-dial or a PPP-dial: then the X25-DIAL is eliminated.

        The maximum number of interfaces that the device can have is 40.
        In addition, there can be 6 DIAL in total between the two basic accesses, for
        each ISDN basic access."
        ::={ telProdNpInterfAsigEntry 3 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This variable allows associating a certain protocol type to the connector. In reading, this variable shows if the last allocation attempt were in success (2, ok), in error (3) or if still any attempt has not been carried out to assign a protocol to a connector (4, indefinite). In writing, it is only permitted to do a set to some of the values allowed like possible protocols associated to the connectors. To LAN lines, the protocol type is determined by the device hardware (Ethernet or TokenRing), reason why they do not admit Set operations that try to modify this protocol. Possible values for WAN lines are: fr (61), ppp (59), pppas (55), sdlc (63), x25 (61444), x28 (11), atppp-dial (31). ISDN lines can have two B channels, and its possible values are: B1 channel: chb1-dial-fr (40), chb1-dial-ppp (41), chb1-dial-x25 (61442) B2 channel: chb2-dial-fr (240), chb2-dial-ppp (241), chb2-dial-x25 (261442) An interface MultiLink PPP can also be assigned to ISDN lines, independently of the type of B channel, since these interfaces are not associated to any specific connector, nor physical line. ch-mppp (75) When doing the allocation, the dial-fr and dial-ppp will always go first and the MPPP after. The INTERNAL interface can take the value xst (61445), associated to index 30. There can be another INTERNAL interface with the value int-270 (61446), associated to the index 33. This is the only way to assign the values, and any interrelation different from the associations above indicated cannot be done. When a atppp-dial (null, value 31) is assigned to one of the WAN lines by first time, two interfaces (one after the other) are added: one for the ATI of the B channel type: X.25(value 18), and another for the particular DIAL (PPP). The allocation of the DIAL interfaces (X25-DIAL, FR-DIAL, PPP-DIAL) is complex. In general, the allocation is done starting for the connector 1 and after with the connector 2. In general, chb1 will be assigned first and chb2 after. If it is tried to generate a chb2 in a connector which doesn't have chb1, it returns error. In case a same connector has FR-dial and/or PPP-dial in a B channel and X25-dial in the other B channel, FR-dial and / or PPP-dial will be assigned to chb1. I. If the device has an only basic access (ISDN) and can carry two B channels, then these will be chb1 and chb2. They are always present and are modified individually. II. If the device has two basic access and can carry two B channels, there are three possibilities: that they are associate one to each basic access, that two B channels are associate to one of the accesses and the other one is empty, and the inverse thing to the previous thing. A. CHB1 ALLOCATION: *If a chb1-x25 is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25 nothing is done. If it is chb1-rdsi-base, it is changed to chb1-x25 and chb1-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is ch2-x25, it is associated to it to the chb1 of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-x25 of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb1-rdsi-base is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25, it is changed to chb1-rdsi-base. If it is chb1-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb1-rdsi-base. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is chb2-x25, it is changed to chb1-rdsi-base. of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-rdsi-base of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. B. CHB2 ALLOCATION: *If a chb2-x25 is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb2 for that connector: If it is chb2-x25 nothing is done. If it is chb2-rdsi-base, it is changed to chb2-x25 and chb2-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore chb1 of the other connector is modified. If it is ch1-x25, it is associated to it to the chb2 of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-x25 of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb2-rdsi-base is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb1 for that connector: If it is chb2-x25, it is changed to chb2-rdsi-base. If it is chb2-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb2-rdsi-base. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore the chb1 of the other connector is modified. If it is chb1-x25, it is changed to chb2-rdsi-base. of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-rdsi-base of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. III. If the device has two basic accesses and can carry 4 B channels, they will be chb1 and chb2 for the RDSI1, and chb1 and chb2 for the RDSI2. They are always present and are modified individually. When a FR-DIAL or PPP-DIAL is assigned to one of the ISDN lines by first time, two interfaces are added: one for the ISDN and another for the particular DIAL (FR or PPP). A X25-DIAL by each ISDN basic access can only be assigned. There can be several FR-DIAL and PPP-DIAL in a same ISDN basic access. X25-dial cannot coexist with FR-dial nor PPP-dial in a same ISDN basic access. For that reason, when assigning a X25-dial to an ISDN connector, the ISDN-base is eliminated, and if there is no another RDSI-base associated to that connector, possible PPP-dial and FR-dial are also eliminated; the same happens if there is a X25-dial in a basic access and it is tried to add a FR-dial or a PPP-dial: then the X25-DIAL is eliminated. The maximum number of interfaces that the device can have is 40. In addition, there can be 6 DIAL in total between the two basic accesses, for each ISDN basic access.

Sources for this description

Teldat MIB copies (MibBrowser.online)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Teldat MIB copies (MibBrowser.online)1 record · 1 source

Description 1

telNpInterfAsigValue · mandatoryTeldat MIB copies (MibBrowser.online)1 source

Status in source: mandatory.

Names: telNpInterfAsigValue

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "telNpInterfAsigValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "ok",
    "(",
    "2",
    ")",
    ",",
    "error",
    "(",
    "3",
    ")",
    ",",
    "indefinite",
    "(",
    "4",
    ")",
    ",",
    "fr",
    "(",
    "61",
    ")",
    ",",
    "ppp",
    "(",
    "59",
    ")",
    ",",
    "pppas",
    "(",
    "55",
    ")",
    ",",
    "sdlc",
    "(",
    "63",
    ")",
    ",",
    "x25",
    "(",
    "61444",
    ")",
    ",",
    "x28",
    "(",
    "11",
    ")",
    ",",
    "atppp-dial",
    "(",
    "31",
    ")",
    ",",
    "chb1-dial-fr",
    "(",
    "40",
    ")",
    ",",
    "chb1-dial-ppp",
    "(",
    "41",
    ")",
    ",",
    "chb1-dial-x25",
    "(",
    "61442",
    ")",
    ",",
    "chb2-dial-fr",
    "(",
    "240",
    ")",
    ",",
    "chb2-dial-ppp",
    "(",
    "241",
    ")",
    ",",
    "chb2-dial-x25",
    "(",
    "261442",
    ")",
    ",",
    "ch-mppp",
    "(",
    "75",
    ")",
    ",",
    "xst",
    "(",
    "61445",
    ")",
    ",",
    "int-270",
    "(",
    "61446",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This variable allows associating a certain protocol type to the connector. In reading, this variable shows if the last allocation attempt were in success (2, ok), in error (3) or if still any attempt has not been carried out to assign a protocol to a connector (4, indefinite). In writing, it is only permitted to do a set to some of the values allowed like possible protocols associated to the connectors. To LAN lines, the protocol type is determined by the device hardware (Ethernet or TokenRing), reason why they do not admit Set operations that try to modify this protocol. Possible values for WAN lines are: fr (61), ppp (59), pppas (55), sdlc (63), x25 (61444), x28 (11), atppp-dial (31). ISDN lines can have two B channels, and its possible values are: B1 channel: chb1-dial-fr (40), chb1-dial-ppp (41), chb1-dial-x25 (61442) B2 channel: chb2-dial-fr (240), chb2-dial-ppp (241), chb2-dial-x25 (261442) An interface MultiLink PPP can also be assigned to ISDN lines, independently of the type of B channel, since these interfaces are not associated to any specific connector, nor physical line. ch-mppp (75) When doing the allocation, the dial-fr and dial-ppp will always go first and the MPPP after. The INTERNAL interface can take the value xst (61445), associated to index 30. There can be another INTERNAL interface with the value int-270 (61446), associated to the index 33. This is the only way to assign the values, and any interrelation different from the associations above indicated cannot be done. When a atppp-dial (null, value 31) is assigned to one of the WAN lines by first time, two interfaces (one after the other) are added: one for the ATI of the B channel type: X.25(value 18), and another for the particular DIAL (PPP). The allocation of the DIAL interfaces (X25-DIAL, FR-DIAL, PPP-DIAL) is complex. In general, the allocation is done starting for the connector 1 and after with the connector 2. In general, chb1 will be assigned first and chb2 after. If it is tried to generate a chb2 in a connector which doesn't have chb1, it returns error. In case a same connector has FR-dial and/or PPP-dial in a B channel and X25-dial in the other B channel, FR-dial and / or PPP-dial will be assigned to chb1. I. If the device has an only basic access (ISDN) and can carry two B channels, then these will be chb1 and chb2. They are always present and are modified individually. II. If the device has two basic access and can carry two B channels, there are three possibilities: that they are associate one to each basic access, that two B channels are associate to one of the accesses and the other one is empty, and the inverse thing to the previous thing. A. CHB1 ALLOCATION: *If a chb1-x25 is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25 nothing is done. If it is chb1-rdsi-base, it is changed to chb1-x25 and chb1-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is ch2-x25, it is associated to it to the chb1 of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-x25 of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb1-rdsi-base is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25, it is changed to chb1-rdsi-base. If it is chb1-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb1-rdsi-base. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is chb2-x25, it is changed to chb1-rdsi-base. of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-rdsi-base of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. B. CHB2 ALLOCATION: *If a chb2-x25 is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb2 for that connector: If it is chb2-x25 nothing is done. If it is chb2-rdsi-base, it is changed to chb2-x25 and chb2-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore chb1 of the other connector is modified. If it is ch1-x25, it is associated to it to the chb2 of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-x25 of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb2-rdsi-base is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb1 for that connector: If it is chb2-x25, it is changed to chb2-rdsi-base. If it is chb2-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb2-rdsi-base. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore the chb1 of the other connector is modified. If it is chb1-x25, it is changed to chb2-rdsi-base. of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-rdsi-base of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. III. If the device has two basic accesses and can carry 4 B channels, they will be chb1 and chb2 for the RDSI1, and chb1 and chb2 for the RDSI2. They are always present and are modified individually. When a FR-DIAL or PPP-DIAL is assigned to one of the ISDN lines by first time, two interfaces are added: one for the ISDN and another for the particular DIAL (FR or PPP). A X25-DIAL by each ISDN basic access can only be assigned. There can be several FR-DIAL and PPP-DIAL in a same ISDN basic access. X25-dial cannot coexist with FR-dial nor PPP-dial in a same ISDN basic access. For that reason, when assigning a X25-dial to an ISDN connector, the ISDN-base is eliminated, and if there is no another RDSI-base associated to that connector, possible PPP-dial and FR-dial are also eliminated; the same happens if there is a X25-dial in a basic access and it is tried to add a FR-dial or a PPP-dial: then the X25-DIAL is eliminated. The maximum number of interfaces that the device can have is 40. In addition, there can be 6 DIAL in total between the two basic accesses, for each ISDN basic access.\"",
    "::=",
    "{",
    "telProdNpInterfAsigEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "ok",
            2
          ],
          [
            "error",
            3
          ],
          [
            "indefinite",
            4
          ],
          [
            "fr",
            61
          ],
          [
            "ppp",
            59
          ],
          [
            "pppas",
            55
          ],
          [
            "sdlc",
            63
          ],
          [
            "x25",
            61444
          ],
          [
            "x28",
            11
          ],
          [
            "atppp-dial",
            31
          ],
          [
            "chb1-dial-fr",
            40
          ],
          [
            "chb1-dial-ppp",
            41
          ],
          [
            "chb1-dial-x25",
            61442
          ],
          [
            "chb2-dial-fr",
            240
          ],
          [
            "chb2-dial-ppp",
            241
          ],
          [
            "chb2-dial-x25",
            261442
          ],
          [
            "ch-mppp",
            75
          ],
          [
            "xst",
            61445
          ],
          [
            "int-270",
            61446
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This variable allows associating a certain protocol type to the connector. In reading, this variable shows if the last allocation attempt were in success (2, ok), in error (3) or if still any attempt has not been carried out to assign a protocol to a connector (4, indefinite). In writing, it is only permitted to do a set to some of the values allowed like possible protocols associated to the connectors. To LAN lines, the protocol type is determined by the device hardware (Ethernet or TokenRing), reason why they do not admit Set operations that try to modify this protocol. Possible values for WAN lines are: fr (61), ppp (59), pppas (55), sdlc (63), x25 (61444), x28 (11), atppp-dial (31). ISDN lines can have two B channels, and its possible values are: B1 channel: chb1-dial-fr (40), chb1-dial-ppp (41), chb1-dial-x25 (61442) B2 channel: chb2-dial-fr (240), chb2-dial-ppp (241), chb2-dial-x25 (261442) An interface MultiLink PPP can also be assigned to ISDN lines, independently of the type of B channel, since these interfaces are not associated to any specific connector, nor physical line. ch-mppp (75) When doing the allocation, the dial-fr and dial-ppp will always go first and the MPPP after. The INTERNAL interface can take the value xst (61445), associated to index 30. There can be another INTERNAL interface with the value int-270 (61446), associated to the index 33. This is the only way to assign the values, and any interrelation different from the associations above indicated cannot be done. When a atppp-dial (null, value 31) is assigned to one of the WAN lines by first time, two interfaces (one after the other) are added: one for the ATI of the B channel type: X.25(value 18), and another for the particular DIAL (PPP). The allocation of the DIAL interfaces (X25-DIAL, FR-DIAL, PPP-DIAL) is complex. In general, the allocation is done starting for the connector 1 and after with the connector 2. In general, chb1 will be assigned first and chb2 after. If it is tried to generate a chb2 in a connector which doesn't have chb1, it returns error. In case a same connector has FR-dial and/or PPP-dial in a B channel and X25-dial in the other B channel, FR-dial and / or PPP-dial will be assigned to chb1. I. If the device has an only basic access (ISDN) and can carry two B channels, then these will be chb1 and chb2. They are always present and are modified individually. II. If the device has two basic access and can carry two B channels, there are three possibilities: that they are associate one to each basic access, that two B channels are associate to one of the accesses and the other one is empty, and the inverse thing to the previous thing. A. CHB1 ALLOCATION: *If a chb1-x25 is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25 nothing is done. If it is chb1-rdsi-base, it is changed to chb1-x25 and chb1-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is ch2-x25, it is associated to it to the chb1 of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-x25 of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb1-rdsi-base is assigned to a connector, two things can occur: - There is chb1 for that connector: If it is chb1-x25, it is changed to chb1-rdsi-base. If it is chb1-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb1-rdsi-base. - There isn't chb1 for that connector: In this case, the other connector has two B channels, chb1 and chb2. Therefore chb2 of the other connector is modified. If it is chb2-x25, it is changed to chb1-rdsi-base. of the initial connector. If it is chb2-rdsi-base, it is changed to chb1-rdsi-base of the initial connector and chb2-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. B. CHB2 ALLOCATION: *If a chb2-x25 is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb2 for that connector: If it is chb2-x25 nothing is done. If it is chb2-rdsi-base, it is changed to chb2-x25 and chb2-rdsi-base is eliminated. The PPP-DIAL or FR-DIAL which it has associate are eliminated if there is no another RDSI-BASE in that connector, otherwise they stay associated to that RDSI-BASE. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore chb1 of the other connector is modified. If it is ch1-x25, it is associated to it to the chb2 of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-x25 of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. *If a chb2-rdsi-base is assigned to a connector (this is always done after having associated the chb1 to that connector), two things can occur: - There is chb1 for that connector: If it is chb2-x25, it is changed to chb2-rdsi-base. If it is chb2-rdsi-base, PPP-DIAL or FR-DIAL is added to that chb2-rdsi-base. - There isn't chb2 for that connector: In this case, the other connector has a B channel (chb1), therefore the chb1 of the other connector is modified. If it is chb1-x25, it is changed to chb2-rdsi-base. of the initial connector. If it is chb1-rdsi-base, it is changed to chb2-rdsi-base of the initial connector and chb1-rdsi-base is eliminated from its connector. The PPP-DIAL or FR-DIAL which it has associate, are eliminated if there is no another RDSI-BASE in its connector, otherwise they stay associated to that RDSI-BASE. III. If the device has two basic accesses and can carry 4 B channels, they will be chb1 and chb2 for the RDSI1, and chb1 and chb2 for the RDSI2. They are always present and are modified individually. When a FR-DIAL or PPP-DIAL is assigned to one of the ISDN lines by first time, two interfaces are added: one for the ISDN and another for the particular DIAL (FR or PPP). A X25-DIAL by each ISDN basic access can only be assigned. There can be several FR-DIAL and PPP-DIAL in a same ISDN basic access. X25-dial cannot coexist with FR-dial nor PPP-dial in a same ISDN basic access. For that reason, when assigning a X25-dial to an ISDN connector, the ISDN-base is eliminated, and if there is no another RDSI-base associated to that connector, possible PPP-dial and FR-dial are also eliminated; the same happens if there is a X25-dial in a basic access and it is tried to add a FR-dial or a PPP-dial: then the X25-DIAL is eliminated. The maximum number of interfaces that the device can have is 40. In addition, there can be 6 DIAL in total between the two basic accesses, for each ISDN basic access."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2007)

Eduardo Robles Esteban

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2007.4.1.1.6.2.1.1.1 telNpInterfAsigIndex00
1.3.6.1.4.1.2007.4.1.1.6.2.1.1.2 telNpInterfAsigConector00