JP7118846B2 - Information processing device, its control method and program - Google Patents

Description

The present invention relates to network interface control via a USB-connected LAN adapter.

2. Description of the Related Art In recent years, with the increasing complexity of security and functionality required for networks, it has become common to use multiple LANs (Local Area Networks) in offices, commercial facilities, and the like. Information processing apparatuses used in such a network environment are required to be compatible with a plurality of LANs. As one method for supporting a plurality of LANs with one information processing apparatus, there is a method using a NIC (Network Interface Card) having a USB (Universal Serial Bus) interface. A NIC having a USB interface is hereinafter referred to as a "USB-LAN adapter".

When the USB-LAN adapter is connected to the USB host interface of the information processing device, a dedicated driver is loaded and the USB host interface is recognized as a network interface. Then, the OS of the information processing apparatus assigns the recognized network interface an index (internal index) for internally distinguishing it from other network interfaces. This enables network communication using the USB-LAN adapter. In this case, the internal index is not uniquely assigned to the USB-LAN adapter. For example, when the same USB-LAN adapter is inserted and removed, a new internal index is issued each time it is inserted and removed, and assigned to the recognized network interface. USB supports hot plugging, and can be used without turning off the power of peripheral devices (USB devices) and information processing devices conforming to the USB standard. A new internal index is set.

On the other hand, there is SNMP (Simple Network Management Protocol) as a technique for acquiring information of the above information processing apparatus connected to a network. SNMP is a protocol for monitoring and controlling network devices that operates on UDP/IP (User Datagram Protocol/Internet Protocol). By periodically polling MIB (Management Information Base) information using SNMP, the monitoring device can monitor the status of network devices and detect anomalies. Here, the MIB means information that a network device managed by SNMP discloses to inform the outside of its own status, and is defined in RFC1213. For example, Japanese Patent Application Laid-Open No. 2002-300000 discloses a technique for a monitored device to appropriately return MIB information requested by a monitoring device.

When an information processing device connected to a network has a plurality of network interfaces, each network interface is identified using "IfIndex" associated with each network interface in the MIB information. As the IfIndex value at this time, the aforementioned internal index value assigned to the network interface by the information processing apparatus is used.

JP 2011-81433 A

When a user uses an information processing apparatus monitored by a monitoring apparatus as described above, the user may mistakenly remove a USB-LAN adapter for which a network connection is being established. A user who notices this fact is expected to reconnect the USB-LAN adapter to restore communication. The reconnection of the hot-pluggable USB-LAN adapter immediately establishes a network connection and enables communication. However, as a result of assigning a new internal index to the network interface recognized by reconnecting the USB-LAN adapter, the information processing apparatus changes the value of the internal index before and after the USB-LAN adapter is inserted and removed.

On the other hand, when the monitoring device starts monitoring the information processing device, it generally acquires the MIB information described above and grasps the configuration of the network interface in the information processing device. Since it is rare that the configuration of the network interface is changed during monitoring, there are many cases where the specifications continue to use IfIndex included in the MIB information acquired at the start of monitoring. In this case, even if the value of IfIndex changes due to the insertion or removal of the USB-LAN adapter, the monitoring device will attempt to acquire the state information of the network interface using the value of IfIndex before the change. As a result, since the information processing device does not have a network interface corresponding to the acquisition request (SNMP request) received from the monitoring device, an error response is made. Then, the monitoring device judges that an abnormality has occurred in the information processing device and notifies the administrator of the error information. end up

An information processing apparatus according to the present invention has at least one network interface, is an information processing apparatus capable of externally connecting another network interface, and is a network recognized by the information processing apparatus. Setting means for setting an index for identifying the network interface to the interface, and SNMP (Simple Network Management Protocol) for responding to a request from an external device that manages a device on the network using SNMP. means and said another network interface are externally connected, and said other network interface is removed from said information processing device after said other network interface is in a usable state, and said other network interface is externally connected is detected again, notification means for notifying the information processing apparatus to restart according to a predetermined condition.

According to the present invention, even if the USB-LAN adapter is inserted/removed in a scene where an information processing apparatus that establishes a network connection using a USB-LAN adapter is monitored using SNMP, it is possible to prevent troubles in monitoring. can do.

