Network Management

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

Its the same config, and its only the model which is not be recognized. Taking the embedded mib viewer, you can access also the model type. And as the screenshot shows the other information has been captured (like contact, location, interfaces). NetEdit discovering does have worked too.

A guess the system oid is missing in IMC :-(
Or it is the combination of this models OID and VSF Stack...

But these two 6200F "B" Models are the only ones I do have at the moment. So I can't test another switch. And as this VSF has been implemented in production, I can't test it without VSF stacking

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

Its the same config, and its only the model which is not be recognized. Taking the embedded mib viewer, you can access also the model type. And as the screenshot shows the other information has been captured (like contact, location, interfaces). NetEdit discovering does have worked too.

A guess the system oid is missing in IMC :-(
Or it is the combination of this models OID and VSF Stack...

But these two 6200F "B" Models are the only ones I do have at the moment. So I can't test another switch. And as this VSF has been implemented in production, I can't test it without VSF stacking

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

Found a document from 2023, which does not contain the OIDs for the "B" Models...

HPE_iMC_HowTo
only goes to 1.3.6.1.4.1.47196.4.1.1.1.304
but OID of my 6200F "B" (JL728B) is: 1.3.6.1.4.1.47196.4.1.1.1.309

I will try to fix it manually with device definition...

Original Message:
Sent: Nov 26, 2024 11:36 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Original Message:
Sent: 11/26/2024 11:28:00 AM
From: r.grossmann
Subject: RE: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Its the same config, and its only the model which is not be recognized. Taking the embedded mib viewer, you can access also the model type. And as the screenshot shows the other information has been captured (like contact, location, interfaces). NetEdit discovering does have worked too.

A guess the system oid is missing in IMC :-(
Or it is the combination of this models OID and VSF Stack...

But these two 6200F "B" Models are the only ones I do have at the moment. So I can't test another switch. And as this VSF has been implemented in production, I can't test it without VSF stacking

Original Message:
Sent: Nov 26, 2024 10:58 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Original Message:
Sent: Nov 26, 2024 10:40 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

It seems working:


What have I done? Added the OID manually to the Aruba 6200 Switch Series:

But why Aruba didn't add the "new" Aruba CX Models to the most recent version, imho the IMC 7.3 E0710P06 Release is from 6th November 2024. The switches are much older....


Original Message:
Sent: Nov 26, 2024 11:58 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Found a document from 2023, which does not contain the OIDs for the "B" Models...

HPE_iMC_HowTo
only goes to 1.3.6.1.4.1.47196.4.1.1.1.304
but OID of my 6200F "B" (JL728B) is: 1.3.6.1.4.1.47196.4.1.1.1.309

I will try to fix it manually with device definition...

Original Message:
Sent: Nov 26, 2024 11:36 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Original Message:
Sent: 11/26/2024 11:28:00 AM
From: r.grossmann
Subject: RE: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Its the same config, and its only the model which is not be recognized. Taking the embedded mib viewer, you can access also the model type. And as the screenshot shows the other information has been captured (like contact, location, interfaces). NetEdit discovering does have worked too.

A guess the system oid is missing in IMC :-(
Or it is the combination of this models OID and VSF Stack...

But these two 6200F "B" Models are the only ones I do have at the moment. So I can't test another switch. And as this VSF has been implemented in production, I can't test it without VSF stacking

Original Message:
Sent: Nov 26, 2024 10:58 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Original Message:
Sent: Nov 26, 2024 10:40 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

It seems working:


What have I done? Added the OID manually to the Aruba 6200 Switch Series:

But why Aruba didn't add the "new" Aruba CX Models to the most recent version, imho the IMC 7.3 E0710P06 Release is from 6th November 2024. The switches are much older....


Original Message:
Sent: Nov 26, 2024 11:58 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Found a document from 2023, which does not contain the OIDs for the "B" Models...

HPE_iMC_HowTo
only goes to 1.3.6.1.4.1.47196.4.1.1.1.304
but OID of my 6200F "B" (JL728B) is: 1.3.6.1.4.1.47196.4.1.1.1.309

I will try to fix it manually with device definition...

Original Message:
Sent: Nov 26, 2024 11:36 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Original Message:
Sent: 11/26/2024 11:28:00 AM
From: r.grossmann
Subject: RE: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Its the same config, and its only the model which is not be recognized. Taking the embedded mib viewer, you can access also the model type. And as the screenshot shows the other information has been captured (like contact, location, interfaces). NetEdit discovering does have worked too.

A guess the system oid is missing in IMC :-(
Or it is the combination of this models OID and VSF Stack...

But these two 6200F "B" Models are the only ones I do have at the moment. So I can't test another switch. And as this VSF has been implemented in production, I can't test it without VSF stacking

Original Message:
Sent: Nov 26, 2024 10:58 AM
From: parnassus
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello Robert, typically similar issues kick in when SNMP access to switch is not working/configured as expected (Is the SNMP configuration used by the new Aruba CX 6200F JL728B equal to the other working SNMP configurations used by other switches?).

Check this, eventually (valid for the latest HPE IMC 7.9 E0710P06 too).

Original Message:
Sent: Nov 26, 2024 10:40 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hello,

We have a lot of Aruba CX Switches like 8325, 8360, 6200F, 6100
8325 and 8360 as VSX
6200F as VSF or Standalone
6100 as Standalone
HPE IMC has recognized this and I can backup config for example.

But now we got 2 "new" B Model of 6200F
Product Name           : JL728B 6200F 48G CL4 4SFP+740W Swch

It has been configured as a VSF Stack and is working and SNMP.

But problem is with IMC. It does NOT recognize the model and classifies it as "Unknown SNMP Product".
And furthermore or because of it, IMC does not backup config etc.


Anyone an idea?

btw.: IMC does not have a actual service contract and is licensed permantly for 100 devices.
I updated to the newest patch version, but no difference in behaviour.
SNMP, SSH and REST credentials are okay.

Thanks and kind regards

Robert

3rd try to reply

Hi Raphael,

If youre are meaning Software Updates. I dont use IMC, as it doesnt have worked properly in generally in case of CX devices. So I had switched over to Aruba NetEdit. Maybe this could be a solution for you, too.

Or maybe it has been fixed in the latest hotfix E0710H08.
HPE Networking | Enterprise
readme_plat_7.3_E0710H08.pdf
I got it via email subscription in April 2025, but unfortunately HPE / Aruba has published is with a wrong time code / year "Released on Apr 10, 2024", should be 2025 instead of 2024, I guess.

And sorry I cannot test Software Update in IMC, as only 4 of my 97 Aruba CX Switches are "B"-Models and are used as two productional VSF-Stacks in a remote branch with opening from 06:00 to 23:00. So I really cannot test it. Even so I haven't appliued the latest hotfix, as I currently have problems with database backup, so update has to wait.

Kind Regards

Robert

Hi Robert,

Thank you for your return. I am not able to use Netedit in this environnement. I did not see this version because it was earlier than the E7010P06. I will to push the E710H08 even if I do not see anithing about 6200B into the release note.

Raphael,

Original Message:
Sent: May 16, 2025 09:19 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

3rd try to reply

Hi Raphael,

If youre are meaning Software Updates. I dont use IMC, as it doesnt have worked properly in generally in case of CX devices. So I had switched over to Aruba NetEdit. Maybe this could be a solution for you, too.

Or maybe it has been fixed in the latest hotfix E0710H08.
HPE Networking | Enterprise
readme_plat_7.3_E0710H08.pdf
I got it via email subscription in April 2025, but unfortunately HPE / Aruba has published is with a wrong time code / year "Released on Apr 10, 2024", should be 2025 instead of 2024, I guess.

And sorry I cannot test Software Update in IMC, as only 4 of my 97 Aruba CX Switches are "B"-Models and are used as two productional VSF-Stacks in a remote branch with opening from 06:00 to 23:00. So I really cannot test it. Even so I haven't appliued the latest hotfix, as I currently have problems with database backup, so update has to wait.

Kind Regards

Robert

One for hint.

Go to your Software library to teh desired software --> Operation --> Modify --> Appplicable Devices --> Select Models --> Vendor Name: Aruba --> Series: for example 6200 --> Check the desired Series, for example "Aruba 6200 Switch Series" (you can unfold to see the devices, unfortunately with shortened names) --> OK --> OK

In my case I guess the 725B and 728B are missing after software import, but could not really tell, because it's difficult to see which devices are in the "Applicable Devices" list..

Edit: The B-Models are not recognized in my custom 6200 Device Group, but can be chosen by the generally Device View "Switches", so it is suitable for the software image to chose. So I guess it should work...

Regards

Robert

Original Message:
Sent: May 16, 2025 09:44 AM
From: raphael.mazot
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

Hi Robert,

Thank you for your return. I am not able to use Netedit in this environnement. I did not see this version because it was earlier than the E7010P06. I will to push the E710H08 even if I do not see anithing about 6200B into the release note.

Raphael,

Original Message:
Sent: May 16, 2025 09:19 AM
From: r.grossmann
Subject: HPE IMC does not recognize the "new" Aruba CX 6200F B models, in my case JL728B

3rd try to reply

Hi Raphael,

If youre are meaning Software Updates. I dont use IMC, as it doesnt have worked properly in generally in case of CX devices. So I had switched over to Aruba NetEdit. Maybe this could be a solution for you, too.

Or maybe it has been fixed in the latest hotfix E0710H08.
HPE Networking | Enterprise
readme_plat_7.3_E0710H08.pdf
I got it via email subscription in April 2025, but unfortunately HPE / Aruba has published is with a wrong time code / year "Released on Apr 10, 2024", should be 2025 instead of 2024, I guess.

And sorry I cannot test Software Update in IMC, as only 4 of my 97 Aruba CX Switches are "B"-Models and are used as two productional VSF-Stacks in a remote branch with opening from 06:00 to 23:00. So I really cannot test it. Even so I haven't appliued the latest hotfix, as I currently have problems with database backup, so update has to wait.

Kind Regards

Robert