The problem device is not configured completely for BGP on the Cisco IOS side. Before Smarts NPM conducts a deep BGP discovery on Smarts NPM BGP, the Smarts IP-AM does a "lite" discovery to create topology components for Smarts NPM BGP. The Smarts IP-AM lite discovery uses the OID bgpPeerLocalAddrOID {".1.3.6.1.2.1.15.3.1.5"} to determine and mark the device as part of the BGP network, and puts the device under BGP TopologyCollection. If the router device has a very limited BGP configuration on it, it may not be marked as BGP on the Smarts IP-AM side, and so will not be recognized by Smarts NPM.
The SNMP walk for such a device could look like the following:
sm_snmp -d rou33900ca -p 30080 -c public walk .1.3.6.1.2.1.15
SNMP Walk MIB starting at .1.3.6.1.2.1.15
.1.3.6.1.2.1.15.1.0 = 10
.1.3.6.1.2.1.15.2.0 = 65333
.1.3.6.1.2.1.15.4.0 = 10.x.x.x