PEGASUS-MIB

File: PEGASUS-MIB.mib (148264 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC

Imported symbols

enterprises Integer32 Counter32
IpAddress OBJECT-TYPE MODULE-IDENTITY
DisplayString TruthValue RowStatus
TEXTUAL-CONVENTION

Defined Types

AdminStateEnum  
INTEGER locked(1), unlocked(2), shutdown(3)    

OperStateEnum  
INTEGER enabled(1), disabled(2)    

AvailabilityStatusElem  
The availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: inTest The device is under test. failed The device has an internal fault that prevents it from operating. powerOff The device requires power to be applied and is not powered on. offLine The device requires a routine operation to be performed to place it online and make it available for use. offDuty 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. notInstalled The device is not present, or incomplete. logFull The log is full.
TEXTUAL-CONVENTION    
  BITS inTest(0), failed(1), powerOff(2), offLine(3), offDuty(4), dependency(5), degraded(6), notInstalled(7), logFull(8)  

CommStateEnum  
INTEGER disconnected(1), init(2), identification(3), checkHw(4), hwAdaption(5), checkHwVers(6), wrongProgram(7), checkConfig(8), downloadConfig(9), uploadConfig(10), statusSynch(11), resetting(12), inactive(13), active(14)    

DataPortSpeedEnum  
INTEGER autoCrossoverAndPortSpeed(1), autoNegotiationPortSpeed(2), base100TFullDuplex(3), base100THalfDuplex(4), base10TFullDuplex(5), base10THalfDuplex(6), unknown(7)    

DataPortFlowControlEnum  
INTEGER autoNegotiationFlowControl(1), onFlowControl(2), offFlowControl(3), unknown(4)    

SlotNumber  
INTEGER 1..12    

DataCardSlotNumber  
INTEGER 1..2    

V5SlotNumber  
INTEGER 3..4    

DslSlotNumber  
INTEGER 5..12    

DslLinkNumber  
INTEGER 1..16    

TrunkNumber  
INTEGER 1..5    

TrunkNumberOrZero  
INTEGER 0..5    

Priority  
INTEGER 0..7    

DslLinkLoopEnum  
INTEGER none(1), loop1(2), loop2(3)    

DslLinkAlarmElem  
Bitset to represent alarms on a DSL link.
TEXTUAL-CONVENTION    
  BITS config(0), service(1)  

DslLinkPSDMaskEnum  
INTEGER symmetric(1), asymmetric(2)    

DslCardAlarmStatus  
Bitset to represent alarms on a DSL card.
TEXTUAL-CONVENTION    
  BITS intercom(0)  

DslCardEntry  
SEQUENCE    
  dslCardSlotNumber DslSlotNumber
  dslCardAvailabilityStatus AvailabilityStatusElem
  dslCardHardwareVersion DisplayString
  dslCardManufacturer DisplayString
  dslCardName DisplayString
  dslCardOperState OperStateEnum
  dslCardFirmwareVersion DisplayString
  dslCardSerialNumber DisplayString
  dslCardCommState CommStateEnum
  dslCardAlarmStatus DslCardAlarmStatus
  dslCardM16FirmwareVersion DisplayString

DslLinkEntry  
SEQUENCE    
  dslLinkNumber DslLinkNumber
  dslLinkActiveLoop DslLinkLoopEnum
  dslLinkAddress DisplayString
  dslLinkAdminState AdminStateEnum
  dslLinkAlarmStatus DslLinkAlarmElem
  dslLinkAvailabilityStatus AvailabilityStatusElem
  dslLinkContact DisplayString
  dslLinkCustomerId DisplayString
  dslLinkDynamicSlotAllocation TruthValue
  dslLinkIsRemotePower TruthValue
  dslLinkLineRate INTEGER
  dslLinkDataRate INTEGER
  dslLinkName DisplayString
  dslLinkNotes DisplayString
  dslLinkNumberOfBRA INTEGER
  dslLinkOperState OperStateEnum
  dslLinkNumberOfZBits INTEGER
  dslLinkPSDMask DslLinkPSDMaskEnum
  dslLinkAssignedTrunk TrunkNumberOrZero
  dslLinkPriority Priority

IadAlarmStatusElem  
Bitset to represent alarms on a IAD.
TEXTUAL-CONVENTION    
  BITS powerdown(0), lifeline(1), dcContinuity(2)  

IadISDNPoweringEnum  
INTEGER off(1), normal(2), lifeline(3), always(4)    

IadPOTSPoweringEnum  
INTEGER off(1), always(2)    

IadEntry  
SEQUENCE    
  iadAvailabilityStatus AvailabilityStatusElem
  iadHardwareVersion DisplayString
  iadManufacturer DisplayString
  iadName DisplayString
  iadOperState OperStateEnum
  iadFirmwareVersion DisplayString
  iadSerialNumber DisplayString
  iadAlarmStatus IadAlarmStatusElem
  iadISDNPowering IadISDNPoweringEnum
  iadPOTSPowering IadPOTSPoweringEnum
  iadEthPortSpeed DataPortSpeedEnum
  iadEthCurrentPortSpeed DataPortSpeedEnum
  iadEthFlowControl DataPortFlowControlEnum
  iadEthCurrentFlowControl DataPortFlowControlEnum

DslInterfaceTypeEnum  
INTEGER ltu(1), ntu(2)    

DslPerformanceStatusElem  
Possible status values or alarms for a DSL interface.
TEXTUAL-CONVENTION    
  BITS att(0), losw(1)  

DslInterfaceEntry  
SEQUENCE    
  dslInterfaceType DslInterfaceTypeEnum
  dslInterfaceAvailabilityStatus AvailabilityStatusElem
  dslInterfaceOperState OperStateEnum
  dslInterfacePerformanceStatus DslPerformanceStatusElem
  dslInterfacePerfControlIndexOrZero INTEGER
  dslInterfaceSignalQuality Integer32
  dslInterfaceAttenuation Integer32

CosClassifierEnum  
INTEGER vlanPriority(1), dscpPriority(2)    

CosClassmap  
Meaning and length of the octet string depends on the value of dslLinkCOSClassifier. If vlanPriority(1) is used, only the first octet is valid. Each bit represents the number of a vlan that is used for the particular queue (EF, AF2 or AF1). In case of dscpPriority(2), 8 octets represent the 64 priorities. Within each octet, the most significant bit represents the lowest numbered vlan/priority, and the least significant bit represents the highest numbered vlan/priority. octet-to-vlan/prio mappings (1st number = value for MSB): octet1 octet2 octet3 octet4 octet5 octet6 octet7 octet8 vlan(1): 0..7 - - - - - - - dscp(2): 0..7 8..15 16..23 24..31 32..39 40..47 48..55 56..64
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..8)  

