topic You use neither. The control in Network Security

CISCO ASA 5516-X SN different on back of unit and show version

Lovleen Arora — Tue, 12 Mar 2019 06:41:39 GMT

Hi,

The back of the ASA 5516-X unit says a different serial number compared to the show version from the unit. Is that a problem, Which SN to link the license to?

I received a 5516 control license in the box.

Thanks

Lovleen

You use neither. The control

Marvin Rhoads — Mon, 05 Oct 2015 02:23:42 GMT

You use neither. The control license is redeemed using the license key ID from the managing FireSIGHT. Once you've done that, you assign it to the ASA from within the FireSIGHT interface..

On the 5516-X that can be via either FireSIGHT embedded in ASDM or via an external FireSIGHT Management Center. FireSIGHT Management Center license key is derived from the product ID and MAC address of the managed system (ASDM-based) or management center host (external FireSIGHT).

Hi Marvin !i also have the

Guillaume BARBEROT — Thu, 08 Oct 2015 12:24:10 GMT

Hi Marvin !

i also have the same issue, but not for licensing purpose, but mainly for contract management ...

the serial i have been given by Cisco during shipment (order) is starting by "JMX..." (it is the same as the external label on the ASA)

BUT it's not the same as the show version which is starting by "JAD..."

if i look for the JAD serial in the CSCC tool (cisco.com/go/cscc) i cannot find anything as contract for this serial

but if i look for with the JMX serial : i get the correct values from cisco cscc

Moreover, i would like to know how to find the JMX serial via CLI (i have checked it is not in a show tech-support),

it also has to be onboarded in our assets CMDB with the right serial ........

Thanks

Guillaume.

This is a known bug with ASAs

Marvin Rhoads — Thu, 08 Oct 2015 12:31:52 GMT

This is a known bug with ASAs. Reference BugID CSCtz56314.

Asset management usually want to check the physical chassis serial number. So you have to read that from the sticker on the chassis (or get it by reloading and interrupting the boot process to retrieve it from rommon - impractical in most cases).

Its called the parent SN

Lovleen Arora — Thu, 08 Oct 2015 22:28:57 GMT

Its called the parent SN (chassis) and the child (show version).

for your support contract, cisco use the chassis SN.

you may look at it using show inventory command.

Thanks Marvin for pointing

Guillaume BARBEROT — Wed, 14 Oct 2015 08:57:39 GMT

Thanks Marvin for pointing out this bug

I hope it will be solved in a new version, since i am running a 9.4x

as you mentioned, reboot and rommon is not possible for us, unless a maintenance window is scheduled ...

Guillaume

[edit] : "show inventory" as proposed by lovleen worked for me, it is also a good (better) solution than reload, you can see the chassis serial