- Community Home
- >
- Networking
- >
- IMC
- >
- IMC Deploy Device Software via OOBM
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2017 05:10 AM
01-12-2017 05:10 AM
IMC Deploy Device Software via OOBM
Trying to deploy new software to HPE 6600ml-48G-4XG Switch via the OOBM interface.
Result shows "Script exist error".
Details show......
G25HP6600a# copy tftp flash 10.50.15.155 10.3.79.250_K_15_18_0014.swi primary allow-no-signature
The primary image will be deleted.
Continue (y/n)? y
000M Peer unreachable.
I think the problem is that the "script" is trying to access the switch by not using the OOBM interface, which is the only IP interface on the switch. The command must have OOBM appended to the end of the string in order to be successful.
Is there some means within IMC to tell it to access these OOBM type switches via this interface when gaining access?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 12:48 PM
10-01-2019 12:48 PM
Re: IMC Deploy Device Software via OOBM
I'm seeing the same behaviour on IMC 7.3 with a 5406R switch, OOBM interface is the only accessible interface to IMC. Anyone have a suggestion?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2019 02:36 AM
10-02-2019 02:36 AM
Re: IMC Deploy Device Software via OOBM
@TomWn wrote: ...OOBM interface is the only accessible interface to IMC...
Is the OoBM IP address reacheable by IMC and vice versa? are IMC and the OoBM on the same subnet?
I'm not an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 10:45 AM - edited 10-08-2019 10:46 AM
10-08-2019 10:45 AM - edited 10-08-2019 10:46 AM
Re: IMC Deploy Device Software via OOBM
Yes, the IMC system is reachable ONLY via the OOBM interface. Ping works when specifying the OOBM interface as the source. Additionally, when manually running the "copy ..." command with an appended OOBM at the end, it can reach the IMC system as expected.
*edit* forgot to mention, they are on the same /16 subnet, no routing involved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 05:58 AM
05-12-2021 05:58 AM
Re: IMC Deploy Device Software via OOBM
Hi,
I am trying to deploy 3810M firmware via oobm with E0705P10.
The problem is the same.
There is no adapter for 3810M sysoid : 1.3.6.1.4.1.11.2.3.7.11.174.1
IMC uses the files in the directory : /opt/iMC/server/conf/adapters/ICC/Hewlett Packard/HPProcurve2500
I tried grep oobm in /opt/iMC/server/conf/adapters/ICC/Hewlett Packard/
oobm is not implemented
copy tftp flash XXXXXXXXXX_KB_16_10_0013.swi primary
The primary image will be deleted.
Continue (y/n)? y
000M Peer unreachable.
IMC and Switchs are in the same VLAN.
Is there anything new about this issue?
Thank you.