Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
What API would show affending WWPNs for path misconfigured?
2013-01-11
02:02 PM
3,245 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello..
I have been poking around the APIs with ZExplorer looking for what is at the end of a 'lun config_check -A' command. Namely:
The following FCP Initiators are sending Read/Write i/o over the
FCP Partner Paths during the last 303 seconds
WWPN Partner's Port ops bytes ostype
21:00:00:24:ff:27:dc:80 0c 210296 1720878592 vmware
20:01:e0:db:55:79:e6:69 0c 3677 23773696 vmware
20:01:e0:db:55:79:e6:83 0c 7469 65996288 vmware
21:00:00:24:ff:27:d6:d2 0c 93084 1000456704 vmware
There are a number of other APIs that deal with options for config_check but those do not address the above aspect.
Is there a single or combo of APIs that would get this info?
Appreciate your time.
pdc
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you tried
lun-config-check-info | ] |
Returns a list of lun/fcp configuration warnings. These warnings are not related to filer cluster configuration.
Output Name Range Type Description alua-setting-mismatch-info alua-setting-mismatch-initiator-group[]
optional
list of initiator groups for which the ALUA (Asymmetric Logical Unit Access) settings do not match between local and partner filers. ALUA is a T10 standard that specifies the access characteristics (in terms of performance and supported SCSI commands) of a Logical Unit that can be accessed through more than one target port. ALUA is typically used by host multi-path software to recognize primary and secondary paths to a Logical Unit when more than one path are available to the Logical Unit. If the ALUA setting does not match between the local and partner filers, it would affect the host multi-path software's ability to distingush primary and secondary paths. This could lead to incorrect system behaviour. alua-setting-mismatch-initiators alua-setting-mismatch-initiator-info[]
optional
List of initiators which are members of initiator groups of differing alua settings. fcp-down-hbas fcp-down-hba-info[]
optional
list of HBA names that have no link or are configured down. invalid-vsa-settings invalid-vsa-setting-info[]
optional
List of initiator groups with invalid Volume Set Addressing (VSA) settings mixed-ostype-initiators mixed-ostype-initiator-info[]
optional
List of initiators which are members of initiator groups of differing ostypes. mixed-vsa-initiators mixed-vsa-initiator-info[]
optional
List of initiators which are members of initiator groups with differing Volume Set Addressing (VSA) settings. An initiator can only be a member of initiator groups which have the same VSA setting across all the initiator groups it is a member of.
Errno | Description | |
EINTERNALERROR | ||
EINVAL |
- Rick -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rick..
Yep, went through all of those APIs before posting on a controller that currently lists offending WWPNs in the check_config CLI output and none of those APIs correlated to the output of the CLI command.
Thanks.
pdc
