2.4.8 30XXXXXX-3fXXXXXX

3000b041

E7

dhcp_snoopingd aborted.

The DHCP snooping program (dhcp_snoopingd) was forced to stop.

DHCP snooping detected an anomaly such as a lack of memory, aborted the operation, and forced the program to stop.

[Action]

The DHCP snooping program should restart automatically. If it does not restart or if restarts occur frequently, restart the switch.

R7

dhcp_snoopingd restarted.

The DHCP snooping program (dhcp_snoopingd) has restarted.

This message is displayed when DHCP snooping program is restarted automatically or when it is restarted by restart dhcp snooping command.

[Action]

None.

3000b042

E3

Discard of packets occurred by a reception rate limit of DHCP packets and ARP packets.

Packets were discarded due to the reception rate limit for DHCP packets and ARP packets.

[Action]

None.

3000b043

E3

Failed in binding database generate by binding entry exceeded(<mac address>/<vlan id>/<ip address>).

Generation of the binding database failed because of insufficient database entries.

<mac address>/<vlan id>/<ip address>: DHCP client terminal information

• <mac address>: MAC address

• <vlan id>: VLAN ID

• <ip address>: IP address

[Action]

The capacity limit of the switch was exceeded. Review the system configuration. If this message is displayed due to addition of a static entry, delete the relevant static entry.

3000b044

E3

The binding database can't be restored(<reason>).

The binding database could not be restored.

<reason>: Reason for the failure

• File is not found. (A file was not found.)

• May be broken. (The binding database might be corrupted.)

• The data is not saved. (There is no restorable data.)

[Action]

Check the storage destination of the binding database.

3000b045

E3

The binding database can't be stored(<reason>).

The binding database could not be stored.

<reason>: Reason for the failure

• File is not writing. (Writing to the file is not possible.)

[Action]

Check the storage destination of the binding database.

3000b046

E3

The binding database was restored from <url>.

The binding database could not be restored.

<url>: The binding database being read

• previous process: The process before the restart

• flash: Internal flash memory

• mc: MC

[Action]

None.

3000b047

E3

Failed in source guard setting by DHCP snooping (<mac address>/<vlan id>/<ip address>/<switch no.>/<nif no.>/<port no.>).

The terminal filter setting failed.

<mac address>/<vlan id>/<ip address>/<switch no.>/<nif no.>/<port no.>: Terminal filter setting info

• <mac address>: MAC address

• <vlan id>: VLAN ID

• <ip address>: IP address

• <switch no.>: Switch number

• <nif no.>: NIF number

• <port no.>: Port number

[Action]

The capacity limit of the switch was exceeded. Review the system configuration.

3000b048

E3

Failed in source garde setting of ChGr by DHCP snooping (<mac address>/<vlan id>/<ip address>/<channel group number>).

The terminal filter setting failed.

<mac address>/<vlan id>/<ip address>/<channel group number> Terminal filter setting info

• <mac address>: MAC address

• <vlan id>: VLAN ID

• <ip address>: IP address

• <channel group number>: Channel group number

[Action]

The capacity limit of the switch was exceeded. Review the system configuration.

3e010001

E7

The event management program(eventManagerd) aborted.

The event management program (eventManagerd) was forcibly terminated.

[Action]

The event management program restarts automatically. If the event management program does not restart or restarts frequently, restart the device.

R7

The event management program(eventManagerd) restarted.

The event management program (eventManagerd) has restarted.

This message is displayed when the event management program restarts automatically or when a restart is requested by restart event-manager command.

[Action]

None.

3e010003

E3

One or more event reports were discarded by the detector. (discard point = <point name>)

An event notification was discarded by the monitoring program. After this message is output, this message is not output for the same discard point until 15 minutes have elapsed.

<point name> Disposal point-name

• system message queue

• high priority queue for script

• normal priority queue for script

• low priority queue for script

• last priority queue for script

• high priority queue for applet

• normal priority queue for applet

• low priority queue for applet

• last priority queue for applet

[Action]

Take the following actions for each disposal point.

• system message queue

  Review the monitoring conditions for operation message monitoring as necessary. Even if information that is not monitored is discarded, it is output.

• high priority queue for script, normal priority queue for script, low priority queue for script, last priority queue for script, high priority queue for applet, normal priority queue for applet, low priority queue for applet, last priority queue for applet

  Review the notification priority setting for each monitor event as necessary.

After this message is output, this message is not output for the same discard point until 15 minutes have elapsed.

3e010004

E3

One or more event reports were discarded by the script functionality. (name = <name>, PID = <pid>)

The script discarded the event notification.

<name> Module name of the script that destroyed the event or file name (if these names exceed 100 characters, the first 100 characters are displayed)

<pid> Process ID of the script that discarded the event

[Action]

Review the receive processing of the event monitor of the applicable script.

3e020001

E7

The script management program(scriptManagerd) aborted.

The script control program (scriptManagerd) was forcibly terminated.

[Action]

The script management program automatically restarts. If the script management program does not restart or restarts frequently, restart the device.

R7

The script management program(scriptManagerd) restarted.

The script control program (scriptManagerd) has restarted.

This message is displayed when the script control program restarts automatically or when a restart is requested by restart script-manager command.

[Action]

None.

3e020003

E3

The resident script started. (script id = <id>)

A resident script was started.

<id>: The corresponding resident scripting ID

[Action]

None.

3e020004

E3

The resident script ended. (script id = <id>)

The resident script terminated.

<id>: The corresponding resident scripting ID

[Action]

None.

3e020005

E3

The resident script could not be started. (script id = <id>)

The resident script could not be started.

<id>: The corresponding resident scripting ID

[Action]

Make sure that the appropriate script file is installed.

3e020006

E3

The starting of the resident script was suppressed. (script id = <id>)

Startup was suppressed because the corresponding resident script restarted repeatedly.

<id>: The corresponding resident scripting ID

[Action]

Check whether there is any problem in the script file.

3e020009

E3

The applet action script could not be started. (applet name = <applet name>, sequence = <sequence>)

The applet function action script could not be started. After this message is output, this message is not output until 15 minutes have elapsed or the applicable action definition has been changed.

<applet name> appropriate applet-name

<sequence> appropriate action sequence number

[Action]

Make sure that the appropriate script file is installed.

3f000001

E3

Loading MC-Configuration failed. (reason = <reason>)

Failed to read MC data when starting the switch in MC operation mode.

<reason>: Reason for the failure

• MC is not inserted.(MC is not installed.)

• File read failed (Failed to read the file.)

[Action]

Confirm that MC is accessed according to the reason for the failure.

3f000002

E3

Changes detected on MC-Configuration. Restarting.

The system is restarted by MC operation-mode processing.

[Action]

None.

3f000011

E3

Updating MC-Configuration is completed.

Updating of the operating software and device data to MC is completed.

[Action]

None.

3f000012

E3

Updating MC-Configuration failed. (reason = <reason>)

Updating of running software and device data to MC failed.

<reason>: Reason for the failure

• Not enough space on MC.(There is not enough space on Not enough space on MC.)

• File write failed. (Failed to write the file.)

• MC is not inserted.(MC is not installed.)

• MC is busy. (Other processes are accessing MC.) Please re-execute after a while.

• Not start-up from flash memory(primary). (It is not normally started from the on-chip flash memory.)

[Action]

Confirm that MC is accessed according to the reason for the failure.

3f000101

E3

Zero-touch-provisioning started.

Start of the device in Zero Touch Provisioning operation mode has started.

[Action]

None.

3f000102

E3

Changes detected on zero-touch-provisioning. Restarting.

Restarts by zero-touch provisioning operation mode processing.

[Action]

None.

3f000103

E3

System started with zero-touch-provisioning.

Started in zero-touch provisioning operation mode.

[Action]

None.

3f000104

E3

System started without zero-touch-provisioning. (reason = <reason>)

Started in normal mode.

<reason> Normal-mode startup reason

• No configuration. (Zero-touch provisioning is disabled.)

• Link down. (The zero-touch provisioning interface is DOWN.)

• Can't communicate with DHCP server.(DHCP servers are not responding.)

• Invalid information.(DHCP servers is invalid.)

• File get failed. (File retrieval failed.)

• File read failed (Failed to read the file.)

• File write failed. (Failed to write the file.)

[Action]

• When the failure reason is "Link down."

  Review the zero-touch provisioning interface.

• When the failure reason is "Can't communicate with DHCP server." or "Invalid information."

  Review the settings of DHCP servers.

• When the failure reason is "File get failed."

  Review the file server settings and the available space on the device.

• When the failure reason is "File read failed." or "File write failed."

  Review the free space of the batch file and the device.

3f000201

E3

System zero-touch-provisioning is disabled, because mc-configuration has been enabled.

Zero-touch provisioning of the exclusive function was disabled because MC operation mode was enabled.

[Action]

None.

3f000202

E3

System zero-touch-provisioning is enabled, because mc-configuration has been disabled.

Zero-touch provisioning of the exclusive function was enabled because MC operation mode was disabled.

[Action]

None.