CHASSIS-MIB: View SNMP OID List / Download MIB
VENDOR: XYLAN CORP.
| Home | MIB: CHASSIS-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| chasInfo | 1.3.6.1.4.1.800.2.1.1 | |||
| chasMake | 1.3.6.1.4.1.800.2.1.1.1 | displaystring | read-only |
An authoritative identification of this chassis or device. By convention, this value is allocated within the SMI enterprises subtree(1.3.6.1.4.1), and provides an easy and unambiguous means for determining `what kind of box' is being managed. If this information is not present or unknown, its value should be set to chasTypeUnknown. |
| chasType | 1.3.6.1.4.1.800.2.1.1.2 | xylanchastype | read-only |
The particular type of Xylan chassis. The value of other(2) will be returned if the variable is supported but the chassis is not one of the currently known types of Omni5(3) or Omni9(4). |
| chasDescription | 1.3.6.1.4.1.800.2.1.1.3 | displaystring | read-write |
A description for this chassis/product. The value shall default to the textual product description, but the user can override this to anything desired. |
| chasPhysicalChanges | 1.3.6.1.4.1.800.2.1.1.4 | counter | read-only |
Depicts the number of physical changes that have occured to the chassis MIB since reset or power on. This includes additions and removal of modules in the module table or additions and removal of controllers in the controller table. |
| chasLogicalChanges | 1.3.6.1.4.1.800.2.1.1.5 | counter | read-only |
Depicts the number of logical changes that have occured to the chassis MIB since reset or power on. This includes all sets to name strings. |
| chasNoOfResets | 1.3.6.1.4.1.800.2.1.1.6 | counter | read-only |
This object is a count of the number of times this this station has been reset since a cold-start. |
| chasBaseMacAddress | 1.3.6.1.4.1.800.2.1.1.7 | macaddress | read-only |
This object is the 'base' MAC address for this chassis. |
| chasFreeSlots | 1.3.6.1.4.1.800.2.1.1.8 | integer | read-only |
The number of free front panel slots. |
| chasIpAddrToPing | 1.3.6.1.4.1.800.2.1.1.9 | ipaddress | read-write |
The IP address to which a ping should be issued. A Network Management Station can use this to issue directed broadcast pings so as to augment the IP ARP table. The ARP table is useful in discovering the IP network topology. |
| chasDupMacSupport | 1.3.6.1.4.1.800.2.1.1.10 | integer | read-only |
The number of Duplication of any single MAC address learned. 0 indicates no duplicate MAC support, 1 up to 64 indicates the number of duplication allowed per board. The value of 1 indicates no duplication allowed per board only, but it is allowed between boards for the entire chassis. |
| chasNewDupMacSupport | 1.3.6.1.4.1.800.2.1.1.11 | integer | read-write |
This variable allows the user to cause duplicate MAC addresses to age out concurrently. If set to zero, it is ignored and the aging timer for each group where the address was learned will be used. Values 1 through 9 are not valid. If set to a value between 10 and 1000000, it will be used instead of the group aging timers. Units are seconds. |
| chasSonetMonitoring | 1.3.6.1.4.1.800.2.1.1.12 | integer | read-write |
on(1) - Start Sonet Monitoring. If the image file (sec.img) is not loaded, this variable should be set to load it. off(2) - Stop Sonet Monitoring. |
| chasVbusMode | 1.3.6.1.4.1.800.2.1.1.13 | integer | read-only |
The Vbus header type used in the OSR. A value of 0 indicates classic Vbus Mode is currently selected . 1 indicates the use of VBUS Mode 2. |
| chasPhysical | 1.3.6.1.4.1.800.2.1.2 | |||
| chasModuleTable | 1.3.6.1.4.1.800.2.1.2.1 | no-access |
A list of installed modules in this chassis. |
|
| 1.3.6.1.4.1.800.2.1.2.1.1 | no-access |
A module entry containing objects for a particular module. This would contain entries that relate to the module in a specific 'slot'. |
||
| chasModuleSlot | 1.3.6.1.4.1.800.2.1.2.1.1.1 | integer | read-only |
The (zero-based) front slot number within the chassis. |
| chasModuleSubUnit | 1.3.6.1.4.1.800.2.1.2.1.1.2 | xylanmodulesubunit | read-only |
The sub-unit number within module in slot 'n'. For each non-empty slot there will exist a module entry with a chasModuleSubUnit value of base. If the chasModuleType of that chasModuleEntry is hsm, then there may be additional chasModuleEntrys with the same chasModuleSlot value but with chasModuleSubUnit values of hsm1, hsm2 or csm3. These are HSM or CSM-U sub-modules. An HSM module can have up to 2 daughter cards on it. The first position would be denoted by hsm1(2) and the second position is hsm2(3). A CSM-U module can have up to 3 daughter cards on it.The first position would be denoted by hsm1(2) and the second position is hsm2(3) and the third postion is csm3(4). The general implication of this field is: each occupied slot will have an entry field will be base(1), and may if the module supports daughter cards have entries for which if this field is hsm1(2), hsm2(3) or cms3(4), corrosponding to an installed daughter card on the HSM or CMS-U in the specified chasModuleSlot. (and the card type will be listed in chasModuleType). |
| chasModuleType | 1.3.6.1.4.1.800.2.1.2.1.1.3 | xylanmoduletype | read-only |
An authoritative identification of the type of physical module that is in this physical location. Notice that the value empty(3) will not be seen in this table, because this table will only have entries that contain modules. |
| chasModulePartNum | 1.3.6.1.4.1.800.2.1.2.1.1.4 | displaystring | read-only |
The part number of ths module. |
| chasModuleDescription | 1.3.6.1.4.1.800.2.1.2.1.1.5 | displaystring | read-write |
Textual description of this particular module. The user can change this value to whatever is desired. |
| chasModuleHwRevision | 1.3.6.1.4.1.800.2.1.2.1.1.6 | integer | read-only |
The current revision of this module's hardware. |
| chasModuleHwModLevel | 1.3.6.1.4.1.800.2.1.2.1.1.7 | integer | read-only |
The modification level of this module's hardware. |
| chasModuleSerialNumber | 1.3.6.1.4.1.800.2.1.2.1.1.8 | displaystring | read-only |
The serial number of the module present in this physical location. |
| chasModuleMfgDate | 1.3.6.1.4.1.800.2.1.2.1.1.9 | displaystring | read-only |
The manufacturing date for this module. This data is retrieved from the module non-volitile memory. |
| chasModuleFwVersion | 1.3.6.1.4.1.800.2.1.2.1.1.10 | displaystring | read-only |
Textual decription of the version/revision level for this module's firmware/software. |
| chasModuleBaseMacAddress | 1.3.6.1.4.1.800.2.1.2.1.1.11 | macaddress | read-only |
This is the 'base' MAC address for this module. If the module does not support the notion of MAC addresses, the vaule shall be 0. |
| chasModuleTimeStamp | 1.3.6.1.4.1.800.2.1.2.1.1.12 | timeticks | read-only |
The value of sysUpTime of this management entitiy, when this module was last (re-) initialized. |
| chasModuleAdminStatus | 1.3.6.1.4.1.800.2.1.2.1.1.13 | integer | read-write |
Provides desired (and actual) state of the given module. Notice that not all values may be supported by a specified physical module. In this case an SNMP error returned when a set is attempted. All modules (even empty slots) are in an unknown(1) state when the chassis first powers up. The invalid state is for non-existant modules, and hence is never seen. Neither of the unknown(1) or invalid(2) status values can be written. A physical module can be activated by writing a value of enable(3). A physical module may be de-activated by writing a value of disable(4). In a disabled state, the module is present in the chassis, but is benign. A disabled module is availible for subsequent activation. Writing a value of reset(5), disables the module AND initiates a reset sequence. Writing a value of load(6), disables the module AND initiates a software load sequence. Writing a value of test(7), disables the module AND initiates selftest within the module. Enumeration: 'reset': 5, 'load': 6, 'enable': 3, 'unknown': 1, 'invalid': 2, 'disable': 4, 'test': 7. |
| chasModuleOperStatus | 1.3.6.1.4.1.800.2.1.2.1.1.14 | integer | read-only |
Provides operational state of the given module. The exact definition of the values is implementation specific. A value of unknown(1) implies some undetermined state, possibly as a result of a module failing the low-level selftest. A value of invalid(2) may mean that the module exists but the chassis manager has no direct control over it. A value of operational(3) implies that the entity is running with no errors or warnings. A value of disabled(4) reflects the response to the chasModuleAdminStatus of disable(4). A value of resetInProgress(5) also reflects the equivalent AdminStatus reset(5). Note that the states warning(8), nonFatalError(9), and fatalError(10) reflect conditions detected during operation. The module may or may not be fuctional at this point. For example a module's value of AdminStatus is disable(4), the OperStatus will reflect that. The AdminStatus is set to enable(3), the OperStatus might then change to testing(7) then change to operational(3). Enumeration: 'nonFatalError': 9, 'unknown': 1, 'resetInProgress': 5, 'testing': 7, 'invalid': 2, 'operational': 3, 'disabled': 4, 'warning': 8, 'fatalError': 10, 'loadInProgress': 6. |
| chasModuleLedStatus | 1.3.6.1.4.1.800.2.1.2.1.1.15 | integer | read-only |
The LED state for this module. The exact definition of the values are implimentation dependent. For example, a power supply module may not have any LEDs present, while a network interface element might have 28 LEDs and a Controller might have 6 LEDs. NOTE: due to European regulation, the LEDs will NEVER be illuminated RED! They in fact will be either green OR amber. This will be reflected in the MIB as either GRN=1/RED=0 or GRN=1/RED=1. Of course, if both are off then the LED is not illuminated. The current bit definitions for the defined modules are: mpm 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - PS1 RED (0 off, 1 on) 3 - PS2 RED (0 off, 1 on) 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - PS1 GRN (0 off, 1 on) 7 - PS2 GRN (0 off, 1 on) 8 - PRI MPM GRN (0 on, 1 off) 9 - SEC MPM GRN (0 on, 1 off) 10 - TEMP ALARM AMBER (0 on, 1 off) 11-21 - undefined 22 - HRE PRESENT (1 yes, 0 no) 23 - BUS SPEED (1 960, 0 640) 24-31 - reserved pizza 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2-3 - unused 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - HSM1 GRN (0 off, 1 on) 7 - HSM2 GRN (0 off, 1 on) 8-31 - reserved eni8 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8-15 - reserved 16 - STA1 GRN 17 - STA2 GRN 18 - STA3 GRN 19 - STA4 GRN 20 - STA5 GRN 21 - STA6 GRN 22 - STA7 GRN 23 - STA8 GRN mesm8 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8 - 1 = Full Duplex Port 1 9 - 1 = Full Duplex Port 2 10 - 1 = Full Duplex Port 3 11 - 1 = Full Duplex Port 4 12 - 1 = Full Duplex Port 5 13 - 1 = Full Duplex Port 6 14 - 1 = Full Duplex Port 7 15 - 1 = Full Duplex Port 8 16 - 1 = STA1 GRN 17 - 1 = STA2 GRN 18 - 1 = STA3 GRN 19 - 1 = STA4 GRN 20 - 1 = STA5 GRN 21 - 1 = STA6 GRN 22 - 1 = STA7 GRN 23 - 1 = STA8 GRN mesm12 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8 - 1 = STA1 GRN 9 - 1 = STA2 GRN 10 - 1 = STA3 GRN 11 - 1 = STA4 GRN 12 - 1 = STA5 GRN 13 - 1 = STA6 GRN 14 - 1 = STA7 GRN 15 - 1 = STA8 GRN 16 - 1 = STA9 GRN 17 - 1 = STA10 GRN 18 - 1 = STA11 GRN 19 - 1 = STA12 GRN 20-23 - reserved mesm16 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8 - 1 = STA1 GRN 9 - 1 = STA2 GRN 10 - 1 = STA3 GRN 11 - 1 = STA4 GRN 12 - 1 = STA5 GRN 13 - 1 = STA6 GRN 14 - 1 = STA7 GRN 15 - 1 = STA8 GRN 16 - 1 = STA9 GRN 17 - 1 = STA10 GRN 18 - 1 = STA11 GRN 19 - 1 = STA12 GRN 20 - 1 = STA13 GRN 21 - 1 = STA14 GRN 22 - 1 = STA15 GRN 23 - 1 = STA16 GRN eni12 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8 - STA1 GRN (1 on, 0 off) 9 - STA2 GRN (1 on, 0 off) 10 - STA3 GRN (1 on, 0 off) 11 - STA4 GRN (1 on, 0 off) 12 - STA5 GRN (1 on, 0 off) 13 - STA6 GRN (1 on, 0 off) 14 - STA7 GRN (1 on, 0 off) 15 - STA8 GRN (1 on, 0 off) 16 - STA9 GRN (1 on, 0 off) 17 - STA10 GRN (1 on, 0 off) 18 - STA11 GRN (1 on, 0 off) 19 - STA12 GRN (1 on, 0 off) 20-31 - reserved eni16 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6-7 - undefined 8 - ENB1 (1 - yes, 0 - no) 9 - ENB2 (1 - yes, 0 - no) 10 - ENB3 (1 - yes, 0 - no) 11 - ENB4 (1 - yes, 0 - no) 12 - ENB5 (1 - yes, 0 - no) 13 - ENB6 (1 - yes, 0 - no) 14 - ENB7 (1 - yes, 0 - no) 15 - ENB8 (1 - yes, 0 - no) 16 - ENB9 (1 - yes, 0 - no) 17 - ENB10 (1 - yes, 0 - no) 18 - ENB11 (1 - yes, 0 - no) 19 - ENB12 (1 - yes, 0 - no) 20 - ENB13 (1 - yes, 0 - no) 21 - ENB14 (1 - yes, 0 - no) 22 - ENB15 (1 - yes, 0 - no) 23 - ENB16 (1 - yes, 0 - no) 24-31 - reserved tni 0-11 - reserved 12 - Status_1 LED (0 = ON) 13 - Status_2 LED (0 = ON) 14 - Status_3 LED (0 = ON) 15 - Status_4 LED (0 = ON) 16 - Status_5 LED (0 = ON) 17 - Status_6 LED (0 = ON) 18 - Beacon_1 LED (0 = ON) 19 - Beacon_2 LED (0 = ON) 20 - Beacon_3 LED (0 = ON) 21 - Beacon_4 LED (0 = ON) 22 - Beacon_5 LED (0 = ON) 23 - Beacon_6 LED (0 = ON) 24-31 - undefined hsm 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6-31 - reserved fddi 0-3 - reserved 4 - LINK (0 flash (DISABLED), 1 on (ENABLED)) 5 - WRAP B LED (0 on, 1 off) 6 - WRAP A LED (0 on, 1 off) 7 - THRU LED (0 on, 1 off) 8-31 - reserved cddi 0-7 - reserved 8-9 - Link LED A 00 - off, x1 - on, 10 - flash 10-11 - Link LED B 00 - off, x1 - on, 10 - flash 12-13 - Link LED C 00 - off, x1 - on, 10 - flash 14-15 - Link LED D 00 - off, x1 - on, 10 - flash 16-31 - reserved for example, the value 0xD8xx indicates Link LED A - off Link LED B - flashing Link LED C - on Link LED D - on atm 0-3 - reserved 4 - FAR END (0 on, 1 off) 5 - YELLOW ALARM LED (0 on, 1 off) 6 - RED ALARM LED (0 on, 1 off) 7 - CELL ERROR LED (0 on, 1 off) 8 - Link (1 Green, 0 off) 9-31 - reserved atm2155fmx, These are ATM OC3/DS3 Uplink Cards for OA408 atm2155fsx, atm2155flx, atm2ds3u, atm2e3u: 0-3 - reserved - off yellow green 4-5 00 01 11 6-31 - reserved atm2155rsx, These are ATM OC3 Uplink Cards with redundant ports for OA408 atm2155rlx: 0-3 - reserved - off yellow green 4-5 LINK1 00 01 11 6-7 LINK2 00 01 11 8-31 - reserved fesm 0-6 - reserved 6 - STA On (1 on, 0 off) 7 - STA Flash (1 Flash, 0 solid) (Not used) 8 - LINK1 On (1 on, 0 off) 9 - LINK1 Flash (1 Flash, 0 solid) (Not used) -- The following are for Copper Only 10 - LINK2 On (1 on, 0 off) 11 - LINK2 Flash (1 Flash, 0 solid) (Not used) 12 - LINK3 On (1 on, 0 off) 13 - LINK3 Flash (1 Flash, 0 solid) (Not used) 14 - LINK4 On (1 on, 0 off) 15 - LINK4 Flash (1 Flash, 0 solid) (Not used) 16 - Full Duplex (1) Half Duplex (0) 17-31 - reserved wsm 0-7 - reserved - off blink slow blink on 8-9 - STA1 00 01 10 11 10-11 - STA2 00 01 10 11 12-13 - STA3 00 01 10 11 14-15 - STA4 00 01 10 11 16-17 - STA5 00 01 10 11 18-19 - STA6 00 01 10 11 20-21 - STA7 00 01 10 11 22-23 - STA8 00 01 10 11 24-31 - reserved csm 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined 8-23 - port = bit - 7; - 0 - port down, LINK OFF, RED Amber - 1 - port up, LINK Green, RED OFF 24-31 - unused cabcm 0-7 - reserved off blink on 8-9 LINK1 00 01 11 10-31 - reserved fcsm 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6-31 - unused atmce2s2t, atmce2s2e 0-7 - reserved 8 - LINK1 (1 on, 0 off) 9 - ERR1 (1 on, 0 off) 10 - LINK2 (1 on, 0 off) 11 - ERR2 (1 on, 0 off) - off blink on 12-13 - STA1 00 01 11 14-15 - STA2 00 01 11 16-31 - reserved csmu 0 - OK1 RED (0 off, 1 on) 1 - OK2 RED (0 off, 1 on) 2 - undefined 3 - undefined 4 - OK1 GRN (0 off, 1 on) 5 - OK2 GRN (0 off, 1 on) 6 - undefined 7 - undefined cabds3: cabe3: 0-7 - reserved off yellow green 8-9 LINK1 00 01 11 10-11 LINK2 00 01 11 12-31 - reserved atm2imat1u: for OA408 atm2imae1u: for OA408 cabds1: cabe1: cabcet1: cabcee1: 0-7 - reserved off yellow green 8-9 LINK1 00 01 11 10-11 LINK2 00 01 11 12-13 LINK3 00 01 11 14-15 LINK4 00 01 11 16-31 - reserved oa4cet1: 0-7 - reserved oa4cee1: off yellow green 8-9 LINK1 00 01 11 10-11 LINK2 00 01 11 12-13 PORT3 00 01 11 14-15 PORT4 00 01 11 16-31 - reserved cab4imat1: cab4imae1: cab8imat1: cab8imae1: 0-7 - reserved off yellow green 8-9 LINK1 00 01 11 10-11 LINK2 00 01 11 12-13 LINK3 00 01 11 14-15 LINK4 00 01 11 16-17 LINK5 00 01 11 18-19 LINK6 00 01 11 20-21 LINK7 00 01 11 22-23 LINK8 00 01 11 24-31 - reserved Other modules will be defined later. |
| chasModuleVbusTxDiscards | 1.3.6.1.4.1.800.2.1.2.1.1.16 | counter | read-only |
The current count of transmit VBUS buffer overruns. |
| chasModuleVbusRxDiscards | 1.3.6.1.4.1.800.2.1.2.1.1.17 | counter | read-only |
The current count of receive VBUS buffer overruns. |
| chasModuleLedStatusExtend | 1.3.6.1.4.1.800.2.1.2.1.1.18 | octet string | read-only |
A octet string containing module led information |
| chasController | 1.3.6.1.4.1.800.2.1.3 | |||
| chasControlTable | 1.3.6.1.4.1.800.2.1.3.1 | no-access |
A list of Module controller status. NOTE: Objects with ACCESS of read-write which are associated with configuration data which presists accross reboots are in fact only valid for the Primary MPM. If the Secondary MPM has different values this information is not available to snmp queries, nor is it possible to write to the Secondaries instance of these objects. Further, once the cconfigured data is sychronized from the Primary to the Secondary, all values set on the Primary will be those used by the Secondary after the Secondary is reset. There is no ability to change a value for the Secondary except by changinging it on the Primary and then writing the configuation of the Primary to the Secondary. |
|
| 1.3.6.1.4.1.800.2.1.3.1.1 | no-access |
A controller entry containing objects for a particular controller. |
||
| chasControlSlot | 1.3.6.1.4.1.800.2.1.3.1.1.1 | integer | read-only |
The physical slot number for this controller card. This is the same as chasModuleSlot. |
| chasControlState | 1.3.6.1.4.1.800.2.1.3.1.1.2 | xylanmpmstatetype | read-write |
Provides desired (and actual) state of the given controller module. The unknown state may be returned if the controller is not present or offline. A controller may be placed into the Primary state by writing a value of primary(3). Note that most implimentations will verify that only one controller is active; thus, setting this will automatically place all other controllers into the secondary state. A controller may be placed into the secondary state by writing a value of secondary(4). The system will ensure two modules are present and that the secondary is capable of entering the primary state. |
| chasControlDCEPortRate | 1.3.6.1.4.1.800.2.1.3.1.1.3 | xylanserialportspeed | read-write |
This is the current (and desired) baud rate for the DCE (console) serial port 1. The power-on default rate is 9600 b/s. |
| chasControlDCEWordSize | 1.3.6.1.4.1.800.2.1.3.1.1.4 | integer | read-write |
This is the current (and desired) word size for serial port 0 (DCE). The power-on default is 8 bits. |
| chasControlDCEStopBits | 1.3.6.1.4.1.800.2.1.3.1.1.5 | integer | read-write |
This is the current (and desired) number of stop bits for serial port 0 (DCE). The power-on default is 1 bit. |
| chasControlDCEParity | 1.3.6.1.4.1.800.2.1.3.1.1.6 | xylanserialportparity | read-write |
This is the current (and desired) parity for serial port 0 (DCE). The power-on default rate is NONE. |
| chasControlDTEPortRate | 1.3.6.1.4.1.800.2.1.3.1.1.7 | xylanserialportspeed | read-write |
This is the current (and desired) baud rate for the DTE (modem) serial port 0. The power-on default rate is 9600 b/s. |
| chasControlDTEWordSize | 1.3.6.1.4.1.800.2.1.3.1.1.8 | integer | read-write |
This is the current (and desired) word size for serial port 1 (DTE). The power-on default is 8 bits. |
| chasControlDTEStopBits | 1.3.6.1.4.1.800.2.1.3.1.1.9 | integer | read-write |
This is the current (and desired) number of stop bits for serial port 1 (DTE). The power-on default is 1 bit. |
| chasControlDTEParity | 1.3.6.1.4.1.800.2.1.3.1.1.10 | xylanserialportparity | read-write |
This is the current (and desired) parity for serial port 1 (DTE). The power-on default rate is NONE. |
| chasControlIPAdd | 1.3.6.1.4.1.800.2.1.3.1.1.11 | ipaddress | read-only |
The IP address for this MPM and it's snmp agent. |
| chasControlBootCode | 1.3.6.1.4.1.800.2.1.3.1.1.12 | displaystring | read-write |
FW boot code to load on reset for this controller. |
| chasControlFreeFFS | 1.3.6.1.4.1.800.2.1.3.1.1.13 | integer | read-only |
The current free Flash File System space. |
| chasControlFreeBuffers | 1.3.6.1.4.1.800.2.1.3.1.1.14 | integer | read-only |
The current software does not pool a specific number of buffers. Therefore this object is obsolete. |
| chasControlBufferUtilization | 1.3.6.1.4.1.800.2.1.3.1.1.15 | gauge | read-only |
The current software does not pool a specific number of buffers. Therefore this object is obsolete. |
| chasControlCPUUtilization | 1.3.6.1.4.1.800.2.1.3.1.1.16 | gauge | read-only |
The current CPU utilization for this controller. |
| chasControlImageSuffix | 1.3.6.1.4.1.800.2.1.3.1.1.17 | displaystring | read-write |
This character string will be used to determine which file is downloaded to the NIs to be brought up by the chassis manager. Only files with suffixes (the part of the file name following '.') matching this character string will be downloaded to NIs which are inserted into the chassis or reset. If the chassis is rebooted these files will be used for the initial NI loads. This value can only be set on the Primary MPM. If automatic synchronization is enabled and the required image files on the Secondary match those on the Primary (State is Redundant or CONFIG FB) then the value set will be copied to the Secondary after the first 5min period of no configuration updates or when a configsync is envoked. |
| chasControlImageSyncStatus | 1.3.6.1.4.1.800.2.1.3.1.1.18 | xylanimagesyncstatus | read-write |
For the Primary this means: insync(1) the files in the secondary's flash file system are the same as those in the primary's. newer(2) the files in the secondary's flash file system have a more recent date than those on the primary older(3) the files in the secondary's flash file system have an earlier date than those on the primary unknown(4)no meaningfull answer exists syncing(5)The Primary has initiated file synchronization this should be temporay - 30 minutes at most! For the Secondary the meaning or 2 and 3 are reversed If this value is SET to 1, the chassis attempts to synchronize the image files. |
| chasControlConfigSyncStatus | 1.3.6.1.4.1.800.2.1.3.1.1.19 | xylanconfigsyncstatus | read-write |
insync(1) All configuration data on the Primary is the same as that on the secondary. newer(2) The config data on the Primary MPM has been updated more recently than the config data on the secondary. (This is not a possible value if the instance is the Secondary) older(3) The config data on the Primary MPM has been updated more recently than the config data on the secondary. (This is not a possible value if the instance is the Primary) unknown(4)No meaniful response can be given. syncing(5)The Primary has initiated configuration synchronization this should be temporay 15 minutes at most! bootvalues(6) The configuration data contains the boot values. Only possible on secondary if snmp is interaction with chassis is possible If this value is SET to 1, the chassis attempts to synchronize the configuration file. |
| chasControlConfigSyncEnable | 1.3.6.1.4.1.800.2.1.3.1.1.20 | xylanconfigsyncenable | read-write |
enabled(1) - After changes to configuration data AND after 5 min from the last change if the image files are synced, sync synchronize the configuration data. disabled(2) - never automatically synchronize the configuration data. |
| chasControlDCEPortMode | 1.3.6.1.4.1.800.2.1.3.1.1.21 | xylanserialportmode | read-only |
down(1) - This port is down. console(2) - This is the console port slip(3) - This is a slip port. This value can only be modified through the console/slip port |
| chasControlDTEPortMode | 1.3.6.1.4.1.800.2.1.3.1.1.22 | xylanserialportmode | read-only |
down(1) - This port is down. console(2) - This is the console port slip(3) - This is a slip port. This value can only be modified through the console/slip port |
| chasControlEthPortIPAddr | 1.3.6.1.4.1.800.2.1.3.1.1.23 | ipaddress | read-write |
The IP network address of the Ethernet Mgmt. Port. |
| chasControlEthPortSubMask | 1.3.6.1.4.1.800.2.1.3.1.1.24 | ipaddress | read-write |
The IP network subnet mask of the Ethernet Mgmt. Port. |
| chasControlEthPortBcast | 1.3.6.1.4.1.800.2.1.3.1.1.25 | ipaddress | read-write |
The IP network broadcast address of the Ethernet Mgmt. Port. |
| chasControlEthPortGateWay | 1.3.6.1.4.1.800.2.1.3.1.1.26 | ipaddress | read-write |
The IP network gateway address of the Ethernet Mgmt. Port. |
| chasControlEthPortRipMode | 1.3.6.1.4.1.800.2.1.3.1.1.27 | integer | read-only |
The RIP mode of the Ethernet Mgmt. Port. Enumeration: 'active': 3, 'inactive': 4, 'deaf': 2, 'silent': 1. |
| chasControlEthPortRemoteHost | 1.3.6.1.4.1.800.2.1.3.1.1.28 | ipaddress | read-write |
The IP network remote host address of the Ethernet Mgmt. Port. |
| chasControlEthPortRemoteMask | 1.3.6.1.4.1.800.2.1.3.1.1.29 | ipaddress | read-write |
The IP network remote host subnet mask of the Ethernet Mgmt. Port. |
| chasControlFFSTable | 1.3.6.1.4.1.800.2.1.3.2 | no-access |
This table provides a file directory listing of both the primary and secondary MPMs. and provides for simple file operations. |
|
| 1.3.6.1.4.1.800.2.1.3.2.1 | no-access |
Each entry describes as single file. Rather than use the entire file name as an instance, a checksum of the file name is used. |
||
| chasControlFFSFileSlot | 1.3.6.1.4.1.800.2.1.3.2.1.1 | integer | read-only |
Which slot, valid values are 1 and 2. If there is no Secondary MPM only one of these will be valid. |
| chasControlFFSFileNameCks | 1.3.6.1.4.1.800.2.1.3.2.1.2 | integer | read-only |
This value/instance is derived from the file name and is used to determine which file the NMS is inquiring about or operating on. The NMS must use the value given by the Switch. |
| chasControlFFSFileName | 1.3.6.1.4.1.800.2.1.3.2.1.3 | displaystring | read-only |
The file name. |
| chasControlFFSFileSize | 1.3.6.1.4.1.800.2.1.3.2.1.4 | integer | read-only |
The file size: bytes of data. |
| chasControlFFSFileDate | 1.3.6.1.4.1.800.2.1.3.2.1.5 | timeticks | read-only |
The unix date the file was created. this is based upon number of seconds since 1/ 1/70. Files created by older versions of the bootcode alway have 1/ 1/70 00:00 as the date. If the date is incorrect on the switch the values in the file system will reflect that. |
| chasControlFFSFileAction | 1.3.6.1.4.1.800.2.1.3.2.1.6 | xylanffsfileaction | read-write |
none(1) No action has been requested for this file writingTo(2) can only be specified for Primary causes the specified file to be written from Primary to Secondary. deletingFrom(3) this file is being removed can be specified for files on both Primary and Secondary. readingFrom(4) can only be specified for Secondary causes the specified file to be copoed from the Secondary to the Promary. This value may be set to delete files from an MPM or copy files between the Primary and Secondary. Only one action is permitted at a time. If a SET is attempted to ANY chasControlFFSFileAction when chasControlLastFFSActionSlot is inProgress(2) the resource will be unavailable. |
| chasControlFFSActionStatus | 1.3.6.1.4.1.800.2.1.3.3 | |||
| chasControlLastFFSAction | 1.3.6.1.4.1.800.2.1.3.3.1 | xylanffsfileaction | read-only |
writingTo(2) The file is being written to the Seconday. deletingFrom(3) the file is being removed from the slot indicated by chasControlLastFFSActionSlot. readingFrom(4) the file is being copied from the Secondary to the Primary. The last action that was requested from the file system. Only one action is permitted at a time. If a SET is attempted to ANY chasControlFFSFileAction when chasControlLastFFSActionSlot is inProgress(2) that resource will be unavailable. |
| chasControlLastFFSActionSlot | 1.3.6.1.4.1.800.2.1.3.3.2 | integer | read-only |
The slot number (1/2) which combined with the action says what is really happening. |
| chasControlLastFFSActionFileName | 1.3.6.1.4.1.800.2.1.3.3.3 | displaystring | read-only |
The name of the file upon which the last Action is was successfully requested. |
| chasControlLastFFSActionDate | 1.3.6.1.4.1.800.2.1.3.3.4 | timeticks | read-only |
The time of the last successfull set to chasControlFFSFileAction |
| chasControlLastFFSActionSource | 1.3.6.1.4.1.800.2.1.3.3.5 | ipaddress | read-only |
The IP address of the NMS which did the last successfull set to chasControlFFSFileAction |
| chasControlLastFFSActionStatus | 1.3.6.1.4.1.800.2.1.3.3.6 | xylanffsfileactionstatus | read-only |
none(1) No file action has ever been succesfully requested since boot up of this MPM. Included takeover by Secondary MPM. inProgress(2) The action described by other members of this group is still underway. successfull(3) The action described by other members of this group completed successfully. failed(4) The action described by other members of this group failed. |
| chasPowerSupply | 1.3.6.1.4.1.800.2.1.4 | |||
| chasPowerSupply1State | 1.3.6.1.4.1.800.2.1.4.1 | xylanpsstatetype | read-only |
The status of power supply slot 1. |
| chasPowerSupply2State | 1.3.6.1.4.1.800.2.1.4.2 | xylanpsstatetype | read-only |
The status of power supply slot 2. |
| chasEnvmnt | 1.3.6.1.4.1.800.2.1.5 | |||
| chasEnvrmnt1TempRange1 | 1.3.6.1.4.1.800.2.1.5.1 | xylantempstatetype | read-only |
This field contains the state of the temp sensor located on the Primary MPM. This is temperature sensor 0. |
| chasEnvrmnt1TempRange2 | 1.3.6.1.4.1.800.2.1.5.2 | xylantempstatetype | read-only |
This field contains the state of the temp sensor located on the Primary MPM. This is temperature sensor 1. If the module type is mpm(5) the value returned is notPresent(2). On other MPM types a returned value of underThreshold(4) indcates that the temperature is NOT too low and overThreshold(3) indicates that the temperature IS too low. |
| chasEnvrmnt2TempRange1 | 1.3.6.1.4.1.800.2.1.5.3 | xylantempstatetype | read-only |
This field contains the state of the temp sensor located on the Secondary MPM. This is temperature sensor 0. |
| chasEnvrmnt2TempRange2 | 1.3.6.1.4.1.800.2.1.5.4 | xylantempstatetype | read-only |
This field contains the state of the temp sensor located on the Secondary MPM. This is temperature sensor 1. If there is no Secondary MPM or if the module type is mpm(5) the value returned is notPresent(2). On other MPM types a returned value of underThreshold(4) indcates that the temperature is NOT too low and overThreshold(3) indicates that the temperature IS too low. |
| chasStatus | 1.3.6.1.4.1.800.2.1.6 | |||
| chasXylanOpaque | 1.3.6.1.4.1.800.2.1.6.1 | octet string | read-only |
The Xylan proprietary status structure. |
| chasXylanCompaq | 1.3.6.1.4.1.800.2.1.6.2 | octet string | read-only |
The Xylan proprietary status structure. |
| chasXylanPollData | 1.3.6.1.4.1.800.2.1.6.3 | octet string | read-only |
The third Xylan proprietary status structure. |
| chasAccounting | 1.3.6.1.4.1.800.2.1.7 | |||
| chasAccountCdrCount | 1.3.6.1.4.1.800.2.1.7.1 | integer | read-only |
The number of Charging Detail Records currently in memory and not safely stored yet. |
| chasAccountMethodInUse | 1.3.6.1.4.1.800.2.1.7.2 | integer | read-only |
The method in use to store terminated Charging Detail Records. Enumeration: 'disabled': 1, 'wire': 2, 'disk': 3. |
| chasAccountDeviceInUse | 1.3.6.1.4.1.800.2.1.7.3 | ipaddress | read-only |
The IP address of the collection device with which a TCP connection was most recently established. If the method is disk, or if no device is available, this parameter is set to 0.0.0.0. |
| chasAccountMaxCnxInUse | 1.3.6.1.4.1.800.2.1.7.4 | integer | read-only |
Indicates the maximum number of taxable connections in use. |
| chasAccountCdrNext | 1.3.6.1.4.1.800.2.1.7.5 | integer | read-only |
The value put as CDR identifier in the next Charging Detail Record. Corresponds to the number of CDRs generated. |
| chasAccountFileCount | 1.3.6.1.4.1.800.2.1.7.6 | integer | read-only |
The number of terminated accounting files awaiting collection (and removal) by an external accounting collection agent. |
| chasAccountPollCycle | 1.3.6.1.4.1.800.2.1.7.7 | integer | read-only |
Indicates whether the switch is awaiting the end of the next period, or is busy completing Charging Detail Records at the end of the current period. Enumeration: 'waiting': 1, 'polling': 2. |
| chasAccountConnectState | 1.3.6.1.4.1.800.2.1.7.8 | integer | read-only |
Shows the state of the connection state machine. Set to unused (0) when storing data on local disk. Enumeration: 'openAlternate': 5, 'openHold': 3, 'unused': 0, 'openAlternateHold': 4, 'closed': 1, 'closeHold': 6, 'open': 2. |
| chasAccountMethod | 1.3.6.1.4.1.800.2.1.7.9 | integer | read-write |
The requested method to store terminated Charging Detail Records. Enumeration: 'disabled': 1, 'wire': 2, 'disk': 3. |
| chasAccountDevicePrimary | 1.3.6.1.4.1.800.2.1.7.10 | ipaddress | read-write |
The IP address of the primary collection device. |
| chasAccountDeviceSecondary | 1.3.6.1.4.1.800.2.1.7.11 | ipaddress | read-write |
The IP address of the secondary collection device. |
| chasAccountDevicePort | 1.3.6.1.4.1.800.2.1.7.12 | integer | read-write |
The port on which the accounting collection device is listening. |
| chasAccountPeriods | 1.3.6.1.4.1.800.2.1.7.13 | octet string | read-write |
A set of tariff periods. Each octet indicates the quarter-hour since midnight at which a new period begins. Each value is at least four units larger than its predecessor, else it is silently ignored. |
| chasAccountInterval | 1.3.6.1.4.1.800.2.1.7.14 | integer | read-write |
The interval for intermediate accounting collection . Enumeration: 'hourly': 4, 'twice-daily': 48, 'two-hours': 8, 'three-hours': 12. |
| chasAccountChargedServices | 1.3.6.1.4.1.800.2.1.7.15 | integer | read-write |
Indicates for which services charging can be enabled. The parameter is a bitmap where each bit represents a service. The following services are already defined: 00000001 = ATM switching 00000002 = FR switching Raising a bit enables charging the service, while clearing the bit disables charging for that service. |
| chasAccountMaxCnx | 1.3.6.1.4.1.800.2.1.7.16 | integer | read-write |
Indicates the configured maximum number of taxable connections. |
| chasAccountFillingLevel | 1.3.6.1.4.1.800.2.1.7.17 | integer | read-only |
This gauge indicates the amount of buffer taken up by accounting data. Values are a percentage of the buffer size. |
| chasAccountThreshold1 | 1.3.6.1.4.1.800.2.1.7.18 | integer | read-write |
The first filling level of the intermediate storage area for accounting data. Crossing this threshold generates a warning. The level is expressed as a percentage of size. |
| chasAccountThreshold2 | 1.3.6.1.4.1.800.2.1.7.19 | integer | read-write |
The second filling level of the intermediate storage area for accounting data. Crossing this threshold generates a warning, the current TCP connection is closed and a new one is established towards the alternate collection device. The level is expressed as a percentage of size. |
| chasAccountThreshold3 | 1.3.6.1.4.1.800.2.1.7.20 | integer | read-write |
The third filling level of the intermediate storage area for accounting data. Beyond this level, the switch enters a congestion state and may refuse new SVC connections. The level is expressed as a percentage of size. |
| chasAccountTcpWriteTimer | 1.3.6.1.4.1.800.2.1.7.21 | integer | read-write |
Indicates the ticker value for writing accounting data onto the TCP connection. Units are hundreds of milli-seconds. |
| chasAccountHoldDownTimer | 1.3.6.1.4.1.800.2.1.7.22 | integer | read-write |
Indicates the holding delay on crossing threshold2. When threshold2 is exceeded, the switch changes to the alternate TCP connection. The buffer must remain filled above the threshold2 level for at least T2 seconds before another change of the TCP connection is authorized. Units are seconds. |
| chasAccountFileSize | 1.3.6.1.4.1.800.2.1.7.23 | integer | read-write |
When accounting data are stored on local disk, this parameter indicates the upper limit of an accounting file. If this limit is exceeded, the file is closed, compressed, and put in the outgoing directory for collection by an external device. Units are in Kbytes. |
| chasAccountCongStrategy | 1.3.6.1.4.1.800.2.1.7.24 | integer | read-write |
When the switch is in congestion state, for lack of resources to store accounting data, this parameter indicates whether new SVC connections are accepted but not charged (acceptCalls), or whether they are refused (refuseCalls). Enumeration: 'acceptCalls': 1, 'refuseCalls': 2. |
| chasAccountFileCountThreshold | 1.3.6.1.4.1.800.2.1.7.25 | integer | read-write |
If more than this number of accounting files are awaiting collection, a trap will be generated. |
| chasAccountName | 1.3.6.1.4.1.800.2.1.7.26 | octet string | no-access |
The fully qualified path name of the most recently terminated accounting file. This object is not intended to be accessed directly. It is defined for use in accounting-related traps. |
| chasAccountMake | 1.3.6.1.4.1.800.2.1.7.27 | integer | read-write |
When chasAccountMake is enabled, the accounting data are collected Enumeration: 'disabled': 2, 'enabled': 1. |
| chasAccountSwitch | 1.3.6.1.4.1.800.2.1.7.28 | integer | read-write |
When chasAccountSwitch is enabled, it forces a switchover from the current to the alternate collection device if on the fly charging is enabled. It has no effect otherwise Enumeration: 'disabled': 2, 'enabled': 1. |
| chasFanTray | 1.3.6.1.4.1.800.2.1.8 | |||
| chasFanTray1State | 1.3.6.1.4.1.800.2.1.8.1 | xylanftstatetype | read-only |
The status of fan tray 1. |
| chasFanTray2State | 1.3.6.1.4.1.800.2.1.8.2 | xylanftstatetype | read-only |
The status of fan tray 2. |
| chasDateAndTime | 1.3.6.1.4.1.800.2.1.9 | |||
| chasCurrentDateAndTime | 1.3.6.1.4.1.800.2.1.9.1 | octet string | read-write |
Current date and time. Format - yyyymmddThhmmss yyyy - year, mm - month, dd - day, 'T' separator, hh - hour, mm - month, ss - second. |
| chasTimezoneName | 1.3.6.1.4.1.800.2.1.9.2 | displaystring | read-write |
String containing the time zone name. nzst - New Zealand Time aest - Australia East Time gst - Guam Time acst - Australia Central Time jst - Japan Time kst - Korean Time awst - Australia West Time msk - Moscow Time eet - Eastern European Time cet - Central European Time met - Middle European Time bst - British Time wet - Western European Time gmt - Greenwich Mean Time wat - West Africa Time nst - Newfoundland Time ast - Atlantic Time est - Eastern Time (USA) cst - Cnetral Time (USA) mst - Mountain Time (USA) pst - Pacific Time (USA) akst - Alaska Time hst - Hawaii Time Returns none is not set. |
| chasTimezoneOffset | 1.3.6.1.4.1.800.2.1.9.3 | integer | read-write |
Time zone offset + or - minutes from UTC. |
| chasTimezoneDstAdmin | 1.3.6.1.4.1.800.2.1.9.4 | integer | read-write |
Daylight Savings Time enable/disable. Enumeration: 'enable': 1, 'disable': 2. |
| chasTimezoneDst | 1.3.6.1.4.1.800.2.1.9.5 | octet string | read-write |
Time and date information for the chassis. wdmmhhmmwdmmhhmmHHMM | start|| end ||offset| w-d-mm,hh:mm,w-d-mm,hh:mm,HH:MM w - Week (first(1), second(2), third(3), fourth(4), last(>4)) d - Day (Sunday(1), ..., Saturday(7)) m - Month (January(1), ..., December(12)) hh:mm - time of day DST changes (0-23:0-59) HH:MM - offset DST changes by. (0-23:0-59) Example: 11040200611002000100 - Starts First Sunday in April at 2:00 Ends Last Sunday in October at 2:00 Time changes by 1:00 hr. Returns disabled if disabled. |