DslLinkCosEntry  
SEQUENCE    
  dslLinkCosAvailable TruthValue
  dslLinkCosEnabled TruthValue
  dslLinkCosClassifier CosClassifierEnum
  dslLinkCosClassmapEF CosClassmap
  dslLinkCosClassmapAF2 CosClassmap
  dslLinkCosClassmapAF1 CosClassmap
  dslLinkCosRateLimitEF INTEGER
  dslLinkCosRateLimitAF2 INTEGER
  dslLinkCosRateLimitAF1 INTEGER

V5ClockModeEnum  
INTEGER v5ClockMaster(1), v5ClockSlave(2)    

V5ClockSourceEnum  
INTEGER v5ClockExternal(1), v5ClockLink1(2), v5ClockLink2(3), v5ClockLink3(4), v5ClockLink4(5), v5ClockLink5(6), v5ClockLink6(7), v5ClockLink7(8), v5ClockLink8(9)    

V5ProtocolVersionEnum  
INTEGER v51(1), v52(2)    

V5CardFlagSet  
Possible configuration flags that can be applied to the V5 card.
TEXTUAL-CONVENTION    
  BITS noFastAlign(0), noLinkId(1), autoPortUnblock(2), retryAutoPortUnblock(3), rejectLinkId(4), forcePSTNDL(5), slowStart(6), deallocBlockedPort(7)  

V5CardEntry  
SEQUENCE    
  v5CardSlotNumber V5SlotNumber
  v5CardAdminState AdminStateEnum
  v5CardAvailabilityStatus AvailabilityStatusElem
  v5CardHardwareVersion DisplayString
  v5CardManufacturer DisplayString
  v5CardName DisplayString
  v5CardOperState OperStateEnum
  v5CardFirmwareVersion DisplayString
  v5CardSerialNumber DisplayString
  v5CardCommState CommStateEnum
  v5CardIsProvisioning TruthValue
  v5CardClockMode V5ClockModeEnum
  v5CardClockSource1 V5ClockSourceEnum
  v5CardClockSource2 V5ClockSourceEnum
  v5CardProtocolVersion V5ProtocolVersionEnum
  v5CardRowStatus RowStatus
  v5CardFlags V5CardFlagSet
  v5CardETSIRelease INTEGER
  v5CardE1LineCode INTEGER
  v5CardE1FrameFormat INTEGER

V5LinkNumber  
INTEGER 1..8    

V5LinkNumberOrZero  
INTEGER 0..8    

V5InterfaceNumber  
V5LinkNumber    

V5InterfaceNumberOrZero  
V5LinkNumberOrZero    

V5PccCount  
INTEGER 0..3    

V5LinkAlarmStatusElem  
Bitset that represents all possible alarms for a V5 link.
TEXTUAL-CONVENTION    
  BITS v5LinkAlarmLOS(0), v5LinkAlarmLFA(1), v5LinkAlarmAIS(2), v5LinkAlarmBERH(3), v5LinkAlarmEXTLOC(4), v5LinkAlarmRAI(5), v5LinkAlarmIdFailure(6)  

V5LinkTypeEnum  
INTEGER primary(1), secondary(2), normal(3)    

V5LinkEntry  
SEQUENCE    
  v5LinkNumber V5LinkNumber
  v5LinkAdminState AdminStateEnum
  v5LinkAvailabilityStatus AvailabilityStatusElem
  v5LinkId INTEGER
  v5LinkOperState OperStateEnum
  v5LinkInterface V5InterfaceNumberOrZero
  v5LinkAlarmStatus V5LinkAlarmStatusElem
  v5LinkType V5LinkTypeEnum
  v5LinkNumberOfPcc V5PccCount
  v5LinkPerfControlIndexOrZero INTEGER
  v5LinkRowStatus RowStatus
  v5LinkLineIdentifier DisplayString

V5InterfaceAlarmSet  
Bitset that contains the possible alarms for a V5 interface
TEXTUAL-CONVENTION    
  BITS idFailure(0), provisioningMismatch(1)  

V5InterfaceEntry  
SEQUENCE    
  v5InterfaceNumber V5InterfaceNumber
  v5InterfaceAdminState AdminStateEnum
  v5InterfaceAvailabilityStatus AvailabilityStatusElem
  v5InterfaceId INTEGER
  v5InterfaceOperState OperStateEnum
  v5InterfaceVariantId INTEGER
  v5InterfaceRowStatus RowStatus
  v5InterfaceAlarmStatus V5InterfaceAlarmSet

V5LccNumber  
INTEGER 1..21    

V5LccNumberOrZero  
INTEGER 0..21    

V5PccNumberOrZero  
INTEGER 0..3    

V5LccEntry  
SEQUENCE    
  v5LccNumber V5LccNumber
  v5LccIsProtected TruthValue
  v5LccId INTEGER
  v5LccOperState OperStateEnum
  v5LccPccV5LinkNumber V5LinkNumberOrZero
  v5LccPccTimeslot V5PccNumberOrZero
  v5LccRowStatus RowStatus

V5IsdnPortLoopEnum  
INTEGER none(1), loop1(2), loop2(3)    

V5IsdnPortBlockingStatusEnum  
INTEGER none(1), local(2), remote(3), both(4)    

V5IsdnPortAlarmStatusElem  
Bitset representing the possible alarms for a ISDN port.
TEXTUAL-CONVENTION    
  BITS l1ActivationFault(0), losTref(1), losDsig(2)  

