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

Best (Public) VMware NSX Learning Resources

Let me qualify the title.. I say “best” with the full authority that my opinion carries.  Just trying to give y’all a place to go to get your NSX learn on…

Digital Literature …

VMware Product Walkthroughs – NSX 

The NSX walkthrough is the perfected balance the brevity of a presentation slide-deck with involved hands-on demonstrations.  Very well put together (Check out some of the other walkthroughs).

VMware NSX Design Guide 

The design guide is a PDF~30 pages is a gentle introduction to NSX topologies.  Fundamental read if you’re still trying to get a handle on NSX concepts. 

VMware Network Virtualization Blog

Subject matter content from the experts.  Posts by Martin Casado, Bruce Davie, Brad HedlundRoger Fortier.

VMware Hands on Labs (HOL) Focus: Networking

Get acquainted with NSX Dynamic Routing, the Distributed Firewall & Load Balancing.

VMware NSX 6 Documentation Center

Nothing fancy about this one… ’tis the manuals.  NSX Install and Upgrade Guide & NSX Administration Guide.  Although in the public domain, this resource is extremely difficult (if not impossible) to find via search.  But they are in the public domain.  Whatever is public is not private…right?  

Martin Casado’s Blog – Network Heresy

Scott Lowe’s Blog – Learning NVP/NSX 

Brad Hedlund’s Blog – NSX

If videos are the way you learn …

NSX Architecture Webinar by Ivan Pepelnjak on ipspace.net

VMworld 2013 – Introducing the World to VMware NSX (By Sachin Thakkar)

VMware Interview – Bruce Davie on NSX

VMware NSX Demo

This should at the very least provide a fair start for anyone looking to mentally ramp up for the NSX NVP.

– Gabe

vShield/vCNS 5.1x CLI Operations using Expect

The vCNS(vShield) practical CLI use is limited from a configuration perspective, but you may need to interact with these from time to time.  Troubleshooting /debugging sessions/log purging come to mind.

The options for getting the job done:

1.  Interact with the vCNS Manager virtual machine console in vCenter (not great for debugging, or reading the long exception output)

2.  SSH (ssh server is enabled from the console: vsm> enable, vsm# ssh start)

Expect works well with the vtysh pseudo-terminal used for the vCNS Manager console.   I tried and failed (due to errors interacting with the terminal).   If you manage multiple vCNS environments, it makes sense to wrap the interactions into these expect scripts.  Here’s a small example expect script to change the CLI password from the default.

#!/usr/bin/expect -f
# Synop: SSH to vCNS Appliance console. Auth. Enter priv mode. Auth Enter global config. Change the 
# default password.
# SSH <vsm#ip> # enable [enter] # default [enter] # config t [enter]
# cli password %passwword> [enter] # end [enter] # wr mem
#
spawn ssh admin@1.2.3.4
expect "password: "
send "default\r"
expect ">"
send "en\r"
expect "Password: "
send "default\r"
expect "#"
send "config t\r"
expect "#"
send "cli password mYn3wp@ssw0rd\r"
expect "#"
send "\r"
send "exit\r"

If your operational policy is to update your password every few months; you will find yourself revisiting a script like this.  For passing commands to multiple vCNS Managers, you can extend the script to spawn connections based on a list (outside the scope of this post).

@gabe_rosas

GabeNetworkDojo