📄 notes.txt
字号:
> SYNTAX PhivCounter ( 0..65535 ) 2155c2157 < SYNTAX INTEGER ( 0..65535 ) --- > SYNTAX PhivCounter ( 0..65535 ) 2163c2165 < SYNTAX INTEGER ( 0..65535 ) --- > SYNTAX PhivCounter ( 0..65535 )rfc1353 A number of changes needed to be made to the IMPORT section: 4,5c4,6 < system, mib, private, internet FROM RFC1155-SMI < OBJECT-TYPE FROM RFC-1212; --- > private, internet FROM RFC1155-SMI > OBJECT-TYPE FROM RFC-1212 > mib-2 FROM SNMPv2-SMI;rfc1414 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 7c7,8 < tcpConnRemAddress, tcpConnRemPort --- > tcpConnRemAddress, tcpConnRemPort, > mib-2rfc1447 Got the following error when trying to compile: "rfc1447.mib:7: SNMPv2-SMI doesn't define UInteger32". Changed lines 7 and 78 to use Integer32 for now so that the file would compile.rfc1471 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 194c194 < SYNTAX INTEGER(1..2147483648) --- > SYNTAX INTEGER(1..2147483647) 208c208 < SYNTAX INTEGER(1..2147483648) --- > SYNTAX INTEGER(1..2147483647) 564c564 < SYNTAX INTEGER(1..2147483648) --- > SYNTAX INTEGER(1..2147483647) 578c578 < SYNTAX INTEGER(1..2147483648) --- > SYNTAX INTEGER(1..2147483647)rfc1472 Below is the only difference between the MIB in the RFC and the installed MIB. The MIB in the RFC _does_ compile, but with a warning. Because the additional IMPORT is not used, the installed MIB has not been updated to match the code from the RFC. 4,5d3 < Counter < FROM RFC1155-SMIrfc1473 Below is the only difference between the MIB in the RFC and the installed MIB. The MIB in the RFC _does_ compile, but with a warning. Because the additional IMPORT is not used, the installed MIB has not been updated to match the code from the RFC. 4,5d3 < Counter < FROM RFC1155-SMIrfc1474 Below is the only difference between the MIB in the RFC and the installed MIB. The MIB in the RFC _does_ compile, but with a warning. Because the additional IMPORT is not used, the installed MIB has not been updated to match the code from the RFC. 4,5d3 < Counter < FROM RFC1155-SMIrfc1512 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 7c7,9 < FROM RFC-1212; --- > FROM RFC-1212 > transmission > FROM RFC1213-MIB;rfc1514 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 4a5 > mib-2,rfc1515 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 6a7 > mib-2 FROM RFC1213-MIBrfc1559 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 1005c1005 < INTEGER, --- > InterfaceIndex, 1432c1432 < INTEGER, --- > PhivAddr, 1500c1500 < PhivCounter --- > INTEGER (0..255) 2165c2165 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2173c2173 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2182c2182 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2190c2190 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2199c2199 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2207c2207 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535) 2215c2215 < SYNTAX INTEGER (0..65535) --- > SYNTAX PhivCounter (0..65535)rfc1592 Got error 'rfc1592.mib:9: expected comma or FROM, got OBJECT'. Replaced missing semicolon at end of IMPORTS. Got errors 'rfc1592.mib:31: The SNMPv2 OBJECT-TYPE macro requires a MAX-ACCESS clause, not an ACCESS clause.' and 'rfc1592.mib:40: The SNMPv2 OBJECT-TYPE macro requires a MAX-ACCESS clause, not an ACCESS clause.'. Changed clauses to MAX-ACCESS. Got errors 'rfc1592.mib:32: SNMPv2 objects may not have STATUS mandatory or optional.' and 'rfc1592.mib:41: SNMPv2 objects may not have STATUS mandatory or optional.'. Changed STATUSes to "current".rfc1604 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. This list does not include the changes to the MAX-ACCESS, listed at the bottom of this file, which were required to get the file to compile. 5,8c5,7 < Counter32, Integer32, < TimeTicks FROM SNMPv2-SMI < DisplayString, PhysAddress, < TimeStamp, RowStatus FROM SNMPv2-TC --- > Counter32, Integer32 FROM SNMPv2-SMI > DisplayString, TimeStamp, > RowStatus, TEXTUAL-CONVENTION FROM SNMPv2-TCrfc1611 For some reason the following line was not included in the installed version of the MIB. It does not generate any compile errors. 157d156 < DISPLAY-HINT "4d"rfc1612 The MIB below had a number of changes due to problems with MAX-ACCESS. These are listed at the bottom of this file. In addition to that, there was also the difference shown below. Because the additional IMPORT is not used, the installed MIB has not been updated to match the code from the RFC. 6c6 < TEXTUAL-CONVENTION, RowStatus, DisplayString --- > RowStatus, DisplayStringrfc1623 Got 'rfc1623.mib:35: The columnar object "dot3StatsEtherChipSet" is not an element of the row sequence type "Dot3StatsEntry".' This appears to have been caused by the dot3StatsEtherChipSet OBJECT not being included at the end of the Dot3StatsEntry SEQUENCE. It has been added. Got 'rfc1623.mib:362: INDEX clause for "dot3CollEntry" references undefined object "ifIndex".' Later there is a comment saying '-- { dot3CollEntry 1 } is no longer in use'. I believe that this might have been the original entry for the ifIndex OBJECT. Since it does not exist in the MIB and appears to have been removed, the entry will be removed from the INDEX clause.rfc1658 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 4c4 < MODULE-IDENTITY, OBJECT-TYPE, --- > MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 7c7 < AutonomousType, InstancePointer, TEXTUAL-CONVENTION --- > AutonomousType, InstancePointer 11c11 < mib-2, DisplayString --- > transmission, mib-2rfc1659 The MIB in the RFC compiles, but with an additional warning that the object is imported but never used. This MIB has been updated to match the contents of the RFC. 4c4 < MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, --- > MODULE-IDENTITY, OBJECT-TYPE,rfc1660 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC compiles, but with an additional warning that the object is imported but never used. This MIB has been updated to match the contents of the RFC. 4c4 < MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, --- > MODULE-IDENTITY, OBJECT-TYPE,rfc1696 Compile failed with 'rfc1696.mib:26: Circular definition for "mdmMIB".' Within the MIB is the following code: mdmMIB MODULE-IDENTITY [...] ::= { mdmMIB 1 } mdmMib OBJECT IDENTIFIER ::= { mib-2 38 } To get the code to compile this was changed to: mdmMIB MODULE-IDENTITY [...] ::= { mib-2 38 }rfc1697 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 4,5c4,5 < MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, < Counter32, Gauge32, Integer32 --- > MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, OBJECT-IDENTITY, > Counter32, Gauge32 8a9,10 > MODULE-COMPLIANCE, OBJECT-GROUP > FROM SNMPv2-CONF 12c14,16 < FROM RFC1213-MIB; --- > FROM RFC1213-MIB > hrSystem > FROM HOST-RESOURCES-MIB; 1276c1280 < MODULE RDBMS-MIB --- > MODULE -- RDBMS-MIBrfc1743 Got 'rfc1743.mib:822: Conflicting registrations "dot5TimerIfIndex" and "dot5StateGroup".' It turns out that, slightly higher up the tree, '{ dot5 5 }' was used twice. Assuming the second use is the wrong one and changing it to '{ dot5 6 }'. It is unknown if this is correct, but it does get the file to compile.rfc1757 Below is a list of the differences between the MIB in the RFC and the installed MIB. The MIB in the RFC does not compile. The installed MIB has not been updated to match the code from the RFC. 4,6c4,5 < Counter FROM RFC1155-SMI < DisplayString FROM RFC1158-MIB
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -