PEGASUS-MIB
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.
Main OID:
pegasusMibModule.1.3.6.1.4.1.6368.2
211
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
211 total| Object Name |
|---|
schmidtelecom OBJECT IDENTIFIER .1.3.6.1.4.1.6368 |
pegasusMibModuleThis 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. MODULE-IDENTITY .1.3.6.1.4.1.6368.2 |
dsl OBJECT IDENTIFIER .1.3.6.1.4.1.6368.2.1 |
dslCardTableA table containing line card specific information. SEQUENCE OF DslCardEntry .1.3.6.1.4.1.6368.2.1.1 |
dslCardEntryRow and index definition for line card table. DslCardEntry .1.3.6.1.4.1.6368.2.1.1.1 |
dslCardSlotNumberSlot number for line card. DslSlotNumber .1.3.6.1.4.1.6368.2.1.1.1.1 |
dslCardAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.1.1.1.2 |
dslCardHardwareVersionHardware version of the Line card. This is also called CHM-number (it always starts with the letters 'CHM'). Example: CHM40510WA0A2. The number '405' after the 'CHM' identifies the card as a line card.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.3 |
dslCardManufacturerName of company which manufactured this line card/ltu.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.4 |
dslCardNameUser defined ame of line card.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.5 |
dslCardOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.1.1.1.6 |
dslCardFirmwareVersionVersion number and build date of the firmware running on the line card. This applies to the PPC part, the M16 firmware part has its own version attribute, dslCardM16FirmwareVersion. Example: '1.3 20020607 16:34' The format is 'major.minor YYYYMMDD hh:mm', where the fields are: major Major and minor version numbers, separated by a dot. Take at minor most 5 characters together, including the space. Both major and minor consist of digits only. YYYYMMDD Date (year YYYY, month MM 1-12 and day DD 1-31) of firmware build. Preceded and followed by exactly one space to separate it from the version numbers and time. hh:mm Time (hour hh 0-23 and minute mm 0-59) of firmware build.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.7 |
dslCardSerialNumberSerial number of the line card. Also called HM-number, as it always starts with 'HM'. Example: HMVSS014810294.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.8 |
dslCardCommStateThe Management Comm State indicates the state of the management connection between the PEM Server and the line card. disconnected No connection has been established. init A connection has freshly been established on the underlying protocol, but no management information has been transmitted so far. identification The connected device is being identified. check hardware The connected hardware is compared to the one stored in the configuration. hardware adaptation If the configured and the existing device do not match, an adoption is made. The behaviour in this case can be configured with the 'HW Adaptation Policy' option. check program version The program version of the connected hardware is compared to the one stored in the configuration. check config version The configuration version of the connected hardware is compared to the one stored in the configuration. download config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Device', the configuration is downloaded from the device to the PEM Server. upload config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Server', the configuration is uploaded from the PEM Server to the device. status synch The values of the status properties are being synchronised. resetting The device is resetting. inactive The device is connected, but it is inactive, that is not operational. This may be due to a hardware mismatch. active The management connection between the device and the PEM Server is fully established and the device is active.ro CommStateEnum .1.3.6.1.4.1.6368.2.1.1.1.9 |
dslCardAlarmStatusAlarm status of the line card. Bits assigned as follows: bit 0 intercom The intercom line between the PPC and M16 has failed.ro DslCardAlarmStatus .1.3.6.1.4.1.6368.2.1.1.1.10 |
dslCardM16FirmwareVersionVersion number and build date of the firmware running on the line card. This applies to the M16 part, the PPC firmware part has its own version attribute, dslCardFirmwareVersion. Example: '1.3 20020607 16:34' The format is 'major.minor YYYYMMDD hh:mm', where the fields are: major Major and minor version numbers, separated by a dot. Take at minor most 5 characters together, including the space. Both major and minor consist of digits only. YYYYMMDD Date (year YYYY, month MM 1-12 and day DD 1-31) of firmware build. Preceded and followed by exactly one space to separate it from the version numbers and time. hh:mm Time (hour hh 0-23 and minute mm 0-59) of firmware build.ro DisplayString .1.3.6.1.4.1.6368.2.1.1.1.11 |
dslLinkTableA table containing dsl link specific information. SEQUENCE OF DslLinkEntry .1.3.6.1.4.1.6368.2.1.2 |
dslLinkEntryInformation about a particular dsl link. DslLinkEntry .1.3.6.1.4.1.6368.2.1.2.1 |
dslLinkNumberNumber 1-8 of link on line card. DslLinkNumber .1.3.6.1.4.1.6368.2.1.2.1.1 |
dslLinkActiveLoopLoop back (test) setup currently active. Disconnect the DSL link before activating the maintenance loop on the LTU (loop1).rw DslLinkLoopEnum .1.3.6.1.4.1.6368.2.1.2.1.2 |
dslLinkAddressCustomer address stored in configuration file of agent.rw DisplayString .1.3.6.1.4.1.6368.2.1.2.1.3 |
dslLinkAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.1.2.1.4 |
dslLinkAlarmStatusAlarms on the link. Bit assignments as follows: Bit 0 Configuration Alarm present on link. Some configuration attribute is invalid. Bit 1 User Service Alarm present on link. This could be for example the IAD being locked (admin-state), or a mis- configuration which keeps the LTU-NTU from operating.ro DslLinkAlarmElem .1.3.6.1.4.1.6368.2.1.2.1.5 |
dslLinkAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.1.2.1.6 |
dslLinkContactA contact person, address or phone number.rw DisplayString .1.3.6.1.4.1.6368.2.1.2.1.7 |
dslLinkCustomerIdAn identification number which has been assigned to this customer.rw DisplayString .1.3.6.1.4.1.6368.2.1.2.1.8 |
dslLinkDynamicSlotAllocationIf set to true(1), the link allows timeslots reserved for voice but currently unused for usage by data. This can improve utilization of the link by increasing the effective data rate. If set to false(2), reserved and unused voice timeslots are not released for data usage.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.1.2.1.9 |
dslLinkIsRemotePowerLTU puts dc supply voltage onto link. IAD uses this if local power fails.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.1.2.1.10 |
dslLinkLineRateNumber of 64Kbit timeslots per second. The signal on the DSL link is structured as 166 2/3 frames with 48 blocks each, for a total of 8000 blocks per second. Each block contains 3 to 36 bytes (also called timeslots), as configured by this object. The bit rate of the DSL link is derived from this value. Individual timeslots can be used for data, for voice, or for voice related signalling data (D-channels). The number of data and voice timeslots is configured with dslLinkDataRate and dslLinkNumberOfBRA. The value of this variable cannot be set outside the range of 3..36, inclusive. It should be chosen such that the following conditions hold: if dslLinkNumberOfBRA is zero dslLinkLineRate >= dslLinkDataRate if dslLinkNumberOfBRA is not zero dslLinkLineRate >= dslLinkDataRate + 2*dslLinkNumberOfBRA + 1 If the value violates this condition, the DSL link raises a 'configuration' alarm.rw INTEGER .1.3.6.1.4.1.6368.2.1.2.1.11 |
dslLinkDataRateNumber of timeslots per block reserved for data. The value of this object cannot be set outside of the range 0..36, inclusive. It should be chosen such that the following conditions hold: if dslLinkNumberOfBRA is zero dslLinkDataRate <= dslLinkLineRate if dslLinkNumberOfBRA is not zero dslLinkDataRate <= dslLinkLineRate - 2*dslLinkNumberOfBRA - 1 If the value violates this condition, the DSL link raises a 'configuration' alarm. The value of this object gives the guaranteed capacity available for data. If dslLinkDynamicSlotAllocation is true(1), the effective data rate may be higher.rw INTEGER .1.3.6.1.4.1.6368.2.1.2.1.12 |
dslLinkNameUser defined name of the DSL link.rw DisplayString .1.3.6.1.4.1.6368.2.1.2.1.13 |
dslLinkNotesNotes stored in the configuration file of the agent.rw DisplayString .1.3.6.1.4.1.6368.2.1.2.1.14 |
dslLinkNumberOfBRANumber of basic rate interfaces on the IAD for which capacity is reserved on the DSL link. The capacity is reserved in units of timeslots, and the table below shows the number of timeslots reserved as a function of dslLinkNumberOfBRA. voice dslLinkDynamicSlotAllocation dslLinkNumberOfBRA reservation true(1) false(2) --------------------------------------------------------------- 0 0 0 0 1 3 1-3 3 2 5 1-5 5 3 7 1-7 7 4 9 1-9 9 If dslLinkNumberOfBRA is 0, no timeslots are reserved in the DSL link. If dslLinkNumberOfBRA is non-zero, one timeslot is always reserved and used for D-channel signalling. For each BRA allowed, exactly two timeslots are reserved (one each for the two B-channels of the basic rate interface). When dynamic (time)slot allocation is off, reserved timeslots are unavailable for data. If dynamic slot allocation is in effect, reserved voice timeslots are used only on demand, that is when a phone call is being made. Reserved but unused voice timeslots are then used for data, increasing the data rate. The timeslot for the D-channel is not dynamically allocated. If a D-channel is reserved, it is unavailable for data. The value of this object cannot be set outside of the range 0..4. It should be chosen such that the following conditions hold: dslLinkNumberOrBRA <= (dslLinkLineRate - dslLinkDataRate - 1) / 2 dslLinkNumberOrBRA <= number of basic rate interfaces on the IAD where the division should round towards zero. If the value violates either of these conditions, the DSL link raises a 'configuration' alarm. Note that if the IAD is not connected, the link may raise the alarm only when the IAD connects. It is allowed to set a value less than the actual number of basic rate interfaces present on the IAD.rw INTEGER .1.3.6.1.4.1.6368.2.1.2.1.15 |
dslLinkOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.1.2.1.16 |
dslLinkNumberOfZBitsNumber of Z bits on the DSL link.rw INTEGER .1.3.6.1.4.1.6368.2.1.2.1.17 |
dslLinkPSDMaskPSD (Power Spectral Density) Mask of DSL link. Asymmetric PSD offers a 5 - 10% longer DSL range. PSD symmetric is default setting. PSD asymmetric is only possible with line rates n = 32 or 36.rw DslLinkPSDMaskEnum .1.3.6.1.4.1.6368.2.1.2.1.18 |
dslLinkAssignedTrunkDetermines the data trunk (aggregate side) on which the all data traffic of this DSL Link is mapped.rw TrunkNumberOrZero .1.3.6.1.4.1.6368.2.1.2.1.19 |
dslLinkPriorityDetermines the priority according to IEEE 802.3x for data traffic coming from this DSL Link. Value range is 0 .. 7. 0 lowest priority, 7 highest priority.rw Priority .1.3.6.1.4.1.6368.2.1.2.1.20 |
iadTableIAD table. IAD is for Integrated Access Device. The IAD contains the DSL NTU, and depending on the model, ISDN Adapters, POTS Terminal Adapters (TA) and Ethernet interfaces. The IAD is also called just modem or NTU. The table contains one entry per DSL link. The entry exists even if the IAD is offline (that is disconnected). SEQUENCE OF IadEntry .1.3.6.1.4.1.6368.2.1.3 |
iadEntryCarry index for iad table. IadEntry .1.3.6.1.4.1.6368.2.1.3.1 |
iadAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.1.3.1.1 |
iadHardwareVersionHardware version of the IAD. This is also called CHM-number (it always starts with the letters 'CHM'). Example: CHM415080WAAA2. The number '415' after the 'CHM' identifies the device as an IAD.ro DisplayString .1.3.6.1.4.1.6368.2.1.3.1.2 |
iadManufacturerName of company which manufactured this IAD.ro DisplayString .1.3.6.1.4.1.6368.2.1.3.1.3 |
iadNameUser defined name of IAD.ro DisplayString .1.3.6.1.4.1.6368.2.1.3.1.4 |
iadOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.1.3.1.5 |
iadFirmwareVersionVersion number and build date of the firmware running on the IAD. Example: '1.3 20020607 16:34' The format is 'major.minor YYYYMMDD hh:mm', where the fields are: major Major and minor version numbers, separated by a dot. Take at minor most 5 characters together, including the space. Both major and minor consist of digits only. YYYYMMDD Date (year YYYY, month MM 1-12 and day DD 1-31) of firmware build. Preceded and followed by exactly one space to separate it from the version numbers and time. hh:mm Time (hour hh 0-23 and minute mm 0-59) of firmware build.ro DisplayString .1.3.6.1.4.1.6368.2.1.3.1.6 |
iadSerialNumberSerial number of the IAD. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014432064.ro DisplayString .1.3.6.1.4.1.6368.2.1.3.1.7 |
iadAlarmStatusAlarm Status of IAD. Individual alarms show that specific (usually adverse) conditions are present. Bits are assigned as follows: bit 0 powerdown The IAD has no local power. bit 1 lifeline The IAD is operating on lifeline, i.e. is taking power from the DSL line, not from the local power supply.ro IadAlarmStatusElem .1.3.6.1.4.1.6368.2.1.3.1.8 |
iadISDNPoweringState of the powering of the ISDN S-Bus port 0. no power No powering of ISDN S0 Bus at all. normal power Powering of ISDN S0 Bus, normal mode. lifeline power Lifeline mode always power Supporting normal operation and lifeline operation.rw IadISDNPoweringEnum .1.3.6.1.4.1.6368.2.1.3.1.9 |
iadPOTSPoweringDefines how the IAD powers the POTS line, i.e. the analog telephone line on the integrated TA. This feature is not reliable on older IAD models.rw IadPOTSPoweringEnum .1.3.6.1.4.1.6368.2.1.3.1.10 |
iadEthPortSpeedConfiguration of the desired speed for the IAD's Ethernet port.rw DataPortSpeedEnum .1.3.6.1.4.1.6368.2.1.3.1.11 |
iadEthCurrentPortSpeedDisplays the currently active speed of a IAD's Ethernet port.ro DataPortSpeedEnum .1.3.6.1.4.1.6368.2.1.3.1.12 |
iadEthFlowControlConfiguration of the desired flow control.rw DataPortFlowControlEnum .1.3.6.1.4.1.6368.2.1.3.1.13 |
iadEthCurrentFlowControlDisplays the currently used flow control.ro DataPortFlowControlEnum .1.3.6.1.4.1.6368.2.1.3.1.14 |
dslInterfaceTableDSL Interface table. SEQUENCE OF DslInterfaceEntry .1.3.6.1.4.1.6368.2.1.4 |
dslInterfaceEntryRow/index definition for dslInterfaceTable. DslInterfaceEntry .1.3.6.1.4.1.6368.2.1.4.1 |
dslInterfaceTypeThe type of device on which the interface sits: LTU (linecard) or Ntu (IAD, modem). DslInterfaceTypeEnum .1.3.6.1.4.1.6368.2.1.4.1.1 |
dslInterfaceAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.1.4.1.2 |
dslInterfaceOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.1.4.1.3 |
dslInterfacePerformanceStatusDisplays the current status of the DSL interfacero DslPerformanceStatusElem .1.3.6.1.4.1.6368.2.1.4.1.4 |
dslInterfacePerfControlIndexOrZeroIf the value of this variable is set to a non-zero value, there must be a row in perfControlTable with this value in perfControlIndex. The perfControlEntry thus identified controls the performance history entries in perfDataTable for the DSL interface referencing the perfControlEntry. If the value is set to zero, performance history for this interface is removed from the perfDataTable.rw INTEGER .1.3.6.1.4.1.6368.2.1.4.1.5 |
dslInterfaceSignalQualityThis object gives the signal quality, expressed as the signal-to-noise ratio (SNR) in decibels (dB). The value 127 shows that the real value is currently unavailable.ro Integer32 (-128 .. 127) UNITS "dB" .1.3.6.1.4.1.6368.2.1.4.1.6 |
dslInterfaceAttenuationThis object shows how much the signal has been weakened (attenuated) on the DSL line. It is expressed in decibels (dB) relative to the transmit power. The value -128 shows that the real value is currently not available. The value normally increases with the line length.ro Integer32 (-128 .. 127) UNITS "dB" .1.3.6.1.4.1.6368.2.1.4.1.7 |
dslLinkCosTableClass of Service (COS) table for a DSL link. The table allows to assign vlans or priorities to the queues EF (Expedited Forwarding) and AF1/AF2 (Assured Forwarding). The last queue, BE (Best Effort) gets the bandwidth that is left. queue: priority: bandwidth: EF highest configurable AF2 higher configurable AF1 lower configurable BE lowesr left-over SEQUENCE OF DslLinkCosEntry .1.3.6.1.4.1.6368.2.1.5 |
dslLinkCosEntryRow/index definition for dslLinkCosTable. DslLinkCosEntry .1.3.6.1.4.1.6368.2.1.5.1 |
dslLinkCosAvailableIf true(1), COS is supported by the LineCard.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.1.5.1.1 |
dslLinkCosEnabledEnabling and disabling of COS for the specified link.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.1.5.1.2 |
dslLinkCosClassifierConfiguration of the desired classifier. Possible values are VLAN priority and DSCP (Differentiated Services Code Point) priority.rw CosClassifierEnum .1.3.6.1.4.1.6368.2.1.5.1.3 |
dslLinkCosClassmapEFClassmap for the EF (Expedited Forwarding) queue. See description of CosClassmap for further information.rw CosClassmap .1.3.6.1.4.1.6368.2.1.5.1.4 |
dslLinkCosClassmapAF2Classmap for the AF2 (Assured Forwarding) queue. See description of CosClassmap for further information.rw CosClassmap .1.3.6.1.4.1.6368.2.1.5.1.5 |
dslLinkCosClassmapAF1Classmap for the AF1 (Assured Forwarding) queue. See description of CosClassmap for further information.rw CosClassmap .1.3.6.1.4.1.6368.2.1.5.1.6 |
dslLinkCosRateLimitEFMaximum rate in kB that the EF queue is allowed to use. Note: The sum of the maxima of EF, AF1 and AF2 queue cannot exceed the configured maximum data rate od the DSL link.rw INTEGER .1.3.6.1.4.1.6368.2.1.5.1.7 |
dslLinkCosRateLimitAF2Maximum rate in kB that the AF2 queue is allowed to use. Note: The sum of the maxima of EF, AF1 and AF2 queue cannot exceed the configured maximum data rate od the DSL link.rw INTEGER .1.3.6.1.4.1.6368.2.1.5.1.8 |
dslLinkCosRateLimitAF1Maximum rate in kB that the AF1 queue is allowed to use. Note: The sum of the maxima of EF, AF1 and AF2 queue cannot exceed the configured maximum data rate od the DSL link.rw INTEGER .1.3.6.1.4.1.6368.2.1.5.1.9 |
v5 OBJECT IDENTIFIER .1.3.6.1.4.1.6368.2.2 |
v5CardTableA table containing V5 card specific information SEQUENCE OF V5CardEntry .1.3.6.1.4.1.6368.2.2.1 |
v5CardEntryRow and index definition for V5 card table. V5CardEntry .1.3.6.1.4.1.6368.2.2.1.1 |
v5CardSlotNumberSlot number for v5 card. V5SlotNumber .1.3.6.1.4.1.6368.2.2.1.1.1 |
v5CardAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.2.1.1.2 |
v5CardAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.2.1.1.3 |
v5CardHardwareVersionHardware version of the V5 card. This is also called CHM-number (it always starts with the letters 'CHM'). Example: CHM40210WA0A2. The number '402' after the 'CHM' identifies the card as a V5 card.ro DisplayString .1.3.6.1.4.1.6368.2.2.1.1.4 |
v5CardManufacturerName of company which manufactured this V5 card.ro DisplayString .1.3.6.1.4.1.6368.2.2.1.1.5 |
v5CardNameUser defined name of the V5 card.ro DisplayString .1.3.6.1.4.1.6368.2.2.1.1.6 |
v5CardOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.2.1.1.7 |
v5CardFirmwareVersionVersion number and build date of the firmware running on the V5 card. Example: '1.3 20020607 16:34' The format is 'major.minor YYYYMMDD hh:mm', where the fields are: major Major and minor version numbers, separated by a dot. Take at minor most 5 characters together, including the space. Both major and minor consist of digits only. YYYYMMDD Date (year YYYY, month MM 1-12 and day DD 1-31) of firmware build. Preceded and followed by exactly one space to separate it from the version numbers and time. hh:mm Time (hour hh 0-23 and minute mm 0-59) of firmware build.ro DisplayString .1.3.6.1.4.1.6368.2.2.1.1.8 |
v5CardSerialNumberSerial number of the V5 card. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014532139.ro DisplayString .1.3.6.1.4.1.6368.2.2.1.1.9 |
v5CardCommStateThe Management Comm State indicates the state of the management connection between the PEM Server and the Data Card. disconnected No connection has been established. init A connection has freshly been established on the underlying protocol, but no management information has been transmitted so far. identification The connected device is being identified. check hardware The connected hardware is compared to the one stored in the configuration. hardware adaptation If the configured and the existing device do not match, an adoption is made. The behaviour in this case can be configured with the 'HW Adaptation Policy' option. check program version The program version of the connected hardware is compared to the one stored in the configura- tion. check config version The configuration version of the connected hardware is compared to the one stored in the configuration. download config If a configuration version mismatch has bee detected and the 'Config Priority' of 'PEGASUS system' is set to 'Device', the configuration is downloaded from the device to the PEM Server. upload config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Server', the configuration is uploaded from the PEM Server to the device. status synch The values of the status properties are being synchronised. resetting The device is resetting. inactive The device is connected, but it is inactive, i.e. not operational. This may be due to a hardware mismatch. active The management connection between the device and the PEM Server is fully established and the device is active.ro CommStateEnum .1.3.6.1.4.1.6368.2.2.1.1.10 |
v5CardIsProvisioningThe V5 Card is in provisioning mode. Only if this flag is true, re-configuration of the V5 Card is possible.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.1.1.11 |
v5CardClockModeClock mode of the V5 Card Master This card is the clock master. Slave This card is a clock slave.rw V5ClockModeEnum .1.3.6.1.4.1.6368.2.2.1.1.12 |
v5CardClockSource1If the card is configured to be the clock master (v5CardClockMode), this property determines the source of the clock. Values range is 1 .. 8 or external clock (from plug on front panel).rw V5ClockSourceEnum .1.3.6.1.4.1.6368.2.2.1.1.13 |
v5CardClockSource2If the card is configured to be the clock master (v5CardClockMode), this property determines the source of the clock in case clock source 1 is not available. Value range is 1 .. 8 or external clock (from plug on front panel).rw V5ClockSourceEnum .1.3.6.1.4.1.6368.2.2.1.1.14 |
v5CardProtocolVersionThe version of the V5 protocol. Can be either V5.1 or V5.2rw V5ProtocolVersionEnum .1.3.6.1.4.1.6368.2.2.1.1.15 |
v5CardRowStatusThis object allows creation and deletion of V5 card table entries. The card can only be deleted when it is disconnected. V5 cards are always created with 512 user ports. All other objects (V5 interfaces, V5 links, and log comm channels) must be created separately. If the card is deleted, all objects related to it are also deleted. To configure the card, or any object associated with it, the card must be disconnected or v5CardRowStatus must not be 'active'. Setting v5CardRowStatus to 'notInService' while the card is connected puts the card into provisioning mode. Setting v5CardRowStatus to 'active' while the card is connected commits provisioning, that is ends provisioning mode (or fails if the card finds the configuration incorrect or incomplete).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.1.1.16 |
v5CardFlagsThis object holds various flags which can be set to modify the behaviour of the V5 protocol stack.rw V5CardFlagSet .1.3.6.1.4.1.6368.2.2.1.1.17 |
v5CardETSIReleaseThe ETSI release (version) of the V5 standard used for the V5 protocol on all V5 interface of the V5 card. This must not be confused with the choice of the V5 protocol (V5.1 or V5.2).rw Enumeration .1.3.6.1.4.1.6368.2.2.1.1.18 |
v5CardE1LineCodeThe E1 line code used on all V5 links of the V5 card.rw Enumeration .1.3.6.1.4.1.6368.2.2.1.1.19 |
v5CardE1FrameFormatThe frame format of E1 frames used on all V5 links of the V5 card.rw Enumeration .1.3.6.1.4.1.6368.2.2.1.1.20 |
v5LinkTableA table containing V5 link specific information SEQUENCE OF V5LinkEntry .1.3.6.1.4.1.6368.2.2.2 |
v5LinkEntryRow and index definition for V5 link table. V5LinkEntry .1.3.6.1.4.1.6368.2.2.2.1 |
v5LinkNumberNumber of the link on the V5 card (used for table indexing). V5LinkNumber .1.3.6.1.4.1.6368.2.2.2.1.1 |
v5LinkAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.2.2.1.2 |
v5LinkAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.2.2.1.3 |
v5LinkIdV5 Link Identifier. Value range is 0 .. 255rw INTEGER .1.3.6.1.4.1.6368.2.2.2.1.4 |
v5LinkOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.2.2.1.5 |
v5LinkInterfaceIdentifies to which V5 interface this V5 link is related.rw V5InterfaceNumberOrZero .1.3.6.1.4.1.6368.2.2.2.1.6 |
v5LinkAlarmStatusAlarm status of the V5 link. Bits assigned as follows: bit 0 LOS Loss of signal bit 1 LFA Loss of frame alignment bit 2 AIS Alarm indication signal bit 3 BERH Bit error rate to high bit 4 EXTLOC Loss of external clock bit 5 RAI Remote alarm indicationro V5LinkAlarmStatusElem .1.3.6.1.4.1.6368.2.2.2.1.7 |
v5LinkTypeSpecifies the type of V5 Link Primary The primary link carries all the important V5 Protocols. Therefore it needs to have at least one Physical Communi- cation Channel on timeslot 16. There must be exactly one primary link per V5 interface. Secondary The secondary link acts as 'standby' link for the primary link; i.e. if the primary link fails, the secondary link will transport the V5 Protocols instead. Therefore it needs to have an unused PhysComm Channel on timeslot 16. If more than one links are available, there must be exactly one secondary link per V5 interface. Normal All other links are 'normal' links and do not take any predefined responsibility concerning protection mechanisms.rw V5LinkTypeEnum .1.3.6.1.4.1.6368.2.2.2.1.8 |
v5LinkNumberOfPccThe number of Physical Communication Channel (Physcommchan or PCC) configured on this V5 link. V5 links are structured as 8000 frames per second of 32 timeslots each. A timeslot can carry voice data, or alternatively signalling, e.g. synchronization data, CRC's, or D-channel data. Timeslot 0 is always used for signalling by lower level layers of E1. For higher level signalling like D-channels, additional timeslots must be explicitly allocated - these are called physcommchans. Timeslots 16, 15 and 31 are available for this purpose. So, a V5 link can have from zero to three physcommchans. Timeslots are always allocated in the order mentioned above, that is the following configurations are possible: Timeslots allocated to v5LinkNumberOfPcc higher level signalling 0 - 1 16 2 16,15 3 16,15,31 Timeslots that are not used for signalling are available for voice data. So, a link can have from 28 to 31 voice data channels.rw V5PccCount .1.3.6.1.4.1.6368.2.2.2.1.9 |
v5LinkPerfControlIndexOrZeroThe value of this variable represents the index of a row within the perfControlTable. If the value is not 0, performance data (statistics) concerning this link are captured.rw INTEGER .1.3.6.1.4.1.6368.2.2.2.1.10 |
v5LinkRowStatusRowStatis variable that allows creation and deletion of V5 links.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.2.1.11 |
v5LinkLineIdentifierAn idenifier assigned to the subscriber (customer).rw DisplayString .1.3.6.1.4.1.6368.2.2.2.1.12 |
v5InterfaceTableA table containing V5 interface specific information. Only AN side interfaces are present. SEQUENCE OF V5InterfaceEntry .1.3.6.1.4.1.6368.2.2.3 |
v5InterfaceEntryRow and index definition for V5 interface table. V5InterfaceEntry .1.3.6.1.4.1.6368.2.2.3.1 |
v5InterfaceNumberinterface number, used for table indexing V5InterfaceNumber .1.3.6.1.4.1.6368.2.2.3.1.1 |
v5InterfaceAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.2.3.1.2 |
v5InterfaceAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.2.3.1.3 |
v5InterfaceIdV5 Interface Identifier. Value range is 0 .. 16777215.rw INTEGER .1.3.6.1.4.1.6368.2.2.3.1.4 |
v5InterfaceOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.2.3.1.5 |
v5InterfaceVariantIdIndicates the V5 provisioning variant, which is currently valid. This is used to decide if the configuration is compliant with the LE. Value range is 0 .. 127.rw INTEGER .1.3.6.1.4.1.6368.2.2.3.1.6 |
v5InterfaceRowStatusVariable to create and delete V5 interfaces.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.3.1.7 |
v5InterfaceAlarmStatusDisplays the currently active alarms of the V5 interface.ro V5InterfaceAlarmSet .1.3.6.1.4.1.6368.2.2.3.1.8 |
v5LccTabletable containing all LCC (Logical Communication Channels) for a V5 interface SEQUENCE OF V5LccEntry .1.3.6.1.4.1.6368.2.2.4 |
v5LccEntryrow defintion for the v5LccTable V5LccEntry .1.3.6.1.4.1.6368.2.2.4.1 |
v5LccNumberindex of the LCC; number in the range of 1..21 V5LccNumber .1.3.6.1.4.1.6368.2.2.4.1.1 |
v5LccIsProtectedIf true, all information transported over this LCC is protected by the V5 Protection protocol (V5.2 only).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.4.1.2 |
v5LccIdUnique L3 address per Logical Communication Channel. Value range is 0 .. 65535.rw INTEGER .1.3.6.1.4.1.6368.2.2.4.1.3 |
v5LccOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.2.4.1.4 |
v5LccPccV5LinkNumberIdentify (together with v5LccPccTimeslot) the Physical Communication Channel used for the signalling data of this Logical Communication Channel.rw V5LinkNumberOrZero .1.3.6.1.4.1.6368.2.2.4.1.5 |
v5LccPccTimeslotIdentify (together with v5LccPccV5LinkNumber) the Physical Communication Channel used for the signalling data of this Logical Communication Channel. The value of this variable is a code with the following value: v5LccPccTimeslot Timeslot 0 none 1 16 2 15 3 31 A value of 0 cannot be set explicitly, and can only appear while the LCC object is being initialized. Once a non-zero value has been set (either through SNMP or by other means of management, a value of 0 can never again appear.rw V5PccNumberOrZero .1.3.6.1.4.1.6368.2.2.4.1.6 |
v5LccRowStatusThe value of this object can be active(1) in order for the value of v5LccPccV5LinkNumber or v5LccPccTimeslot to be modified. To set the PCC both attributes v5LccPccV5LinkNumber and v5LccPccTimeslot must be set before the values become active. The values become only active if v5LccPccV5LinkNumber and v5LccPccTimeslot specify an existing Physical Communication Channel on the V5 card identified by the instance of v5CardSlotNumber used to index this v5LccEntry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.4.1.7 |
v5IsdnPortTableA table containing information specific to V5 ISDN user ports, i.e. S0 interfaces on IADs. SEQUENCE OF V5IsdnPortEntry .1.3.6.1.4.1.6368.2.2.5 |
v5IsdnPortEntryRow and index definition for V5 ISDN user port table. Sometimes, user ports are numbered 0..511 (8 cards @ 16 ltus @ 4 bras/ntu), with an implicit assignment of linecard = port/(8*16). dsl link = port%(8*16)/4 bra = port%(8*16*4). V5IsdnPortEntry .1.3.6.1.4.1.6368.2.2.5.1 |
v5IsdnPortBRANumberindex number for this port INTEGER .1.3.6.1.4.1.6368.2.2.5.1.3 |
v5IsdnPortAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.2.5.1.4 |
v5IsdnPortOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.2.5.1.5 |
v5IsdnPortBlockingStatusIn the case of an unlocked/disabled status, this attribute indicates, if the disabled-state is due to local or remote reasons (ETS 300 376-1, A.2), (Definition in ETS 300 377-1) None The User Port is unblocked. Local The User Port is blocked on the Access Network side only Remote The User Port is blocked on the Local Exchange side only Both The User Port is blocked both on the AN and on the LE side.ro V5IsdnPortBlockingStatusEnum .1.3.6.1.4.1.6368.2.2.5.1.6 |
v5IsdnPortBearer1TimeslotAssigned bearer time slot number to port B1 channel. No assignment for V5.2 interfaces because the BCC protocol is used for dynamic assignment. In V5.1 the association between V5Interface and V5Link is one to one. The link associated to this user port is fully determined by the UserPort-V5Interface association. Value range is 1 .. 15 or 17 .. 31.rw V5TimeslotNumber .1.3.6.1.4.1.6368.2.2.5.1.7 |
v5IsdnPortBearer2TimeslotAssigned bearer time slot number to port B2 channel. No assignment for V5.2 interfaces because the BCC protocol is used for dynamic assignment. In V5.1 the association between V5Interface and V5Link is one to one. The link associated to this user port is fully determined by the UserPort-V5Interface association. Value range is 1 .. 15 or 17 .. 31.rw V5TimeslotNumber .1.3.6.1.4.1.6368.2.2.5.1.8 |
v5IsdnPortEnvelopeFuncAddressLayer 3 Address of this User Port. Value range is 0 .. 8175.rw V5EnvelopeFuncAddress .1.3.6.1.4.1.6368.2.2.5.1.9 |
v5IsdnPortIsActivatedLayer 1 activation statusro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.2.5.1.10 |
v5IsdnPortAlarmStatusdisplays the currently active alarms for the ISDN portro V5IsdnPortAlarmStatusElem .1.3.6.1.4.1.6368.2.2.5.1.11 |
v5IsdnPortActiveLooprwobsolete V5IsdnPortLoopEnum .1.3.6.1.4.1.6368.2.2.5.1.12 |
v5IsdnPortV5CardSlotNumberSlot number of V5 card which owns this user port configuration. Physically, user ports are on IAD devices. Logically, their configuration is part of the V5 configuration, so it is the V5 card which owns the configuration, not the DSL card. For this reason, user ports are created in the context of a V5 card, which is why the V5 card cannot be changed.ro V5SlotNumber .1.3.6.1.4.1.6368.2.2.5.1.13 |
v5IsdnPortV5InterfaceNumberThe V5 interface whose V5 links provide signalling and B channel capacity for this user port. The value zero appears only after creation. Once a non-zero value has been set here, it is no more possible to reset the value to zero.rw V5InterfaceNumberOrZero .1.3.6.1.4.1.6368.2.2.5.1.14 |
v5IsdnPortDSignallingCommChanThe ISDN Communication Path over which the D-Signalling control information of this User Port is transported.rw V5LccNumberOrZero .1.3.6.1.4.1.6368.2.2.5.1.15 |
v5IsdnPortFrameCommChanThe ISDN Communication Path over which the Frame control information of this User Port is transported.rw V5LccNumberOrZero .1.3.6.1.4.1.6368.2.2.5.1.16 |
v5IsdnPortPacketCommChanThe ISDN Communication Path over which the Packet control information of this User Port is transported.rw V5LccNumberOrZero .1.3.6.1.4.1.6368.2.2.5.1.17 |
v5IsdnPortLineIdentifierAn idenifier assigned to the subscriber (customer).rw DisplayString .1.3.6.1.4.1.6368.2.2.5.1.18 |
data OBJECT IDENTIFIER .1.3.6.1.4.1.6368.2.3 |
dataCardTableattributes concerning the data switch (slot 1) SEQUENCE OF DataCardEntry .1.3.6.1.4.1.6368.2.3.1 |
dataCardEntryentry/row within the dataCardTable DataCardEntry .1.3.6.1.4.1.6368.2.3.1.1 |
dataCardSlotNumberPosition of the slot card in the rack. DataCardSlotNumber .1.3.6.1.4.1.6368.2.3.1.1.1 |
dataCardAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.3.1.1.2 |
dataCardHardwareVersionHardware Version Number of the data card. This is also called CHM-number (it always starts with the letters 'CHM'). Example: CHM40310WA0A2. The number '403' after the 'CHM' identifies the card as a data card.ro DisplayString .1.3.6.1.4.1.6368.2.3.1.1.3 |
dataCardManufacturerManufacturer of the data card.ro DisplayString .1.3.6.1.4.1.6368.2.3.1.1.4 |
dataCardNameUser defined name of the data card.ro DisplayString .1.3.6.1.4.1.6368.2.3.1.1.5 |
dataCardOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.3.1.1.6 |
dataCardFirmwareVersionVersion number and build date of the firmware running on the data card. Example: '1.3 20020607 16:34' The format is 'major.minor YYYYMMDD hh:mm', where the fields are: major Major and minor version numbers, separated by a dot. Take at minor most 5 characters together, including the space. Both major and minor consist of digits only. YYYYMMDD Date (year YYYY, month MM 1-12 and day DD 1-31) of firmware build. Preceded and followed by exactly one space to separate it from the version numbers and time. hh:mm Time (hour hh 0-23 and minute mm 0-59) of firmware build.ro DisplayString .1.3.6.1.4.1.6368.2.3.1.1.7 |
dataCardSerialNumberSerial number of the data card. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014332080.ro DisplayString .1.3.6.1.4.1.6368.2.3.1.1.8 |
dataCardCommStateThe Management Comm State indicates the state of the management connection between the PEM Server and the Data Card. disconnected No connection has been established. init A connection has freshly been established on the underlying protocol, but no management information has been transmitted so far. identification The connected device is being identified. check hardware The connected hardware is compared to the one stored in the configuration. hardware adaptation If the configured and the existing device do not match, an adoption is made. The behaviour in this case can be configured with the 'HW Adaptation Policy' option. check program version The program version of the connected hardware is compared to the one stored in the configura- tion. check config version The configuration version of the connected hardware is compared to the one stored in the configuration. download config If a configuration version mismatch has bee detected and the 'Config Priority' of 'PEGASUS system' is set to 'Device', the configuration is downloaded from the device to the PEM Server. upload config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Server', the configuration is uploaded from the PEM Server to the device. status synch The values of the status properties are being synchronised. resetting The device is resetting. inactive The device is connected, but it is inactive, i.e. not operational. This may be due to a hardware mismatch. active The management connection between the device and the PEM Server is fully established and the device is active.ro CommStateEnum .1.3.6.1.4.1.6368.2.3.1.1.9 |
dataCardVLANModeIf true(1), enhanced switching (trunk assignment according to setting in DSL link configuration) is enabled. Otherwise transparent switching (any DSL link to any trunk) is used.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.3.1.1.10 |
dataPortTableThe table contains an entry for each Ethernet trunk on the data switch (card). SEQUENCE OF DataPortEntry .1.3.6.1.4.1.6368.2.3.2 |
dataPortEntryentry within the dataPortTable DataPortEntry .1.3.6.1.4.1.6368.2.3.2.1 |
dataPortNumberindex of the (ethernet) trunk on the data switch TrunkNumber .1.3.6.1.4.1.6368.2.3.2.1.1 |
dataPortAdminStateThis configuration attribute allows the administrator to enable or disable the operability of a device. unlocked The device is administratively permitted to perform services for its users. locked The device is administratively prohibited from performing services for users.rw AdminStateEnum .1.3.6.1.4.1.6368.2.3.2.1.2 |
dataPortOperStateThe operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.ro OperStateEnum .1.3.6.1.4.1.6368.2.3.2.1.3 |
dataPortAvailabilityStatusThe availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.ro AvailabilityStatusElem .1.3.6.1.4.1.6368.2.3.2.1.4 |
dataPortSpeedThis object allows specification of options for three areas: crossover Normally, DTE and hub sockets are wired such that they can connect with a straight-through cable, that is the hub has RX and TX circuits swapped (it has internal crossover). If a DTE must be connected directly to another DTE (or hub port to a port on another hub), a crossover cable must be used. The data card trunk interfaces have an automatic crossover function, which turns on or off crossover. Any sort of cable can then be used to connect to any sort of device (DTE or hub). duplex mode If duplex mode is full duplex, transmission is allowed while data are received. With half duplex, transmission must wait until the receiver is idle. speed The port can operate in 10 or 100 MBits per second. The values possible for this variable are: autoCrossoverAndPortSpeed(1) Allows the port to negotiate speed, duplex mode, and to enable or disable the internal crossover function. autoNegotiationPortSpeed(2) Allows the port to negotiate speed and and duplex mode. Internal crossover is on - a straight-through cable is needed to connect to a DTE (PC), a crossover cable is needed to connect to a repeater or hub. base100TFullDuplex(3) Speed is set to 100 MBits per second, with full duplex. Internal crossover is on. base100THalfDuplex(4) Speed is set to 100 MBits per second, with half duplex. Internal crossover is on. base10TFullDuplex(5) Speed is set to 10 MBits per second, with full duplex. Internal crossover is on. base10THalfDuplex(6) Speed is set to 10 MBits per second, with half duplex. Internal crossover is on.rw DataPortSpeedEnum .1.3.6.1.4.1.6368.2.3.2.1.5 |
dataPortFlowControlSetting of Flow Control according to IEEE 802.3x. Auto Enables auto negotiation of IEEE 802.3x flow control when in full-duplex mode. On Force flow control operation Off No flow control.rw DataPortFlowControlEnum .1.3.6.1.4.1.6368.2.3.2.1.6 |
pegasusSystem OBJECT IDENTIFIER .1.3.6.1.4.1.6368.2.4 |
autoPersistDelayIf Auto Persist Config is enabled, this is the delay (in seconds) after which the configuration is persisted on the PEM Server. The default value is: 10s.rw INTEGER .1.3.6.1.4.1.6368.2.4.1 |
autoPersistEnabledDetermines, whether configuration changes are made persistent automatically (a certain interval after the last change of a configuration attribute) or explicitly by a corresponding message from the PEM Client.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.2 |
configPriorityDetermines, which configuration is used in case of a configuration mismatch. Possible values: Server or device. Device: The device config is used (replaces server config). Server: The server config is used (replaces device config)rw ConfigPriorityEnum .1.3.6.1.4.1.6368.2.4.3 |
hwAdaptionPolicyIn case of a hardware mismatch (the configured device does not match with the one detected in the rack): shall the PEM Server be reconfigured with the new device or shall the device be taken out of operation? Possible Values: Server or Device. Device: The device config is used (replaces server config). Server: The server config is used (replaces device config)rwobsolete HWAdaptionPolicyEnum .1.3.6.1.4.1.6368.2.4.4 |
ipBaseAddressBase address for the computation of the IP addresses for the management interfaces of the cards. When the PEMServer wants to connect to a card in the rack, it computes the card IP address from ipBaseAddress, the slot number of the card, and the systemNumber of the rack (also in pegasusSystem), as follows: the slot number is added to the last byte of ipBaseAddress, modulo 256, and the systemNumber is added to the next to last byte of ipBaseAddress, again modulo 256. Example 1 2 3 iPBaseAddress |192.168. 0. 0|192.168.244.231|192.168. 0. 0 systemNumber | +4 | +4 | +4 slot number | +1| +3| +5 sum | 4 1| 4 234| 4 5 sum modulo 256 | 4 1| 4 234| 4 5 Resulting mgmt IP-# |192.168. 4. 1|192.168.248.234|192.168. 4. 5 The slot cards compute their own management interface IP addresses in a similar way, using their own ip base addresses. These base addresses are not visible through the PEM Client or SNMP. To read or change them on a card, the CLI must be used. All slot cards within a PEGASUS system must have the management IP addresses in the same network in order to communicate with each other. They must then have the same base address (with the exception of biasing, as explained below). The base addresses of all cards are usually chosen such that the management IP addresses end up in a non-routable (private) networks. Biasing: cards read slot and rack numbers through dedicated pins on their backplane plugs. If such a pin is damaged, cards read bad numbers and compute bad (possibly conflicting) IP addresses. In this case, the CLI can be used to set the base address such that the resulting address is still correct.rw IpAddress .1.3.6.1.4.1.6368.2.4.5 |
javaRuntimeVersionVersion of the installed Java Runtime.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.6 |
javaVMNameName of the installed Java virtual machine.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.7 |
javaVMVersionVersion of the installed Java virtual machine on the work-station.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.8 |
mgmtIPAddressThe IP Address of the PEGASUS system through which the PEM Server is accessible.ro IpAddress .1.3.6.1.4.1.6368.2.4.9 |
osArchitectureDisplays information about the operating system where the PEM server is running.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.11 |
osNameAndVersionName and version of the operating system that is running on the workstation where the PEM server is running.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.12 |
pemVersionThe version of the PEM Software that is installed on the PEGASUS system.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.13 |
startedByThe username of the person that started the PEM server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.14 |
systemNumberA number between 0 and 31 which uniquely identifies a PEGASUS system within a subnet. The system number is identified by the HW.ro INTEGER .1.3.6.1.4.1.6368.2.4.15 |
mibRevisionThe version number assigned by the version control system. You can query this from the agent, to find out with which version of the MIB was built into the agent. The value is also present in copies of the MIB to feed into SNMP managers. Comparing the version numbers from both sources can help to detect mismatches. The revision string for this version is: $Workfile: PEGASUS.mib $ $Revision: 48 $ $Date: 12/17/04 1:16p $ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.16 |
readCommunitySNMP operations with this community name are given read access to all variables in the MIB.rw DisplayString .1.3.6.1.4.1.6368.2.4.17 |
writeCommunitySNMP operations with this community name are given read access to all variables in the MIB, and write access to all writable variables in the MIB. Note that you can write this value provided you know the old value. For requests with a protocol offering no privacy, this variable always reads as three stars (***). Setting this to the empty string effectively turns off all SNMP write access.rw DisplayString .1.3.6.1.4.1.6368.2.4.18 |
trapCommunityThis community name is used for SNMPv1 or SNMPv2c traps sent by the Pegasus system.rw DisplayString .1.3.6.1.4.1.6368.2.4.19 |
trapDestinationIP number of the system to receive traps from the Pegasus system. If this variable is set to the empty string, the Pegasus system sends no traps.rw DisplayString .1.3.6.1.4.1.6368.2.4.20 |
agentPortUDP port number of the SNMP agent on the Pegasus system. The initial value is the standard SNMP port number for SNMP, 161. If this variable is set to a non-zero value different from the old value, the agent is immediately restarted with the new port number. If the value is set to zero, the agent is turned off.rw INTEGER .1.3.6.1.4.1.6368.2.4.21 |
authRespEnabledIf authentication/authorization fails for an SNMP request, the agent normally replies with an SNMP standard error message. If this variable is set to false(2), the agent sends no error message. The initial value is true(1).rwobsolete TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6368.2.4.22 |
rackAlarmStatusShows the alarms currently set for the Pegasus rack.ro RackAlarmStatusElem .1.3.6.1.4.1.6368.2.4.23 |
perf OBJECT IDENTIFIER .1.3.6.1.4.1.6368.2.7 |
perfSweepCyclePeriodTime in seconds between attempts to clear unused performance history data. Performance history can take a lot of memory. If the manager fails to delete entries in the perfControlTable, the memory will never be recovered. To avoid this, the agent periodically removes entries which have not been used recently. This is done through a mark-and-sweep method, as follows: - each perfControEntry has a mark - reading perfDataEntries sets the mark on associated perfControlEntry - the sweeper sweeps all perfControlEntries periodically. If an entry is not marked, it is deleted. If an entry is marked, it is unmarked, and will be deleted in the next sweep, if not used (marked) before. This value is volatilerw INTEGER .1.3.6.1.4.1.6368.2.7.1 |
perfControlTableThe table is used to control the gathering of G.826 statistics. This is currently possible for DSL interfaces and V5 links. If it's desired to get statstic samples, a row within this table must be created. Then link between subject and this entry must be established using the variables dslInterface- and v5LinkPerfControlIndexOrZero. Afterwards the perfDataTable is filled and can be read. SEQUENCE OF PerfControlEntry .1.3.6.1.4.1.6368.2.7.2 |
perfControlEntryDefinition of a row within the perfControlTable. Such a row contains information about the monitored subject (currently DSL interfaces and V5 links) and the status of the monitoring. PerfControlEntry .1.3.6.1.4.1.6368.2.7.2.1 |
perfControlIndexindex of perfControlEntries Integer32 .1.3.6.1.4.1.6368.2.7.2.1.1 |
perfControlStatusThis is a set of bits giving information on the status of this entry of the perfControlTable. The meaning of the individual bits is as follows: bit name Description 0 busy This bit is one if there is a DSL interface or V5 link referencing this perfControlEntry through a dslInterfacePerfControlIndexOrZero or a v5LinkPerfControlIndexOrZero value. This indicates that this perfControlEntry is busy, and its perfControlIndex value cannot be used in another DSL interface or V5 link. If the ...PerfControlIndexOrZero of the referencing interface or link is set to zero, this bit is also set to zero to show that this perfControlEntry is no longer busy - it can be used in another interface or link. 1 offline Device is offline, data may be absent or out of date. This bit is 0 if the last attempt to get performance history data from the device succeeded. In this case, the data bit (see below) is also 1. This bit (offline) is 1 if the last attempt to get performance history data failed. In this case, if no data have been received from the device, the data bit is 0, and no perfDataEntries are associated with this perfControlEntry. If some data was received from the device before the device went offline, the data bit may be 1, but the data may be out of date. 2 data Data is present. If this perfControlEntry is active, busy, and the device is not offline, this bit is to 1, which indicates that the perfDataEntries associated with this perfControlEntry are present and can be read from the perfDataTable. 3 marked This perfControlEntry has been used recently. The sweeper periodically sweeps all perfControlEntries, deleting entries with 0 in this bit. For entries with 1 in this bit, the bit is set to 0. Reading perfDataEntries sets the marked bit of the associated perfControlEntries to 1.ro PerfControlStatus .1.3.6.1.4.1.6368.2.7.2.1.2 |
perfControlLinkDescrDescription of the interface or link using this perfControlEntry. If the perfControlEntry is busy, the value is a textual description of the object referencing this entry through its ...PerfControlIndexOrZero instance. Example: dslInterface 8.1.ltu (DSL interface on card in slot 8, link 1, on ltu) v5Link 3.8 (V5 link 8 on V5 card in slot 3) If the perfControlEntry is not busy, the value is the empty string (length zero). This object helps to find the interface or link using this entry.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.6368.2.7.2.1.3 |
perfControlUpdatePeriodTime interval in seconds to wait between querying the performance history data from the device. Minimum value is 1 second. Shorter values yield more accurate/up-to-date figures, at higher communication cost. A value of 0 turns off online reporting.rw INTEGER .1.3.6.1.4.1.6368.2.7.2.1.4 |
perfControlEffectiveUpdatePeriodIf several clients monitor the same V5 link or DSL interface, each sets its own update period. The server then computes the greatest common divisor of all values. For example, if a PEM client wants to have an update every 15 seconds, and the SNMP agent wants an update every 21 seconds, the server will produce updates every 3 seconds (15=3*5, 21=3*7). The subsequence of every fifth update than has a period of 15 seconds, and the subsequence of every seventh has a period of 21 seconds.roobsolete INTEGER .1.3.6.1.4.1.6368.2.7.2.1.5 |
perfControlRowStatusAttribute to create and delete rows dynamically.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.6368.2.7.2.1.6 |
perfDataTableG.826 statistics table for DSL interfaces and V5 links. Each entry is associated to exactly one perfControlEntry that represents the link between the DSL interface or V5 link and the data entry. SEQUENCE OF PerfDataEntry .1.3.6.1.4.1.6368.2.7.3 |
perfDataEntryEach perfDataEntry is associated with exactly one perfControlEntry row through the perfControlIndex instance which is part of the index. PerfDataEntry .1.3.6.1.4.1.6368.2.7.3.1 |
perfDataKindThe second position in the index, shows the type of history - either 'history15m' (15 minute history) or 'history24h' (24 hour history). PerfHistoryType .1.3.6.1.4.1.6368.2.7.3.1.1 |
perfDataIndexRegister number. Each register has 5 values (ES/SES/UAS/CV/LOSWS). The 15 minute history has 32 history registers, indexed from 1 to 32. Each accumulates its measures over 15 minutes. The register with index 1 is the oldest register (numerical equals chronological order). The 15 minute history has an additional entry (index 33) for the current register (which is only updated when perfControlUpdatePeriod of the associated perfControlEntry is not zero). The 24 hour history has 7 true history registers, indexed 1 to 7. These accumulate there measures over 24 hours. Again, the register with index 1 is the oldest, and again, there is a current register with index 8. This current register is updated every 15 minutes, no matter what the value of perfControlUpdatePeriod of the associated perfControlEntry is. Integer32 .1.3.6.1.4.1.6368.2.7.3.1.2 |
perfDataESNumber of errored seconds. An errored second is one with at least one CRC anomaly (see perfDataCV below) and/or at least one LOSW defect (see perfDataLOSWS below). In the 15 minute history, this register ranges from 0 to 900. In the 24 hour history, it ranges from 0 to 86400 (=24*3600) seconds). This register is inhibited, that is not counted while UAS is counting. Due to variations in the communication delay, sampling periods can slightly deviate from their ideal length of 15 minutes or 24 hours. This can cause the register to show values somewhat above 900 (86400 resp.) seconds.ro Integer32 UNITS "Seconds" .1.3.6.1.4.1.6368.2.7.3.1.3 |
perfDataSESNumber of severely errored seconds. A severely errored second is one with 50 or more CRC anomalies (see perfDataCV below) or at least one LOSW defect (see perfDataLOSWS below). In the 15 minute history, this register ranges from -9 to about 450. In the 24 hour history, it ranges from -9 to about 43200. (These limits may seem strange, but are a result of the UAS derivation and SES inhibition rules of the ETSI standard. This register is inhibited, that is not counted while UAS is counting. Deviations in the sampling period length can cause this register to deviate from its true value (see perfDataES).ro Integer32 UNITS "Seconds" .1.3.6.1.4.1.6368.2.7.3.1.4 |
perfDataUASNumber of unavailable seconds. Seconds from the beginning of 10 or more SES (perfDataSES) to the beginning of 10 or more non-SES are considered as unavailable. In the 15 minute history, this register ranges from -9 to 900. In the 24 hour history, it ranges from -9 to 86400 (24*3600). Deviations in the sampling period length can cause this register to deviate from the true value (see perfDataES).ro Integer32 UNITS "Seconds" .1.3.6.1.4.1.6368.2.7.3.1.5 |
perfDataCVNumber of error checking code faults (the usual error checking code is CRC). DSL links are structured as 166 2/3 frames per second, each with a CRC value. This register is subject to inhibition, that is it counts at most 50 CRC faults per second.ro Integer32 UNITS "Frames with CRC faults" .1.3.6.1.4.1.6368.2.7.3.1.6 |
perfDataLOSWSNumber of seconds with one or more LOSW defects (loss of frame synchronization word).ro Integer32 UNITS "Seconds" .1.3.6.1.4.1.6368.2.7.3.1.7 |