Nothing Special   »   [go: up one dir, main page]

WO2001075634A1 - Systeme utilisant un protocole de gestion de reseau pour un acces double a un reseau local/eloigne - Google Patents

Systeme utilisant un protocole de gestion de reseau pour un acces double a un reseau local/eloigne Download PDF

Info

Publication number
WO2001075634A1
WO2001075634A1 PCT/US2001/009780 US0109780W WO0175634A1 WO 2001075634 A1 WO2001075634 A1 WO 2001075634A1 US 0109780 W US0109780 W US 0109780W WO 0175634 A1 WO0175634 A1 WO 0175634A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
dual
local
remote
access
Prior art date
Application number
PCT/US2001/009780
Other languages
English (en)
Inventor
Mark Kent Sloan
Rayman W. Pon
Original Assignee
Tellus Technology, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tellus Technology, Inc. filed Critical Tellus Technology, Inc.
Priority to AU2001247823A priority Critical patent/AU2001247823A1/en
Publication of WO2001075634A1 publication Critical patent/WO2001075634A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor

Definitions

  • the current invention is in the field of network management protocols, and more specifically, in the field of the simple network management protocols (SNMP) ,
  • the SNMP protocol is widely used for getting and setting values from an Internet- based programmable device.
  • the advantage of the prior art SNMP protocol usage was the opportunity for a user to buy a number of configuration tools, including an open view interface (OVI) , from a vendor and to write a proprietary management information base (MIB) module (MIB file) that can be plugged in into interface .
  • the OVI interface reads the MIB files in order to obtain the proprietary information about the Internet-based programmable device and in order to use the proprietary information to manage the Internet-based programmable device.
  • OVI interface Hewlett-Packard (HP) sells the open view interface (OVI) for SNMP protocol.
  • Another advantage of using SNMP protocol is the ability to interrogate the Internet-based programmable device by using the SNMP protocol without prior knowledge of the particular programmable device. This is possible because the SNMP protocol uses the get/next model of interrogation in its MIB files. In the get/next model of interrogation the SNMP protocol uses different MIB files written for different applications but all having the same topological structure as a tree of different variables, but with the same trunk.
  • the prior art method of using the SNMP protocol does not allow a user to interrogate the Internet-based programmable device locally, without
  • the service technician has two options: (a) to service the Internet-based programmable device remotely by dialing the Internet access number and using the SNMP protocol, or (b) to service the
  • the problem with this approach is that for each new pro- grammable device, or for each new usage of the same programmable device, the service technician has to change the service program in order to access and to service the programmable device locally.
  • the present invention provides a network dual access (local/remote) system that allows the service technician to access and to service any new Internet -based programmable device both locally and remotely.
  • one aspect of the present invention is directed to a network dual access system comprising: (1) a network_dual_access programmable device configured to be accessed using a dual local_remote mode; and (2) a local_remote_interface device coupled to the network_dual_access programmable device; wherein the network_dual_access programmable device utilizes the local__remote_interface device for information transfer in the dual local_remote access mode.
  • the network_dual_access programmable device comprises a local__remote Simple Network Management Protocol (SNMP) Agent (L_R_SNMP_Agent) configured to interact with the local_remote_interface device in the dual local_remote access mode utilizing a Simple Network Management Protocol (SNMP) .
  • the network_dual_access programmable device comprises a local_remote Common Management Information Protocol (CMIP) Agent (L_R_CMIP_Agent) configured to interact with the local_remote_interface programmable device in the dual local_remote access mode utilizing a Common Management Information Protocol (CMIP) .
  • CMIP Common Management Information Protocol
  • the network_dual_access programmable device further includes: (a) a data conversion management module configured to convert a set of data transferred from and/or to the MIB file using the SNMP protocol; and (b) a data storage system configured to store a set of network_dual_access programmable device-based parameters that are related to a set of local__remote_interface device-based parameters stored in a management information base (MIB) file.
  • MIB management information base
  • FIG. 1A depicts a prior art local system architecture designed to service a programmable device.
  • FIG. IB shows a system of the present invention that allows to service a programmable device in both local and remote modes.
  • FIG. 1C depicts a prior art SNMP model of a managed network.
  • FIG. 2A shows a prior art diagram illustrating the retrieval and modification operations utilizing a request message and a response message.
  • FIG. 2B is a prior art diagram depicting the first event report operation using a single message trap.
  • FIG. 2C depicts a prior art diagram illustrat- ing the second event report operation using the inform message and the response message.
  • FIG. 3 illustrates the prior art rules for writing MIB modules that come from two sources: (1) ASN.l modules defining macros and base type specifications; and (2) textual description that modify the ASN.l modules.
  • FIG. 4 is a flow chart of a method of the present invention for the entire SNMP client-server dual mode access model.
  • FIG. 5 illustrates a flow chart of a method of the present invention that is performed by the SNMP Client side of the SNMP client-server dual mode access model .
  • FIG. 1A depicts a prior art local system architecture 10 designed to service a programmable device 16.
  • the technician is located in physical proximity to the programmable device 16 and has a local access to the programmable device 16.
  • the technician uploads the programmable device parameters 18 to his PC/laptop 12, writes or uses the already written proprietary service program 11, and downloads the program 11 to the command interpreter 14 that interprets the program commands to the programmable device 16.
  • the problem with this approach is that if additional parameters are to be installed on the programmable device 16, the technician has to change the service program 11.
  • FIG. IB shows the system 20 that allows to service the programmable device 30 in both local and remote modes. This is done by extending the usage of the Simple Network Management Protocol (SNMP) that was primary used in the prior art for remote (including Internet-based) applications, to the local usage in order to access and to service any programmable device in both remote and local mode.
  • SNMP Simple Network Management Protocol
  • the dual SNMP local/remote access system (and method) presented in the current patent application allows a user to stop using a local service program that has to be adjusted every time when a new feature or parameter are added to the programmable device 30.
  • the user equipped with a dual SNMP local/remote access system 20 of the present invention can access the progr ⁇ mmable__de ⁇ i.ce 30 via the Internet 28, or locally via the serial connector 32, but without having to re-write the service program.
  • the job of finding out the new system parameters 38 is done by using the SNMP interrogation tools. (See detailed discussion below) .
  • the programmable device can be serviced both locally and/or remotely (via Internet) by using the same universal SNMP protocol and SNMP Agent 36.
  • a custom application program interface such as API, has to be defined, tested, and maintained. An implementation of such an API would require additional resources, like RAM and ROM (read only memory) .
  • FIG. 1C depicts a prior art model 50 of an API
  • Each of managed nodes 54, 58, 60 includes a processing entity called an Agent 70.
  • Each management station 52 includes at least one processing entity called management application 72 (or manager) .
  • a management station includes a dual- role entity 56 that is able to perform in both manager and Agent roles.
  • Management information 74 in each managed nodes 54, 58, 60 describes the configuration, state, and statistics that control the actions of a managed node.
  • a management protocol is utilized by the managers and Agents to exchange messages during management communication sessions 62, 64, or 66. This prior art model of SNMP-based management is applied to the system 20 of the present patent application in order to service the programmable device 30 in both remote mode via Internet, and in a local mode bypassing Internet altogether.
  • the SNMP-based management model is defined by a collection of documents. These documents define a man- agement framework including four major components: (1) a management protocol; (2) a definition of management information and events; (3) a core set of management information and events; and (4) a mechanism and approach to manage the use of the protocol including security and access control.
  • the management protocol defines the format and meaning of the management communications between the SNMP processing entities.
  • the operations in SNMP are limited to retrieving the value of management information, modifying the value of management information, and reporting an eve t.
  • Each class (or type) of management information is assigned a unique identity.
  • An instance from a class of management information is called a variable.
  • Each variable is given a unique identity based on the identity of its class and its identification within its class.
  • Each class (or type) of event is assigned a unique identity.
  • the operand to a set is a list of pairs. Each pair includes the identity of a variable and its desired value.
  • Set operations are used to configure and control a managed system.
  • the first type of retrieval operation requires that the identities are those that match exactly the identity of returned variables . This retrieval operation is used when the identity for each variable is known. There is a single operation of this type, called get .
  • the second type of retrieval operation uses each identity in a request as an approximation of the identity for a variable.
  • Each returned identity is the one assigned to the first accessible variable whose identity is greater than the given identity.
  • the get, getnext and getbulk operations are used to moni- tor a managed system.
  • SNMP operations occur through message exchange over a message transport service.
  • the format of messages is defined using a subset of the Ab- stract Syntax Notation One (ASN.l) language. This format, called an abstract syntax, is independent of the representation of data on any particular system. To transmit a message, it should be first converted into a string of octets (bytes) . A transfer syntax specifies the format of converted data.
  • SNMP uses a subset of the
  • BER Basic Encoding Rules
  • the retrieval and modification operations set, get, getnext, and getbulk require two messages: a request message and a response message, as depicted in diagram 80 of FIG. 2A.
  • the first event report operation trap uses a single message operation, which is also called trap, as shown in diagram 82 of FIG. 2B.
  • the second event report operation inform uses two messages: the inform message and the response message, as illustrated in diagram 84 of FIG. 2C.
  • An SNMP message includes administrative information and an SNMP Protocol Data UNIT (PDU) .
  • the PDU identifies the type of the message.
  • SNMP messages are exchanged between processes called SNMP entities.
  • An SNMP entity may be designed to process only one message at a time (i. e., be implemented as single-threaded), or may be designed to process multiple messages concurrently (i. e., be implemented as multi-threaded) .
  • An SNMP entity can play one of many roles during message exchange. The role is determined by the message type and message originator.
  • An SNMP entity is called SNMP manager (72 of FIG. 1) if it assumes the operational role to generate requests to retrieve and modify management information, receive the responses to requests, or to receive event reports.
  • An SNMP entity is called SNMP Agent (70 of FIG. 1) if it assumes the operational role to receive, pro- cess, and respond to requests, and to generate event reports.
  • An SNMP Agent should have access to network management information to respond to requests, and should be notified of internal events to generate reports.
  • An SNMP entity can also play a dual role of being both an SNMP Agent and an SNMP manager (68 of FIG. 1) . However, in describing SNMP message exchange, an entity should perform either as a manager, or as an Agent for a particular message.
  • Dual-role entities are typically used to forward SNMP messages (an SNMP proxy) , or to consolidate and synthesize information from many systems and make that information available to a higher-level manager (a mid-level manager) .
  • a Client generally is an SNMP manager
  • a server is an SNMP Agent.
  • SNMP message exchange one needs only a simple connectionless (i. e., datagram) transport service.
  • Examples includes the User Datagram Protocol (UDP) from the Internet protocol suite, the Connectionless-mode Transport Service (CLTS) from the OSI protocol suite, the Datagram Delivery Protocol (DDP) from the AppleTalk protocol suite, the Packet Exchange protocol (PEP) from the Novell IPX protocol suite, or any form of interprocess communication message within a single system.
  • the SNMP protocol is stateless, that is the SNMP protocol does not keep information about or for the entities after an operation has been performed. Any such information is kept by the entities themselves .
  • the second component of the framework is a definition of management information and events that is specified in a plurality of documents called the Structure of Management Information (SMI) .
  • the SMI includes the model of management information, the allowed data types, and the rules for specifying classes (or types) of management information.
  • An SNMP system is managed by retrieval and modification of management information.
  • Each class (or type) of management information is called an object or object type .
  • a specific instance from a class of management information is called an SNMP variable or an object instance.
  • the definition of an object type includes its data type, the maximum allowed access, its assigned iden- tity, how instances are identified, and its semantics (or behavior) .
  • SNMP uses an identification scheme found in ASN.l to uniquely identify items for all space and time. An identifier in this scheme is called an object identifier (or OID) .
  • OID object identifier
  • the permanent assignment of an OID value, an identity, to an item is called registration .
  • SNMP uses OIDs to iden- tify many types of items. Besides the data types and rules for specifying management information, the SMI also includes some administrative assignments. These assignments are used to organize the definitions of management information into those targeted for the Internet Engi- neering Task Force (IETF) standards track, experimental ones within the IETF, and proprietary ones developed by vendors of SNMP-based management systems. The SMI also includes rules for specifying implementation compliance requirements, and actual implemented characteristics of SNMP Agents.
  • IETF Internet Engi- neering Task Force
  • MIB Management Infor- mation Base
  • FIG. 3 illustrates the rules 90 for writing MIB modules that come from two sources: (1) ASN.l modules 94 defining macros, and defining base type specifications; and (2) textual description 96.
  • the textual description 96 indicate (a) the allowed constructs from ASN.l language that can be used in MIB modules, (b) the restrictions on those ASN. 1 constructs; and (c) the additions and adaptions to ASN.l constructs for use in SNMP MIB modules.
  • the rules 90 create a new SNMP MIB language 100 that is used to specify SNMP MIB modules.
  • the SNMP MIB language 100 has common elements 104 with the ASN.l language 102 that define macros, and additional elements that come from textual descriptions.
  • the network dual access system 20 of the present invention includes a network_dual_access programmable device 30 and a local_remote_interface device 25 coupled to the network_dual_access programmable device 30.
  • the network_dual_access programmable device 30 can comprise: a router network programmable device; a bridge network programmable device; a network server; or a credit card validation programmable device.
  • the local_remote_interface device 25 can comprise: a laptop computer; or a personal computer.
  • the network_dual_access programmable device 30 further comprises a local_remote Simple Network Management Protocol (SNMP) Agent (L_R_SNMP_Agent) 36 configured to interact with the local_remote_interface device 25 in the dual local__remote access mode utilizing a Simple Network Management Protocol (SNMP) .
  • SNMP Simple Network Management Protocol
  • SNMP Agent (L_R_SNMP_Agent) 36 includes the described above SNMP Agent 70 of FIG. 1C .
  • the network_dual_access programmable device 30 of FIG. IB includes a local_remote Common Management Information Protocol (CMIP) Agent (L_R_CMIP_Agent) configured to interact with the local_remote_interface device 25 in the dual local_remote access mode utilizing a prior art Common Management Information Protocol (CMIP) .
  • CMIP Common Management Information Protocol
  • the SNMP Agent should include the following functional areas: (1) access to one or more transport stacks; (2) a protocol engine which includes security; and (3) a dispatch table to method routines.
  • An SNMP Agent uses a transport stack to receive and transmit messages.
  • An SNMP Agent typically uses a well-known transport selector to receive messages.
  • UDP port is used as the transport selector with an IP address of the system including an Agent to form the transport address.
  • the socket interface can be used as an interface between an Agent and a transport stack.
  • the protocol stack should also include instrumentation and access interfaces for method routines at all layers for the management information in the protocol stack to be accessible by the Agent.
  • the protocol engine includes a part of an Agent that receives an SNMP message, decodes it, implements the checks of the administration framework, looks up mappings in the dispatch table, calls method routines, and encodes and sends a response message.
  • the protocol engine also receives notifications of events within the system and generates SNMP event reports.
  • the dispatch table includes mappings to method routines based on management information identity and selector.
  • SNMP messages received or generated by an Agent include the identity information (or approximation of the identity of management information in messages for the getnext and getbulk operations) .
  • the identity of an instance of management information includes at least two parts. The first part is the type of management information, and the second part specifies an individual (or instance) of that type.
  • SNMP messages also include a selector which is used to qualify the identities in that message. For example, in SNMPvl, the selector is the community string field in a message, wherein in SNMPv2 , the selector is the context field in a message.
  • Agent For each management information identity in a message, an Agent should use the selector from that message, and both parts of the identity to access the management information. An identity and selector should also be specified in requests through a local interface, if this is supported by the Agent.
  • Agent implementations have tools to automate the generation of a dispatch table, and allows new entries to be created and removed during Agent execution. Adding a new mapping is called registration . Deleting a mapping is called deregi s tra tion.
  • the network dual access system 20 of the present invention further includes a network port 37 configured to access the network_dual_access programmable device 30 in a remote mode utilizing a Simple Network Management Protocol (SNMP) , and a non-network port 23 including a protocol configured to access the network_dual_access programmable device 30 in a local mode using the SNMP protocol.
  • the non-network port 23 can comprise: a serial port, or a parallel port.
  • the serial port can comprise a RS-232 port, or an infrared data access port (IRDA) .
  • the parallel port can comprise a general purposes interface bus (GP B) , or a CENTRONIX port.
  • the network port 37 can comprise an Ethernet line, a phone line, a cable modem, or a wireless port configured to wirelessly access the network_dual_access programmable device 30.
  • the system parameters 38 can be also obtained locally by using the SNMP Agent 36.
  • the SNMP Agent 36 obtains the system parameters 38 in a local mode by using the same interrogation commands get, and getnext .
  • MIB question What is the programmable device type? 2-nd MIB question: What is the version number? 3-d MIB question: What is the length of time? 4-th MIB question: What is the reset time?
  • the local_remote_interface device 25 includes a local connector 32 configured to exchange a set of data between the MIB files 24 and system parameters block 38.
  • the system parameters obtained from the block 38 are sent to the MIB Interpreter 21 via command queue pipeline 40.
  • the command queue pipeline 40 can be implemented by using a common queue 40 to run the connection between the service PC 22 and the SNMP Agent 36 residing on the programmable device 30.
  • the SNMP protocol handles one message at a time, and the common queue pipeline 40 is used to build up the message in both directions.
  • the user can interrogate the programmable device 30 by using SNMP Agent 36. This is possible, because the MIB files topologically are trees of variables, and the topological trunk of all trees is the same for all applications .
  • the dual access network system 20 of FIG. IB utilizes the double access to the programmable device 30 from the local_remote_interface device 25 both locally (via local connector 32, and without trouble of re-writing the program for SNMP) , and remotely (via remote connector and via Internet 28) in order to activate the SNMP Agent 36 that is used to interrogate the programmable device 30 and to find out the updated system parameters 28.
  • the local_remote_interface device 25 represents a client
  • the network_dual_access programmable device 30 represents a server (the so called client-server model)
  • the SNMP Client resides on the client side
  • the SNMP Agent 36 resides on the server side. Therefore, in the SNMP embodiment, the local_remote_interface device 25 further includes a Simple Network Management Protocol (SNMP) Client (not shown)
  • the network_dual_access programmable device 30 includes the SNMP Agent 36.
  • the SNMP Client includes the set/get emulator (not shown) configured to access the network_dual_access programmable device 30 in the dual local/remote access mode utilizing the SNMP protocol.
  • the network_dual_access programmable device 30 further includes a data conversion management module (not shown) configured to convert a set of data transferred from and/or to the MIB file 24 using the SNMP protocol, and a data storage system 39 configured to store a set of system parameters 38 that are related to a set of variables stored in the MIB file 24.
  • the data conversion management module further includes an SNMP interpreter (not shown) configured to interpret a set of data in ASN.l format transferred to and /or from the MIB file 24.
  • the local_remote_interface device 25 includes the MIB interpreter configured to interpret the system parameters 38 and to send the updated data to the MIB files 24.
  • the user changes MIB files 24 in his service PC 22 if he needs to update the system parameters 38 of the double access programmable device 30.
  • the user uses the same SNMP Agent 36 and the same SNMP protocol in both modes, locally and remotely.
  • the technician can service the programmable device 30 locally without writing the new service program for each new feature or application because the new system parameters that correspond to the new features or applications of the device 30 are downloaded to the service PC 22 from the MIB interpreter 21.
  • system parameters 38 include ⁇ device type; version number ⁇ .
  • the MIB files 24 set of variables also include ⁇ device type; version number ⁇ .
  • the system parameters block 38 include some additional parameters ⁇ length_of_time; reset_time ⁇ .
  • the device 30 has to be turned off for the duration of time equal to the parameter ⁇ length_of_time ⁇ , and has to be reset after the time equal to the parameter
  • the MIB files 24 also include the variables ⁇ length_of_time; reset_time ⁇ .
  • the system parameters 38 include the enterprise dependent parame- ters .
  • the enterprise dependent variables are: ⁇ the number of sprinklers N that should be turned off or on; the id of each particular sprinkler II, 2, ...IK that has to be turned off or on ⁇ , wherein N and K are integers.
  • the MIB files also include the set variables ⁇ the number of sprinklers N that should be turned off or on; the id of each particular sprinkler II, 12, ... IK that has to be turned off or on ⁇ .
  • FIG. 4 is a flow chart 110 illustrating the method of the present invention describing a dual local_remote SNMP access of a network_dual_access programmable device (30 of FIG. IB) by using a local_remote_interface device (25 of FIG. IB) .
  • the method of FIG. 4 is performed by the entire dual access network system (20 of FIG. IB) .
  • an Abstract Syntax Notation One (ASN.l) format derived from a management information based (MIB) file including a set of variables is transferred from the network_dual_access programmable device (30 of FIG. IB) to the local_remote_interface device (25 of FIG. IB) .
  • ASN.l Abstract Syntax Notation One
  • MIB management information based
  • an SNMP transaction is emulated on the local_remote_interface device (25 of FIG. IB) by utilizing the MIB file (24 of FIG. IB) and an SNMP Client (not shown) .
  • the local_remote_interface device (25 of FIG. IB) is treated as a client in the SNMP client-server model, and therefore includes an SNMP Client, wherein the network_dual_access programmable device (30 of FIG. IB) is treated as a server in the SNMP client server model, and accordingly, includes an SNMP Agent (36 of FIG. IB) .
  • the emulated SNMP transaction is transmitted (step 116 of FIG.
  • step 118 of FIG. 4 the emulated SNMP transaction is converted into a set of data readable by an SNMP Agent (36 of FIG. IB) .
  • the step of trans- ferring the management information base (MIB) file further includes the following steps: (step 120 of FIG. 4) reading and/or writing a set of variables in the MIB file (24 of FIG. IB) by utilizing a configuration management tool (26 of FIG. IB) ; and (step 122 of FIG. 4) utilizing the set of variables in the MIB file (24 of FIG. IB) in order to change configuration of a graphic user interface (GUI) (not shown) .
  • the step of transmitting the emulated SNMP transaction from the local_remote_interface device to the network_dual_access programmable device further includes the step (not shown) of using a local connector (32 of FIG. IB) in order to make a local connection and to bypass the Internet, and the step (not shown) of using a remote connector (not shown) in order to make a remote connection via the Internet (28 of FIG.l B) .
  • the step of converting the emulated SNMP transaction (step 118 of FIG. 4) further includes ths step of interpreting the emulated SNMP transaction as set of data by utilizing an SNMP interpreter (step 122 of FIG. 4) , and the step of reading (step 124) the set of converted data by a local_remote Simple Network Management Protocol (SNMP) Agent (L_R_SNMP_Agent) installed on the network_dual_access programmable device (30 of FIG. IB) .
  • SNMP local_remote Simple Network Management Protocol
  • the step of reading the set of converted data is performed by a local_remote Common Management Information Protocol (CMIP) (L_R_CMIP_Agent) Agent (not shown) installed on the network_dual_access programmable device (30 of FIG. IB) .
  • CMIP Common Management Information Protocol
  • FIG. 5 illustrates a flow chart 140 of a method of the present invention for a dual local_remote SNMP access of a network_dual_access programmable device.
  • the method 140 of FIG. 5 is performed by the SNMP Client side of the SNMP client-server model. This means that the steps of flowchart 140 are performed by the local_remote_interface device (25 of FIG. IB).
  • an Abstract Syntax Notation One (ASN.l) format derived from a management information based (MIB) file including a set of variables is transferred from the network_dual_access programmable device (30 of FIG. IB) to the local__remote_interface device (25 of FIG. IB) .
  • ASN.l Abstract Syntax Notation One
  • MIB management information based
  • an SNMP transaction is emulated on the local_remote_interface device (25 of FIG. IB) by utilizing the MIB file (24 of FIG. IB) and an SNMP Client (not shown) .
  • the emulated SNMP transaction is transmitted (step 146 of FIG.
  • the step of transferring the management information base (MIB) file (step 142) further includes the following steps: (step 148 of FIG. 5) reading and/or writing a set of variables in the MIB file (24 of FIG. IB) by utilizing a configuration management tool (26 of FIG. IB) ; and (step 150 of FIG. ) utilizing the set of variables in the MIB file (24 of FIG. IB) in order to change configuration of a graphic user interface (GUI) (not shown) .
  • GUI graphic user interface
  • the step of transmitting the emulated SNMP transaction from the local_remote_interface device to the network_dual_access programmable device further includes the step (not shown) of using a local connector (32 of FIG. IB) in order to make a local connection and to by- pass the Internet, and the step (not shown) of using a remote connector (not shown) in order to make a remote connection via the Internet (28 of FIG.l B) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un système et un procédé d'accès double à un réseau (20) permettant d'accéder à un dispositif programmable d'accès double à un réseau (30) dans un mode double local/éloigné au moyen d'un dispositif programmable d'accès double à un réseau (30). Dans le mode de réalisation préféré, ce dispositif programmable d'accès double à un réseau (30) comporte un agent local/éloigné de protocole simple de gestion de réseau (SNMP) (36) conçu pour interagir avec le dispositif d'interface local/éloigné (25) dans le mode d'accès double local/éloigné au moyen d'un protocole simple de gestion de réseau (SNMP). Dans une variante, le dispositif programmable d'accès double à un réseau (30) comporte un agent local/éloigné de protocole commun d'informations de gestion (CMIP) conçu pour interagir avec le dispositif programmable d'interface local/éloigné (25) dans le mode d'accès double local/éloigné au moyen d'un protocole commun d'informations de gestion (CMIP).
PCT/US2001/009780 2000-04-01 2001-03-26 Systeme utilisant un protocole de gestion de reseau pour un acces double a un reseau local/eloigne WO2001075634A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001247823A AU2001247823A1 (en) 2000-04-01 2001-03-26 System utilizing a network management protocol for dual local/remote network access

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US54131300A 2000-04-01 2000-04-01
US09/541,313 2000-04-01

Publications (1)

Publication Number Publication Date
WO2001075634A1 true WO2001075634A1 (fr) 2001-10-11

Family

ID=24159041

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/009780 WO2001075634A1 (fr) 2000-04-01 2001-03-26 Systeme utilisant un protocole de gestion de reseau pour un acces double a un reseau local/eloigne

Country Status (2)

Country Link
AU (1) AU2001247823A1 (fr)
WO (1) WO2001075634A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1376932A2 (fr) * 2002-04-26 2004-01-02 Extreme Networks Procédé et appareil de gestion dynamique de configuration
WO2004045148A1 (fr) * 2002-11-13 2004-05-27 Thomson Licensing S.A. Dispositif routeur ou pont comprenant une application d'installation
WO2007054035A1 (fr) * 2005-11-11 2007-05-18 Huawei Technologies Co., Ltd. Systeme, procede et noeud de gestion de transfert de fichiers snmp
US7689678B2 (en) 2002-04-26 2010-03-30 Extreme Networks Method and apparatus for restoring the configuration of a network device
CN112054916A (zh) * 2019-06-06 2020-12-08 烽火通信科技股份有限公司 事件自动化转换的方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5634009A (en) * 1993-10-01 1997-05-27 3Com Corporation Network data collection method and apparatus
US5757801A (en) * 1994-04-19 1998-05-26 Multi-Tech Systems, Inc. Advanced priority statistical multiplexer

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5634009A (en) * 1993-10-01 1997-05-27 3Com Corporation Network data collection method and apparatus
US5757801A (en) * 1994-04-19 1998-05-26 Multi-Tech Systems, Inc. Advanced priority statistical multiplexer

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1376932A2 (fr) * 2002-04-26 2004-01-02 Extreme Networks Procédé et appareil de gestion dynamique de configuration
EP1376932A3 (fr) * 2002-04-26 2004-01-07 Extreme Networks Procédé et appareil de gestion dynamique de configuration
US7689678B2 (en) 2002-04-26 2010-03-30 Extreme Networks Method and apparatus for restoring the configuration of a network device
US7783733B1 (en) 2002-04-26 2010-08-24 Extreme Networks, Inc. Method and apparatus for dynamic configuration management
WO2004045148A1 (fr) * 2002-11-13 2004-05-27 Thomson Licensing S.A. Dispositif routeur ou pont comprenant une application d'installation
WO2007054035A1 (fr) * 2005-11-11 2007-05-18 Huawei Technologies Co., Ltd. Systeme, procede et noeud de gestion de transfert de fichiers snmp
CN112054916A (zh) * 2019-06-06 2020-12-08 烽火通信科技股份有限公司 事件自动化转换的方法及系统

Also Published As

Publication number Publication date
AU2001247823A1 (en) 2001-10-15

Similar Documents

Publication Publication Date Title
KR100791429B1 (ko) Ｎａｓ ｓｎｍｐ 단일 시스템 이미지
US7370105B2 (en) Quality of service control, particularly for telecommunication
US7039724B1 (en) Programmable command-line interface API for managing operation of a network device
US20060155825A1 (en) Network device managing apparatus and method and storage medium
Yoon et al. Development of SNMP‐XML translator and gateway for XML‐based integrated network management
EP0762281A2 (fr) Gestion de réseau avec acquisition de données de vidage formatés d'un processus éloigné
Valenčić et al. Implementation of netconf protocol
Leppinen et al. Java-and CORBA-based network management
US7433941B1 (en) Method and apparatus for accessing network information on a network device
US7580936B2 (en) Extendable discovery of network device information
WO2001075634A1 (fr) Systeme utilisant un protocole de gestion de reseau pour un acces double a un reseau local/eloigne
CN100364275C (zh) 一种通信网络管理方法
KR100395223B1 (ko) 티엠엔과 씨오알비에이 연동 시스템
US7260621B1 (en) Object-oriented network management interface
EP1548588A2 (fr) Procédé pour transformer code programme d'ordinateur, système de communication et système pour la gestion de réseau
Bartl et al. Data exchange between real network component and OPNET modeler simulation environment
Guerrero Network management & monitoring with Linux
Lopes et al. Distributed Management: Implementation issues
Zhu et al. Towards integrated network management scripting frameworks
Bartl et al. Integration of real network components into OPNET modeler co-simulation process
CN101330441A (zh) 一种工业交换机snmp协议到opc协议之间转换的实现方法
KR101042358B1 (ko) 계층 네트워크의 망 관리 시스템
Carey et al. Heterogeneous Tools for Heterogeneous Network Management with WBEM
KR100547224B1 (ko) 컴포넌트 기반의 통합 망 관리 방법 및 그 장치
Shi DETAILED DESIGN OF INTELLIGENT OBJECT FRAMEWORK

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: RULE 69(1) EPC

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP