Support For Allied Telesis Enterprise Mibs in Alliedware Plus™
Support For Allied Telesis Enterprise Mibs in Alliedware Plus™
Support For Allied Telesis Enterprise Mibs in Alliedware Plus™
Introduction
This guide describes SNMP Management Information Bases (MIBs) and managed objects
supported by the AlliedWare Plus™ Operating System. The following topics are covered:
“Allied Telesis Enterprise MIB” on page 7 describes the objects implemented in the Allied Telesis
Enterprise MIB
“Public MIBs” on page 134 describes the public MIBs supported by the AlliedWare PlusTM
Operating System, and any variations from the standard implementation.
Contents
Introduction .........................................................................................................................................1
Products and software version that apply to this guide ...............................................................4
Related documents.......................................................................................................................4
About MIBs ...................................................................................................................................4
About SNMP .................................................................................................................................4
Obtaining MIBs .............................................................................................................................4
Loading MIBs................................................................................................................................5
AT-UDLD-MIB ...........................................................................................................................122
AT-UFO-MIB .............................................................................................................................123
AT-USER-MIB ...........................................................................................................................124
AT-VCSTACK-MIB ....................................................................................................................126
AT-VLAN-MIB ............................................................................................................................131
AT-XEM-MIB .............................................................................................................................133
This guide applies to all AlliedWare Plus™ products, running version 5.4.5-1 or later.
Related documents
The following documents give more information about the MIBs and SNMP on AlliedWare Plus
products:
These documents are available from the above links on our website at alliedtelesis.com.
About MIBs
A MIB is a collection of managed objects organized into a tree-like hierarchy of nodes in which the
managed objects form the leaves. Within the tree, each node is identified by a non-negative integer
identifier that is unique among the node’s siblings. The address, or object identifier, of any node
within the tree is expressed as a series of dot-delimited node identifiers that trace the path from the
root of the tree to the node. For example, the object identifier for the sysDescr object is
1.3.6.1.2.1.1.1.
Note: This guide does not indicate which MIB objects are not-accessible (and therefore cannot be
queried directly). Please consult the MIB files for that information.
About SNMP
A Network Management Station (NMS) uses a protocol known as Simple Network Management
Protocol (SNMP) to query or change the values of objects in the MIB of managed devices.
A managed device uses SNMP to respond to queries from an NMS, and to send unsolicited alerts
(traps) to an NMS in response to events.
Obtaining MIBs
You can download MIBs from the following locations:
Allied Telesis Enterprise MIB The MIB files are available with the software files from the Support area at:
www.alliedtelesis.com/support/software.
Public MIBs defined in RFCs www.rfc-editor.org/rfc.html.
IANAifType-MIB www.iana.org/assignments/ianaiftype-mib.
Loading MIBs
Individual MIBs define a portion of the total MIB for a device. For example, the MAU-MIB defines
objects for managing IEEE 802.3 Medium Attachment Units (MAUs), and forms a sub-tree under
mib-2 with the object identifier snmpDot3MauMgt (1.3.6.1.2.1.26).
All the objects within a MIB are assigned object identifiers relative to a parent object. Most MIBs
import the object identifier of the parent object, along with other object identifiers, textual
conventions, macros and syntax types from the MIBs where they are defined. This creates
dependencies between MIBs.
Some network management stations and MIB compilers will generate errors if you load a MIB that
depends on another MIB that has not already been loaded. To avoid these errors, we recommend
that you load MIBs in the following order:
1. RFC 1212
RFC 1239
RFC 2257
RFC 3410.
7. AT-PRODUCT-MIB
AT-BOARDS-MIB
AT-SYSINFO-MIB
AT-XEM-MIB
AT-ENVMONv2-MIB
AT-VCSTACK-MIB
AT-PORTINFO-MIB
AT-MIBVERSION-MIB
AT-VLAN-MIB
AT-USER-MIB
AT-RESOURCE-MIB
AT-LICENSE-MIB
AT-HHM-MIB
AT-LINKMON-MIB
AT-LINKTRAP-MIB
AT-ALMMON-MIB
AT-FIBER-MONITORING-MIB
AT-PLUGGABLES-DIAGNOSTICS-MIB
AT-TRIGGER-MIB
AT-LOOPPROTECT-MIB
AT-SETUP-MIB
AT-DNS-CLIENT-MIB
AT-NTP-MIB
AT-QOSv2-MIB
AT-PTP-MIB
AT-EPSRV2-MIB
AT-UDLD-MIB
AT-DHCPSN-MIB
ATFILEV2-MIB
AT-LOG-MIB
AT-HHM-MIB
AT-ATMF-MIB
AT-G8032V2-MIB
AT-UFO-MIB
This document describes only those portions of the Allied Telesis Enterprise MIB supported by the
AlliedWare Plus™ Operating System. Figure 1 shows the structure of the Allied Telesis Enterprise
MIB. Each component MIB is detailed in the following sections of this chapter.
Figure 1: The Allied Telesis Enterprise MIB sub-tree of the Internet-standard Management Information Base (MIB)
internet
OID 1.3.6.1
alliedTelesis (207)
brouterMib (4)
industrial bridgeRouter (1) routerSwitch (14)
switch (24) atRouter (4)
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces (5) protocols (6) Agents (7)
MIB_at.eps
AT-SMI-MIB
AT-SMI-MIB defines the high-level structure and root objects of the Allied Telesis Enterprise MIB, see
Table 2. The object identifier is alliedTelesis { enterprises 207 } OID 1.3.6.1.4.1.207. These objects
are imported by other component MIBs of the Allied Telesis Enterprise MIB.
alliedTelesis { enterprises 207 } Root of the Allied Telesis Enterprise MIB under the private(4) node defined in
1.3.6.1.4.1.207 RFC1155-SMI.
products { alliedTelesis 1 } Sub-tree of all product OIDs. Described in “AT-PRODUCTS-MIB” on page 81.
1.3.6.1.4.1.207.1
bridgeRouter { products 1 } Sub-tree of bridge product MIB objects (not applicable for AlliedWare Plus).
1.3.6.1.4.1.207.1.1
routerSwitch { products 14 } Sub-tree for all router and switch product MIB objects.
1.3.6.1.4.1.207.1.2
objects { atRouter 1 } Sub-tree of OIDs for boards, releases, interface types, and chips.
1.3.6.1.4.1.207.8.4.4.1
traps { atRouter 2 } Sub-tree for generic traps (not applicable for AlliedWare Plus).
1.3.6.1.4.1.207.8.4.4.2
arInterfaces { atRouter 5 } Sub-tree of objects describing boards, slots and physical interfaces.
1.3.6.1.4.1.207.8.4.4.5
protocols { atRouter 6 } Sub-tree of OIDs for protocols.
1.3.6.1.4.1.207.8.4.4.6
Table 3 lists the major modules of the AT-SMI-MIB grouped by their object identifiers.
AT-SMI-MIB 1.3.6.1.4.1.207 This section describes the structure of management information for
the Allied Telesis Enterprise object, alliedTelesis { 1.3.6.1.4.1.207 }.
See “AT-SMI-MIB” on page 8.
AT-PRODUCTS-MIB 1.3.6.1.4.1.207.1 Object identifiers for Allied Telesis products. See
“AT-PRODUCTS-MIB” on page 81.
AT-BOARDS-MIB 1.3.6.1.4.1.207.8.4.4.1.1 Object identifiers for boards, interface types, and chip sets. See
“AT-BOARDS-MIB” on page 18.
AT-SYSINFO-MIB 1.3.6.1.4.1.207.8.4.4.3 Objects that describe generic system information and environmental
monitoring. See “AT-SYSINFO-MIB” on page 116.
AT-VCSTACK-MIB 1.3.6.1.4.1.207.8.4.4.3.13 Objects for managing Virtual Chassis Stacking (VCS). See
“AT-VCSTACK-MIB” on page 125.
AT-PORTINFO-MIB 1.3.6.1.4.1.207.8.4.4.3.14 Objects for managing interface port objects such as transceivers. See
“AT-PORTINFO-MIB” on page 79.
AT-MIBVERSION-MIB 1.3.6.1.4.1.207.8.4.4.3.15 Objects to display the last software release that contained changes to
the support AT Enterprise MIB definition files. See
“AT-MIBVERSION-MIB” on page 71.
AT-VLAN-MIB 1.3.6.1.4.1.207.8.4.4.3.16 Objects for managing VLANS. See “AT-VLAN-MIB” on page 130.
AT-USER-MIB 1.3.6.1.4.1.207.8.4.4.3.20 Objects for displaying information of users currently logged into a
device, or configured in the Local User Data base of the device. See
“AT-USER-MIB” on page 123.
AT-RESOURCE-MIB 1.3.6.1.4.1.207.8.4.4.3.21 Objects for displaying system hardware resource information. See
“AT-RESOURCE-MIB” on page 107.
AT-TRIGGER-MIB 1.3.6.1.4.1.207.8.4.4.4.53 Objects for managing triggers. See “AT-TRIGGER-MIB” on page 119.
AT-LOOPPROTECT-MIB 1.3.6.1.4.1.207.8.4.4.4.54 Objects for managing Allied Telesis Loop Protection. See
“AT-LOOPPROTECT-MIB” on page 69.
AT-SETUP-MIB 1.3.6.1.4.1.207.8.4.4.4.500 Objects for managing software installation and configuration files.
See “AT-SETUP-MIB” on page 108.
AT-DNS-CLIENT-MIB 1.3.6.1.4.1.207.8.4.4.4.501 Objects for managing Allied Telesis Domain Name System (DNS)
Client Configuration. See “AT-DNS-CLIENT-MIB” on page 32.
AT-NTP-MIB 1.3.6.1.4.1.207.8.4.4.4.502 Objects for managing Allied Telesis Network Time Protocol (NTP)
configuration. See “AT-NTP-MIB” on page 72.
AT-QOSv2-MIB 1.3.6.1.4.1.207.8.4.4.4.503 Objects for managing Allied Telesis Quality of Service (QoS)
configuration. See “AT-QOSv2-MIB” on page 106.
AT-PTP-MIB 1.3.6.1.4.1.207.8.4.4.4.504 Objects for managing Allied Telesis Network Precision Time Protocol
(PTP) configuration. See “AT-PTP-MIB” on page 87.
AT-EPSRv2-MIB 1.3.6.1.4.1.207.8.4.4.4.536 Objects for managing Allied Telesis Ethernet Automatic Protection
Switching (EPSR). See “AT-EPSRv2-MIB” on page 41.
AT-DHCPSN-MIB 1.3.6.1.4.1.207.8.4.4.4.537 Objects for managing Allied Telesis Dynamic Host Configuration
Protocol (DHCP) Snooping. See “AT-DHCPSN-MIB” on page 29.
AT-UDLD-MIB 1.3.6.1.4.1.207.8.4.4.4.550 Objects for managing Allied Telesis UniDirectional Link Detection
(UDLD). See “AT-UDLD-MIB” on page 121.
AT-FILEv2-MIB 1.3.6.1.4.1.207.8.4.4.4.600 Objects for displaying and managing file content on local, stacked,
and remote sources. See “AT-FILEv2-MIB” on page 46.
AT-LOG-MIB 1.3.6.1.4.1.207.8.4.4.4.601 Objects for listing log entries from the buffered and permanent logs.
See “AT-LOG-MIB” on page 67.
AT-IP-MIB 1.3.6.1.4.1.207.8.4.4.4.602 Objects for Allied Telesis specific IP address management. See
“AT-IP-MIB” on page 58.
AT-ATMF-MIB 1.3.6.1.4.1.207.8.4.4.4.603 Objects for managing ATMF. See “AT-ATMF-MIB” on page 13.
AT-G8032v2-MIB 1.3.6.1.4.1.207.8.4.4.4.604 Objects for managing Ethernet Protection Ring Switching (EPRS).
See “AT-G8032v2-MIB” on page 56.
AT-UFO-MIB 1.3.6.1.4.1.207.8.4.4.4.605 Objects for Allied Telesis Upstream Forwarding Only (UFO) for private
VLANs. See “AT-UFO-MIB” on page 122.
AT-LINKMON-MIB 1.3.6.1.4.1.207.8.4.4.4.606 Objects for Allied Telesis Link Monitoring for collecting and reporting
link metrics. See “AT-LINKMON-MIB” on page 63.
AT-ALMMON-MIB
AT-ALMMON-MIB defines objects for managing and reporting device alarms, see Table 4. Objects in
this group have the object identifier atAlmMon { sysinfo 26 } OID 1.3.6.1.4.1.207.8.4.4.3.26.
Table 4: Objects defined by the AT-ALMMON-MIB
atAlmMonActionStackMemberId { atAlmMonActionEntry 1 } The index of the stack member of this alarm action.
207.8.4.4.3.26.1.1.1 Read only.
atAlmMonActionIndex { atAlmMonActionEntry 2 } The numeric identifier of this alarm action. Read only.
207.8.4.4.3.26.1.1.2
atAlmMonAlarmType { alAlmMonActionEntry 3 } The type of alarm that this action monitors. Read only.
207.8.4.4.3.26.1.1.3 Values can be:
■ externalPSU (1)
■ epsr (2)
■ contactInput (3)
■ portLinkDown (4)
■ loopDetect (5)
■ mainPse (6)
■ portPoeFailure (7)
■ temperature (8)
■ g8032 (9)
■ ufo (10)
atAlmMonAlarmTypeSelection { atAlmMonActionEntry 4 } The 1-based index of the alarm of the particular type
(as categorized by AlmMonAlarmType).
atAlmMonAbnormalState { atAlmMonActionEntry 10 } Indicates/sets the abnormal (i.e., alarm active) state for
a contact input. Only used for contactInput alarm
monitors, ignored for all other types. Read-write.
Values can be:
■ open (1)
■ closed (2).
atAlmMonActionState { atAlmMonActionEntry 11 } Indicates the current state of this alarm monitor. Read
only. Values can be:
■ Inactive (1)
■ Active (2).
AT-ATMF-MIB
The ATMF-MIB defines objects for managing the Allied Telesis Management Framework (AMF).
Objects and triggers are shown diagrammatically in Figure 2 and Figure 3. Objects in this group
have the object identifier atmf { modules 603 } OID 1.3.6.1.4.1.207.8.4.4.4.603.
enterprises (1)
alliedTelesis (207)
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces protocols (6)
ATMF_mib_tree-Upper.eps_
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces protocols (6)
at-Atmf (603)
atAtmfTrapNetworkName (3)
atAtmfNodeStatusChangeTrap (2)
atAtmfTrapNodeName (1)
atAtmfTrapNodeStatusChange (2) atAtmfTrapInterfaceName (4)
atAtmfTrapNetworkName (3)
atAtmfTrapBackupStatus
atAtmfTrapInterfaceName(5)(4)
atAtmfNodeRecoveryTrap (3)
atAtmfTrapNodeName (1)
atAtmfTrapMasterNodeName (2) atAtmfTrapNodeStatusChange
atAtmfTrapInterfaceName (4) (6)
atAtmfTrapNodeRecoveryStatus (3)
atAtmfTrapInterfaceStatusChange
atAtmfTrapInterfaceName (4) (7)
atAtmfInterfaceStatusChangeTrap (4)
atAtmfTrapNodeName (1) atAtmfTrapNodeRecoveryStatus
atAtmfTrapInterfaceName (4) (8)
atAtmfTrapInterfaceName (2)
atAtmfTrapInterfaceStatusChange (3)
atAtmfTrapMediaType
atAtmfTrapInterfaceName
(9) (4)
atAtmfIExternalMediaLowMemoryTrap (5)
atAtmfTrapMasterNodeName (1) atAtmfTrapMediaTotal
atAtmfTrapInterfaceName
(10) (4)
atAtmfTrapMediaType (2)
atAtmfTrapMediaTotal (3)
atAtmfTrapMediaFree (4) atAtmfTrapMediaFree
atAtmfTrapInterfaceName
(11) (4)
atAtmfRollingRebootCompleteTrap (6)
atAtmfTrapRollingRebootStatus
atAtmfTrapInterfaceName
atAtmfTrapInterfaceName (4)
(4) (12)
atAtmfTrapNodeName (1)
atAtmfTrapRollingRebootStatus (2)
atAtmfTrapRollingRebootReleaseName
atAtmfTrapInterfaceName
atAtmfTrapInterfaceName (4)
(4) (13)
atAtmfRollingRebootReleaseCompleteTrap (7)
atAtmfTrapRollingRebootStatus
atAtmfTrapInterfaceName
atAtmfTrapInterfaceName (4)
(4) (14)
atAtmfTrapNodeName (1)
atAtmfTrapRollingRebootStatus (2)
atAtmfTrapRollingRebootReleaseName (3)
atAtmfTrapRollingRebootReleaseStatus (4)
atAtmfSummaryStatus (2)
disabled (1) atAtmfNodeName
enabled (2)
atAtmfSummaryRole (3)
member (1)
master (2)
atAtmfSummaryNetworkName (4)
atAtmfSummaryParentName (5)
atAtmfSummaryCoreDistance (6)
atAtmfSummaryDomainId (7)
atAtmfSummaryRestrictedLogin (8)
disabled (1)
enabled (2)
Table 5: AT-ATMF-MIB
atmf { modules 603 } Root of the Allied Telesis ATMF MIB under the
1.3.6.1.4.1.207.8.4.4.4.603 private(4) node defined in RFC1155-SMI.
atAtmfTrapNodeStatusChange { atAtmfTrapVariable 6 } An ATMF trap node has changed its status in the
ATMF network. Its objects are:
■ left(1)
■ joined(2).
atAtmfSummaryRole { atAtmfSummary 3 } The role configured for this ATMF device, either
Master or Member.
atAtmfSummaryNetworkName { atAtmfSummary 4 } The ATMF network that a particular node
belongs to.
atAtmfSummaryParentName { atAtmfSummary 5 } The parent name of the node or 'none'.
AT-BOARDS-MIB
AT-BOARDS-MIB defines object identifiers for components of Allied Telesis products—base CPU
and expansion boards, interface types, and chip sets. Objects in this MIB have the object identifier
objects { atRouter 1 } OID 1.3.6.1.4.1.207.8.4.4.1, and are organized into the following groups:
Base CPU and expansion boards, see Table 6. These object identifiers are for use with the
hrDeviceID object in the Host Resources MIB (see “Public MIBs” on page 134).
pprx90024XTN { boards 281 } x900-24XT, Enhanced Gigabit Layer 3+ Expandable Switch, 24 x 10/100/
1000BASE-T copper ports (RJ-45 connectors), 2 x 20 Gigabit expansion
bays, NEBS compliant.
pprSwitchBladex908 { boards 282 } SwitchBlade x908, 8 Slot Layer 3 Switch Chassis.
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprAtSBx81CFC400 { boards 317 } AT-SBx81CFC, Control Fabric Card for SwitchBlade x8112.
pprAtSBxPWRSYSAC { boards 320 } AT-SBxPWR SYS/AC, system power supply unit for the SwitchBlade
x8112 (AC input).
pprAtSBxPWRPOEAC { boards 321 } AT-SBxPWR POE/AC, PoE power supply unit for the SwitchBlade x8112
(AC input).
pprAtSBxFAN12 { boards 322 } AT-SBxFAN12, fan tray for the SwitchBlade x8112.
pprAtPWR05DC { boards 323 } AT-PWR05, DC power supply unit for SwitchBlade x908.
pprXem2XT { boards 325 } XEM-2XT, Expansion Module, 2 x 10Gbe copper XEM port.
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprXem24T { boards 356 } AT-XEM-24T, Expansion Module, 24 x 10/100/1000T (RJ Point 5) ports.
pprx51028GTX { boards 370 } AT-x510-28GTX, 24 10/100/1000Base-T ports and four 10Gb/s SFP+
ports.
pprx51028GPX { boards 371 } AT-x510-28GPX, 24 10/100/1000Base-T ports, four 10 Gb/s SFP+ ports
and PSE function available on pins 1/2 and 3/6 (Mode A) of every copper
port.
pprx51028GSX { boards 372 } AT-x510-28GSX, 24 100/1000 SFP ports and four 10 Gb/s SFP+ ports.
pprx51052GTX { boards 373 } AT-x510-52GTX, 48 10/100/1000Base-T ports and four 10 Gb/s SFP+
ports.
pprx51052GPX { boards 374 } AT-x510-52GPX, 48 10/100/1000Base-T ports, four 10 Gb/s SFP+ ports
and PSE function available on pins 1/2 and 3/6 (Mode A) of every copper
port.
pprAtSBx8106 { boards 375 } AT-SBx8106, SwitchBlade x8106 chassis.
pprAtSBxFAN06 { boards 376 } AT-SBxFAN06, fan tray for the SwitchBlade x8106.
pprAtSBx81CFC960 { boards 377 } AT-SBx81CFC960, Control Fabric Card for SwitchBlade x8100 Series
chassis, four 10GbE SFP+ ports.
pprx510DP52GTX { boards 386 } AT-x510DP-52GTX, 48 10/100/1000Base-T ports and four 10 Gb/s SFP+
ports.
pprxIX528GPX { boards 387 } AT-IX5-28GPX, 24 10/100/1000Base-T ports, four 10 Gb/s SFP+ ports
and PSE function available on pins 1/2 and 3/6 (Mode A) of every copper
port.
pprx93028GTX { boards 388 } AT-x930-28GTX, 24 1000BASE-T ports, 4 x 10 Gb/s SFP+ ports.
pprx93028GSTX { boards 390 } AT-x930-28GSTX, 24 1000BASE-T ports (combo), 24 x 1000 SFP ports
(combo), 4 x 10 Gb/s SFP+ ports.
pprx93052GTX { boards 391 } AT-x930-52GTX, 48 10/100/1000BASE-T ports, 4 x 10 Gb/s SFP+ ports.
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprx31026FT { boards 393 } AT-x310-26FT, 24 10/100 Base-T ports, two 10/100/1000Base-T ports,
and four 10 Gb/s SFP+ ports.
pprx31050FT { boards 394 } AT-x310-50FT, 48 10/100 Base-T ports, two 10/100/1000Base-T ports,
and four 10 Gb/s SFP+ ports.
pprx31026FP { boards 395 } AT-x310-26FP, 24 10/100 Base-T ports, two 10/100/1000Base-T ports,
four 10 Gb/s SFP+ ports, plus PSE function available on pins 1/2 and 3/
6 (Mode A) of every copper port.
pprx31050FP { boards 396 } AT-x310-50FP, 48 10/100 Base-T ports, two 10/100/1000Base-T ports,
four 10 Gb/s SFP+ ports, plus PSE function available on pins 1/2 and 3/
6 (Mode A) of every copper port.
pprx23010GP { boards 405 } AT-x230-10GP, 8 10/100/1000BASE-RJ-45 ports, 2 1000Base SFP ports.
pprx23018GP { boards 406 } AT-x 230-18GP, 16 10/100/1000BASE RJ-45 ports and 2 1000BASE SFP
ports.
pprx23028GP { boards 407 } AT-x 230-28GP, 24 10/100/1000BASE RJ-45 ports and 4 1000BASE SFP
ports.
pprIE2006GT { boards 410 } IE200-6GT, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports and 2 x SFP uplinks (100/1000X).
pprIE2006GP { boards 411 } IE200-6GP, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports (with 802.3at PoE+) and 2 x SFP uplinks (100/1000X).
pprIE2006GPW { boards 412 } IE200-6GPW, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports (with 802.3at PoE+) and 2 x SFP uplinks (100/1000X) and
802.11bgn wireless.
pprIE2006FP { boards 430 } AT-IE200-6FP, 4 × 10/100TX ports (PoE+ support) and 2 × 100/1000X SFP
Industrial switch.
pprx510DP28GTX { boards 431 } AT-x510DP-28GTX, 24 10/100/1000BASE RJ-45 ports, 4 x SFP+ ports.
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprIE30012GP { boards 439 } Industrial Ethernet Layer 3 Switch Gigabit 12-port IE300-12GT.
pprSH23028GT { boards 475 } AT-x230-18GT L3 switch with 16 x 10/100/1000T ports and 2 x 100/
1000X SFP ports.
pprAtFS980M9 { boards 476 } AT-FS980M/9, 8 x 10/100TX ports and 1 combo (10/100/1000T or 100/
1000X SFP) uplink port.
pprAtFS980M9PS { boards 477 } AT-FS980M/9PS, 8 x 10/100TX PoE+ ports and 1 combo (10/100/1000T
or 100/1000X SFP) uplink port.
pprAtFS980M18 { boards 478 } AT-FS980M/18, 16 x 10/100TX ports and 2 combo (10/100/1000T or 100/
1000X SFP) uplink ports.
pprAtFS980M18PS { boards 479 } AT-FS980M/18PS, 16 x 10/100TX PoE+ ports and 2 combo (10/100/
1000T or 100/1000X SFP) uplink ports.
pprAtFS980M28 { boards 480 } AT-FS980M/28, 24 x 10/100TX ports and 4 x 100/1000X SFP uplink/
stacking ports.
pprAtFS980M28PS { boards 481 } AT-FS980M/28PS, 24 x 10/100TX PoE+ ports and 4 x 100/1000X SFP
uplink/stacking ports.
pprAtFS980M52 { boards 482 } AT-FS980M/52, 48 x 10/100TX ports and 4 x 100/1000X SFP uplink/
stacking ports.
pprAtFS980M52PS { boards 483 } AT-FS980M/52PS, 48 x 10/100TX PoE+ ports and 4 x 100/1000X SFP
uplink/stacking ports.
pprSBx908G2 { boards 484 } AT-SBx908 GEN 2, High capacity Layer 3+ modular switch chassis with
8 x high speed expansion bays.
pprAtFan08 { boards 486 } AT-FAN08, Hot-swappable fan module for the SwitchBlade x908
Generation 2.
pprAtXem2QS4 { boards 487 } AT-XEM2-4QS, 4 x 40G QSFP+ ports.
pprx55018XTQ { boards 491 } AT- x550-18XTQ, stackable 10 Gigabit Layer 3 switch is a high-
performing and feature-rich solution, with 16 x 1G/10G copper Ethernet
ports and 2 x 40G uplinks.
pprx55018XSQ { boards 492 } AT-x550-18XSQ, stackable 10 Gigabit Layer 3 switch is a high-performing
and feature-rich solution, with 16 x 1G/10G SFP+ ports and 2 x 40G
uplinks.
pprx55018XSPQm { boards 493 } AT-x550-18XSPQm, stackable 10 Gigabit Layer 3 switch is a high-
performing and feature-rich solution, with 8 x 1G/10G SFP+ slots, 8 x 1G/
2.5G/5G/10G PoE+ Ethernet ports, and 2 x 40G uplinks.
pprAtXem2CQ1 { boards 494 } AT-XEM2-1CQ, 1 x 100G QSFP28 port module.
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprx95028XSQ { boards 549 } AT-950-28XSQ, 24 x 1/10G SFP+ ports, 4 x 40G/100G uplink ports, and
1 x expansion bay.
pprx230L17GT { boards 556 } L3 switch with 16 x 10/100/1000T ports and 1 x 100/1000X SFP port.
pprx230L26GT { boards 557 } L3 switch with 24 x 10/100/1000T ports and 2 x 100/1000X SFP ports.
pprx32010GH { boards 558 } 8-port 10/100/1000T PoE++ switch with 2 SFP ports, and 3 external PSU
ports.
pprx32011GPT { boards 559 } 8-port 10/100/1000T PoE+ switch with 2 SFP ports, one AC adapter
port(4), and one PoE-in port(5) (supporting PD and PoE pass-through)
Table 6: Object identifiers for base CPU and expansion boards (continued)
pprx55018XSQV2 { boards 563 } AT-x550-18XSQ, stackable 10 Gigabit Layer 3 switch 16 x 1G/10G SFP+
ports and 2 x 40G uplinks.
pprx530L28GTX { boards 568 } AT-x530L-28GTX, 24-port 10/100/1000T stackable switch with 4 SFP+
ports and 2 fixed power supplies.
pprx530L28GPX { boards 569 } AT-x530L-28GPX, 24-port 10/100/1000T PoE+ stackable switch with 4
SFP+ ports and 2 fixed power supplies.
pprx530L52GTX { boards 570 } AT-x530L-52GTX, 48-port 10/100/1000T stackable switch with 4 SFP+
ports and 2 fixed power supplies.
pprx530L52GPX { boards 571 } AT-x530L-52GPX, 48-port .10/100/1000T PoE+ stackable switch with 4
SFP+ ports and 2 fixed power supplies
pprAtFS980M28DP { boards 573 } AT-FS980M/28DP, 24-port 10/100TX PoE+ switch with 4 SFP
uplinks and dual fixed AC power supply.
pprAtSBx81FAN12v2 { boards 575 } AT-x81FAN12, contains four fans, temperature sensors and controller
board for SBx8106 chassis.
pprx95052XSQ { boards 577 } AT-x950-52XSQ, 48 x SFP+, 4 x QSFP+/QSFP28.
pprAtGS980EM10H { boards 578 } AT-GS980EM/10H, 8-port 10/100/1000T PoE++ switch with 2 SFP ports,
and 3 external PSU ports.
pprAtGS980EM11PT { boards 579 } AT-GS980EM/11PT, 8-port 10/100/1000 PoE+ switch with 2 SPF ports,
one AC adapter port and one PoE-in port (supporting PD and PoE pass-
through).
pprVAPA { boards 580 } AT-VAPA, Virtual AMF Plus Appliance.
pprAtSBx81GP24v2 { boards 581 } AT-SBx81GP24 v2, 24-port 10/100/1000T PoE+ Ethernet line card.
iftypes { objects 3 } A subtree beneath which interface type ids are assigned.
AT-CHASSIS-MIB
See Table 9 for the list of objects defined in the AT-CHASSIS-MIB. These objects manage chassis-
based devices. Objects in this group have the object identifier chassis { sysinfo 23 } OID
1.3.6.1.4.1.207.8.4.4.3.23.
chassisCardRoleChangeNotify { chassis 0.1 } Notification generated when the Control Fabric Card’s
role changes.
chassisCardJoinNotify { chassis 0.2 } Notification generated when a line card connects to the
Control Fabric Card.
chassisCardLeaveNotify { chassis 0.3 } Notification generated when a line card detaches from
the Control Fabric Card.
slotNumber { chassis 0.4 } The slot number of the line card or Control Fabric Card
that has changed.
Has the numeric range 1-12.
chassisRole { chassis 0.5 } The Control Fabric Card’s role in the chassis. Can be
one of the following:
■ leaving (1)
■ discovering (2)
■ synchronizing (3)
■ standbyMember (4)
■ pendingMaster (5)
■ disabledMaster (6)
■ activeMaster (7).
chassisCardTable { chassis 1 } A list of cards presented on the device.
chassisCardSlot { chassis 1.1.1 } The slot number that the card is installed in.
chassisCardBoardOID { chassis 1.1.2 } The object ID used to identify the AT board type as
defined in the AT Enterprise MIB.
chassisCardName { chassis 1.1.3 } The name of the card; e.g. AT-SBx81CFC400, AT-
SBx81CFC960 for controller cards; and
AT-SBx81GP24, AT-SBx81GT24, AT-SBx81GS24, AT-
SBx81XS6 for line cards; “unknown” is displayed for
unsupported hardware.
chassisCardState { chassis 1.1.4 } The current state of the card. The valid state is in one of
the following:
■ unknown(1),
■ configuring(2),
■ syncing(3),
■ online(4),
■ syncingFirmware(5),
■ joining(6),
■ incompatibleSW(7),
■ disabled(8),
■ initializing(9),
■ booting(10),
■ unsupportedHW(11),
■ provisioned(12).
chassisCardControllerState { chassis 1.1.5 } The current state of the controller card, in addition to
the card state.
The valid state is in one of the following:
■ unknown(1)
■ active(2)
■ standby(3).
chassiCardSwVersion { chassis 1.1.6 } The software version that the card is running. When
feature ISSU (In Service Software Update) is supported,
there are situations when a LIF card may run a different
software version to that running on the active CFC.
chassismappingtable { chassis 2 } A list of cards existing on the device.
chassismappingentry { chassis 2.1 } Other SNMP SET/GET operations that refer to a card in
a chassis using a single integer index, i.e. a 'node-ID'.
This table entry maps a node-ID value to the VCS
member-ID and slot number of the card.
For example, node-ID 17 would map to card 2.5 (VCS
member-ID 2, slot 5).
chassisNodeId { chassis 2.1.1 } The node ID of a chassis card.
chassisVCSMemberId { chassis 2.1.2 } The VCS member ID of the chassis that contains the
card.
chassisSlotNumber { chassis 2.1.3 } The chassis slot number that the card is installed in.
chassisNodeDisplayString { chassis 2.1.4 } The name of the chassis card, e.g. 'card 1.5'.
chassisNodeStateString { chassis 2.1.5 } The current state of the card located in the bay. If the
card is present, then its state is displayed as “online”. If
the bay is provisioned then the display will be
“Provisioned”.
AT-DHCPSN-MIB
This MIB contains objects for displaying and managing DHCP snooping and ARP security
information on the switch, see Table 10. The objects reside in the module atDhcpsn { modules 537 }
OID 1.3.6.1.4.1.207.8.4.4.4.537, organized in the following groups:
atDhcpsn { modules 537 } or This MIB file contains definitions of managed objects for DHCP
1.3.6.1.4.1.207.8.4.4.4.537 Snooping in AlliedWare Plus.
atDhcpsnVariablesTable { atDhcpsn 1 } The DHCP Snooping table. This table contains rows of DHCP
Snooping information.
atDhcpsnVariablesEntry { atDhcpsnVariablesTable 1 } A set of parameters that describe the DHCP Snooping features.
atDhcpsnIfIndex { atDhcpsnVariablesEntry 1 } Ifindex of the port that the packet was received on.
atDhcpsnVid { atDhcpsnVariablesEntry 2 } VLAN ID of the port that the packet was received on.
atDhcpsnSmac { atDhcpsnVariablesEntry 3 } Source MAC address of the packet that caused the trap.
atDhcpsnOpcode { atDhcpsnVariablesEntry 4 } Opcode value of the BOOTP packet that caused the trap. Only
bootpRequest(1) or bootpReply(2) is valid.
atDhcpsnCiaddr { atDhcpsnVariablesEntry 5 } Ciaddr value of the BOOTP packet that caused the trap.
atDhcpsnYiaddr { atDhcpsnVariablesEntry 6 } Yiaddr value of the BOOTP packet that caused the trap.
atDhcpsnGiaddr { atDhcpsnVariablesEntry 7 } Giaddr value of the BOOTP packet that caused the trap.
atDhcpsnSiaddr { atDhcpsnVariablesEntry 8 } Siaddr value of the BOOTP packet that caused the trap.
atDhcpsnChaddr { atDhcpsnVariablesEntry 9 } Chaddr value of the BOOTP packet that caused the trap.
atArpsecVariablesTable { atDhcpsn 2 } The ARP Security table. This table contains rows of DHCP
Snooping ARP Security information.
atArpsecVariablesEntry { atArpsecVariablesTable 1 } A set of parameters that describe the DHCP Snooping ARP
Security features.
atArpsecIfIndex { atArpsecVariablesEntry 1 } Ifindex of the port that the ARP packet was received on.
atArpsecVid { atArpsecVariablesEntry 4 } VLAN ID of the port that the ARP packet was received on.
AT-DNS-CLIENT-MIB
AT-DNS-CLIENT-MIB contains definitions of managed objects for the Allied Telesis DNS Client
Configuration. Objects in this group have the object identifier atDns { Modules 501 } OID
1.3.6.1.4.1.207.8.4.4.4.501. Table 11 lists the objects supported by the AlliedWare PlusTM Operating
System.
atDNSServerIndexNext { atDnsClient 1 } The next available value for the object ‘atDNSServerIndex’. The
value is used by a management application to create an entry in
the ‘atDNSServerTable’.
atDNSServerTable { atDnsClient 2 } Table of information about the Domain Name System (DNS)
Server configurations in the system, indexed by
‘atDNSServerIndex’.
atDNSServerEntry { atDNSServerTable 1 } Information about a single DNS Server Configuration.
atDNSServerAddrType { atDNSServerEntry 2 } The Internet Address Type of the ‘atDNSServerAddr’ object. Can
be one of the following:
■ unknown (0)
■ ipv4 (1) - default
■ ipv6 (2) - not supported
■ ipv4z (3) - not supported
■ ipv6z (4) - not supported
■ dns (16) - not supported.
atDNSServerAddr { atDNSServerEntry 3 } The IP Address of the DNS Server. When a new entry is created,
this object is set to the default of ‘0.0.0.0’ { ‘00000000’h }. The
management application will change this to the desired value
using a SET operation.
atDNSServerStatus { atDNSServerEntry 4 } The status of the current entry (row). Can be one of the following:
■ active (1)
■ createAndGo (4)
■ destroy (6).
To create a new entry the management application must set this
object with value ‘createAndGo (4)’.
To delete an entry, the management application must set this
object with value ‘destroy (6)’. Once an entry is deleted, all
subsequent entries in the table will be renumbered.
The default is 1 (active).
AT-ENVMONv2-MIB
The AT Environment Monitoring v2 MIB contains objects for managing and reporting data relating to
fans, voltage rails, temperature sensors and power supply units installed in the device, see Table 12.
Objects in this group have the object identifier EnvMonv2 { sysinfo 12 } OID
1.3.6.1.4.1.207.8.4.4.3.12.
atEnvMonv2PsbHostSlotIndex { atEnvMonv2PsbEntry 3 } Index of this power supply bay slot on its host
board. This index is fixed for each slot, on
each type of board.
atEnvMonv2Traps { atEnvMonv2 5 } or Note that objects under this portion of the tree
(1.3.6.1.4.1.207.8.4.4.3.12.5) have been deprecated, and replaced by
objects under the tree portion
207.8.4.4.3.12.0.
AT-EPSRv2-MIB
The EPSRv2 Group-MIB defines objects for managing Epsrv2 objects and triggers, see Figure 4 and
Table 13. Objects in this group have the object identifier Epsrv2 { modules 536 } OID
1.3.6.1.4.1.207.8.4.4.4.536.
enterprises (1)
alliedTelesis (207)
brouterMib (4)
bridgeRouter (1) routerSwitch (14)
atRouter (4)
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces protocols (6)
Epsrv2DomainId (3)
Epsrv2FromState (4)
Epsrv2CurrentState (5)
Epsrv2ControlVlanId (6)
Epsrv2PrimaryIfIndex (7)
Epsrv2PrimaryIfIndex (7)
Epsrv2PrimaryIfState (8)
Epsrv2SecondaryIfIndex (9)
Epsrv2SecondaryIfState (10)
EPSR2_MIB_Tree
.
Table 13: atEpsrv2Objects Defined in the AT-EPSRV2 MIB
{ at-Epsrv2 } { modules 536 } The root of the Epsrv2 object sub tree.
1.3.6.1.4.1.207.8.4.4.4.536
{ atEpsrv2Notify } { atEpsrv2Notifications 1 } EPSR Master/Transit node state transition trap. Note that
there is a one to one relationship between nodes and
domains.
{ Epsrv2NodeType } { atEpsrv2VariablesEntry 1 } The EPSR node type: either master or transit.
TEXTUAL CONVENTIONS
AT-FIBER-MONITORING-MIB
See Table 14 for the list of objects defined in the AT-HHM-MIB. These objects manage definition and
notification definitions for Fiber Monitoring. Objects in this group have the object identifier
atFiberMon { sysinfo 27 } OID 1.3.6.1.4.1.207.8.4.4.3.27.
atFiberMonReading { atFiberMonTrapVariable 1 } The current received optical power reading for the port
specified in the trap (x0.0001mW).
atFiberMonConfigTable { atFiberMon 2 } It contains the objects used to configure the operation of
fiber monitoring.
atFiberMonConfigEntry { atFiberMonConfigTable 1 } Entry for the table. It contains configurable options for
fiber monitoring for an interface.
atFiberMonIfname { atFiberMonConfigEntry 1 } The name of the interface where the pluggable is in.
AT-FILEv2-MIB
This MIB contains objects for displaying and managing file content of:
Flash.
SD cards.
Copying, moving and deleting files from local, stacked and remote sources.
The objects reside in the module atFilev2 { modules 600 }, OID 1.3.6.1.4.1.207.8.4.4.4.600,
organized in the following groups:
The file operation devices - object for various devices supported for file operations.
The SD card table - information about the SD Cards configured on the device.
The File Info Table - information about all files, including pathnames, that are present on the
device.
The USB storage device table - information about the USB storage device configured on the
device.
To see how to use these MIB objects to upgrade to a new software version and boot configuration
file, see the procedure “Copy a File to or from a TFTP Server” in the SNMP Feature Overview and
Configuration Guide.
atFilev2 { modules 600 } MIB containing objects for listing and managing files.
1.3.6.1.4.1.207.8.4.4.4.600
atFilev2SourceStackID { atFilev2Operation 1 } Specifies the Stack ID of the source file. Set an integer
corresponding to the stack ID of the stack member to use
as the source. For devices that are not capable of being
stacked, set with the value 1. This value is ignored if the
source device is set to TFTP.
atFilev2SourceDevice { atFilev2Operation 2 } Specifies the source device for the file to be copied.
Valid values are 1 to 5. Set a value that corresponds
with the various devices, as below:
■ Flash - default
■ Card
■ NVS
■ TFTP
■ USB.
For moving files you cannot use TFTP as source or
destination.
For deleting files, the source cannot be TFTP.
You must fully configure all required parameters before
an operation can commence. Where a TFTP operation
is configured, an IP address must also be set via
atFilev2TftpIPAddr.
To copy a file from TFTP to Flash, use 4 for source and
1 for destination.
atFilev2SourceFilename { atFilev2Operation 3 } Specifies the filename of the source file to copy, move
or delete. Include any path as required, but the storage
type is not necessary. For example, to copy the file
latest.cfg from the backupconfigs/routers directory
on the TFTP server, you would set: backupconfigs/
routers/latest.cfg.
atFilev2DestinationStackID { atFilev2Operation 4 } Specifies the Stack ID for the destination file. For
devices that are not capable of being stacked, set with
the value 1. This value is ignored if the destination
device is set to TFTP, or if a deletion operation is
carried out.
atFilev2DestinationDevice { atFilev2Operation 5 } Specifies the destination device for the files to be
copied into. Valid values are 1 to 5. Set a value that
corresponds with the various devices, as below:
■ Flash - default
■ Card
■ NVS
■ TFTP
■ USB.
For copying files, you may use any combination of
devices for the source and destination, except for
copying from TFTP to TFTP. For moving files you
cannot use TFTP as source or destination. For deleting
files, this object is ignored. You must fully configure all
required parameters before an operation can
commence. Where a TFTP operation is configured, an
IP address must also be set via atFilev2TftpIPAddr. To
copy a file from TFTP to Flash, use 4 for source and 1
for destination.
atFilev2CopyBegin { atFilev2Operation 7 } Represents the status of the copy file operation, in the
form of octet string.
A read on this object can return several possible
values, depending on the current status of the system
and the various file operation objects:
■ idle - There is no file operation in progress and all
required objects have been set correctly. Setting a
'1' to this object will begin the file copy.
■ Error codes: [1-7] - A copy operation cannot be
started until these errors are resolved. See below
for key.
■ [action]ing x [--> y] - A file operation is currently in
progress. You cannot start another operation while
the object is returning this value.
■ [action] x [--> y] success - The last copy, move or
delete operation was successfully completed.
■ [action] x [--> y] failure: [err] - The last copy, move
or delete operation failed, with the error message
attached. Common failures include lack of space
on the destination file system, incorrect source file
names or communication errors with remote
services.
Upon reading a success or failure message, the
message will be cleared and the next read will result in
either an 'idle' message or an 'Error codes' message if
not all required objects have been correctly set. If the
read returned 'idle', a new file operation can now be
started. Following are possible values returned as
Error codes for file copy:
■ atFilev2SourceDevice has not been set
■ atFilev2SourceFilename has not been set
■ atFilev2DestinationDevice has not been set
■ atFilev2DestinationFilename has not been set
■ atFilev2SourceDevice and
atFilev2DestinationDevice are both set to TFTP
■ the combination of source device, stackID and
filename is the same as the destination device,
stackID and filename (i.e. it is not valid to copy a
file onto itself)
■ TFTP IP address has not been set and TFTP has
been set for one of the devices.
TFTP IP address has not been set and TFTP has been
set for one of the devices
Provided all above requirements are met, immediately
upon executing the SNMP set, the device will indicate
that it was a success. The actual file copy itself will be
started and continue on the device until it has
completed. For large files, operations can take several
minutes to complete. Subsequent reads of the object
will return one of messages shown in the first table, to
allow for tracking of the progress of the copy
operation.
atFilev2MoveBegin { atFilev2Operation 8 } Represents the status of the move file operation, in the
form of octet string. A read on this object can return
several possible values, depending on the current
status of the system and the various file operation
objects:
■ idle - There is no file operation in progress and all
required objects have been set correctly. Setting a
'1' to this object will begin the file move.
■ Error codes: [1-6] - A move operation cannot be
started until these errors are resolved. See below
for key.
■ [action]ing x [--> y] - A file operation is currently in
progress. You cannot start another operation while
the object is returning this value.
■ [action] x [--> y] success - The last copy, move or
delete operation was successfully completed.
■ [action] x [--> y] failure: [err] - The last copy, move
or delete operation failed, with the error message
attached. Common failures include lack of space
on the destination file system, incorrect source file
names or communication errors with remote
services.
Upon reading a success or failure message, the
message will be cleared and the next read will result in
either an 'idle' message or an 'Error codes' message if
not all required objects have been correctly set. If the
read returned 'idle', a new file operation can now be
started. Following are possible values returned as
Error codes for file move:
■ atFilev2SourceDevice has not been set
■ atFilev2SourceFilename has not been set
■ atFilev2DestinationDevice has not been set
■ atFilev2DestinationFilename has not been set
■ either atFilev2SourceDevice or
atFilev2DestinationDevice are set to TFTP
■ the combination of source device, stackID and
filename is the same as the destination device,
stackID and filename (i.e. it is not valid to move a
file onto itself.
Provided all above requirements are met, immediately
upon executing the SNMP set, the device will indicate
that it was a success. The actual file move itself will be
started and continue on the device until it has
completed. For large files, operations can take several
minutes to complete. Subsequent reads of the object
will return one of messages shown in the first table, to
allow for tracking of the progress of the move
operation.
atFilev2TftpIPAddr { atFilev2Tftp_4 1 } The IP address of the TFTP server that is to be used for
the file copy process. This IP Address needs to be
reachable from the device, or the file copy will fail.
atFilev2Usb { atFilev2Operation 15 } Represents the USB storage device operation device
object.
atFilev2SDcardStackMemberId { atFilev2SDcardEntry 1 } The index of the stack member hosting this SD Card.
atFilev2InfoFileIsWriteable { atFilev2InfoEntry 6 } This object will return the value TRUE if the file is
writeable, or FALSE if it is not.
atFilev2InfoFileIsExecutable { atFilev2InfoEntry 7 } This object will return the value TRUE if the file is
executable, or FALSE if it is not.
atFilev2USBMediaTable { atFilev2 6 } The USB storage device table, containing information
related to USB storage devices.
atFilev2USBMediaStackMemberId { atFilev2USBMediaEntry 1 } The index of the stack member hosting this USB
media. For devices that are not capable of being
stacked, this object will always return the value 1.
atFilev2FileViewer { atFilev2 7 } The set of objects in this section allow for a view of the
files on this managed device that is reminiscent of the
view that a shell user on a device would have, with the
concepts of current working directory, changing
directories and viewing files within a directory all
supported.
This section obsoletes the first two attempts at
creating a view of files for the reason that performance
and functionality of the original views was not
sufficient. In particular, trying to create a view of all files
in the device, sorted by path and file name, proved to
be very difficult when scaling considerations were
taken into account.
atFilev2FileViewerDevice { atFilev2FileViewer 2 } The file system device for which files will be displayed
in the FileViewer table. The values supported for this
variable are identical to the values for other variables in
the MIB, although not all values will actually result in
the display of files. The different devices and whether
they will result in the display of files are:
■ Flash - Onboard Flash
■ Card - Removable SD card
■ NVS - Onboard battery backed RAM
■ FTP - not supported
■ USB - Removable USB media.
AT-G8032v2-MIB
These objects manage Ethernet Protection Ring Switching (EPRS). Objects in this group have the
object identifier atG8032v2 { modules 604 }, OID 1.3.6.1.4.1.207.8.4.4.4.604. See Table 16 for the
list of objects defined in the AT-G8032v2-MIB.
TEXTUAL CONVENTIONS
AT-HHM-MIB
See Table 17 for the list of objects defined in the AT-HHM-MIB. These objects manage Hardware
Health Monitoring notification generated log messages. Objects in this group have the object
identifier atwhealthMon { sysinfo 24 } OID 1.3.6.1.4.1.207.8.4.4.3.24.
AT-IP-MIB
This MIB contains objects for Allied Telesis specific IP address management, see Table 18. The
objects reside in the module atIpMib { modules 602 }, OID 1.3.6.1.4.1.207.8.4.4.4.602.
A
atIpAddressLabel { AtIpAddressEntry 4 } The name assigned to the IP address represented by this entry.
atIpAddressIfIndex { AtIpAddressEntry 5 } The index value that uniquely identifies the interface to which
this entry is applicable. The interface identified by a particular
value of this index corresponds to the interface identified by the
same value of the IF-MIB's ifIndex.
atIpAddressAssignmentType { AtIpAddressEntry 6 } The IP address assignment type for this entry (primary or
secondary), as described in the Textual Convention
‘AtIpAddressAssignmentType’.
AT-LICENSE-MIB
The AT-LICENSE-MIB contains objects for managing the AlliedWare PlusTM Operating System
software licenses: listing applied software licenses, adding new licenses and deleting existing
licenses, see Table 19. The objects in this group have the object identifier license { sysinfo 22 }, OID
1.3.6.1.4.1.207.8.4.4.3.22, and are organized in the following groups:
Base Software License Table - a table containing the installed base software licenses on the
device.
Installed Software License Table - a list of installed software licenses; used also to remove
software license from the device.
license { sysinfo 22 } MIB containing objects for listing applied software licenses,
1.3.6.1.4.1.207.8.4.4.3.22 adding new licenses, and deleting existing licenses.
baseLicenseTable { license 1 } Table containing information about base software licenses
installed on a device. Indexed by:
■ baseLicenseStkId.
baseLicenseStkId { baseLicenseEntry 1 } The stack member ID of the device hosting the license.
baseLicenseFeatures { baseLicenseEntry 7 } The feature set that this license enables, in the format of an octet
string. Each bit in the returned octet string represents a particular
feature that can be license-enabled. The bit position within the
string maps to the feature entry with the same index, in
licenseFeatureTable:
■ binary ‘1’ indicates that the feature is included in the license
■ binary ‘0’ indicates that the feature is not included in the
license.
licenseFeatures { licenseEntry 9 } The feature set that this license enables, in the format of octet
string. Each bit in the returned octet string represents a particular
feature that can be license-enabled. The bit position within the
string maps to the feature entry with the same index, in
licenseFeatureTable:
■ binary ‘1’ indicates that the feature is included in the license
■ binary ‘0’ indicates that the feature is not included in the
license.
licenseRowStatus { licenseEntry 10 } The current status of the license. The following values may be
returned when reading this object:
■ active (1) - the license is currently installed and valid
■ notInService (2) - the license has expired or is invalid
licenseFeatureTable { license 3 } Table containing all available Software Features. A feature must be
license-enabled to be utilized on the device.
licenseFeatureEntry { licenseFeatureTable 1 } Information about a single feature that must be license-enabled in
order to be utilized on the device.
licenseFeatureIndex { licenseFeatureEntry 1 } The index number of the feature which must be license-enabled.
licenseFeatureStkMembers { licenseFeatureEntry 3 } The set of stack members on which the feature is enabled, in the
format of an octet string.
Each bit in the string maps to an individual stacking member, e.g.
bit one represents stacking member one, bit two represents
stacking member two.
■ a bit value of ‘1’ indicates that the applicable feature is
enabled on the matching device
■ a bit value of ‘0’ indicates that the feature is disabled.
licenseNew { license 4 } Group of objects available for updates, used when installing a new
software license on the device.
licenseNewStackId { licenseNew 1 } The ID of the stacking member upon which the new license is to
be installed. The value zero (0) indicates that the license should be
applied to all stack members.
licenseNewName { licenseNew 2 } The name of the new license to be installed.
AT-LINKMON-MIB
See Table 20 for the list of objects defined in the AT-LINKMON-MIB. This contains objects for link
monitoring used for collecting and reporting link metrics. Objects in this group have the object
identifier atLinkMon { modules 606 } OID 1.3.6.1.4.1.207.8.4.4.4.606.
atLinkMonProbeHistoryProbe { atLinkMonProbeHistoryEntry 2 } The name of the probe the metrics are sampled
Name from.
AT-LINKTRAP-MIB
See Table 21 for the list of objects defined in the AT-LINKTRAP-MIB. This contains objects for link up
and down traps. Objects in this group have the object identifier atLinkTrap { sysinfo 25 } OID
1.3.6.1.4.1.207.8.4.4.3.25.
AT-LOG-MIB
The AT Log MIB contains objects for listing log entries from the buffered and permanent logs, see
Table 22. The object identifier log { modules 601 }, OID 1.3.6.1.4.1.207.8.4.4.4.601, organized in the
following groups:
Log Table - objects containing the information from log messages issued by the system, ordered
from oldest to newest entry.
Log Options - contains objects used to set up the log options configuration.
log { modules 601 } MIB containing objects for listing log entries from the buffered and permanent
1.3.6.1.4.1.207.8.4.4.4.601 logs.
logTable { log 1 } A list of log entries from the source specified in the ‘logSource’ object. The list
is ordered from oldest entry to newest entry.
Indexed by:
■ logIndex.
logEntry { logTable 1 } Information about a single log entry, from the source specified in the
‘logSource’ object.
logIndex { logEntry 1 } An index integer. This index is not directly tied to any specific log entry. Over
time, the log will grow larger and eventually older entries will be removed from
the log.
logDate { logEntry 2 } The date of the log entry. Data resides in the format octet string, in the form
YYYY MMM DD, e.g. 2008 Oct 9.
logTime { logEntry 3 } The time of the log entry. Data resides in the format octet string, in the form
HH:MM:SS, e.g. 07:15:04.
logFacility { logEntry 4 } The syslog facility that generated the log entry, in the format octet string. See
the reference manual for more information.
logSeverity { logEntry 5 } The severity level of the log entry, in the format octet string. Severities are given
below:
■ emerg (Emergency, system is unusable)
■ alert (Action must be taken immediately)
■ crit (Critical conditions)
■ errr (Error conditions)
■ warning (Warning conditions)
■ notice (Normal, but significant, conditions)
■ info (Informational messages)
■ debug (Debug-level messages).
logProgram { logEntry 6 } The program that generated the log entry, in the format octet string. See the
reference manual for more information.
logMessage { logEntry 7 } The message of the new log entry, in the format octet string.
logOptions { log 2 } Contains objects used to set up the required log options configuration.
logSource { logOptions 1 } An integer indicating the source from which the log entries are retrieved. The
valid values are:
■ 1 - Buffered log (default)
■ 2 - Permanent log.
This information is used when retrieving the logTable objects, and also specifies
the log to be cleared when the ‘clearLog’ object is set.
logAll { logOptions 2 } An integer indicating whether to display all log entries in the logTable objects,
or not. The valid values are:
■ 0 - to display only the most recent log messages. This is the default.
■ 1 - to show all available log entries.
Note: Choosing to display all log entries may result in delays of several
seconds when accessing the logTable objects.
clearLog { logOptions 3 } An integer indicating whether to clear the log that is specified by the ‘logSource’
object. Valid values are:
■ 0 - do not clear log
■ 1 - clear log.
AT-LOOPPROTECT-MIB
The atLoopProtect-MIB, see Figure 5 and Table 23, defines objects for managing Loop Protection
objects and triggers. Objects in this group have the object identifier atLoopProtect { modules 4 },
OID 1.3.6.1.4.1.207.8.4.4.4.54.
enterprises (1)
alliedTelesis (207)
brouterMib (4)
bridgeRouter (1) routerSwitch (14)
atRouter (4)
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces protocols (6)
atLoopProtect (54)
atLoopProtectAction (1)
atLoopProtectTrap (0)
atLoopProtectRxLDFIfIndex (4)
atLoopProtectRxLDFVlanId (5)
LoopProtect_MIB_
{ atLoopProtect } { modules 54 } The root of the Loop Protect object sub tree.
1.3.6.1.4.1.207.8.4.4.4.54
{ atLoopProtectTrap } { atLoopProtect0 } The Loop Protection node state transition trap. List of traps
(notifications) generated for Loop Protection.
{ atLoopProtectDetected { atLoopProtectTrap1 } Notification generated when the Loop Protection feature blocks
LoopBlockedTrap } an interface with a loop. The following bindings are associated
with this trap:
■ atLoopProtectIfIndex
■ atLoopProtectVlanId
■ atLoopProtectAction.
{ atLoopProtectRecover { atLoopProtectTrap2 } Notification generated when the Loop Protection feature restores
LoopBlockedTrap } a blocked interface back to normal operation. The following
bindings are associated with this trap:
■ atLoopProtectIfIndex
■ atLoopProtectVlanId
■ atLoopProtectAction.
{ atLoopProtectDetected { atLoopProtectTrap3 } Notification generated when the Loop Protection feature detects
ByLoopDetectionTrap } a loop by Loop Detection method. The following bindings are
associated with this trap:
■ atLoopProtectIfIndex
■ atLoopProtectVlanId
■ atLoopProtectRxLDFIfIndex
■ atLoopProtectRxLDFVlanId.
{ atLoopProtectAction } { atLoopProtect1 } The Action for the Loop Protection feature. The following values
are defined:
■ atLoopProtectAction-LearnDisable (0)
■ atLoopProtectAction-LearnEnable (1)
■ atLoopProtectAction-PortDisable (2)
■ atLoopProtectAction-PortEnable (3)
■ atLoopProtectAction-LinkDown (4)
■ atLoopProtectAction-LinkUp (5)
■ atLoopProtectAction-VlanDisable (6)
■ atLoopProtectAction-VlanEnable (7).
{ atLoopProtectRxLDFIfIndex } { atLoopProtect4 } The interface on which the loop detection frame was received.
{ atLoopProtectRxLDFVlanId } { atLoopProtect5 } The VLAN ID on which the loop detection frame was received.
AT-MIBVERSION-MIB
The AT-MIBVERSION-MIB contains an object to display the last software release that contained
changes to the supported AT Enterprise MIB definition files, see Table 24. Objects in this group have
the object identifier atMibsetVersion { sysinfo 15 }, OID 1.3.6.1.4.1.207.8.4.4.3.15.
atMibVersion { sysinfo 15 } This object returns a five digit integer which indicates the last software
1.3.6.1.4.1.207.8.4.4.3.15 release that contained changes to the supported AT Enterprise MIB
definition files. For example, If the currently loaded software release on
the device is 5.3.1-0.3 but the Enterprise MIBs have not changed since
5.3.1-0.1, then the value returned will be 53101.
AT-NTP-MIB
This MIB contains objects for managing the Allied Telesis Network Time Protocol (NTP)
configuration, see Table 25. The objects reside in the module atNtp { modules 502 }, OID
1.3.6.1.4.1.207.8.4.4.4.502, organized in the following groups:
NTP Peer/Server Table - a table containing information on the Network Time Protocol (NTP) peers
or server configurations in the system.
Associations Table - a list of installed software; used also to remove software from the device.
atNtpPeerPreference { atNtpPeerEntry 4 } The values in this object specifies whether this peer is the
preferred one. Valid values are 0 to 2:
■ 0 - unknown - default
■ 1 - not preferred
■ 2 - preferred.
When the value is ‘not preferred’ (1) NTP chooses the
peer with which to synchronize the time on the local
system. If the object is set to ‘preferred’ (2) NTP will
choose the corresponding peer to synchronize the time
with.
atNtpPeerVersion { atNtpPeerEntry 5 } The NTP version the peer supports. Can be one of the
following:
■ 0 - unknown - default
■ 1 - version 1
■ 2 - version 2
■ 3 - version 3
■ 4 - version 4.
atNtpAssociationConfigured { atNtpAssociationEntry 4 } The value in this object specifies whether the association
is from configuration or not. Value can be:
■ configured
■ dynamic.
atNtpAssociationPoll { atNtpAssociationEntry 7 } The time between NTP requests from the device to the
server, in seconds.
atNtpAssociationDelay { atNtpAssociationEntry 9 } The round trip delay between the device and the server.
atNtpAssociationOffset { atNtpAssociationEntry 10 } The difference between the device clock and the server
clock.
atNtpAssociationDisp { atNtpAssociationEntry 11 } The lowest measure of error associated with peer offset,
based on delay, in seconds.
atNtpStatus { atNtp 11 } Group of objects containing system status information.
The objects in this group are not supported.
atNtpSysFrequency { atNtpStatus 4 } The actual clock frequency, a numeric value in ‘Hz’ units
atNtpSysPrecision { atNtpStatus 5 } A signed integer indicating the precision of the system
clock, in seconds.
The value is rounded to the next larger power of two. For
example, a 50-Hz (20 ms) or 60-Hz (16.67 ms) power-
frequency clock would be assigned the value -5 (31.25
ms), while a 1000-Hz (1 ms) crystal-controlled clock
would be assigned the value -9 (1.95 ms).
atNtpSysRefTime { atNtpStatus 6 } Indicates the local time when the local clock was last
updated. If the local clock has never been synchronized,
the value is zero.
The values are in the format of an Octet string.
atNtpSysClkOffset { atNtpStatus 7 } Indicates the offset of the local clock relative to the server
clock, in milliseconds.
atNtpSysRootDelay { atNtpStatus 8 } The total round trip delay, in milliseconds, to the primary
reference source at the root of the synchronization
subnet.
atNtpSysRootDisp { atNtpStatus 9 } The maximum error, in milliseconds, relative to the
primary reference source at the root of the
synchronization subnet.
AT-PLUGGABLE-DIAGNOSTICS-MIB
This MIB contains objects for monitoring Optical Digital Diagnostics for pluggable devices, see
Table 26. The objects identifier for this MIB is atPluggableDiag { sysinfo 28 }, OID
1.3.6.1.4.1.207.8.4.4.3.28, see "AT-SYSINFO-MIB" on page 116.
AT-PORTINFO-MIB
The table below, Table 27, defines objects for managing interface port objects such as transceivers.
Objects in this group have the object identifier atPortInfo { sysinfo 14 }, OID
1.3.6.1.4.1.207.8.4.4.3.14 see “AT-SYSINFO-MIB” on page 116.
atPortInfoTransceiverifIndex { atPortInfoTransceiverEntry 1 } The ifIndex for the interface represented by this entry of
the interfaces table.
AT-PRODUCTS-MIB
AT-PRODUCT-MIB defines object identifiers for Allied Telesis products. Objects in this MIB, see
Table 28, have the object identifier products { alliedTelesis 1 }, OID 1.3.6.1.4.1.207.1.
.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System
products { alliedTelesis 1 } This file defines the identities of Allied Telesis products.
1.3.6.1.4.1.207.1
swhub { products 4 } Subtree beneath which switching hubs are defined.
at_x200_GE52T { swhub 181 } x200-GE52T layer two switch.
at_x310_26FT { swhub 216} AT-x310-26FT layer two switch with 24 10/100 Base-T ports, two 10/100/
1000 Base-T ports, and four 10 Gb/s SFP+ ports.
at_x310_50FT { swhub 217} AT-x310-50FT layer two switch with 48 10/100 Base-T ports, two 10/100/
1000 Base-T ports, and four 10 Gb/s SFP+ ports.
at_x310_26FP { swhub 218} AT-x310-26FP layer two switch with 24 10/100 Base-T ports, two 10/100/
1000 Base-T ports, four 10 Gb/s SFP+ ports, plus PSE function available on
pins 1/2 and 3/6 (Mode A) of every copper port.
at_x310_50FP { swhub 219} AT-x310-50FP layer two switch with 48 10/100 Base-T ports, two 10/100/
1000 Base-T ports, four 10 Gb/s SFP+ ports, plus PSE function available on
pins 1/2 and 3/6 (Mode A) of every copper port.
at_x230_10GT { swhub 224 } AT-x230-10GP L3 switch with 8 x 10/100/1000T PoE ports and
2 x 100/1000X SFP ports.
at_x230_18GT { swhub 225 } AT-x230-18GT L3 switch with 16 x 10/100/1000T ports and
2 x 100/1000X SFP ports.
at_x230_28GT { swhub 226 } AT-x230-28GT L3 switch with 24 x 10/100/1000T ports and
4 x 100/1000X SFP ports.
at_x230_10GP { swhub 228 } AT-x230-10GP, 8 10/100/1000BASE-RJ-45 ports, 2 10/100/1000Base SFP
ports.
at_x230_18GP { swhub 229 } AT-x 230-18GP, 16 10/100/1000BASE RJ-45 ports and 2 10/100/1000BASE
SFP ports.
at_x230_28GP { swhub 230 } AT-x 230-28GP, 24 10/100/1000BASE RJ-45 ports and 4 10/100/1000BASE
SFP ports.
at_GS924MX { swhub 253 } AT-GS924MX, 24 x 10/100/1000T ports, 2 combo ports (10/100/1000T or
100/1000X SFP) and 2 X 10G SFP+ Stacking/User ports.
at_GS924MPX { swhub 254 } AT-GS924MPX, 24 x 10/100/1000T POE+ ports, 2 combo ports (10/100/
1000T or 100/1000X SFP) and 2 X 10G SFP+ Stacking/User ports.
at_GS948MX { swhub 255 } AT-GS948MX, 48 x 10/100/1000T ports, 2 combo ports (10/100/1000T or
100/1000X SFP) and 2 X 10G SFP+ Stacking/User ports.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System (continued)
at_XS916MXT { swhub 257 } AT-S916MXT, 12 x 100/1000/10G BASE-T ports and 4 x SFP/SFP+ slots.
at_XS916MXS { swhub 258 } AT-XS916MXS, 12 x SFP/SFP+ slots and 4 x 100/1000/10G BASE-T ports.
at_SH230_10GT { swhub 270 } AT-x230-10GT, L3 switch with 8 x 10/100/1000T ports and 2 x 100/1000X
SFP ports.
at_SH230_18GT { swhub 271 } AT-x230-18GT, L3 switch with 16 x 10/100/1000T ports and 2 x 100/1000X
SFP ports.
at_SH230_28GT { swhub 272 } AT-x230-28GT, L3 switch with 24 x 10/100/1000T ports and 4 x 100/1000X
SFP ports.
atFS980M9 { swhub 274 } AT-FS980M/9, 8 x 10/100TX ports and 1 combo (10/100/1000T or 100/
1000X SFP) uplink port.
atFS980M9PS { swhub 275 } AT-FS980M/9PS, 8 x 10/100TX PoE+ ports and 1 combo (10/100/1000T or
100/1000X SFP) uplink port.
atFS980M18 { swhub 276 } AT-FS980M/18, 16 x 10/100TX ports and 2 combo (10/100/1000T or 100/
1000X SFP) uplink ports.
atFS980M18PS { swhub 277 } AT-FS980M/18PS, 16 x 10/100TX PoE+ ports and 2 combo (10/100/1000T
or 100/1000X SFP) uplink ports
atFS980M28 { swhub 278 } AT-FS980M/28, 24 x 10/100TX ports and 4 x 100/1000X SFP uplink/stacking
ports.
atFS980M28PS { swhub 279 } AT-FS980M/28PS, 24 x 10/100TX PoE+ ports and 4 x 100/1000X SFP
uplink/stacking ports.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System (continued)
atFS980M52PS { swhub 281 } AT-FS980M/52PS, 48 x 10/100TX PoE+ ports and 4 x 100/1000X SFP
uplink/stacking ports.
atGS970M28PS { swhub 312 } AT-GS970M/28PS, Layer 3 24 x 10/100/1000T Gigabit PoE+ ports and
4 x 100/1000X SFP ports.
atGS970M18PS { swhub 313 } AT-GS970M/18PS, Layer 3 16 x 10/100/1000T Gigabit PoE+ ports and
2 x 100/1000X SFP ports.
atGS970M10PS { swhub 314 } AT-GS970M/10PS, Layer 3 8 x 10/100/1000T Gigabit PoE+ ports and
2 x 100/1000X SFP ports.
atGS970M28 { swhub 315 } AT-GS970M/28, Layer 3 24 x 10/100/1000T Gigabit Ethernet ports and
4 x 100/1000X SFP ports.
atGS970M18 { swhub 316 } AT-GS970M/18, Layer 3 16 x 10/100/1000T Gigabit Ethernet ports and
2 x 100/1000X SFP ports.
atGS970M10 { swhub 317 } AT-GS970M/10, Layer 3 8 x 10/100/1000T Gigabit Ethernet ports and
2 x 100/1000X SFP ports.
routerSwitch { products 14 } Subtree beneath which router and (non industrial) switch product MIB object
IDs are assigned.
at_SwitchBladex908 { routerSwitch 69 } SwitchBlade x908 8 Slot Layer 3 Switch Chassis.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System (continued)
at_x600-24TsPoE { routerSwitch 91} x600-24Ts-POE Stackable Managed L2+/L3 Ethernet PoE Switch,
24 x 1000BASE-T PoE ports, 4 x SFP (combo) ports.
at_x600_24TPoEPlus {routerSwitch 92} x600-24Ts-POE+ Stackable Managed L2+/L3 Ethernet PoE+ Switch,
24 x 1000BASE-T PoE+ ports, 4 x SFP (combo) ports.
x610_48Ts_X_POEPlus {routerSwitch 93} x610-48Ts/X-POE+ Stackable Managed L2+/L3 Ethernet PoE+ Switch,
48 x 10/100/1000BASE-T PoE+ ports, 2 x SFP (combo) ports, 2 x SFP+
ports.
x610_48Ts_POEPlus {routerSwitch 94} x610-48Ts-POE+ Stackable Managed L2+/L3 Ethernet PoE+ Switch,
48 x 10/100/1000BASE-T PoE+ ports, 4 x SFP (combo) ports.
x610_24Ts_X_POEPlus {routerSwitch 95} x610-24Ts/X-POE+ Stackable Managed L2+/L3 Ethernet PoE+ Switch,
24 x 10/100/1000BASE-T PoE+ ports, 4 x SFP (combo) ports, 2 x SFP+
ports.
x610_24Ts_POEPlus {routerSwitch 96} x610-24Ts-POE+ Stackable Managed L2+/L3 Ethernet PoE+ Switch,
24 x 10/100/1000BASE-T PoE+ ports, 4 x SFP (combo) ports.
x610_48Ts_X {routerSwitch 97} x610-48Ts/X Stackable Managed L2+/L3 Ethernet Switch, 48 x 10/100/
1000BASE-T copper ports, 2 x SFP (combo) ports, 2 x SFP+ ports.
x610_48Ts {routerSwitch 98} x610-48Ts Stackable Managed L2+/L3 Ethernet Switch, 24 x 10/100/
1000BASE-T copper ports, 4 x SFP (combo) ports.
x610_24Ts_X {routerSwitch 99} x610-24Ts/X Stackable Managed L2+/L3 Ethernet Switch, 24 x 10/100/
1000BASE-T copper ports, 4 x SFP (combo) ports, 2 x SFP+ ports.
x610_24Ts {routerSwitch 100} x610-24Ts Stackable Managed L2+/L3 Ethernet Switch, 24 x 10/100/
1000BASE-T copper ports, 4 x SFP (combo) ports.
x610_24SP_X {routerSwitch 101} x610-24SP/X Stackable Managed L2+/L3 Ethernet Switch, 24 x SFP
(combo) ports, 2 x SFP+ ports.
x510_28GTX {routerSwitch 109} x510-28GTX Stackable Managed L2+/L3 Ethernet Switch with 24 x 10/100/
1000 Base-T ports and 4 x 10 Gb/s SFP+ ports.
x510_28GPX {routerSwitch 110} x510-28GPX Stackable Managed L2+/L3 Ethernet Switch with 24 x 10/100/
1000 Base-T ports with PoE, 4 x 10 Gb/s SFP+ ports.
x510_28GSX {routerSwitch 111} x510-28GSX Stackable Managed L2+/L3 Ethernet Switch with 24 x 100/
1000 SFP ports and 4 x 10 Gb/s SFP+ ports.
x510_52GTX {routerSwitch 112} x510-52GTX Stackable Managed L2+/L3 Ethernet Switch with 48 x 10/100/
1000 Base-T ports and 4 x 10 Gb/s SFP+ ports.
x510_52GPX {routerSwitch 113} x510-52GPX Stackable Managed L2+/L3 Ethernet Switch with 48 x 10/100/
1000 Base-T ports with PoE, and 4 x 10 Gb/s SFP+ ports.
at-SBx8106 {routerSwitch 114} AT-SBx8106, SwitchBlade x8106 chassis.
x510DP_52GTX {routerSwitch 116} x510DP-52GTX, Stackable Managed L2+/L3 Ethernet Switch with 48 x 10/
100/1000 Base-T ports and 4 x 10 Gb/s SFP+ ports.
IX5_28GPX {routerSwitch 117} IX5-28GPX, Stackable Managed L2+ Ethernet Switch with 24 x 10/100/1000
Base-T ports with PoE, 4 x 10 Gb/s SFP+ ports.
at_x930_28GTX { routerSwitch 118 } AT-x930-28GTX, 24 10/100/1000BASE-T ports, 4 x 10 Gb/s SFP+ ports.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System (continued)
at_dc2552xs { routerSwitch 123 } AT-DC2552XS/L3, Stackable 10 Gigabit Layer 3 switch with 48 x SFP+
ports, 4 x QSFP ports.
at_x510_28GSX_DC { routerSwitch 124 } AT-x510-28GSX, 24 x 100/1000X fiber access ports and 4 x 1G/10G SFP+
uplink ports.
at_x510DP_28GTX { routerSwitch 126 } AT-x510DP-28GTX, 24 10/100/1000BASE RJ-45 ports, 4 x SFP+ ports.
at_x510L_52GT { routerSwitch 128 } T-x510L-52GT Gigabit edge switch features 48 x 10/100/1000T ports
and 4 x 1G/10G SFP+ uplink ports.
atx51028GTXR { routerSwitch 131 } AT-x510-28GTX, 24 x 10/100/1000T ports and 4 x 10G/1G SFP+ uplink
ports.
atx51052GTXR { routerSwitch 132 } AT-x510-52GTX, 48 x 10/100/1000T ports and 4 x 10G/1G SFP+ uplink port.
atSH51028GTX { routerSwitch 133 } AT-x510-28GTX, 24 x 10/100/1000T ports and 4 x 10G/1G SFP+ uplink
ports.
atSH51052GTX { routerSwitch 134 } AT-x510-52GTX, 48 x 10/100/1000T ports and 4 x 10G/1G SFP+ uplink
ports.
atSH51028GPX { routerSwitch 135 } AT-x510-28GPX, 24 x 10/100/1000T PoE+ ports and 4 x 10G/1G SFP+
uplink ports.
atSH51052GPX { routerSwitch 136 AT-x510-52GPX, 48 x 10/100/1000T PoE+ ports and 4 x 10G/1G SFP+
uplink ports.
atsbx908g2 { routerSwitch 137 } AT-SBx908GEN2, High capacity Layer 3+ modular switch chassis with
8 x high speed expansion bays.
atx55018XTQ { routerSwitch 139 } AT-x550-18XTQ-xx, 16-port 1G/10G BaseT stackable switch with
2 QSFP ports.
atx55018XSQ { routerSwitch 140 } AT-x550-18XSQ-xx, 16-port 1G/10G SFP+ stackable switch with
2 QSFP ports.
atx55018XSPQm { routerSwitch 141 } AT-x550-18XSPQm-xx, 8-port 1G/2.5G/5G/10G BaseT PoE+ and 8-port
1G/10G SFP+ stackable switch with
2 QSFP ports.
atSBx81XLEM { routerSwitch 142 } AT-SBx81XLEM, Modular 40G line card with 12 x 100/1000X SFP
atx53028GTXm { routerSwitch 143 } AT-x530-28GTXm, layer 3 switch is high-performing and feature-rich, with
24 x 100M/1G copper ports and 4 x 10G uplinks.
atx53028GPXm { routerSwitch 144 } AT-x530-28GPXm, layer 3 switch is high-performing and feature-rich, with
24 x 100M/1G copper PoE+ ports and 4 x 10G uplinks.
Table 28: Object identifiers for Allied Telesis products supported by the AlliedWare PlusTM Operating System (continued)
atx95028XSQ { routerSwitch 151 } AT-x950-28XSQ, 24-port 1/10G SFP/SFP+ stackable switch with
4 x 40G/100G QSFP+/QSFP28 ports.
atx530L28GTX { routerSwitch 158 } AT-x530-28GTXm, 24-port 100/1000T stackable switch with 4 SFP+ ports.
atx530L28GPX { routerSwitch 159 } AT-x530-28GPXm, 24-port 100/1000T PoE+ stackable switch with 4 SFP+
ports.
industrialSwitch { products 24 } Subtree beneath which industrial switch product MIB object IDs are
assigned.
at_IE200_6GT {industrialSwitch 1} IE200-6GT, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports and 2 x SFP uplinks (100/1000X).
at_IE200_6GP {industrialSwitch 2} IE200-6GP, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports (with 802.3at PoE+) and 2 x SFP uplinks (100/1000X).
at_IE200_6GPW {industrialSwitch 3} IE200-6GPW, L2+ managed industrial Switch with 4 x 10/100/1000T LAN
ports (with 802.3at PoE+) and 2 x SFP uplinks (100/1000X) and 802.11bgn
wireless.
at_IE200_6FT { industrialSwitch 6 } AT-IE200-6FT, 4 × 10/100TX ports and 2 × 100/1000X SFP ports.
at_IE200_6FP { industrialSwitch 7 } AT-IE200-6FP, 4 × 10/100TX ports (PoE+ support) and 2 × 100/1000X SFP
ports.
at_IE300_12GT { industrialSwitch 8 } AT-IE300-12GT-80, 8 x 10/100/1000T, 4 x 100/1000X SFP, Industrial
Ethernet, Layer 3 Switch.
at_IE300_12GP { industrialSwitch 9 } AT-IE300-12GP-80, 8 x 10/100/1000T, 4 x 100/1000X SFP, Industrial
Ethernet, Layer 3 Switch.
AT-PTP-MIB
See Table 29 for the list of objects defined in the AT-PTP-MIB. These objects contain definitions of managed objects for Precision Time Protocol (PTP).
Objects in this group have the object identifier atPtpMIB { modules 504 } OID 1.3.6.1.4.1.207.8.4.4.4.504.
atPtpMIB { modules 504 } This MIB file contains definitions of managed objects for the IEEE 1588v2 Precision Time
1.3.6.1.4.1.207.8.4.4.4.504 Protocol (PTP) module.
TEXTUAL CONVENTIONS
PtpClockDomainType The Domain is identified by an integer, the domainNumber, in the range of 0 to 255. An integer value that is used to assign each
PTP device to a particular domain. The following values define the valid domains:
Table 30:
Value Definition
0 Default domain
1 Alternate domain 1
2 Alternate domain 2
3 Alternate domain 3
28-255 Reserved
PtpClockIdentity The clock Identity is an 8-octet array and will be presented in the form of a character array. Network byte order is assumed. The
value of the PtpClockIdentity should be taken from the IEEE EUI-64 individual assigned numbers as indicated in Section 7.5.2.2.2
of [IEEE 1588-2008]. It can also be non-EUI-64 address as defined in section 7.5.2.2.3 of [IEEE 1588-2008]. The EUI-64 address is
divided into the following fields:
■ OUI bytes (0-2)
■ Extension identifier bytes (3-7)
The clock identifier can be constructed from existing EUI-48 assignments and here is an abbreviated example extracted from
section 7.5.2.2.2 [IEEE 1588-2008].
■ Company EUI-48 = 0xACDE4823456716
■ EUI-64 = ACDE48FFFE23456716
It is important to note the IEEE Registration Authority has deprecated the use of MAC-48 in any new design.
PtpClockInstanceType The instance of the Clock of a given clock type in a given domain.
PtpClockIntervalBase2 The interval included in message types Announce, Sync, Delay_Req, and Pdelay_Req as indicated in section 7.7.2.1 of [IEEE 1588-
2008].
The mean time interval between successive messages shall be represented as the logarithm to the base 2 of this time interval
measured in seconds on the local clock of the device sending the message. The values of these logarithmic attributes shall be
selected from integers in the range -128 to 127 subject to further limits established in an applicable PTP profile.
PtpClockMechanismType The clock type based on whether end-to-end or peer-to-peer mechanisms are used. The mechanism used to calculate the Mean
Path Delay as indicated in Table 9 of [IEEE 1588-2008]:
Table 31:
PtpClockPortNumber An index identifying a specific Precision Time Protocol (PTP) port on a PTP node.
PtpClockPortState This is the value of the current state of the protocol engine associated with this port:
Table 32:
initializing 1 In this state a port initializes its data sets, hardware and communication facilities.
disabled 3 The port shall not place any messages on its communication path.
listening 4 The port is waiting for the announceReceiptTimeout to expire or to receive an Announce message from
a master.
preMaster 5 The port shall behave in all respects as though it were in the MASTER state except that it shall not place
any messages on its communication path except for Pdelay_Req, Pdelay_Resp,
Pdelay_Resp_Follow_Up, Signaling, or management messages.
master 6 The port is behaving as a master port.
passive 7 The port shall not place any messages on its communication path except for Pdelay_Req, Pdelay_Resp,
Pdelay_Resp_Follow_Up, or signaling messages, or management messages that are a required
response to another management message.
uncalibrated 8 The local port is preparing to synchronize to the master port.
PtpClockPortTransportTypeAddress The Clock port transport protocol address used for this communication between the clock nodes. This is a string corresponding to
the address type as specified by the transport type used. The transport types can be defined elsewhere, in addition to the ones
defined in this document. This can be an address of type IP version 4, IP version 6, Ethernet, DeviceNET, ControlNET or IEC61158.
The OCTET STRING representation of the OID of ptpWellKnownTransportTypes will be used in the values contained in the OCTET
STRING.
PtpClockProfileType Clock Profile used. A profile is the set of allowed Precision Time Protocol (PTP) features applicable to a device.
PtpClockQualityAccuracyType The ClockQuality as specified in sections 5.3.7, 7.6.2.5 and Table 6 of [IEEE 1588-2008]. The following values are not represented
in the enumerated values.
■ 0x01-0x1F Reserved
■ 0x32-0x7F Reserved
It is important to note that section 7.1.1 of [RFC 2578] allows for gaps and enumerate values starting at zero when indicated by the
protocol.
PtpClockQualityClassType The ClockQuality as specified in section 5.3.7 ClockQuality, 7.6.2.4 clockClass and Table 5 clockClass specifications of [IEEE 1588-
2008]:
Table 33:
Value Description
1-5 Reserved.
6 Shall designate a clock that is synchronized to a primary reference time source. The timescale distributed shall be PTP.
A clockClass 6 clock shall not be a slave to another clock in the domain.
7 Shall designate a clock that has previously been designated as clockClass 6 but that has lost the ability to synchronize
to a primary reference time source and is in holdover mode and within holdover specifications. The timescale
distributed shall be PTP. A clockClass 7 clock shall not be a slave to another clock in the domain.
8 Reserved.
11-12 Reserved.
13 Shall designate a clock that is synchronized to an application-specific source of time. The timescale distributed shall
be ARB. A clockClass 13 clock shall not be a slave to another clock in the domain.
14 Shall designate a clock that has previously been designated as clockClass 13 but that has lost the ability to
synchronize to an application-specific source of time and is in holdover mode and within holdover specifications. The
timescale distributed shall be ARB. A clockClass 14 clock shall not be a slave to another clock in the domain.
15-51 Reserved.
52 Degradation alternative A for a clock of clockClass 7 that is not within holdover specification. A clock of clockClass
52 shall not be a slave to another clock in the domain.
PtpClockQualityClassType (continued)
Table 34:
Value Description
53-57 Reserved.
58 Degradation alternative A for a clock of clockClass 14 that is not within holdover specification. A clock of clockClass
58 shall not be a slave to another clock in the domain.
59-67 Reserved.
123-127 Reserved.
128-132 Reserved.
171-186 Reserved.
187 Degradation alternative B for a clock of clockClass 7 that is not within holdover specification. A clock of clockClass
187 may be a slave to another clock in the domain.
188-192 Reserved.
193 Degradation alternative B for a clock of clockClass 14 that is not within holdover specification. A clock of clockClass
193 may be a slave to another clock in the domain.
194-215 Reserved.
233-247 Reserved.
248 Default. This clockClass shall be used if none of the other clockClass definitions apply.
249-250 Reserved.
251 Reserved for version 1 compatibility; see Clause 18.
252-254 Reserved.
PtpClockRoleType The Clock Role. The protocol generates a Master Slave relationship among the clocks in the system:
Table 35:
Master clock 1 A clock that is the source of time to which all other clocks on that path synchronize.
Freerun state 1 Applies to a slave device that is not locked to a master. This is the initial state a slave starts out with
when it is not getting any PTP packets from the master or because of some other input error (erroneous
packets, etc).
Holdover state 2 In this state the slave device is locked to a master but communication with the master has been lost or
the timestamps in the PTP packets are incorrect. Since the slave was locked to the master, it can run
in this state, with similar accuracy for some time. If communication with the master is not restored for
an extended period (dependent on the clock implementation), the device should move to the Freerun
state.
Acquiring 3 The slave device is receiving packets from a master and is trying to acquire a lock.
state
Freq_locked 4 Slave device is locked to the Master with respect to frequency, but not phase aligned.
state
PtpClockTimeInterval This textual convention corresponds to the TimeInterval structure indicated in section 5.3.2 of [IEEE 1588-2008]. It will be presented
in the form of a character array. Network byte order is assumed.
The TimeInterval type represents time intervals.
struct TimeInterval {Integer64 scaledNanoseconds}
The scaledNanoseconds member is the time interval expressed in units of nanoseconds and multiplied by 2**16. Positive or
negative time intervals outside the maximum range of this data type shall be encoded as the largest positive and negative values
of the data type, respectively. For example, 2.5 ns is expressed as string '0000 0000 0002 8000' in Base16.
PtpClockTimeSourceType The ClockQuality as specified in Sections 5.3.7, 7.6.2.6 and Table 7 of [IEEE 1588-2008].
The following values are not represented in the enumerated values:
■ 0xF0-0xFE - For use by alternate PTP profiles
■ 0xFF - Reserved
It is important to note that section 7.1.1 RFC 2578 allows for gaps and enumerate values to start with zero when indicated by the
protocol.
ptpSystemTable { ptpMIBSystemInfo 1 } Table of count information about the PTP system for all domains.
ptpSystemEntry { ptpSystemTable 1 } An entry in the table, containing count information about a single domain. New row entries
are added when the PTP clock for this domain is configured, while the unconfiguration of
the PTP clock removes it.
ptpDomainIndex { ptpSystemEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
The Clock Domain is a logical group of clocks and devices that synchronize with each
other using the PTP protocol:
Table 37:
Value Definition
0 Default domain
1 Alternate domain 1
2 Alternate domain 2
3 Alternate domain 3
28-255 Reserved
ptpInstanceIndex { ptpSystemEntry 2 } This object specifies the instance of the Clock for this domain.
ptpDomainClockPortsTotal { ptpSystemEntry 3 } This object specifies the total number of clock ports configured within a domain in the
system.
ptpSystemDomainTable { ptpMIBSystemInfo 2 } Table of information about the PTP system for all clock modes -- ordinary, boundary or
transparent.
ptpSystemDomainEntry { ptpSystemDomainTable 1 } An entry in the table, containing information about a single clock mode for the PTP system.
A row entry gets added when PTP clocks are configured on the node.
ptpSystemDomainClockTypeIndex { ptpSystemDomainEntry 1 } This object specifies the clock type as defined in the Textual convention description.
ptpSystemDomainTotals { ptpSystemDomainEntry 2 } This object specifies the total number of PTP domains for this particular clock type
configured in this node.
ptpSystemProfile { ptpMIBSystemInfo 3 } This object specifies the PTP Profile implemented on the system.
ptpClockCurrentDSTable { ptpMIBClockInfo 1 } Table of information about the PTP clock Current Datasets for all domains.
ptpClockCurrentDSEntry { ptpClockCurrentDSTable 1 } An entry in the table, containing information about a single PTP clock Current Datasets for
a domain.
ptpClockCurrentDSDomainIndex { ptpClockCurrentDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockCurrentDSClockTypeIndex { ptpClockCurrentDSEntry 2 } This object specifies the clock type as defined in the Textual convention description
ptpClockCurrentDSInstanceIndex { ptpClockCurrentDSEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockCurrentDSStepsRemoved { ptpClockCurrentDSEntry 4 The current clock dataset StepsRemoved value. This object specifies the distance
measured by the number of Boundary clocks between the local clock and the Foreign
master as indicated in the stepsRemoved field of Announce messages.
ptpClockCurrentDSOffsetFromMaster { ptpClockCurrentDSEntry 5 } This object specifies the current clock dataset ClockOffset value. The value of the
computation of the offset in time between a slave and a master clock
ptpClockCurrentDSMeanPathDelay { ptpClockCurrentDSEntry 6 } This object specifies the current clock dataset MeanPathDelay value. The mean path
delay between a pair of ports as measured by the delay request-response mechanism
ptpClockParentDSTable { ptpMIBClockInfo 2 } Table of information about the PTP clock Parent Datasets for all domains.
ptpClockParentDSEntry { ptpClockParentDSTable 1 } An entry in the table, containing information about a single PTP clock Parent Datasets for
a domain.
ptpClockParentDSDomainIndex { ptpClockParentDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockParentDSClockTypeIndex { ptpClockParentDSEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockParentDSInstanceIndex { ptpClockParentDSEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockParentDSParentPortIdentity { ptpClockParentDSEntry 4 } This object specifies the value of portIdentity of the port on the master that issues the Sync
messages used in synchronizing this clock.
ptpClockParentDSParentStats { ptpClockParentDSEntry 5 } This object specifies the Parent Dataset ParentStats value. This value indicates whether
the values of ParentDSOffset and ParentDSClockPhChRate have been measured and are
valid. A TRUE value shall indicate valid data.
ptpClockParentDSOffset { ptpClockParentDSEntry 6 } This object specifies the Parent Dataset ParentOffsetScaledLogVariance value. This value
is the variance of the parent clock's phase as measured by the local clock.
ptpClockParentDSClockPhChRate { ptpClockParentDSEntry 7 } This object specifies the clock's parent dataset ParentClockPhaseChangeRate value. This
value is an estimate of the parent clock's phase change rate as measured by the slave
clock.
ptpClockParentDSGMClockIdentity { ptpClockParentDSEntry 8 } This object specifies the parent dataset Grandmaster clock identity.
ptpClockParentDSGMClockPriority1 { ptpClockParentDSEntry 9 } This object specifies the parent dataset Grandmaster clock priority1.
ptpClockParentDSGMClockPriority2 { ptpClockParentDSEntry 10 } This object specifies the parent dataset grandmaster clock priority2.
ptpClockParentDSGMClockQualityClass { ptpClockParentDSEntry 11 } This object specifies the parent dataset grandmaster clock quality class.
ptpClockParentDSGMClockQualityAccuracy { ptpClockParentDSEntry 12 } This object specifies the parent dataset grandmaster clock quality accuracy.
ptpClockParentDSGMClockQualityOffset { ptpClockParentDSEntry 13 } This object specifies the parent dataset grandmaster clock quality offset.
ptpClockDefaultDSTable { ptpMIBClockInfo 3 } Table of information about the PTP clock Default Datasets for all domains.
ptpClockDefaultDSEntry { ptpClockDefaultDSTable 1 } An entry in the table, containing information about a single PTP clock Default Datasets for
a domain.
ptpClockDefaultDSDomainIndex { ptpClockDefaultDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockDefaultDSClockTypeIndex { ptpClockDefaultDSEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockDefaultDSInstanceIndex { ptpClockDefaultDSEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockDefaultDSTwoStepFlag { ptpClockDefaultDSEntry 4 } This object specifies whether the Two Step process is used.
ptpClockDefaultDSClockIdentity { ptpClockDefaultDSEntry 5 } This object specifies the default Datasets clock identity.
ptpClockDefaultDSPriority1 { ptpClockDefaultDSEntry 6 } This object specifies the default Datasets clock Priority1.
ptpClockDefaultDSPriority2 { ptpClockDefaultDSEntry 7 } This object specifies the default Datasets clock Priority2.
ptpClockDefaultDSQualityClass { ptpClockDefaultDSEntry 9 } This object specifies the default dataset Quality Class.
ptpClockDefaultDSQualityAccuracy { ptpClockDefaultDSEntry 10 } This object specifies the default dataset Quality Accuracy.
ptpClockDefaultDSQualityOffset { ptpClockDefaultDSEntry 11 } This object specifies the default dataset Quality offset.
ptpClockRunningTable { ptpMIBClockInfo 4 } Table of information about the PTP clock Default Datasets for all domains.
ptpClockRunningEntry { ptpClockRunningTable 1 } An entry in the table, containing information about a single PTP clock running Datasets for
a domain.
ptpClockRunningDomainIndex { ptpClockRunningEntry 1 } This object specifies the domain number used to create a Logical group of PTP devices.
ptpClockRunningClockTypeIndex { ptpClockRunningEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockRunningInstanceIndex { ptpClockRunningEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockRunningState { ptpClockRunningEntry 4 } This object specifies the Clock state returned by a PTP engine which was described
earlier.
Freerun state. Applies to a slave device that is not locked to a master. This is the initial
state a slave starts out with when it is not getting any PTP packets from the master, or
because of some other input error (erroneous packets, etc).
Holdover state. In this state the slave device is locked to a master but communication with
the master has been lost or the timestamps in the PTP packets are incorrect. Since the
slave was previously locked to the master, it can run in this state, with similar accuracy for
some time.
Acquiring state. The slave device is receiving packets from a master and is trying to
acquire a lock.
Freq_locked state. Slave device is locked to the Master with respect to frequency, but
not phase aligned.
Phase_aligned state. Locked to the master with respect to frequency and phase.
ptpClockRunningPacketsSent { ptpClockRunningEntry 5 } This object specifies the total number of all unicast and multicast packets that have been
sent out for this clock in this domain for this type. These counters are discontinuous.
ptpClockRunningPacketsReceived { ptpClockRunningEntry 6 } This object specifies the total number of all unicast and multicast packets that have been
received for this clock in this domain for this type. These counters are discontinuous.
ptpClockTimePropertiesDSTable { ptpMIBClockInfo 5 } Table of information about the PTP clock time properties datasets for all domains.
ptpClockTimePropertiesDSEntry { ptpClockTimePropertiesDSTable 1 } An entry in the table, containing information about a single PTP clock timeproperties
Datasets for a domain
ptpClockTimePropertiesDSDomainIndex { ptpClockTimePropertiesDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockTimePropertiesDSClockTypeIndex { ptpClockTimePropertiesDSEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockTimePropertiesDSInstanceIndex { ptpClockTimePropertiesDSEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockTimePropertiesDSCurrentUTCOffsetValid { ptpClockTimePropertiesDSEntry 4 } This object specifies the timeproperties dataset value of whether the current UTC offset is
valid.
ptpClockTimePropertiesDSCurrentUTCOffset { ptpClockTimePropertiesDSEntry 5 } This object specifies the timeproperties dataset value of the current UTC offset.
ptpClockTimePropertiesDSLeap59 { ptpClockTimePropertiesDSEntry 6 } This object specifies the Leap59 value in the clock Current Dataset.
ptpClockTimePropertiesDSLeap61 { ptpClockTimePropertiesDSEntry 7 } This object specifies the Leap61 value in the clock Current Dataset.
ptpClockTimePropertiesDSTimeTraceable { ptpClockTimePropertiesDSEntry 8 } This object specifies the Time Traceable value in the clock Current Dataset.
ptpClockTimePropertiesDSFreqTraceable { ptpClockTimePropertiesDSEntry 9 } This object specifies the Frequency Traceable value in the clock Current Dataset.
ptpClockTimePropertiesDSPTPTimescale { ptpClockTimePropertiesDSEntry 10 } This object specifies the PTP Timescale value in the clock Current Dataset.
ptpClockTimePropertiesDSSource { ptpClockTimePropertiesDSEntry 11 } This object specifies the Timesource value in the clock Current Dataset.
ptpClockTransDefaultDSTable { ptpMIBClockInfo 6 } Table of information about the PTP Transparent clock Default Datasets for all domains.
ptpClockTransDefaultDSEntry { ptpClockTransDefaultDSTable 1 } An entry in the table, containing information about a single PTP Transparent clock Default
Datasets for a domain.
ptpClockTransDefaultDSDomainIndex { ptpClockTransDefaultDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockTransDefaultDSInstanceIndex { ptpClockTransDefaultDSEntry 2 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockTransDefaultDSClockIdentity { ptpClockTransDefaultDSEntry 3 } This object specifies the value of the clockIdentity attribute of the local clock.
ptpClockTransDefaultDSNumOfPorts { ptpClockTransDefaultDSEntry 4 } This object specifies the number of PTP ports of the device. These counters are
discontinuous.
ptpClockTransDefaultDSDelay { ptpClockTransDefaultDSEntry 5 } This object, if the transparent clock is an end-to-end transparent clock, has the value of
E2E; if the transparent clock is a peer-to-peer transparent clock, the value shall be P2P.
ptpClockTransDefaultDSPrimaryDomain { ptpClockTransDefaultDSEntry 6 } This object specifies the value of the primary syntonization domain. The initialization value
shall be 0.
ptpClockPortTable { ptpMIBClockInfo 7 } Table of information about the clock ports for a particular domain.
ptpClockPortEntry { ptpClockPortTable 1 } An entry in the table, containing information about a single clock port.
ptpClockPortDomainIndex { ptpClockPortEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockPortClockTypeIndex { ptpClockPortEntry 2 } This object specifies the clock type as defined in the Textual convention description
ptpClockPortClockInstanceIndex { ptpClockPortEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockPortTablePortNumberIndex { ptpClockPortEntry 4 } This object specifies the PTP Portnumber for this port.
ptpClockPortName { ptpClockPortEntry 5 } This object specifies the PTP clock port name configured on the node.
ptpClockPortRole { ptpClockPortEntry 6 } This object describes the current role (slave/master) of the port.
ptpClockPortSyncTwoStep { ptpClockPortEntry 7 } This object specifies that two-step clock operation between the PTP master and slave
device is enabled
ptpClockPortCurrentPeerAddressType { ptpClockPortEntry 8 } This object specifies the current peer's network address type used for PTP
communication.
ptpClockPortCurrentPeerAddress { ptpClockPortEntry 9 } This object specifies the current peer's network address used for PTP communication.
ptpClockPortNumOfAssociatedPorts { ptpClockPortEntry 10 } For a master port - the number of PTP slave sessions (peers) associated with this PTP
port.
For a slave port - the number of masters available to this slave port (might or might not be
peered).
ptpClockPortDSTable { ptpMIBClockInfo 8 } Table of information about the clock ports dataset for a particular domain.
ptpClockPortDSEntry { ptpClockPortDSTable 1 } An entry in the table, containing port dataset information for a single clock port.
ptpClockPortDSDomainIndex { ptpClockPortDSEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockPortDSClockTypeIndex { ptpClockPortDSEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockPortDSClockInstanceIndex { ptpClockPortDSEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockPortDSPortNumberIndex { ptpClockPortDSEntry 4 } This object specifies the PTP portnumber associated with this PTP port.
ptpClockPortDSName { ptpClockPortDSEntry 5 } This object specifies the PTP clock port dataset name.
ptpClockPortDSPortIdentity { ptpClockPortDSEntry 6 } This object specifies the PTP clock port Identity.
ptpClockPortDSlogAnnouncementInterval { ptpClockPortDSEntry 7 } This object specifies the Announce message transmission interval associated with this
clock port.
ptpClockPortDSAnnounceRctTimeout { ptpClockPortDSEntry 8 } This object specifies the Announce receipt timeout associated with this clock port
ptpClockPortDSlogSyncInterval { ptpClockPortDSEntry 9 } This object specifies the Sync message transmission interval.
ptpClockPortDSMinDelayReqInterval { ptpClockPortDSEntry 10 } This object specifies the Delay_Req message transmission interval.
ptpClockPortDSPeerDelayReqInterval { ptpClockPortDSEntry 11 } This object specifies the Pdelay_Req message transmission interval.
ptpClockPortDSDelayMech { ptpClockPortDSEntry 12 } This object specifies the delay mechanism used. If the clock is an end-to-end clock, the
value of the is e2e, else if the clock is a peer to-peer clock, the value shall be p2p.
ptpClockPortDSPeerMeanPathDelay { ptpClockPortDSEntry 13 } This object specifies the peer meanPathDelay.
ptpClockPortDSGrantDuration { ptpClockPortDSEntry 14 } This object specifies the grant duration allocated by the master.
ptpClockPortDSPTPVersion { ptpClockPortDSEntry 15 } This object specifies the PTP version being used.
ptpClockPortRunningTable { ptpMIBClockInfo 9 } Table of information about the clock ports running datasets for a particular domain
ptpClockPortRunningEntry { ptpClockPortRunningTable 1 } An entry in the table, containing running dataset information about a single clock port.
ptpClockPortRunningDomainIndex { ptpClockPortRunningEntry 1 } This object specifies the domain number used to create a logical group of PTP devices.
ptpClockPortRunningClockTypeIndex { ptpClockPortRunningEntry 2 } This object specifies the clock type as defined in the Textual convention description.
ptpClockPortRunningClockInstanceIndex { ptpClockPortRunningEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockPortRunningPortNumberIndex { ptpClockPortRunningEntry 4 } This object specifies the PTP portnumber associated with this clock port
ptpClockPortRunningName { ptpClockPortRunningEntry 5 } This object specifies the PTP clock port name.
ptpClockPortRunningState { ptpClockPortRunningEntry 6 } This object specifies the port state returned by PTP engine:
Table 38:
Initializing In this state a port initializes its data sets, hardware, and communication
facilities.
disabled The port shall not place any messages on its communication path.
preMaster The port shall behave in all respects as though it were in the MASTER
state except that it shall not place any messages on its communication
path except for Pdelay_Req, Pdelay_Resp,
Pdelay_Resp_Follow_Up, signaling, or management messages.
passive The port shall not place any messages on its communication path
except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, or
signaling messages, or management messages that are a required
response to another management message.
ptpClockPortRunningInterfaceIndex { ptpClockPortRunningEntry 8 } This object specifies the interface on the node being used by the PTP Clock for PTP
communication.
ptpClockPortRunningTransport { ptpClockPortRunningEntry 9 } This object specifies the transport protocol being used for PTP communication (the
mapping used).
ptpClockPortRunningEncapsulationType { ptpClockPortRunningEntry 10 } This object specifies the type of encapsulation if the interface is adding extra layers (e.g.,
VLAN, Pseudowire encapsulation...) for the PTP messages.
ptpClockPortRunningTxMode { ptpClockPortRunningEntry 11 } This object specifies the clock transmission mode as:
■ unicast: Using unicast communication channel.
■ multicast: Using Multicast communication channel.
■ multicast-mix: Using multicast-unicast communication channel.
ptpClockPortRunningRxMode { ptpClockPortRunningEntry 12 } This object specifies the clock receive mode as:
■ unicast: Using unicast communication channel.
■ multicast: Using Multicast communication channel.
■ multicast-mix: Using multicast-unicast communication channel.
ptpClockPortRunningPacketsReceived { ptpClockPortRunningEntry 13 } This object specifies the packets received on the clock port (cumulative). These counters
are discontinuous.
ptpClockPortRunningPacketsSent { ptpClockPortRunningEntry 14 } This object specifies the packets sent on the clock port (cumulative). These counters are
discontinuous.
ptpClockPortTransDSTable { ptpMIBClockInfo 10 } Table of information about the Transparent clock ports running dataset for a particular
domain.
ptpClockPortTransDSEntry { ptpClockPortTransDSTable 1 } An entry in the table, containing clock port Transparent dataset information about a single
clock port.
ptpClockPortTransDSDomainIndex { ptpClockPortTransDSEntry 1 } This object specifies the domain number used to create a Logical group of PTP devices.
ptpClockPortTransDSInstanceIndex { ptpClockPortTransDSEntry 2 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockPortTransDSPortNumberIndex { ptpClockPortTransDSEntry 3 } This object specifies the PTP port number associated with this port.
ptpClockPortTransDSPortIdentity { ptpClockPortTransDSEntry 4 } This object specifies the value of the PortIdentity attribute of the local port.
ptpClockPortTransDSlogMinPdelayReqInt { ptpClockPortTransDSEntry 5 } This object specifies the value of the logarithm to the base 2 of the minPdelayReqInterval.
ptpClockPortTransDSFaultyFlag { ptpClockPortTransDSEntry 6 } This object specifies the value TRUE if the port is faulty and FALSE if the port is operating
normally.
ptpClockPortTransDSPeerMeanPathDelay { ptpClockPortTransDSEntry 7 } This object specifies, if the delayMechanism used is P2P, the value of the estimate of the
current one-way propagation delay, i.e., <meanPathDelay> on the link attached to this
port, computed using the peer delay mechanism. If the value of the delayMechanism used
is E2E, then the value will be zero.
ptpClockPortAssociateEntry { ptpClockPortAssociateTable 1 } An entry in the table, containing information about a single associated port for the given
clockport.
ptpClockPortCurrentDomainIndex { ptpClockPortAssociateEntry 1 } This object specifies the given port's domain number.
tpClockPortCurrentClockTypeIndex { ptpClockPortAssociateEntry 2 } This object specifies the given port's clock type.
ptpClockPortCurrentClockInstanceIndex { ptpClockPortAssociateEntry 3 } This object specifies the instance of the clock for this clock type in the given domain.
ptpClockPortCurrentPortNumberIndex { ptpClockPortAssociateEntry 4 } This object specifies the PTP Port Number for the given port.
ptpClockPortAssociatePortIndex { ptpClockPortAssociateEntry 5 } This object specifies the associated port's serial number in the current port's context
ptpClockPortAssociateAddressType { ptpClockPortAssociateEntry 6 } This object specifies the peer port's network address type used for PTP communication.
The OCTET STRING representation of the OID of ptpWellKnownTransportTypes will be
used in the values contained in the OCTET STRING.
ptpClockPortAssociateAddress { ptpClockPortAssociateEntry 7 } This object specifies the peer port's network address used for PTP communication.
ptpClockPortAssociatePacketsSent { ptpClockPortAssociateEntry 8 } The number of packets sent to this peer port from the current port. These counters are
discontinuous.
ptpClockPortAssociatePacketsReceived { ptpClockPortAssociateEntry 9 } The number of packets received from this peer port by the current port. These counters
are discontinuous.
ptpClockPortAssociateInErrors { ptpClockPortAssociateEntry 10 } This object specifies the input errors associated with the peer port. These counters are
discontinuous
ptpClockPortAssociateOutErrors { ptpClockPortAssociateEntry 11 } This object specifies the output errors associated with the peer port. These counters are
discontinuous.
ptpMIBCompliances { ptpMIBConformance 1 } Conformance Information Definition.
ptpMIBCompliancesSystemInfo { ptpMIBCompliances 1 } Compliance statement for agents that provide read-only support for PTPBASE-MIB to
provide system level information of clock devices. Such devices can only be monitored
using this MIB module.
The Module is implemented with support for read-only. In other words, only monitoring is
available by implementing this MODULE-COMPLIANCE.
ptpMIBCompliancesClockInfo { ptpMIBCompliances 2 } Compliance statement for agents that provide read-only support for PTPBASE-MIB to
provide clock related information. Such devices can only be monitored using this MIB
module.
The Module is implemented with support for read-only. In other words, only monitoring is
available by implementing this MODULE-COMPLIANCE.
ptpMIBCompliancesClockPortInfo { ptpMIBCompliances 3 } Compliance statement for agents that provide read-only support for PTPBASE-MIB to
provide clock port related information.
Such devices can only be monitored using this MIB module.
The Module is implemented with support for read-only. In other words, only monitoring is
available by implementing this MODULE-COMPLIANCE.
ptpMIBCompliancesTransparentClockInfo { ptpMIBCompliances 4 } Compliance statement for agents that provide read-only support for PTPBASE-MIB to
provide Transparent clock related information. Such devices can only be monitored using
this MIB module.
The Module is implemented with support for read-only. In other words, only monitoring is
available by implementing this MODULE-COMPLIANCE.
ptpMIBClockCurrentDSGroup { ptpMIBGroups 2 } Group which aggregates objects describing PTP Current Dataset information.
ptpMIBClockParentDSGroup { ptpMIBGroups 3 } Group which aggregates objects describing PTP Parent Dataset information.
ptpMIBClockDefaultDSGroup { ptpMIBGroups 4 } Group which aggregates objects describing PTP Default Dataset information.
ptpMIBClockRunningGroup { ptpMIBGroups 5 } Group which aggregates objects describing PTP running state information.
ptpMIBClockTimepropertiesGroup { ptpMIBGroups 6 } Group which aggregates objects describing PTP Time Properties information.
ptpMIBClockTranparentDSGroup { ptpMIBGroups 7 } Group which aggregates objects describing PTP Transparent Dataset information.
ptpMIBClockPortGroup { ptpMIBGroups 8 } Group which aggregates objects describing information for a given PTP Port.
ptpMIBClockPortDSGroup { ptpMIBGroups 9 } Group which aggregates objects describing PTP Port Dataset information.
ptpMIBClockPortRunningGroup { ptpMIBGroups 10 } Group which aggregates objects describing PTP running interface information.
ptpMIBClockPortTransDSGroup { ptpMIBGroups 11 } Group which aggregates objects describing PTP TransparentDS information.
ptpMIBClockPortAssociateGroup { ptpMIBGroups 12 } Group which aggregates objects describing information on peer PTP ports for a given PTP
clock-port.
AT-QOSv2-MIB
See Table 39 for the list of objects defined in the AT-QOSv2-MIB. These objects manage
notifications and variables for the QoS module. Objects in this group have the object identifier
atQosv2 { modules 503 } OID 1.3.6.1.4.1.207.8.4.4.4.503.
atQosv2IfIndex { atQosv2NotificationVariables 1 } The index of the interface where the storm is detected
on.
atQosv2VlanId { atQosv2NotificationVariables 2 } The VLAN ID of the interface where the storm is
detected on.
AT-RESOURCE-MIB
The AT-RESOURCE-MIB contains objects for displaying system hardware resource and host
information, see Table 40. Objects in this group have the object identifier rsc { sysinfo 21 }, OID
1.3.6.1.4.1.207.8.4.4.3.21. See “AT-SYSINFO-MIB” on page 116.
resource { sysinfo 21 } Contains objects for displaying system hardware resource and
1.3.6.1.4.1.207.8.4.4.3.21 host information.
rscBoardName { rscBoardEntry 4 } The name of the board. Can be one of the following:
■ SwitchBlade x908
■ XEM-12S
■ AT-PWR05-AC.
rscBoardId { rscBoardEntry 5 } The ID number of the board. Its value is an Allied Telesis assigned
number, such as 274 for the XEM-12S, or 255 for the AT-9924Ts.
rscBoardBay { rscBoardEntry 6 } The board installation location. Its value can be Bay1, Bay2, PSU1.
For a base board, it has a value of a single character space.
rscBoardRevision { rscBoardEntry 7 } The revision number of the board.
AT-SETUP-MIB
AT-SETUP-MIB defines objects for managing software installation and configuration files, see
Figure 6 and Table 41. Objects in this group have the object identifier setup { modules 500 }, OID
1.3.6.1.4.1.207.8.4.4.4.500. To see how to use these MIB objects to upgrade to a new software
version and boot configuration file, see the SNMP Feature Overview and Configuration Guide. For
objects used for file copying, see “AT-FILEv2-MIB” on page 46.
enterprises (1)
alliedTelesis (207)
atRouter (4)
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces protocols (6)
setup (500)
backupFirmware (3)
backupCnfgLastSetResult (4)
setup_mib_tree
restartDevice { setup 1 } Object for restarting the device. When set to ‘1’, the device will
1.3.6.1.4.1.207.8.4.4.4.500.1 restart immediately.
firmware { setup 2 } Objects for managing the software version files that the device
1.3.6.1.4.1.207.8.4.4.4.500.2 will install and run.
currentFirmware { firmware 1 } Information about the current software version installed on the
device.
currSoftVersion { currentFirmware 1 } Current software version.
currSoftSaveAs { currentFirmware 3 } The file name to save the currently running software to the root
of the Flash. Only one save operation can be executed at a time
across all SNMP users.
currSoftSaveToFile { currentFirmware 4 } Set with a URL to save the currently running software to the root
of Flash or USB Flash drive (e.g. 'flash:/filename.rel' or 'USB:/
filename.rel'). The URL must not contain whitespace characters.
Only one save operation can be executed at a time across all
SNMP users and an operation may not be started unless the
current value of currSoftSaveStatus is 'idle'. Immediately upon
executing the set action, the actual firmware save operation is
started and will continue on the device until it has completed or
a failure occurs. When read, this object will return the URL of the
last firmware save operation that was attempted.
currSoftSaveStatus { currentFirmware 5 } This object will return the status of any current operation to store
the running software to a release file. The following values may
be returned:
■ (idle) - there is no release file save operation in progress.
■ (success) - the last release file save operation completed
successfully.
■ (failure) - the last release file save operation failed.
■ (saving) - a release file save operation is currently in
progress.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
currSoftLastSaveResult.
currSoftLastSaveResult { currentFirmware 6 } Gives an indication of the result of the last completed SNMP
operation to save the running firmware to a release file.
nextBootFirmware { firmware 2 } Information about the software version to be installed on the
device when booting.
nextBootPath { nextBootFirmware 2 } The full path to the release file that will be used the next time the
device is rebooted. The URL must not contain whitespace
characters. Only one set operation can be executed at a time
across all SNMP users and an operation may not be started
unless the current value of nextBootSetStatus is 'idle'.
Immediately upon executing the set action, the system will
attempt to set the new configuration path, and the process will
continue on the device until it has completed or a failure occurs.
This object can be set with an empty string in order to clear the
current boot firmware. Otherwise, the path should be of the form
‘flash:/filename.cfg’ or 'card:/filename.cfg'. In order to set this
object, the file must meet the following conditions:
■ it must exist.
■ it must be located in the root of Flash (on the active master
in a stacked environment) or USB flash drive.
■ it must not be the same as the backup release file.
■ it must have a .rel suffix.
■ it must pass several internal checks to ensure that it is a
genuine release file.
■ in a stacked environment, there must be enough disk space
available to store the release file on each stack member.
nextBootSetStatus { nextBootFirmware 3 } Returns the status of any current operation to set the next boot
release file. The following values may be returned:
■ 1 (idle) - there is no boot release setting operation in
progress.
■ 2 (success) - the last boot release setting operation
completed successfully.
■ 3 (failure) - the last boot release setting operation failed.
■ 5 (syncing) - a boot release setting operation is currently in
progress and the file is being synchronized across the
stack.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
nextBootLastSetResult.
nextBootLastSetResult { nextBootFirmware 4 } Gives an indication of the result of the last completed SNMP
operation to set the boot release filename.
backupFirmware { firmware 3 } Information about the backup software version and path.
backupPath { backupFirmware 2 } The full path to the backup release file that will be used the next
time the device is rebooted. The URL must not contain
whitespace characters. Only one set operation can be executed
at a time across all SNMP users and an operation may not be
started unless the current value of backupSetStatus is 'idle'.
Immediately upon executing the set action, the system will
attempt to set the new configuration path, and the process will
continue on the device until it has completed or a failure occurs.
This object can be set with an empty string in order to clear the
current backup firmware. Otherwise, the path should be of the
form ‘flash:/filename.cfg’ or 'card:/filename.cfg'. In order to set
this object, the file must meet the following conditions:
■ it must exist.
■ it must be located in the root of Flash (on the active master
in a stacked environment) or USB flash drive.
■ it must not be the same as the configured main release file.
■ it must have a .rel suffix.
■ it must pass several internal checks to ensure that it is a
genuine release file.
■ in a stacked environment, there must be enough disk space
available to store the release file on each stack member.
backupSetStatus { backupFirmware 3 } Returns the status of any current operation to set the backup
boot release file. The following values may be returned:
■ 1 (idle) - there is no backup boot release setting operation in
progress.
■ 2 (success) - the last backup boot release setting operation
completed successfully.
■ 3 (failure) - the last backup boot release setting operation
failed.
■ 5 (syncing) - a backup boot release setting operation is
currently in progress and the file is being synchronized
across the stack.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
backupLastSetResult.
backupLastSetResult { backupFirmware 4 } Gives an indication of the result of the last completed SNMP
operation to set the backup boot release filename.
deviceConfiguration { setup 3 Objects for managing device configuration.
1.3.6.1.4.1.207.8.4.4.4.500.3
runningConfig { deviceConfiguration 1 } Set with a URL to save the running configuration to the Flash or
Card filesystem using that filename (e.g.'flash:/myconfig.cfg' or
'card:/myconfig.cfg').
runCnfgSaveAs { runningConfig 1 } Set with a URL to save the currently running software to the root
of Flash or USB flash drive (e.g. 'flash:/filename.rel' or 'usb:/
filename.rel'). The URL must not contain whitespace characters.
Only one set operation can be executed at a time across all
SNMP users and an operation may not be started unless the
current value of runCnfgSaveAsStatus is 'idle'. Immediately
upon executing the set action, the system will attempt to save
the running configuration and the process will continue on the
device until it has completed or a failure occurs. When read, this
object will return the URL of the last firmware save operation
that was attempted.
runCnfgSaveAsStatus { runningConfig 2 } Returns the status of any current operation to save the running
configuration. The following values may be returned:
■ (idle) - there is no config file save operation in progress.
■ (success) - the last config file save operation completed
successfully.
■ (failure) - the last config file save operation failed.
■ (saving) - a config file save operation is currently in
progress.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
runCnfgLastSaveResult.
runCnfgLastSaveResult { runningConfig 3 } Gives an indication of the result of the last completed SNMP
operation to save the running configuration.
nextBootConfig { deviceConfiguration 2 } The full path of the configuration file to be used the next time the
device restarts. There is no guarantee that the file referenced
exists (i.e. it may have been deleted since the configuration path
was last set).
bootCnfgPath { nextBootConfig 1 } The full path to the configuration file that will be used the next
time the device is rebooted. The URL must not contain
whitespace characters. Only one set operation can be executed
at a time across all SNMP users and an operation may not be
started unless the current value of bootCnfgSetStatus is 'idle'.
Immediately upon executing the set action, the system will
attempt to set the new configuration path, and the process will
continue on the device until it has completed or a failure occurs.
This object can be set with an empty string in order to clear the
current boot configuration. Otherwise, the path should be of the
form ‘flash:/myconfig.cfg’ or 'card:/filename.cfg'. In order to set
this object, the file must meet the following conditions:
■ it must exist.
■ it must be located in the root of Flash (on the active master
in a stacked environment) or USB flash drive.
■ it must have a .cfg suffix.
■ in a stacked environment, there must be enough disk space
available to store the configuration file on each stack
member.
bootCnfgExists { nextBootConfig 2 } This object will return the value TRUE if the currently defined
boot configuration file exists, or FALSE if it does not.
bootCnfgSetStatus { nextBootConfig 3 } Returns the status of any current operation to set the next boot
configuration file. The following values may be returned:
■ 1 (idle) - there is no boot configuration setting operation in
progress.
■ 2 (success) - the last boot configuration setting operation
completed successfully.
■ 3 (failure) - the last boot configuration setting operation
failed.
■ 5 (syncing) - a boot configuration setting operation is
currently in progress and the file is being synchronized
across the stack.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
bootCnfgLastSetResult.
bootCnfgLastSetResult { nextBootConfig 4 } Gives an indication of the result of the last completed SNMP
operation to set the boot configuration filename.
defaultConfig { deviceConfiguration 3 } The full path of the configuration file to be used upon device
restart, if no user-defined boot or backup configuration files can
be found. There is no guarantee that the file referenced exists
(i.e. it may have been deleted).
dfltCnfgPath { defaultConfig 1 } The full path of the configuration file to use as backup when the
device is rebooted. This object is not settable. The default
configuration file is always ‘flash:/default.cfg’.
dfltCnfgExists { defaultConfig 2 } This object will return the value TRUE if the currently defined
default configuration file exists, or FALSE if it does not.
backupConfig { deviceConfiguration 4 } The full path of the backup configuration file to be used the next
time the device restarts, if the boot configuration file cannot be
accessed. There is no guarantee that the file referenced exists
(i.e. it may have been deleted since the backup configuration
path was last set).
backupCnfgPath { backupConfig 1 } The full path to the backup configuration file that will be used the
next time the device is rebooted. The URL must not contain
whitespace characters. Only one set operation can be executed
at a time across all SNMP users and an operation may not be
started unless the current value of backupCnfgSetStatus is
'idle'. Immediately upon executing the set action, the system
will attempt to set the new backup configuration path, and the
process will continue on the device until it has completed or a
failure occurs. This object can be set with an empty string in
order to clear the current boot configuration. Otherwise, the
path should be of the form ‘flash:/myconfig.cfg’ or 'card:/
filename.cfg'. In order to set this object, the file must meet the
following conditions:
■ it must exist.
■ it must be located in the root of Flash (on the active master
in a stacked environment) or USB flash drive.
■ it must have a .cfg suffix.
■ in a stacked environment, there must be enough disk space
available to store the configuration file on each stack
member.
backupCnfgExists { backupConfig 2 } This object will return the value TRUE if the currently defined
backup configuration file exists, or FALSE if it does not.
backupCnfgSetStatus { backupConfig 3 } Returns the status of any current operation to set the next
backup boot configuration file. The following values may be
returned:
■ 1 (idle) - there is no backup boot configuration setting
operation in progress.
■ 2 (success) - the last backup boot configuration setting
operation completed successfully.
■ 3 (failure) - the last backup boot configuration setting
operation failed.
■ 5 (syncing) - a backup boot configuration setting operation
is currently in progress and the file is being synchronized
across the stack.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new operation
may be initiated if desired. A detailed description of the last
completed operation may be determined by reading
backupCnfgLastSetResult.
backupCnfgLastSetResult { backupConfig 4 } Gives an indication of the result of the last completed SNMP
operation to set the backup boot configuration filename.
serviceConfig { setup 5 } This object represents the state of the telnet server of a device.
1.3.6.1.4.1.207.8.4.4.4.500.5
srvcTelnetEnable { serviceConfig 1 } This object is used to either read or set the state of the telnet
server on a device. Telnet can be enabled by setting the value of
this object to ‘enable(1)’ or can be disabled by setting the value
‘disable(2)’.
srvcSshEnable { serviceConfig 2 } This object is used to either read or set the state of the SSH
server on a device. SSH can be enabled by setting the value of
this object to ‘enable(1)’ or can be disabled by setting the value
‘disable(2)’.
guiConfig { setup 6 } This object represents the system software release that the
1.3.6.1.4.1.207.8.4.4.4.500.6 currently selected GUI applet was designed to run on.
guiAppletConfig { guiConfig 1 } This object represents the system software release that the
currently selected GUI applet was designed to run on.
guiAppletSysSwVer { guiAppletConfig 1 } This object represents the system software release that the
currently selected GUI applet was designed to run on. The
system automatically searches for GUI applet files that reside in
the root directory of the Flash memory, and selects the latest
available file that is applicable to the currently running system
software. This is the applet that will be uploaded to a user's web
browser when they initiate the GUI.
guiAppletSwVer { guiAppletConfig 2 } This object represents the software version of the currently
selected GUI applet. The system automatically searches for GUI
applet files residing in the root directory of the Flash memory,
and selects the latest available one that is applicable to the
currently running system software. This is the applet that will be
uploaded to a user's web browser when they initiate the GUI.
AT-SYSINFO-MIB
AT-SYSINFO-MIB defines objects that describe generic system information and environmental
monitoring. Objects in this group have the object identifier sysinfo { atRouter 3 }, OID
1.3.6.1.4.1.207.8.4.4.3. Table 42 lists the objects supported by the AlliedWare Plus sysinfo MIB.
AT-TRIGGER-MIB
AT-TRIGGER-MIB defines objects for managing triggers Table 43. Objects in this group have the
object identifier trigger { modules 53 }, OID 1.3.6.1.4.1.207.8.4.4.4.53. All objects in this group have
read only access.
triggerLasttimeActivation { triggerConfigInfoEntry 13 } Date and time that the trigger was last
activated.
triggerScript2 { triggerConfigInfoEntry 16 } Name of the second script that this trigger will
execute if the trigger is activated.
triggerScript3 { triggerConfigInfoEntry 17 } Name of the third script that this trigger will
execute if the trigger is activated.
triggerScript4 { triggerConfigInfoEntry 18 } Name of the fourth script that this trigger will
execute if the trigger is activated.
triggerScript5 { triggerConfigInfoEntry 19 } Name of the fifth script that this trigger will
execute if the trigger is activated.
AT-UDLD-MIB
see Table 44 for the list of objects defined in the AT-UDLD-MIB. These objects contain definitions of
managed objects for the UniDirectional Link Detection (UDLD) protocol. Objects in this group have
the object identifier atQosv2 { modules 550 } OID 1.3.6.1.4.1.207.8.4.4.4.550.
AT-UFO-MIB
AT-UFO-MIB defines objects for managing Upstream Forwarding Only (UFO) for private VLANs, see
Table 45. Objects in this group have the object identifier atUfo in { modules 605 }, OID
1.3.6.1.4.1.8.4.4.4.605
Table 45: Objects defined by the AT-UFO-MIB
atUfo { modules 605 } This MIB file contains definitions of managed objects
(1.3.6.1.4.1.207.8.4.4.4.605) for the UFO module.
atUfoTraps { atUfo 0 } Traps generated when a UFO private VLAN state
(605.0) changes. One of the following:
■ atUfoVlanBlackHoleTrap
■ atUfoBlackHoleAlarmTrap.
atUfoBlackHoleAlarmTrap { atUfoTraps 2 } Generated when the first UFO private VLAN transitions
(605.0.2) to the blackhole state indicating an alarm has been
triggered, and, when the last UFO private VLAN
transitions to the non-blackhole state it indicates the
alarm has been cleared:
■ atUfoAlarmState.
AT-USER-MIB
The AT-USER-MIB contains objects for displaying information about users currently logged into a
device, or configured in the Local User Database of the device Table 46. Objects in this group have
the object identifier user { sysinfo 20 }, OID 1.3.6.1.4.1.207.8.4.4.3.20.
userInfoIndex { userInfoEntry 2 } Index of the line upon which the user logged into the
device. Can be a value in range 1 to 16.
userInfoName { userInfoEntry 3 } User name of the user logged into the device.
userInfoPrivilegeLevel { userInfoEntry 4 } The user’s privilege level. Can be a value in range 1
to 15.
userInfoIdleTime { userInfoEntry 5 } The amount of time since the user was last active, in
the form hh:mm:ss.
userInfoLocation { userInfoEntry 6 } The user location or login method. It can be an IP
Address used by the user to telnet into the device, or
an asyn port.
userInfoPasswordLastChange { userInfoEntry 8 } The number of days since the password was last
altered.
AT-VCSTACK-MIB
AT-VCSTACK-MIB defines objects for managing Virtual Chassis Stacking, see Table 47. Objects in
this group have the object identifier vcstack { sysinfo 13 }, OID 1.3.6.1.4.1.207.8.4.4.3.13.
Figure 7 on page 125 shows the tree structure of the AT-VCSTACK objects.
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces (5) protocols (6)
vcstack (13)
vcstackRoleChangeNotify (1)
vcstackEntry (1)
vcstackMemberJoinNotify (2)
vcstackId (1)
vcstackMemberLeaveNotify (3)
vcstackPendingId (2)
vcstackResiliencyLinkHealthCheckReceivingNotify (4)
vcstackMacAddr (3)
vcstackResiliencyLinkHealthCheckTimeOutNotify (5 )
vcstackPriority (4)
vcstackStkPortLinkUpNotify (6)
vcstackRole (5)
vcstackStkPortLinkDownNotify (7)
vcstackStatus (1) vcstackLastRoleChange (6)
vcstackNbrMemberIdNotify (8)
vcstackHostname (7)
vcstackStkPortNameNotify (9) vcstackOperational Status (2)
vcstackProductType (8)
vcstackSWVersionAutoSync (9)
vcstackMgmtVlanId (3)
vcstackFallbackConfigStatus (10)
vcstackFallbackConfigFilename (11)
vcstackMgmtVlanSubnetAddr (4)
vcstackResiliencyLinkStatus (12)
vcstackResiliencyLinkInterfaceName (13)
vcstackVirtualMacAddressStatus (7)
vcstackActiveStkHardware (14)
vcstackStkPort1Status (15)
vcstackVirtualChassisId (8)
vcstackStkPort1NeighbourId (16)
vcstackStkPort2Status (17)
vcstackVirtualMacAddr (9)
vcstackStkPort2NeighbourId (18)
vcstackNumMembersJoined (19)
vcstackMasterId (10)
vcstackNumMembersLeft (20)
vcstackNumIdConflict (21)
vcstackNumMasterConflict (22)
vcstackNumMasterFailover (23)
vcstackNumStkPort1NbrIncompatible (24)
vcstackNumStkPort2NbrIncompatible (25)
VCStack_MIB
AT-VLAN-MIB
The atVlanStatistics-MIB Figure 8, and Table 48 defines objects for managing VLANs. The MIB
contains a sub tree for managing VLAN statistics. Objects in the VLAN Statistics sub-tree have the
object identifier atvlaninfo { sysinfo 16 } OID, 1.3.6.1.4.1.207.8.4.4.3.16. see “AT-SYSINFO-MIB” on
page 116.
objects (1) traps (2) sysinfo (3) modules (4) arInterfaces (5) protocols (6)
atVlanInfo (16)
atVlanStatCollectionTable (2)
atVlanStatCollectionEntry (1)
atVlanStatCollectionName (1)
atVlanStatCollectionVlanId (2)
atVlanStatCollectionPortMap (3)
atVlanStatCollectionIngressPkts (4)
atVlanStatCollectionIngressOctets (5)
atVlanStatCollectionResetStats (6)
atVLANStatistics_MIB
atvlaninfo { sysinfo 16 } Root of the Allied Telesis Enterprise MIB under the
1.3.6.1.4.1.207.8.4.4.3.16. private(4) node defined in RFC1155-SMI.
atVlanStatCollectionResetStats { atVlanStatCollectionEntry 6 } When read, this object will always return 2 (false).
Setting its value to 1 (true) will cause the matching
VLAN statistics collection instance's ingress
packets and ingress octet values to be reset to
zero.
AT-XEM-MIB
AT-XEM-MIB defines objects for managing XEMs (Expansion Modules) installed in the device
Table 49. Objects in this group have the object identifier xem { sysinfo 11 } OID,
1.3.6.1.4.1.207.8.4.4.3.11 and reside in the sysinfo Group of the Allied Telesis Enterprise MIB.
Table 49: Objects defined in AT-XEM-MIB
xemInfoBayId { xemInfoEntry 2 } Number of the XEM bay in which the XEM is installed.
xemInfoXemId { xemInfoEntry 3 } Numeric board identity of the XEM. This information is displayed in
the ID column of the SHOW SYSTEM command.
xemInfoBoardType { xemInfoEntry 4 } Board type. For XEMs this is always “Expansion”. This information is
displayed in the Board column of the SHOW SYSTEM command.
xemInfoBoardName { xemInfoEntry 5 } Name of the XEM. This information is displayed in the Board Name
column of the SHOW SYSTEM command.
xemInfoRevision { xemInfoEntry 6 } Board revision of the XEM. This information is displayed in the Rev
column of the SHOW SYSTEM command.
xemInfoSerialNumber { xemInfoEntry 7 } Serial number of the XEM. This information is displayed in the Serial
Number column of the SHOW SYSTEM command.
sFlow-MIB
The sFlow-MIB Figure 9, and Table 50 show references to objects for managing the generation and
transportation of sFlow data records.
sFlow-MIB All MIB objects are fully supported. For more information, see
www.sflow.org/SFLOW-MIB5.txt.
internet (1)
sFlow-MIB (1)
Public MIBs
The following table lists the public MIBs supported by the AlliedWare PlusTM Operating System. In
general, all objects are supported except where the relevant protocol or feature is either not
supported or not applicable to the device. Any variations from the standard are listed.
RFC1155-SMI RFC 1155, Structure and Identification of Management Information for TCP/IP-based Internets.
- RFC 1215, A Convention for Defining Traps for use with the SNMP.
BGP4-MIB RFC 1657, Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol
(BGP-4) using SMIv2.
IP-MIB The IP MIB tree encompasses IP-MIB, RFC1213-MIB and IP-FORWARD-MIB definitions. The
following documents define the components:
■ RFC 1213, Management Information Base for Network Management of TCP/IP-based
internets: MIB-II
■ RFC 4292, IP Forwarding Table MIB
■ RFC 4293, Management Information Base for the Internet Protocol (IP).
TCP-MIB RFC 2012, SNMPv2 Management Information Base for the Transmission Control Protocol using
SMIv2.
UDP-MIB RFC 2013, SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2.
SNMP-MPD-MIB RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol
(SNMP).
SNMP-COMMUNITY-MIB RFC 2576, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard
Network Management Framework.
SNMPv2-SMI RFC 2578, Structure of Management Information Version 2 (SMIv2).
P-BRIDGE-MIB RFC 2674, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and
Virtual LAN Extensions.
Q-BRIDGE-MIB RFC 2674, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and
Virtual LAN Extensions.
VRRPv3-MIB RFC 6527, Definitions of Managed Objects for the Virtual Router Redundancy Protocol Version 3
(VRRPv3).
All objects with read-write and read-create access are implemented as read-only. RFC 6527
(VRRPv3-MIB) obsoletes RFC 2787 (VRRP-MIB).
HOST-RESOURCES-MIB RFC 2790, Host Resources MIB.
SNMPv2-PDU RFC 3416, Version 2 of the Protocol Operations for the Simple Network Management Protocol
(SNMP).
SNMPv2-TM RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP).
SNMPv2-MIB RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol
(SNMP).
POE-MIB RFC 3621, Power Ethernet MIB.
In each of the following objects, if one entry is set then all other entries for the same object in the
table are set to the same value:
■ pethMainPseUsageThreshold
■ pethNotificationControlEnable.
EtherLike-MIB RFC 3635, Definitions of Managed Objects for the Ethernet-like Interface Types.
MAU-MIB RFC 3636, Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs).
RSTP-MIB RFC 4318, Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol.
The following read-write objects are implemented as read-only:
■ dot1dStpPortProtocolMigration
■ dot1dStpPortAdminEdgePort
■ dot1dStpPortAdminPointToPoint
■ dot1dStpPortAdminPathCost.
LLDP-EXT-DOT1-MIB IEEE Standard 802.1AB-2005, Annex F, IEEE 802.1 Organizationally Specific TLVs. Section F.7.1,
IEEE 802.1LLDP extension MIB module.
In each of the following tables, if one entry is set, all other entries in the table are set to the same
value:
■ lldpXdot1ConfigVlanNameTxEnable
■ lldpXdot1ConfigProtoVlanTxEnable
■ lldpXdot1ConfigProtocolTxEnable.
LLDP-EXT-DOT3-MIB IEEE Standard 802.1AB-2005, Annex G, IEEE 802.3 Organizationally Specific TLVs, Section G.7.1,
IEEE 802.3 LLDP extension MIB module.
LLDP-EXT-MED-MIB ANSI/TIA-1057- 2006, Section 13.3, LLDP-MED MIB Definition.
C613-30001-00 REV F
NETWORK SMARTER
North America Headquarters | 19800 North Creek Parkway | Suite 100 | Bothell | WA 98011 | USA | T: +1 800 424 4284 | F: +1 425 481 3895
Asia-Pacific Headquarters | 11 Tai Seng Link | Singapore | 534182 | T: +65 6383 3832 | F: +65 6383 3830
EMEA & CSA Operations | Incheonweg 7 | 1437 EK Rozenburg | The Netherlands | T: +31 20 7950020 | F: +31 20 7950021
alliedtelesis.com
© 2019 Allied Telesis, Inc. All rights reserved. Information in this document is subject to change without notice. All company names, logos, and product designs that are trademarks or registered trademarks are the property of their respective owners.