A diagram showing an example of the configuration of an information processing system (a) is a block diagram showing an example of the hardware configuration of the MFP, and (b) is a block diagram showing an example of the hardware configuration of the PC. (a) is a block diagram showing an example of the software configuration of the MFP, and (b) is a block diagram showing an example of the hardware configuration of the PC. A diagram showing an example of the USB-LAN use permission setting screen Flowchart showing the flow of network interface status monitoring processing 4 is a flowchart showing the flow of processing executed when the MFP detects connection of a USB-LAN adapter, according to the first embodiment; A diagram showing an example of a reboot instruction screen 8 is a flowchart showing the flow of processing executed when the MFP detects connection of a USB-LAN adapter, according to the second embodiment; Flowchart showing the flow of processing executed by the MFP upon receiving an SNMP request

BEST MODE FOR CARRYING OUT THE INVENTION The best mode for carrying out the present invention will be described below with reference to the drawings and tables. The following embodiments do not limit the invention according to the claims, and not all the combinations of features described in the embodiments are essential for the solution of the invention.

Embodiment 1

(System configuration)
FIG. 1 is a diagram showing an example of the configuration of an information processing system according to this embodiment. The information processing system according to this embodiment includes a PC 100 as a device for monitoring network devices and an MFP 150 to be monitored. The MFP 150 is an information processing device having multiple functions such as printing, copying, and facsimile. The MFP 150 is connected to a USB compatible network card (hereinafter referred to as “USB-LAN adapter”) 120 via a USB cable 140 and to the network relay device 110 via a network cable (LAN cable) 130 . The network relay device 110 is, for example, a switch or hub. The PC 100 is also connected to the network relay device 110 with a network cable 130 . PC 100 monitors the status of MFP 150 via network cable 130 and USB cable 140 .

(MFP hardware configuration)
FIG. 2A is a block diagram showing an example of the hardware configuration of the MFP 150 according to this embodiment. The MFP 150 includes a control unit 200 , an operation unit 205 , a printer unit 206 , a scanner unit 207 and an external I/F 208 . The control unit 200 includes a CPU 201 , a ROM 202 , a RAM 203 and an HDD 204 and controls each unit within the MFP 150 . The CPU 201 reads control programs stored in the ROM 202 and performs various controls such as communication control. A RAM 203 is used as a main memory of the CPU 201 and a temporary area such as a work area. The HDD 204 is a large-capacity storage device that stores data, various programs, or various information tables. An operation unit 205 is a user interface for the user of the MFP 150 to perform various input operations, and in the present embodiment adopts a touch panel system and also functions as a display unit. A printer unit 206 performs a process of forming an image on paper or the like according to a print job received from a client PC (not shown) and outputting the image. A scanner unit 207 optically reads a document set on a document platen (not shown) and outputs it as image data. The external I/F 208 includes a wired LAN interface (hereinafter referred to as "wired LAN I/F") 209 as communication means and three USB interfaces (hereinafter referred to as "USB I/F") 210a-210a as USB host interfaces. 210c. In this specification, when describing the contents common to the three USBI/Fs 210a to 210c, the term "USBI/F 210" may be used simply. The wired LAN I/F 209 is network connection means for connecting to a wired LAN represented by Ethernet (registered trademark), and transmits and receives various data to and from the PC 100 on the same network and a client terminal (not shown). Communication interface. The USB I/F 210 is a serial interface for connecting a USB standard compliant peripheral device (hereinafter referred to as a “USB device”) to the MFP 150 . USB devices include a keyboard, a mouse, an external HDD, and the aforementioned USB-LAN adapter. In FIG. 2, the USB-LAN adapter 120 is connected to the USB I/F 210a.

The USB-LAN adapter 120 comprises a USB I/F 211 for connecting to a USB I/F 210 as a USB host interface, and a wired LAN I/F 212 . By connecting the USB-LAN adapter 120, the USB I/F 210 on the main body side of the MFP 150 can be used as network connection means similar to the wired LAN I/F 209. FIG.

FIG. 2B is a block diagram showing an example of the hardware configuration of the PC 100 according to this embodiment. The PC 100 has the hardware configuration of a general computer. That is, it is composed of a CPU 221, a ROM 222, a RAM 223, an HDD 224, a graphic controller 225, a monitor 226, a USB I/F 227 and a wired LAN I/F 228, and each component is communicably connected via a bus. The CPU 221 is a processor that controls the PC 100 in an integrated manner. The CPU 221 reads programs stored in the ROM 222 or HDD 224 to the RAM 223 and executes various processes. The ROM 222 stores system programs and the like. A RAM 223 is used as a work area for the CPU 221 . The graphic controller 225 generates UI screens displayed on the monitor 226 . The HDD 224 as a large-capacity storage device stores various application programs and data. Note that an SSD (Solid State Drive) or the like may be used instead of the HDD. A USB I/F 227 connects a keyboard, a mouse, and the like. LAN I/F 228 is network connection means for communicating via network cable 130 .

