📄 rfc1665.mib
字号:
SNA-NAU-MIB DEFINITIONS ::= BEGIN-- This MIB module contains objects necessary-- for management of the following SNA devices: PU types 1.0, 2.0, 2.1-- and LU types 0, 1, 2, 3, 4, 7. It also contains generic objects-- which can be used to manage LU 6.2.-- Naming conventions in this document:-- The following names are used in object descriptors according to-- SNA conventions.-- The name 'PU' or 'Node' is used to describe Node type 1.0, 2.0 or-- 2.1.-- The name 'LU' is used to describe Logical Unit of type 0,1,2,3,-- 4,7 or 6.2.IMPORTS DisplayString, RowStatus, TimeStamp, InstancePointer FROM SNMPv2-TC Counter32, Gauge32, Integer32, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF mib-2 FROM RFC1213-MIB;snanauMIB MODULE-IDENTITY LAST-UPDATED "9402041800Z" ORGANIZATION "IETF SNA NAU MIB Working Group" CONTACT-INFO " Zbigniew Kielczewski Eicon Technology Inc. 2196 32nd Avenue Lachine, Que H8T 3H7 Canada Tel: 1 514 631 2592 E-mail: zbig@eicon.qc.ca Deirdre Kostick Bell Communications Research Red Bank, NJ 07701 Tel: 1 908 758 2642 E-mail: dck2@mail.bellcore.com Kitty Shih (editor) Novell 890 Ross Drive Sunnyvale, CA 94089 Tel: 1 408 747 4305 E-mail: kmshih@novell.com" DESCRIPTION "This is the MIB module for objects used to manage SNA devices."::= { mib-2 34 }-- The SNANAU MIB module contains an objects part and a conformance part.-- Objects are organized into the following groups:-- (1)snaNode group,-- (2)snaLU group,-- (3)snaMgtTools group.snanauObjects OBJECT IDENTIFIER ::= { snanauMIB 1 } snaNode OBJECT IDENTIFIER ::= { snanauObjects 1 } snaLu OBJECT IDENTIFIER ::= { snanauObjects 2 } snaMgtTools OBJECT IDENTIFIER ::= { snanauObjects 3}-- ***************************************************************-- snaNode group---- It contains Managed Objects related to any type of Node and-- some specific objects for Node Type 2.0.-- ***************************************************************-- ***************************************************************-- The following table contains generic Node configuration-- parameters.-- ***************************************************************snaNodeAdminTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaNodeAdminEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains objects which describe the configuration parameters for an SNA Node. Link specific configuration objects are contained in a separate MIB module (e.g., SNA DLC MIB) corresponding to the link type. The table snaNodeAdminLinkTable contains objects which identify the relationship between node instances and link instances. The entries (i.e., rows) in this table can be created by either an Agent or a Management Station. The Management Station can do this through setting the appropriate value in the snaNodeAdminRowStatus. The snaNodeAdminRowStatus object describes the status of an entry and is used to change the status of an entry. The entry is deleted by an Agent based on the value of the snaNodeAdminRowStatus. The snaNodeAdminState object describes the desired operational state of a Node and is used to change the operational state of a Node. For example, such information may be obtained from a configuration file. How an Agent or a Management Station obtains the initial value of each object at creation time is an implementation specific issue. For each entry in this table, there is a corresponding entry in the snaNodeOperTable. While the objects in this table describe the desired or configured operational values of the SNA Node, the actual runtime values are contained in snaNodeOperTable." ::= { snaNode 1 }snaNodeAdminEntry OBJECT-TYPE SYNTAX SnaNodeAdminEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry contains the configuration parameters for one SNA Node instance. The objects in the entry have read-create access. An entry can be created, modified or deleted. The object snaNodeAdminRowStatus is used (i.e., set) to create or delete a row entry." INDEX { snaNodeAdminIndex } ::= { snaNodeAdminTable 1 }SnaNodeAdminEntry ::= SEQUENCE { snaNodeAdminIndex Integer32, snaNodeAdminName DisplayString, snaNodeAdminType INTEGER, snaNodeAdminXidFormat INTEGER, snaNodeAdminBlockNum DisplayString, snaNodeAdminIdNum DisplayString, snaNodeAdminEnablingMethod INTEGER, snaNodeAdminLuTermDefault INTEGER, snaNodeAdminMaxLu Integer32, snaNodeAdminHostDescription DisplayString, snaNodeAdminStopMethod INTEGER, snaNodeAdminState INTEGER, snaNodeAdminRowStatus RowStatus }snaNodeAdminIndex OBJECT-TYPE SYNTAX Integer32 -- MAX-ACCESS not-accessible MAX-ACCESS read-only STATUS current DESCRIPTION "Index used to uniquely identify each Node instance. If an Agent creates the entry, then it will assign this number otherwise a Management Station generates a random number when it reserves the entry for creation." ::= { snaNodeAdminEntry 1 }snaNodeAdminName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..17)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the desired name of the Node for use during Node activation. In Type 2.1 networks, this is a fully-qualified name, meaning that the Node name is preceded by the NetId (if present) with a period as the delimiter. A write operation to this object will not change the operational value reflected in snaNodeOperName until the Node has been re-activated (e.g., after the next initialization of the SNA services)." ::= { snaNodeAdminEntry 2 }snaNodeAdminType OBJECT-TYPE SYNTAX INTEGER { other(1), pu10(2), pu20(3), t21len(4), endNode(5), networkNode(6) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the type of SNA Node. A write operation to this object will not change the operational value reflected in snaNodeOperType until the Node has been re-activated (e.g., after the next initialization of the SNA services)." ::= { snaNodeAdminEntry 3 }snaNodeAdminXidFormat OBJECT-TYPE SYNTAX INTEGER { format0(1), format1(2), format3(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the type of XID format used for this Node. Note that there is no format type 2. A write operation to this object will not change the operational value reflected in snaNodeOperAdminXidFormat until the Node has been re-activated (e.g., after the next initialization of the SNA services)." ::= { snaNodeAdminEntry 4 }snaNodeAdminBlockNum OBJECT-TYPE SYNTAX DisplayString (SIZE(3)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the block number for this Node instance. It is the first 3 hexadecimal digits of the SNA Node id. A write operation to this object will not change the operational value reflected in snaNodeOperBlockNum until the Node has been re-activated (e.g., after the next initialization of the SNA services)." ::= { snaNodeAdminEntry 5 }snaNodeAdminIdNum OBJECT-TYPE SYNTAX DisplayString (SIZE(5)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the ID number for this Node instance. This is the last 5 hexadecimal digits of the SNA Node id. A write operation to this object will not change the operational value reflected in snaNodeOperIdNum until the Node has been re-activated (e.g., after the next initialization of the SNA services)." ::= { snaNodeAdminEntry 6 }snaNodeAdminEnablingMethod OBJECT-TYPE SYNTAX INTEGER { other (1), startup (2), demand (3), onlyMS (4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates how the Node should be activated for the first time. The values have the following meanings: other (1) - may be used for proprietary methods not listed in this enumeration, startup (2) - at SNA services' initialization time (this is the default), demand (3) - only when LU is requested by application, or onlyMS (4) - by a Management Station only. A write operation to this object may immediately change the operational value reflected in snaNodeOperEnablingMethod depending on the Agent implementation. If the Agent implementation accepts immediate changes, then the behavior of the Node changes immediately and not only after the next system startup of the SNA services. An immediate change may only apply when the current value `demand (3)' is changed to `onlyMS (4)' and vice versa." ::= { snaNodeAdminEntry 7 }snaNodeAdminLuTermDefault OBJECT-TYPE SYNTAX INTEGER { unbind (1), termself (2), rshutd (3), poweroff(4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value indicates the desired default method used to deactivate LUs for this Node For LU6.2s, `unbind(1)' is the only valid value. unbind(1) - terminate the LU-LU session by sending an SNA UNBIND request. termself(2) - terminate the LU-LU session by sending an SNA TERM-SELF (Terminate Self) request on the SSCP-LU session. The SSCP will inform the remote session LU partner to send an UNBIND request to terminate the session. rshutd(3) - terminate the LU-LU session by sending an SNA RSHUTD (Request ShutDown) request to the remote session LU partner. The remote LU
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -