VeloCloud VCE OIDs
						
					
					
				
			
		
	
			
	
	
	
	
	
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
06-19-2023 08:32 AM
Hello Community,
I'm looking for knowledge on discovering our VeloCloud VCE router correctly. I have a SNMPv3 creational that validates on the IP when testing. Im running a quick discovery on a single IP at the moment but it returns "Active, couldn't classify, now finished".
Ive added a lot of different OIDs from the payload to try and help with classifying but it still ends the same way. What am I doing wrong?
- Labels:
 - 
						
							
		
			Discovery
 
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
06-20-2023 09:46 AM
Doug,
Thanks for the link. I followed your video on creating/mapping a pattern which seems to work in the Pattern Designer (see below) but during a quick discovery the IP still remains unclassified. Any tips for getting it to pull in?
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
06-20-2023 10:02 AM
Again, because you are trying to use a oid query as a response value in your sysoid...
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
06-20-2023 12:20 PM
I apologize for not comprehending this.
Am I to create a new SNMP Classification were the classification criteria is sysDescr contains VeloCloud and set the trigger probe to my newly created pattern?
Thanks again for being patient with me.
Robert
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
06-20-2023 01:50 PM
Yes, you can try that, it should work.
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
12-06-2024 03:18 AM
Dear @RRolling did you get the discovery working for the Velocloud SDWAN devices ?
How about the serial number , Routing rules , dependencies/relations to other devices/switches ?
like we have for the cisco switches ?
Probably we need to get the information from RestAPI calls to their element manager, that's my idea.
thank you in advance,
Spiros
