JP2007334409A - Network connection apparatus, method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network connection apparatus, method, and program, which enable an operator to set automatic connection for a subsequent NE (network element) even if he has only knowledge to manually use and connect a CLI for connection. <P>SOLUTION: The network connection apparatus 1 has a connection information storage means for previously storing connection information for connecting with a terminal in association with system information on the terminal, a connection destination input means for receiving connection destination information for designating a terminal of a connection destination, a product detection means for detecting system information related to a terminal for the connection destination information on the basis of the connection destination information received with the connection destination input means, and a login means for connecting to a terminal for the connection destination information on the basis of selected connection information after selecting, from a connection information storage section, the connection information related to the system information detected with the product detection means. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technology of a network management apparatus and a network management program, and in particular, a user on a CLI (Command Line Interface) that requires a user name and password such as Telnet, FTP (File Transfer Protocol), and SSH (Secure Shell). The present invention relates to a technology of a connection device using a communication protocol for performing interactive communication between a device and a device.

  In order to perform operations such as starting, restarting, stopping, changing or deleting various parameters, collecting information, etc., for network elements (hereinafter referred to as NEs) such as routers and switches constituting communication networks represented by the Internet. The operator uses a communication protocol such as Telnet, FTP, or SSH to connect to the NE from the terminal, executes a command on the CLI (Command Line Interface), and detects a response from the NE. At this time, as an initial connection procedure of communication protocols such as Telnet, FTP, and SSH, the user transmits a user name and password to the NE in order to have the connection permitted.

  Also, in order to perform a process that requires special authority, a process of logging in again as a user having a different authority such as an administrator is performed after connection. At this time, a command for changing the authority (for example, su, enable, etc.), a user name and a password are transmitted to the NE.

A command to change the user name, password, and authority in advance as a method to automatically advance the connection procedure for exchanging the command, user name, and password in order to reduce the trouble of entering the command, user name, and password each time a connection is made. Is registered in the network management apparatus, and when a predetermined response is detected, a predetermined user name and password are transmitted, so that it is possible to connect to the NE CLI without user intervention.
For example, there is a method of exchanging management information by preparing a definition based on an object-oriented format description in accordance with a management protocol standardized by OSI or the like (see Patent Document 1).
In addition, when connecting, there is a method of performing automatic connection by preparing a special method such as incorporating an agent in the NE group to be monitored and the network management apparatus in advance and determining a password for both.
Japanese Patent Laid-Open No. 3-198139

  However, in order to automate connection processing using a communication protocol such as Telnet, a user name and password are registered in the network management system, and the user name, password, and specific command are specified for specific information transmitted by the NE. There has been a problem that the user has to implement an application function for sending a message by programming.

For example, after establishing a Telnet connection session, after detecting that a character string such as “login:” has been sent from the NE, a character string such as “Password:” is transmitted. There is a problem that it is necessary to implement a procedure of transmitting a password character string after detecting that the password has been received.
For this reason, automatic connection is not possible unless the information content transmitted by the NE is known to the application function for automatic connection. In this case, implementation work such as programming for creating application functions according to a new pattern is required. Of course, there is a problem that knowledge of programming is necessary for the implementation work.

  Even if programming knowledge is not required, a formal description definition based on object orientation is required as in Patent Document 1, and knowledge other than knowledge necessary for manual connection by CLI such as Telnet ( For example, Patent Document 1 has a problem that knowledge of a description format defined by OSI is also required.

In addition, even when a management apparatus and a management agent are prepared and automatic connection is performed, there is a problem that when a new NE needs to be managed, an operation for mounting the management agent is required.
In addition, there is a problem that it is difficult for a user who has only knowledge to perform an operation operation of NE using CLI such as Telnet at the site of network operation to newly perform the above advanced operation.

  The present invention has been made in view of such circumstances, and an object of the present invention is to enable automatic connection setting for subsequent NEs even when the operator has only knowledge to manually connect using the CLI. To provide a connection device, a method, and a program.

  The present invention has been made to solve the above-described problems, and the invention according to claim 1 is a connection information storage means for preliminarily storing connection information for connecting to the terminal in association with system information of the terminal. A connection destination input means for receiving connection destination information for designating a connection destination terminal; and a product detection means for detecting system information relating to the terminal of the connection destination information based on the connection destination information received by the connection destination input means. And login means for selecting connection information related to the system information detected by the product detection means from the connection information storage unit and connecting to the terminal of the connection destination information based on the selected connection information. This is a featured network connection device.

  The invention according to claim 2 is a connection information storage means for preliminarily storing connection information for connecting to the terminal in association with product information which is a part of system information of the terminal, and a product for preliminarily storing the product information. Based on the connection destination information received by the connection destination input means, the connection destination input means for receiving the connection destination information specifying the connection destination terminal, and the system information related to the terminal of the connection destination information is received. Product detection means for detecting product information that matches the received system information from the product information stored in the product information storage means, and connection information related to the product information detected by the product detection means. A log-in selected from the connection information storage unit and connected to the terminal of the connection destination information based on the selected connection information. A network connection device, characterized in that it comprises a means.

  According to a third aspect of the present invention, the product detection means detects whether or not the connection destination terminal is operating normally based on the connection destination information received by the connection destination input means. The network connection device according to claim 1, further comprising:

The invention according to claim 4 is a connection information generating means for receiving product information and connection information, and storing the received product information and connection information in association with each other in the connection information storage means,
The network connection device according to claim 1, further comprising:

  According to a fifth aspect of the present invention, the connection information storage means stores in advance connection information for connecting to the terminal in association with connection destination information designating a terminal, and the login means is the connection destination input means. The connection information is selected from the connection information storage unit based on the received connection destination information, and connected to the terminal of the connection destination information based on the selected connection information. Item 5. The network connection device according to Item 4.

  According to a sixth aspect of the present invention, the connection information includes connection information based on a plurality of connection methods for connecting to the terminal, and the log-in means includes the selected connection destination information indicating connection information based on a plurality of connection methods. If it has, the connection information by one connection method is selected from the connection information by the plurality of connection methods, and the terminal is connected to the terminal based on the connection information by the selected one connection method. The network connection device according to any one of claims 1 to 5.

  According to a seventh aspect of the present invention, in the network connection device according to any one of the first to sixth aspects, the connection destination information of the connection information storage means is described in an XML format or a TEXT format. is there.

  In the invention according to claim 8, the system information of the terminal is information on a manufacturer of the terminal, information on an application operating on the terminal, or information on a version of an application operating on the terminal, and the connection information Is prompt information transmitted from the terminal, user name information for authentication of the terminal, password information for authentication of the terminal, or right change command information of the terminal. The network connection device according to claim 1.

  The invention according to claim 9 stores in advance connection information for connecting to the terminal in association with the system information of the terminal, receives connection destination information designating a connection destination terminal, and receives the received connection destination information Based on the connection destination information, detecting system information related to the terminal of the connection destination information, selecting connection information related to the detected system information from the previously stored connection information, and based on the selected connection information, A network connection method characterized by connecting to a terminal.

  The invention described in claim 10 receives connection information storage means for preliminarily storing connection information for connecting a computer to the terminal in association with system information of the terminal, and connection destination information for designating a connection destination terminal. Connection destination input means, product detection means for detecting system information related to the terminal of the connection destination information based on the connection destination information received by the connection destination input means, and system information detected by the product detection means A network connection program for selecting connection information to be selected from the connection information storage unit and functioning as a log-in means for connecting to the terminal of the connection destination information based on the selected connection information.

  According to the present invention, there is an effect that an automatic connection to the NE is possible even when the operator has only knowledge to manually connect using the CLI.

First, the basic technique used in the embodiment of the present invention will be outlined.
SNMP (Simple Network Management Protocol) is a protocol for monitoring and controlling a communication device (NE) connected to a network such as a router, a computer, and a terminal in a TCP / IP network.

The device (NE) to be controlled has a management information database called MIB-II (Management Information Base-II), and the device to be managed is set appropriately based on the MIB-II of the target device. Shall be performed.
One of the MIB-IIs includes SysDescr information. The SysDescr information includes a device name of the target NE, a vendor name of the device name (manufacturer information), and information of a program operating on the target NE (for example, OS (Operating System)). System information of the target NE such as the version of the system).

