HP Cisco Nexus 5000 Cisco MDS 9000 Family MIB Quick Reference (OL-18087-01, Fe - Page 41

Cisco-iscsi-mib, Cisco-isns-client-mib, Cisco-isns-ip-nw-discovery-mib

Get HP Cisco Nexus 5000 - Converged Network Switches PDF manuals and user guides View all HP Cisco Nexus 5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 41 highlights

Send documentation comments to [email protected] CISCO-ISCSI-MIB This MIB manages iSCSI devices and is based on the Internet Draft (draft-ietf-ips-iscsi-mib-05.txt). In terms of object syntax and semantics, the content of this Cisco MIB is the same as the corresponding Internet Draft revision. This Cisco MIB was created because of the "subject to change" nature of Internet Drafts. This Cisco MIB may eventually be replaced by a stable RFC. The CISCO-ISCSI-MIB is layered between the CISCO-SCSI-MIB and the TCP-MIB (RFC 2012). These MIBs are related as follows: • CISCO-SCSI-MIB-Each iscsiNode, whether it is an initiator, target, or both, is related to one SCSI device within the CISCO-SCSI-MIB. The iscsiNodeTransportType attribute points to the SCSI transport object within the CISCO-SCSI-MIB, which in turn contains an attribute that points back to the iscsiNode. In this way, a management station can navigate between the two MIBs. • TCP-MIB-Each iSCSI connection is related to one transport-level connection. The iSCSI connection is related to a TCP connection using its normal (protocol, source address, source port, destination address, and destination port) 5-tuple. CISCO-ISNS-CLIENT-MIB This MIB configures and monitors the iSNS client. The Cisco MDS 9000 Family switches act as iSNS clients. This MIB lists iSNS server profiles known to the iSNS client. CISCO-ISNS-IP-NW-DISCOVERY-MIB This MIB discovers and manages the disjoint IP networks connected to the various Gigabit Ethernet interfaces in the SAN fabric. Disjoint IP networks are separate IP networks that are not reachable to each other using IP. Multiple disjoint IP networks may terminate on a single Fibre Channel switch in a fabric. In such a scenario, the iSNS server must ensure that the targets returned on a query by iSCSI devices are filtered based on access control lists (specified by the user during configuration), and also based on Gigabit Ethernet ports that are reachable by the IP network on which the iSCSI device is present. The iSNS server partitions all known Gigabit Ethernet ports into disjoint sets based on IP reachability by sending discovery packets. Each discovered set is referred to as an IP network. The Gigabit Ethernet ports contained in these IP networks are referred to as IP network members. This MIB provides the ability to initiate, configure, and show discovery results for the IP networks in the SAN fabric. Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA © Cisco Systems, Inc. All rights reserved.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
Send documentation comments to [email protected]
Americas Headquarters:
© <2009> Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706
USA
CISCO-ISCSI-MIB
This MIB manages iSCSI devices and is based on the Internet Draft (draft-ietf-ips-iscsi-mib-05.txt). In
terms of object syntax and semantics, the content of this Cisco MIB is the same as the corresponding
Internet Draft revision. This Cisco MIB was created because of the “subject to change” nature of Internet
Drafts. This Cisco MIB may eventually be replaced by a stable RFC.
The CISCO-ISCSI-MIB is layered between the CISCO-SCSI-MIB and the TCP-MIB (RFC 2012). These
MIBs are related as follows:
•
CISCO-SCSI-MIB—Each iscsiNode, whether it is an initiator, target, or both, is related to one SCSI
device within the CISCO-SCSI-MIB. The iscsiNodeTransportType attribute points to the SCSI
transport object within the CISCO-SCSI-MIB, which in turn contains an attribute that points back
to the iscsiNode. In this way, a management station can navigate between the two MIBs.
•
TCP-MIB—Each iSCSI connection is related to one transport-level connection. The iSCSI
connection is related to a TCP connection using its normal (protocol, source address, source port,
destination address, and destination port) 5-tuple.
CISCO-ISNS-CLIENT-MIB
This MIB configures and monitors the iSNS client. The Cisco MDS 9000 Family switches act as iSNS
clients. This MIB lists iSNS server profiles known to the iSNS client.
CISCO-ISNS-IP-NW-DISCOVERY-MIB
This MIB discovers and manages the
disjoint
IP networks connected to the various Gigabit Ethernet
interfaces in the SAN fabric. Disjoint IP networks are separate IP networks that are not reachable to each
other using IP. Multiple disjoint IP networks may terminate on a single Fibre Channel switch in a fabric.
In such a scenario, the iSNS server must ensure that the targets returned on a query by iSCSI devices are
filtered based on access control lists (specified by the user during configuration), and also based on
Gigabit Ethernet ports that are reachable by the IP network on which the iSCSI device is present.
The iSNS server partitions all known Gigabit Ethernet ports into disjoint sets based on IP reachability
by sending discovery packets. Each discovered set is referred to as an IP network. The Gigabit Ethernet
ports contained in these IP networks are referred to as IP network members.
This MIB provides the ability to initiate, configure, and show discovery results for the IP networks in
the SAN fabric.