Home/Catalog/CISCO-NS-MIB

CISCO-NS-MIB

AI MIB Summary

The CISCO-NS-MIB provides management capabilities for Cisco Fibre Channel Name Servers to monitor FC-GS3 compliant service discovery parameters, including registered domain identifiers, port state transitions, and active fabric service bindings.

The MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS).
Main OID:
ciscoNsMIB.1.3.6.1.4.1.9.9.293
50
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

50 total
Object Name
ciscoNsMIBThe MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS).
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.293
ciscoNameServerMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1
fcNameServerConfiguration
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1.1
fcNameServerProxyPortTableThis table contains a list of proxy ports on all configured VSANs on the local switch. Only one proxy port is allowed on a VSAN.
SEQUENCE OF FcNameServerProxyPortEntry
.1.3.6.1.4.1.9.9.293.1.1.1
fcNameServerProxyPortEntryAn entry (conceptual row) in this table.
FcNameServerProxyPortEntry
.1.3.6.1.4.1.9.9.293.1.1.1.1
fcNameServerProxyPortNameName of the proxy port which can register/deregister for other ports on this VSAN. Users can enable third party registrations by setting this object. In order to disable third party registrations, this object should be set to ''H.rw
FcNameIdOrZero (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.1.1.1
fcNameServerTableLastChangeThe value of sysUpTime at the time of the last update to the fcNameServerTable. This includes creation of an entry, deletion of an entry and modification of an existing entry. If no updates have taken place since the last re-initialization of the local network management subsystem, then this object contains a zero value.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.9.9.293.1.1.2
fcNameServerNumRowsThe number of Nx_Ports currently registered with this device fabric wide.ro
Integer32
.1.3.6.1.4.1.9.9.293.1.1.3
fcNameServerTableThis table contains entries for all Nx_Ports registered with Fx_Ports on all the VSANs configured on the local switch.
SEQUENCE OF FcNameServerEntry
.1.3.6.1.4.1.9.9.293.1.1.4
fcNameServerEntryAn entry (conceptual row) in the fcNameServerTable. This contains information about an Nx_Port represented by fcNameServerPortIdentifier for a particular VSAN identified by vsanIndex.
FcNameServerEntry
.1.3.6.1.4.1.9.9.293.1.1.4.1
fcNameServerPortIdentifierThe Fibre Channel Identifier (FC-ID) of this Nx_Port.
FcAddressId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.1
fcNameServerPortNameThe fibre channel Port_Name (WWN) of this Nx_port. If this object is not set, then it will contain the null value '0000000000000000'h.ro
FcNameId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.2
fcNameServerNodeNameThe fibre channel Node_Name (WWN) of this Nx_port. If this object is not set, then it will contain the null value '0000000000000000'h.ro
FcNameId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.3
fcNameServerClassOfSvcThe class of service indicator. This object is a array of bits that contain a bit map of the classes of service supported by the associated port. If a bit in this object is 1, it indicates that the class of service is supported by the associated port. When a bit is set to 0, it indicates that no class of service is supported by this Nx_port.ro
FcClassOfServices (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.4
fcNameServerNodeIpAddressThe IP address of the node of this Nx_port, as indicated by the Nx_Port in a GS3 message that it transmitted. The GS3 format specifies a 32-bit IPv4 address or a 128-bit IPv6 address. For the former, the leftmost 96 bits (12 bytes) are set to x'00 00 00 00 00 00 00 00 00 00 FF FF' and the rightmost 32 bits are supposed to contain the IPv4 address.rw
OCTET STRING
.1.3.6.1.4.1.9.9.293.1.1.4.1.5
fcNameServerProcAssocThe Fibre Channel initial process associator (IPA).ro
OCTET STRING
.1.3.6.1.4.1.9.9.293.1.1.4.1.6
fcNameServerFC4TypeThe FC-4 protocol types supported by this Nx_port. This is an array of 256-bits. Each bit in the array corresponds to a Type value as defined by the fibre channel standards and contained in the Type field of the frame header.rw
OCTET STRING
.1.3.6.1.4.1.9.9.293.1.1.4.1.7
fcNameServerPortTypeThe port type of this port.ro
Enumeration
.1.3.6.1.4.1.9.9.293.1.1.4.1.8
fcNameServerPortIpAddressThis object contains the IP address of the associated port in either 32-bit IPv4 format or 128-bit IPv6 format. When this object contains a IPv4 address, the leftmost 96 bits (12 bytes) should contain x'00 00 00 00 00 00 00 00 00 00 FF FF'. The IPv4 address should be present in the rightmost 32 bits. Note that the value of this object is the IP address value that is received in the GS3 message Register IP address (Port) RIPP_ID. It is not validated against any IP address format.rw
OCTET STRING
.1.3.6.1.4.1.9.9.293.1.1.4.1.9
fcNameServerFabricPortNameThe Fabric Port Name (WWN) of the Fx_port to which this Nx_port is attached. If this object is not set, then it will contain the null value '0000000000000000'h.ro
FcNameId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.10
fcNameServerHardAddressThe format of this object is identical to the format of Hard Address defined in the Discover Address (ADISC) Extended Link Service (FC-PH-2). Hard Address is the 24-bit NL_Port identifier which consists of - the 8-bit Domain Id in the most significant byte - the 8-bit Area Id in the next most significant byte - the 8-bit AL-PA(Arbitrated Loop Physical Address) which an NL_port attempts acquire during FC-AL initialization in the least significant byte. If the port is not an NL_Port, or if it is an NL_Port but does not have a hard address, then all bits are reported as 0s.ro
FcAddressId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.11
fcNameServerSymbolicPortNameThe user-defined name of this port. If this object has not been set, then the value of this object is the zero length string.rw
SnmpAdminString
.1.3.6.1.4.1.9.9.293.1.1.4.1.12
fcNameServerSymbolicNodeNameThe user-defined name of the node of this port. If this object has not been set, then the value of this object is the zero length string.rw
SnmpAdminString
.1.3.6.1.4.1.9.9.293.1.1.4.1.13
fcNameServerFC4FeaturesThe FC-4 Features associated with this port and the FC-4 Type. Refer to FC-GS3 specification for the format of this object. This object is an array of 4-bit values, one for each TYPE code value. The 5 most significant bits of the TYPE field will be used to identify the word for the FC-4 Features object. - Word 0 contains information related to TYPE code '00' thru' '07'; - Word 1 contains information related to TYPE code '08' thru' 0F'; - and so forth to Word 31 that contains information related to TYPE code 'F8' thru' 'FF'. The 3 least significant bits of the TYPE field will be used to identify the position within the word for the 4-bit FC-4 Features value.rw
OCTET STRING
.1.3.6.1.4.1.9.9.293.1.1.4.1.14
fcNameServerPortFunctionThe function of this port. trapPort(0) indicates that this port is functioning as a Trap Port. vep(1) indicates that this port is functioning as a Virtual Enclosure Port (VEP). volOwner(2) indicates that this port is functioning as a Volume Owner. ipfcPort(3) indicates that this port is functioning as a IP-FC port. intPort(4) indicates that this port is functioning as an internal port.rodeprecated
Bits
.1.3.6.1.4.1.9.9.293.1.1.4.1.15
fcNameServerPermanentPortNameThe Permanent Port Name of this Nx_port. If multiple Port_Name(s) are associated with this Nx_port via FDISC (Discover F_Port Service Parameters), the Permanent Port Name is the original Port_Name associated with this Nx_port at login. If this object is not set, then it will contain the null value '0000000000000000'h.ro
FcNameId (CISCO-ST-TC)
.1.3.6.1.4.1.9.9.293.1.1.4.1.16
fcNameServerRejReqNotifyEnableThis object specifies if the Name Server should generate 'fcNameServerRejectRegNotify' notifications. If value of this object is 'true', then the notification is generated when a request is rejected. If it is 'false', the notification is not generated.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.293.1.1.5
fcNameServerStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1.2
fcNameServerTotalRejectsThe total number of requests rejected by the local switch across all VSANs.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.1
fcNameServerStatsTableThis table contains statistic counters which are maintained by the Name Server. These counters are maintained per VSAN.
SEQUENCE OF FcNameServerStatsEntry
.1.3.6.1.4.1.9.9.293.1.2.2
fcNameServerStatsEntryAn entry (conceptual row) in this table.
FcNameServerStatsEntry
.1.3.6.1.4.1.9.9.293.1.2.2.1
fcNameServerInGetReqsThe total number of Get Requests received by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.1
fcNameServerOutGetReqsThe total number of Get Requests sent by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.2
fcNameServerInRegReqsThe total number of Registration Requests received by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.3
fcNameServerInDeRegReqsThe total number of De-registration Requests received by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.4
fcNameServerInRscnsThe total number of RSCN commands received by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.5
fcNameServerOutRscnsThe total number of RSCN commands sent by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.6
fcNameServerRejectsThe total number of requests rejected by the local switch on this VSAN.ro
Counter32
.1.3.6.1.4.1.9.9.293.1.2.2.1.7
fcNameServerInformation
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1.3
fcNameServerRejectReasonCodeThe registration reject reason code. This object contains the reason code corresponding to the most recent Name Server Registration request failure.ro
FcGs3RejectReasonCode
.1.3.6.1.4.1.9.9.293.1.3.1
fcNameServerRejReasonCodeExpThe registration reject reason code explanation. This object contains the reason code explanation if the above object has a reason code corresponding to 'Unable to perform command request'. This object like the one above, corresponds to the most recent Name Server Registration request rejection.ro
FcNameServerRejReasonExpl
.1.3.6.1.4.1.9.9.293.1.3.2
fcNameServerNotification
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1.4
fcNameServerNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.1.4.0
fcNameServerRejectRegNotifyThis notification is generated by the Name Server whenever it rejects a registration request. The Name Server should update the 'fcNameServerRejectReasonCode' and 'fcNameServerRejReasonCodeExp' objects with the corresponding reason code and reason code explanation before sending the notification. These two objects are also included along with the notification to provide the reason for the reject.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.293.1.4.0.1
fcNameServerDatabaseFullThis notification is generated by the Name Server when the Name Server cannot allocate space for a new entry.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.293.1.4.0.2
fcNameServerEntryAddThis notification is generated by the Name Server when a new entry gets added to the Name Server database.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.293.1.4.0.3
fcNameServerEntryDeleteThis notification is generated by the Name Server when an existing entry is deleted from the Name Server database.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.293.1.4.0.4
fcNameServerMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.2
fcNameServerMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.2.1
fcNameServerMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.293.2.2