Description:
|
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 explicitly. 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."
-- Revisions deleted.
REVISION "200012210000Z" -- 21 Dec, 2001
DESCRIPTION
"Initial revision."
|
|
iso(1)
dsl(1)
