AppleTalk Management Information Base
obsoleted by
- rfc-1742 — AppleTalk Management Information Base II
Extracted elements (23)
The DdpAddress textual convention is introduced solely to enhance readability and ease comparison with other specifications. Its introduction has no effect on the syntax or semantics of any managed objects; objects are always encoded by the rules that define the underlying primitive type.
The nine MIB groups (LLAP, AARP, ATPort, DDP, RTMP, KIP, ZIP, NBP, ATEcho) serve as the basic unit of conformance and provide a method for managed agents to determine which objects they must implement, reflecting an all-or-nothing group membership model.
For Phase 1 networks or non-extended networks, the 'End' field of any network range (atportNetEnd, rtmpRangeEnd, kipNetEnd, zipZoneNetEnd) shall be set to two octets of zero, distinguishing them from extended (Phase 2) networks.
If the semantics of a group is applicable to an implementation, then it must implement all objects in that group. For example, a managed agent must implement the KIP group if and only if it implements the KIP protocol.
Management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant status object (atportStatus, rtmpState, kipState, zipZoneState, or nbpState).
atportNetConfig and atportZoneConfig each report how the port's network or zone configuration was obtained: configured(1) by explicit administration, garnered(2) from inspection of the network, guessed(3) as a random configuration, or unconfigured(4).
ddpHopCountErrors counts datagrams dropped because forwarding them would cause the hop count to exceed 15, reflecting AppleTalk's maximum hop-count limit enforced at the DDP layer.
kipShare indicates whether a KIP routing entry is propagated to other routers as part of a routing protocol (shared(1)) or kept private to the device (private(2)), enabling policy control over route redistribution.
The aarpTable (AARP Group) maps AppleTalk DDP network addresses to data-link physical addresses. Each entry is indexed by aarpIfIndex and aarpNetAddress (DdpAddress), and contains aarpPhysAddress as a media-dependent OCTET STRING.
The ATEcho Group provides two scalar counters: atechoRequests (AppleTalk echo requests received) and atechoReplies (echo replies sent), supporting verification of AppleTalk internet reachability.
The atportTable (ATPort Group) describes each logical AppleTalk port, with fields for atportType (localtalk, ethertalk1/2, tokentalk, iptalk, serial-ppp, serial-nonstandard, virtual), atportNetStart/End (2-octet network range), atportNetAddress (DdpAddress), atportStatus, atportNetConfig, atportZoneConfig, atportZone, and atportIfIndex.
The DDP Group exposes scalar counters for the Datagram Delivery Protocol layer: ddpOutRequests, ddpOutShorts, ddpOutLongs, ddpInReceives, ddpForwRequests, ddpInLocalDatagrams, ddpNoProtocolHandlers, ddpOutNoRoutes, ddpTooShortErrors, ddpTooLongErrors, ddpBroadcastErrors, ddpShortDDPErrors, ddpHopCountErrors, and ddpChecksumErrors.
The kipTable (KIP Group) manages routing of AppleTalk datagrams over an IP internet. Each entry contains kipNetStart/End (AppleTalk range), kipNextHop (IpAddress), kipHopCount, kipBCastAddr (IP broadcast form), kipCore (core/notcore), kipType (kipRouter, net, host, other), kipState, and kipShare.
The llapTable (LLAP Group) provides per-interface counters for LocalTalk link-layer statistics, including llapInPkts, llapOutPkts, llapCollisions, llapDefers, llapNoDataErrors, llapRandomCTSErrors, llapFCSErrors, llapInNoHandlers, and llapInLengthErrors, all indexed by llapIfIndex.
The nbpTable (NBP Group) enumerates Name Binding Protocol services registered on the managed entity. Each entry contains nbpIndex, nbpObject (service name), nbpType (service type), nbpZone, and nbpState (valid/invalid).
The rtmpTable (RTMP Group) represents AppleTalk routing entries, each containing rtmpRangeStart/End (2-octet network range), rtmpNextHop, rtmpType (appletalk, serial-ppp, serial-nonstandard), rtmpPort, rtmpHops, and rtmpState.
The zipTable (ZIP Group) maps zone names to AppleTalk network ranges. Each entry contains zipZoneName, zipZoneIndex (unique integer per zone name shared across entries with the same name), zipZoneNetStart/End, and zipZoneState (valid/invalid).
zipZoneIndex provides a stable integer identifier for a zone name: all zipTable entries with the same zipZoneName share the same zipZoneIndex, enabling efficient lookup of all networks in a given zone.
Security issues are not discussed in this memo.
atportStatus defines four states: operational(1), unconfigured(2), off(3), and invalid(4). Setting atportStatus to invalid(4) disassociates the port entry; agents may or may not remove the row, so management stations must be prepared to receive stale entries.
kipState has three values: configured(1) for administratively set entries, learned(2) for dynamically acquired entries, and invalid(3) to disassociate an entry. Agents may or may not remove invalidated rows from the table.
rtmpState tracks the freshness of a routing table entry through states: good(1), suspect(2), goingBad(3), and bad(4). Setting rtmpState to bad(4) invalidates the entry; agents may retain or remove invalidated rows.
DdpAddress is encoded as an OCTET STRING of SIZE(3): two octets of DDP network number in network byte order, followed by one octet of node number. This textual convention has no effect on SMI or SNMP encoding rules.