UnknownASN models being discovered and modeled in Spectrum

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

We are seeing hundreds of UnknownASN Provider_Cloud models being discovered:

 

How are these being discovered? 

Environment

Release : Any
Component : Enterprise VPN Manager

Cause

These are created from the Enterprise VPN Manager. The Enterprise VPN Manager tries to match a discovered a known Autonomous System Number (ASN) to the ASN provider name. If it can, it will create the Provider_Cloud model with the provider name. If it cannot, it will create the Provider_Cloud model as an UnknownASN_<ASN> where <ASN> is the Autonomous System Number.

Resolution

You can manually map the UnknownASN to an ASN name by doing the following:

- Run a search for the ASN (I ran a Google search for "autonomous system numbers lookup" and found several. One in particular is https://hackertarget.com/as-ip-lookup/)

- Log into OneClick as an ADMIN user

- Find and select the "Enterprise VPN Manager" folder in the Explorer tab of the Navigation panel

- Right mouse click on the "Enterprise VPN Manager" folder and select "Component Detail" from the menu

- Expand the Configuration subview in the Information tab

- In the ASN Mapping field, click on the Add link

- In the Add window, enter the mapping then click the OK button

For example, if you have "UnknownASN_700" and need to map it to "JoeASN_700", enter the following in the Add window:

JoeASN_700,UnknownASN_700

This will map "UnknownASN_700" to "JoeASN_700"