Managing Serviceguard Sixteenth Edition, March 2009

Example 1: If Local Switching is Configured
If local switching is configured and a failure is detected by link-level monitoring, output
from cmviewcl -v will look like something like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (Link and IP) 0/3/1/0 lan2
PRIMARY up 0/5/1/0 lan3
cmviewcl -v -f line will report the same failure like this:
node:gary|interface:lan2|status=down
node:gary|interface:lan2|local_switch_peer=lan1
node:gary|interface:lan2|disabled=false
node:gary|interface:lan2|failure_type=link+ip
But if the IP Monitor detects the failure (and link-level monitoring does not) cmviewcl
-v output will look something like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (disabled) (IP only) 0/3/1/0 lan2
PRIMARY up 0/5/1/0 lan3
cmviewcl -v -f line will report the same failure like this:
node:gary|interface:lan2|status=down
node:gary|interface:lan2|local_switch_peer=lan1
node:gary|interface:lan2|disabled=true
node:gary|interface:lan2|failure_type=ip_only
In this case, you would need to re-enable the primary interface on each node after the
link is repaired, using cmmodnet (1m); for example:
cmmodnet —e lan2
Example 2: If There Is No Local Switching
If local switching is not configured and a failure is detected by link-level monitoring,
output from cmviewcl -v will look like something like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (Link and IP) 0/3/1/0 lan2
PRIMARY up 0/5/1/0 lan3
cmviewcl -v -f line will report the same failure like this:
node:gary|interface:lan2|status=down
node:gary|interface:lan2|disabled=false
node:gary|interface:lan2|failure_type=link+ip
If local switching is not configured and a failure is detected by IP monitoring, output
from cmviewcl -v will look like something like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (IP only) 0/3/1/0 lan2
PRIMARY up 0/5/1/0 lan3
How the Network Manager Works 103