the ability administer windows 2008 failover clustering improved on windows 2003 failover clustering (single copy clustering exchange 2007 system engineers). since intent post number of subsequent blog entries on windows 2008 failover clustering thought offer introduction several of administrative consoles windows 2008 failover clustering referenced @ future time. in entry not using windows powershell failover cluster administration. intent offer insights powershell @ future time.
i outline complete installation of 2-node windows 2008 failover cluster several blog entries planned coming weeks steps long, not point of being worrisome. find 30 screen captures in post 'just right' working professionals, consultants, system engineers , architects.
figure 1 - using windows 2008 x64 enterprise edition 2 node failover cluster introduction. analysis of screen captures confirms use of 2 nics (public , private) on 2 separate ip subnets. additionally, the user context user has ability modify computer security principals in organizational unit (ou) default computers placed in windows 2008 active directory. important consideration move forward way 'computer accounts' created cluster service differs windows 2003 active directory. useful modification there no more requirement 'cluster service account' in windows 2008 failover clustering!
figure 2 - 'dig in' configuration should versed in network configuration both nics/hbas failover clustering. also, ipv6 integral part of windows 2008. notice have 'turned off' ipv6 functionality on these 2 nics.
figure 3 - here nic details viewed through failover cluster management console. failover cluster management console primary 'graphical' mechanism installing, configuring , maintaining windows 2008 failover cluster. observe ease can view network connections node. have focused screen capture on 'public_network' associated nics each individual cluster node (b01-node-1 , b01-node-2).
figure 4 - here focus on 'private_network' used cluster node heartbeat. using interface can define 'what traffic type' each network (either public or private) carries. options include 'private only' (for cluster heartbeat traffic) , 'public' (client connection traffic , storage traffic) , final option being 'mixed' (which includes both client traffic , cluster heartbeat traffic).
figure 5 - failover cluster management console focus on cluster defined in 2 node failover configuration (cluster name 'app-cluster-01.corp.itpslab.local'). have pointed out many of salient data points perspective. summary includes (moving left right): 1) cluster node name (app-cluster-01.corp.itpslab.local), 2) quorum configuration - 'node , disk majority using defined quorum drive', 3) current host server (b01-node-1.corp.itpslab.local) , 4) subnets defined configuration (all ipv4).
figure 6 - if had defined 'cluster aware applications' see detail in console screen. defined in another, future blog entry. suffice say, 'services , applications' 'heart' of maintaining cluster aware applications on failover cluster.
figure 7 - 'node' leaf provides summary information each cluster node in configuration. 2 nodes support failover cluster (b01-node-1 , b01-node-2).
figure 8 - 'storage' leaf provides detailed information regarding storage available in cluster configuration. summary information of 'storage', 'total capacity' , 'available capacity' provide useful, concise reporting information.
figure 9 - reviewed of detail regarding 'networks' in prior figure (figure 2 , 3). again, summary detail (whether device 'up' or 'down') useful observing health of cluster components.
figure 10 - when select cluster name , 'right mouse click' detailed menu of actions visible. notably 'fly out menu' 'view validation report' and, 'configure cluster quorum settings'.
figure 11 - selection of 'services , applications' leaf, associated 'right mouse click' generates 'fly out menu' option 'configure service or application'. again, 1 way of manually adding service (such clustered dhcp) or application.
figure 12 - selection of 'node' leaf provides option 'add nodes' cluster.
figure 13 - selecting 'storage' leaf provides rich information specific storage configuration cluster. notice in both 'fly out menu' , 'action pane' (upper right corner) can 'add disk' on fly.
figure 14 - useful console administering windows 2008 failover cluster services server manager. new event trace session application available logging detailed event data failover clustering services , devices.
figure 15 - here reinforce depth of capabilities command line install, configure , administer windows 2008 failover cluster. issuing 'cluster res' command (cluster resource) provides quick summary of cluster status.
figure 16 - issuing 'cluster group /prop' command (cluster group properties) provides details cluster group. since no application or service defined see details of available storage , state cluster configuration.
figure 17 - next invoke sequence of command line commands modify failover cluster configuration. sequence 1) 'cluster group' (to understand node controls group items), 2) 'cluster group "available storage: /move' (wo move 'available storage' node 1 node 3), , finally, 'cluster group' (again, view node controls group items).
figure 18 - moving 'failover cluster management console', remiss not point out 'validate configuration' wizard 'management section' of console. inevitably, has of challenging 'software engineering' in windows 2008 failover clustering. not challenging , i, end consumer, challenging software developers wizard queries, populates , defines 100s of data points. in effort make windows 2008 failover clustering more 'straight forward' system engineers , i!
figure 19 - previously, validated both cluster nodes (b01-node-1 , b01-node-2). can review last validation report 'fly out menu' off 'cluster name' in failover cluster management console.
figure 20 - here first screen of 'failover cluster validation report'. inventory of hardware comprising cluster nodes.
figure 21 - additional detail of 'failover cluster validation report'. these specifics of 'network' , 'storage' components.
figure 22 - finally, (although actual detail defined in report also) can see specifics of 'system configuration'. there comparison of patches applied each individual cluster node.
figure 23 - main 'failover cluster management console' windows 2008 failover clustering.
summary: in blog entry review several of primary windows 2008 failover clustering administrative consoles. consoles reviewed here include 1) using failover cluster management console , 2) using command line cluster administration. blog entry introduces several of administrative interfaces reference in future blog entries.
video lessons on windows 2008 sp2 failover cluster nodes highly available file services- http://www.exchangesummit.net
Comments
Post a Comment