PF6800 Ver. 6.0 Log Message Reference · PFC.ifm IFM PFC interface management function PFC.pfvlan...

PF6800 Ver. 6.0Log Message Reference

PFC00EG0600-01

CopyrightsInformation in this manual may not include all information disclosed by NEC Corporation or mayuse different expressions than information disclosed by other means. Also, this information is subjectto revision or removal without prior notice.

Although every effort has been made to ensure accuracy in producing this manual, NEC Corporationdoes not guarantee the accuracy or applicability of the information contained herein. In addition,NEC Corporation is not liable for any damages that may occur due to the use or non-use of thisinformation by any party. Translation or reproduction of all or part of this document by any meansincluding electronic, mechanical, or recording means is prohibited unless authorized in writing byNEC Corporation.

Copyright © NEC Corporation 2011-2014

Trademarks• The NEC logo is a registered trademark or a trademark of NEC Corporation in Japan and other

countries.

• Microsoft and the Microsoft logo are registered trademarks of Microsoft Corporation (USA).

• Windows is a registered trademark or a trademark of Microsoft Corporation in the United Statesand/or other countries.

• Linux is a registered trademark or trademark of Linus Torvalds in Japan and other countries.

• Other company names and product names are trademarks or registered trademarks of theirrespective companies. Trademark symbols such as TM or ® are not indicated in the main text.

i

IntroductionThank you for purchasing the PF6800 (referred to as PFC). The PF6800 is a path control device usedfor centralized management of networks, and conforms to OpenFlow 1.0/1.3.

Unlike conventional switch products, the packet transfer and path control functions are separated toenable a greater flexibility in the network configuration.

To take full advantage of the functions of this product, please read this manual carefully and becomefully familiar with the handling of this device.

About this ManualThis manual describes the messages and logs output by the PF6800.

In the description, OFS refers to OpenFlow Switch, and PFS refers to PF5xxx Switch.

The only OFS guaranteed to operate with this product is the PFS.

SymbolsIn this manual, the following three types of symbols are used. These symbols and their meanings areimportant for proper handling of the PFC.

ImportantIndicates items for which special care should be taken to follow regarding handling of equipment andsoftware operation.

RememberPoints that should be checked when operating devices or software.

TipHelpful, good-to-know information

Structure of this ManualThis manual has two chapters and the index. The following explanations are provided in these parts.

"Chapter 1. Operation Messages and Logs (page 1)"This chapter describes the messages and logs output when PFC is in operation.

"Chapter 2. Alarm Messages (page 56)"This chapter describes the alarm messages and traps output when PFC is in operation.

INDEXThe index of this manual.

ii

DisclaimerUnless explicitly set forth in a license agreement, NEC Corporation makes no explicit or implicitguarantees regarding this product and the related documentation, including its commercial use orfitness for a particular purpose, and disclaims all liability pertaining to its handling, use, or attendanttrade practices.

AcknowledgmentWe would like to express our thanks to Mr. Linus Torvalds and all the people involved in Linuxdevelopment.

iii

ContentsChapter 1. Operation Messages and Logs ................................................................................. 1

1.1 Operation Logs .....................................................................................................................1

1.2 Logs Output by the ClusterStateManager ..............................................................................2

1.3 Logs Output by SDB...........................................................................................................13

1.4 Logs Output by NodeManager ............................................................................................16

1.5 Logs Output by the Operation Manager ..............................................................................20

1.6 Logs Output by the Policy Manager ....................................................................................24

1.7 Logs Output by the VTN Controller....................................................................................27

1.8 Logs Output by the Physical Network .................................................................................28

1.9 Logs Output by the PFC Core Network...............................................................................45

1.10 Logs Output by the CLI ....................................................................................................48

1.11 Logs Output by the License Manager ................................................................................49

1.12 Logs Output by the Traffic Monitor ..................................................................................50

1.13 Logs Output by Automatic VLAN Setting ........................................................................51

1.14 Logs Output by the Dual Cluster Management..................................................................53

Chapter 2. Alarm Messages ...................................................................................................... 562.1 Alarms and Traps ................................................................................................................56

Index............................................................................................................................................. 83

iv

Chapter 1. Operation Messages and LogsThis chapter describes the messages and logs output during operation.

1.1 Operation LogsOperation logs are the PFC server software logs that are output in syslog format and are in achronological sequence.

TipOperation logs are output to the following files:/var/log/messages* : Operation logs including system information

/var/log/pfc_messages* : Operation logs of PFC server software

For how to display operation logs on a PFC shell, refer to show log syslog in the Command Reference.

All of the display items based on the actual output results are explained below.

Apr 15 22:42:45 pfc PFC.ofcm: Starting audit of OFS 0000-0000-0000-0105.1 2 3 4

1. Apr 15 22:42:45: Log output date and time (Format: Month Day Hour:Minute:Second)

2. pfc: Host name

3. PFC.ofcm: Identifier

Unique identifier for the components in the output log. The identifiers of the PFC serversoftware are as follows:

Table 1-1 List of Identifiers

Identifier Component name Description

PFC.csm ClusterStateManager Cluster state management function

PFC.sdb SDB Data synchronization function in a redundantconfiguration

PFC.mgmt Operation Manager Operation management function of the PFCserver

PFC.nomg NodeManager Control function of PFC applications,resources, and alarms

PFC.pom Policy Manager Network policy management function

PFC.vtnctl VTN Control Virtual tenant network control function

PFC.pthctl Path Control Network path control function

PFC.ofcm OFCM OFS connection management function

PFC.pfcd PFC Core Network PFC core network control function

PFC.pfcsh.conf CLI Command line interface function

PFC.licd License Manager License management function

PFC.trmon Traffic Monitor Network traffic monitor function

Chapter 1. Operation Messages and Logs

1

Identifier Component name Description

PFC.ifm IFM PFC interface management function

PFC.pfvlan Automatic VLAN setting Automatic VLAN setting function

PFC.dcsd Dual cluster management Dual cluster function

4. Starting audit of OFS 0000-0000-0000-0105: Output contentsFrom "1.2 Logs Output by the ClusterStateManager (page 2)" , the output contents of 4 areexplained with the identifiers from 3 as a reference. Also, the log levels are syslog compliant, and areexplained below.

Table 1-2 List of Log Levels

Level Meaning

High↑

↓Low

ALERT Failures which cause stopping and rebooting of the PFC Software.Important failures which must immediately be handled by maintenancestaff.

CRIT Failures connected to stopping and rebooting of the PFC Software,while the PFC Software is in continuous operation and not stopped.Important failures which must immediately be handled by maintenancestaff.

ERR PFC Software Failures.Important failures for maintenance staff to recognize.

WARNING Failures on the network of devices which manage the PFC.Important failures for maintenance staff to recognize.

NOTICE Information necessary the security of the PFC if the state of the PFChas changed after recovering from a failure, and other importantinformation.Information which needs maintenance staff to handle and recognize.

INFO PFC Operating Information which needs maintenance staff to handleand recognize.

TipLogs of INFO and higher levels are output by default.For details about how to change the log level, refer to syslog severity in the Command Reference.

1.2 Logs Output by the ClusterStateManagerPFC ClusterStateManager already running

Level:NOTICE

Identifier:PFC.csm


2

[Explanation]An attempt was made to start ClusterStateManager when ClusterStateManager was alreadyrunning.

[Action]Unnecessary

Starting PFC ClusterStateManager

Level:NOTICE

Identifier:PFC.csm

[Explanation]ClusterStateManager is being started.

[Action]Unnecessary

Shutting down PFC ClusterStateManager

Level:NOTICE

Identifier:PFC.csm

[Explanation]ClusterStateManager is being shut down.

[Action]Unnecessary

PFC ClusterStateManager not running

Level:NOTICE

Identifier:PFC.csm

[Explanation]An attempt was made to stop ClusterStateManager when ClusterStateManager was not running.


3

[Action]Unnecessary

PFC ClusterStateManager stopped

Level:NOTICE

Identifier:PFC.csm

[Explanation]ClusterStateManager has shut down.

[Action]Unnecessary

pfccsmmonitor process started.

Level:INFO

Identifier:PFC.csm

[Explanation]The ClusterStateManager monitor process has started.

[Action]Unnecessary

pfccsmmonitor process terminated.

Level:INFO

Identifier:PFC.csm

[Explanation]The ClusterStateManager monitor process has stopped.

[Action]Unnecessary

pfccsmd process started.


4

Level:INFO

Identifier:PFC.csm

[Explanation]The ClusterStateManager daemon has started.

[Action]Unnecessary

pfccsmd process terminated.(signal=<Signal No.>)

Level:INFO

Identifier:PFC.csm

[Explanation]The ClusterStateManager daemon has stopped.

[Action]Unnecessary

Cluster switchover had been started due to request.

Level:INFO

Identifier:PFC.csm

[Explanation]Cluster switchover has been started by execution of the pfc_switch_cluster command.

[Action]Unnecessary

Split brain detected.

Level:ERR


5

Identifier:PFC.csm

[Explanation]Split-brain syndrome has been detected.

[Action]If the server does not automatically restart, or if the cluster does not start correctly after theserver has restarted, take action according to Cluster Trouble in the Troubleshooting Guide.

Failover resource exists in opposite node, and connection to opposite node is not established.

Level:ERR

Identifier:PFC.csm

[Explanation]A CLUSTERPRO failover resource has been detected on the opposite node, and connection tothe opposite node cannot be established.


When cluster state of local node is FAILURE, failover resource has moved to local node.

Level:ERR

Identifier:PFC.csm

[Explanation]A CLUSTERPRO failover resource was moved to the local node while the cluster state of thelocal node was FAILURE.


When cluster state of local node is ACT or ACT_TRANS, failover resource has moved to opposite node.

Level:ERR


6

Identifier:PFC.csm

[Explanation]A CLUSTERPRO failover resource was moved to the opposite node while the cluster state ofthe local node was ACT or ACT_TRANS.


CLUSTERPRO is not running.

Level:ERR

Identifier:PFC.csm

[Explanation]It was detected that CLUSTERPRO is not running.

[Action]Contact the maintenance and service company.

cluster state of local node transited from <state before transfer> to <state after transit>.

Level:NOTICE

Identifier:PFC.csm

[Explanation]The cluster state of the local node has changed from <state before transfer> to <stateafter transit>. The following lists the character strings displayed before and after statetransition, together with their meanings:

INIT: Initial state

INIT(AP_STARTED): Initial state (where the SDB and other components start up)

ACT_TRANS: Transitioning to active state

ACT: Active state

SBY_TRANS: Transitioning to standby state

SBY: Standby state

FAILURE: Failure has occurred


7

[Action]Unnecessary

pfccsmd abnormally terminated.

Level:CRIT

Identifier:PFC.csm

[Explanation]The ClusterStateManager daemon has terminated due to an error.


CSM daemon is not started.

Level:ERR

Identifier:PFC.csm

[Explanation]ClusterStateManager could not start within the waiting time for startup.


This node isn't eligible to become ACT because redundancy configuration is not completed yet.

Level:ERR

Identifier:PFC.csm

[Explanation]Even if another node is set as the Master by the pfc_setup_redundancy command, this nodecannot become the active node because it is not declared as a Follower.


8

[Action]Execute the pfc_setup_redundancy command on the appropriate node. For details aboutpfc_setup_redundancy, "Master", and "Follower", refer to pfc_setup_redundancy in theCommand Reference.

This node isn't eligible to become ACT because redundancy configuration is in progress yet.

Level:NOTICE

Identifier:PFC.csm

[Explanation]Even if a redundancy configuration has been specified for this node by the pfc_setup_redundancy command, this node cannot become the active node because the processing for changingthe configuration by the component on the node is not complete.

[Action]Prior to the configuration change processing being completed, ensure that this node runs whilethe active node is running, because this node must run as a standby node. Check if clusterswitchover is enabled by using the pfc_show_cluster_status command to confirmcompletion of the configuration change processing.For details about pfc_show_cluster_status and pfc_setup_redundancy, refer to Command Reference.

This node isn't eligible to become SBY because master node exists. Please execute redundancy configuration.

Level:ERR

Identifier:PFC.csm

[Explanation]Even if another node is set as the Master by the pfc_setup_redundancy command, that nodecannot become the standby node because it is not declared as a Follower.

[Action]Execute the pfc_setup_redundancy command on the appropriate node. For details about pfc_setup_redundancy refer to pfc_setup_redundancy in the Command Reference.

This node isn't eligible to become SBY because currently single node configuration. Please execute redundancy configuration.

Level:ERR


9

Identifier:PFC.csm

[Explanation]This node cannot become the standby node because the redundant configuration has beenspecified for a single node.

[Action]Execute the pfc_setup_redundancy command on the appropriate node. For details about pfc_setup_redundancy refer to pfc_setup_redundancy in the Command Reference.

This node isn't eligible to become SBY because redundancy configuration is not yet done. Please execute redundancy configuration.

Level:ERR

Identifier:PFC.csm

[Explanation]This node cannot become the standby node because the redundant configuration has not beenspecified.

[Action]Execute the pfc_setup_redundancy command on the appropriate node. For details about pfc_setup_redundancy, "Master", and "Follower", refer to pfc_setup_redundancy in theCommand Reference.

Mirror break was detected. Please recover mirror disk condition.

Level:ERR

Identifier:PFC.csm

[Explanation]A mirror break has been detected.

[Action]Recover from the mirror break state (known as "mirror recovery") according to Cluster Troublein the Troubleshooting Guide.

SBY node is stopped because the PFC version is different and incompatible combination between cluster nodes.


10

Level:ERR

Identifier:PFC.csm

[Explanation]The standby node is stopped because the PFC versions differ between cluster nodes and are anincompatible combination.

[Action]The standby cluster node is stopped. Install a PFC of the same version as the active cluster nodeto the stopped node. Refer to the Configuration Guide for PFC installation.

Cluster switchover had succeeded.

Level:NOTICE

Identifier:PFC.csm

[Explanation]Cluster switchover started by execution of the pfc_switch_cluster command wassuccessful.

[Action]Unnecessary

Cluster switchover had been failed.

Level:NOTICE

Identifier:PFC.csm

[Explanation]Cluster switchover started by execution of the pfc_switch_cluster command failed.

[Action]A node that is normal switched over to the active node. Check which node switched to the activenode by using the pfc_show_cluster_status command. For details about pfc_show_cluster_status and pfc_switch_cluster, refer to the Command Reference.

Software upgrade finalization had been started due to request.


11

Level:INFO

Identifier:PFC.csm

[Explanation]Software upgrade finalization has been started by executing the pfc_upgrade command.

[Action]Unnecessary

Software upgrade finalization of local node had completed.

Level:NOTICE

Identifier:PFC.csm

[Explanation]Software upgrade finalization on the local node is complete.

[Action]Unnecessary

Couldn't resume cluster, please stop the cluster with pfc_stop_cluster at opposite node.

Level:ERR

Identifier:PFC.csm

[Explanation]The standby node was restarted while the cluster setting was being applied to the active nodewithout stopping the cluster on the node. This caused the suspended redundancy monitoringfunction not to restart.

[Action]Stop the cluster of the opposite node by using the pfc_stop_cluster command. Then, theredundancy monitoring function automatically starts. For details about pfc_stop_cluster,refer to the Command Reference.

Couldn't resume cluster, so will stop cluster at own node.


12

Level:ERR

Identifier:PFC.csm

[Explanation]The suspended state of the redundancy monitoring function as continued for a long time becausethe cluster at the opposite node was not stopped by using the pfc_stop_cluster command.The cluster at the own node is stopped because the state of the redundancy function is notexpected to be recovered. However, before this message is output, activating FIP fails on theopposite node fails to activate FIP and the cluster is stopped. The event indicated by thismessage does not basically occur.

[Action]Make sure that the cluster at the own node stopped, and then restart the own node.

1.3 Logs Output by SDBAbnormally terminated

Level:ALERT

Identifier:PFC.sdb

[Explanation]SDB has terminated due to an error.


Starting PFC SDB

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB is being started.


13

[Action]Unnecessary

PFC SDB already running

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB is already running.

[Action]Unnecessary

PFC SDB started

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB has started.

[Action]Unnecessary

Can't start PFC SDB because SDB initialization is failed

Level:ALERT

Identifier:PFC.sdb

[Explanation]SDB could not be started because initialization failed.


Shutting down PFC SDB


14

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB is being shut down.

[Action]Unnecessary

PFC SDB not running

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB is not running.

[Action]Unnecessary

PFC SDB stopped

Level:NOTICE

Identifier:PFC.sdb

[Explanation]SDB has stopped.

[Action]Unnecessary

monitor: pfcsdbd aborted.

Level:ALERT


15

Identifier:PFC.sdb

[Explanation]Abnormal termination of SDB has been detected.


monitor: pfcsdbd stalled.

Level:ALERT

Identifier:PFC.sdb

[Explanation]An SDB stall has been detected.


1.4 Logs Output by NodeManagerStarting PFC NodeManager

Level:NOTICE

Identifier:PFC.nomg

[Explanation]NodeManager is being started.

[Action]Unnecessary

Can not start PFC NodeManager because cluster status is xxx

Level:ALERT


16

Identifier:PFC.nomg

[Explanation]Cannot start the NodeManager daemon because the cluster status is abnormal.

[Action]Reboot the system.

Shutting down PFC NodeManager

Level:NOTICE

Identifier:PFC.nomg

[Explanation]NodeManager is being shut down.

[Action]Unnecessary

PFC NodeManager stopped

Level:NOTICE

Identifier:PFC.nomg

[Explanation]NodeManager has stopped.

[Action]Unnecessary

PFC NodeManager already running

Level:NOTICE

Identifier:PFC.nomg


17

[Explanation]The NodeManager boot processing was executed while NodeManager was running.

[Action]Unnecessary

Health check timeout To Node Management Daemon

Level:ALERT

Identifier:PFC.nomg

[Explanation]NodeManager has stopped responding.


Health check timeout To Node Management Monitor

Level:ERR

Identifier:PFC.nomg

[Explanation]The NodeManager monitor process has stopped responding.


Restarting PFC NodeManager because of the restart level 2

Level:ALERT

Identifier:PFC.nomg

[Explanation]The PFC application is being restarted because it has entered an abnormal state.


18


Rebooting PFC NodeManager because of the restart level 3

Level:ALERT

Identifier:PFC.nomg

[Explanation]The PFC server is being restarted because it has entered an abnormal state.


Stopping PFC NodeManager because of the restart level 4

Level:ALERT

Identifier:PFC.nomg

[Explanation]The PFC application is being stopped because it has entered an abnormal state.


Failed to initialize pfc_nomg_check_starting (xxx)

Level:ALERT

Identifier:PFC.nomg

[Explanation]Failed to initialize the NodeManager monitor process.


The start confirmation of NodeManager did the time-out


19

Level:ALERT

Identifier:PFC.nomg

[Explanation]Could not confirm that NodeManager had started after the system restart.


Can not start PFC NodeManager because pfcsdbd is not running

Level:ALERT

Identifier:PFC.nomg

[Explanation]NodeManager could not be started because SDB is not running.


1.5 Logs Output by the Operation ManagerSending trap failed. (xxx)

Level:ERR

Identifier:PFC.mgmt

[Explanation]Failed to send trap.

[Action]Reboot the PFC server. Contact the maintenance and service company if this happens again.

Starting PFC Management System Monitor


20

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]The link status monitor function is being started.

[Action]Unnecessary

Shutting down PFC Management System Monitor

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]The link status monitor function is being stopped.

[Action]Unnecessary

PFC Management System Monitor is already running

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]Processing to start up the link status monitor function was executed while the link status monitorfunction was running.

[Action]Unnecessary

PFC Management System Monitor is not running

Level:NOTICE


21

Identifier:PFC.mgmt

[Explanation]The link status monitor function is not running.

[Action]Unnecessary

PFC Management System Monitor stopped

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]The link status monitor function has stopped.

[Action]Unnecessary

xxx NIC Link is Up.

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]The NIC xxx link is up.

[Action]Unnecessary

xxx NIC Link is Down.

Level:WARNING

Identifier:PFC.mgmt


22

[Explanation]The NIC xxx link is down.

[Action]Confirm that the LAN cable is correctly connected.

Waiting link event failed. (xxx)

Level:ERR

Identifier:PFC.mgmt

[Explanation]Monitoring the link status failed.

[Action]Contact the maintenance and service company if this happens repeatedly.

Error logging is stopped until errors recover.

Level:ERR

Identifier:PFC.mgmt

[Explanation]Output of errors is stopped until the error in the link status monitor function recovers.

[Action]Reboot the PFC server. Contact the maintenance and service company if this happens again.

Link status monitoring recovered.

Level:NOTICE

Identifier:PFC.mgmt

[Explanation]The link status monitor function has been recovered.


23

[Action]Unnecessary

ntpd restarted.

Level:INFO

Identifier:PFC.mgmt

[Explanation]ntpd was restarted because the NTP settings were changed.

[Action]Unnecessary

1.6 Logs Output by the Policy ManagerThe state of the network-monitor-group <group name> has changed fault.

Level:WARNING

Identifier:PFC.pom

[Explanation]The system has switched to fail status as there was no response from any of the monitored hostsin the network monitor group <group name>.

The flow filter entries set by <group name> will be disabled.

The routing table for the vRouter set by <group name> will be disabled.

[Action]Investigate what has caused the monitored hosts to not respond, and perform recovery if there isa failure.

The state of the network-monitor-group <group name> was recovered.

Level:NOTICE

Identifier:PFC.pom


24

[Explanation]The system has switched to recovery status as there was a response from the monitored hostsspecified by the network monitor group <group name>.

The flow filter entries set by <group name> will be enabled.

The routing table for the vRouter set by <group name> will be enabled.

[Action]Unnecessary

The state of the network-monitor-group <group name> was canceled.

Level:NOTICE

Identifier:PFC.pom

[Explanation]The network monitor group <group name> in the fail state has been disabled by the no enable command.

The flow filter entries set by <group name> will be enabled.

The routing table for the vRouter set by <group name> will be enabled.

[Action]To re-enable the disabled network monitor group <group name>, execute the enablecommand.

Failure in a setup of Policer by OFS resource full. ofs=<DPID> port=<PortName> policer=<VTN Name>,<vNode Name>,<SeqNum>

Level:WARNING

Identifier:PFC.pom

[Explanation]The Policer setting (the setting in which the sequence number <SeqNum> is set for <VTN Name><vNode Name> (for a Policer set to VTN, vNode Name is an empty string)) failed to be inputfor the physical port name <PortName> of the OFS with a DPID of <DPID> due to insufficientOFS resources.

[Action]There is a possibility of a failure in the architecture of the system configuration. Check theconfiguration of the entire network.


25

Failed Policer(Resource full) has been deleted. ofs=<DPID> port=<PortName> policer=<VTN Name>,<vNode Name>,<SeqNum>

Level:NOTICE

Identifier:PFC.pom

[Explanation]The Policer setting (the setting of the entry whose sequence number <SeqNum> is set for <VTNName><vNode Name> (for a Policer set to VTN, vNode Name is an empty string)) failed due toinsufficient resources for the physical port name <PortName> of the OFS with a DPID of <DPID> has been deleted.

[Action]Unnecessary

Failure in a setup of Policer. ofs=<DPID> port=<PortName> policer=<VTN Name>,<vNode Name>,<SeqNum>

Level:WARNING

Identifier:PFC.pom

[Explanation]The Policer setting (the setting of the entry whose sequence number <SeqNum> is set for <VTNName><vNode Name> (for a Policer set to VTN, vNode Name is empty string)) failed to beinput for the physical port name <PortName> of the OFS with a DPID of <DPID>.

[Action]Delete the corresponding policing map setting by using the PFC shell, and then perform thesetting again.

Failed Policer(Setting failure) has been deleted. ofs=<DPID> port=<PortName> policer=<VTN Name>,<vNode Name>,<SeqNum>

Level:NOTICE

Identifier:PFC.pom


26

[Explanation]The Policer setting (the setting of the entry whose sequence number <SeqNum> is set for <VTNName><vNode Name> (for a Policer set to VTN, vNode Name is empty string)) failed to be setfor the physical port name <PortName> of the OFS with a DPID of <DPID> has been deleted.

[Action]Unnecessary

1.7 Logs Output by the VTN Controllervtnctl initialize start.

Level:INFO

Identifier:PFC.vtnctl

[Explanation]Initialization of the vtnctl module has started.

[Action]Unnecessary

vtnctl started.

Level:INFO


[Explanation]The vtnctl module has started.

[Action]Unnecessary

vtnctl finalize start.

Level:INFO



27

[Explanation]Termination of the vtnctl module has started.

[Action]Unnecessary

vtnctl finalize stopped.

Level:INFO


[Explanation]The vtnctl module has stopped.

[Action]Unnecessary

Failed to synchronize.

Level:ALERT


[Explanation]Synchronization between cluster nodes has failed.


1.8 Logs Output by the Physical NetworkOFS nnnn-nnnn-nnnn-nnnn has connected.

Level:NOTICE

Identifier:PFC.ofcm


28

[Explanation]An OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been connected to the PFC server.

[Action]Unnecessary

OFS nnnn-nnnn-nnnn-nnnn has disconnected.

Level:WARNING

Identifier:PFC.ofcm

[Explanation]The OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been disconnected from the PFC server.

[Action]If this disconnection is not intended, check the connection between the OFS and the PFC server.

ofcm has started.

Level:INFO

Identifier:PFC.ofcm

[Explanation]The OFCM module has started.

[Action]Unnecessary

ofcm has stopped.

Level:INFO

Identifier:PFC.ofcm

[Explanation]The OFCM module has stopped.


29

[Action]Unnecessary

Starting audit of OFS nnnn-nnnn-nnnn-nnnn.

Level:NOTICE

Identifier:PFC.ofcm

[Explanation]An audit of the OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been started.

[Action]Unnecessary

Terminating audit of OFS nnnn-nnnn-nnnn-nnnn.

Level:NOTICE

Identifier:PFC.ofcm

[Explanation]The audit of the OFS with a DPID of nnnn-nnnn-nnnn-nnnn was stopped because the OFSwas disconnected from the PFC server.

[Action]If this disconnection is not intended, check the connection between the OFS and the PFC server.

Audit of OFS nnnn-nnnn-nnnn-nnnn failed, disconnecting.

Level:WARNING

Identifier:PFC.ofcm

[Explanation]An audit (initialization upon connection) has been executed on the OFS with a DPID of nnnn-nnnn-nnnn-nnnn, but connection to the OFS was terminated due to a flow setting error.


30

[Action]Connect the OFS to the PFC server again (the OFS is automatically reconnected by specifying aflow setting). This message may also be output when the response is slow due to a high OFSprocessing load.

Finished audit of OFS nnnn-nnnn-nnnn-nnnn.

Level:NOTICE

Identifier:PFC.ofcm

[Explanation]The audit of the OFS with a DPID of nnnn-nnnn-nnnn-nnnn has finished.

[Action]Unnecessary

pthctl started.

Level:INFO

Identifier:PFC.pthctl

[Explanation]The pthctl module has started.

[Action]Unnecessary

pthctl initialize start.

Level:INFO


[Explanation]Initialization of the pthctl module has started.

[Action]Unnecessary


31

pthctl finalize start.

Level:INFO


[Explanation]Termination of the pthctl module has started.

[Action]Unnecessary

pthctl stopped.

Level:INFO


[Explanation]The pthctl module has stopped.

[Action]Unnecessary

Add edge_node [nnnn-nnnn-nnnn-nnnn] from [m].

Level:INFO


[Explanation]The OFS with a DPID of nnnn-nnnn-nnnn-nnnn has started to be used as EdgeNode.

(m is either 0 or 1: If 0, EdgeNode is registered as path control; if 1, EdgeNode is registered asVTN.)

[Action]Unnecessary

Delete edge_node [nnnn-nnnn-nnnn-nnnn] from [m].


32

Level:INFO


[Explanation]The OFS with a DPID of nnnn-nnnn-nnnn-nnnn has stopped being used as EdgeNode.

(m is either 0 or 1: If 0, EdgeNode is registered as path control; if 1, EdgeNode is registered asVTN.)

[Action]Unnecessary

Set Avoid OFS [nnnn-nnnn-nnnn-nnnn] is [OK].

Level:INFO


[Explanation]The OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been excluded.

[Action]Unnecessary

Delete Avoid OFS [nnnn-nnnn-nnnn-nnnn] is [OK].

Level:INFO


[Explanation]Exclusion of the OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been canceled.

[Action]Unnecessary

Broadcast OFS Core Domain splits in domain=[OFS domain].(Centered OFS DPIDs:nnnn-nnnn-nnnn-nnnn,mmmm-mmmm-mmmm-mmmm)


33

Level:WARNING


[Explanation]An OFS core domain split in the network for broadcast delivery has occurred in the OFSdomain. Delivery has been split into 2 groups, one for the OFS with a DPID of nnnn-nnnn-nnnn-nnnn, and one for the OFS with a DPID of mmmm-mmmm-mmmm-mmmm.

[Action]A split in the PFC network has occurred. Confirm OFSs that belong to the OFS core domain ofthe OFS domain, and OFS domain affiliation settings via the show ofs-domain command,confirm the topology of the connection between the OFS and PFC, and the state of connectionbetween OFSs.

If this alarm message is issued but the error is recovered immediately after the PFC server startson the active or standby node, there is no problem.

Recover broadcast OFS Core Domain splits in domain=[OFS domain].

Level:NOTICE


[Explanation]The broadcast delivery network disconnection has been recovered in the OFS core domain in theOFS domain.

[Action]Unnecessary

Broadcast OFS subdomain splits in domain=[OFS domain]:subdomain=[OFS subdomain].(Centered OFS DPIDs:nnnn-nnnn-nnnn-nnnn,mmmm-mmmm-mmmm-mmmm)

Level:WARNING


[Explanation]A split in the network for broadcast delivery has occurred. Delivery has been split into 2 groups,one for the OFS with a DPID ofnnnn-nnnn-nnnn-nnnn, and one for the OFS with a DPID of mmmm-mmmm-mmmm-mmmm.


34

[Action]A split in the PFC network has occurred. Run the show ofs-domain command to confirmOFSs that belong to the OFS subdomain and OFS subdomain affiliation setting/OFS subdomaingateway setting status, and connect OFS and PFC in the OFS subdomain. Then, confirmtopology of connection status between OFSs, and connect OFS subdomain gateway port.

If this alarm message is issued but the error is recovered immediately after the PFC server startson the active or standby node, there is no problem.

Recover broadcast OFS subdomain splits in domain=[OFS domain]:subdomain=[OFS subdomain].

Level:NOTICE


[Explanation]The split in the network for broadcast delivery has been recovered in the OFS subdomain.

[Action]Unnecessary

Flow entry full occurred.(OFS DPID[nnnn-nnnn-nnnn-nnnn])

Level:WARNING


[Explanation]A flow settings overflow to the OFS with a DPID of nnnn-nnnn-nnnn-nnnn has occurred.

[Action]As a flow settings overflow to OFS has occurred, check the configuration of the entire network.

Flow entry full recovery.(OFS DPID[nnnn-nnnn-nnnn-nnnn])

Level:NOTICE



35

[Explanation]The flow settings for the OFS with a DPID of nnnn-nnnn-nnnn-nnnn have been successfullyspecified, and the OFS has recovered from the settings overflow.

[Action]Unnecessary

Push mode degraded.(OFS DPID[nnnn-nnnn-nnnn-nnnn])

Level:WARNING


[Explanation]An unsupported OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been connected in the Pushmode settings, limiting the functions.

[Action]PFSs other than PF5240 are registered to either ofs map or vlan map, so check the VTNconfiguration.

Push mode recovery.(OFS DPID[nnnn-nnnn-nnnn-nnnn])

Level:NOTICE


[Explanation]The unsupported OFS with a DPID of nnnn-nnnn-nnnn-nnnn has been removed in the Pushmode settings, lifting the functional limitations.

[Action]Unnecessary

Path failed between OFS [nnnn-nnnn-nnnn-nnnn] and OFS [mmmm-mmmm-mmmm-mmmm] on path-policy [index].

Level:WARNING



36

[Explanation]On the path policy index, there is no valid path between the OFS with a DPID of nnnn-nnnn-nnnn-nnnn and the OFS with a DPID of mmmm-mmmm-mmmm-mmmm, causing a path failure.

[Action]A split in the PFC network has occurred. Confirm the topology of the connection between theOFS and PFC, and the state of connection between OFSs.

Path recovered between OFS [nnnn-nnnn-nnnn-nnnn] and OFS [mmmm-mmmm-mmmm-mmmm] on path-policy [index].

Level:NOTICE


[Explanation]On the path policy index, the path failure between the OFS with a DPID of nnnn-nnnn-nnnn-nnnn and the OFS with a DPID of mmmm-mmmm-mmmm-mmmm has been recovered.

[Action]Unnecessary

OFS Domain Miss Link Occurred between [OFS domain 1]:nnnn-nnnn-nnnn-nnnn:[port 1] and [OFS domain 2]:mmmm-mmmm-mmmm-mmmm:[port 2].

Level:WARNING


[Explanation]A connection spanning OFS domains is detected between port 1 of the OFS domain 1 with aDPID of nnnn-nnnn-nnnn-nnnn and port 2 of the OFS domain 2 with a DPID of mmmm-mmmm-mmmm-mmmm.

[Action]A link spanning OFS domains is being automatically detected. Run the show ofs-domaincommand to confirm OFS domain settings of OFSs with a DPID of nnnn-nnnn-nnnn-nnnnand a DPID of mmmm-mmmm-mmmm-mmmm, and confirm connection to port 1 of the OFS with aDPID of nnnn-nnnn-nnnn-nnnn and port 2 of the OFS with a DPID of mmmm-mmmm-mmmm-mmmm. To intentionally connect multiple OFSs for operation, run the show trunk-port and showofs commands to confirm MCLAG member port setting or external port setting for port 1 of theOFS with a DPID of nnnn-nnnn-nnnn-nnnn and port 2 of the OFS with a DPID of mmmm-mmmm-mmmm-mmmm.


37

OFS Domain Miss Link Recovered between [OFS domain name]:nnnn-nnnn-nnnn-nnnn:[port name] and [OFS domain]:mmmm-mmmm-mmmm-mmmm:[port name].

Level:NOTICE


[Explanation]A connection link spanning OFS domains between port 1 of the OFS domain with a DPID of nnnn-nnnn-nnnn-nnnn and port 2 of the OFS domain with a DPID of mmmm-mmmm-mmmm-mmmmhas been cleared.

[Action]Unnecessary

OFS Subdomain Miss Link Occurred in Domain=[OFS domain] between [OFS subdomain 1]:nnnn-nnnn-nnnn-nnnn:[port 1] and [OFS subdomain 2]:mmmm-mmmm-mmmm-mmmm:[port 2].

Level:WARNING


[Explanation]A connection link spanning OFS subdomains between port 1 of the OFS subdomain 1 (or OFScore domain) with a DPID of nnnn-nnnn-nnnn-nnnn and port 2 of the OFS subdomain 2 witha DPID of mmmm-mmmm-mmmm-mmmm in the OFS domain has been detected.

[Action]A link spanning OFS subdomains or a connection between OFS core domain and OFSsubdomain via a port without OFS subdomain gateway setting is being automatically detected.Run the show ofs-domain command to confirm the subdomain affiliation settings of OFS/port1 with a DPID of nnnn-nnnn-nnnn-nnnn and OFS/port2 with a DPID of mmmm-mmmm-mmmm-mmmm, the OFS subdomain gateway setting of OFS/port1 with a DPID of nnnn-nnnn-nnnn-nnnn, and a confirm connection to OFS/port1 with a DPID nnnn-nnnn-nnnn-nnnn and aconnection to OFS/port2 with a DPID mmmm-mmmm-mmmm-mmmm.

OFS Subdomain Miss Link Recovered in Domain=[OFS domain] between [OFS subdomain 1]:nnnn-nnnn-nnnn-nnnn:[port 1] and [OFS subdomain 22]:mmmm-mmmm-mmmm-mmmm:[port 2].

Level:NOTICE



38

[Explanation]A connection spanning OFS subdomains between OFS port 1 of the OFS subdomain 1 with aDPID of nnnn-nnnn-nnnn-nnnn and OFS port 2 of the OFS subdomain 2 with a DPID of mmmm-mmmm-mmmm-mmmm has been cleared.

[Action]Unnecessary

Path-oam started. (ingress OFS[nnnn-nnnn-nnnn-nnnn] and egress OFS[mmmm-mmmm-mmmm-mmmm])

Level:INFO


[Explanation]Confirmation of conduction of the path between DPID nnnn-nnnn-nnnn-nnnn and DPID mmmm-mmmm-mmmm-mmmm has started.

[Action]Unnecessary

Path-oam canceled. (ingress OFS[nnnn-nnnn-nnnn-nnnn] and egress OFS[mmmm-mmmm-mmmm-mmmm])

Level:INFO


[Explanation]Confirmation of conduction of the path between DPID nnnn-nnnn-nnnn-nnnn and DPID mmmm-mmmm-mmmm-mmmm has stopped.

[Action]Unnecessary

Path-oam finished.(ingress OFS[nnnn-nnnn-nnnn-nnnn] and egress OFS[mmmm-mmmm-mmmm-mmmm]) (result:xxxx)

Level:INFO



39

[Explanation]Confirmation of conduction of the path between DPID nnnn-nnnn-nnnn-nnnn and DPID mmmm-mmmm-mmmm-mmmm is completed. The result is xxxx.

[Action]Unnecessary

Switch port-group audit started(dpid:mmmm-mmmm-mmmm-mmmm).

Level:NOTICE


[Explanation]The port group state matching process between the PFC and the OFS with a DPID of mmmm-mmmm-mmmm-mmmm has started.

[Action]Unnecessary

Switch port-group audit finished(dpid:mmmm-mmmm-mmmm-mmmm, result:n).

Level:NOTICE


[Explanation]The port group state matching process between the PFC and the OFS with a DPID of mmmm-mmmm-mmmm-mmmm has finished.

n: Result of the port group state matching process (Completed / Incompleted / Aborted)

[Action]Unnecessary

Link Down Relay policy enable. (<policy_name>)

Level:INFO

Identifier:PFC.ifm


40

[Explanation]The Link Down Relay policy has been enabled.

policy_name: Policy name

[Action]Unnecessary

Link Down Relay policy disable. (<policy_name>)

Level:INFO

Identifier:PFC.ifm

[Explanation]The Link Down Relay policy has been disabled.

policy_name: Policy name

[Action]Unnecessary

Link Down Relay policy action status changed. (<policy_name>, <before_action_status> -> <after_action_status> [auto|manual])

Level:INFO

Identifier:PFC.ifm

[Explanation]The Link Down Relay policy status has changed.

<policy_name>: Policy name

<before_action_status>: Status before transition

<after_action_status>: Status after transition

auto: Auto recovery

manual: Manual recovery

[Action]Unnecessary

Link Down Relay policy activated. (<policy_name>, <policy_action_status>)


41

Level:INFO

Identifier:PFC.ifm

[Explanation]The Link Down Relay policy has been activated.


<policy_action_status>: Policy status

[Action]Unnecessary

Link Down Relay policy inactivated. (<policy_name>, <policy_action_status>)

Level:INFO

Identifier:PFC.ifm

[Explanation]The Link Down Relay policy has been inactivated.


<policy_action_status>: Policy status

[Action]Unnecessary

OFS Port AdminStatus change success. (<dpid>, <port_name>, up|down, init|ldr|command)

Level:INFO

Identifier:PFC.ifm or PFC.ofcm

[Explanation]The OFS port AdminStatus change setting has been successfully executed.

<dpid>: DPID value

<port_name>: Port name

up: Setting for changing the port AdminStatus to up


42

down: Setting for changing the port AdminStatus to down

init: Output when the port AdminStatus change setting has been executed at port initializationduring OFS connection

ldr: Output when the port AdminStatus change setting has been executed by Link Down Relay

command: Output when the port AdminStatus change setting has been executed via a CLIcommand

[Action]Unnecessary

OFS Port AdminStatus change skipped. (<dpid>, <port_name>, up|down, init [none]|ldr)

Level:INFO

Identifier:PFC.ifm

[Explanation]Execution of the OFS port AdminStatus change setting has been skipped.

<dpid>: DPID value





none: Output when the init processing has been skipped (for the execution port for which theLink Down Relay policy is enabled)


[Action]Unnecessary

OFS Port AdminStatus change failed.(<dpid>, <port_name>, up|down, init|ldr, result=<result>)

Level:WARNING

Identifier:PFC.ifm

[Explanation]Execution of the OFS port AdminStatus change setting has failed.


43

<dpid>: DPID value






result: Reason for error

[Action]Unnecessary

Ethernet CFM MA fault. (<md_name>, <ma_name>)

Level:WARNING

Identifier:PFC.ifm

[Explanation]An MA failure occurred.

<md_name>: MD name

<ma_name>: MA name

[Action]MA information is now abnormal due to a problem of OFS. Execute the show ethernet-cfmfault status command to check MA information of <md_name> and <ma_name>. Bychecking the OFS settings making up the MA information, resolve the problems of OFS.

For details about how to connect or disconnect the OFS to/from the OpenFlow network, refer to(1) Disconnects the operating OFS from the network and (2) Procedures for reconnecting theOFS to the network of Procedures for changing the configuration of an OFS during operation inthe Configuration Guide.

Ethernet CFM MA fault recovery. (<md_name>, <ma_name>)

Level:NOTICE

Identifier:PFC.ifm

[Explanation]The MA failure has recovered.


44

<md_name>: MD name

<ma_name>: MA name

[Action]Unnecessary

1.9 Logs Output by the PFC Core NetworkPort is down. dpid = [dpid] port_name = [Port Name]

Level:WARNING

Identifier:PFC.pfcd

[Explanation]The OFS port <Port name> with a DPID of <dpid> is down.

[Action]If the expected port is not down, check the connection state.

Port is UP. dpid = [dpid] port_name = [Port Name]

Level:NOTICE

Identifier:PFC.pfcd

[Explanation]The OFS port <Port name> with a DPID of <dpid> has been up.

[Action]Unnecessary

Same OpenFlowSwitch already connected. dpid = [dpid]

Level:ERR

Identifier:PFC.pfcd


45

[Explanation]A secure channel connection request from an OFS with the same DPID as a connected OFS(caused by a setting mistake or network failure) has been received.

[Action]Check the settings. Each OFS must have a different DPID.

Port direction is inconsistent. DPID:[dpid] (ofs:[ofs_id]) (trunk-port), PortName:[Port name]

Level:WARNING

Identifier:PFC.pfcd

[Explanation]It was detected that the connection status of the port in question is different from the settings.

[Action]Check the connection status of the port and the settings (ofs and trunk-port on the PFC shell)and correct the problem with the connection, or the settings.

Port direction is consistent. DPID:[dpid] (ofs:[ofs_id]) (trunk-port), PortName:[Port name]

Level:NOTICE

Identifier:PFC.pfcd

[Explanation]The abnormal status that the connection status of the port in question is different from thesettings has been recovered.

[Action]Unnecessary

Port is configured as external, but it is connected with another OFS. dpid=[dpid], port_name=[Port name], peer_dpid=[dpid], peer_port_name=[Port name]

Level:WARNING

Identifier:PFC.pfcd


46

[Explanation]It was detected that the port configured as external is connected to another OFS port.

[Action]Check the connection status of the port and the settings (ofs and trunk-port on the PFC shell)and correct the problem with the connection, or the settings.

The number of activated licenses has exceeded the limit. license type=<type>, ofs=<dpid>, peer=<ipaddr>:<port>

Level:WARNING

Identifier:PFC.pfcd

[Explanation]The number of OFSs connected through the secure channel has exceeded the number of licenses.Those OFSs that exceed the limit cannot be used.

License type: <type>DPID: <dpid>Address of secure channel on OFS side: <ipaddr>:<port>This message is output for each license type.

After this message is output, but until the clear license rejected-ofs command isexecuted, this message is not output even if the number of licenses is again exceeded for thelicense type in question at secure channel connection.

[Action]Execute the show license ofs rejected-ofs command, and then disconnect the securechannel for the indicated OFS. After disconnecting the secure channel, execute the clear license rejected-ofs command.

Then, purchase and install a license, and then reconnect the secure channel for the OFS.

dpid:<dpid> is duplicate. Older SecureChannel is disconnected. Older peer = <ipaddr1>:<port1>, Newer peer = <ipaddr2>:<port2>

Level:WARNING

Identifier:PFC.pfcd

[Explanation]Since the DPID <dpid> of the secure channel that was newly set up is the same as an existingDPID, the existing secure channel was disconnected.


47

The addresses of the corresponding secure channels in the OFS are as follows.

Old address: <ipaddr1>:<port1>New address: <ipaddr2>:<port2>

[Action]Check whether the same DPID is set to the OFSs of <ipaddr1> and <ipaddr2>.

dpid:<dpid> SecureChannel connection fail over. Older peer = <ipaddr1>:<port1>, Newer peer = <ipaddr2>:<port2>

Level:NOTICE

Identifier:PFC.pfcd

[Explanation]Failover of a secure channel was performed and a detour path is being used.

The secure channel with a DPID of <dpid> was taken over by a new path.

The addresses of the corresponding secure channels in the OFS are as follows.

Old address: <ipaddr1>:<port1>New address: <ipaddr2>:<port2>

[Action]This log may be output when the network load between the OFS and PFC is high. (This is notabnormal.)

1.10 Logs Output by the CLIConfiguration sync failed. ACT PFCapisvd exiting.

Level:WARNING

Identifier:PFC.pfcsh.conf

[Explanation]An abnormality occurred in the active node during configuration synchronization processing in acluster configuration PFC. PFCapisvd in the active node of the cluster configuration has beenstopped.


48

[Action]Check if cluster node switchover is complete. If cluster node switchover has failed and the PFCshell cannot be started, take action according to Cluster Trouble in the Troubleshooting Guide.

Configuration sync failed. SBY PFCapisvd exiting.

Level:WARNING

Identifier:PFC.pfcsh.conf

[Explanation]An abnormality occurred in the standby node during configuration synchronization processing incluster configuration PFC. PFCapisvd in the standby node of the cluster configuration has beenstopped.

[Action]Check if the PFC in the standby node of the cluster configuration has restarted and if the PFCshell can be started.

1.11 Logs Output by the License ManagerPFC license has expired: count=%u, U-code=%s

Level:ERR

Identifier:PFC.licd

[Explanation]The license has expired. The number of expired U-codes is displayed in count=%u, and up tothree expired U-code values are displayed in U-code=%s.

[Action]Check the license information, and update the licenses that have expired. Refer to the pfc_licmgtlist in the Command Reference for how to check the license information.

PFC license will expire: count=%u, U-code=%s

Level:WARNING

Identifier:PFC.licd


49

[Explanation]The expiry date for the license is approaching. The number of U-codes nearing the expiry date isdisplayed in count=%u, and up to three U-code values are displayed in U-code=%s.

[Action]Check the license information, and update the licenses. Refer to the pfc_licmgt list in theCommand Reference for how to check the license information.

All PFC licenses have been successfully validated.

Level:NOTICE

Identifier:PFC.licd

[Explanation]The licenses have been updated, and all the licenses have been successfully authenticated.

[Action]Unnecessary

1.12 Logs Output by the Traffic MonitorOFS port congestion occurred. ofs = [dpid] port = [Port name]

Level:WARNING

Identifier:PFC.trmon

[Explanation]An increase in traffic has caused congestion at the port [Port name] for the OFS with a DPIDof [dpid].

[Action]It is possible that there is a large amount of traffic on the OpenFlow network. Check thenetwork.

OFS port congestion recovered. ofs = [dpid] port = [Port name]

Level:NOTICE


50

Identifier:PFC.trmon

[Explanation]The port [Port name] for the OFS with a DPID of [dpid] has recovered from the congestion.

[Action]Unnecessary

1.13 Logs Output by Automatic VLAN Settingpfvlan has started.

Level:INFO

Identifier:PFC.pfvlan

[Explanation]The PFVLAN module has started.

[Action]Unnecessary

pfvlan has stopped.

Level:INFO


[Explanation]The PFVLAN module has stopped.

[Action]Unnecessary

Starting VLAN audit of OFS <DPID>.

Level:NOTICE


51


[Explanation]Re-input of the VLAN settings for the OFS with a DPID of <DPID> has started.

[Action]Unnecessary

Terminating VLAN audit of OFS <DPID>.

Level:NOTICE


[Explanation]Re-input of the VLAN settings for the OFS with a DPID of <DPID> was stopped because theconnection to the OFS was interrupted.

[Action]End Sub

VLAN audit of OFS <DPID> port <PortName> failed.

Level:WARNING


[Explanation]Re-input of the VLAN settings for the OFS port <PortName> with a DPID of <DPID> hasfailed.

[Action]There may be an error in the OFS settings. Take corrective action as described in Cannotconfigure VLAN settings for OFS in the Troubleshooting Guide.

VLAN audit of OFS <DPID> port <PortName> skipped.

Level:WARNING


52


[Explanation]Processing has been skipped because re-input of the VLAN settings for OFS port <PortName>with a DPID of <DPID> was in progress.

[Action]After re-input of the VLAN settings has been completed, check whether the VLAN settings arecorrectly configured. If they are not correct, take corrective action as described in Cannotconfigure VLAN settings for OFS in the Troubleshooting Guide.

Finished VLAN audit of OFS <DPID>.

Level:NOTICE


[Explanation]Re-input of the VLAN settings for the OFS with a DPID of <DPID> has finished.

[Action]Unnecessary

1.14 Logs Output by the Dual ClusterManagement

Dcsd process started.

Level:INFO

Identifier:PFC.dcsd

[Explanation]The dual cluster management process started.

[Action]Unnecessary

Dcsd process terminated.


53

Level:INFO

Identifier:PFC.dcsd

[Explanation]The dual cluster management process stopped.

[Action]Unnecessary

Dual Cluster getting backup file failed.

Level:ALERT

Identifier:PFC.dcsd

[Explanation]Failed to acquire the dual cluster automatic backup file.

[Action]Confirm the collection history of main cluster operation status.

Run the command below for the active-system PFC in the reserve cluster to confirm the backupdate and time and the file name. If there is no file, confirm the regular backup setting for themain cluster. Also, confirm conduction status between the main cluster and the reserve clusterfor the management network.

# pfc_dual_cluster -bDate File Checksum20121101_11:00:00 back_20121101110052_V4.0.0.0buildXX.tar.gz/back_20121101110052_V4.0.0.0buildXX.tar.gz.sha256sum OK20121101_12:00:00 back_20121101120052_V4.0.0.0buildXX.tar.gz/back_20121101120052_V4.0.0.0buildXX.tar.gz.sha256sum OK

Dual Cluster getting PFC (ACT) status from Main-cluster failed.

Level:ALERT

Identifier:PFC.dcsd

[Explanation]Failed to collect the operation history of main cluster of the dual cluster.


54

[Action]Confirm the collection of operation history of the main cluster.

Run the command below for the active-system PFC in the reserve cluster to confirm the date andtime in the collection history and operation status of the main cluster. If the operation status isNG, confirm the conduction state between the main cluster and the reserve cluster for themanagement network.

# pfc_dual_cluster -mDate Main PFC Cluster Status20121225_11:00:00 NG20121225_12:00:00 NG

PFC (ACT) stoped in Main-cluster

Level:ALERT

Identifier:PFC.dcsd

[Explanation]An error may have been occurred in the active-system PFC in the main cluster.

This includes a case where the appropriate PFC status has not been acquired.

[Action]Run the command below for the active-system PFC in the reserve cluster to confirm the date andtime of operation status collection and the operation status of the main cluster. If the operationstatus is NG, confirm the conduction state between the main cluster and the reserve cluster forthe management network.

# pfc_dual_cluster -mDate Main PFC Cluster Status20121225_11:00:00 NG20121225_12:00:00 NG


55

Chapter 2. Alarm MessagesThis chapter describes the alarms that occur during operation.

2.1 Alarms and TrapsThis section shows a list of alarms and traps.

TipFor details about the traps, refer to the MIB Reference.

The following table lists and describes the levels of importance of the alarms and traps.

Table 2-1 List of Importance Levels

Level of Importance Meaning

High↑

↓Low

ale AlertFailures that cause the PFC software to stop or have to be rebooted.These are failures that must be immediately handled by maintenance staff.

cri CriticalFailures that, while not causing the PFC software to immediately stop, willcause the PFC software to stop or have to be rebooted if it continues to run.These are failures that must be immediately handled by maintenance staff.

err ErrorPFC software failures.These are failures that must be checked by maintenance staff.

war WarningPFC software failures.These are failures that must be checked by maintenance staff.

not NoticeInformation necessary the security of the PFC if the state of the PFC haschanged after recovering from a failure, and other important information.This is information that should be checked by maintenance staff if required.

inf InformationPFC operating information.This is information that should be checked by maintenance staff if required.

The following table lists and describes the types of alarms and traps.

Table 2-2 List of Types

Type Operation

Notification Only trap transmission is performed. Alarms are not displayed.

Occurrence Trap transmission is performed, and alarms are displayed.

Recovery Trap transmission is performed, and alarms are displayed.Using the show alarm history command to bring up the alarm display, the alarm messages andlevels of importance are displayed, and alarms are separated, with recovered alarms displayed as

Chapter 2. Alarm Messages

56

Type Operationeither recovered or r. Refer to show alarm history in the Command Reference for details of thealarm display.

Alarms displayed by using the show alarm history command indicate the time when the PFCserver software started (--- start ---) in addition to the alarm information.

Table 2-3 List of Alarms and Traps

Levelof

Importance

Type Trap Name AlarmMessage

(Summary)

Alarm Message Meaning Action

- Notification

coldStart - - The SNMPfunction hasstarted.

None.

- Notification

linkDown - - The NIC link isdown.

Confirm that theLAN cable iscorrectlyconnected.

- Notification

linkUp - - The NIC link isup.

None.

- Notification

pf6000ColdStart - - The SNMPfunction hasstarted.

None.

- Notification

pf6000LinkDown - - The NIC link isdown.

Confirm that theLAN cable iscorrectlyconnected.

- Notification

pf6000LinkUp - - The NIC link isup.

None.

war Occurrence

pf6000sVtnctlVTNFaultWaO

VTN Fault VTN Faultvtn=<value>

More than onepath that cannotcommunicatewith vtn=<value> has occurred.

A failure in theOpenFlownetwork hasoccurred. Followthe actionsdescribed in 3.4Virtual NetworkFailure in theTroubleshootingGuide.

not Recovery

pf6000sVtnctlVTNFaultNoR

VTN FaultRecovery

VTN FaultRecoveryvtn=<value>

All failures onthe paths to vtn=<value> havebeen recovered.

None.

not Notification

pf6000sNomgSWStartNoN

PFC ServerSoftware started

PFC ServerSoftware started

The PFC ServerSoftware hasstarted.

None.

ale Notification

pf6000sNomgSWStartFailAlN

PFC Server Softstart failed

PFC ServerSoftware startfailed

Failed to start thePFC ServerSoftware.

An automaticrecovery will beperformed at therestart level.(Refer topfc_clear_restart


57

Levelof

Importance


(Summary)


_level in theCommandReference fordetails about therestart level.)

not Notification

pf6000sNomgSWStopNoN

PFC ServerSoftware stopped

PFC ServerSoftware stopped

The PFC ServerSoftware hasstopped.

None.

ale Notification

pf6000sNomgSWAbortAlN

PFC ServerSoftware aborted

PFC ServerSoftware aborted

The PFC ServerSoftware hasbeen aborted.

An automaticrecovery will beperformed at therestart level.(Refer topfc_clear_restart_level in theCommandReference fordetails about therestart level.)

not Notification

pf6000sNomgSWRestartNoN

PFC ServerSoftwarerestarted

PFC ServerSoftware restarted

The PFC ServerSoftware hasrestarted.

None.

ale Notification

pf6000sNomgSWRestartFailAlN

PFC Server Softrestart failed

PFC ServerSoftware restartfailed

Failed to restartthe PFC ServerSoftware.


ale Notification

pf6000sNomgServerRebootAlN

Rebooting PFCServer

Rebooting PFCServer because ofthe restart level 3

The PFC serverwas rebootedbecause therestart level islevel 3.


ale Notification

pf6000sNomgSWStopAlN

Stopping PFCServer Software

Stopping PFCServer Softwarebecause of therestart level 4

Stoppedrebooting thePFC serverbecause therestart level islevel 4.

As the automaticrecovery failed,contact themaintenance andservice company.(Refer topfc_clear_restart


58

Levelof

Importance


(Summary)


_level in theCommandReference fordetails about theautomaticrecovery.)

war Occurrence

pf6000sResmgrCpuUsageRiseWaO

CPU usage abovethreshold

CPU utilizationabove rising-threshold xx%

CPU usage onthe PFC Serverhas exceeded theupper threshold.

Check the state ofthe PFC Server,and considerrevising theupper threshold ifthere is not aproblem.

not Recovery

pf6000sResmgrCpuUsageFallNoR

(1) CPU usagebelow threshold(2) CPUthreshold wasdeleted

(1) CPUutilization belowfalling-thresholdxx%(2) The high loadjudgment of CPUutilization wascanceled becausethreshold wasdeleted

(1) CPU usageon the PFCServer has fallenbelow the lowerthreshold.(2) The thresholdsettings formonitoring CPUusage on the PFCserver have beendeleted, sojudgment abouthigh loads hasbeen stopped.

None.

war Occurrence

pf6000sResmgrMemUsageRiseWaO

Mem usageabove threshold

Memoryutilization aboverising-thresholdxx%

Physical memoryusage on the PFCServer hasexceeded theupper threshold.

Check the state ofthe PFC Server,and considerrevising theupper threshold ifthere is not aproblem.

not Recovery

pf6000sResmgrMemUsageFallNoR

(1) Mem usagebelow threshold(2) Memthreshold wasdeleted

(1) Memoryutilization belowfalling-thresholdxx%(2) The high loadjudgment ofmemoryutilization wascanceled becausethreshold wasdeleted

(1) Physicalmemory usageon the PFCServer has fallenbelow the lowerthreshold.(2) The thresholdsettings formonitoring CPUusage on the PFCserver have beendeleted, sojudgment abouthigh loads hasbeen stopped.

None.

war Occurrence

pf6000sResmgrDiskUsageRiseWaO

Disk usage abovethreshold

<Device Name>utilization above

Disk usage onthe PFC Serverhas exceeded theupper threshold.

Check the state ofthe PFC Server,and considerrevising the


59

Levelof

Importance


(Summary)


rising-thresholdxx%

upper threshold ifthere is not aproblem.

not Recovery

pf6000sResmgrDiskUsageFallNoR

(1) Disk usagebelow threshold(2) Diskthreshold wasdeleted

(1) <DeviceName> utilizationbelow falling-threshold xx%(2) The high loadjudgment of<Device Name>utilization wascanceled becausethreshold wasdeleted

(1) Disk usageon the PFCServer has fallenbelow the lowerthreshold.(2) The thresholdsettings formonitoring CPUusage on the PFCserver have beendeleted, sojudgment abouthigh loads hasbeen stopped.

None.

err Occurrence

pf6000sResmgrDiskFailErO

Failed to get diskinformation

Failed to get diskinformation.<Device Name>

Failed to getinformationabout the PFCServer disk.

Check that thesettings for thedisk on the PFCServer have notbeen changed. Ifthe settings havenot beenchanged, checkthe condition ofthe PFC serverdisk, and if theproblem is stillnot solved,contact theservice andmaintenancecompany.

not Recovery

pf6000sResmgrDiskRecoverNoR

Recovered to getdisk info

Failure to get diskinformation wasrecovered.<Device Name>

The failure to getinformationabout the PFCServer disk hasbeen recovered.

None.

not Notification

pf6000sAplmgrProcStartNoN

PFC processstarted

PFC processstarted.Process:<PFCProcess Name>

A PFC processhas started.

None.

ale Occurrence

pf6000sAplmgrProcStartFailAlO

PFC process startfailed

PFC process startfailed.Process:<PFCProcess Name>

A PFC processhas failed tostart. (Level ofImportance:Alert)

An automaticrecovery will beperformed at therestart level.(Refer topfc_clear_restart_level in theCommandReference for


60

Levelof

Importance


(Summary)


details about therestart level.)

cri Occurrence

pf6000sAplmgrProcStartFailCrO



PFC process hasfailed to start.(Level ofImportance:Critical)


err Occurrence

pf6000sAplmgrProcStartFailErO



A PFC processhas failed tostart. (Level ofImportance:Error)


war Occurrence

pf6000sAplmgrProcStartFailWaO



A PFC processhas failed tostart. (Level ofImportance:Warning)


not Occurrence

pf6000sAplmgrProcStartFailNoO



A PFC processhas failed tostart. (Level ofImportance:Notice)


ale Occurrence

pf6000sAplmgrProcStartTimeoutAlO

PFC process starttimeout

PFC process starttimeout.Process:<PFCProcess Name>

A PFC processhas timed out.(Level ofImportance:Alert)

An automaticrecovery will beperformed at therestart level.(Refer topfc_clear_restart


61

Levelof

Importance


(Summary)


_level in theCommandReference fordetails about therestart level.)

cri Occurrence

pf6000sAplmgrProcStartTimeoutCrO



A PFC processhas timed out.(Level ofImportance:Critical)


err Occurrence

pf6000sAplmgrProcStartTimeoutErO



A PFC processhas timed out.(Level ofImportance:Error)


war Occurrence

pf6000sAplmgrProcStartTimeoutWaO



A PFC processhas timed out.(Level ofImportance:Warning)


not Occurrence

pf6000sAplmgrProcStartTimeoutNoO



A PFC processhas timed out.(Level ofImportance:Notice)


not Notification

pf6000sAplmgrProcStopNoN

PFC processstopped

PFC processstopped.

A PFC processhas stopped.

None.


62

Levelof

Importance


(Summary)


Process:<PFCProcess Name>

war Occurrence

pf6000sAplmgrProcStopFailWaO

PFC process stopfailed

PFC process stopfailed.Process:<PFCProcess Name>

A PFC processhas failed tostop.

The process forstopping the PFCServer Softwarewill continue.Check thecondition of thePFC Server, andif there is aproblem, contactthe maintenanceand servicecompany.

war Occurrence

pf6000sAplmgrProcStopTimeoutWaO

PFC process stoptimeout

PFC process stoptimeout.Process:<PFCProcess Name>

A PFC processhas not stoppedwithin thetimeout limit.

The process forstopping the PFCServer Softwarewill continue.Check thecondition of thePFC Server, andif there is aproblem, contactthe maintenanceand servicecompany.

ale Occurrence

pf6000sAplmgrProcAbortAlO

PFC processaborted

PFC processaborted.Process:<PFCProcess Name>

A PFC processhas been aborted.(Level ofImportance:Alert)


cri Occurrence

pf6000sAplmgrProcAbortCrO

PFC processaborted


A PFC processhas been aborted.(Level ofImportance:Critical)


err Occurrence

pf6000sAplmgrProcAbortErO

PFC processaborted


A PFC processhas been aborted.(Level of

An automaticrecovery will beperformed at therestart level.


63

Levelof

Importance


(Summary)


Importance:Error)

(Refer topfc_clear_restart_level in theCommandReference fordetails about therestart level.)

war Occurrence

pf6000sAplmgrProcAbortWaO

PFC processaborted


A PFC processhas been aborted.(Level ofImportance:Warning)


not Occurrence

pf6000sAplmgrProcAbortNoO

PFC processaborted


A PFC processhas been aborted.(Level ofImportance:Notice)


war Occurrence

pf6000sViewgaFlowThresholdOWaO

Rising sFlowThreshold

Rising sFlowThresholdofs=<value>IN IF=<value>srcIP=<value>dstIP=<value>srcPort=<value>dstPort=<value>setting=<value>over=<value>

The value hasexceeded thesFlow threshold.

It is possible thatthere is a largeamount of trafficon the OpenFlownetwork. Checkthe network

not Recovery

pf6000sViewgaFlowThresholdRNoR

Rising sFlowThresholdrecovery

Rising sFlowThresholdRecoveryofs=<value>IN IF=<value>srcIP=<value>dstIP=<value>srcPort=<value>dstPort=<value>

The value hasfallen below thesFlow threshold.

None.


64

Levelof

Importance


(Summary)


war Occurrence

pf6000sPthctlPhysPathFaultWaO

Physical PathFault

Physical PathFaultIngressofs=<value>Egressofs=<value>PathPolicyIndex=<index>

On the pathpolicy <index>, apath failure hasoccurredbetween Ingress ofs=<value>and gress ofs=<value>.

A failure in theOpenFlownetwork hasoccurred.Confirm thetopology of theconnectionbetween the OFSand PFC, and theconnection statebetween OFSs.

not Recovery

pf6000sPthctlPhysPathFaultNoR

Physical PathFault Recovery

Path FaultRecoveryIngressofs=<value>Egressofs=<value>PathPolicyIndex=<index>

On the pathpolicy <index>,the path failurebetween Ingress ofs=<value>and Egress ofs=<value> hasbeen recovered.

None.

war Occurrence

pf6000sPthctlFlowEntFullOccurWaO

FlowEntry FullOccurred

FlowEntry FullOccurredofs=<value>

A flow settingsoverflow for ofs=<value> hasoccurred.

There is apossibility of afailure in thearchitecture ofthe systemconfiguration.Check theconfiguration ofthe entirenetwork.

not Recovery

pf6000sPthctlFlowEntFullRecovNoR

FlowEntry FullRecovery

FlowEntry FullRecoveryofs=<value>

The flow settingshave beensuccessfullyspecified for ofs=<value>, andthe settingsoverflow hasbeen recovered.

None.

war Occurrence

pf6000sPthctlOFSDomMissLinkOWaO

OFS DomainMiss LinkOccurred

OFS DomainMiss LinkOccurreddomain1=<value>ofs1=<value>port1=<value>domain2=<value>ofs2=<value>port2=<value>

Themisconnectionlink between theOFS domain ofdomain1=<value> and the OFSdomain ofdomain2=<value> has occurred.

A link spanningOFS domains isbeingautomaticallydetected.Run the show ofs-domaincommand toconfirm OFSdomain settingsof OFSs withofs1=<value>andofs2=<value>,and confirm


65

Levelof

Importance


(Summary)


connection toport1=<value> ofofs1=<value>andport2=<value> ofofs2=<value>.To intentionallyconnect multipleOFSs foroperation, run theshow trunk-port and show ofs commands toconfirm MCLAGmember portsetting orexternal portsetting forport1=<value> ofofs1=<value>andport2=<value> ofofs2=<value>.

not Recovery

pf6000sPthctlOFSDomMissLinkRNoR

OFS DomainMiss LinkRecovery

OFS DomainMiss LinkRecoverydomain1=<value>ofs1=<value>port1=<value>domain2=<value>ofs2=<value>port2=<value>

Themisconnectionlinke betweenthe OFS domainofdomain1=<value> and the OFSdomain ofdomain2=<value> has recovered.

None.

war Occurrence

pf6000sPthctlSubdomMissLinkOWaO

Subdomain MissLink Occurred

OFS SubdomainMiss LinkOccurreddomain=<value>sub1=<value>ofs1=<value>port1=<value>sub2=<value>ofs2=<value>port2=<value>

A misconnectionlink between theOFS subdomainor OFS coredomain ofsub1=<value>and the OFSsubdomain ofsub2=<value>occurred.

A link spanningOFS subdomainsor a connectionbetween OFScore domain andOFS subdomainvia a port withoutOFS subdomaingateway setting isbeingautomaticallydetected. Run theshow ofs-domain command toconfirm thesubdomainaffiliationsettings ofport1=<value>withofs1=<value>


66

Levelof

Importance


(Summary)


andport2=<value>withofs2=<value>,the OFSsubdomaingateway settingof port1=<value>withofs1=<value>,and a confirmconnection toport1=<value>withofs1=<value>and a connectionto port2=<value>withofs2=<value>.

not Recovery

pf6000sPthctlSubdomMissLinkRNoR

Subdomain MissLink Recovery

OFS SubdomainMiss LinkRecoverydomain=<value>sub1=<value>ofs1=<value>port1=<value>sub2=<value>ofs2=<value>port2=<value>

Themisconnectionlink between theOFS subdomainor OFS coredomain ofsub1=<value>and the OFSsubdomain ofsub2=<value>has recovered.

None.

war Occurrence

pf6000sPthctlCoreDomainSplitWaO

OFS CoreDomain Split

Broadcast OFSCore DomainSplitdomain=<value>

The broadcastdelivery networkof the OFSdomain ofdomain=<value>is disconnected.

A split in thePFC network hasoccurred in theOFS domain.Confirm OFSsthat belong to theOFS core domainof the OFSdomain, and OFSdomain affiliationsettings via the show ofs-domain command,confirm thetopology of theconnectionbetween the OFSand PFC, and thestate ofconnectionbetween OFSs.


67

Levelof

Importance


(Summary)


not Recovery

pf6000sPthctlCoreDomainRecovNoR

OFS CoreDomainRecovery

Broadcast OFSCore DomainRecoverydomain=<value>

Disconnection ofthe broadcastdelivery networkof the OFSdomain ofdomain=<value>is recovered.

None.

war Occurrence

pf6000sPthctlSubdomainSplitWaO

OFS SubdomainSplit

Broadcast OFSSubdomainSplitdomain=<value>subdomain=<value>

The broadcastdelivery networkof the OFSsubdomain ofsubdomain=<value> in the OFSdomain ofdomain=<value>is disconnected.

A split in thePFC network hasoccurred in theOFS domain.Run the show ofs-domaincommand toconfirm OFSsthat belong to theOFS subdomainand OFSsubdomainaffiliationsetting/OFSsubdomaingateway settingstatus, andconnect OFS andPFC in the OFSsubdomain. Then,confirm topologyof connectionstatus betweenOFSs, andconnect OFSsubdomaingateway port.

not Recovery

pf6000sPthctlSubdomainRecovNoR

OFS SubdomainRecovery

Broadcast OFSSubdomainRecoverydomain=<value>subdomain=<value>

The broadcastdelivery networkof the OFSsubdomain ofsubdomain=<value> in the OFSdomain ofdomain=<value>has recovered.

None.

war Occurrence

pf6000sOfcmOFSSecChanDisconWaO

OFSSecureChannelDisconnect

OFSSecureChannelDisconnectofs=<value>

The OFS of ofs=<value> hasbeendisconnected.

There is apossibility that afailure hasoccurred in theOpenFlownetwork. Checkthe network.

not Recovery

pf6000sOfcmOFSSecChanConNoR

OFSSecureChannelConnect

OFSSecureChannelConnect

The OFS of ofs=<value> has

None.


68

Levelof

Importance


(Summary)


ofs=<value> beenreconnected.

war Occurrence

pf6000sOfcmOFSPortLinkDownWaO

OFS PortLinkDown

OFS PortLinkDownofs=<value>port=<value>

The status of theport of port=<value> of theOFS of ofs=<value> is linkdown.The port willrecover from thisalarm if thesecure channel tothe OFS to whichit belongs isdisconnected.

There is apossibility that afailure in theOpenFlownetwork hasoccurred. Checkthe network

not Recovery

pf6000sOfcmOFSPortLinkUpNoR

OFS Port LinkUp OFS Port LinkUpofs=<value>port=<value>

The status of theport of port=<value> of theOFS of ofs=<value> is link up.

None.

inf Notification

pf6000sPfcshLoginInN

Login LoginUSER:<user>TTY:<tty> from<ipaddress>.

The user haslogged on to thePFC shell.

None.

inf Notification

pf6000sPfcshLogoutInN

Logout (1) NormalCommandLogoutUSER:<user>TTY:<tty> from<ipaddress>.(2) ForceCommandClear loginsession <session-id> byUSER:<user>TTY:<tty> from<ipaddress>.(3) TimeoutTimeoutUSER:<user>TTY:<tty> from<ipaddress>.

The user haslogged off fromthe PFC shell.

None.

not Notification

pf6000sPfcshLoginFailureNoN

Login Failure Login failureUSER:<user>TTY:<tty> from<ipaddress>.

The user hasfailed to log onto the PFC shell.

None.

inf Notification

pf6000sPfcshconfCommitSuccessInN

Commit Success Commitsucceeded by

Execution of thecommitcommand by the

None.


69

Levelof

Importance


(Summary)


USER:<user>TTY:<tty>.

user wassuccessful.

cri Notification

pf6000sCsmClusterFailureCrN

- - The daemonmanaging thecluster hasdetected anabnormal state.

If the server isnot automaticallyrestarted, or if thecluster does notstart correctlyafter the serverhas restarted, takeaction accordingto ClusterTrouble in theTroubleshootingGuide.

inf Notification

pf6000sCsmClusterSwitchoverInN

- - Clusterswitchover hasbeen started byexecution of thepfc_switch_clustercommand.

None.

not Notification

pf6000sCsmClusterSwitchoverSsNoN

- - Clusterswitchoverstarted byexecution of thepfc_switch_cluster commandwas successful.

None.

not Notification

pf6000sCsmClusterSwitchoverFlNoN

- - Clusterswitchoverstarted byexecution of thepfc_switch_cluster commandhas failed.

A node that isnormal switchedover to the activenode. For how toreference thecluster state, refertopfc_show_cluster_status in theCommandReference. Checkthe cause of theclusterswitchoverfailure bychecking thealarms, etc.

not Notification

pf6000sCsmClusterTransitionNoN

- - The cluster stateof the local nodehas changed to <state>.

None.

inf Notification

pf6000sCsmStartUpgradeFinalInN

- - Softwareupgradefinalization has

None.


70

Levelof

Importance


(Summary)


been started byexecution of thepfc_upgradecommand.

not Notification

pf6000sCsmCompUpgradeFinalNoN

- - Softwareupgradefinalization onthe local node iscomplete.

None.

war Occurrence

pf6000sPombasePolicerFullOccuWaO

Policer resourcefull Occurred

Failure in a setupof Policer by OFSresource full.ofs=<DPID>port=<PortName>policer=<VTNName>,<vNodeName>policer_seqnum=<SeqNum>

The Policersetting (thesetting in whichthe sequencenumber <SeqNum> is set for <VTN Name><vNodeName> (for aPolicer set toVTN, vNodeName is anempty string))failed to be inputfor the physicalport name <PortName> of theOFS with aDPID of <DPID>due toinsufficient OFSresources.


not Recovery

pf6000sPombasePolicerFullRecvNoR

Policer resourcefull Recovery

FailedPolicer(Resourcefull) has beendeleted.ofs=<DPID>port=<PortName>policer=<VTNName>,<vNodeName>policer_seqnum=<SeqNum>

The Policersetting (thesetting of theentry whosesequence number<SeqNum> is setfor <VTN Name><vNode Name>(for a Policer setto VTN, vNodeName is anempty string))failed due toinsufficientresources for thephysical portname <PortName> of the OFSwith a DPID of <DPID> has beendeleted.

None.


71

Levelof

Importance


(Summary)


war Occurrence

pf6000sPombasePolicerFailOccuWaO

Failure in a setupof Policer

Failure in a setupof Policer.ofs=<DPID>port=<PortName>policer=<VTNName>,<vNodeName>policer_seqnum=<SeqNum>

The Policersetting (thesetting of theentry whosesequence number<SeqNum> is setfor <VTN Name><vNode Name>(for a Policer setto VTN, vNodeName is emptystring)) failed tobe input to thephysical portname <PortName> of the OFSwith a DPID of <DPID>.

Delete thecorrespondingpolicing mapsetting by usingthe PFC shell,and then performthe setting again.

not Recovery

pf6000sPombasePolicerFailRecvNoR

Failed Policerwas deleted

FailedPolicer(Settingfailure) has beendeleted.ofs=<DPID>port=<PortName>policer=<VTNName>,<vNodeName>policer_seqnum=<SeqNum>

The Policersetting (thesetting of theentry whosesequence number<SeqNum> is setfor <VTN Name><vNode Name>(for a Policer setto VTN, vNodeName is emptystring)) failed tobe set for thephysical portname <PortName> of the OFSwith a DPID of <DPID> has beendeleted.

None.

war Occurrence

pf6000sPombaseFilterFailOccuWaO

Failure in a setupof SafeFlowEntry

Failure in a setupof SafeFlowEntryofs=<DPID>port=<PortName>flowentry=<VTNName>,<vExternal Name>priority=<priority>entry-id=<entry-id>status=down

ApplyingSafeFlowEntrysetting tophysical port<PortName> ofOFS where dpidis <DPID> isfailed (By failingeven oneSafeFlowEntrysetting, theconfigurationinformationunder flow-filter-safe/priority<priority-id>/entry-id<id>

Delete theexistingSafeFlowEntrysetting by usingPFCShell, andthen specify thesetting again.


72

Levelof

Importance


(Summary)


specified for<VTNName><vExternal Name>becomes invalid,and allSafeFlowEntriesgenerated by thisinformation aredeleted.)

not Recovery

pf6000sPombaseFilterFailRecvNoR

FailedSafeFlowEntrywas deleted

FailedSafeFlowEntry(Setting failure) hasbeen deleted.ofs=<DPID>port=<PortName>flowentry=<VTNName>,<vExternal Name>priority=<priority >entry-id=<entry-id>status=down

SafeFlowEntrysetting whichfailed to beapplied to thephysical port<PortName> ofOFS where dpidis <DPID> hasbeen deleted.(When any ofsettinginformation ofmatch and actionunder flow-filter-safe/priority<priority-id>/entry-id<id>specified for<VTNName><vExternal Name> isdeleted, thealarm isreleased.)

None.

war Occurrence

pf6000sPombaseFilterFullOccuWaO

SafeFlowEntryresource fullOccurred

Failure in a setupof SafeFlowEntryby OFS resourcefull.ofs=<DPID>port=<PortName>flowentry=<VTNName>,<vExternal Name>priority=<priority>entry-id=<entry-id>status=down

ApplyingSafeFlowEntrysetting to thephysical port<PortName> ofOFS where dpidis <DPID> isfailed due toresourceshortage.(Once failed toapplySafeFlowEntrysetting, theconfigurationinformationunder flow-filter-safe/priority<priority-id>/entry-id<id>



73

Levelof

Importance


(Summary)


specified for<VTNName><vExternal Name> isinvalid, and allSafeFlowEntriesgenerated by thisinformation aredeleted.)

not Recovery

pf6000sPombaseFilterFullRecvNoR

SafeFlowEntryresource fullRecovery

FailedSafeFlowEntry(Resource full)has been deleted.ofs=<DPID>port=<PortName>flowentry=<VTNName>,<vExternal Name>priority=<priority>entry-id=<entry-id>status=down

SafeFlowEntrysetting whichfailed to beapplied to thephysical port<PortName> ofOFS where dpidis <DPID> hasbeen deleted.(<When any ofsettinginformation ofmatch and actionunder flow-filter-safe/priority<priority-id>/entry-id<id>specified for<VTNName><vExternal Name> isdeleted, thealarm isreleased.)

None.

cri Occurrence

pf6000sLicLicenseExpiredCrO

PFC license hasexpired

PFC license hasexpired. Pleaseupdate license.

The license hasexpired.

Check the licenseinformation, andrenew thelicenses that haveexpired.Refer topfc_licmgt list inthe CommandReference forhow to check thelicenseinformation.

cri Notification

pf6000sLicLicenseExpiredCrN

PFC license hasexpired

PFC license hasexpired. Pleaseupdate license.

The license hasexpired.

Check the licenseinformation, andrenew thelicenses that haveexpired.Refer topfc_licmgt list inthe CommandReference for


74

Levelof

Importance


(Summary)


how to check thelicenseinformation.

war Occurrence

pf6000sLicLicenseWillExpireWaO

PFC license willexpire

PFC license willexpire at %Y-%m-%d %H:%M:%S. Please updatelicense.

The expiry datefor the license isapproaching.

Check the licenseinformation, andrenew thelicenses.Refer topfc_licmgt list inthe CommandReference forhow to check thelicenseinformation.

war Notification

pf6000sLicLicenseWillExpireWaN

PFC license willexpire

PFC license willexpire at %Y-%m-%d %H:%M:%S. Please updatelicense.

The expiry datefor the License isapproaching.

Check the licenseinformation, andrenew thelicenses.Refer topfc_licmgt list inthe CommandReference forhow to check thelicenseinformation.

not Recovery

pf6000sLicLicenseValidatedNoR

PFC license hasbeen validated

All PFC licenseshave beensuccessfullyvalidated.

The licenseshave beenrenewed, and alllicenses havebeen successfullyauthenticated.

None.

war Occurrence

pf6000sPomnmNWMonGrpFaultWaO

Network MonitorGroup Fault

The state of thenetwork-monitor-group <groupname> haschanged fault.

The system haswitched to thefail status asthere was noresponse fromany of themonitored hostson the network-monitor-group<group name>.The flow filterentries set by <group name>will be disabled.The routing tablefor the vRouterset by <group name> will bedisabled.

Investigate whatcaused themonitored hoststo not respond,and performrecovery if thereis a failure.


75

Levelof

Importance


(Summary)


not Recovery

pf6000sPomnmNWMonGrpRecoveryNoR

(1) NetworkMonitor GroupRecovery(2) NetworkMonitor GroupCancel

(1) The state ofthe network-monitor-group<group name>was recovered.(2) The state ofthe network-monitor-group<group name>was canceled.

(1) The systemhas switched tothe recoverystatus as therewas a responsefrom themonitored hostson the network-monitor-group<group name>.(2) Disabled thenetwork-monitor-group <group name> in thefail status by theno enablecommand. (Theflow filter entriesset by <group name> will beenabled.The routing tablefor the vRouterset by <group name> will beenabled.)

(1) None.(2) Whenwishing to re-enable thedisabled networkmonitor group,execute theenable command.

war Occurrence

pf6000sTmPortDirectionNGWaO

Port direction isinconsistent

Port direction isinconsistentDPID:<value>(ofs: <value>)(trunk-port)PortName:<value>

Detected that theconnection statusof the said port isdifferent fromthe settings.

Check theconnection statusof the port andthe settings (ofsand trunk-porton the PFC Shell)and correct theproblem with theconnection or thesettings.

not Recovery

pf6000sTmPortDirectionOKNoR

Port direction isconsistent

Port direction isconsistentDPID:<value>(ofs: <value>)(trunk-port)PortName:<value>

Detected that theconnection statusof the said port isconsistent withthe settings.

None.

war Occurrence

pf6000sTrmonPortCongesOccurWaO

OFS PortCongestionOccurred

OFS PortCongestionOccurredofs=<value>port=<value>

As the traffic ofport=<value>of the OFS of ofs=<value> hasincreased, theport has enteredin a state ofcongestion.

It is possible thatthere is a largeamount of trafficon the OpenFlownetwork. Checkthe network


76

Levelof

Importance


(Summary)


not Recovery

pf6000sTrmonPortCongesRecovNoR

OFS PortCongestionRecovered

OFS PortCongestionRecoveredofs=<value>port=<value>

The congestionstate of port=<value> of theOFS of ofs=<value> has beenrecovered.

None.

ale Occurrence

pf6000sOfsmOFSLackOfFeaturesAlO

OFS is lack offeatures

OFS is lack offeaturesofs=<value>

The OFS doesnot havesufficientfeatures tooperate the PFCfeatures.

Check the detailsof the lackingOFS features byusing the show ofs features detail command,and takeappropriateaction. Fordetails, refer toshow ofs featuresin the CommandReference.

cri Occurrence

pf6000sOfsmOFSLackOfFeaturesCrO





err Occurrence

pf6000sOfsmOFSLackOfFeaturesErO





war Occurrence

pf6000sOfsmOFSLackOfFeaturesWaO




Check the detailsof the lackingOFS features byusing the show ofs features detail command,and takeappropriate


77

Levelof

Importance


(Summary)


action. Fordetails, refer toshow ofs featuresin the CommandReference.

not Recovery

pf6000sOfsmOFSLackOfFeaturesNoR

OFS hasrecovered lack offeatures

OFS hasrecovered lack offeaturesofs=<value>

The OFSfeatures are nolonger lacking.

None.

not Occurrence

pf6000sOfsmOFSLackOfFeaturesNoO





inf Occurrence

pf6000sOfsmOFSLackOfFeaturesInO





war Occurrence

pf6000sOfsmLicenseExceededWaO

License exceeded The number ofactivated licenseshas exceeded thelimit.type=<type>ofs=<dpid>peer=<ipaddr>:<port>

A shortage ofOFS licenses hasoccurred.

Execute the showlicense ofs rejected-ofscommand, andthen disconnectthe securechannel for theindicated OFS.Afterdisconnecting thesecure channel,execute the clear license rejected-ofscommand.Then, purchaseand install thelicense, and then


78

Levelof

Importance


(Summary)


reconnect thesecure channelfor the OFS.

not Recovery

pf6000sOfsmLicenseExceededNoR

Excess of licensewas cleared

Excess of theactivated numberof licenses wascleared.type=<type>

The clear license rejected-ofs commandhas been used toclear theinformation forthe OFS forwhichconnection wasrejected becausethe number oflicenses wasexceeded.

None.

not Occurrence

pf6000sIfmLinkDownRelayNoO

Link Down Relay Link Down Relaypolicy_name=<policy_name>

Link DownRelay hasoccurred.

None.

not Recovery

pf6000sIfmLDRRecoveryNoR

(1) Link DownRelay Recovery(2) Link DownRelay ForceRecovery

(1) Link DownRelay Recoverypolicy_name=<policy_name>(2) Link DownRelay ForcedRecoverypolicy_name=<policy_name>

(1) Recoveryfrom Link DownRelay.(2) Forcedrecovery fromLink DownRelay.

None.

war Occurrence

pf6000sIfmEthCcMAFaultWaO

ETH-CC MAFault

ETH-CC MAFaultmd_name=<md_name>ma_name=<ma_name>

MA failure hasoccurred.

MA informationis now abnormaldue to a problemof OFS. Executethe show ethernet-cfm faultstatuscommand tocheck MAinformation of<md_name> and<ma_name>. Bychecking the OFSsettings makingup the MAinformation,resolve theproblems of OFS.Disconnect theappropriate OFSfrom theOpenFlownetwork, and thenconnect it to the


79

Levelof

Importance


(Summary)


OpenFlownetwork again.For details abouthow to connect ordisconnect theOFS to/from theOpenFlownetwork, refer to(1) Disconnectsthe operatingOFS from thenetwork and (2)Procedures forreconnecting theOFS to thenetwork ofProcedures forchanging theconfiguration ofan OFS duringoperation in theConfigurationGuide.

not Recovery

pf6000sIfmEthCcMAFaultRecovNoR

ETH-CC MARecovery

ETH-CC MAFault Recoverymd_name=<md_name>ma_name=<ma_name>

MA failure hasbeen recovered.

None.

war Occurrence

pf6000sFemonAboveThresholdWaO

Flow entry abovethreshold

Flow entry aboverising threshold.ofs=<dpid>target=<target>risingthreshold=<threshold>

The number offlow entriesregistered for theOFS hasexceeded thethreshold valuefor alarmgeneration.

Execute the showlicense ofs rejected-ofscommand, andthen disconnectthe securechannel for theindicated OFS.Afterdisconnecting thesecure channel,execute the clear license rejected-ofscommand.Then, purchaseand install thelicense, and thenreconnect thesecure channelfor the OFS.

not Recovery

pf6000sFemonAboveThresholdNoR

(1) Flow entrybelow threshold

(1) Flow entrybelow threshold.ofs=<dpid>

(1) The numberof flow entriesregistered for the

None.


80

Levelof

Importance


(Summary)


(2) Flow entrymonitor canceled(3) Securechannel wasdisconnected

target=<target>fallingthreshold=<threshold>(2) Flow entrymonitor canceled.ofs=<dpid>target=<target>(3) Securechannel wasdisconnected.ofs=<dpid>target=<target>

OFS has fallenbelow thethreshold valuefor recoveryfrom alarm.(2) OFS flowentry countmonitoring hasbeen canceled.(3) OFS flowentry countmonitoring hasbeen canceledbecause the OFShas beendisconnected.

war Occurrence

pf6000sFemonMonitorStopWaO

Flow entrymonitor stopped

Flow entrymonitor stoppedbecause there istarget that can notbe monitored.ofs=<dpid>target=<target>ofsmodel=<model>

OFS flow entrycount monitoringhas stopped.

Execute the flowentry countmonitoringsetting commandwith the correcttargets specified.

not Recovery

pf6000sFemonMonitorStopNoR

(1) Flow entrymonitor started(2) Flow entrymonitor canceled(3) Securechannel wasdisconnected

(1) Flow entrymonitor started.ofs=<dpid>(2) Flow entrymonitor canceled.ofs=<dpid>(3) Securechannel wasdisconnected.ofs=<dpid>

(1) OFS flowentry countmonitoring hasstarted.(2) OFS flowentry countmonitoring hasbeen canceled.(3) OFS flowentry countmonitoring hasbeen canceledbecause the OFShas beendisconnected.

None.

war Occurrence

pf6000sPfvlanVlanMisconfigWaO

VLAN MisconfigOccurred

VLAN MisconfigOccurredofs=<value>port=<value>

Becauseautomatic VLANsetting for theport=<value> ofthe OFS ofofs=<value> hasfailed or theVLAN settingshave beenchanged from theCLI of the OFS,the VLAN

There may be anerror in the OFSsettings. Takecorrective actionaccording to theTroubleshootingGuide.


81

Levelof

Importance


(Summary)


settings mayhave becomeinvalid.

not Recovery

pf6000sPfvlanVlanConfRecoveryNoR

VLAN MisconfigRecovered

VLAN MisconfigRecoveredofs=<value>port=<value>

VLAN settingfor theport=<value> ofthe OFS ofofs=<value> hasbeen retried tocorrect theVLAN settings.

None.

not Notification

pf6000sMacmapMACFilterNoticeNoN

Denied by mac-filter

Denied by mac-filter. MACaddress=<MACaddress>

mac-filter deniedmapping for thehost connected tothe OFS.

Set mac-filter toallow connectionfor the hostconnected to theOFS.

not Notification

pf6000sMacmapMACMapNoticeNoN

Denied by mac-map

Denied by mac-map. MACaddress=<MACaddress>

mac-map deniedmapping for thehost connected tothe OFS.

Set mac-map toallow connectionfor the hostconnected to theOFS.


82

IndexAACT..........................................................................7Active Node.......................................................... 8,9Audit................................................................. 30,31

BBroadcast................................................................34

CCluster......................................................... 6,7,17,70CLUSTERPRO.....................................................6,7ClusterStateManager......................................... 3-5,8Component name.................................................. 1,2Congestion Status..............................................76,77

DDPID, dpid......................... 29-34,36,37,40,46-48,76

EEdgeNode..........................................................32,33

FFailover............................................................ 6,7,48

IIdentifier................................................................1,2

LLevel........................................................................ 2License................................................. 1,49,50,74,75Link Down........................................................ 23,57Link Status........................................................21-23Link Up............................................................. 22,57

MMirror Break.......................................................... 10

NNetwork Monitor Group......................... 24,25,75,76NodeManager................................................... 16-20

OOFCM............................................................... 68,69OFS.................... ii,2,29,30,32-34,46-48,68,69,76,77

PPath Control................................................ ii,1,32,33PFC Shell..................................................... 46,47,76Port Down.............................................................. 45pthctl......................................................... 1,31-37,40Push Mode............................................................. 36

RRestart Level...........................................57,58,60-64

Ssecure channel..............................................46-48,68Split brain syndrome................................................ 6syslog format............................................................1

TTrap................................................................ ii,20,56

UU-code...............................................................49,50

VVTN............................................................. 32,33,57

83

PF6800 Ver. 6.0Log Message Reference

PFC00EG0600-01

July, 2014 1st Edition

NEC Corporation

©NEC Corporation 2011-2014

PF6800 Ver. 6.0 Log Message Reference · PFC.ifm IFM PFC interface management function PFC.pfvlan...

Documents

Transcript of PF6800 Ver. 6.0 Log Message Reference · PFC.ifm IFM PFC interface management function PFC.pfvlan...