Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent. I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve. Thanks for your help.
Yours
Elmar
Does this apply to /all/ checkpoint devices?
We can control use of ifName instead of ifDescr (they're not always the same, ifName is often a shortened version of ifDescr, and sometimes it's a customisable name) in the OS definition.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 08:11 To: observium@observium.org Cc: Hofer, Elmar (BITBW) Elmar.Hofer@bitbw.bwl.de Subject: [Observium] Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent.
I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve.
Thanks for your help.
Yours
Elmar
The problem starts with Checkpoint Version R80.40. In earlier Versions the Interface names are displayed correctly. Starting with R80.40 I'm getting network card names such as Intel X710 instead of eth1 for example.
Elmar
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium Gesendet: Montag, 4. Oktober 2021 11:19 An: 'Observium' observium@observium.org Cc: Adam Armstrong adama@observium.org Betreff: Re: [Observium] Problems with Checkpoint Gaia interface naming
Does this apply to /all/ checkpoint devices?
We can control use of ifName instead of ifDescr (they're not always the same, ifName is often a shortened version of ifDescr, and sometimes it's a customisable name) in the OS definition.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 08:11 To: observium@observium.orgmailto:observium@observium.org Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.demailto:Elmar.Hofer@bitbw.bwl.de> Subject: [Observium] Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent. I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve. Thanks for your help.
Yours
Elmar
Oh, they start doing the thing of putting hardware names into ifDescr. You'd think these companies would employ people who actually know what's expected from these fields, rather than blindly following the MIBs no one who matters has bothered following for 10 years :D
ifDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual string containing information about the
interface. This string should include the name of
the manufacturer, the product name and the version
of the hardware interface."
::= { ifEntry 2 }
Has ifName always been populated usefully on this OS?
Changing behaviour is a really bad thing, but if ifName was always useful, it's easy enough to just change the toggle for this in the OS definition.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 10:27 To: Observium observium@observium.org Cc: Hofer, Elmar (BITBW) Elmar.Hofer@bitbw.bwl.de Subject: Re: [Observium] Problems with Checkpoint Gaia interface naming
The problem starts with Checkpoint Version R80.40. In earlier Versions the Interface names are displayed correctly. Starting with R80.40 I'm getting network card names such as Intel X710 instead of eth1 for example.
Elmar
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium Gesendet: Montag, 4. Oktober 2021 11:19 An: 'Observium' <observium@observium.org mailto:observium@observium.org > Cc: Adam Armstrong <adama@observium.org mailto:adama@observium.org > Betreff: Re: [Observium] Problems with Checkpoint Gaia interface naming
Does this apply to /all/ checkpoint devices?
We can control use of ifName instead of ifDescr (they're not always the same, ifName is often a shortened version of ifDescr, and sometimes it's a customisable name) in the OS definition.
Adam.
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 08:11 To: observium@observium.org mailto:observium@observium.org Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.de mailto:Elmar.Hofer@bitbw.bwl.de > Subject: [Observium] Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent.
I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve.
Thanks for your help.
Yours
Elmar
And which OS(es) is this specifically? "checkpoint" seems to cover a dozen platform/os combinations.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Adam Armstrong via observium Sent: 04 October 2021 10:34 To: 'Observium' observium@observium.org Cc: Adam Armstrong adama@observium.org Subject: Re: [Observium] Problems with Checkpoint Gaia interface naming
Oh, they start doing the thing of putting hardware names into ifDescr. You'd think these companies would employ people who actually know what's expected from these fields, rather than blindly following the MIBs no one who matters has bothered following for 10 years :D
ifDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual string containing information about the
interface. This string should include the name of
the manufacturer, the product name and the version
of the hardware interface."
::= { ifEntry 2 }
Has ifName always been populated usefully on this OS?
Changing behaviour is a really bad thing, but if ifName was always useful, it's easy enough to just change the toggle for this in the OS definition.
Adam.
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 10:27 To: Observium <observium@observium.org mailto:observium@observium.org > Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.de mailto:Elmar.Hofer@bitbw.bwl.de > Subject: Re: [Observium] Problems with Checkpoint Gaia interface naming
The problem starts with Checkpoint Version R80.40. In earlier Versions the Interface names are displayed correctly. Starting with R80.40 I'm getting network card names such as Intel X710 instead of eth1 for example.
Elmar
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium Gesendet: Montag, 4. Oktober 2021 11:19 An: 'Observium' <observium@observium.org mailto:observium@observium.org > Cc: Adam Armstrong <adama@observium.org mailto:adama@observium.org > Betreff: Re: [Observium] Problems with Checkpoint Gaia interface naming
Does this apply to /all/ checkpoint devices?
We can control use of ifName instead of ifDescr (they're not always the same, ifName is often a shortened version of ifDescr, and sometimes it's a customisable name) in the OS definition.
Adam.
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 08:11 To: observium@observium.org mailto:observium@observium.org Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.de mailto:Elmar.Hofer@bitbw.bwl.de > Subject: [Observium] Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent.
I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve.
Thanks for your help.
Yours
Elmar
The problem started with Gaia R80.40. This software is used in our company on serveral appliances of different type. Once you add a vlan-tag on the interface then ifDescr and ifName are the same again. Before R80.40 I never had that problem with network card names. I'm using Checkpoint Gaia on their firewall appliances.
Where can I find the OS definitions in the observium installation. On the observium Website I have found a part which covers special rules fort he OS detection but no filename is mentioned where I can adjust the behaviar.
Elmar
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium Gesendet: Montag, 4. Oktober 2021 11:39 An: 'Observium' observium@observium.org Cc: Adam Armstrong adama@observium.org Betreff: Re: [Observium] Problems with Checkpoint Gaia interface naming
And which OS(es) is this specifically? "checkpoint" seems to cover a dozen platform/os combinations.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Adam Armstrong via observium Sent: 04 October 2021 10:34 To: 'Observium' <observium@observium.orgmailto:observium@observium.org> Cc: Adam Armstrong <adama@observium.orgmailto:adama@observium.org> Subject: Re: [Observium] Problems with Checkpoint Gaia interface naming
Oh, they start doing the thing of putting hardware names into ifDescr. You'd think these companies would employ people who actually know what's expected from these fields, rather than blindly following the MIBs no one who matters has bothered following for 10 years :D
ifDescr OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the hardware interface." ::= { ifEntry 2 }
Has ifName always been populated usefully on this OS?
Changing behaviour is a really bad thing, but if ifName was always useful, it's easy enough to just change the toggle for this in the OS definition.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 10:27 To: Observium <observium@observium.orgmailto:observium@observium.org> Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.demailto:Elmar.Hofer@bitbw.bwl.de> Subject: Re: [Observium] Problems with Checkpoint Gaia interface naming
The problem starts with Checkpoint Version R80.40. In earlier Versions the Interface names are displayed correctly. Starting with R80.40 I'm getting network card names such as Intel X710 instead of eth1 for example.
Elmar
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium Gesendet: Montag, 4. Oktober 2021 11:19 An: 'Observium' <observium@observium.orgmailto:observium@observium.org> Cc: Adam Armstrong <adama@observium.orgmailto:adama@observium.org> Betreff: Re: [Observium] Problems with Checkpoint Gaia interface naming
Does this apply to /all/ checkpoint devices?
We can control use of ifName instead of ifDescr (they're not always the same, ifName is often a shortened version of ifDescr, and sometimes it's a customisable name) in the OS definition.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Hofer, Elmar (BITBW) via observium Sent: 04 October 2021 08:11 To: observium@observium.orgmailto:observium@observium.org Cc: Hofer, Elmar (BITBW) <Elmar.Hofer@bitbw.bwl.demailto:Elmar.Hofer@bitbw.bwl.de> Subject: [Observium] Problems with Checkpoint Gaia interface naming
Dear List-Users,
maybe someone can help me with my problem as it seems to happen quite often.
Checkpoint uses different names in the ifDescr and ifNames field. The correct interface names are in the ifNames field.
Now Observium uses the ifDescr field to display the interface names, because normally both fields have the same conntent. I'm lokking for an option to change this behaviar. It would be great to get an hint where to look for this problem to resolve. Thanks for your help.
Yours
Elmar
participants (2)
-
Adam Armstrong -
Hofer, Elmar (BITBW)