In the MFP 150 and PC 100 of the present embodiment, one CPU uses one memory (RAM) to execute each process shown in various flowcharts described later, but the present invention is not limited to this. For example, multiple CPUs or multiple memories may cooperate to execute each process.

(MFP software configuration)
FIG. 3A is a block diagram showing an example of a software configuration related to communication processing in the MFP 150 as a monitored device. FIG. 3A shows a network control module 301, a UI control module 302, and an SNMP processing module. Each module operates on an OS (Operating System) 300. It is realized by reading the program to the RAM 203 and executing it.

The network control module 301 performs activation control of the wired LAN I/F 209 and activation control of the USB I/F 210 when functioning as network connection means, thereby establishing network connection. For example, when the connection of the USB-LAN adapter 120 to the USB I/F 210 is detected, the network connection is established to enable data communication. At this time, as described above, the recognized network interface is assigned a unique index for internal identification (hereinafter referred to as "internal index"). Allocation of this internal index will be described later. The network control module 301 further sets the network driver corresponding to the connected USB-LAN adapter 120 and notifies the UI control module 302 according to the status of the network connection. It also refers to a database (USB-LAN DB) 305 that stores information about compatible USB-LAN adapters, and determines whether or not the connected USB-LAN adapter 120 is of an operable type. .

The UI control module 302 displays a UI screen for the user of the MFP 150 to make various settings, accepts input instructions, and issues error notifications. The setting value DB 304 stores and manages various setting values used by each module operating inside the MFP 150 (not shown in FIG. 3, including, for example, software modules responsible for controlling the operations of the printer unit 206 and the scanner unit 207). It is a DB to do. These various setting values include a setting value as to whether or not network connection using the USB-LAN adapter 120 is permitted. If this set value is set to a value indicating prohibition, even if the user connects the USB-LAN adapter 120 to the USB I/F 210, it cannot be used as network connection means. For example, by restricting access to these setting values to general users, the administrator of the MFP 150 or the like can prevent the MFP 150 from being placed in a communicable state using the USB-LAN adapter 120 against their intention. can be prevented. FIG. 4 is an example of a UI screen (USB-LAN use permission setting screen) for the administrator or the like to set the use permission of the USB-LAN adapter 120 . The USB-LAN use permission setting screen 400 in FIG. 4 includes an “permit” button 401 and a “not permit” button 402 . When the user selects the "permit" button 401 and presses the "OK" button 403, the USB-LAN adapter 120 is set to a state in which network connection is possible (permitted state). Specifically, a value representing the permission state is set in the setting value related to the use of the USB-LAN adapter 120 in the setting value DB 304 described above. In this permission state, when the user inserts the USB-LAN adapter 120 into the USB I/F 210, the wired LAN I/F 209 and the wired LAN I/F 212 inside the USB-LAN adapter 120 are activated. As a result, network connection by wired LAN via USB (hereinafter referred to as "usbLAN network") is established. On the other hand, in the disallowed state, the MFP 150 does not establish the usbLAN network even if the connection of the USB-LAN adapter 120 is detected. Note that FIG. 4 shows a UI screen for only setting permission to use the USB-LAN adapter, but the present invention is not limited to this. For example, a screen for collectively setting usage permission with other USB devices such as a USB memory and a keyboard may be used.

The SNMP processing module 303 is a module (SNMP agent) that notifies an external monitoring device of information about the MFP 150 by SNMP. In this specification, a request made by the monitoring device to the monitored device is called an "SNMP request", and a response made by the monitored device to the request is called an "SNMP response". For example, if the received SNMP request is a status information acquisition request indicating the current state of the network interface, the SNMP processing module 303 refers to the MIB information described above and returns the status information to the PC 100 as an SNMP response.

(PC software configuration)
FIG. 3B is a block diagram showing an example of a software configuration related to communication processing in the PC 100 as a monitoring device. FIG. 3B shows a UI control module 311, a monitoring target registration module 312, an SNMP processing module 313, a status monitoring module 314 and an abnormality notification module 315. FIG. Each module operates on an OS (Operating System) 310, and is implemented by the CPU 221 reading a predetermined program stored in the ROM 222 to the RAM 223 and executing it.

The UI control module 311 displays a UI screen for the user of the PC 100 to perform various input operations, accepts input instructions, and designates the IP address of the network device (the MFP 150 in this case) to be monitored.

The monitoring target registration module 312 uses the SNMP processing module 313 to acquire the configuration information of the network interface of the network device to be monitored, and performs processing for registering it in the monitoring target DB 316 . The general flow for registering the MFP 150 as a monitoring target is as follows 1) to 4.
1) Receiving a user instruction to register the MFP 150 as a monitoring target 2) Accessing the MFP 150 and obtaining MIB information 3) Extracting IfIndex from the MIB information 4) Correlating the ID identifying the MFP 150 with the IfIndex to register the monitoring target Register in DB316

The table shown below is an extraction of a portion of the MIB information acquired in 2) above that plays an important role in this embodiment.

In the case of the above table, in the MFP 150, two wired LAN networks, the wired LAN network by the wired LAN I/F 209 and the usbLAN network by the USB-LAN adapter 210, are established. Then, as a result of setting internal indexes "1" and "2" for each network interface, the value of "IfIndex" is as described above. "IfDescr" corresponds to the name of the network being established. "ifAdminStatus" is information indicating whether the network interface is alive (up/down). "up(1)" indicates normal, and "down(2)" indicates abnormal. Then, the "IfIndex" values ("1" and "2" in this case) extracted from the MIB information are associated with the ID specifying the MFP 150 and registered in the monitoring target DB 316. FIG. At this time, all network interfaces specified by "IfIndex" extracted from the MIB information may be registered as monitoring targets, or only network interfaces corresponding to a predetermined value (for example, "1") may be monitored. You can register as an object.

The SNMP processing module 313 is a module (SNMP manager) that requests various information from the MFP 150 by SNMP. As described above, in this specification, a request made by the SNMP processing module 313 to the MFP 150 is called an "SNMP request".

The status monitoring module 314 uses the SNMP processing module 313 to acquire the network interface status information of the monitoring target device (the MFP 150 in this embodiment) registered in the monitoring target DB 316 after a certain period of time or at a certain time. Then, the acquired status information is analyzed to detect the occurrence of an abnormality in MFP 150 . Details of the detected abnormality are transmitted to the abnormality notification module 315 .

The anomaly notification module 315 notifies the content of the anomaly received from the status monitoring module 314 in a predetermined notification manner, such as display on a monitor or transmission to a designated e-mail address.

(Flow of monitoring process)
Next, a network interface state monitoring process in the MFP 150 executed by the PC 100 will be described with reference to the flowchart of FIG. The symbol "S" at the beginning of each process means step.

When execution of monitoring processing starts, first, in S501, the status monitoring module 314 uses the SNMP processing module 313 to transmit an SNMP request (acquisition request) for acquiring network interface status information from the MFP 150. FIG. At this time, the monitoring target DB 316 is referenced, and the status information about the network interface corresponding to the value of "IfIndex" registered as the monitoring target becomes the acquisition request target. In the case of the table described above, status information about two network interfaces, the wired LAN 209 and the USB-LAN adapter 210, corresponding to "1" and "2" in "IfIndex" is the object of the acquisition request. In the MFP 150 that received the acquisition request, the network control module 301 checks whether there is an internal index corresponding to "IfIndex", and uses the SNMP processing module 303 to send an SNMP response according to the determination result. Specifically, if an internal index having the same value as "IfIndex" exists, the status information of the internal index is obtained and returned to the PC 100, and if not, an error response is returned. An example of status information returned as an SNMP response to the acquisition request is shown below. As shown below, the status information at this time includes at least the "ifAdminStatus" value described above.
Simple Network Management Protocol
version: version-1 (0)
community: public
data: get-response (2)
get-response
request-id: 184
error-status: noError (0)
error-index: 0
variable-bindings: 1 item
IF-MIB::ifAdminStatus.1 (1.3.6.1.2.1.2.2.1.7.1): 1
Object Name: 1.3.6.1.2.1.2.2.1.7.1 (IF-MIB::ifAdminStatus.1)
Value (Integer32): 1

Then, in the PC 100, in subsequent S502, the SNMP processing module 313 determines whether or not the status information has been acquired within a predetermined period of time after making the status information acquisition request. If the acquisition of status information has succeeded, the process proceeds to S503; otherwise, the process proceeds to S504. In S504 in this case, the status monitoring module 314 determines that an abnormality has occurred in the monitored network interface or the MFP 150 itself, and notifies the abnormality notification module 315 of this fact. Then, the abnormality notification module 315 outputs a report notifying of the abnormality.

On the other hand, in S503 when the acquisition of the status information has succeeded, the status monitoring module 314 determines whether it is normal based on the value of "IfAdminStatus" included in the status information. As described above, if it is "up(1)", it is determined to be normal, and if it is "down(2)", it is determined to be abnormal. As a result of the determination, if the value of "IfAdminStatus" is "up(1)", no problem has occurred in the network interface of MFP 150, so this processing ends. On the other hand, if the value of "IfAdminStatus" is "down(2)", it means that a problem has occurred.

The contents of the monitoring process by the PC 100 have been described above. The PC 100 is set to periodically perform this monitoring process.

(Assignment of internal index)
When MFP 150 detects connection of a LAN cable to wired LAN I/F 209 or connection of USB-LAN adapter 120 to USB I/F 210, an internal index is assigned to the recognized network interface. Specifically, a predetermined value is determined by OS 310, and the determined value is set as an internal index for the recognized network interface. The predetermined value determined as the internal index is incremented by "1" each time a network interface is recognized from the initial value "1". In the numbering of the internal index, for example, wired LAN is primary (first order) and USB-LAN is secondary (second order). is normal. For example, when the connection of both the wired LAN cable and the USB-LAN adapter 120 is detected at startup of the MFP 150, the internal index "1 (=initial value)" for the former and the internal index "2 (==initial value)" for the latter Initial value + 1)” will be assigned. Assume that the MFP 150 for which the internal index is set in this way is registered as a monitoring target, and the monitoring processing according to the above-described flow of FIG. 5 has been performed. After that, when the USB-LAN adapter 120 is once removed and the connection is detected again, a new internal index "3 (=initial value + 2)" is assigned to the network interface recognized by the reconnection. Become. In other words, the internal index of the network interface by the USB-LAN adapter 120 changes from the initially assigned "2" to "3". As a result, the PC 100 that monitors the MFP 150 using "IfIndex" having the same value as the initially assigned internal interface value "2" will not be able to monitor the status of the usbLAN network thereafter. Therefore, in this embodiment, the user is prompted to restart the MFP 150 as described later. As a result, the internal index value assigned to the network interface by the USB-LAN adapter 120 is restored to prevent the occurrence of the above problem.

(Flow when connection detection of USB-LAN adapter)
Next, processing executed when the network control module 301 detects connection of the USB-LAN adapter 120 in the MFP 150 in which the use of the USB-LAN adapter 120 is permitted will be described. FIG. 6 is a flowchart showing the flow of processing executed when connection of the USB-LAN adapter 120 is detected according to this embodiment. Note that when the MFP 150 is activated with the USB-LAN adapter 120 connected and the connection of the USB-LAN adapter 120 is detected, normal network connection is established using the driver of the USB-LAN adapter 120. Processing is performed. Further, in this specification, the symbol "S" at the beginning of each process shown in the flow chart means step.

In S601, the setting value DB 304 is referenced to determine whether or not the use of the USB-LAN adapter 120 is permitted. If the setting value DB 304 has a value indicating the "permitted state", the process advances to step S602. At this time, processing such as displaying a message on the operation unit 205 to the effect that the network connection using the USB-LAN adapter 120 is set to "not permitted" may be performed.

In S602, the USB device information of the USB-LAN adapter 120 detected to be connected to the USB I/F 210 is acquired. Here, the USB device information includes, for example, product IDs and vendor IDs. Therefore, the manufacturer, product name, and model name of the connected USB-LAN adapter 120 can be specified from the USB device information.

In subsequent S603, it is determined whether or not the LAN adapter 120 whose connection is detected is of a type that can operate with the MFP 150, using the USB device information acquired in S602. Specifically, it is checked in the USB-LAN DB 305 whether the USB-LAN adapter 120 specified by the obtained USB device information is registered as an operable type. If the USB-LAN adapter 120 detected to be connected is registered in the USB-LAN DB 305, the process proceeds to S604, and if not registered, the process exits.