V5TimeslotNumber  
INTEGER 1..15 | 17..31    

V5EnvelopeFuncAddress  
INTEGER 0..8175    

V5IsdnPortEntry  
SEQUENCE    
  v5IsdnPortBRANumber INTEGER
  v5IsdnPortAdminState AdminStateEnum
  v5IsdnPortOperState OperStateEnum
  v5IsdnPortBlockingStatus V5IsdnPortBlockingStatusEnum
  v5IsdnPortV5CardSlotNumber V5SlotNumber
  v5IsdnPortV5InterfaceNumber V5InterfaceNumberOrZero
  v5IsdnPortBearer1Timeslot V5TimeslotNumber
  v5IsdnPortBearer2Timeslot V5TimeslotNumber
  v5IsdnPortEnvelopeFuncAddress V5EnvelopeFuncAddress
  v5IsdnPortDSignallingCommChan V5LccNumberOrZero
  v5IsdnPortFrameCommChan V5LccNumberOrZero
  v5IsdnPortPacketCommChan V5LccNumberOrZero
  v5IsdnPortIsActivated TruthValue
  v5IsdnPortAlarmStatus V5IsdnPortAlarmStatusElem
  v5IsdnPortActiveLoop V5IsdnPortLoopEnum
  v5IsdnPortLineIdentifier DisplayString

DataCardEntry  
SEQUENCE    
  dataCardSlotNumber DataCardSlotNumber
  dataCardAvailabilityStatus AvailabilityStatusElem
  dataCardHardwareVersion DisplayString
  dataCardManufacturer DisplayString
  dataCardName DisplayString
  dataCardOperState OperStateEnum
  dataCardFirmwareVersion DisplayString
  dataCardSerialNumber DisplayString
  dataCardCommState CommStateEnum
  dataCardVLANMode TruthValue

DataPortEntry  
SEQUENCE    
  dataPortNumber TrunkNumber
  dataPortAdminState AdminStateEnum
  dataPortOperState OperStateEnum
  dataPortAvailabilityStatus AvailabilityStatusElem
  dataPortSpeed DataPortSpeedEnum
  dataPortFlowControl DataPortFlowControlEnum

ConfigPriorityEnum  
INTEGER server(1), device(2)    

HWAdaptionPolicyEnum  
INTEGER device(1), server(2)    

RackAlarmStatusElem  
possible alarms concerning the Pegasus rack
TEXTUAL-CONVENTION    
  BITS psu1Failure(0), psu2Failure(1), fanFailure(2), urgentExt(3), nonUrgentExt(4)  

PerfControlStatus  
status of a performance control entry
TEXTUAL-CONVENTION    
  BITS busy(0), offline(1), data(2), marked(3)  

PerfControlEntry  
SEQUENCE    
  perfControlIndex Integer32
  perfControlStatus PerfControlStatus
  perfControlLinkDescr DisplayString
  perfControlUpdatePeriod INTEGER
  perfControlEffectiveUpdatePeriod INTEGER
  perfControlRowStatus RowStatus

PerfHistoryType  
INTEGER history15m(1), history24h(2)    

PerfDataEntry  
SEQUENCE    
  perfDataKind PerfHistoryType
  perfDataIndex Integer32
  perfDataES Integer32
  perfDataSES Integer32
  perfDataUAS Integer32
  perfDataCV Integer32
  perfDataLOSWS Integer32

Defined Values

pegasusMibModule 1.3.6.1.4.1.6368.2
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.
MODULE-IDENTITY    

schmidtelecom 1.3.6.1.4.1.6368
OBJECT IDENTIFIER    

dsl 1.3.6.1.4.1.6368.2.1
OBJECT IDENTIFIER    

v5 1.3.6.1.4.1.6368.2.2
OBJECT IDENTIFIER    

data 1.3.6.1.4.1.6368.2.3
OBJECT IDENTIFIER    

pegasusSystem 1.3.6.1.4.1.6368.2.4
OBJECT IDENTIFIER    

perf 1.3.6.1.4.1.6368.2.7
OBJECT IDENTIFIER    

dslCardTable 1.3.6.1.4.1.6368.2.1.1
A table containing line card specific information.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DslCardEntry

dslCardEntry 1.3.6.1.4.1.6368.2.1.1.1
Row and index definition for line card table.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslCardEntry  

dslCardSlotNumber 1.3.6.1.4.1.6368.2.1.1.1.1
Slot number for line card.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslSlotNumber  

dslCardAvailabilityStatus 1.3.6.1.4.1.6368.2.1.1.1.2
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

dslCardHardwareVersion 1.3.6.1.4.1.6368.2.1.1.1.3
Hardware 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslCardManufacturer 1.3.6.1.4.1.6368.2.1.1.1.4
Name of company which manufactured this line card/ltu.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslCardName 1.3.6.1.4.1.6368.2.1.1.1.5
User defined ame of line card.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslCardOperState 1.3.6.1.4.1.6368.2.1.1.1.6
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

dslCardFirmwareVersion 1.3.6.1.4.1.6368.2.1.1.1.7
Version 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslCardSerialNumber 1.3.6.1.4.1.6368.2.1.1.1.8
Serial number of the line card. Also called HM-number, as it always starts with 'HM'. Example: HMVSS014810294.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslCardCommState 1.3.6.1.4.1.6368.2.1.1.1.9
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  CommStateEnum  

dslCardAlarmStatus 1.3.6.1.4.1.6368.2.1.1.1.10
Alarm status of the line card. Bits assigned as follows: bit 0 intercom The intercom line between the PPC and M16 has failed.
Status: current Access: read-only
OBJECT-TYPE    
  DslCardAlarmStatus  

dslCardM16FirmwareVersion 1.3.6.1.4.1.6368.2.1.1.1.11
Version 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslLinkTable 1.3.6.1.4.1.6368.2.1.2
A table containing dsl link specific information.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DslLinkEntry

dslLinkEntry 1.3.6.1.4.1.6368.2.1.2.1
Information about a particular dsl link.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslLinkEntry  

dslLinkNumber 1.3.6.1.4.1.6368.2.1.2.1.1
Number 1-8 of link on line card.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslLinkNumber  

