I found this is the minimum Comware release to use for OAP modules:
display version H3C Comware Platform Software Comware software, Version 5.20, Release 1206, Basic Copyright (c) 2004-2007 Hangzhou H3C Tech. Co., Ltd. All rights reserved. H3C MSR30-20 uptime is 0 week, 0 day, 3 hours, 55 minutes Last reboot 2010/12/01 04:36:57 System returned to ROM By Power-up. CPU type: FREESCALE MPC8349 533MHz 256M bytes DDR SDRAM Memory 4M bytes Flash Memory Pcb Version: 3.0 Logic Version: 2.0 Basic BootROM Version: 2.11 Extend BootROM Version: 2.11 [SLOT 0]CON (Hardware)3.0, (Driver)1.0, (Cpld)2.0 [SLOT 0]AUX (Hardware)3.0, (Driver)1.0, (Cpld)2.0 [SLOT 0]GE0/0 (Hardware)3.0, (Driver)1.0, (Cpld)2.0 [SLOT 0]GE0/1 (Hardware)3.0, (Driver)1.0, (Cpld)2.0 [SLOT 5]MIM-OAP (Hardware)3.0, (Driver)1.0, (Cpld)1.0
This is just 6 release numbers above the one for my MSR30-60 🙂
oap connect slot 5
Connected to OAP!
CentOS release 4.4 (Final)
Kernel 2.6.9-42.0.3.EL on an i686
The root password (“root”) is not contained in any of the H3C / Huawei manuals, luckily 3com rewrote parts of the manual and added that and some more info, i.e. the fact that ctrl-k will disconnect from the serial port session.
It’s creepy that the command for 3Com will be osn connect slot 5, but beyond that there are no differences.
The OAP has two GigE ports, one (eth0) is connected to the backplane, the other one (eth1) is the one on the IO shield.
The default IP for the “internal” port is 184.108.40.206. There will also be a “new” Line interface in the router called GigabitEthernet SlotID/0 i.e. 5/0 in my case.
If you configure an IP on that you’ll be able to ping/ssh via the internal port.
From what I understood there is also some special driver that will handle traffic mirroring to the OAP and other applications like that.
My hardware specs for the OAP are:
A quick 256MB ssd
80GB 5400rpm Seagate momentus (IDE)
1024MB DDR SDRAM
As you might have seen above, the OS delivered on it is a CentOS 4.4 and that’s where the news start to get worse. All the manuals refer to needing board-specific linux kernel patches and also some patching to the e1000 driver is done. The setup still uses LILO.
There’s also a manual section on reinstalling the OAP.
Unfortunately my OAP came without any software and, specifically, kernel patches.
I’ll search for them some time, but I am worried there.
The kernel / standard install they deliver is heavily outdated and unmaintained.
I hope my support issue with the MSR30-60 is soon resolved, then I’ll try to just open a case about that. In the meantime I have backed up using tar and will try to yum upgrade a lil.