ExpressCluster X 2.0 for Windows Reference Guide - Nec

More documents

Recommendations

Info

Chapter 6 Group resource details 392 Note: Exclusion is not performed to the normal and absolute exclusion groups. Normal exclusion is performed only among the normal exclusion groups. Absolute exclusion is performed only among the absolute exclusion groups. In either case, exclusion is not performed with the no-exclusion group. For details on the failover exclusive attribute, see “Understanding failover policy.” - Failover Attribute Set either auto failover or manual failover. In the case of auto failover, failover is automatically performed when a heartbeat is timed out. In the case of manual failover, failover is not automatically performed when a heartbeat is timed out. In that case, perform failover manually by using the WebManager or the clpgrp command. For details on the WebManager, see Chapter 1, “Functions of the WebManager” and for the details of the clpgrp command, see Chapter 4, “ExpressCluster command reference.” Note: Even if the failover attribute is set to the manual failover, the failover is performed automatically when the startup of a group failed or when a monitor resource detected an error. The failover is not performed automatically only when a heartbeat is timed out. - Failback Attribute Set either auto failback or manual failback. In the case of the auto failback, failback will be automatically performed when the server that is given the highest priority is started after a failover. In the case of the manual failback, a failback is not performed even if a server is started. Perform a failback manually by using the WebManager or executing the clpgrp command. For details on the WebManager, see Chapter 1, “Functions of the WebManager, for details on the clpgrp command, see Chapter 4, “ExpressCluster command reference.” A group that registers a mirror disk resource cannot configure the setting of auto failback. - Logical Service Set the logical service name. The logical service is the character string that is used as an identifier when using an application which identifies a group by using the compatible API of ExpressCluster Ver8.0 or earlier. ExpressCluster X 2.0 for Windows Reference Guide
Understanding failover policy Section II Resource details What is a group? A failover policy is a rule that determines a server to be the failover destination from multiple servers, and it is defined by the properties of a group. When you configure the failover policy, avoid making certain servers more heavily loaded at a failover. The following describes how servers behave differently depending on failover policies when a failover occurs using example of the server list that can fail over and failover priority in the list. Server status Description o Normal (properly working as a cluster) od Suspended (not recovered as a cluster yet) × Stopped (cluster is stopped) 3-node configuration: Group Order of server priorities 1 st priority server 2 nd priority server 3 rd priority server A server1 server3 server2 B server2 server3 server1 2-node configuration: Group Order of server priorities 1 st priority server 2 nd priority server A server1 server2 B server2 server1 It is assumed that the group startup attributes are set to auto startup and the failback attributes are set to manual failback for both Group A and B. It is also assumed that the servers are configured not to recover automatically from the status of being suspended. Whether to perform auto recovery from the suspended status is set ON/OFF of Auto Return on the Auto Recovery tab in Cluster Properties. • If groups of different failover exclusive attributes co-exist in a cluster, they do not interfere with each other. For example, a group of full exclusive attributes may start on a server where a group of non-exclusive attributes is active, and vice versa. • For groups whose failover exclusive attributes are normal or full, the server which they start up or fail over is determined by the failover priority to the server. If a group has two or more servers of the same failover priority, it is determined by the order of numbers, the specific symbols and alphabets of the group name. • The failover priority of the WebManager group is determined by the server priority. You can specify server priority on the Master Server tab in Cluster Properties. 393
Page 1 and 2:
ExpressCluster ® X 2.0 for Windows
Page 3:
© Copyright NEC Corporation 2008.
Page 6 and 7:
vi How to verify the status of each
Page 8 and 9:
Network warning light switch off co
Page 10 and 11:
x Service resources................
Page 12 and 13:
xii Displaying NAS monitor resource
Page 14 and 15:
Displaying and changing the details
Page 16 and 17:
xvi IP monitor resource ...........
Page 18 and 19:
ExpressCluster X Documentation Set
Page 20 and 21:
Contacting NEC For the latest produ
Page 23 and 24:
Chapter 1 Functions of the WebManag
Page 25 and 26:
Section I Detailed functions of Exp
Page 27 and 28:
Server Name: Select this to search
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Module type Category pm ExpressClus
Page 59 and 60:
Mirror disk helper Overview of the
Page 61 and 62:
The following is the description of
Page 63 and 64:
For hybrid disk resource Section I
Page 65 and 66:
(6) Current server (only hybrid dis
Page 67 and 68:
Page 69 and 70:
When you click the icon of the serv
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Limitations of the WebManager Secti
Page 79 and 80:
Page 81 and 82:
Error Detected disk error while rec
Page 83 and 84:
Page 85 and 86:
Chapter 2 Functions of the Integrat
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93:
Page 96 and 97:
Chapter 3 Function of the Builder O
Page 98 and 99:
Chapter 3 Function of the Builder D
Page 100 and 101:
Chapter 3 Function of the Builder T
Page 102 and 103:
Chapter 3 Function of the Builder T
Page 104 and 105:
Chapter 3 Function of the Builder 1
Page 106 and 107:
Chapter 3 Function of the Builder U
Page 108 and 109:
Chapter 3 Function of the Builder C
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Chapter 3 Function of the Builder R
Page 118 and 119:
Chapter 3 Function of the Builder P
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Chapter 3 Function of the Builder I
Page 136 and 137:
Page 138 and 139:
Chapter 3 Function of the Builder M
Page 140 and 141:
Chapter 3 Function of the Builder A
Page 142 and 143:
Chapter 3 Function of the Builder R
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Chapter 3 Function of the Builder I
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Chapter 3 Function of the Builder M
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 199 and 200:
Chapter 4 ExpressCluster command re
Page 201 and 202:
Page 203 and 204:
Return Value --grp [group_name] Sec
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Examples of executing the command t
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Status Descriptions Server Function
Page 249 and 250:
Operating the cluster (clpcl comman
Page 251 and 252:
Page 253 and 254:
Message Cause/Solution Internal com
Page 255 and 256:
Page 257 and 258:
Example of Execution The following
Page 259 and 260:
Error message Message Cause/Solutio
Page 261 and 262:
Collecting logs (clplogcc command)
Page 263 and 264:
Execution Result Section I Detailed
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Error Message Section I Detailed fu
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Modifying the log level and size Se
Page 279 and 280:
Types that can be specified for the
Page 281 and 282:
Type Module Description regsyncw cl
Page 283 and 284:
Type Level Size (byte) hdsnapshot 8
Page 285 and 286:
Monitoring Agent Types that can be
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Mirror disk resource operation comm
Page 293 and 294:
Message Cause/Solution clpmdctrl fa
Page 295 and 296:
Error messages Message Causes/Solut
Page 297 and 298:
Page 299 and 300:
Hybrid disk status display command
Page 301 and 302:
Mirror Color Hybrid disk status in
Page 303 and 304:
� Hybrid disk resource configurat
Page 305 and 306:
Page 307 and 308:
Message output command clplogcmd: t
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Error Messages Message Causes/Solut
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
CPU frequency control command clpcp
Page 321 and 322:
Chassis identify control command cl
Page 323 and 324:
Page 325 and 326:
EXEC_SCRIPT IP: Specified script (s
Page 327 and 328:
New password: ********** Retype new
Page 329:
# clphookctrl -m REBOOT Error messa
Page 332 and 333:
Chapter 5 Compatible command refere
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343: Chapter 5 Compatible command refere
Page 389 and 390: Chapter 6 Group resource details Th
Page 391: What is a group? Section II Resourc
Page 395 and 396: X X X When the failover exclusive a
Page 397 and 398: X X ~ For Replicator ~ (two-server
Page 399 and 400: The following describes how an erro
Page 401 and 402: Section II Resource details Failove
Page 403 and 404: Reboot count limit Section II Resou
Page 405 and 406: Max reboot count 1 Current reboot c
Page 407 and 408: Section II Resource details Failove
Page 409 and 410: Section II Resource details Display
Page 411 and 412: Displaying and changing the group a
Page 413 and 414: Section II Resource details Logical
Page 419 and 420: “C:\Program Files\script.bat” S
Page 423 and 424: Status: Status of the resources of
Page 429 and 430: Section II Resource details Resourc
Page 431 and 432: Section II Resource details Underst
Page 433 and 434: Displaying the application resource
Page 435 and 436: Understanding floating IP resources
Page 437 and 438: Notes on floating IP resources Sect
Page 443 and 444:
Understanding mirror disk resources
Page 445 and 446:
Section II Resource details Underst
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Examples of mirror disk constructio
Page 453 and 454:
Page 455 and 456:
Tuning mirror disk resource Section
Page 457 and 458:
Displaying the mirror disk resource
Page 459 and 460:
Understanding registry synchronizat
Page 461 and 462:
Notes on registry synchronization r
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Server 1 Group A 1 Start Stop Group
Page 469 and 470:
Execution timing of script resource
Page 471 and 472:
Environment variables for Start. ba
Page 473 and 474:
Page 475 and 476:
Understanding script resources (6)
Page 477 and 478:
Page 479 and 480:
(10) Stopping Group B The stop scri
Page 481 and 482:
Additional information 1 Section II
Page 483 and 484:
Additional information 2 When a mon
Page 485 and 486:
A. Group A start script: a sample o
Page 487 and 488:
B. Group A stop script: a sample of
Page 489 and 490:
Tips for creating scripts Section I
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Understanding disk resources Depend
Page 497 and 498:
Disk Resource Properties: Details t
Page 499 and 500:
If you click the Details button, th
Page 501 and 502:
Service resource tuning properties
Page 503 and 504:
Page 505 and 506:
Understanding print spooler resourc
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Services available to the virtual c
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Understanding virtual IP resources
Page 521 and 522:
Determining virtual IP address Sect
Page 523 and 524:
Page 525 and 526:
• Timeout (1 to 999999) SuspendRe
Page 527 and 528:
RIPng tab Detailed settings of RIP
Page 529 and 530:
Page 531 and 532:
Understanding CIFS resources Depend
Page 533 and 534:
CIFS resource tuning properties Cac
Page 535 and 536:
Permission Select one of following
Page 537 and 538:
Understanding NAS resources Depende
Page 539 and 540:
NAS resource tuning properties Disc
Page 541 and 542:
Understanding hybrid disk resources
Page 543 and 544:
Hybrid disk resource details tab Se
Page 545 and 546:
Name: Hybrid disk resource name Com
Page 547 and 548:
Chapter 7 Monitor resource details
Page 549 and 550:
Monitor resource name Service monit
Page 551 and 552:
Section II Resource details Disk TU
Page 553 and 554:
esources Tuxedo monitor resources W
Page 555 and 556:
Section II Resource details Monitor
Page 557 and 558:
Monitoring starts after a cluster i
Page 559 and 560:
Public LAN (Also used for Interconn
Page 561 and 562:
Public LAN (Also used for Interconn
Page 563 and 564:
Public LAN (Also used for interconn
Page 565 and 566:
Public LAN (Also used for interconn
Page 567 and 568:
Section II Resource details Monitor
Page 569 and 570:
Returning from monitor error (Norma
Page 571 and 572:
Monitor error occurred Public LAN (
Page 573 and 574:
Activation and deactivation error o
Page 575 and 576:
Section II Resource details Disk re
Page 577 and 578:
Activation failure Section II Resou
Page 579 and 580:
Activation failure Section II Resou
Page 581 and 582:
Delay warning of monitor resources
Page 583 and 584:
appli1 Section II Resource details
Page 585 and 586:
Configuration example Interval 60
Page 587 and 588:
Maximum reboot count 1 Reboot count
Page 589 and 590:
Changing the name of a monitor reso
Page 591 and 592:
Choose servers that execute monitor
Page 593 and 594:
ecovery target. Failover Target Ser
Page 595 and 596:
Replace Section II Resource details
Page 597 and 598:
Page 599 and 600:
Page 601 and 602:
Page 603 and 604:
Page 605 and 606:
Understanding IP monitor resources
Page 607 and 608:
Page 609 and 610:
Page 611 and 612:
Mirror Disk Resource SuspendResume
Page 613 and 614:
Page 615 and 616:
Page 617 and 618:
Page 619 and 620:
NIC Link Up/Down monitor resource p
Page 621 and 622:
Page 623 and 624:
Page 625 and 626:
Warning Threshold · When selected:
Page 627 and 628:
Page 629 and 630:
Page 631 and 632:
Disk TUR monitor resource: disk res
Page 633 and 634:
Service monitor resources monitor s
Page 635 and 636:
Page 637 and 638:
Page 639 and 640:
Page 641 and 642:
CIFS monitor resources monitor CIFS
Page 643 and 644:
Page 645 and 646:
Page 647 and 648:
Understanding hybrid disk monitor r
Page 649 and 650:
Page 651 and 652:
Page 653 and 654:
Page 655 and 656:
Page 657 and 658:
Understanding DB2 monitor resources
Page 659 and 660:
Page 661 and 662:
Monitoring by FTP monitor resources
Page 663 and 664:
Page 665 and 666:
IP Address SuspendResume Section II
Page 667 and 668:
Page 669 and 670:
User Name Within 255 bytes SuspendR
Page 671 and 672:
Page 673 and 674:
Page 675 and 676:
Select the Oracle features to be mo
Page 677 and 678:
Page 679 and 680:
Page 681 and 682:
Section II Resource details Only th
Page 683 and 684:
Understanding POP3 monitor resource
Page 685 and 686:
Authentication Method SuspendResume
Page 687 and 688:
Page 689 and 690:
Page 691 and 692:
Page 693 and 694:
Understanding SQL Server monitor re
Page 695 and 696:
Page 697 and 698:
Page 699 and 700:
Page 701 and 702:
Page 703 and 704:
Install Path Within 1023 bytes Susp
Page 705 and 706:
Page 707 and 708:
Default value: None Section II Reso
Page 709 and 710:
Page 711 and 712:
Page 713 and 714:
Page 715 and 716:
Chapter 8 Heartbeat resources This
Page 717 and 718:
Page 719 and 720:
Chapter 9 Details on network partit
Page 721 and 722:
Page 723 and 724:
Page 725 and 726:
Page 727 and 728:
Page 729 and 730:
PING network partition resolution r
Page 731 and 732:
Page 733 and 734:
Chapter 10 Other monitor settings T
Page 735 and 736:
Section II Resource details The for
Page 737 and 738:
The alarms command option -N [targe
Page 739 and 740:
Mail report actions Section II Reso
Page 741:
Section III Maintenance information
Page 744 and 745:
Chapter 11 The system maintenance i
Page 746 and 747:
Page 748 and 749:
Page 750 and 751:
Page 752 and 753:
Page 754 and 755:
Page 756 and 757:
Page 758 and 759:
Page 760 and 761:
Page 762 and 763:
Page 764 and 765:
Page 766 and 767:
Page 768 and 769:
Page 771 and 772:
Chapter 12 Troubleshooting This cha
Page 773 and 774:
When activating or deactivating net
Page 775 and 776:
Recovering a suspended server (with
Page 777 and 778:
Page 779 and 780:
Page 781 and 782:
Page 783 and 784:
Checking the mirror break status wi
Page 785 and 786:
Page 787 and 788:
3. Logically examine the data on th
Page 789 and 790:
� While mirror recovery is in pro
Page 791 and 792:
Recovering mirror using the WebMana
Page 793:
Page 796 and 797:
Chapter 13 Error messages Messages
Page 798 and 799:
Module Type Chapter 13 Error messag
Page 800 and 801:
Page 802 and 803:
Page 804 and 805:
Page 806 and 807:
Page 808 and 809:
Page 810 and 811:
Page 812 and 813:
Page 814 and 815:
Page 816 and 817:
Page 818 and 819:
Chapter 13 Error messages Driver ev
Page 820 and 821:
Chapter 13 Error messages Module Ty
Page 822 and 823:
Chapter 13 Error messages Mirror di
Page 824 and 825:
Page 826 and 827:
Page 828 and 829:
Chapter 13 Error messages Virtual c
Page 830 and 831:
Page 832 and 833:
Chapter 13 Error messages DB2 monit
Page 834 and 835:
Page 836 and 837:
Page 838 and 839:
Page 840 and 841:
Chapter 13 Error messages IMAP4 mon
Page 842 and 843:
Chapter 13 Error messages Mirror co
Page 844 and 845:
Page 846 and 847:
Page 848 and 849:
Page 850 and 851:
Page 852 and 853:
Chapter 13 Error messages SQL Serve
Page 854 and 855:
Page 856 and 857:
Page 859:
Appendix This section covers: • A
Page 862 and 863:
Appendix A Glossary 862 Mirror conn
Page 864 and 865:
Appendix B Index Displaying and cha
Page 866 and 867:
Appendix B Index Floating IP, 435 F
Page 868:
Appendix B Index Settings of the PI
show all

ExpressCluster X 2.0 for Windows Reference Guide - Nec

Create successful ePaper yourself

Delete template?

Save as template?