dslLinkActiveLoop 1.3.6.1.4.1.6368.2.1.2.1.2
Loop back (test) setup currently active. Disconnect the DSL link before activating the maintenance loop on the LTU (loop1).
Status: current Access: read-write
OBJECT-TYPE    
  DslLinkLoopEnum  

dslLinkAddress 1.3.6.1.4.1.6368.2.1.2.1.3
Customer address stored in configuration file of agent.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..80)  

dslLinkAdminState 1.3.6.1.4.1.6368.2.1.2.1.4
This 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.
Status: current Access: read-write
OBJECT-TYPE    
  AdminStateEnum  

dslLinkAlarmStatus 1.3.6.1.4.1.6368.2.1.2.1.5
Alarms 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.
Status: current Access: read-only
OBJECT-TYPE    
  DslLinkAlarmElem  

dslLinkAvailabilityStatus 1.3.6.1.4.1.6368.2.1.2.1.6
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

dslLinkContact 1.3.6.1.4.1.6368.2.1.2.1.7
A contact person, address or phone number.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

dslLinkCustomerId 1.3.6.1.4.1.6368.2.1.2.1.8
An identification number which has been assigned to this customer.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslLinkDynamicSlotAllocation 1.3.6.1.4.1.6368.2.1.2.1.9
If 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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

dslLinkIsRemotePower 1.3.6.1.4.1.6368.2.1.2.1.10
LTU puts dc supply voltage onto link. IAD uses this if local power fails.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

dslLinkLineRate 1.3.6.1.4.1.6368.2.1.2.1.11
Number 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 3..36  

dslLinkDataRate 1.3.6.1.4.1.6368.2.1.2.1.12
Number 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..36  

dslLinkName 1.3.6.1.4.1.6368.2.1.2.1.13
User defined name of the DSL link.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..20)  

dslLinkNotes 1.3.6.1.4.1.6368.2.1.2.1.14
Notes stored in the configuration file of the agent.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

dslLinkNumberOfBRA 1.3.6.1.4.1.6368.2.1.2.1.15
Number 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..4  

dslLinkOperState 1.3.6.1.4.1.6368.2.1.2.1.16
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

dslLinkNumberOfZBits 1.3.6.1.4.1.6368.2.1.2.1.17
Number of Z bits on the DSL link.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..1  

dslLinkPSDMask 1.3.6.1.4.1.6368.2.1.2.1.18
PSD (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.
Status: current Access: read-write
OBJECT-TYPE    
  DslLinkPSDMaskEnum  

dslLinkAssignedTrunk 1.3.6.1.4.1.6368.2.1.2.1.19
Determines the data trunk (aggregate side) on which the all data traffic of this DSL Link is mapped.
Status: current Access: read-write
OBJECT-TYPE    
  TrunkNumberOrZero  

dslLinkPriority 1.3.6.1.4.1.6368.2.1.2.1.20
Determines 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.
Status: current Access: read-write
OBJECT-TYPE    
  Priority  

iadTable 1.3.6.1.4.1.6368.2.1.3
IAD 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).
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    IadEntry

iadEntry 1.3.6.1.4.1.6368.2.1.3.1
Carry index for iad table.
Status: current Access: not-accessible
OBJECT-TYPE    
  IadEntry  

iadAvailabilityStatus 1.3.6.1.4.1.6368.2.1.3.1.1
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

iadHardwareVersion 1.3.6.1.4.1.6368.2.1.3.1.2
Hardware 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

iadManufacturer 1.3.6.1.4.1.6368.2.1.3.1.3
Name of company which manufactured this IAD.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

iadName 1.3.6.1.4.1.6368.2.1.3.1.4
User defined name of IAD.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

iadOperState 1.3.6.1.4.1.6368.2.1.3.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

iadFirmwareVersion 1.3.6.1.4.1.6368.2.1.3.1.6
Version 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

iadSerialNumber 1.3.6.1.4.1.6368.2.1.3.1.7
Serial number of the IAD. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014432064.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

iadAlarmStatus 1.3.6.1.4.1.6368.2.1.3.1.8
Alarm 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.
Status: current Access: read-only
OBJECT-TYPE    
  IadAlarmStatusElem  

iadISDNPowering 1.3.6.1.4.1.6368.2.1.3.1.9
State 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.
Status: current Access: read-write
OBJECT-TYPE    
  IadISDNPoweringEnum  

iadPOTSPowering 1.3.6.1.4.1.6368.2.1.3.1.10
Defines 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.
Status: current Access: read-write
OBJECT-TYPE    
  IadPOTSPoweringEnum  

iadEthPortSpeed 1.3.6.1.4.1.6368.2.1.3.1.11
Configuration of the desired speed for the IAD's Ethernet port.
Status: current Access: read-write
OBJECT-TYPE    
  DataPortSpeedEnum  

iadEthCurrentPortSpeed 1.3.6.1.4.1.6368.2.1.3.1.12
Displays the currently active speed of a IAD's Ethernet port.
Status: current Access: read-only
OBJECT-TYPE    
  DataPortSpeedEnum  

iadEthFlowControl 1.3.6.1.4.1.6368.2.1.3.1.13
Configuration of the desired flow control.
Status: current Access: read-write
OBJECT-TYPE    
  DataPortFlowControlEnum  

iadEthCurrentFlowControl 1.3.6.1.4.1.6368.2.1.3.1.14
Displays the currently used flow control.
Status: current Access: read-only
OBJECT-TYPE    
  DataPortFlowControlEnum  

dslInterfaceTable 1.3.6.1.4.1.6368.2.1.4
DSL Interface table.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DslInterfaceEntry

dslInterfaceEntry 1.3.6.1.4.1.6368.2.1.4.1
Row/index definition for dslInterfaceTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslInterfaceEntry  

dslInterfaceType 1.3.6.1.4.1.6368.2.1.4.1.1
The type of device on which the interface sits: LTU (linecard) or Ntu (IAD, modem).
Status: current Access: not-accessible
OBJECT-TYPE    
  DslInterfaceTypeEnum  

dslInterfaceAvailabilityStatus 1.3.6.1.4.1.6368.2.1.4.1.2
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

dslInterfaceOperState 1.3.6.1.4.1.6368.2.1.4.1.3
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

dslInterfacePerformanceStatus 1.3.6.1.4.1.6368.2.1.4.1.4
Displays the current status of the DSL interface
Status: current Access: read-only
OBJECT-TYPE    
  DslPerformanceStatusElem  

dslInterfacePerfControlIndexOrZero 1.3.6.1.4.1.6368.2.1.4.1.5
If 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER  

dslInterfaceSignalQuality 1.3.6.1.4.1.6368.2.1.4.1.6
This 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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -128..127  

dslInterfaceAttenuation 1.3.6.1.4.1.6368.2.1.4.1.7
This 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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -128..127  

dslLinkCosTable 1.3.6.1.4.1.6368.2.1.5
Class 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
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DslLinkCosEntry

dslLinkCosEntry 1.3.6.1.4.1.6368.2.1.5.1
Row/index definition for dslLinkCosTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  DslLinkCosEntry  

dslLinkCosAvailable 1.3.6.1.4.1.6368.2.1.5.1.1
If true(1), COS is supported by the LineCard.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

dslLinkCosEnabled 1.3.6.1.4.1.6368.2.1.5.1.2
Enabling and disabling of COS for the specified link.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

dslLinkCosClassifier 1.3.6.1.4.1.6368.2.1.5.1.3
Configuration of the desired classifier. Possible values are VLAN priority and DSCP (Differentiated Services Code Point) priority.
Status: current Access: read-write
OBJECT-TYPE    
  CosClassifierEnum  

dslLinkCosClassmapEF 1.3.6.1.4.1.6368.2.1.5.1.4
Classmap for the EF (Expedited Forwarding) queue. See description of CosClassmap for further information.
Status: current Access: read-write
OBJECT-TYPE    
  CosClassmap  

dslLinkCosClassmapAF2 1.3.6.1.4.1.6368.2.1.5.1.5
Classmap for the AF2 (Assured Forwarding) queue. See description of CosClassmap for further information.
Status: current Access: read-write
OBJECT-TYPE    
  CosClassmap  

dslLinkCosClassmapAF1 1.3.6.1.4.1.6368.2.1.5.1.6
Classmap for the AF1 (Assured Forwarding) queue. See description of CosClassmap for further information.
Status: current Access: read-write
OBJECT-TYPE    
  CosClassmap  

dslLinkCosRateLimitEF 1.3.6.1.4.1.6368.2.1.5.1.7
Maximum 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..2312  

dslLinkCosRateLimitAF2 1.3.6.1.4.1.6368.2.1.5.1.8
Maximum 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..2312  

dslLinkCosRateLimitAF1 1.3.6.1.4.1.6368.2.1.5.1.9
Maximum 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..2312  

v5CardTable 1.3.6.1.4.1.6368.2.2.1
A table containing V5 card specific information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    V5CardEntry

v5CardEntry 1.3.6.1.4.1.6368.2.2.1.1
Row and index definition for V5 card table.
Status: current Access: not-accessible
OBJECT-TYPE    
  V5CardEntry  

v5CardSlotNumber 1.3.6.1.4.1.6368.2.2.1.1.1
Slot number for v5 card.
Status: current Access: not-accessible
OBJECT-TYPE    
  V5SlotNumber  

v5CardAdminState 1.3.6.1.4.1.6368.2.2.1.1.2
This 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.
Status: current Access: read-create
OBJECT-TYPE    
  AdminStateEnum  

v5CardAvailabilityStatus 1.3.6.1.4.1.6368.2.2.1.1.3
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

v5CardHardwareVersion 1.3.6.1.4.1.6368.2.2.1.1.4
Hardware 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

v5CardManufacturer 1.3.6.1.4.1.6368.2.2.1.1.5
Name of company which manufactured this V5 card.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

v5CardName 1.3.6.1.4.1.6368.2.2.1.1.6
User defined name of the V5 card.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

v5CardOperState 1.3.6.1.4.1.6368.2.2.1.1.7
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

v5CardFirmwareVersion 1.3.6.1.4.1.6368.2.2.1.1.8
Version 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

v5CardSerialNumber 1.3.6.1.4.1.6368.2.2.1.1.9
Serial number of the V5 card. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014532139.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

v5CardCommState 1.3.6.1.4.1.6368.2.2.1.1.10
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  CommStateEnum  

v5CardIsProvisioning 1.3.6.1.4.1.6368.2.2.1.1.11
The V5 Card is in provisioning mode. Only if this flag is true, re-configuration of the V5 Card is possible.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

v5CardClockMode 1.3.6.1.4.1.6368.2.2.1.1.12
Clock mode of the V5 Card Master This card is the clock master. Slave This card is a clock slave.
Status: current Access: read-create
OBJECT-TYPE    
  V5ClockModeEnum  

v5CardClockSource1 1.3.6.1.4.1.6368.2.2.1.1.13
If 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).
Status: current Access: read-create
OBJECT-TYPE    
  V5ClockSourceEnum  

v5CardClockSource2 1.3.6.1.4.1.6368.2.2.1.1.14
If 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).
Status: current Access: read-create
OBJECT-TYPE    
  V5ClockSourceEnum  

v5CardProtocolVersion 1.3.6.1.4.1.6368.2.2.1.1.15
The version of the V5 protocol. Can be either V5.1 or V5.2
Status: current Access: read-create
OBJECT-TYPE    
  V5ProtocolVersionEnum  

v5CardRowStatus 1.3.6.1.4.1.6368.2.2.1.1.16
This 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).
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

v5CardFlags 1.3.6.1.4.1.6368.2.2.1.1.17
This object holds various flags which can be set to modify the behaviour of the V5 protocol stack.
Status: current Access: read-create
OBJECT-TYPE    
  V5CardFlagSet  

v5CardETSIRelease 1.3.6.1.4.1.6368.2.2.1.1.18
The 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).
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER v1(1), v2(2)  

