Data required for making a certification request in Spectrum

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

How to make a certification request in Spectrum.

Environment

Release : All

Component : SPCCRT - Spectrum Certification

Resolution

To make a certification request in Spectrum, we need the following information.

#######################################################
- Device Name - 

- Vendor -

- SysOID -

- Purpose (category) for the certification request: - Enhanced Device Certification

- MIB walk gathered using sapwalk2 - 

- MIB files - Specific requirements (e.g. Specific tables or views) by default we will presume MIB2 support only

 #######################################################

 

 

Additional Information

To gather a mib walk using the sapwalk2 application:

The sapwalk application is stored on your SpectroSERVER at <SPECROOT>\bin 
It walks the mib via SNMP getNext commands and builds an SNMP simulation of the device based on this.
This is will allow us to simulate the device in-house in an attempt to reproduce the issue.
 
 
To capture a simulation with the  sapwalk application:
 
1 - Browse to  <SPECROOT>\bin  on your SpectropSERVER where the problematic device is modeled.
2 - Run: 
sapwalk2.exe -i <ip address of the modeled device> -v <snmp version> -s 1.3.6.1 -c <community name> -o <ticket_#>.walk 

<ip address> = The IP address of the device at issue 
<snmp version> = The SNMP version the device at issue runs. Valid values are: v1, v2c or v3 
<community name> = The community string for accessing the devices MIB. 
 
In order to see more options, simply execute the command with no options or arguments. 
Any valid community string with Read permissions can be used.  
Once the command has completed, please forward the resulting <ticket_#>.walk file for use in simulating the device. 
 
Optional (depending on technology): 
 
SNMPv3: 
<-u username> <-l seclevel (nAnP/AnP/AP)> [-xt auth type (MD5/SHA)] [-xa auth password] [-xp priv password] 
 
Busy Devices: 
[-t timeout(msec) ] [-r retries ] [-d sleep_bet_req(msec) ] 
 
VLAN: 
With the "-xv vlanstartoid" argument it will use community string indexing (csi) to capture vlan specific objects for all configured vlans on the device, starting from the oid specified with this argument. Here you should specify the dot1dBridge branch: 1.3.6.1.2.1.17 [-xv bridge/vlanstartoid do auto vlan learn]