HP Cisco Nexus 5000 Cisco MDS 9000 Family MIB Quick Reference (OL-18087-01, Fe - Page 40
Cisco-ipsec-signaling-mib, Cisco-ipsec-tc, Cisco-isci-gw-mib
View all HP Cisco Nexus 5000 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 40 highlights
Send documentation comments to [email protected] CISCO-IPSEC-SIGNALING-MIB This MIB provides status, performance, and fault detection for a protocol with the generic characteristics of signaling protocols used with IPsec and FC-SP, such as IKE and KINK. Signaling protocols are also referred to in this document as control protocols because they perform session control. The protocol-specific aspects of a signaling protocol are captured in a protocol-specific MIB such as the CISCO-IKE-FLOW-MIB. This MIB contains major groups of objects that are used to manage the generic aspects of IPsec signaling. These groups include the following information: • Global statistics, tunnel table, and peer association groups-Aid in real-time monitoring of IPsec signaling activity. • History group-Aids applications that do trending analysis. • Failure group-Enables troubleshooting and detection of potential security violations. • Notifications-Modeled as generic IPsec control notifications and are identified by the specific signaling protocol that caused the notification. CISCO-IPSEC-TC This file defines the textual conventions used in the IPsec suite of MIBs, which includes Internet DOI numbers defined in RFC 2407, ISAKMP numbers defined in RFC 2408, and IKE numbers defined in RFC 2409. CISCO-ISCI-GW-MIB This MIB configures and monitors iSCSI (SCSI over TCP) gateway functions. An iSCSI node (target or initiator) is presented to the Fibre Channel network as a virtual Fibre Channel node that can be accessed by the real Fibre Channel nodes on that network. Similarly, a Fibre Channel node is presented to the iSCSI network as a virtual iSCSI node that can be access by the real iSCSI nodes on that network. It is up to the gateway implementation how to represent the nodes in each of these networks. For example, a gateway implementation may choose to represent multiple Fibre Channel targets either as one iSCSI target (many to one mapping) or multiple iSCSI targets (one to one mapping). Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA © Cisco Systems, Inc. All rights reserved.