In the embodiment, it is assumed that the NE is operating an SNMP agent (Simple Network Management Protocol Agent). Here, the SNMP agent is a program provided in a network device such as a hub that supports SNMP, manages its own MIB-II, and passes the MIB-II to the SNMP manager according to a request from the SNMP manager. , To operate the machine.
In the embodiment according to the present invention, as will be described later, the present invention can be applied even when the SNMP agent is not operating in the target NE.

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing a configuration of a network connection device 1 according to an embodiment of the present invention.
In FIG. 1, the network connection device 1 displays output information to the user A and receives input information from the user A. Further, the network connection apparatus 1 connects to the NE 2 via the network 3 (NW 3).

  The network connection device 1 includes a GUI unit 101, a product detection unit 102, a PING connection unit 103, an SNMP connection unit 104, an automatic login unit 105, a manual login unit 106, a Telnet connection unit 107, an adapter file generation unit 108, and a product csv storage unit 120. And an adapter file storage unit 121 for automatic login.

  The product csv storage unit 120 stores the OS name of the NE device and the manufacturer (vendor) of the NE device as shown in FIG. Store as a csv file. Product. In the csv file, a character string for uniquely determining a later-described product file, which is NE connection information, is described.

Product. Of FIG. The csv file describes the OS name of the NE device and the name of the manufacturer (vendor) of the NE device. These can be arbitrarily described in a classification that is easy for the user A to manage.
For example, if you want to use the same login method for NEs of the same manufacturer, you may classify them according to the manufacturer. If you want to use the same login method for NEs of the same OS, classify them according to the same OS. Good. Also, how the classification is performed is arbitrary.
For example, in FIG. 2, there are OS1, OS2006, OSY, OS1500, OSZ, OSXP as NE OS names, and RED, BLUE, GREEN, PURPLE as NE vendor names. The NE OS name may include not only the NE OS name but also the OS version, and the NE vendor name may include not only the NE vendor name but also the NE series name and its version. It may be information.

The automatic login adapter file storage unit 121 has a function of storing a plurality of adapter files. For example, as shown in FIG. 1, a plurality of adapter files that are F01, F02,..., F08,.
Each adapter file stored in the automatic log-in adapter file storage unit 121 stores information (connection information) for connecting to the corresponding target NE.

  An example of the adapter file is shown in FIG. In the embodiment, the adapter file is an XML (extensible Markup Language) file. In part of the adapter file, Product. There is one unique character string described in csv, and each adapter file is identified by this character string.

For example, in FIG. 3, a character string “RED” surrounded by <product></product> tags is a unique character string of this adapter file.
The adapter file also stores prompt information, which is information related to a prompt transmitted by the target NE, along with login name information and password information that are information for connecting to the target NE. Here, the prompt information is a character string of a prompt such as “Username:” or “Password:” sent from the target NE for authentication.

  For example, in FIG. 3, a character string (for example, “neso”) surrounded by a <LoginName> tag and a </ LoginName> tag is user name information, and is surrounded by a <Password> tag and a </ Password> tag. The character string (for example, “nesopassword”) is the password information, and a character string (for example, “Username:”) surrounded by the <LoginPromp> tag and the </ LoginPrompt> tag is a prompt for inputting the login. Information, and a character string (for example, “Password:”) surrounded by a <PasswordPrompt> tag and a </ PasswordPrompt> tag is prompt information for inputting a password.

The character string in the tag shown in the example of the adapter file is not limited to this example. In the example of FIG. 3, the adapter file is shown on the premise that there is one file for each interface specification (system information), but the character string in the tab is changed and all information is collected into one file. May be.
In the embodiment, for example, Product. Of the productcsv storage unit 120 shown in FIG. One of the character strings included in the csv file matches, for example, a character string enclosed by <product></product> tags of one adapter file stored in the adapter file storage unit 121 for automatic login shown in FIG.

