What would be the impact of the blocking the OIDs over Networking tool from doing its job of monitoring and correlation as in the following:
snmp-server view CPU iso included
snmp-server view CPU internet included
snmp-server view CPU at excluded 1.3.6.1.2.1.3 (Address translation)
snmp-server view CPU snmpUsmMIB excluded 1.3.6.1.6.3.15 (User-based Security Model?)
snmp-server view CPU snmpVacmMIB excluded 1.3.6.1.6.3.16 (View-based Access Control Model for SNMP)
snmp-server view CPU snmpCommunityMIB excluded 1.3.6.1.6.3.18
snmp-server view CPU ip.21 excluded 1.3.6.1.2.1.4.21 (IP Routing table)
snmp-server view CPU ip.21 excluded 1.3.6.1.2.1.4.22 (IP Address Translation table - for mapping from IP to physical addresses)
snmp-server view CPU ip.35 excluded 1.3.6.1.2.1.4.35 (looks similar to .22)
In addition, in Smarts IP 8.1 SP1 and later, there is a feature that allows the user to check if the device continues to possess a default route. When this feature is enabled, the Smarts IP domain manager looks for a specific index in the table (0.0.0.0), but will not walk the entries. Other than the exception listed above, there is no data collection against the ipRouteTable MIB tree that takes place in Smarts IP. All the necessary auto-discovery information such as the IP Networks configured on router interfaces comes from the ipAddrTable, ARP tables and Topology MIBs (if checked). Finally, OID 1.3.6.1.2.1.4.22 (the IP Address Translation table used for mapping) is polled in auto-discovery for discovering neighboring devices.