Message and Log Reference


2.4.8 30XXXXXX-3eXXXXXX

This section describes operation messages in which the two most significant digits of the message identifier are 3e from 30.

Table 2-11: Operation messages for event location SOFTWARE (30XXXXXX)

Message

ID

Event

Level

Message text

Content and response

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>/<nif no.>/<port no.>).

The terminal filter setting failed.

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

  • <mac address>: MAC address

  • <vlan id>: VLAN ID

  • <ip address>: IP address

  • <nif no.>: NIF number

  • <port no.>: Port number

[Action]

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

32001001

E7

trackobjd aborted.

The track object program (trackobjd) was forced to stop.

[Action]

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

R7

trackobjd restarted.

The track object program (trackobjd) has restarted.

This message is displayed when the Track Object Program is restarted automatically or when a restart is requested by restart track-object command.

[Action]

None.

34000010

E9

Switch <switch no.> restarted because stackd aborted.

The switch was restarted because the stack management program (stackd) was forcibly ended.

<switch no.>: Switch number

Note, however, that 0 is displayed if the switch number cannot be acquired.

[Action]

If this message is repeatedly output, replace the device.

36000001

E7

The BFD program (bfdd) aborted.

BFD programming (bfdd) was forced to stop.

[Action]

BFD programme will restart automatically. If BFD program does not restart, or if restarting occurs frequently, restart the equipment.

R7

The BFD program (bfdd) restarted.

BFD programme (bfdd) has restarted.

This message is displayed when BFD program restarts automatically or when a restart is requested by restart bfd command.

[Action]

None.

3a000001

E7

overlayd aborted.

The Overlay (VXLAN) program (vxland) was forced to stop. Operation was aborted and forced to stop because an error, such as a memory area shortage, was detected.

[Action]

The overlay program will restart automatically. If the overlay program does not restart, or if the restart occurs frequently, restart the equipment.

R7

overlayd restarted.

The overlay (VXLAN) program (vxland) has restarted.

This message is displayed when the overlay program restarts automatically or when a restart is requested by restart overlay commandI will.

[Action]

None.

3a000003

E4

The VXLAN tunnel entry can't be registered at hardware tables.

VXLAN tunnel entry for VXLAN feature could not be configured in the hardware table.

[Action]

Review the capacity limit.

However, depending on the hardware specification, the setting to the maximum of the capacity limit might not be available.

3a000012

E4

The VXLAN Layer2 Nexthop entry can't be registered at hardware tables.

Nexthop entry for a VXLAN Network port configured for link aggregation could not be set in the hardware table.

[Action]

Review the configuration so that it is within the capacity limit.

3b000001

E7

ptpd aborted.

PTP programming (ptpd) was forced to stop.

[Action]

PTP programme will restart automatically. If PTP program does not restart, or if restarting occurs frequently, restart the equipment.

R7

ptpd restarted.

PTP programme (ptpd) has restarted.

This message is displayed when PTP program restarts automatically.

[Action]

None.

3c000001

E4

The flow rate-alarm state changed from conform to exceed. ( interface = <inteface name>, QoS flow list = <qos flow list name>, sequence = <sequence> )

The bandwidth status of QoS flow entry changed from the bandwidth compliance status to the bandwidth violation status.

<interface name>: Interface name

<qos flow list name> QoS flow list name

<sequence> Sequence number

[Action]

None.

3c000002

E4

The flow rate-alarm state changed from exceed to conform. ( interface = <inteface name>, QoS flow list = <qos flow list name>, sequence = <sequence> )

The bandwidth status of QoS flow entry changed from the bandwidth violation status to the bandwidth compliance status.

<interface name>: Interface name

<qos flow list name> QoS flow list name

<sequence> Sequence number

[Action]

None.

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.

Module or filename of the script that discarded the <name> event. (If these names exceed 100 characters, the first 100 characters are displayed.)

Processing ID of scripts that discarded <pid> events

[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.

3e020007

E3

The script files of the master switch do not match those of other switches.

The script file does not match on the master switch and on the other member switches.

[Action]

Synchronize the script file with install script sync command.

3e020008

E3

The script file could not be synchronized. (file name = <file name>)

The script file could not be synchronized on the master switch and other member switches.

<file name> script file name

[Action]

Use show logging command to check the log. If another error has occurred, take the appropriate action. If this is not an issue, use install script sync command to synchronize 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.