Returning to the description of the network connection device 1 of FIG. The GUI unit 101 has a display device and an input device, and displays output information for the user to input or confirm to the user A via the display device, and the user B uses the input device. It has a function of receiving input information.
Here, for example, the display device is a CRT (Cathode Ray Tube), a liquid crystal display device, or the like, and the input device is an input device such as a keyboard or a mouse.

For example, the output information output from the GUI unit 101 to the user via the display device is information for designating the NE that the user desires to connect to (hereinafter referred to as the target NE), and the IP address of the target NE is directly specified. Information on a screen for inputting and information on a screen for displaying an icon associated with the IP address of the target NE are displayed.
For example, the input information that the GUI unit 101 receives from the user via the input device is the IP of the target NE that is directly input or the IP address of the target NE that is associated with the selected icon.

Further, the GUI unit 101 has a function of receiving information on a connection method for performing automatic connection or manual connection based on the input IP address.
In addition, when the input connection method information is automatic connection, the GUI unit 101 transmits the input IP address of the target NE to the product detection unit 102 and the automatic login unit 105, and the input connection method information When the information is manual connection, it has a function of transmitting the input IP address of the target NE to the manual login unit 106.

The product detection unit 102 has a function of receiving the IP address of the target NE from the GUI unit 101, detecting the product information of the target NE based on the received IP address, and transmitting the detected product information to the automatic login unit 105. .
The product detection unit 102 detects the product information of the target NE based on the received IP address by detecting whether the target NE is operating via the PING connection unit 103. , SysDescr information that is one of the MIB-IIs of the target NE is acquired via the SNMP connection unit 104, and then the acquired SysDescr information (a character string thereof) is stored in the Product. It is detected whether or not it exists in the description of the csv file, and if the detection result exists, the Product. The description of the csv file is detected as product information.

The PING connection unit 103 has a function of detecting whether or not the NE specified by the IP address is operating normally based on the IP address received from the product detection unit 102.
The method for detecting whether or not the NE specified by the IP address performed by the PING connection unit 103 is operating normally is, for example, that the PING connection unit 103 issues an IP packet to the NE specified by the IP address Then, the packet arrives correctly at the NE, an IP packet issued from the NE is responded, and whether or not the IP packet response is received from the NE is detected.
It is also possible to detect whether the network up to the NE is normal or not by detecting that the NE is operating normally.

The SNMP connection unit 104 has a function of acquiring SysDescr information that is one of the MIB-IIs of the NE (target NE) specified by the IP address based on the IP address information received from the product detection unit 102.
The SNMP connection unit 104 acquires the SysDescr information that is one of the MIB-IIs of the target NE, for example, by acquiring the MIB-II by an SNMP Get command by the target NE and the SNMP, and by using one of the MIB-IIs. Get some SysDescr information.

The automatic login unit 105 receives the IP address from the GUI unit 101, receives the product information of the target NE from the product detection unit 102, and converts the adapter file from the automatic login adapter file storage unit 121 based on the received product information. It has a function of selecting and logging in to the target NE via the Telnet connection unit 107 based on the selected adapter file and the received IP address.
Here, the method for selecting the adapter file based on the product information received by the automatic login unit 105 is that the automatic login unit 105 has received a character string enclosed in <product></product> tags in the adapter file. The adapter file that matches the product information is selected from the automatic login adapter file storage unit 121 and executed.

The manual login unit 106 receives the IP address of the target NE from the GUI unit 101, generates connection information for connection with the received IP address, and is designated by the received IP address based on the generated connection information. A function to connect to the target NE.
Further, when the manual login unit 106 succeeds in connecting to the target NE specified by the received IP address based on the generated connection information, the generated connection information is transmitted via the adapter file generation unit 108 described later. Is stored in the adapter file storage unit 121 for automatic login as an adapter file.

  The Telnet connection unit 107 has a function of receiving an IP address and connection information from the automatic login unit 105 or the manual login unit 106 and connecting to the target NE specified by the received IP address based on the received connection information. Have.

  The adapter file generation unit 108 has a function of receiving an IP address and connection information from the manual login unit 106 and generating an adapter file in the automatic login adapter file storage unit 121 based on the received IP address and connection information.

Next, the operation of the network connection device 1 according to the embodiment of the present invention will be described with reference to the flowcharts of FIGS.
First, referring to FIG. 4, as a first operation example, a NE product to be connected is detected, an adapter file in which the detected NE product is valid is selected from XML files registered in advance, and the selected adapter is selected. The operation when automatically logging in to the target NE will be described based on the connection information such as the user name and password that are the contents of the file.

First, the GUI unit 101 receives an input of the IP address of the NE (target NE) to be connected from the user A (step A2).
Next, the GUI unit 101 receives a selection input as to whether to connect automatically or manually to the target NE input from the user A (step A3). Here, it is assumed that the user A has selected and input automatic connection.

The GUI unit 101 that has received the IP address of the target NE and has received information on the connection method for automatic connection transmits the IP address of the target NE to the product detection unit 102 and the automatic login unit 105.
Next, the product detection unit 102 that has received the IP address of the target NE detects whether or not the target NE is operating normally via the PING connection unit 103 (step A4). Here, a description will be given assuming that the target NE is detected as operating normally.
Next, the product detection unit 102 acquires information on SysDescr, which is one of the MIB-IIs of the target NE, via the SNMP connection unit 104 (step A5).

  Next, the SNMP connection unit 104 transmits the acquired character string information of SysDescr to the product detection unit 102. The product detection unit 102 that has received the character string information of SysDescr from the SNMP connection unit 104, the Product.com in the productcsv storage unit 120 in the character string information of the SysDescr. What is described in the csv file is detected (step A6). Here, Product. Description will be made assuming that the character string of SysDescr exists in csv.