In S<b>604 , an instruction screen prompting the user to restart the MFP 150 is displayed on the operation unit 205 . FIG. 7 is a diagram showing an example of this restart instruction screen. By checking this screen, the user of MFP 150 can understand that MFP 150 needs to be restarted.

The above is the content of the processing when detecting the connection of the USB-LAN adapter in this embodiment.

<Modification>
In the present embodiment, priority is set according to the type of network interface when issuing internal indexes to recognized network interfaces. Based on these preconditions, a configuration has been described in which the monitored device is restarted to return the internal index to its original state so that a mismatch with the IFIndex handled by the monitoring device does not occur. However, in the case of a monitored device for which priority is not set for the numbering of internal indexes, there is no guarantee that the internal indexes after restarting will be the same as before restarting. In other words, simply restarting the monitored device may cause a mismatch between the internal index assigned by the monitored device and the IFIndex handled by the monitoring device. Therefore, in cases where it is expected that the above-mentioned priority is not set for the numbering of the internal index, notification processing such as sending an e-mail prompting the re-registration of the monitoring target to the administrator etc. It may be performed together in S604. As a result, as in the present embodiment, the internal index assigned by the monitored device and the IFIndex handled by the monitoring device can be matched.

The purpose of prompting the user to restart the monitored device in this embodiment is to prevent status information acquisition using SNMP from becoming impossible. In other words, even if the internal index is changed on the monitored device side by inserting or removing the USB-LAN adapter, the monitored device is placed in a situation where SNMP is not used in the first place, such as being temporarily excluded from the monitoring target. If so, no need to reboot. Therefore, a step of checking the operation setting of the SNMP processing module 303 is added to the above-described flow of FIG. It may be configured to perform network establishment processing. This makes it possible to avoid useless restarts.

As described above, according to the present embodiment, when the connection of the USB-LAN adapter 120 is detected again after the removal of the USB-LAN adapter 120, a notification prompting the user to restart the MFP 150 is issued. In the restarted MFP 150, the recognized network interface is reallocated with an internal index, so the value of the internal index returns to the value before it was removed. As a result, the discrepancy between the IfIndex registered and managed as a monitoring target in the PC 100 and the internal index is resolved, so that the network status can be continuously monitored.

Embodiment 2

In the first embodiment, when reconnection of the USB-LAN adapter 120 is detected, the user is urged to restart the monitored device so that a mismatch between the internal index and the IFIndex does not occur. was allowing it to continue correctly. However, depending on the specifications of the OS of the monitored device, even if the USB-LAN adapter 120 is inserted or removed, there may be cases where the internal index does not change before and after that. In such a case, there will be no mismatch between the internal index after reconnection and the IFIndex registered and managed by the monitoring device, so there is no need to prompt the user to restart the monitored device. On the contrary, it will be a waste of time and effort. Therefore, a mode in consideration of this point will be described as a second embodiment. Note that the description of the contents common to the first embodiment, such as the basic configuration of the system, will be omitted, and the differences will be mainly described below.

FIG. 8 is a flow chart showing the flow of processing executed when the MFP 150 in which the use of the USB-LAN adapter 120 is permitted is detected according to this embodiment.

In S801, the network control module 301 repeats the process of detecting insertion/removal of the USB-LAN adapter 120 at predetermined intervals. When the insertion/removal is detected, it is determined in S802 whether or not the USB-LAN adapter 120 is removed (disconnection of the connected usbLAN network). If disconnection of the network connection due to removal of the USB-LAN adapter 120 is detected, the process proceeds to S803; otherwise (when insertion of the USB-LAN adapter 120 is detected), the process proceeds to S804. Then, in S803, the value of the internal index set for the network interface by the USB-LAN adapter 120 is saved in the RAM 203 or the like as usbLAN network connection history information.

In S804, an internal index is assigned and set for the network interface recognized by inserting the USB-LAN adapter 120. FIG. In the following S805, it is determined whether or not there is usbLAN network connection history information. If there is connection history information (past internal index values are stored), the process proceeds to S806. On the other hand, if the connection history information does not exist, it means that it is the first connection to the usbLAN network after the MFP 150 is activated. Therefore, the problem of mismatch with the IFIndex registered and managed on the PC 100 side cannot occur, and the present processing is terminated as it is.

