MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 10 (transmission). 230 (ifcpMgmtMIB). 1 (ifcpGatewayObjects). 2 (ifcpNportSessionInfo). 1 (ifcpSessionAttributesTable). 1 (ifcpSessionAttributesEntry)
OID : 1.3.6.1.2.1.10.230.1.2.1.1
TXT : iso. org. dod. internet. mgmt. mib-2. transmission. ifcpMgmtMIB. ifcpGatewayObjects. ifcpNportSessionInfo. ifcpSessionAttributesTable. ifcpSessionAttributesEntry
Enfants
D├ętails
OID1.3.6.1.2.1.10.230.1.2.1.1
Module IFCP-MGMT-MIB (ietf)
NomifcpSessionAttributesEntry
Statuscurrent
DescriptionEach entry contains information about one iFCP session consisting of a pair of N_PORTs joined by a single TCP/IP connection. This table's INDEX includes ifcpLclGtwyInstIndex, which identifies the local iFCP Gateway instance that created the session for the entry. Soon after an entry is created in this table for an iFCP session, it will correspond to an entry in the tcpConnectionTable of the TCP-MIB (RFC 4022). The corresponding entry might represent a preexisting TCP connection, or it might be a newly-created entry. (Note that if IPv4 is being used, an entry in RFC 2012's tcpConnTable may also correspond.) The values of ifcpSessionLclPrtlAddrType and ifcpSessionRmtPrtlIfAddrType in this table and the values of tcpConnectionLocalAddressType and tcpConnectionRemAddressType used as INDEX values for the corresponding entry in the tcpConnectionTable should be the same; this makes it simpler to locate a session's TCP connection in the TCP-MIB. (Of course, all four values need to be 'ipv4' if there's a corresponding entry in the tcpConnTable.) If an entry is created in this table for a session, prior to knowing which local and/or remote port numbers will be used for the TCP connection, then ifcpSessionLclPrtlTcpPort and/or ifcpSessionRmtPrtlTcpPort have the value zero until such time as they can be updated to the port numbers (to be) used for the connection. (Thus, a port value of zero should not be used to locate a session's TCP connection in the TCP-MIB.) When the TCP connection terminates, the entry in the tcpConnectionTable and the entry in this table both get deleted (and, if applicable, so does the entry in the tcpConnTable).