Product. When it is detected that there is a character string that matches the character string of SysDescr in the csv file, the product detection unit 102 transmits the detected character string (product information) to the automatic login unit 105 (step A6).
Here, the character string information of SysDescr and Product. It is assumed that the character string matched with the information described in csv is “RED”, and the character string “product information” (product information) is transmitted to the automatic login unit 105 by the product detection unit 102.

Next, the automatic login unit 105 receives the product information from the product detection unit 102, and searches the adapter file storage unit 121 for automatic login based on the received product information (character string “RED”) (step A6).
For example, when the received product information is a character string “RED”, the automatic login unit 105 automatically logs in an adapter file whose character string “RED” is surrounded by a <product> tag and a </ product> tag. Select from the adapter file storage unit 121.
In this case, it is assumed that the adapter file selected by the automatic login unit 105 is, for example, the adapter file shown in FIG.

Next, the automatic login unit 105 executes login to the target NE specified by the IP address received from the GUI unit 101 via the Telnet connection unit 107 based on the selected adapter file (step A7).
As a method for the automatic login unit 105 to log in to the target NE, for example, first, the automatic login unit 105 connects to the target NE specified by the IP address by Telnet via the Telnet connection unit 107.

After that, the automatic login unit 105 targets the character string enclosed between the <LoginPromp> tag and the </ LoginPromp> tag of the selected adapter file or the character string enclosed between the <PasswordPrompt> tag and the </ PasswordPrompt> tag. Wait for the transmission from NE.
In this case, it waits for the character string “Username:” or “Password:” to be transmitted from the target NE.

  Next, the automatic login unit 105 receives a character string from the target NE, and when the received character string is a character string surrounded by a <LoginPromp> tag and a </ LoginPromp> tag of the selected adapter file. The character string enclosed by the <LoginName> tag and the </ LoginName> tag is transmitted to the target NE, and the received character string is enclosed by the <PasswordPrompt> tag and the </ PasswordPrompt> tag of the selected adapter file. In the case of a character string, a character string enclosed by a <Password> tag and a </ Password> tag is transmitted.

In this case, when the character string “Username:” is received from the target NE, the character string “neso” is transmitted to the target NE, and when the character string “Password:” is received from the target NE, the character string “Nesopassword” is transmitted to the target NE.
Thereby, for example, the connection with the target NE on the communication protocol such as Telnet is completed, and then the user A can set the target NE on the CLI.

For example, by connecting to the target NE, for example, the GUI unit 101 generates a CLI console, and displays a prompt from the target NE on the generated CLI console (step A8). After that, the GUI unit 101 inputs a command from the user A via the CLI console and transmits it to the target NE (step A9), acquires a response from the target NE, and displays the acquired response on the CLI console (step A10). ). Thereafter, the GUI unit 101 repeats the processes of step A9 and step A10, so that the user A can set the target NE.
Thereafter, the GUI unit 101 receives information on the connection termination with the target NE from the user A, transmits the received connection termination information to the target NE (step A11), and disconnects the connection with the target NE (step A12). ), The process is terminated.

  Note that the automatic login unit 105 includes, in the previously selected adapter file, prompt information (for example, “>”) from the target NE after connection, a character string of a command for changing authority such as su and enable, When the password prompt character string and the password character string related to the above are present in the adapter file selected earlier, a process for changing authority is executed in the connected NE using these.

For example, in step A8, when the automatic login unit 105 detects that the character string “>” of the prompt from the target NE has been received, the automatic login unit 105 changes the right described in the adapter file selected earlier. The command to send “su” or “enable”, which is the command of, waits for receiving the character string of the prompt for entering the password (for example, “Password:”) from the target NE, and prompts to enter the password Is received from the target NE, a password character string is transmitted.
As described above, the automatic login unit 105 can connect to the target NE and execute authority change based on the selected adapter file.

  Note that a reserved character string such as “BLANK” is described in the character string enclosed in the tag of the adapter file illustrated in FIG. When transmitting a user name or the like to the target NE based on the adapter file, the unit 105 detects the reserved character string “BLANK” in the character string of the user name surrounded by the tag, It is also possible to send a special character of the Enter key (character information corresponding to the Enter key) without sending a character string.

  In the above description, the product detection unit 102 determines that the received SysDescr information is stored in Product.csv of the productcsv storage unit 120. The connection destination product of the target NE is detected by detecting whether or not the character string of SysDescr is present in the description of the csv file, but the Product.c in the productcsv storage unit 120 is detected. The product detection unit 102 transmits the received SysDescr information to the automatic login unit 105 without using the csv file, and the adapter file including the character string of the SysDescr information received by the automatic login unit 105 is used as the adapter file storage unit 121 for automatic login. You may make it select directly from.

In the first operation example, the operation of the network connection device 1 according to the embodiment in which the adapter file for connection already exists and the automatic connection is performed using the information of the adapter file has been described.
Next, an operation when the adapter file does not exist in the network connection device 1 according to the embodiment will be described. A second operation example for performing a setting process for automatic login in the subsequent operation using only the operation knowledge by CLI when the adapter file does not exist will be described with reference to FIGS.

  First, in FIG. 4, the GUI unit 101 receives an input of an IP address of a NE (target NE) to be connected from the user A (step A2). Next, the GUI unit 101 receives a selection input as to whether to connect automatically or manually to the target NE input from the user A (step A3). The processing so far is the same as the first operation example. Next, it is assumed that user A selects and inputs manual connection in step A3.

The GUI unit 101 that has received the IP address of the target NE and has received the information on the connection method for manual connection transmits the IP address of the target NE to the manual login unit 106 (from D1 in FIG. 4 to D1 in FIG. 5). ).
Next, the manual login unit 106 displays to the user A via the GUI unit 101 whether to select an adapter file or input prompt information (step B4 in FIG. 5). Here, it is assumed that the user A has selected input of prompt information.
Next, the manual login unit 106 displays a screen for inputting information (prompt information) necessary for connection to the user A via the GUI unit 101, and the prompt input by the user A via the GUI unit 101. Information is received (step B5).

For example, the screen for inputting prompt information displayed by the manual login unit 106 includes an input field for inputting the IP address, login prompt, login user name, password prompt, password, etc. of the target NE as shown in FIG. Have.
User A inputs information corresponding to each of the input fields of the input screen of FIG.

User A inputs a command for changing the IP address, login user name, password, and, if necessary, user authority of the target NE based on the input screen of FIG. Furthermore, the user A prompts a character string for entering a login user name (eg “Username:” in the example), a prompt for entering a password (eg “Password:” in the example), and a command for changing user authority. A prompt character string (for example, “>”) is input.
When the manual login unit 106 displays a screen for inputting prompt information, the IP address of the target NE previously received from the GUI unit 101 by the manual login unit 106 is displayed in the input field of the IP address of the target NE. You may input and display beforehand.

  Next, based on the character string information of the input prompt information, the manual login unit 106 stores a temporary adapter file for automatic login (referred to as a temporary adapter file) in, for example, the memory of the manual login unit 106. , Generate.

  In the embodiment, the information input on the screen shown in FIG. 6 is converted into an XML file shown in FIG. 3, for example, and stored. For example, in the temporary adapter file, between the tags <LoginPromp> and </ LoginPrompt>, for example, an input character string such as “Username:”, and between the tags <PasswordPrompt> and </ PasswordPrompt>. For example, an input character string such as “Password:” is described.

In the temporary adapter file, a character string of the input user name is described between the tags <LoginName> and </ LoginName>, and the input password character string is stored in <Password></Password>. Described.
Furthermore, in the temporary adapter file, when a command for changing authority is input in the input of FIG. 6, for example, the input character string “>” is described in <Prompt></Prompt>, and <EnableCommand></EnableCommand> describes a character string of the input command such as “enable” or “su”, and <EnablePassword></EnablePassword> describes the character string of the input password for changing the authority. Is done.

Next, based on the generated temporary adapter file, the manual login unit 106 connects (automatic login) to the target NE specified by the IP address received from the GUI unit 101 via the Telnet connection unit (step B6). .
Here, the connection to the target NE executed by the manual login unit 106 (step B6 in FIG. 5) is the connection (FIG. 4) that the automatic login unit 105 connects to the target NE based on the product file in the first operation example. Step A7).

  For example, after the manual login unit 106 is connected to the target NE via the Telnet connection unit 107, the prompt information of the temporary product file input, for example, “Username:” or “Password:” character string from the target NE. Wait for it to be sent.

After detecting that the character string is transmitted from the target NE, the manual login unit 106 detects <UserName:>, which is a character string in <LoginPromp></LoginPrompt>, and <LoginName></LoginName> The character string of the user name described in the URL is transmitted to the target NE via the Telnet connection unit 107.
Further, when the manual login unit 106 detects “Username:” that is a character string in <PasswordPrompt></PasswordPrompt>, the manual login unit 106 converts the password character string described in <Password></Password> into the Telnet connection unit. The information is transmitted to the target NE via 107.

  In step B6, when the user name and password transmitted by the manual login unit 106 are not valid for the target NE and the manual login unit 106 cannot connect to the target NE, the manual login unit 106 executes input of prompt information again. (Step B5) Based on the prompt information input again, the connection with the target NE is repeated (Step B6).

In step B6, when the user name and password transmitted by the manual login unit 106 are valid for the target NE and the manual login unit 106 can connect to the target NE, the manual login unit 106 passes through the adapter file generation unit. An adapter file is generated in the automatic log-in adapter file storage unit 121 based on the temporary adapter file (step B7).
Here, as the adapter file to be generated, the input IP address to be connected is used as the adapter file name. For example, if the IP address is “192.168.1.5”, an adapter file is generated according to a naming rule that adds “adapter” to an IP address such as “192.168.1.5.adapter” as an adapter file name.

  Next, since the connection with the target NE has been established, the user A sets the target NE. The subsequent processing is the same as step A8 to step A12 in FIG.

As described above, the adapter file for connecting to the target NE is generated in the automatic login adapter file storage unit 121.
Thereafter, the automatic login unit 105 of the network connection device 1 in the embodiment can connect to the target NE using the generated adapter file.

  For example, when connecting to the same target NE thereafter, the automatic login unit 105 searches for an adapter file bearing the same IP address from the IP address input from the GUI unit 101 (step B9). If an adapter file is detected, the above procedure is automatically executed and login is performed. If the adapter file does not exist (because it is deleted, etc.), the user selects a different adapter file as an unknown target and connects. Alternatively, assuming that the corresponding adapter file does not exist, the second operation is repeated, and the user is made to input a necessary character string to generate an adapter file. Details will be described later.

Next, using FIG. 4 and FIG. 5, an operation in which the manual login unit 106 executes connection processing when automatic connection fails is described.
First, in step A4 in FIG. 4, the product detection unit 102 that has received the IP address of the target NE performs detection of whether or not the target NE is operating normally via the PING connection unit 103. Is not operating normally, the connection with the target NE is impossible, and the process is terminated.

  In step A5 of FIG. 4, the product detection unit 102 acquires information on SysDescr, which is one of the MIB-IIs of the target NE, via the SNMP connection unit 104, but the target NE does not respond to the SNMP connection. (D2 in FIG. 4), the product detection unit 102 displays a message that the SNMP agent of the target NM is not operating (step B10), displays a selection dialog, and selects input from the dialog from the user A. (Step B11).

The selection dialog displayed by the product detection unit 102 includes adapter file selection, manual setting, and processing end.
When the selection input from the user A is an adapter file selection, the manual login unit 106 displays to the user A via the GUI unit 101 whether to select an adapter file or input prompt information (step B4). ). The subsequent processing is the same as the procedure described above.

  When the selection input from the user A is manual setting, the manual login unit 106 displays a screen for inputting information (prompt information) necessary for connection to the user A via the GUI unit 101. Prompt information entered via the GUI unit 101 is input (step B5). The subsequent processing is the same as the procedure described above.