v5CardE1LineCode 1.3.6.1.4.1.6368.2.2.1.1.19
The E1 line code used on all V5 links of the V5 card.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER hdb3(1), ami(2)  

v5CardE1FrameFormat 1.3.6.1.4.1.6368.2.2.1.1.20
The frame format of E1 frames used on all V5 links of the V5 card.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER crc4(1), crc4e(2), dff(3)  

v5LinkTable 1.3.6.1.4.1.6368.2.2.2
A table containing V5 link specific information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    V5LinkEntry

v5LinkEntry 1.3.6.1.4.1.6368.2.2.2.1
Row and index definition for V5 link table.
Status: current Access: not-accessible
OBJECT-TYPE    
  V5LinkEntry  

v5LinkNumber 1.3.6.1.4.1.6368.2.2.2.1.1
Number of the link on the V5 card (used for table indexing).
Status: current Access: not-accessible
OBJECT-TYPE    
  V5LinkNumber  

v5LinkAdminState 1.3.6.1.4.1.6368.2.2.2.1.2
This 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.
Status: current Access: read-create
OBJECT-TYPE    
  AdminStateEnum  

v5LinkAvailabilityStatus 1.3.6.1.4.1.6368.2.2.2.1.3
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

v5LinkId 1.3.6.1.4.1.6368.2.2.2.1.4
V5 Link Identifier. Value range is 0 .. 255
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..255  

v5LinkOperState 1.3.6.1.4.1.6368.2.2.2.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

v5LinkInterface 1.3.6.1.4.1.6368.2.2.2.1.6
Identifies to which V5 interface this V5 link is related.
Status: current Access: read-create
OBJECT-TYPE    
  V5InterfaceNumberOrZero  

v5LinkAlarmStatus 1.3.6.1.4.1.6368.2.2.2.1.7
Alarm 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 indication
Status: current Access: read-only
OBJECT-TYPE    
  V5LinkAlarmStatusElem  

v5LinkType 1.3.6.1.4.1.6368.2.2.2.1.8
Specifies 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.
Status: current Access: read-create
OBJECT-TYPE    
  V5LinkTypeEnum  

v5LinkNumberOfPcc 1.3.6.1.4.1.6368.2.2.2.1.9
The 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.
Status: current Access: read-create
OBJECT-TYPE    
  V5PccCount  

v5LinkPerfControlIndexOrZero 1.3.6.1.4.1.6368.2.2.2.1.10
The 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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER  

v5LinkRowStatus 1.3.6.1.4.1.6368.2.2.2.1.11
RowStatis variable that allows creation and deletion of V5 links.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

v5LinkLineIdentifier 1.3.6.1.4.1.6368.2.2.2.1.12
An idenifier assigned to the subscriber (customer).
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

v5InterfaceTable 1.3.6.1.4.1.6368.2.2.3
A table containing V5 interface specific information. Only AN side interfaces are present.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    V5InterfaceEntry

v5InterfaceEntry 1.3.6.1.4.1.6368.2.2.3.1
Row and index definition for V5 interface table.
Status: current Access: not-accessible
OBJECT-TYPE    
  V5InterfaceEntry  

v5InterfaceNumber 1.3.6.1.4.1.6368.2.2.3.1.1
interface number, used for table indexing
Status: current Access: not-accessible
OBJECT-TYPE    
  V5InterfaceNumber  

v5InterfaceAdminState 1.3.6.1.4.1.6368.2.2.3.1.2
This 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.
Status: current Access: read-create
OBJECT-TYPE    
  AdminStateEnum  

v5InterfaceAvailabilityStatus 1.3.6.1.4.1.6368.2.2.3.1.3
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

v5InterfaceId 1.3.6.1.4.1.6368.2.2.3.1.4
V5 Interface Identifier. Value range is 0 .. 16777215.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..16777215  

v5InterfaceOperState 1.3.6.1.4.1.6368.2.2.3.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

v5InterfaceVariantId 1.3.6.1.4.1.6368.2.2.3.1.6
Indicates 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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..127  

v5InterfaceRowStatus 1.3.6.1.4.1.6368.2.2.3.1.7
Variable to create and delete V5 interfaces.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

v5InterfaceAlarmStatus 1.3.6.1.4.1.6368.2.2.3.1.8
Displays the currently active alarms of the V5 interface.
Status: current Access: read-only
OBJECT-TYPE    
  V5InterfaceAlarmSet  

v5LccTable 1.3.6.1.4.1.6368.2.2.4
table containing all LCC (Logical Communication Channels) for a V5 interface
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    V5LccEntry

v5LccEntry 1.3.6.1.4.1.6368.2.2.4.1
row defintion for the v5LccTable
Status: current Access: not-accessible
OBJECT-TYPE    
  V5LccEntry  

v5LccNumber 1.3.6.1.4.1.6368.2.2.4.1.1
index of the LCC; number in the range of 1..21
Status: current Access: not-accessible
OBJECT-TYPE    
  V5LccNumber  

v5LccIsProtected 1.3.6.1.4.1.6368.2.2.4.1.2
If true, all information transported over this LCC is protected by the V5 Protection protocol (V5.2 only).
Status: current Access: read-create
OBJECT-TYPE    
  TruthValue  

v5LccId 1.3.6.1.4.1.6368.2.2.4.1.3
Unique L3 address per Logical Communication Channel. Value range is 0 .. 65535.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER  

v5LccOperState 1.3.6.1.4.1.6368.2.2.4.1.4
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

v5LccPccV5LinkNumber 1.3.6.1.4.1.6368.2.2.4.1.5
Identify (together with v5LccPccTimeslot) the Physical Communication Channel used for the signalling data of this Logical Communication Channel.
Status: current Access: read-create
OBJECT-TYPE    
  V5LinkNumberOrZero  

v5LccPccTimeslot 1.3.6.1.4.1.6368.2.2.4.1.6
Identify (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.
Status: current Access: read-create
OBJECT-TYPE    
  V5PccNumberOrZero  

v5LccRowStatus 1.3.6.1.4.1.6368.2.2.4.1.7
The 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.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

v5IsdnPortTable 1.3.6.1.4.1.6368.2.2.5
A table containing information specific to V5 ISDN user ports, i.e. S0 interfaces on IADs.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    V5IsdnPortEntry

v5IsdnPortEntry 1.3.6.1.4.1.6368.2.2.5.1
Row 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).
Status: current Access: not-accessible
OBJECT-TYPE    
  V5IsdnPortEntry  

v5IsdnPortBRANumber 1.3.6.1.4.1.6368.2.2.5.1.3
index number for this port
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER 1..4  

v5IsdnPortAdminState 1.3.6.1.4.1.6368.2.2.5.1.4
This 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.
Status: current Access: read-write
OBJECT-TYPE    
  AdminStateEnum  

v5IsdnPortOperState 1.3.6.1.4.1.6368.2.2.5.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

v5IsdnPortBlockingStatus 1.3.6.1.4.1.6368.2.2.5.1.6
In 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.
Status: current Access: read-only
OBJECT-TYPE    
  V5IsdnPortBlockingStatusEnum  

v5IsdnPortBearer1Timeslot 1.3.6.1.4.1.6368.2.2.5.1.7
Assigned 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.
Status: current Access: read-write
OBJECT-TYPE    
  V5TimeslotNumber  

v5IsdnPortBearer2Timeslot 1.3.6.1.4.1.6368.2.2.5.1.8
Assigned 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.
Status: current Access: read-write
OBJECT-TYPE    
  V5TimeslotNumber  

v5IsdnPortEnvelopeFuncAddress 1.3.6.1.4.1.6368.2.2.5.1.9
Layer 3 Address of this User Port. Value range is 0 .. 8175.
Status: current Access: read-write
OBJECT-TYPE    
  V5EnvelopeFuncAddress  

v5IsdnPortIsActivated 1.3.6.1.4.1.6368.2.2.5.1.10
Layer 1 activation status
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

v5IsdnPortAlarmStatus 1.3.6.1.4.1.6368.2.2.5.1.11
displays the currently active alarms for the ISDN port
Status: current Access: read-only
OBJECT-TYPE    
  V5IsdnPortAlarmStatusElem  

v5IsdnPortActiveLoop 1.3.6.1.4.1.6368.2.2.5.1.12
Tok_String
Status: obsolete Access: read-write
OBJECT-TYPE    
  V5IsdnPortLoopEnum  

v5IsdnPortV5CardSlotNumber 1.3.6.1.4.1.6368.2.2.5.1.13
Slot 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.
Status: current Access: read-only
OBJECT-TYPE    
  V5SlotNumber  

v5IsdnPortV5InterfaceNumber 1.3.6.1.4.1.6368.2.2.5.1.14
The 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.
Status: current Access: read-write
OBJECT-TYPE    
  V5InterfaceNumberOrZero  

v5IsdnPortDSignallingCommChan 1.3.6.1.4.1.6368.2.2.5.1.15
The ISDN Communication Path over which the D-Signalling control information of this User Port is transported.
Status: current Access: read-write
OBJECT-TYPE    
  V5LccNumberOrZero  

v5IsdnPortFrameCommChan 1.3.6.1.4.1.6368.2.2.5.1.16
The ISDN Communication Path over which the Frame control information of this User Port is transported.
Status: current Access: read-write
OBJECT-TYPE    
  V5LccNumberOrZero  

v5IsdnPortPacketCommChan 1.3.6.1.4.1.6368.2.2.5.1.17
The ISDN Communication Path over which the Packet control information of this User Port is transported.
Status: current Access: read-write
OBJECT-TYPE    
  V5LccNumberOrZero  

v5IsdnPortLineIdentifier 1.3.6.1.4.1.6368.2.2.5.1.18
An idenifier assigned to the subscriber (customer).
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

dataCardTable 1.3.6.1.4.1.6368.2.3.1
attributes concerning the data switch (slot 1)
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DataCardEntry

dataCardEntry 1.3.6.1.4.1.6368.2.3.1.1
entry/row within the dataCardTable
Status: current Access: not-accessible
OBJECT-TYPE    
  DataCardEntry  

dataCardSlotNumber 1.3.6.1.4.1.6368.2.3.1.1.1
Position of the slot card in the rack.
Status: current Access: not-accessible
OBJECT-TYPE    
  DataCardSlotNumber  

dataCardAvailabilityStatus 1.3.6.1.4.1.6368.2.3.1.1.2
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

dataCardHardwareVersion 1.3.6.1.4.1.6368.2.3.1.1.3
Hardware 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dataCardManufacturer 1.3.6.1.4.1.6368.2.3.1.1.4
Manufacturer of the data card.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dataCardName 1.3.6.1.4.1.6368.2.3.1.1.5
User defined name of the data card.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dataCardOperState 1.3.6.1.4.1.6368.2.3.1.1.6
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

dataCardFirmwareVersion 1.3.6.1.4.1.6368.2.3.1.1.7
Version 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dataCardSerialNumber 1.3.6.1.4.1.6368.2.3.1.1.8
Serial number of the data card. Also called HM-number, as it always starts with 'HM'. Example: HMHMZ014332080.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..20)  

dataCardCommState 1.3.6.1.4.1.6368.2.3.1.1.9
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  CommStateEnum  

dataCardVLANMode 1.3.6.1.4.1.6368.2.3.1.1.10
If 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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

dataPortTable 1.3.6.1.4.1.6368.2.3.2
The table contains an entry for each Ethernet trunk on the data switch (card).
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DataPortEntry

dataPortEntry 1.3.6.1.4.1.6368.2.3.2.1
entry within the dataPortTable
Status: current Access: not-accessible
OBJECT-TYPE    
  DataPortEntry  

dataPortNumber 1.3.6.1.4.1.6368.2.3.2.1.1
index of the (ethernet) trunk on the data switch
Status: current Access: not-accessible
OBJECT-TYPE    
  TrunkNumber  

dataPortAdminState 1.3.6.1.4.1.6368.2.3.2.1.2
This 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.
Status: current Access: read-write
OBJECT-TYPE    
  AdminStateEnum  

dataPortOperState 1.3.6.1.4.1.6368.2.3.2.1.3
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  OperStateEnum  

