|
|
|
Service violations detected by SANscreen are classified as:
- Missing Active Host Ports - A path exists between a server and a specific volume, but too few host ports have access to the volume. Performance could be compromised.
- Missing Redundancy - A path exists between a server and a specific volume, but the required dual-fabric redundancy does not exist. The policy specifies that the host must reach the storage device through at least two different fabrics. Because the redundancy level is not met, a single failure could cause downtime.
- Path Outage - According to the current SAN configuration, no path exists between a server and a particular volume, but such a path was previously authorized by SANscreen. The path existed and previously conformed to the applications service policy but is now no longer present. Since the path is now inactive and the server cannot access its data volume, the result is downtime.
- Single Point of Failure - A path exists between a server and a specific volume, but the required no-single point of failure redundancy does not exist. The policy specifies that all SAN devices traversed by this path must be redundant. In this case, path availability is compromised. Any device that’s included in the path could present a single point of failure.
- Switch Hop Count - A path exists between a server and a specific volume, but there are too many switch hops in the path possibly compromising path performance.
- Unauthorized Path - A path exists between a server and a specific volume, but the path is not authorized. This could be the result of a SAN change that inadvertently led to the creation of an invalid path, or it might represent a potential security problem.
- Unauthorized Sharing - The path volume is shared and accessible by too many hosts, in violation of the sharing policy. This unauthorized sharing could turn into application downtime and data corruption.
|
|
|