In step A6 of FIG. 4, the product detection unit 102 determines that the product.product stored in the productcsv storage unit 120. When it is detected that the character string of SysDescr received from the SNMP connection unit 104 does not exist in the description of the csv file (D3), the automatic login unit 105 automatically logs in the adapter file of the IP address received from the GUI unit 101. The adapter file storage unit 121 is searched (step B9).
For example, assuming that the IP address received from the GUI unit 101 is 192.168.1.5, the automatic log-in unit 105 stores the adapter file whose adapter file name is “192.168.1.5.adapter”, and the product csv storage unit 120. Search from.

  When the automatic login unit 105 can retrieve the adapter file of the received IP address from the adapter file storage unit 121 for automatic login (E2), the automatic login unit 105 is designated by the IP address received from the GUI unit 101 based on the retrieved adapter file. The target NE is logged in via the Telnet connection unit 107 (step A7). The subsequent processing is the same as the procedure described above.

  When the automatic login unit 105 cannot retrieve the adapter file of the received IP address from the automatic login adapter file storage unit 121 (E2), the manual login unit 106 sends the adapter file to the user A via the GUI unit 101. Or selection of prompt information input is displayed (step B4). The subsequent processing is the same as the procedure described above.

  Further, in step B4, the manual login unit 106 displays to the user A via the GUI unit 101 whether the adapter file is selected or the prompt information is input, and the selection of the user A is the adapter file selection. In this case, the manual login unit 106 acquires a list of product files from the productcsv storage unit 120, displays the acquired list of product files to the user A via the GUI unit 101, and selects and inputs a product file from the user A (Step B8).

  Upon receiving the product file selection input from the user A, the manual login unit 106 acquires the received product file of the selection input from the productcsv storage unit 120, and receives the IP address received from the GUI unit 101 based on the acquired adapter file. Login is performed to the target NE specified by (1) via the Telnet connection unit 107 (step A7). The subsequent processing is the same as the procedure described above.

  As described above, even if the process by the automatic login unit 105 cannot connect to the target NE, the manual login unit 106 can execute the process to connect to the target NE.

In the embodiment, the adapter file associated with the IP address has been described as being created with the adapter file name “192.168.1.5.adapter”. However, the present invention is not limited to this. , “192.168.1.5” is described between the tags <IPADDRESS> and </ IPADDRESS>, and the file name may be arbitrary.
In this case, the automatic login unit 105 selects and selects the adapter file in which the character string between the tags <IPADDRESS> and </ IPADDRESS> matches the IP address received from the GUI unit 101 in the adapter file. Based on the adapter file, a function to connect to the NE specified by the received IP address is provided.

In the embodiment, the adapter file associated with the IP address is created as the adapter file name “192.168.1.5.adapter” (step B7). A unique file name may be generated by adding information on the date and time when the file is generated.
By generating the adapter file in this way, the same IP address is used when the automatic login unit 105 searches for the adapter file of the IP address received from the GUI unit 101 from the automatic login adapter file storage unit 121 (step B9). Even when there are a plurality of adapter files, the automatic login unit 105 can select one adapter file by selecting an adapter file with a new date and time generated, for example. is there.
In the adapter file, the date and time information may be described as information surrounded by tags in the adapter file. In this case, for example, when there are a plurality of adapter files, the automatic login unit 105 selects an adapter file with a new date and time at the date and time in the tag of the adapter file.

Next, a procedure for generating an adapter file by a simple method when the adapter file does not exist and performing a setting process for automatically connecting to the target NE in the subsequent operation will be described.
The procedure for the automatic login unit 105 to perform automatic login by inputting a necessary character string in the adapter file has been described in the first and second operation examples.
Next, a method for rewriting the adapter file generated in the second operation example to change it to a more general-purpose adapter file will be described.

  For example, the adapter file with the adapter file name “192.168.1.1.adapter” generated in the second operation example (hereinafter referred to as 192.168.1.1 adapter file) is the IP address of the target NE. Is selected by the automatic login unit 105 (in step B9).

  Therefore, for example, the generated adapter file, 192.168.1.1 adapter file, is copied, and a character string (an arbitrary character string or a blank space between the tag <product> and the tag </ product> in the adapter file) For example, “XXX”). For example, the character string “XXX” is changed to “ABC”. Also, product. A character string “ABC” is newly added to the csv file.

  As a result, a procedure for operating with the character string “ABC” is newly added to the first specific example, and the product “ABC” (the character string “ABC” appears easily in the character string of SysDescr by SNMP). It is possible to realize automatic login to the target NE.

Next, the login when the target NE has a plurality of login methods will be described with reference to FIG.
For example, there are a case where there are a plurality of connected users in the target NE, and a case where it is desired to use an automatic login to the router with an administrator authority and a case where it is desired to log in with a general user authority.
Various connection methods (login patterns) can be selected by describing connection information of a plurality of patterns (default, login, enable, lab) in the adapter file, for example, as shown in FIG. .

In the example of FIG. 7, a portion surrounded by tags <default> and </ default>, a portion surrounded by tags <login> and </ login>, and surrounded by tags <enable> and </ enable>. The parts surrounded by the tags <lab> and </ lab> are described as different login patterns.
Each is identified by a unique character string of default, login, enable, and lab, and when the user selects these character strings, the login pattern is changed and automatic login is performed.
In addition, character strings of a plurality of patterns are described in a portion surrounded by tags <select> and </ select> (default, login, enable, lab).

  In this case, when there are a plurality of login methods in the selected adapter file, the manual login unit 106 selects a login method from the plurality of login methods of the selected adapter file, and connects based on the selected login method. Make it functional.

For example, in step B8, the manual login unit 106 that acquired the adapter file in response to the selection input of the product file from the user A is a portion surrounded by the tags <select> and </ select> of the acquired adapter file. In addition, it is detected whether there are character strings of a plurality of patterns.
If there are a plurality of patterns of character strings, the manual login unit 106 sends a character string (for example, default) enclosed by tags <select> and </ select> of the selected adapter file via the GUI unit 101. , Login, enable, lab) are displayed to the user A, and the selection input by the user A from the displayed character string is awaited.

  Next, when the manual login unit 106 receives the selection input (for example, enable) of the user A from the displayed character string, the IP received from the GUI unit 101 based on the connection information surrounded by the received selection input tag. Log in to the target NE specified by the address via the Telnet connection unit 107 (step A7).

  Note that when there are a plurality of login methods in the adapter file selected for connection with the target NE, the automatic login unit 105 connects using the default login method. In this way, when the user selects automatic connection, the user does not need to select a login method even when there are multiple login methods in the adapter file, and connects to the target NE. I can do it.

  As described above, in the present embodiment, the user name, password, etc. for connecting to the NE in advance are associated with the NE manufacturer (manufacturer name), the NE OS, the NE OS version, and the like. Connection information is stored in advance in a storage device.

  First, the IP address of the connection target NE is acquired from the user via the user interface. As a method for acquiring the IP address of the connection target NE, a method in which the user directly inputs the IP address or a method of clicking and specifying an icon for selecting the connection target NE in the software GUI may be used.

Next, the interface specification on the CLI of the connection target NE having the acquired IP address is specified. The interface specification often depends on the NE OS, and if the NE OS type can be specified, the pattern of character string information transmitted by the NE, that is, the CLI login interface specification can be specified.
For this purpose, first, the parameters of the MIB-II SysDescr object are obtained from the NE by SNMP, and the NE, OS manufacturer, OS version, etc. are specified.
Next, connection information is retrieved from the storage device based on the identified NE OS, OS version, manufacturing vendor, and the like, and the connection target NE is connected based on the retrieved connection information.

  If communication with the SNMP agent is not possible or communication with SNMP is not desired, the manufacturer name may be input to the software together with the IP address in advance. Alternatively, if the product of the target NE is known in advance before connection, the XML file for the target NE to be performed in the next process may be manually selected directly.

  According to the present invention described above, it is possible to automatically log in to a plurality of NEs having different specifications of character string information transmitted from the NE on the CLI due to differences in manufactured products, NE OS versions, and the like. Even if the above specifications are different and connection is not possible due to the introduction of OS or OS version renewal, automatic connection can be made immediately without the need for re-implementation by programming or agent technology.

  In addition, according to the present invention described above, special commands for changing the login user name, login password, and user authority (such as the SU command in the UNIX (registered trademark) CLI and the enable in the router CLI) for NEs having different specifications. ) And the interface specification of the character string information transmitted from the NE are described in an XML format text file called an adapter file, and the interface specification (system information of the target NE) is read and the interface specification is used. Character string information to be sent for automatic login due to the difference in the character string information described in the adapter file to the NE having a plurality of different specifications and the function of automatically transmitting an appropriate character string to the NE Change the user's awareness It is possible to automatically login without a.

  Further, according to the present invention described above, it is possible to automatically select and log in which information is used for automatic login from a plurality of XML files by acquiring information on the target product and OS by SNMP. In addition, it has a function to register a rule for applying different XML files for each target, and a specific XML file is applied to a specific NE according to the rule, and automatic connection can be made even if the password and user name are different. it can.

As described above, when the present invention is used, even when the operator has only knowledge of manually using the CLI to connect, subsequent automatic connection setting for the NE is enabled.
Further, connection to various types of NEs having different interface specifications, such as prompt information response, can be automatically performed depending on the NE manufacturing vendor and OS. Even when connection to multiple types of NEs with different interface specifications such as response to prompt information due to differences in NE manufacturing vendor and OS cannot be performed automatically by the above method, it is equivalent to connecting manually using CLI. With this knowledge alone, it is possible to automatically connect the first and subsequent processes.

Even when NEs that are unknown and have different interface specifications are to be monitored, automatic connection can be set without developing and implementing an application program of the network management apparatus.
Further, not only automatic connection but also setting of processing to be automatically performed at the time of connection, such as an authority change command, can be performed even when the operator has only the same knowledge as when manually connecting using the CLI.
Further, not only automatic connection but also setting of processing to be performed automatically at the time of connection such as authority change command can be performed without developing and implementing an application program of the network management apparatus.

In addition, automatic connection is possible for a plurality of objects with different user names and passwords.
Therefore, even when a new NE is introduced and set as a management target, automatic connection and subsequent setting processing can be continued without taking any period, cost, and effort for development of the network management apparatus.

In addition, the present invention has a function of reading a response related to CLI connection, a function of judging a target product by SNMP, and a function of reading a setting definition by XML and automatically connecting, so that automatic connection is not required. Can be performed.
In addition, the present invention has a function of simplifying a plurality of user interfaces for displaying / changing an XML setting definition, a function for automatically generating a setting definition, and a function for selecting an XML setting definition. By using only skills and knowledge necessary for business, automatic connection can be set and subsequent automatic connection can be realized.

In the above-described embodiments, each device that implements the present invention has been described in terms of functions. However, each function of each device can also be realized by causing a computer such as a personal computer or a workstation to execute a program.
That is, the various processing procedures described in the above embodiments can be realized by executing a program prepared in advance on a computer. These programs are recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, and a DVD, and can be executed by being read from the recording medium by the computer.
For example, a CD-ROM storing a program as shown in the embodiment (may be a separate CD-ROM for each apparatus) is distributed, and each computer reads the program stored in the CD-ROM. You may make it perform.

Using FIG. 8, the SysDescr information of NE and Product. It supplements about the relationship between the character string contained in a csv file, and the character string enclosed by the <product></product> tag of an adapter file, and its operation | movement.
As shown in (1) of FIG. 8, for example, there are NE1 to NE10.
Here, in the NE management, NE1 to NE6 have the same connection method (the connection user name and password are the same as connection information), and NE7 to NE10 have the same connection method.
Here, it is assumed that the SysDescr information, which is system information acquired from NE1 to NE6, includes information (as a character string) that the vendor is vendor 1 and each OS is OS2 to OS7.
Further, it is assumed that the SysDescr information, which is system information acquired from NE7 to NE10, includes information (as a character string) that the OS is OS1 and each vendor is vendor 2 to vendor 5.

  For example, as shown in FIG. When the character strings included in the csv file are “vendor 1” and “OS1”, the SysDesc information (in the character string information) that is the system information of each NE, and the Product. As shown in FIG. 8B, NE1 to NE6 are “vendor 1” and NE7 to NE10 are “OS1” as information matching the character string included in the csv file.

Next, in the embodiment, an adapter file in which the character string enclosed by the <product></product> tag of the adapter file shown in FIG. 8 (4) matches the character string shown in FIG. It becomes possible to connect to each NE using the connection information of the selected adapter file.
Here, as shown in (3) and (4) of FIG. The character string included in the csv file matches the character string enclosed in the <product></product> tag of the adapter file.

Further, in the case where there are NE1 to NE10 as shown in FIG. 8, even when NE11 whose OS is OS1 is newly added, it is connected to NE11 only by setting the connection method in the case of OS1 to NE11. It becomes possible. This is because part of the system information of the NE 11 matches the OS 1, the adapter file of the OS 1 is selected, and the NE 11 is connected to the NE 11 based on the selected adapter file of the OS 1.
Further, even when the NE 12 whose vendor is the vendor 1 is newly added, it is possible to connect to the NE 12 only by setting the connection method for the vendor 1 to the NE 12. This is because part of the system information of the NE 12 matches the vendor 1, the adapter file of the vendor 1 is selected, and the NE 12 is connected based on the adapter file of the selected vendor 1.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design and the like within a scope not departing from the gist of the present invention.

  The present invention is suitable for use in a management apparatus that manages a plurality of network devices.

It is a block diagram which shows the structure of the network connection apparatus in one Embodiment of this invention. Product. It is explanatory drawing which shows an example of a csv file. It is explanatory drawing which shows the 1st example of an adapter file. FIG. 3 is a first flowchart showing the operation of the network connection device of FIG. 1. FIG. 6 is a second flowchart showing the operation of the network connection device of FIG. 1. It is a figure which shows the input screen as an example. It is explanatory drawing which shows the 2nd example of an adapter file. It is explanatory drawing which shows the relationship between system information and NE.

Explanation of symbols

1 Network connection device 2 NE
3 NW
DESCRIPTION OF SYMBOLS 101 GUI part 102 Product detection part 103 PING connection part 104 SNMP connection part 105 Automatic login part 106 Manual login part 107 Telnet connection part 108 Adapter file generation part 120 productcsv storage part 121 Adapter file storage part for automatic login

Claims (10)

Connection information storage means for preliminarily storing connection information for connecting to the terminal in association with system information of the terminal;
A connection destination input means for receiving connection destination information for specifying a connection destination terminal;
Product detection means for detecting system information related to the terminal of the connection destination information based on the connection destination information received by the connection destination input means;
Login means for selecting connection information related to the system information detected by the product detection means from the connection information storage unit, and connecting to the terminal of the connection destination information based on the selected connection information;
A network connection device comprising: Connection information storage means for preliminarily storing connection information for connecting to the terminal in association with product information that is a part of system information of the terminal;
Product information storage means for storing the product information in advance;
A connection destination input means for receiving connection destination information for specifying a connection destination terminal;
Based on the connection destination information received by the connection destination input means, system information related to the terminal of the connection destination information is received and matches the received system information from among the product information stored in the product information storage means. Product detection means for detecting product information;
Login information for selecting connection information related to product information detected by the product detection means from the connection information storage unit, and connecting to the terminal of the connection destination information based on the selected connection information;
A network connection device comprising: The product detection means is
An operation detecting means for detecting whether or not the terminal of the connection destination is operating normally based on the connection destination information received by the connection destination input means;
The network connection device according to claim 1, further comprising: Connection information generating means for receiving product information and connection information, and storing the received product information and connection information in association with each other in the connection information storage means;
The network connection device according to claim 1, further comprising: The connection information storage means
Preliminarily storing connection information for connecting to the terminal in association with connection destination information for specifying the terminal,
The login means is
Selecting the connection information from the connection information storage means based on the connection destination information received by the connection destination input means, and connecting to the terminal of the connection destination information based on the selected connection information;
The network connection device according to claim 1, wherein the network connection device is a network connection device. The connection information is
Having connection information by a plurality of connection methods for connecting to the terminal;
The login means is
When the selected connection destination information includes connection information based on a plurality of connection methods, connection information based on one connection method is selected from connection information based on the plurality of connection methods, and connection information based on the selected connection method is selected. To connect to the terminal based on
The network connection device according to claim 1, wherein the network connection device is a network connection device. The connection destination information of the connection information storage means is
It is described in XML format or TEXT format.
The network connection device according to claim 1, wherein the network connection device is a network connection device. The system information of the terminal is
Information about the manufacturer of the terminal, information about the application running on the terminal, or information about the version of the application running on the terminal,
The connection information is
Prompt information transmitted from the terminal, user name information for authentication of the terminal, password information for authentication of the terminal, or right change command information of the terminal,
The network connection device according to claim 1, wherein: Pre-store connection information for connecting to the terminal in association with the system information of the terminal,
Receives connection destination information that specifies the destination device,
Based on the received connection destination information, system information related to the terminal of the connection destination information is detected,
Select connection information related to the detected system information from the previously stored connection information, and connect to the terminal of the connection destination information based on the selected connection information,
A network connection method characterized by the above. Computer
Connection information storage means for preliminarily storing connection information for connecting to the terminal in association with system information of the terminal;
A connection destination input means for receiving connection destination information for specifying a connection destination terminal;
Product detection means for detecting system information related to the terminal of the connection destination information based on the connection destination information received by the connection destination input means;
Login means for selecting connection information related to the system information detected by the product detection means from the connection information storage unit and connecting to the terminal of the connection destination information based on the selected connection information;
Network connection program to function as.

Images