OID reference

pegasusMibModule

1.3.6.1.4.1.6368.2

Description

This MIB applies to the PEGASUS SDSL product manufactured by Schmid Telecom Zurich. The MIB is modelled after the PEM management model, so object hierarchy and individual variables agree with the PEM client. The overall structure is five groups, one for each of DSL, V5 and Data cards, one with global parameters for th…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6368 (6368, schmidtelecom)
Node code
2
Node name
pegasusMibModule
Numeric OID
1.3.6.1.4.1.6368.2
URN notation
urn:oid:1.3.6.1.4.1.6368.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6368 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2)}
OID-IRI notation
  • /1/3/6/1/4/1/6368/2
  • /ISO/Identified-Organization/6/1/4/1/6368/2
  • /ISO/3/6/1/4/1/6368/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6368/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/enterprises/6368/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6368/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/vendor-objects/6368/pegasusMibModule
  • /iso/identified-organization/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule
  • /iso/org/dod/internet/private/enterprise/6368/pegasusMibModule
  • /iso/org/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule
  • /iso/org/dod/internet/private/enterprises/6368/pegasusMibModule
  • /iso/org/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule
  • /iso/org/dod/internet/private/ldap-enterprise/6368/pegasusMibModule
  • /iso/org/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule
  • /iso/org/dod/internet/private/vendor-objects/6368/pegasusMibModule
  • /iso/org/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule
  • Additional combinations skipped.

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

pegasusMibModule  MODULE-IDENTITY
  LAST-UPDATED "200412170000Z"  -- 17 December, 2004
  ORGANIZATION "Schmid Telecom, Zurich"
  CONTACT-INFO
    "Schmid Telecom AG
     Binzstrasse 35, CH-8048 Zurich
     Switzerland

     Email: xdslsupport@schmid-telecom.ch"
  DESCRIPTION
    "This MIB applies to the PEGASUS SDSL product manufactured by Schmid
    Telecom Zurich. The MIB is modelled after the PEM management model, so
    object hierarchy and individual variables agree with the PEM client.

    The overall structure is five groups, one for each of DSL, V5 and Data
    cards, one with global parameters for the whole rack, and finally one group
    for performance history measurement.

    The DSL group contains four tables:

    - dslCardTable       one entry for each DSL card (line card) configured.
    - dslLinkTable       one entry for each DSL link.
    - dslInterfaceTable  one entry per DSL interface, i.e. two per DSL link.
    - iadTable           one entry per DSL link.
    - dslLinkCosTable    one entry per DSL link.

    The V5 group contains five tables:

    - v5CardTable        one entry for each V5 card configured.
    - v5LinkTable        one entry for each V5 link.
    - v5InterfaceTable   one entry for each V5 interface.
    - v5IsdnPortTable    one entry per ISDN User Port (S0 interface on IAD).
    - v5LccTable         one entry per Logical Communication Channel.

    The data switch group contains two tables:

    - dataCardTable      one entry per data card (normally one)
    - dataPortTable      one entry per trunk interface.

    The Pegasus System group contains individual variables related to the
    rack as a whole.

    The perf group for performance histories contains two tables and one extra
    variable:

    - perfSweeperCyclePeriod  how soon are unused perfDataTable entries cleared
    - perfControlTable        configuration of performance history monitoring
    - perfDataTable           performance history registers

    Note

    - Notification definitions are singled out to their own MIB, to allow for
      alternative sets of notification styles.
    - Tables in this MIB are indexed hierarchically with physical attributes.
      E.g. all cards are indexed by the slot number. DSL links are indexed by
      two variables: first the slot number of the DSL card which carries the
      link, then the number of the link within that card.
    - Unlike the PEM client, this MIB does not model V5 Physical Communication
      Channels explicitely. They have no interesting variables of their own.
      Rather, the user allots a range of these objects through the V5 link
      configuration, and then maps the Logical Communication Channels to them
      (using indexes within the alloted range, of course). These objects are
      then created, deleted and managed under the hood.
    - V5 interfaces are logical entities, unlike DSL interfaces.
    - ISDN user ports are physically part of the IAD, and are indexed by DSL
      attributes. Their configuration, though, belongs to V5, so the user port
      tables are in the V5 group, not in the DSL group."

  REVISION "200412170000Z"  -- 17 December, 2004
  DESCRIPTION
    "A new table dslLinkCosTable has been added to the dsl branch to allow 
    the configuration of the Class of Service (COS) attributes. Each row 
    within this table corresponds to a DSL link.
    Besides, some missing type and variable descriptions have been added."
  REVISION "200406140000Z"  -- 14 June, 2004
  DESCRIPTION
    "Line identifiers are have been added for ISDN user ports and V5 links."
  REVISION "200404080000Z"  -- 8 April, 2004
  DESCRIPTION
    "Maximum size of dslLinkAddress and trapDestination have been increased."
  REVISION "200312110000Z"  -- 11 December, 2003
  DESCRIPTION
    "Improved the description of DslLinkLoopEnum. The variables 
    v5IsdnPortActiveLoop and authRespEnabled are now obsolete. The agent never 
    sends an error message if the request contains a wrong community string."
  REVISION "200310300000Z"  -- 30 October, 2003
  DESCRIPTION
    "Corrected the value range of perfSweepCyclePeriod. The new maximum value 
    is 604800 seconds (1 week)."
  REVISION "200310240000Z"  -- 24 October, 2003
  DESCRIPTION
    "Declared perfControlEffectiveUpdatePeriod as obsolete. The definition 
    would be now redundant to perfControlUpdatePeriod.
    The behaviour of v5LccPccV5LinkNumber/v5LccPccTimeslot has been modified.
    The assignment of a PCC becomes active after both attributes have been set.
    To erase the PCC, only one of these attributes has to be set to 0. Write 
    access is allowed for RowStatus active now. The comments of attributes and 
    table habe been aapted."
  REVISION "200310020000Z"  -- 2 October, 2003
  DESCRIPTION
    "Declared hwAdaptionPolicy as obsolete. The definition of DataPortSpeedEnum
    and DataPortFlowConrtolEnum has been moved within the MIB file to make 
    possible the compilation without errors using the MG-Soft MIB Compiles.
    This revision of the MIB is compatible with the preceeding revision."
  REVISION "200303140000Z"  -- 14 March, 2003
  DESCRIPTION
    "Deleted all IP base address objects: dslCardIPBaseAddress,
    dataCardIPBaseAddress, and v5CardIPBaseAddress.  The base address of a
    card can no longer be set through Pegasus Management, but only through
    the CLI on the card itself.
    The remaining objects were renumbered to keep the numbering compact, so
    this revision of the MIB is again NOT COMPATIBLE with preceeding revisions!
    Changed the type of perfControlIndex and perfDataIndex from INTEGER to
    Integer32, with range (1..2147483647), which is the set of positive values
    possible for an Integer32.  This change is rather formal (Integer32 is
    indistinguishable from INTEGER, as SNMPv2-SMI puts it, that is, its
    serialisation is identical to INTEGER), but it makes certain parsers happy.
    In fact, the value is always chosen by the client, and the agent gladly
    takes what it gets - including 0 and negative values."
  REVISION "200303110000Z"  -- 11 March, 2003
  DESCRIPTION
    "Deleted all config version objects: dslCardConfigVersion,
    v5CardConfigVersion, and dataCardConfigVersion.  These objects were never
    really useful for customers, and so have been removed.  Objects following
    them were renumbered, so this revision of the MIB is NOT COMPATIBLE with
    preceeding revisions!
    Added new literals at end of DataPortSpeedEnum and DataPortFlowControlEnum
    to convey that the value of a (read-only) status variable is currently
    unknown (for example because a sub-device like the Iad cannot be queried
    because is not connected).
    Added four new objects to the Iad table, to describe configuration and
    corresponding status of the Ethernet port on the Iad.  This was mandated
    by the Iad Rev. B, which can control its Ethernet port and also report its
    status.  For the older Iad Rev. B, control and status of the Ethernet port
    are not available, and the new objects will read with fixed values. The
    objects are: iadEthPortSpeed, iadEthCurrentPortSpeed, iadEthFlowControl,
    iadEthCurrentFlowControl."
  REVISION "200210090000Z"  -- 9 October, 2002
  DESCRIPTION
    "SignalQuality and Attenuation were prefixed with dslLink in
    dslInterfaceEntry sequence, changed to dslInterface.
    Type DslLinkNumber was defined as 1..8, but V5 configurations already hold
    user port parameters for future DSL cards with 16 DSL links. This caused
    problems with some clients, so the definition was changed to 1..16.
    Revamped description of writeCommunity."
  REVISION "200209190000Z"  -- 19 September, 2002
  DESCRIPTION
    "The following objects were added or changed:

    dataPortSpeed         New literal autoCrossoverAndPortSpeed(1) was added to
                          type DataPortSpeedEnum. Warning: existing literals
                          have changed their ordinal numbers.
                          Revamped description, added reference.

    v5CardFlags           Four new objects added to table v5CardTable, and
    v5CardETSIRelease     the new type V5CardFlagSet.
    v5CardE1LineCode
    v5CardFrameFormat

    v5LinkAlarmStatus     New literal v5LinkAlarmIdFailure(6) was added to type
                          V5LinkAlarmStatusElem (at the end, without changing
                          the ordinal numbers of existing literals).

    iadAlarmStatus        New literal dcContinuity(2) was added to type
                          IadAlarmStatusElem (at the end, without changing the
                          ordinal numbers of existing literals).

    dslInterfaceSignalQuality  Three new objects added to dslInterfaceTable.
    dslInterfaceAttenuation
    v5InterfaceAlarmStatus"
  REVISION "200208230000Z"  -- 23 August, 2002
  DESCRIPTION
    "Fixed a number of typos and formatting problems. Renamed l2 group to data
    group. (Input from BBe)."
  REVISION "200207160000Z"  -- 16 July, 2002
  DESCRIPTION
    "Changed all type assignments with BITS to textual conventions (BITS is part
    of the OBJECT-TYPE and TEXTUAL-CONVENTION macros (for SMI v2 only), but not
    a ASN.1 builtin or DefinedType, and so cannot be used in a type assignment
    or sequence definition). The types are:
    AvailabilityStatusElem, DslLinkAlarmElem, DslCardAlarmStatus,
    IadAlarmStatusElem, DslPerformanceStatusElem, V5LinkAlarmStatusElem,
    V5IsdnPortAlarmStatusElem, RackAlarmStatusElem, PerfControlStatus.
    Added import clause for TEXTUAL-CONVENTION.
    Changed dataCardAvailabilityStatus in DataCardEntry from BITS to
    AvailabilityStatusElem.
    Changed spelling bit-names of AvailabilityStatusElem to agree with ASN.1
    definitions in X.721.
    Added description for the AvailabilityStatusElem textual convention (taken
    from attributes, with updates).
    In v5CardTable and v5LccTable, changed all read-write access clauses to
    read-create.
    Improved list of references in initial comment.
    Added list of tools tested with this MIB to initial comment.
    Constrained type Priority to (0..7).
    Constrained dslLinkNumberOfZBits to (0..1)."
  REVISION "200207030000Z"  -- 3 July, 2002
  DESCRIPTION
    "dslLinkAssignedTrunk was TrunkNumber in its Object-Type definition, fixed
    to TrunkNumberOrZero. For dslCardIPBaseAddress, v5CardIPBaseAddress and
    dataCardIPBaseAddress: corrected descriptions and examples to have plausible
    slot-numbers. ipBaseAddress adapted, with general examples."
  REVISION "200206240000Z"  -- 24 June, 2002
  DESCRIPTION
    "User manual realignment with syntax errors fixed, raw version."
  REVISION "200206200000Z"  -- 20 June, 2002
  DESCRIPTION
    "Changed all ...IPAddressPrefix variable names to ...IPBaseAddress (dslCard,
    v5Card, dataCard, pegasusSystem. Changed the variable in pegasusSystem from
    DisplayString to IpAddress, to agree with other variables.
    Renamed dataCardAlarmStatus to rackAlarmStatus (also renamed the associated
    BITS type to RackAlarmStatusElem). Moved to pegasusSystem.
    Renamed dslLinkAssociatedTrunk to dslLinkAssignedTrunk, to realign with
    PEMClient.
    Eliminated type DataPortNumber, used TrunkNumber in its place. Also created
    type TrunkNumberOrZero, to allow reference to 'no trunk'.
    Renamed ...ProgramVersion to ...FirmwareVersion: dslCard, dslCardM16, iad,
    v5Card, dataCard.
    Removed dataPortVLAN (and its type VLanId): is automatically computed as
    part of the enhanced switching configuration. For future general VLAN
    switching, it will be configured through standard MIBs.
    Removed FilterBroadcast and FilterUnknown for both dslLink and dataPort:
    present in the devices, but not in the PEMClient. It was not clear if these
    are useful, and according to PSt it was decided to 'hide' them.
    Removed special(4) from DslLinkLoopEnum - no longer supported."
  REVISION "200206070000Z"  -- 7 June, 2002
  DESCRIPTION
    "Removed ProceduralStatus and its enumeration type from all three cards and
    IAD. Fixed spelling of 'v5LccIsProteced' to 'v5LccIsProtected'. Improved
    various descriptions."
  REVISION "200205220000Z"  -- 22 May, 2002
  DESCRIPTION
    "Changed Gauge32 in perfData to Integer32, removed import for Gauge32.
    Added description for v5CardRowStatus."
  REVISION "200205100000Z"  -- 10 May, 2002
  DESCRIPTION
    "Improved descriptions for dslLink{DataRate,LinkRate,NumberOfBRA} and
    dslLinkDynamicSlotAllocation.
    Added 6 remaining objects for SNMP configuration to group pegasusSystem
    (read/write/trapCommunity, agentPort, authRespEnabled, trapDestination).
    Improved description of objects in perf group.
    DslCard, dataCard: removed AdminState, renumbered attributes contiguously.
    v5Lcc: renumbered objects contiguously, starting at 1.
    v5Interface: added RowStatus, changed all read-write objects to read-create,
    renumbered objects contigously, starting at 1.
    v5Link: added RowStatus, changed all read-write objects to read-create.
    iad: removed AdminState, renumbered attributes contiguously."
  REVISION "200204250000Z"  -- 25 Apr, 2002
  DESCRIPTION
    "Added group for performance history of V5 links and DSL interfaces.
    Added description for dslLinkNumberOfBRA, dslLinkDataRate, and
    dslLinkLineRate."
  REVISION "200204160000Z"  -- 16 Apr, 2002
  DESCRIPTION
    "Changed numbering scheme. { schmidtelecom 1 } is now reserved for a
    centralized registry, and the pegasusMibModule is { schmidtelecom 2 }.
    All groups and objects in this and other Pegasus MIBs are below
    pegasusMibModule."
  REVISION "200204030000Z"  -- 3 Apr, 2002
  DESCRIPTION
    "v5CardTable and V5LccTable (LogCommChan) now have a RowStatus. For 
    v5CardTable, this controls provisioning mode, but it does not yet
    support creation. For v5LccTable, it controls verification of the
    v5LccPccV5LinkNumber and and v5LccPccTimeslot columns, which define
    the Pcc (PhysCommChan) (i.e. the RowStatus supports transactions on
    these values). Again, creation is not yet supported for v5LccTable.
    The new object mibRevision holds the revision number of the MIB with
    which the agent was compiled."
  REVISION "200203190000Z"  -- 19 Mar, 2002
  DESCRIPTION
    "Added missing import of DisplayString. Changed definitions of dslInterface
    counter values to Counter32 consistently. Added one missing variable to
    V5IsdnPortEntry sequence."
  REVISION "200203140000Z"  -- 14 Mar, 2002
  DESCRIPTION
    "Initial comments updated and moved to the module description, where they
    are more useful for typical browsers."
  REVISION "200203010000Z"  -- 1 Mar, 2002
  DESCRIPTION
    "Added PegasusSystem."
  REVISION "200202280000Z"  -- 28 Feb, 2002
  DESCRIPTION
    "Removed dslInterfaceIsRestartEnabled. Renumbered dslInterfaceEntry and
    dslLinkEntry columns to start with one and form a compact sequence."
  REVISION "200202180000Z"  -- 18 Feb, 2002
  DESCRIPTION
    "Added initial comment with overview and additional hints.
    Corrected spelling of CommStateEnum literals to comply with SNMPv2 (dashes
    were replaced by mixed-case spelling).
    Added VLAN support (DSL link and data card port). Presently only for
    enhanced mode, transparent and VLAN modes to come.
    Removed some VLAN related definitions which are not yet used."
  REVISION "200202140000Z"  -- 14 Feb, 2002
  DESCRIPTION
    "Added definitions for data switch and data switch port."
  REVISION "200201250000Z"  -- 25 Jan, 2002
  DESCRIPTION
    "Added object-type definition of v5IsdnPortAlarmStatus. Renumbered
     remaining objects."
  REVISION "200201230000Z"  -- 23 Jan, 2002
  DESCRIPTION
    "Changed all occurrences of NetworkAddress to IpAddress (imported
    from SNMPv2-SMI). NetworkAddress was in SNMPv1, but was replaced
    by IpAddress for SNMPv2.

    Corrected dataCardVLANMode to SYNTAX TruthValue - it erronously
    used NetworkAddress.

    Correct the year on the previous revision clause."
  REVISION "200012210000Z"  -- 21 Dec, 2001
  DESCRIPTION
    "Initial revision."
  ::= { schmidtelecom 2 }