dataPortAvailabilityStatus 1.3.6.1.4.1.6368.2.3.2.1.4
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  AvailabilityStatusElem  

dataPortSpeed 1.3.6.1.4.1.6368.2.3.2.1.5
This 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.
Status: current Access: read-write
OBJECT-TYPE    
  DataPortSpeedEnum  

dataPortFlowControl 1.3.6.1.4.1.6368.2.3.2.1.6
Setting 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.
Status: current Access: read-write
OBJECT-TYPE    
  DataPortFlowControlEnum  

autoPersistDelay 1.3.6.1.4.1.6368.2.4.1
If 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER  

autoPersistEnabled 1.3.6.1.4.1.6368.2.4.2
Determines, 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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

configPriority 1.3.6.1.4.1.6368.2.4.3
Determines, 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)
Status: current Access: read-write
OBJECT-TYPE    
  ConfigPriorityEnum  

hwAdaptionPolicy 1.3.6.1.4.1.6368.2.4.4
In 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)
Status: obsolete Access: read-write
OBJECT-TYPE    
  HWAdaptionPolicyEnum  

ipBaseAddress 1.3.6.1.4.1.6368.2.4.5
Base 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.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

javaRuntimeVersion 1.3.6.1.4.1.6368.2.4.6
Version of the installed Java Runtime.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

javaVMName 1.3.6.1.4.1.6368.2.4.7
Name of the installed Java virtual machine.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

javaVMVersion 1.3.6.1.4.1.6368.2.4.8
Version of the installed Java virtual machine on the work-station.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

mgmtIPAddress 1.3.6.1.4.1.6368.2.4.9
The IP Address of the PEGASUS system through which the PEM Server is accessible.
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

osArchitecture 1.3.6.1.4.1.6368.2.4.11
Displays information about the operating system where the PEM server is running.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

osNameAndVersion 1.3.6.1.4.1.6368.2.4.12
Name and version of the operating system that is running on the workstation where the PEM server is running.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

pemVersion 1.3.6.1.4.1.6368.2.4.13
The version of the PEM Software that is installed on the PEGASUS system.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

startedBy 1.3.6.1.4.1.6368.2.4.14
The username of the person that started the PEM server.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

systemNumber 1.3.6.1.4.1.6368.2.4.15
A number between 0 and 31 which uniquely identifies a PEGASUS system within a subnet. The system number is identified by the HW.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER  

mibRevision 1.3.6.1.4.1.6368.2.4.16
The 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: : PEGASUS.mib $ : 48 $ : 12/17/04 1:16p $
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

readCommunity 1.3.6.1.4.1.6368.2.4.17
SNMP operations with this community name are given read access to all variables in the MIB.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

writeCommunity 1.3.6.1.4.1.6368.2.4.18
SNMP 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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

trapCommunity 1.3.6.1.4.1.6368.2.4.19
This community name is used for SNMPv1 or SNMPv2c traps sent by the Pegasus system.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

trapDestination 1.3.6.1.4.1.6368.2.4.20
IP 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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..40)  

agentPort 1.3.6.1.4.1.6368.2.4.21
UDP 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..65535  

authRespEnabled 1.3.6.1.4.1.6368.2.4.22
If 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).
Status: obsolete Access: read-write
OBJECT-TYPE    
  TruthValue  

rackAlarmStatus 1.3.6.1.4.1.6368.2.4.23
Shows the alarms currently set for the Pegasus rack.
Status: current Access: read-only
OBJECT-TYPE    
  RackAlarmStatusElem  

perfSweepCyclePeriod 1.3.6.1.4.1.6368.2.7.1
Time 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 volatile
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 0..604800  

perfControlTable 1.3.6.1.4.1.6368.2.7.2
The 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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PerfControlEntry

perfControlEntry 1.3.6.1.4.1.6368.2.7.2.1
Definition 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.
Status: current Access: not-accessible
OBJECT-TYPE    
  PerfControlEntry  

perfControlIndex 1.3.6.1.4.1.6368.2.7.2.1.1
index of perfControlEntries
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..2147483647  

perfControlStatus 1.3.6.1.4.1.6368.2.7.2.1.2
This 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.
Status: current Access: read-only
OBJECT-TYPE    
  PerfControlStatus  

perfControlLinkDescr 1.3.6.1.4.1.6368.2.7.2.1.3
Description 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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

perfControlUpdatePeriod 1.3.6.1.4.1.6368.2.7.2.1.4
Time 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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 0..180  

perfControlEffectiveUpdatePeriod 1.3.6.1.4.1.6368.2.7.2.1.5
If 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  INTEGER 0..180  

perfControlRowStatus 1.3.6.1.4.1.6368.2.7.2.1.6
Attribute to create and delete rows dynamically.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

perfDataTable 1.3.6.1.4.1.6368.2.7.3
G.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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PerfDataEntry

perfDataEntry 1.3.6.1.4.1.6368.2.7.3.1
Each perfDataEntry is associated with exactly one perfControlEntry row through the perfControlIndex instance which is part of the index.
Status: current Access: not-accessible
OBJECT-TYPE    
  PerfDataEntry  

perfDataKind 1.3.6.1.4.1.6368.2.7.3.1.1
The second position in the index, shows the type of history - either 'history15m' (15 minute history) or 'history24h' (24 hour history).
Status: current Access: not-accessible
OBJECT-TYPE    
  PerfHistoryType  

perfDataIndex 1.3.6.1.4.1.6368.2.7.3.1.2
Register 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.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..2147483647  

perfDataES 1.3.6.1.4.1.6368.2.7.3.1.3
Number 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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

perfDataSES 1.3.6.1.4.1.6368.2.7.3.1.4
Number 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).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

perfDataUAS 1.3.6.1.4.1.6368.2.7.3.1.5
Number 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).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

perfDataCV 1.3.6.1.4.1.6368.2.7.3.1.6
Number 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.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

perfDataLOSWS 1.3.6.1.4.1.6368.2.7.3.1.7
Number of seconds with one or more LOSW defects (loss of frame synchronization word).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor