What is the RHIstate setting in the vServer configuration?

What is the RHIstate setting in the vServer configuration?

• A. ACTIVE
• B. PASSIVE
• C. NEGATIVE
• D. ENABLED

Answer: (B)

The setting controls how the vServer participates in health information handling. When it is set to PASSIVE, the vServer does not actively perform its own health probes; instead, it relies on external health signals or monitoring sources to determine backend health. This is useful when you want to minimize probe traffic or delegate health decisions to a central monitor or upstream system. The other options describe behavior you wouldn’t want if your goal is not to generate or rely on active health probes—ACTIVE would mean the vServer actively checks health itself, while NEGATIVE isn’t a meaningful health-state in this context, and ENABLED does not specify the passive/active health probing mode.

The setting controls how the vServer participates in health information handling. When it is set to PASSIVE, the vServer does not actively perform its own health probes; instead, it relies on external health signals or monitoring sources to determine backend health. This is useful when you want to minimize probe traffic or delegate health decisions to a central monitor or upstream system. The other options describe behavior you wouldn’t want if your goal is not to generate or rely on active health probes—ACTIVE would mean the vServer actively checks health itself, while NEGATIVE isn’t a meaningful health-state in this context, and ENABLED does not specify the passive/active health probing mode.