In S806 when the connection history information exists, it is determined whether or not the value of the internal index assigned in S804 matches the past internal index value saved as the connection history information. As a result of the determination, if the values of both indexes do not match, the process proceeds to S807. If the values of both internal indexes match, it also matches the IFIndex registered and managed on the PC 100 side, so monitoring can be continued as it is. Therefore, in this case, the MFP 150 does not need to be restarted, so the process ends.

In S807, a UI screen prompting restart of the MFP 150 is displayed. This allows the user to restart the MFP 150, return the value of the internal index of the network interface of the USB-LAN adapter 120 whose insertion was detected in S801 to the value before the network connection was disconnected, and monitor the PC 100. state.

The above is the content of the processing when detecting the connection of the USB-LAN adapter in this embodiment. With the above-described processing, the same effect as in the first embodiment can be obtained without forcing the user to uselessly restart the computer.

Embodiment 3

In the first and second embodiments, when the MFP 150 as the monitored device detects reconnection of the USB-LAN adapter, the user is prompted to restart the MFP 150 under certain conditions. These methods have a preventive effect of preventing the PC 100 from becoming incapable of monitoring as a monitoring device, but not all devices existing on the network have a role as a monitoring device. For example, most network devices are client terminals that issue print instructions (transmit print jobs) to the MFP 150, and it is quite conceivable that they do not have a function as a monitoring device. Therefore, if the SNMP request received by the MFP 150 is of a type that does not presuppose the use of IfIndex (for example, a request for checking the progress of a print job, etc.), the MFP 150 does not need to be restarted.

Therefore, a mode in which the user is prompted to restart at the timing when the destination of the SNMP request is found to be a monitoring device that monitors the state of the network interface of the MFP 150 will be described as a third embodiment. Note that the description of the contents common to the first and second embodiments, such as the basic configuration of the system, will be omitted, and the following description will focus on the points of difference.

FIG. 9 is a flow chart showing the flow of processing executed by the MFP 150 upon receiving an SNMP request, according to this embodiment. Execution of this process is based on the premise that the use of the USB-LAN adapter 120 in the MFP 150 is set to a permitted state, and that the network control module 301 has detected the connection of the USB-LAN adapter 120. shall be

When the SNMP processing module 303 receives the SNMP request transmitted from the PC 100, it is determined in S901 whether or not the SNMP request is of a type requiring access to MIB information. If no access to MIB information is required, then there is no adverse effect from changing the internal index. Therefore, in this case, the process proceeds to S906, an SNMP response to the received SNMP request is transmitted, and this process ends. An example of the SNMP response at this time is shown below.
Simple Network Management Protocol
version: version-1 (0)
community: public
data: get-response (2)
get-response
request-id: 184
error-status: noError (0)
error-index: 0
variable-bindings: 1 item
IF-MIB::ifAdminStatus.1 (1.3.6.1.2.1.2.2.1.7.1): 1
Object Name: 1.3.6.1.2.1.2.2.1.7.1 (IF-MIB::ifAdminStatus.1)
Value (Integer32): 1

On the other hand, if the received SNMP request is of a type that requires access to MIB information, the process proceeds to S902.

In S902, the IfIndex specified in the received SNMP request is confirmed, and it is determined whether or not there is a network interface in which the internal index corresponding to the IfIndex is set. If there is a network interface corresponding to the specified IfIndex, the process proceeds to S905 and the value of the IfIndex is stored in the RAM 203. After saving, the process proceeds to S906, and an SNMP response to the received SNMP request is transmitted. Then, after the transmission is completed, this processing ends. On the other hand, if there is no network interface corresponding to the specified IfIndex, the process proceeds to S903.

In S903, it is determined whether or not the same value as the value of IfIndex specified in the received SNMP request is saved in the RAM 203 or not. If the same value as the specified IfIndex value is not saved, it means that the PC 100 has sent an SNMP request using an invalid IfIndex (the network interface corresponding to the specified IfIndex does not exist in the MFP 150). . Therefore, in this case, the process proceeds to S906, and an error response indicating that an invalid IfIndex was specified is transmitted as an SNMP response to the received SNMP request. An example of the SNMP response at this time is shown below. Since there is no MIB information corresponding to the specified IfIndex, the response is "error-status: noSuchName (2)".
Simple Network Management Protocol
version: version-1 (0)
community: public
data: get-response (2)
get-response
request-id: 185
error-status: noSuchName (2)
error-index: 1
variable-bindings: 1 item
IF-MIB::ifAdminStatus.2 (1.3.6.1.2.1.2.2.1.7.2): Value (Null)
Object Name: 1.3.6.1.2.1.2.2.1.7.2 (IF-MIB::ifAdminStatus.2)
Value (Null)

