Browse Prior Art Database

Base Definitions of Managed Objects for TN3270E Using SMIv2 (RFC2561)

IP.com Disclosure Number: IPCOM000003148D
Original Publication Date: 1999-Apr-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 56 page(s) / 65K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. White: AUTHOR [+1]

Related Documents

10.17487/RFC2561: DOI

Abstract

This memo defines a Management Information Base (MIB) for configuring and managing TN3270E servers. The MIB defined by this memo provides generic support for both host and gateway TN3270E server implementations. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group K. White Request for Comments: 2561 IBM Corp. Category: Standards Track R. Moore IBM Corp. April 1999

Base Definitions of Managed Objects for TN3270E Using SMIv2

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This memo defines a Management Information Base (MIB) for configuring and managing TN3270E servers. TN3270E, defined by RFC 2355 [19], refers to the enhancements made to the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC 1041 [18], STD 8, RFC 854 [16], and STD 31, RFC 860 [17] for a sample of what is meant by TN3270 practices.

The MIB defined by this memo provides generic support for both host and gateway TN3270E server implementations. A TN3270E server connects a Telnet client performing 3270 emulation to a target SNA host over both a client-side network (client to TN3270E server) and an SNA Network (TN3270E server to target SNA host). The client-side network is typically TCP/IP, but it need not be.

A host TN3270E server refers to an implementation where the TN3270E server is collocated with the Systems Network Architecture (SNA) System Services Control Point (SSCP) for the dependent Secondary Logical Units (SLUs) that the server makes available to its clients for connecting into a SNA network. A gateway TN3270E server resides on an SNA node other than an SSCP, either an SNA type 2.0 node, a boundary-function-attached type 2.1 node, or an APPN node acting in the role of a Dependent LU Requester (DLUR). Host and gateway TN3270E server implementations typically differ greatly as to their internal implementation and system definition (SYSDEF) methods.

White & Moore Standards Track [Page 1]

RFC 2561 TN3270E Using SMIv2 MIB April 1999

It is the intent that the MIB defined herein be extended by subsequent memos. For example, one such extension enables collection of TN3270E response time data.

Table of Contents

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 The SNMP Network Management Framework . . . . . . . . . . 3 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . 4 3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . 5 3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . 5 3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . 6 3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . 7 3.2 TN3270E Server Resource Configuration . . . . . . . . . . 7 3.3 Resource Name / Client Address Mappings . . . . . . . . . 8 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . 8 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . 9 3.3.3 tn3270eTc...

Processing...
Loading...