System Messages – NSX Edge Services Gateway

[Back to Unofficial System Messages Guide Home]

System Messages – NSX Edge Services Gateway

System Events

CRMD – Cluster Resource Management Daemon

Appname:     cmrd 
Priority:    notice
Message:     run_graph: Transition 6431 (Complete=0, Pending=0, Fired=0, Skipped=0,
             Incomplete=0, Source=/usr/var/lib/pengine/pe-input-6430.bz2): Complete
Explanation: 

Appname:     crmd
Priority:    info 
Message:     do_state_transition: Starting PEngine Recheck Timer
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE
             [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]
Explanation: 

Appname:     crmd
Priority:    info
Message:     notify_crmd: Transition 6431 status: done - 
Explanation: 

Appname:     crmd
Priority:    info
Message:     te_graph_trigger: Transition 6431 is now complete
Explanation: 

Appname:     crmd
Priority:    info
Message:     run_graph: ====================================================
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_te_invoke: Prinfo: Message:     ocessing graph 6431 (ref=pe_calc-
             dc-1406976970-6473) derived from /usr/var/lib/pengine/pe-input-6430.
             bz2
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_te_invoke: Processing graph 6431 (ref=pe_calc-dc-1406976970-6473) 
             derived from /usr/var/lib/pengine/pe-input-6430.bz2
Explanation: 

Appname:     crmd
Priority:    info
Message:     unpack_graph: Unpacked transition 6431: 0 actions in 0 synapses
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_state_transition: State transition S_POLICY_ENGINE -> S_TRANS
             ITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_Message origin=handle_
             response ]
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_pe_invoke_callback: Invoking the PE: query=6517, ref=pe_calc-dc-
             1406976970-6473, seq=8, quorate=1
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_pe_invoke: Query 6517: Requesting the current CIB: S_POLICY_ENGINE
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_state_transition: All 2 cluster nodes are eligible to run resources.
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_state_transition: Progressed to state S_POLICY_ENGINE after C_TIMER
             _POPPED
Explanation: 

Appname:     crmd
Priority:    info
Message:     do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ 
             input=I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]
Explanation: 

Appname:     crmd
Priority:    info
Message:     crm_timer_popped: PEngine Recheck Timer (I_PE_CALC) just popped!
Explanation: 
Advertisements

System Messages – NSX Manager

[Back to Unofficial System Messages Guide Home]

System Messages – NSX Manager

Module vShield Edge Gateway

Code Severity Event Message:
30024 Informational Configuration changed for : [$component] on vShield Edge with id : edge-#

Module vShield Edge Health Check

Code Severity Event Message:
30033 Major VShield Edge VM not responding to health check.
30034 Informational None of the VShield Edge VMs found in serving state. There is a possibility of network disruption.
30042 Informational vShield Edge VM has recovered and now responding to health check.

Module vShield Edge Appliance

Code Severity Event Message:
30152 Informational vShield Edge system time sync up happens

Module vShield Edge HighAvailability

Code Severity Event Message:
30202 High vShield Edge HighAvailability switch over happened. VM has moved to ACTIVE state.
30203 High vShield Edge HighAvailability switch over happened. VM has moved to STANDBY state.

Module vShield Edge IPSec

Code Severity Event Message:
30401 Informational IPsec Channel from localIp : <local-endpoint-ip> to peerIp : <peer-end point-ip> changed the status to up
30402 Informational IPsec Channel from localIp : <local-subnet-ip> to peerIp : <peer-subnet-ip> changed the status to down
30403 Informational IPsec Tunnel from localSubnet : <local-subnet-ip> to peerSubnet : <peer-subnet-ip> changed the status to up
30404 Informational IPsec Tunnel from localSubnet : <local-subnet-ip> to peerSubnet : <peer-subnet-ip> changed the status to down