Meaning

Descriptions

1 unique

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

This MIB applies to the PEGASUS SDSL product manufactured by Schmid Telecom Zurich. The MIB is modelled after the PEM management model, so object hierarchy and individual variables agree with the PEM client. The overall structure is five groups, one for each of DSL, V5 and Data cards, one with global parameters for the whole rack, and finally one group for performance history measurement. The DSL group contains four tables: - dslCardTable one entry for each DSL card (line card) configured. - dslLinkTable one entry for each DSL link. - dslInterfaceTable one entry per DSL interface, i.e. two per DSL link. - iadTable one entry per DSL link. - dslLinkCosTable one entry per DSL link. The V5 group contains five tables: - v5CardTable one entry for each V5 card configured. - v5LinkTable one entry for each V5 link. - v5InterfaceTable one entry for each V5 interface. - v5IsdnPortTable one entry per ISDN User Port (S0 interface on IAD). - v5LccTable one entry per Logical Communication Channel. The data switch group contains two tables: - dataCardTable one entry per data card (normally one) - dataPortTable one entry per trunk interface. The Pegasus System group contains individual variables related to the rack as a whole. The perf group for performance histories contains two tables and one extra variable: - perfSweeperCyclePeriod how soon are unused perfDataTable entries cleared - perfControlTable configuration of performance history monitoring - perfDataTable performance history registers Note - Notification definitions are singled out to their own MIB, to allow for alternative sets of notification styles. - Tables in this MIB are indexed hierarchically with physical attributes. E.g. all cards are indexed by the slot number. DSL links are indexed by two variables: first the slot number of the DSL card which carries the link, then the number of the link within that card. - Unlike the PEM client, this MIB does not model V5 Physical Communication Channels explicitely. They have no interesting variables of their own. Rather, the user allots a range of these objects through the V5 link configuration, and then maps the Logical Communication Channels to them (using indexes within the alloted range, of course). These objects are then created, deleted and managed under the hood. - V5 interfaces are logical entities, unlike DSL interfaces. - ISDN user ports are physically part of the IAD, and are indexed by DSL attributes. Their configuration, though, belongs to V5, so the user port tables are in the V5 group, not in the DSL group.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

pegasusMibModule · unspecifiedMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: unspecified.

Names: pegasusMibModule

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "pegasusMibModule",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303431323137303030305a22"
    ],
    "ORGANIZATION",
    "\"Schmid Telecom, Zurich\"",
    "CONTACT-INFO",
    "\"Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch\"",
    "DESCRIPTION",
    "\"This MIB applies to the PEGASUS SDSL product manufactured by Schmid Telecom Zurich. The MIB is modelled after the PEM management model, so object hierarchy and individual variables agree with the PEM client. The overall structure is five groups, one for each of DSL, V5 and Data cards, one with global parameters for the whole rack, and finally one group for performance history measurement. The DSL group contains four tables: - dslCardTable one entry for each DSL card (line card) configured. - dslLinkTable one entry for each DSL link. - dslInterfaceTable one entry per DSL interface, i.e. two per DSL link. - iadTable one entry per DSL link. - dslLinkCosTable one entry per DSL link. The V5 group contains five tables: - v5CardTable one entry for each V5 card configured. - v5LinkTable one entry for each V5 link. - v5InterfaceTable one entry for each V5 interface. - v5IsdnPortTable one entry per ISDN User Port (S0 interface on IAD). - v5LccTable one entry per Logical Communication Channel. The data switch group contains two tables: - dataCardTable one entry per data card (normally one) - dataPortTable one entry per trunk interface. The Pegasus System group contains individual variables related to the rack as a whole. The perf group for performance histories contains two tables and one extra variable: - perfSweeperCyclePeriod how soon are unused perfDataTable entries cleared - perfControlTable configuration of performance history monitoring - perfDataTable performance history registers Note - Notification definitions are singled out to their own MIB, to allow for alternative sets of notification styles. - Tables in this MIB are indexed hierarchically with physical attributes. E.g. all cards are indexed by the slot number. DSL links are indexed by two variables: first the slot number of the DSL card which carries the link, then the number of the link within that card. - Unlike the PEM client, this MIB does not model V5 Physical Communication Channels explicitely. They have no interesting variables of their own. Rather, the user allots a range of these objects through the V5 link configuration, and then maps the Logical Communication Channels to them (using indexes within the alloted range, of course). These objects are then created, deleted and managed under the hood. - V5 interfaces are logical entities, unlike DSL interfaces. - ISDN user ports are physically part of the IAD, and are indexed by DSL attributes. Their configuration, though, belongs to V5, so the user port tables are in the V5 group, not in the DSL group.\"",
    "REVISION",
    [
      "literal",
      "223230303431323137303030305a22"
    ],
    "DESCRIPTION",
    "\"A new table dslLinkCosTable has been added to the dsl branch to allow the configuration of the Class of Service (COS) attributes. Each row within this table corresponds to a DSL link. Besides, some missing type and variable descriptions have been added.\"",
    "REVISION",
    [
      "literal",
      "223230303430363134303030305a22"
    ],
    "DESCRIPTION",
    "\"Line identifiers are have been added for ISDN user ports and V5 links.\"",
    "REVISION",
    [
      "literal",
      "223230303430343038303030305a22"
    ],
    "DESCRIPTION",
    "\"Maximum size of dslLinkAddress and trapDestination have been increased.\"",
    "REVISION",
    [
      "literal",
      "223230303331323131303030305a22"
    ],
    "DESCRIPTION",
    "\"Improved the description of DslLinkLoopEnum. The variables v5IsdnPortActiveLoop and authRespEnabled are now obsolete. The agent never sends an error message if the request contains a wrong community string.\"",
    "REVISION",
    [
      "literal",
      "223230303331303330303030305a22"
    ],
    "DESCRIPTION",
    "\"Corrected the value range of perfSweepCyclePeriod. The new maximum value is 604800 seconds (1 week).\"",
    "REVISION",
    [
      "literal",
      "223230303331303234303030305a22"
    ],
    "DESCRIPTION",
    "\"Declared perfControlEffectiveUpdatePeriod as obsolete. The definition would be now redundant to perfControlUpdatePeriod. The behaviour of v5LccPccV5LinkNumber/v5LccPccTimeslot has been modified. The assignment of a PCC becomes active after both attributes have been set. To erase the PCC, only one of these attributes has to be set to 0. Write access is allowed for RowStatus active now. The comments of attributes and table habe been aapted.\"",
    "REVISION",
    [
      "literal",
      "223230303331303032303030305a22"
    ],
    "DESCRIPTION",
    "\"Declared hwAdaptionPolicy as obsolete. The definition of DataPortSpeedEnum and DataPortFlowConrtolEnum has been moved within the MIB file to make possible the compilation without errors using the MG-Soft MIB Compiles. This revision of the MIB is compatible with the preceeding revision.\"",
    "REVISION",
    [
      "literal",
      "223230303330333134303030305a22"
    ],
    "DESCRIPTION",
    "\"Deleted all IP base address objects: dslCardIPBaseAddress, dataCardIPBaseAddress, and v5CardIPBaseAddress. The base address of a card can no longer be set through Pegasus Management, but only through the CLI on the card itself. The remaining objects were renumbered to keep the numbering compact, so this revision of the MIB is again NOT COMPATIBLE with preceeding revisions! Changed the type of perfControlIndex and perfDataIndex from INTEGER to Integer32, with range (1..2147483647), which is the set of positive values possible for an Integer32. This change is rather formal (Integer32 is indistinguishable from INTEGER, as SNMPv2-SMI puts it, that is, its serialisation is identical to INTEGER), but it makes certain parsers happy. In fact, the value is always chosen by the client, and the agent gladly takes what it gets - including 0 and negative values.\"",
    "REVISION",
    [
      "literal",
      "223230303330333131303030305a22"
    ],
    "DESCRIPTION",
    "\"Deleted all config version objects: dslCardConfigVersion, v5CardConfigVersion, and dataCardConfigVersion. These objects were never really useful for customers, and so have been removed. Objects following them were renumbered, so this revision of the MIB is NOT COMPATIBLE with preceeding revisions! Added new literals at end of DataPortSpeedEnum and DataPortFlowControlEnum to convey that the value of a (read-only) status variable is currently unknown (for example because a sub-device like the Iad cannot be queried because is not connected). Added four new objects to the Iad table, to describe configuration and corresponding status of the Ethernet port on the Iad. This was mandated by the Iad Rev. B, which can control its Ethernet port and also report its status. For the older Iad Rev. B, control and status of the Ethernet port are not available, and the new objects will read with fixed values. The objects are: iadEthPortSpeed, iadEthCurrentPortSpeed, iadEthFlowControl, iadEthCurrentFlowControl.\"",
    "REVISION",
    [
      "literal",
      "223230303231303039303030305a22"
    ],
    "DESCRIPTION",
    "\"SignalQuality and Attenuation were prefixed with dslLink in dslInterfaceEntry sequence, changed to dslInterface. Type DslLinkNumber was defined as 1..8, but V5 configurations already hold user port parameters for future DSL cards with 16 DSL links. This caused problems with some clients, so the definition was changed to 1..16. Revamped description of writeCommunity.\"",
    "REVISION",
    [
      "literal",
      "223230303230393139303030305a22"
    ],
    "DESCRIPTION",
    "\"The following objects were added or changed: dataPortSpeed New literal autoCrossoverAndPortSpeed(1) was added to type DataPortSpeedEnum. Warning: existing literals have changed their ordinal numbers. Revamped description, added reference. v5CardFlags Four new objects added to table v5CardTable, and v5CardETSIRelease the new type V5CardFlagSet. v5CardE1LineCode v5CardFrameFormat v5LinkAlarmStatus New literal v5LinkAlarmIdFailure(6) was added to type V5LinkAlarmStatusElem (at the end, without changing the ordinal numbers of existing literals). iadAlarmStatus New literal dcContinuity(2) was added to type IadAlarmStatusElem (at the end, without changing the ordinal numbers of existing literals). dslInterfaceSignalQuality Three new objects added to dslInterfaceTable. dslInterfaceAttenuation v5InterfaceAlarmStatus\"",
    "REVISION",
    [
      "literal",
      "223230303230383233303030305a22"
    ],
    "DESCRIPTION",
    "\"Fixed a number of typos and formatting problems. Renamed l2 group to data group. (Input from BBe).\"",
    "REVISION",
    [
      "literal",
      "223230303230373136303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed all type assignments with BITS to textual conventions (BITS is part of the OBJECT-TYPE and TEXTUAL-CONVENTION macros (for SMI v2 only), but not a ASN.1 builtin or DefinedType, and so cannot be used in a type assignment or sequence definition). The types are: AvailabilityStatusElem, DslLinkAlarmElem, DslCardAlarmStatus, IadAlarmStatusElem, DslPerformanceStatusElem, V5LinkAlarmStatusElem, V5IsdnPortAlarmStatusElem, RackAlarmStatusElem, PerfControlStatus. Added import clause for TEXTUAL-CONVENTION. Changed dataCardAvailabilityStatus in DataCardEntry from BITS to AvailabilityStatusElem. Changed spelling bit-names of AvailabilityStatusElem to agree with ASN.1 definitions in X.721. Added description for the AvailabilityStatusElem textual convention (taken from attributes, with updates). In v5CardTable and v5LccTable, changed all read-write access clauses to read-create. Improved list of references in initial comment. Added list of tools tested with this MIB to initial comment. Constrained type Priority to (0..7). Constrained dslLinkNumberOfZBits to (0..1).\"",
    "REVISION",
    [
      "literal",
      "223230303230373033303030305a22"
    ],
    "DESCRIPTION",
    "\"dslLinkAssignedTrunk was TrunkNumber in its Object-Type definition, fixed to TrunkNumberOrZero. For dslCardIPBaseAddress, v5CardIPBaseAddress and dataCardIPBaseAddress: corrected descriptions and examples to have plausible slot-numbers. ipBaseAddress adapted, with general examples.\"",
    "REVISION",
    [
      "literal",
      "223230303230363234303030305a22"
    ],
    "DESCRIPTION",
    "\"User manual realignment with syntax errors fixed, raw version.\"",
    "REVISION",
    [
      "literal",
      "223230303230363230303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed all ...IPAddressPrefix variable names to ...IPBaseAddress (dslCard, v5Card, dataCard, pegasusSystem. Changed the variable in pegasusSystem from DisplayString to IpAddress, to agree with other variables. Renamed dataCardAlarmStatus to rackAlarmStatus (also renamed the associated BITS type to RackAlarmStatusElem). Moved to pegasusSystem. Renamed dslLinkAssociatedTrunk to dslLinkAssignedTrunk, to realign with PEMClient. Eliminated type DataPortNumber, used TrunkNumber in its place. Also created type TrunkNumberOrZero, to allow reference to 'no trunk'. Renamed ...ProgramVersion to ...FirmwareVersion: dslCard, dslCardM16, iad, v5Card, dataCard. Removed dataPortVLAN (and its type VLanId): is automatically computed as part of the enhanced switching configuration. For future general VLAN switching, it will be configured through standard MIBs. Removed FilterBroadcast and FilterUnknown for both dslLink and dataPort: present in the devices, but not in the PEMClient. It was not clear if these are useful, and according to PSt it was decided to 'hide' them. Removed special(4) from DslLinkLoopEnum - no longer supported.\"",
    "REVISION",
    [
      "literal",
      "223230303230363037303030305a22"
    ],
    "DESCRIPTION",
    "\"Removed ProceduralStatus and its enumeration type from all three cards and IAD. Fixed spelling of 'v5LccIsProteced' to 'v5LccIsProtected'. Improved various descriptions.\"",
    "REVISION",
    [
      "literal",
      "223230303230353232303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed Gauge32 in perfData to Integer32, removed import for Gauge32. Added description for v5CardRowStatus.\"",
    "REVISION",
    [
      "literal",
      "223230303230353130303030305a22"
    ],
    "DESCRIPTION",
    "\"Improved descriptions for dslLink{DataRate,LinkRate,NumberOfBRA} and dslLinkDynamicSlotAllocation. Added 6 remaining objects for SNMP configuration to group pegasusSystem (read/write/trapCommunity, agentPort, authRespEnabled, trapDestination). Improved description of objects in perf group. DslCard, dataCard: removed AdminState, renumbered attributes contiguously. v5Lcc: renumbered objects contiguously, starting at 1. v5Interface: added RowStatus, changed all read-write objects to read-create, renumbered objects contigously, starting at 1. v5Link: added RowStatus, changed all read-write objects to read-create. iad: removed AdminState, renumbered attributes contiguously.\"",
    "REVISION",
    [
      "literal",
      "223230303230343235303030305a22"
    ],
    "DESCRIPTION",
    "\"Added group for performance history of V5 links and DSL interfaces. Added description for dslLinkNumberOfBRA, dslLinkDataRate, and dslLinkLineRate.\"",
    "REVISION",
    [
      "literal",
      "223230303230343136303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed numbering scheme. { schmidtelecom 1 } is now reserved for a centralized registry, and the pegasusMibModule is { schmidtelecom 2 }. All groups and objects in this and other Pegasus MIBs are below pegasusMibModule.\"",
    "REVISION",
    [
      "literal",
      "223230303230343033303030305a22"
    ],
    "DESCRIPTION",
    "\"v5CardTable and V5LccTable (LogCommChan) now have a RowStatus. For v5CardTable, this controls provisioning mode, but it does not yet support creation. For v5LccTable, it controls verification of the v5LccPccV5LinkNumber and and v5LccPccTimeslot columns, which define the Pcc (PhysCommChan) (i.e. the RowStatus supports transactions on these values). Again, creation is not yet supported for v5LccTable. The new object mibRevision holds the revision number of the MIB with which the agent was compiled.\"",
    "REVISION",
    [
      "literal",
      "223230303230333139303030305a22"
    ],
    "DESCRIPTION",
    "\"Added missing import of DisplayString. Changed definitions of dslInterface counter values to Counter32 consistently. Added one missing variable to V5IsdnPortEntry sequence.\"",
    "REVISION",
    [
      "literal",
      "223230303230333134303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial comments updated and moved to the module description, where they are more useful for typical browsers.\"",
    "REVISION",
    [
      "literal",
      "223230303230333031303030305a22"
    ],
    "DESCRIPTION",
    "\"Added PegasusSystem.\"",
    "REVISION",
    [
      "literal",
      "223230303230323238303030305a22"
    ],
    "DESCRIPTION",
    "\"Removed dslInterfaceIsRestartEnabled. Renumbered dslInterfaceEntry and dslLinkEntry columns to start with one and form a compact sequence.\"",
    "REVISION",
    [
      "literal",
      "223230303230323138303030305a22"
    ],
    "DESCRIPTION",
    "\"Added initial comment with overview and additional hints. Corrected spelling of CommStateEnum literals to comply with SNMPv2 (dashes were replaced by mixed-case spelling). Added VLAN support (DSL link and data card port). Presently only for enhanced mode, transparent and VLAN modes to come. Removed some VLAN related definitions which are not yet used.\"",
    "REVISION",
    [
      "literal",
      "223230303230323134303030305a22"
    ],
    "DESCRIPTION",
    "\"Added definitions for data switch and data switch port.\"",
    "REVISION",
    [
      "literal",
      "223230303230313235303030305a22"
    ],
    "DESCRIPTION",
    "\"Added object-type definition of v5IsdnPortAlarmStatus. Renumbered remaining objects.\"",
    "REVISION",
    [
      "literal",
      "223230303230313233303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed all occurrences of NetworkAddress to IpAddress (imported from SNMPv2-SMI). NetworkAddress was in SNMPv1, but was replaced by IpAddress for SNMPv2. Corrected dataCardVLANMode to SYNTAX TruthValue - it erronously used NetworkAddress. Correct the year on the previous revision clause.\"",
    "REVISION",
    [
      "literal",
      "223230303031323231303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial revision.\"",
    "::=",
    "{",
    "schmidtelecom",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200412170000Z"
    ],
    [
      "ORGANIZATION",
      "Schmid Telecom, Zurich"
    ],
    [
      "CONTACT-INFO",
      "Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch"
    ],
    [
      "DESCRIPTION",
      "This MIB applies to the PEGASUS SDSL product manufactured by Schmid Telecom Zurich. The MIB is modelled after the PEM management model, so object hierarchy and individual variables agree with the PEM client. The overall structure is five groups, one for each of DSL, V5 and Data cards, one with global parameters for the whole rack, and finally one group for performance history measurement. The DSL group contains four tables: - dslCardTable one entry for each DSL card (line card) configured. - dslLinkTable one entry for each DSL link. - dslInterfaceTable one entry per DSL interface, i.e. two per DSL link. - iadTable one entry per DSL link. - dslLinkCosTable one entry per DSL link. The V5 group contains five tables: - v5CardTable one entry for each V5 card configured. - v5LinkTable one entry for each V5 link. - v5InterfaceTable one entry for each V5 interface. - v5IsdnPortTable one entry per ISDN User Port (S0 interface on IAD). - v5LccTable one entry per Logical Communication Channel. The data switch group contains two tables: - dataCardTable one entry per data card (normally one) - dataPortTable one entry per trunk interface. The Pegasus System group contains individual variables related to the rack as a whole. The perf group for performance histories contains two tables and one extra variable: - perfSweeperCyclePeriod how soon are unused perfDataTable entries cleared - perfControlTable configuration of performance history monitoring - perfDataTable performance history registers Note - Notification definitions are singled out to their own MIB, to allow for alternative sets of notification styles. - Tables in this MIB are indexed hierarchically with physical attributes. E.g. all cards are indexed by the slot number. DSL links are indexed by two variables: first the slot number of the DSL card which carries the link, then the number of the link within that card. - Unlike the PEM client, this MIB does not model V5 Physical Communication Channels explicitely. They have no interesting variables of their own. Rather, the user allots a range of these objects through the V5 link configuration, and then maps the Logical Communication Channels to them (using indexes within the alloted range, of course). These objects are then created, deleted and managed under the hood. - V5 interfaces are logical entities, unlike DSL interfaces. - ISDN user ports are physically part of the IAD, and are indexed by DSL attributes. Their configuration, though, belongs to V5, so the user port tables are in the V5 group, not in the DSL group."
    ],
    [
      "Revisions",
      [
        [
          "200412170000Z",
          [
            "DESCRIPTION",
            "A new table dslLinkCosTable has been added to the dsl branch to allow the configuration of the Class of Service (COS) attributes. Each row within this table corresponds to a DSL link. Besides, some missing type and variable descriptions have been added."
          ]
        ],
        [
          "200406140000Z",
          [
            "DESCRIPTION",
            "Line identifiers are have been added for ISDN user ports and V5 links."
          ]
        ],
        [
          "200404080000Z",
          [
            "DESCRIPTION",
            "Maximum size of dslLinkAddress and trapDestination have been increased."
          ]
        ],
        [
          "200312110000Z",
          [
            "DESCRIPTION",
            "Improved the description of DslLinkLoopEnum. The variables v5IsdnPortActiveLoop and authRespEnabled are now obsolete. The agent never sends an error message if the request contains a wrong community string."
          ]
        ],
        [
          "200310300000Z",
          [
            "DESCRIPTION",
            "Corrected the value range of perfSweepCyclePeriod. The new maximum value is 604800 seconds (1 week)."
          ]
        ],
        [
          "200310240000Z",
          [
            "DESCRIPTION",
            "Declared perfControlEffectiveUpdatePeriod as obsolete. The definition would be now redundant to perfControlUpdatePeriod. The behaviour of v5LccPccV5LinkNumber/v5LccPccTimeslot has been modified. The assignment of a PCC becomes active after both attributes have been set. To erase the PCC, only one of these attributes has to be set to 0. Write access is allowed for RowStatus active now. The comments of attributes and table habe been aapted."
          ]
        ],
        [
          "200310020000Z",
          [
            "DESCRIPTION",
            "Declared hwAdaptionPolicy as obsolete. The definition of DataPortSpeedEnum and DataPortFlowConrtolEnum has been moved within the MIB file to make possible the compilation without errors using the MG-Soft MIB Compiles. This revision of the MIB is compatible with the preceeding revision."
          ]
        ],
        [
          "200303140000Z",
          [
            "DESCRIPTION",
            "Deleted all IP base address objects: dslCardIPBaseAddress, dataCardIPBaseAddress, and v5CardIPBaseAddress. The base address of a card can no longer be set through Pegasus Management, but only through the CLI on the card itself. The remaining objects were renumbered to keep the numbering compact, so this revision of the MIB is again NOT COMPATIBLE with preceeding revisions! Changed the type of perfControlIndex and perfDataIndex from INTEGER to Integer32, with range (1..2147483647), which is the set of positive values possible for an Integer32. This change is rather formal (Integer32 is indistinguishable from INTEGER, as SNMPv2-SMI puts it, that is, its serialisation is identical to INTEGER), but it makes certain parsers happy. In fact, the value is always chosen by the client, and the agent gladly takes what it gets - including 0 and negative values."
          ]
        ],
        [
          "200303110000Z",
          [
            "DESCRIPTION",
            "Deleted all config version objects: dslCardConfigVersion, v5CardConfigVersion, and dataCardConfigVersion. These objects were never really useful for customers, and so have been removed. Objects following them were renumbered, so this revision of the MIB is NOT COMPATIBLE with preceeding revisions! Added new literals at end of DataPortSpeedEnum and DataPortFlowControlEnum to convey that the value of a (read-only) status variable is currently unknown (for example because a sub-device like the Iad cannot be queried because is not connected). Added four new objects to the Iad table, to describe configuration and corresponding status of the Ethernet port on the Iad. This was mandated by the Iad Rev. B, which can control its Ethernet port and also report its status. For the older Iad Rev. B, control and status of the Ethernet port are not available, and the new objects will read with fixed values. The objects are: iadEthPortSpeed, iadEthCurrentPortSpeed, iadEthFlowControl, iadEthCurrentFlowControl."
          ]
        ],
        [
          "200210090000Z",
          [
            "DESCRIPTION",
            "SignalQuality and Attenuation were prefixed with dslLink in dslInterfaceEntry sequence, changed to dslInterface. Type DslLinkNumber was defined as 1..8, but V5 configurations already hold user port parameters for future DSL cards with 16 DSL links. This caused problems with some clients, so the definition was changed to 1..16. Revamped description of writeCommunity."
          ]
        ],
        [
          "200209190000Z",
          [
            "DESCRIPTION",
            "The following objects were added or changed: dataPortSpeed New literal autoCrossoverAndPortSpeed(1) was added to type DataPortSpeedEnum. Warning: existing literals have changed their ordinal numbers. Revamped description, added reference. v5CardFlags Four new objects added to table v5CardTable, and v5CardETSIRelease the new type V5CardFlagSet. v5CardE1LineCode v5CardFrameFormat v5LinkAlarmStatus New literal v5LinkAlarmIdFailure(6) was added to type V5LinkAlarmStatusElem (at the end, without changing the ordinal numbers of existing literals). iadAlarmStatus New literal dcContinuity(2) was added to type IadAlarmStatusElem (at the end, without changing the ordinal numbers of existing literals). dslInterfaceSignalQuality Three new objects added to dslInterfaceTable. dslInterfaceAttenuation v5InterfaceAlarmStatus"
          ]
        ],
        [
          "200208230000Z",
          [
            "DESCRIPTION",
            "Fixed a number of typos and formatting problems. Renamed l2 group to data group. (Input from BBe)."
          ]
        ],
        [
          "200207160000Z",
          [
            "DESCRIPTION",
            "Changed all type assignments with BITS to textual conventions (BITS is part of the OBJECT-TYPE and TEXTUAL-CONVENTION macros (for SMI v2 only), but not a ASN.1 builtin or DefinedType, and so cannot be used in a type assignment or sequence definition). The types are: AvailabilityStatusElem, DslLinkAlarmElem, DslCardAlarmStatus, IadAlarmStatusElem, DslPerformanceStatusElem, V5LinkAlarmStatusElem, V5IsdnPortAlarmStatusElem, RackAlarmStatusElem, PerfControlStatus. Added import clause for TEXTUAL-CONVENTION. Changed dataCardAvailabilityStatus in DataCardEntry from BITS to AvailabilityStatusElem. Changed spelling bit-names of AvailabilityStatusElem to agree with ASN.1 definitions in X.721. Added description for the AvailabilityStatusElem textual convention (taken from attributes, with updates). In v5CardTable and v5LccTable, changed all read-write access clauses to read-create. Improved list of references in initial comment. Added list of tools tested with this MIB to initial comment. Constrained type Priority to (0..7). Constrained dslLinkNumberOfZBits to (0..1)."
          ]
        ],
        [
          "200207030000Z",
          [
            "DESCRIPTION",
            "dslLinkAssignedTrunk was TrunkNumber in its Object-Type definition, fixed to TrunkNumberOrZero. For dslCardIPBaseAddress, v5CardIPBaseAddress and dataCardIPBaseAddress: corrected descriptions and examples to have plausible slot-numbers. ipBaseAddress adapted, with general examples."
          ]
        ],
        [
          "200206240000Z",
          [
            "DESCRIPTION",
            "User manual realignment with syntax errors fixed, raw version."
          ]
        ],
        [
          "200206200000Z",
          [
            "DESCRIPTION",
            "Changed all ...IPAddressPrefix variable names to ...IPBaseAddress (dslCard, v5Card, dataCard, pegasusSystem. Changed the variable in pegasusSystem from DisplayString to IpAddress, to agree with other variables. Renamed dataCardAlarmStatus to rackAlarmStatus (also renamed the associated BITS type to RackAlarmStatusElem). Moved to pegasusSystem. Renamed dslLinkAssociatedTrunk to dslLinkAssignedTrunk, to realign with PEMClient. Eliminated type DataPortNumber, used TrunkNumber in its place. Also created type TrunkNumberOrZero, to allow reference to 'no trunk'. Renamed ...ProgramVersion to ...FirmwareVersion: dslCard, dslCardM16, iad, v5Card, dataCard. Removed dataPortVLAN (and its type VLanId): is automatically computed as part of the enhanced switching configuration. For future general VLAN switching, it will be configured through standard MIBs. Removed FilterBroadcast and FilterUnknown for both dslLink and dataPort: present in the devices, but not in the PEMClient. It was not clear if these are useful, and according to PSt it was decided to 'hide' them. Removed special(4) from DslLinkLoopEnum - no longer supported."
          ]
        ],
        [
          "200206070000Z",
          [
            "DESCRIPTION",
            "Removed ProceduralStatus and its enumeration type from all three cards and IAD. Fixed spelling of 'v5LccIsProteced' to 'v5LccIsProtected'. Improved various descriptions."
          ]
        ],
        [
          "200205220000Z",
          [
            "DESCRIPTION",
            "Changed Gauge32 in perfData to Integer32, removed import for Gauge32. Added description for v5CardRowStatus."
          ]
        ],
        [
          "200205100000Z",
          [
            "DESCRIPTION",
            "Improved descriptions for dslLink{DataRate,LinkRate,NumberOfBRA} and dslLinkDynamicSlotAllocation. Added 6 remaining objects for SNMP configuration to group pegasusSystem (read/write/trapCommunity, agentPort, authRespEnabled, trapDestination). Improved description of objects in perf group. DslCard, dataCard: removed AdminState, renumbered attributes contiguously. v5Lcc: renumbered objects contiguously, starting at 1. v5Interface: added RowStatus, changed all read-write objects to read-create, renumbered objects contigously, starting at 1. v5Link: added RowStatus, changed all read-write objects to read-create. iad: removed AdminState, renumbered attributes contiguously."
          ]
        ],
        [
          "200204250000Z",
          [
            "DESCRIPTION",
            "Added group for performance history of V5 links and DSL interfaces. Added description for dslLinkNumberOfBRA, dslLinkDataRate, and dslLinkLineRate."
          ]
        ],
        [
          "200204160000Z",
          [
            "DESCRIPTION",
            "Changed numbering scheme. { schmidtelecom 1 } is now reserved for a centralized registry, and the pegasusMibModule is { schmidtelecom 2 }. All groups and objects in this and other Pegasus MIBs are below pegasusMibModule."
          ]
        ],
        [
          "200204030000Z",
          [
            "DESCRIPTION",
            "v5CardTable and V5LccTable (LogCommChan) now have a RowStatus. For v5CardTable, this controls provisioning mode, but it does not yet support creation. For v5LccTable, it controls verification of the v5LccPccV5LinkNumber and and v5LccPccTimeslot columns, which define the Pcc (PhysCommChan) (i.e. the RowStatus supports transactions on these values). Again, creation is not yet supported for v5LccTable. The new object mibRevision holds the revision number of the MIB with which the agent was compiled."
          ]
        ],
        [
          "200203190000Z",
          [
            "DESCRIPTION",
            "Added missing import of DisplayString. Changed definitions of dslInterface counter values to Counter32 consistently. Added one missing variable to V5IsdnPortEntry sequence."
          ]
        ],
        [
          "200203140000Z",
          [
            "DESCRIPTION",
            "Initial comments updated and moved to the module description, where they are more useful for typical browsers."
          ]
        ],
        [
          "200203010000Z",
          [
            "DESCRIPTION",
            "Added PegasusSystem."
          ]
        ],
        [
          "200202280000Z",
          [
            "DESCRIPTION",
            "Removed dslInterfaceIsRestartEnabled. Renumbered dslInterfaceEntry and dslLinkEntry columns to start with one and form a compact sequence."
          ]
        ],
        [
          "200202180000Z",
          [
            "DESCRIPTION",
            "Added initial comment with overview and additional hints. Corrected spelling of CommStateEnum literals to comply with SNMPv2 (dashes were replaced by mixed-case spelling). Added VLAN support (DSL link and data card port). Presently only for enhanced mode, transparent and VLAN modes to come. Removed some VLAN related definitions which are not yet used."
          ]
        ],
        [
          "200202140000Z",
          [
            "DESCRIPTION",
            "Added definitions for data switch and data switch port."
          ]
        ],
        [
          "200201250000Z",
          [
            "DESCRIPTION",
            "Added object-type definition of v5IsdnPortAlarmStatus. Renumbered remaining objects."
          ]
        ],
        [
          "200201230000Z",
          [
            "DESCRIPTION",
            "Changed all occurrences of NetworkAddress to IpAddress (imported from SNMPv2-SMI). NetworkAddress was in SNMPv1, but was replaced by IpAddress for SNMPv2. Corrected dataCardVLANMode to SYNTAX TruthValue - it erronously used NetworkAddress. Correct the year on the previous revision clause."
          ]
        ],
        [
          "200012210000Z",
          [
            "DESCRIPTION",
            "Initial revision."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6368)

Poltera Gian Lucas

Direct children (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6368.2.1 dsl571
1.3.6.1.4.1.6368.2.2 v5573
1.3.6.1.4.1.6368.2.3 data220
1.3.6.1.4.1.6368.2.4 pegasusSystem2222
1.3.6.1.4.1.6368.2.5 pegasusLeanTrapModule211
1.3.6.1.4.1.6368.2.7 perf318
1.3.6.1.4.1.6368.2.8 pegasusSdhMibModule663