After sending the SNMP response as described above, the process ends. On the other hand, if the same value as the specified IfIndex value is saved, it means that the network interface corresponding to the IfIndex existed in the past and was used for status monitoring of the network interface using SNMP. . At present, it means that a normal SNMP response cannot be returned to an SNMP request sent from the PC 100 as a monitoring device, that is, the PC 100 cannot normally monitor the state of the network interface. . Therefore, in this case, the process advances to step S<b>904 to display a UI screen prompting the restart of the MFP 150 . This causes the user to restart the MFP 150, restore the internal index value of the network interface of the USB-LAN adapter 120 whose insertion has been detected, and enable monitoring in the PC 100. FIG. Then, after the UI screen prompting the restart is displayed, the process advances to S906, and an error response indicating that an invalid IfIndex has been specified is sent as an SNMP response to the received SNMP request, similar to the case of No in S903. , terminate the process.

According to the present embodiment, even if the internal index of the network interface used by the MFP 150 changes, the display prompting the user to restart the MFP 150 is displayed unless SNMP communication actually affected by the change occurs. do not do. This can reduce unnecessary reboots.

(Other examples)
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and one or more processors in the computer of the system or device reads and executes the program. It can also be realized by processing to It can also be implemented by a circuit (for example, ASIC) that implements one or more functions.

Claims (10)

An information processing device having at least one network interface and capable of externally connecting another network interface,
setting means for setting an index for identifying a network interface recognized by the information processing device;
a response means for responding using SNMP to a request from an external device that manages devices on a network using SNMP (Simple Network Management Protocol);
After the other network interface is externally connected and the other network interface becomes available, the other network interface is removed from the information processing device, and the external connection of the other network interface is detected again. and notification means for notifying that the information processing apparatus is restarted according to a predetermined condition when the information processing apparatus is restarted. The predetermined condition is that the SNMP operation setting is enabled in the information processing device, and if the predetermined condition is not satisfied, the external connection of the other network interface is detected again. 2. The information processing apparatus according to claim 1, wherein the notification prompting the restart is not performed even if the restart is performed. storing an index corresponding to the other network interface set by the setting means when it is detected that the other network interface has been removed after the other network interface has become available; further equipped with means,
The predetermined condition includes an index newly set for the other network interface by the setting means when an external connection of the other network interface is detected again, and the other network stored in the storage means. If the index set for the other network interface before the interface is removed does not match the predetermined condition, and if the external connection of the other network interface is detected again. 2. The information processing apparatus according to claim 1, wherein even if there is, the notification prompting the restart is not performed. 2. The information processing apparatus according to claim 1, wherein said notification means further performs notification prompting re-registration regarding management of said information processing apparatus by said SNMP. further comprising a USB (Universal Serial Bus) interface capable of connecting an external device,
5. The network adapter according to any one of claims 1 to 4, wherein the other network interface is a USB connection type network adapter that is connected to the USB interface and recognized as a network interface by the information processing device. The information processing device described. When the restart is performed, the index set by the setting means is initialized,
When the information processing device detects that the at least one network interface and the other network interface are available after the restart, the setting means determines the available state according to a predetermined priority. 6. The information processing apparatus according to any one of claims 1 to 5, wherein an index is set for each network interface that becomes a network interface. 7. The information processing apparatus according to claim 1, wherein said information processing apparatus is a printing apparatus. 7. The information processing apparatus according to claim 1, wherein said information processing apparatus is a scanner device. A control method for an information processing device having at least one network interface and capable of externally connecting another network interface, comprising:
a setting step of setting an index for identifying a network interface recognized by the information processing device;
a response step of responding using SNMP to a request from an external device that manages devices on the network using SNMP (Simple Network Management Protocol);
After the other network interface is externally connected and the other network interface becomes available, the other network interface is removed from the information processing device, and the external connection of the other network interface is detected again. and a notification step of issuing a notification prompting a restart of the information processing device according to a predetermined condition when the restart is performed. A program for causing a computer to execute the control method for the information processing apparatus according to claim 9 .

Images