Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

fcnsq(8) [centos man page]

FCNSQ(8)							  Open-FCoE Tools							  FCNSQ(8)

NAME
fcnsq - Fibre Channel Name Server Query Tool SYNOPSIS
fcnsq host --gpn port_id [-q | --quiet] fcnsq host --gnn port_id [-q | --quiet] fcnsq host --gspn port_id [-q | --quiet] fcnsq host --gsnn wwpn [-q | --quiet] fcnsq ? DESCRIPTION
The fcnsq command performs Fibre Channel Name Server queries for a user-specified FC Host. The supported name server query commands include: Get Port Name (GPN), Get Node Name (GNN), Get Symbolic Node Name (GSNN), and Get Symbolic Port Name (GSPN) as described in FC-GS-3 for the Common Transport (CT) services. fcnsq takes the host bsg name as the input for the target host. Host bsg name must be a valid bsg device, e.g., "host12" as derived from /dev/bsg/fc_host12. For each name server query command, the argument is either a Port ID or a World Wide Port Name. Port IDs and World Wide Names must be specified in hexadecimal. To disable verbose output, use the --quiet option. OPTIONS
host --gpn port_id Get Port Name by Port ID for host. host --gnn port_id Get Node Name by Port ID for host. host --gspn port_id Get Symbolic Port Name by Port ID for host. host --gsnn wwpn Get Symbolic Node Name by World Wide Port Name for host. -q, --quiet Disable verbose output. ? Display a help message with basic usage instructions. EXAMPLES
Query Get Port Name (GPN) from host12 for Port ID 0xbf0027 fcnsq host12 --gpn bf0027 Query Get Node Name (GNN) from host12 for Port ID 0xbf0027 fcnsq host12 --gnn bf0027 Query Get Symbolic Port Name (GSPN) from host12 for Port ID 0xbf0027 fcnsq host12 --gspn bf0027 Query Get Symbolic Node Name (GSNN) from host12 for WWWPN 0x1000001B213C9DDA fcnsq host12 --gsnn 0x1000001B213C9DDA SEE ALSO
fcoeadm(8) SUPPORT
fcnsq is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found at the Open-FCoE website http://open-fcoe.org/. Open-FCoE 06/09/2010 FCNSQ(8)

Check Out this Related Man Page

ARCMSR(4)						   BSD Kernel Interfaces Manual 						 ARCMSR(4)

NAME
arcmsr -- Areca Technology Corporation SATA/SAS RAID controller SYNOPSIS
arcmsr* at pci? dev ? function ? DESCRIPTION
The arcmsr driver provides support for the PCI-X and PCI Express RAID controllers from Areca Technology Corporation: - ARC-1110 PCI-X 4 Port SATA RAID Controller - ARC-1110ML PCI-X 4 Port SATA RAID Controller - ARC-1120 PCI-X 8 Port SATA RAID Controller - ARC-1120ML PCI-X 8 Port SATA RAID Controller - ARC-1130 PCI-X 12 Port SATA RAID Controller - ARC-1130ML PCI-X 12 Port SATA RAID Controller - ARC-1160 PCI-X 16 Port SATA RAID Controller - ARC-1160ML PCI-X 16 Port SATA RAID Controller - ARC-1170 PCI-X 24 Port SATA RAID Controller - ARC-1200 Rev A PCI Express 2 Port SATA RAID Controller - ARC-1202 PCI Express 2 Port SATA RAID Controller - ARC-1210 PCI Express 4 Port SATA RAID Controller - ARC-1220 PCI Express 8 Port SATA RAID Controller - ARC-1230 PCI Express 12 Port SATA RAID Controller - ARC-1230ML PCI Express 12 Port SATA RAID Controller - ARC-1231ML PCI Express 12 Port SATA RAID Controller - ARC-1260 PCI Express 16 Port SATA RAID Controller - ARC-1260ML PCI Express 16 Port SATA RAID Controller - ARC-1261ML PCI Express 16 Port SATA RAID Controller - ARC-1280 PCI Express 24 Port SATA RAID Controller - ARC-1280ML PCI Express 24 Port SATA RAID Controller - ARC-1680 PCI Express 8 Port SAS RAID Controller - ARC-1680LP PCI Express 8 Port SAS RAID Controller - ARC-1680i PCI Express 8 Port SAS RAID Controller - ARC-1680x PCI Express 8 Port SAS RAID Controller - ARC-1681 PCI-X 8 Port SAS RAID Controller These controllers support RAID levels 0, 1, 1E, 3, 5, 6, and JBOD using either SAS or SATA II drives. arcmsr supports management and monitoring of the controller through the bioctl(8) and envstat(8) commands. Please note, however, that to use some features that require special privileges, such as creating/removing hot-spares, pass-through disks or RAID volumes will require to have the password disabled in the firmware; otherwise a Permission denied error will be reported by bioctl(8). When a RAID 1 or 1+0 volume is created, either through the bioctl(8) command or controller's firmware, the volume won't be accessible until the initialization is done. A way to get access to the sd(4) device that corresponds to that volume without rebooting, is to issue the fol- lowing command (once the initialization is finished): $ scsictl scsibus0 scan any any The arcmsr driver will also report to the kernel log buffer any error that might appear when handling firmware commands, such as used by the bioctl(8) command. EVENTS
The arcmsr driver is able to send events to powerd(8) if a volume or any drive connected to the volume is not online. The state-changed event will be sent to the /etc/powerd/scripts/sensor_drive script when such condition happens. SEE ALSO
intro(4), pci(4), scsi(4), sd(4), bioctl(8), envstat(8), powerd(8), scsictl(8) HISTORY
The arcmsr driver first appeared in NetBSD 5.0. AUTHORS
The arcmsr driver was originally written for OpenBSD by David Gwynne. It was ported to NetBSD and extended by Juan Romero Pardines. BSD
March 3, 2008 BSD
Man Page