HPE 12500-CMW710-R7377P01 Release
Notes
Software version: 12500-CMW710-R7377P01
Document version: 6W100-20160616
The information in this document is subject to change without notice.
© Copyright 2016 Hewlett Packard Enterprise Development LP
Contents
Version information ···········································································1
Version number ··························································································································· 1
Version history ···························································································································· 1
Hardware and software compatibility matrix ······················································································ 2
Upgrading restrictions and guidelines······························································································· 7
Hardware feature updates ··································································7
12500-CMW710-R7377P01 ··········································································································· 7
12500-CMW710-R7377 ················································································································ 7
12500-CMW710-R7376 ················································································································ 8
12500-CMW710-R7375 ················································································································ 8
12500-CMW710-R7374 ················································································································ 8
12500-CMW710-F7373 ················································································································· 8
12500-CMW710-F7372 ················································································································· 8
12500-CMW710-F7371 ················································································································· 8
12500-CMW710-R7328P01 ··········································································································· 8
12500-CMW710-R7328 ················································································································ 8
12500-CMW710-R7326 ················································································································ 9
Software feature and command updates ···············································9
12500-CMW710-R7377P01 ··········································································································· 9
12500-CMW710-R7377 ················································································································ 9
12500-CMW710-R7376 ················································································································ 9
12500-CMW710-R7375 ················································································································ 9
12500-CMW710-R7374 ················································································································ 9
12500-CMW710-F7373 ··············································································································· 10
12500-CMW710-F7372 ··············································································································· 10
12500-CMW710-F7371 ··············································································································· 10
12500-CMW710-R7328P01 ········································································································· 10
12500-CMW710-R7328 ·············································································································· 10
12500-CMW710-R7326 ·············································································································· 10
MIB updates·················································································· 10
Operation changes ········································································· 11
Operation changes in 12500-CMW710-R7377P01 ··········································································· 11
Operation changes in 12500-CMW710-R7377 ················································································· 11
Operation changes in 12500-CMW710-R7376 ················································································· 12
Operation changes in 12500-CMW710-R7375 ················································································· 12
Operation changes in 12500-CMW710-R7374 ················································································· 12
Operation changes in 12500-CMW710-F7373 ················································································· 12
Operation changes in 12500-CMW710-F7372 ················································································· 12
Operation changes in 12500-CMW710-F7371 ················································································· 12
Operation changes in 12500-CMW710-R7328P01 ··········································································· 12
Operation changes in 12500-CMW710-R7328 ················································································· 12
Operation changes in 12500-CMW710-R7326 ················································································· 12
Restrictions and cautions ································································· 13
Open problems and workarounds ······················································ 15
List of resolved problems ································································· 15
Resolved problems in 12500-CMW710-R7377P01 ··········································································· 15
Resolved problems in 12500-CMW710-R7377 ················································································ 16
Resolved problems in 12500-CMW710-R7376 ················································································ 18
Resolved problems in 12500-CMW710-R7375 ················································································ 20
Resolved problems in 12500-CMW710-R7374 ················································································ 23
i
Resolved problems in 12500-CMW710-F7373 ················································································· 25
Resolved problems in 12500-CMW710-F7372 ················································································· 26
Resolved problems in 12500-CMW710-F7371 ················································································· 29
Resolved problems in 12500-CMW710-R7328P01 ··········································································· 29
Resolved problems in 12500-CMW710-R7328 ················································································ 29
Resolved problems in 12500-CMW710-R7326 ················································································ 30
Support and other resources····························································· 33
Accessing Hewlett Packard Enterprise Support················································································ 33
Documents ······························································································································· 33
Related documents ·············································································································· 33
Documentation feedback ······································································································ 33
Appendix A Feature list ··································································· 34
Hardware features ······················································································································ 34
Card specifications in different working modes················································································· 39
Memory requirements of MPUs and interface cards ·········································································· 40
Software features ······················································································································· 42
Appendix B Upgrading software ························································ 46
Comware software file types ········································································································ 46
Upgrade methods ······················································································································ 47
Preparing for the upgrade ············································································································ 47
Upgrading from the CLI without using ISSU ···················································································· 48
Using TFTP to upgrade software ···························································································· 48
Using FTP to upgrade software ······························································································ 50
Upgrading from the BootWare menu ······························································································ 53
Accessing the BootWare menu ······························································································ 53
Using TFTP/FTP to upgrade software through an Ethernet port ··················································· 55
Using XMODEM to upgrade software through the console port ···················································· 57
Handling software upgrade failures································································································ 61
ii
List of Tables
Table 1 Version history .................................................................................................................................................................... 1
Table 2 HPE 12500 and 12500E product family matrix ...................................................................................................... 2
Table 3 Hardware and software compatibility matrix ......................................................................................................... 2
Table 4 ISSU Version Compatibility Matrix .............................................................................................................................. 7
Table 5 MIB updates ......................................................................................................................................................................10
Table 6 12500 series Chassis hardware features .................................................................................................................34
Table 7 12500E series Chassis hardware features ..............................................................................................................34
Table 8 12500 series unit/module hardware features ......................................................................................................35
Table 9 MPU features ....................................................................................................................................................................35
Table 10 12500 hardware modules with minimum software release .........................................................................36
Table 11 EB/EC/EF card specifications in different working modes ............................................................................39
Table 12 FD card specifications in different working modes .........................................................................................40
Table 13 FG card specifications in different working modes .........................................................................................40
Table 14 Support of Ethernet interface cards for ISSU and MDC ................................................................................41
Table 15 12500 software features .............................................................................................................................................42
Table 16 File control submenu options ..................................................................................................................................55
Table 17 Parameter description .................................................................................................................................................56
iii
This document describes features, restrictions and guidelines, open problems, and workarounds for
version 12500-CMW710-R7377P01. Before you use this version in a live network, back up the
configuration and test this version in a non-production environment to avoid the software upgrade
from affecting your live network.
Use this document in conjunction with the documents listed in "Support and other resources".
Version information
Version number
HPE Comware Software, Version 7.1.045, Release 7377P01
You can see the version number by using the command display version in any view. Please see
Note①.
Version history
Table 1 Version history
Version
number
Last version
Release
date
Release
type
Remarks
12500-CMW710R7377P01
12500-CMW710R7377
Jun 14, 2016
Release
version
•
•
HPE rebranding
Fixes bugs
•
New feature: Configuring the
RIB to flush route attribute
information to the FIB, Logging
for BGP route flapping,
Configuring a subordinate
VRRP group to follow a master
VRRP group
Fixes bugs
12500-CMW710R7377
12500-CMW710R7376
Mar 24, 2016
Release
version
•
•
12500-CMW710R7376
12500-CMW710R7375
12500-CMW710R7374
12500-CMW710R7375
12500-CMW710R7374
12500-CMW710F7373
Nov 10, 2015
Jul 10, 2015
Mar 20, 2015
•
New feature: Keychain
authentication for OSPFv3;
Suite B cryptography
Fixes bugs
•
•
New feature: BGP NSR
Fixes bugs
•
New feature: Automatic
configuration; Auto-RP
listening; MPLS TE; VPLS;
Object group
Fixes bugs
Release
version
Release
version
Release
version
•
•
12500-CMW710F7373
12500-CMW710F7372
12500-CMW710F7372
12500-CMW710F7371
Jan 23, 2015
Dec 3, 2014
1
•
New feature: Multiport ARP
entries for interaction with
Microsoft NLB in IGMP
multicast mode
Fixes bugs
•
•
New feature: Packet capture
Fixes bugs
Feature
version
Feature
version
Version
number
Last version
Release
date
Release
type
Remarks
•
12500-CMW710F7371
12500-CMW710R7328P01
Jun 25, 2014
•
New feature: IGMP/MLD SSM
Mapping; IGMP/MLD
Snooping; NETCONF over
SSH; MACsec; Python
Fixes bugs
Modified feature: IPv6
Fixes bugs
Feature
version
12500-CMW710R7328P01
12500-CMW710R7328
Mar 7, 2014
Release
version
•
•
12500-CMW710R7328
12500-CMW710R7326
Jan 22, 2014
Release
version
Fixes bugs
12500-CMW710R7326
First release
Dec 25, 2013
Release
version
First release
Hardware and software compatibility matrix
Table 2 shows the comparable H3C products which are identical in every way except branding. This
Release Note only refers to the HPE branded products, but it applies equally to the H3C branded
products.
Table 2 HPE 12500 and 12500E product family matrix
HPE 12500 and 12500E
H3C S12500
HPE 12504
None
HPE 12508
H3C S12508 G2
HPE 12518
H3C S12518 G2
HPE FlexFabric 12508E
H3C S12508 G3
HPE FlexFabric 12518E
H3C S12518 G3
CAUTION:
To perform an upgrade, use Table 3 to verify hardware and software compatibility before
performing an upgrade.
Table 3 Hardware and software compatibility matrix
Item
Specifications
Product family
HPE 12500 Switch Series
Hardware platform
12504/12508/12518/12508E/12518E
8 G for MPUs prefixed with LST1MRPNE (JG802A)
Memory
4 G for MPUs prefixed with LST2MRPNC (JC072A, JC808A, JC072B or
JG497A)
4 G for interface cards prefixed with LST1XLP16, LST1XP48, LST1XP40,
or LST1CP4 (JG796A, JG790A, JG794A, JG792A, JG788A or JG786A)
1 G for other interface cards
2
Item
Specifications
512 M flash and 4 G CF card for MPUs prefixed with LST1MRPNE
(JG802A)
Flash
At least 1 G CF card for MPUs prefixed with LST2MRPNC (JC072A,
JC808A, JC072B, or JG497A)
Note: CF cards must be HPE certified.
BootWare 1.08 or later for MPUs prefixed with LST1MRPNE (JG802A)
(See Note⑧)
BootWare 2.24 or later for MPUs prefixed with LST2MRPNC (JC072A,
JC808A, JC072B or JG497A) (See Note②)
BootWare 1.06 or later for the LST1ECP CPU daughter card (See Note
⑨)
Boot ROM version
BootWare 1.07 or later for interface cards prefixed with LST1XLP16,
LST1XP48, LST1XP40 or LST1CP4 (JG796A, JG790A, JG794A,
JG792A, JG788A or JG786A) (See Note⑦)
BootWare 2.14 or later for other interface cards and CPU daughter cards
(See Note③)
BootWare 1.08 or later for switching fabric modules prefixed with
LST1SF18E or LST1SF08E (JG798A, JG800A) (See Note⑥)
BootWare 2.13 or later for other switching fabric modules (See Note④)
MBUS version
115 or above. See Note⑤.
Fan version
No special requirements.
12500-CMW710-R7377P01.ipe (271,682,560 bytes)
Host software
12500-CMW710-BOOT-R7377P01.bin (40,414,208 bytes)
12500-CMW710-SYSTEM-R7377P01.bin (231,261,184 bytes)
12500-CMW710-PACKET-CAPTURE-R7377P01.bin (36,052,992 bytes)
iMC EAD 7.2 (E0402)
iMC TAM 7.2 (E0402)
iMC UAM 7.2 (E0402)
iMC NTA 7.2 (E0401)
iMC PLAT 7.2 (E0403P04)
iMC version
iMC QoSM 7.2 (E0403)
iMC RAM 7.2 (E0402)
iMC SDNM 7.2 (E0402)
iMC SHM 7.2 (E0402)
iMC UBA 7.2 (E0401)
iMC VFM 7.2 (E0403)
iNode version
iNode (PC) 7.2 (E0401)
Web version
Not support
OAA version
LST1FW2A1 (JC635A): SECBLADEII-CMW520-R3178P02
LST1FW3A1 (JG371A): SECBLADEIII-CMW520-R3819
To display version information:
<HPE>display version
HPE Comware Software, Version 7.1.045, Release 7377P01--------Note①
Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP
HPE 12504 uptime is 0 weeks, 0 days, 2 hours, 27 minutes
3
Last reboot reason : User reboot
Boot image: cfa0:/12500-CMW710-BOOT-R7377P01.bin
Boot image version: 7.1.045, Release 7377P01
Compiled Jun 13 2016 16:00:00
System image: cfa0:/12500-CMW710-SYSTEM-R7377P01.bin
System image version: 7.1.045, Release 7377P01
Compiled Jun 13 2016 16:00:00
LST2MRPNC1 1:
uptime is 0 weeks, 0 days, 2 hours, 27 minutes
Last reboot reason : User reboot
3456
Mbytes SDRAM
1024
Kbytes NVRAM Memory
Type
: LST2MRPNC1
BootRom
: 2.24
-------- Note②
Software : 12500-CMW710-R7377P01
PCB
: Ver.B
Board Cpu:
Number of Cpld: 2
Cpld 0:
SoftWare
: 005
Cpld 1:
SoftWare
PowChipA
: 005
: 005
CpuCard
Type
: LSR1CPA
PCB
: Ver.C
Number of Cpld: 1
Cpld 0:
SoftWare
BootRom
: 001
: 2.14
-------- Note③
Mbus card
Type
: LSR1MBCB
Software
: 115
PCB
: Ver.B
LST1GT48LEC1 4:
--------Note⑤
uptime is 0 weeks, 0 days, 2 hours, 26 minutes
Last reboot reason : Other
1024
Mbytes SDRAM
0
Kbytes NVRAM Memory
Type
: LST1GT48LEC1
Software : 12500-CMW710-R7377P01
PCB
: Ver.A
Board Cpu:
Number of Cpld: 1
Cpld 0:
SoftWare
: 003
PowChipA
: 004
PowChipB
: 004
4
CpuCard
Type
: LSR1CPAE
PCB
: Ver.C
Number of Cpld: 1
Cpld 0:
SoftWare
BootRom
: 001
: 2.14
-------- Note③
Mbus card
Type
: LSR1MBCB
Software
: 115
PCB
: Ver.B
LST2SF08C1 8:
--------Note⑤
uptime is 0 weeks, 0 days, 2 hours, 26 minutes
Last reboot reason : Heart-beat timeout reboot
128
Mbytes SDRAM
0
Kbytes NVRAM Memory
Type
: LST2SF08C1
BootRom
: 2.13
--------Note④
Software : 12500-CMW710-R7377P01
PCB
: Ver.A
Board Cpu:
Number of Cpld: 1
Cpld 0:
SoftWare
PowChipA
: 001
: 001
<HPE>display version
LST1MRPNE1 1/0:
uptime is 0 weeks, 0 days, 3 hours, 53 minutes
Last reboot reason : User reboot
8192
Mbytes SDRAM
1024
Kbytes NVRAM Memory
Type
: LST1MRPNE1
BootRom
: 1.08
--------Note⑧
Software : 12500-CMW710-R7377P01
PCB
: Ver.B
Board Cpu:
Number of Cpld: 2
Cpld 0:
SoftWare
: 001
Cpld 1:
SoftWare
PowChipA
: 001
: 001
EcpCpu
Type
: LST1ECP
PCB
: Ver.B
BootRom
: 1.06
--------Note⑨
Mbus card
5
Type
: LSR1MBCB
Software
: 115
PCB
: Ver.B
……
LST1XP48LFD1 4/3:
uptime is 0 weeks, 0 days, 3 hours, 52 minutes
Last reboot reason : Other
2816
Mbytes SDRAM
0
Kbytes NVRAM Memory
Type
: LST1XP48LFD1
Software : 12500-CMW710-R7377P01
PCB
: Ver.A
Board Cpu:
Number of Cpld: 2
Cpld 0:
SoftWare
: 001
Cpld 1:
SoftWare
: 001
PowChipA
: 001
PowChipB
: 001
CpuCard
Type
: LST1CPC
PCB
: Ver.A
Number of Cpld: 1
Cpld 0:
SoftWare
BootRom
: 001
: 1.07
--------Note⑦
Mbus card
Type
: LSR1MBCB
Software
: 115
PCB
: Ver.B
LST1SF08E1 4/17:
uptime is 0 weeks, 0 days, 3 hours, 52 minutes
Last reboot reason : Power on
512
Mbytes SDRAM
0
Kbytes NVRAM Memory
Type
: LST1SF08E1
BootRom
: 1.08
--------Note⑥
Software : 12500-CMW710-R7377P01
PCB
: Ver.A
Board Cpu:
Number of Cpld: 1
Cpld 0:
SoftWare
PowChipA
: 001
: 001
6
Table 4 shows ISSU compatibility between current version and history version.
Table 4 ISSU Version Compatibility Matrix
Current version
History version
ISSU compatibility
12500-CMW710-R7377
Compatible
12500-CMW710-R7376
Compatible
12500-CMW710-R7375
Not support
12500-CMW710-R7374
Compatible
12500-CMW710-F7373
Incompatible
12500-CMW710-F7372
Incompatible
12500-CMW710-F7371
Not support
12500-CMW710-R7328P04
Incompatible
12500-CMW710-R7328P03
Incompatible
12500-CMW710-R7328P02
Incompatible
12500-CMW710-R7328P01
Incompatible
12500-CMW710-R7328
Incompatible
12500-CMW710-R7326
Incompatible
12500-CMW710-R7129
Incompatible
12500-CMW710-R7377P01
Upgrading restrictions and guidelines
•
Versions F7373 and R7374 cannot be upgraded to the current software version through ISSU if
OpenFlow is configured. The same restriction applies to downgrading from the current software
version to F7373 or R7374 through ISSU. The restriction exists even though OpenFlow
configurations have been deleted.
•
Do not use ISSU to downgrade the software version to F7372 or an earlier version.
Hardware feature updates
12500-CMW710-R7377P01
None
12500-CMW710-R7377
Deleted:
•
JG836A HP FlexFabric 12518E AC Switch TAA-compliant Chassis
•
JG834A HP FlexFabric 12508E AC Switch TAA-compliant Chassis
•
JG835A HP FlexFabric 12508E DC Switch TAA-compliant Chassis
•
JG837A HP FlexFabric 12518E DC Switch TAA-compliant Chassis
•
JG803A HP FlexFabric 12500E TAA-compliant Main Processing Unit
7
•
JG797A HP FlexFabric 12500 48-port 10GbE SFP+ FD TAA-compliant Module
•
JG791A HP FlexFabric 12500 16-port 40GbE QSFP+ FD TAA-compliant Module
•
JG795A HP FlexFabric 12500 40-port 10GbE SFP+ FG TAA-compliant Module
•
JG793A HP FlexFabric 12500 40-port 10GbE SFP+ FD TAA-compliant Module
•
JG789A HP FlexFabric 12500 4-port 100GbE CFP FG TAA-compliant Module
•
JG787A HP FlexFabric 12500 4-port 100GbE CFP FD TAA-compliant Module
•
JG799A HP FlexFabric 12508E TAA-compliant Fabric Module
•
JG801A HP FlexFabric 12518E TAA-compliant Fabric Module
12500-CMW710-R7376
None
12500-CMW710-R7375
None
12500-CMW710-R7374
None
12500-CMW710-F7373
None
12500-CMW710-F7372
Deleted:
•
JG328A HP 240 40G QSFP+ 5m DAC Cable.
12500-CMW710-F7371
None
12500-CMW710-R7328P01
None
12500-CMW710-R7328
None
8
12500-CMW710-R7326
Newly added:
•
JG784A HPE FlexFabric 12518E AC Switch Chassis
•
JG782A HPE FlexFabric 12508E AC Switch Chassis
•
JG783A HPE FlexFabric 12508E DC Switch Chassis
•
JG785A HPE FlexFabric 12518E DC Switch Chassis
•
JG802A HPE FlexFabric 12500E Main Processing Unit
•
JG796A HPE FlexFabric 12500 48-port 1/10GbE SFP+ FD Module
•
JG790A HPE FlexFabric 12500 16-port 40GbE QSFP+ FD Module
•
JG794A HPE FlexFabric 12500 40-port 1/10GbE SFP+ FG Module
•
JG792A HPE FlexFabric 12500 40-port 1/10GbE SFP+ FD Module
•
JG788A HPE FlexFabric 12500 4-port 100GbE CFP FG Module
•
JG786A HPE FlexFabric 12500 4-port 100GbE CFP FD Module
•
JG798A HPE FlexFabric 12508E Fabric Module
•
JG800A HPE FlexFabric 12518E Fabric Module
Software feature and command updates
12500-CMW710-R7377P01
None
12500-CMW710-R7377
For more information about the software feature and command update history, see HP
12500-CMW710-R7377 Release Notes (Software Feature Changes).
12500-CMW710-R7376
For more information about the software feature and command update history, see HP
12500-CMW710-R7376 Release Notes (Software Feature Changes).
12500-CMW710-R7375
For more information about the software feature and command update history, see HP
12500-CMW710-R7375 Release Notes (Software Feature Changes).
12500-CMW710-R7374
For more information about the software feature and command update history, see HP
12500-CMW710-R7374 Release Notes (Software Feature Changes).
9
12500-CMW710-F7373
For more information about the software feature and command update history, see HP
12500-CMW710-F7373 Release Notes (Software Feature Changes).
12500-CMW710-F7372
For more information about the software feature and command update history, see HP
12500-CMW710-F7372 Release Notes (Software Feature Changes).
12500-CMW710-F7371
For more information about the software feature and command update history, see HP
12500-CMW710-F7371 Release Notes (Software Feature Changes).
12500-CMW710-R7328P01
For more information about the software feature and command update history, see HP
12500-CMW710-R7328P01 Release Notes (Software Feature Changes).
12500-CMW710-R7328
For more information about the software feature and command update history, see HP
12500-CMW710-R7328 Release Notes (Software Feature Changes).
12500-CMW710-R7326
For more information about the software feature and command update history, see HP
12500-CMW710-R7326 Release Notes (Software Feature Changes).
MIB updates
Table 5 MIB updates
Item
MIB file
Module
Description
12500-CMW710-R7377P01
New
None
None
None
Modified
None
None
None
New
None
None
None
Modified
None
None
None
New
None
None
None
Modified
None
None
None
12500-CMW710-R7377
12500-CMW710-R7376
10
Item
MIB file
Module
Description
New
None
None
None
Modified
None
None
None
New
hh3c-config-man.mib
hh3cCfgOperateTable
Support
hh3cCfgOperateSrvVP
NName
Modified
rfc1213.mib
ip Group {mib-2.4}
ipForwarding,
ipDefaultTTL only
support read operation
New
None
None
None
Modified
None
None
None
New
None
None
None
Modified
None
None
None
New
None
None
None
Modified
None
None
None
12500-CMW710-R7375
12500-CMW710-R7374
12500-CMW710-F7373
12500-CMW710-F7372
12500-CMW710-F7371
12500-CMW710-R7328P01
New
None
None
None
Modified
None
None
None
New
None
None
None
Modified
None
None
None
New
First Release
None
None
Modified
First Release
None
None
12500-CMW710-R7328
12500-CMW710-R7326
Operation changes
Operation changes in
12500-CMW710-R7377P01
None
Operation changes in 12500-CMW710-R7377
None
11
Operation changes in 12500-CMW710-R7376
None
Operation changes in 12500-CMW710-R7375
•
This release does not support configuring an interface as both an outbound mirroring source
port and sFlow sampled interface if it is on one of the following 16-port 10-GbE LPUs (JC782A,
JC783A and JC814A).
Operation changes in 12500-CMW710-R7374
•
Added support for isolating an interface card on which the buffer-managed SRAM fails.
Operation changes in 12500-CMW710-F7373
None
Operation changes in 12500-CMW710-F7372
None
Operation changes in 12500-CMW710-F7371
None
Operation changes in
12500-CMW710-R7328P01
None
Operation changes in 12500-CMW710-R7328
•
IRF physical ports do not support the PFC feature.
Operation changes in 12500-CMW710-R7326
•
Operation changes in 12500-CMW710-R7326 Version, 18xx cannot be upgraded to version
73xx by using the v5to7 upgrade command.
•
The upper limit for the Maximum Receive Unit (MRU) of the 16-port 10-GbE modules (JC782A,
JC783A and JC814A) was changed from 8168 to 8164. If the MRU configured before upgrade
is larger than 8164, the MRU will be restored to the default after upgrade.
•
The maximum number of static MAC entries (including black hole MAC entries) was changed
from 4K to 32K. More MAC entries on a card need more time to be assigned after the card starts
up. If the software is downgraded from this version to an earlier version, the MAC entries
12
exceeding the specification will not be assigned. If the software is upgraded to this version,
MAC entries are not affected.
•
Incompatible ISSU is available for an upgrade from 71xx to 73xx. However, it is not available for
a downgrade from 73xx to 71xx.
Restrictions and cautions
Restriction 1
[Configuration management] Do not perform any configuration within one minute prior to an
active/standby switchover because the configurations might be lost after the switchover.
Restriction 2
[Tunnel] IPv6 addresses that begin with 2002 can only be used on 6to4 tunnels. Use of such
addresses on other types of tunnels causes forwarding problems.
Restriction 3
[QoS] Make sure the CBS and EBS configured for CAR are larger than the maximum packet size.
Otherwise, the CAR policy cannot regulate traffic precisely.
Restriction 4
[Port] Do not reinsert an optical-to-electrical conversion module within 1 second after it is removed.
Otherwise, the ports on the module will not activate.
Restriction 5
[Port] Replace failed transceiver modules as soon as possible to avoid continual failure event
alarms.
Restriction 6
[QoS] If the weights configured for two WRR queues have a big difference, the WRR queue with
higher weight might not get all the bandwidth it was assigned. If the ratio is not in its simplest form,
the software automatically reduces the WRR queue ratio to its simplest form to avoid the problem.
For example, if the configured WRR queue weight ratio is 20:30, the effective ratio will be 2:3.
Restriction 7
[Port] After configuring Jumbo frame or Switching LAN/WAN mode on a 10-GE port that connects
with a single optical fiber, the LED of the port turns to abnormal. You need to insert both transmit
and receive fiber.
Restriction 8
[L3VPN] If system-working-mode standard is configured, the reserved VLANs for MPLS L3VPNs
cannot be used for any other services, including Layer-2/-3 forwarding.
Restriction 9
[MAC] Each time the number of MAC address entries on a port or VLAN reaches the user-configured
limit, the system displays a warning message. If this message is continually displayed for a VLAN or
port, check the port or VLAN for MAC attacks and shut down the affected port or ports as necessary.
Restriction 10
[Console] Flow control settings are not configurable if you are logged in through the console port of
an MPU prefixed with LST2MRPNC (JC072A, JC808A, JC072B or JG497A).
Restriction 11
[IRF] After being bound to an IRF port, an Ethernet port supports only the shutdown, description,
and display commands.
13
Restriction 12
[IRF] The BFD MAD VLAN must not have physical loops or be configured for any services other than
BFD MAD.
Restriction 13
[Enhanced IRF] In enhanced IRF mode, the following requirements must be met:
•
Each IRF member switch must have two MPUs.
•
The IRF fabric uses a ring topology.
•
The downstream switch must have one link to each IRF member switch and aggregate these
links in an aggregation group.
Restriction 14
[IRF] The physical ports bound to IRF port 1 (west port) on a switch must be connected to the
physical ports bound to IRF port 2 (east port) on its neighbor switch. If IRF port 1 on one switch is
connected to IRF port 1 on the other switch, and the physical ports have been UP, system exceptions
will occur. To recover the system, you must connect the physical ports correctly (IRF port 1 on switch
1 to IRF port 2 on switch 2) and reboot all the member switches.
Restriction 15
[Enhanced IRF] In enhanced IRF mode, all ports in chassis do not support routed mode or RRPP.
Restriction 16
[IRF] If a 1XXX release switch attempts to join a 7XXX release IRF fabric, the software auto-update
function cannot automatically synchronize the 7XXX release software to the joining switch. Likewise,
if a 7XXX release switch attempts to join a 1XXX release IRF fabric, the software auto-update
function cannot automatically synchronize the 1XXX release software to the joining switch.
Restriction 17
[EVI] To avoid loops, do not assign transport-facing ports to extended VLANs. To avoid data breach,
make sure all edge devices in an EVI network maintain the same list of extended VLANs.
Restriction 18
[Active/standby switchover] An active/standby switchover can be started only if the HA actions for the
most recent active/standby switchover have been completed in all MDCs. Before an active/standby
switchover is complete, interface card and MDC manipulations are not allowed. Examples include
interface card removal or insertion, card assignment or removal for MDCs, and port assignment or
removal for MDCs.
Restriction 19
[Device management] Type-B (JC066A, JC067B, JC819A or JC820A) and Type-C (JC657A,
JC658A, JC816A or JC815A) switching fabric modules should not generally be mixed in the same
chassis, but they can be on a short-term basis during an upgrade to Type-C fabrics without powering
off the chassis. This short-term mixing of modules is allowed to prevent traffic disruption during the
upgrade.
Restriction 20
[MDC with IRF] If an MDC on a two-chassis IRF fabric contains only interface modules on the
subordinate chassis, BFD cannot work in the MDC.
Restriction 21
[MPLS] If a 12500 switch acts as the penultimate hop and the peer PE is configured to advertise an
explicit null label of 0, the switch forwards MPLS packets with VLAN ID 0. If the PE cannot process
packets with VLAN ID 0, the interface connecting the switch to the PE must be configured as a trunk
port.
14
Restriction 22
[QoS] Configuring WRR on an interface might cause other interfaces on the same forwarding chip to
drop packets.
Open problems and workarounds
None
List of resolved problems
Resolved problems in
12500-CMW710-R7377P01
201606020523
•
Symptom: When the scheduling module on the FAP chip of a line card has an error, the packet
forwarding of other line cards might be affected.
•
Condition: This symptom might occur if the scheduling module on the FAP chip of a line card
has a hardware error.
201605300071
•
Symptom: VLAN ID-based PBR does not take effect when the configuration is made after the
switch is rebooted.
•
Condition: This symptom might occur if VLAN ID-based PBR is configured after the switch is
rebooted.
201605110262
•
Symptom: Split IRF fabrics cannot reunite when certain conditions exist.
•
Condition: This symptom might occur if the physical ports bound to an IRF port are on a 40-port
1/10GbE SFP+ FG Module (JG794A) that has more than 18 ports working with 100-Mbps or
1000-Mbps transceiver modules.
201604110290
•
Symptom: CVE-2016-2842
•
Condition: Fixed vulnerability in the doapr_outch function in crypto/bio/b_print.c, which allows
remote attackers to cause a denial of service (out-of-bounds write or memory consumption) or
possibly have unspecified other impact via a long string.
201603310172
•
Symptom: Board state of FD/FG line card changes to fault after a chassis reboot.
•
Condition: This symptom occurs if configure MSTP VLAN-to-instance mapping table and the
number of VLAN exceeds 3000.
201603220607
•
Symptom: CVE-2016-0705
15
•
Condition: Fixed vulnerability when OpenSSL parses malformed DSA private keys and could
lead to a DoS attack or memory corruption for applications that receive DSA private keys from
untrusted sources.
•
Symptom: CVE-2016-0798
•
Condition: Fixed vulnerability in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows
remote attackers to cause a denial of service (memory consumption) by providing an invalid
username in a connection attempt.
•
Symptom: CVE-2016-0797
•
Condition: Fixed vulnerability in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allow
remote attackers to cause a denial of service (heap memory corruption or NULL pointer
dereference).
•
Symptom: CVE-2016-0799
•
Condition: Fixed vulnerability in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g
improperly calculates string lengths, which allows remote attackers to cause a denial of service
which could lead to memory allocation failure or memory leaks.
•
Symptom: CVE-2016-0702
•
Condition: Fixed vulnerability in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g which
makes it easier for local users to discover RSA keys leveraging cache-bank conflicts, aka a
"CacheBleed" attack.
201603170163
•
Symptom: CVE-2016-0701
•
Condition: Fixed vulnerability in the DH_check_pub_key function which makes it easier for
remote attackers to discover a private DH (Diffie-Hellman) exponent by making multiple
handshakes with a peer that chose an inappropriate number. This issue affects OpenSSL
version 1.0.2. and addressed in 1.0.2f. OpenSSL 1.0.1 is not affected by this CVE.
•
Symptom: CVE-2015-3197
•
Condition: Fixed vulnerability when using SSLv2 which can be exploited in a man-in-the-middle
attack, if device has disabled ciphers.
Resolved problems in 12500-CMW710-R7377
201601130447
•
Symptom: The switch reboots unexpectedly.
•
Condition: This symptom occurs if the switch has LDP enabled and receives abnormal LDP
PDUs with the PDU length value of 0 in the header.
201601080143
•
Symptom: The switch prints IRF link failure logs.
•
Condition: This symptom occurs if the FAP chips where the IRF physical interfaces reside have
ECC errors, which will cause the chips to be reset.
16
201512280464
•
Symptom: CVE-2015-3194
•
Condition: Fixed vulnerability which can be exploited in a DoS attack, if device is presented with
a specific ASN.1 signature using the RSA.
•
Symptom: CVE-2015-3195
•
Condition: Fixed vulnerability with malformed OpenSSL X509_ATTRIBUTE structure used by
the PKCS#7 and CMS routines which may cause memory leak.
•
Symptom: CVE-2015-3196
•
Condition: Fixed vulnerability where a race condition can occur when specific PSK identity hints
are received.
•
Symptom: CVE-2015-1794
•
Condition: Fixed vulnerability if a client receives a ServerKeyExchange for an anonymous
Diffie-Hellman (DH) ciphersuite which can cause possible Denial of Service (DoS) attack.
201511200312
•
Symptom: CVE-2015-7871
•
Condition: Cause ntpd to accept time from unauthenticated peers.
•
Symptom: CVE-2015-7704
•
Condition: An ntpd client forged by a DDoS attacker located anywhere on the Internet, that can
exploit NTP's to disable NTP at a victim client or it may also trigger a firewall block for packets
from the target machine.
•
Symptom: CVE-2015-7705
•
Condition: The DDoS attacker can send a device a high volume of ntpd queries that are
spoofed to look like they come from the client. The servers then start rate-limiting the client.
•
Symptom: CVE-2015-7855
•
Condition: Ntpd mode 6 or mode 7 packet containing an unusually long data value could
possibly use cause NTP to crash, resulting in a denial of service.
201511180374
•
Symptom: After the evi arp-suppression enable command is executed on the local EVI edge
switch and the remote EVI edge switch, a local host cannot ping a remote host.
•
Condition: This symptom might occur if the following conditions exist:


Only ARP packets are sent between the hosts.
The MAC address of the local host ages out on both the local and remote edge switches.
201510290071
•
Symptom: Cannot decode multi area addresses in SPB hello PDUs.
•
Condition: This symptom can be seen when SPBM interoperates with other vendor’s device.
201511100238
•
Symptom: The routes for the secondary IP addresses of interfaces cannot be advertised.
•
Condition: This symptom might occur if OSPF NSR is enabled and the LSA length is set to 264
bytes.
17
201511100206
•
Symptom: After a switch reboot and an active/standby MPU switchover, the MPUs have
different STP states for an aggregate interface, and the aggregation member ports cannot
forward traffic.
•
Condition: This symptom might occur if the following operations are performed:
a. Enable STP on an aggregation interface.
b. Reboot the switch.
c. Perform an active/standby MPU switchover.
201511100204
•
Symptom: The switch is disconnected from the OpenFlow controllers when the switch receives
a large number of ARP packets.
•
Condition: This symptom might occur if OpenFlow is configured, and the switch receives a large
number of ARP packets.
201511100199
•
Symptom: BGP neighbor flapping occurs when the switch receives dense traffic.
•
Condition: This symptom might occur when the switch receives dense traffic.
201511100189
•
Symptom: The switch cannot process VRRP multicast packets correctly when the switch is
attacked by dense high-priority multicast traffic. As a result, a VRRP group has two masters.
•
Condition: This symptom might occur if the switch is attacked by dense high-priority multicast
traffic.
201511100184
•
Symptom: MPUs reboot unexpectedly if the switch has multiple OSPF neighbors and OSPF
neighbor flapping has lasted for a long period of time.
•
Condition: This symptom might occur if the switch has multiple OSPF neighbors, and OSPF
neighbor flapping has lasted for a long period of time.
Resolved problems in 12500-CMW710-R7376
201509290286
•
Symptom: The switch prompts that the login password or shared key is incorrect when working
with a TACACS server to authenticate the user.
•
Condition: This symptom occurs if the switch runs Release 7375 and acts as a TACACS client.
201509170051
•
Symptom: The switch fails to establish an MPLS TE tunnel with a peer device because the
incoming RSVP path message cannot be identified.
•
Condition: This symptom occurs if the peer device is not an HP device.
18
201509170050
•
Symptom: Some NETCONF sessions cannot be established when multiple users log in to the
switch through NETCONF for configuration at the same time.
•
Condition: This symptom occurs if multiple users log in to the switch through NETCONF for
configuration at the same time.
201508170050
•
Symptom: A switch configured with IPsec fails to be authenticated by a Comware-V5-based
peer device.
•
Condition: This symptom might occur if the switch is configured with an IKE-based IPsec policy
and the PFS feature is enabled for the IPsec policy.
201508120090
•
Symptom: Power supply fault information in the display power-supply verbose command
output is inaccurate.
•
Condition: This symptom occurs if one power supply module is faulty and its output voltage is
greater than the system limit.
201508120028
•
Symptom: In a two-chassis IRF fabric, one member device cannot forward Layer 3 packets
through the other member device to a connected server after a NIC active/standby switchover
occurs on the server.
•
Condition: This symptom occurs if the following conditions exist:

The server has one MAC address and is configured with multiple IP addresses for the two
NICs operating in active/standby mode.

The two NICs on the server connect to interfaces on the two member devices with the same
slot number and port number, for example, interface 1/3/0/1 on the master device and
interface 2/3/0/1 on the subordinate device.

The IRF fabric has learned multiple ARP entries with the same MAC address (server MAC
address) on a VLAN interface.
201507220171
•
Symptom: The switch does not update the corresponding ARP entry when receiving an ARP
reply.
•
Condition: This symptom occurs if the target IP address in the ARP reply is a directed broadcast
address.
201507210314
•
Symptom: Loops exist between one 12500 switch and another Comware-V7-based device
interconnected through dynamic Layer 2 aggregate interfaces.
•
Condition: This symptom occurs if the following operations are performed:

Enable the spanning tree feature globally on one device and disable the spanning tree
feature globally on the other device.

The aggregation group on each device has two or more member ports.

Remove all but one member port from the aggregation group on the spanning-tree-disabled
device when all member ports are up.
19

Shut down all member ports in the aggregation group on the spanning-tree-enabled device,
remove them from the aggregation group, and bring up all removed member ports.
201507200291
•
Symptom: A 12500 switch cannot ping the peer device when they are interconnected through
dynamic Layer 3 aggregate interfaces.
•
Condition: This symptom occurs if the following operations are performed:

Enable the spanning tree feature globally on the switch.

Set the spanning tree mode to PVST.

Assign interfaces to a dynamic Layer 3 aggregation group on the switch.
201507160287
•
Symptom: CVE-2014-8176
•
Condition: If a DTLS peer receives application data between the ChangeCipherSpec and
Finished messages. May result in a segmentation fault or potentially, memory corruption.
•
Symptom: CVE-2015-1788
•
Condition: When processing an ECParameters structure OpenSSL enters an infinite loop. This
can be used to perform denial of service against any system which processes public keys,
certificate requests or certificates.
•
Symptom: CVE-2015-1789
•
Condition: X509_cmp_time does not properly check the length of the ASN1_TIME string and/or
accepts an arbitrary number of fractional seconds in the time string. An attacker can use this to
craft malformed certificates and CRLs of various sizes and potentially cause a segmentation
fault, resulting in a DoS on applications that verify certificates or CRLs.
•
Symptom: CVE-2015-1790
•
Condition: The PKCS#7 parsing code does not handle missing inner EncryptedContent
correctly. An attacker can craft malformed PKCS#7 blobs with missing content and trigger a
NULL pointer dereference on parsing.
•
Symptom: CVE-2015-1791
•
Condition: If a NewSessionTicket is received by a multi-threaded client when attempting to
reuse a previous ticket then a race condition can occur potentially leading to a double free of the
ticket data.
201507150062
•
Symptom: The display power-supply verbose command displays inaccurate values for the
System power redundant (actual) and System power allocated fields.
•
Condition: This symptom occurs when the display power-supply verbose command is
executed.
Resolved problems in 12500-CMW710-R7375
201506230017
•
Symptom: CVE-2015-3143
20
•
Condition: cURL and libcurl 7.10.6 through 7.41.0 does not properly re-use NTLM connections,
which allows remote attackers to connect as other users via an unauthenticated request.
•
Symptom: CVE-2015-3148
•
Condition: cURL and libcurl 7.10.6 through 7.41.0 does not properly re-use authenticated
negotiate connections, which allows remote attackers to connect as other users via a request.
201506040234
•
Symptom: The DHCP server on the switch has a static address pool and a dynamic address
pool. DHCP clients do not preferentially use the DNS servers of the static address pool.
•
Condition: This symptom might occur if the network segment of the dynamic address pool
includes all addresses in the static address pool, and the address pools have different DNS
servers.
201506040427
•
Symptom: NQA operations fail.
•
Condition: This symptom might occur if a large number of NQA operations are configured.
201506040209
•
Symptom: A 16-port 10-GbE LPU, JC782A, JC783A or JC814A drops some packets when it
forwards traffic.
•
Condition: This symptom might occur if an interface on the LPU is configured as an outbound
mirroring source port and enabled with sFlow.
201506040085
•
Symptom: Operation of the switch is affected by repeated reboots of an isolated switching fabric
module.
•
Condition: This symptom might occur if a switching fabric module is isolated for hardware failure
by using the board-offline command.
201506030144 (CVE-2015-5434)
•
Symptom: When an interface without MPLS enabled receives MPLS-labeled packets, the
interface incorrectly forwards the MPLS-labeled packets to the next LSR by LFIB entry.
•
Condition: This symptom occurs when the interface does not have MPLS enabled and the
interface receives MPLS-labeled packet that match the FIB entries.
201506010072
•
Symptom: The switch displays the message transceiver type not supported for a transceiver
module, but the transceiver module can work correctly.
•
Condition: This symptom occurs if an HP X130 10G SFP+ LC LH 40km Transceiver (JG234A)
is installed in a 40-port 10GbE SFP+ FD Module (JG792A).
201505200097
•
Symptom: Memory leaks.
•
Condition: This symptom occurs if a large number of portal users come online, access the
Internet, and go offline.
21
201505200087
•
Symptom: A switch cannot work correctly.
•
Condition: This symptom occurs if the switch receives a large number of packets and sends
them to the CPU.
201505200079
•
Symptom: An OpenFlow switch cannot send ARP packets to the controller after the switch is
rebooted.
•
Condition: This symptom occurs if the switch is rebooted.
201505180201
•
Symptom: The first ICMP packet for an NQA operation has a long round-trip time.
•
Condition: This symptom occurs if NQA is configured.
201505180143
•
Symptom: The CPU usage of a switch is high because of a login process.
•
Condition: This symptom occurs if the following operations are performed:

Log in to the switch through Telnet.

Press Ctrl+K to disconnect from the switch before entering the username and password.
201504270393
•
Symptom: A static route cannot be deleted.
•
Condition: This symptom occurs if the static route has a static recursive route.
201504270389
•
Symptom: A switch learns an incorrect ARP entry.
•
Condition: This symptom occurs if the switch receives an ARP request with an all-zero sender
IP address.
201504200203
•
Symptom: A port that is shut down by using the shutdown command comes up unexpectedly
and then goes down after a few seconds.
•
Condition: This symptom might occur if the transceiver module or fiber for the port is installed
and then removed and the port receives optical signals from the peer port.
201504170471
•
Symptom: CVE-2015-1799
•
Condition: Authentication doesn’t protect symmetric associations against DoS attacks.
201504130020
•
Symptom: CVE-2015-0209
•
Condition: A malformed EC private key file consumed via the d2i_ECPrivateKey function could
cause a use after free condition. This could lead to a DoS attack or memory corruption for
applications that receive EC private keys from untrusted sources.
•
Symptom: CVE-2015-0286
22
•
Condition: DoS vulnerability in certificate verification operation. Any application which performs
certificate verification is vulnerable including OpenSSL clients and servers which enable client
authentication.
•
Symptom: CVE-2015-0287
•
Condition: Reusing a structure in ASN.1 parsing may allow an attacker to cause memory
corruption via an invalid write. Applications that parse structures containing CHOICE or ANY
DEFINED BY components may be affected.
•
Symptom: CVE-2015-0288
•
Condition: The function X509_to_X509_REQ will crash with a NULL pointer dereference if the
certificate key is invalid.
•
Symptom: CVE-2015-0289
•
Condition: The PKCS#7 parsing code does not handle missing outer ContentInfo correctly. An
attacker can craft malformed ASN.1-encoded PKCS#7 blobs with missing content and trigger a
NULL pointer dereference on parsing.
•
Symptom: CVE-2015-0292
•
Condition: A vulnerability existed in previous versions of OpenSSL related to the processing of
base64 encoded data.
•
Symptom: CVE-2015-0293
•
Condition: A malicious client can trigger an OPENSSL_assert in servers that both support
SSLv2 and enable export cipher suites by sending a specially crafted SSLv2
CLIENT-MASTER-KEY message.
201504080172
•
Symptom: When congestion occurs in a queue between an interface of a 16-port 10-GbE
interface card, (JC782A, JC783A or JC814A) and a GE interface, packet loss occurs in the
queues with the same priority between interfaces of the XP16 interface card and other
interfaces.
•
Condition: This symptom can be seen when traffic is forwarded from an interface of the 16-port
10-GbE interface card to a GE interface of another interface card and congestion occurs.
Resolved problems in 12500-CMW710-R7374
201503190430
•
Symptom: TCAM ECC errors occur and cause packet loss on LST1XP40RFG or
LST1CP4RFG interface cards (JG794A, JG788A).
•
Condition: This symptom might be seen on LST1XP40RFG or LST1CP4RFG interface cards.
201503020294
•
Symptom: CVE-2014-3571
•
Condition: A carefully crafted DTLS message can cause a segmentation fault in OpenSSL due
to a NULL pointer dereference. This could lead to a Denial of Service attack.
•
Symptom: CVE-2015-0206
23
•
Condition: A memory leak can occur in the dtls1_buffer_record function under certain
conditions. In particular this could occur if an attacker sent repeated DTLS records with the
same sequence number but for the next epoch. The memory leak could be exploited by an
attacker in a Denial of Service attack through memory exhaustion.
•
Symptom: CVE-2015-0205
•
Condition: An OpenSSL server will accept a DH certificate for client authentication without the
certificate verify message. This effectively allows a client to authenticate without the use of a
private key. This only affects servers which trust a client certificate authority which issues
certificates containing DH keys.
•
Symptom: CVE-2014-3570
•
Condition: Bignum squaring (BN_sqr) may produce incorrect results on some platforms,
including x86_64. This bug occurs at random with a very low probability, and is not known to be
exploitable in any way.
•
Symptom: CVE-2015-0204
•
Condition: An OpenSSL client will accept the use of an RSA temporary key in a non-export RSA
key exchange ciphersuite. A server could present a weak temporary key and downgrade the
security of the session.
•
Symptom: CVE-2014-3572
•
Condition: An OpenSSL client will accept a handshake using an ephemeral ECDH ciphersuite
using an ECDSA certificate if the server key exchange message is omitted. This effectively
removes forward secrecy from the ciphersuite.
•
Symptom: CVE-2014-8275
•
Condition: By modifying the contents of the signature algorithm or the encoding of the signature,
it is possible to change the certificate's fingerprint. Only custom applications that rely on the
uniqueness of the fingerprint may be affected.
•
Symptom: CVE-2014-3569
•
Condition: The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 0.9.8zc, 1.0.0o, and
1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote
attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an
unexpected handshake, as demonstrated by an SSLv3 handshake to a no-ssl3 application with
certain error handling.
201502160110
•
Symptom: A client requests an IP address again from the switch acting as a DHCP server.
•
Condition: This symptom can be seen if packets from the client arrive at a different interface on
the switch after it requests an IP address.
201502160108
•
Symptom: Packets originated on the switch have a TTL of 1.
•
Condition: This symptom can be seen if the ipDefaultTTL node is set to 1 by an SNMP attack
on the switch.
201407070018
•
Symptom: The portal authentication feature cannot work correctly.
24
•
Condition: This symptom can be seen after the switch reboots.
201410210219
•
Symptom: The undo rule command in ACL view cannot be executed successfully when
attributes in an ACL rule are specified.
•
Condition: None.
201501070493
•
Symptom: For the HP X120 1G SFP RJ45 T transceiver module (JD089B), the display
transceiver interface command displays UNKNOWN for the Connector Type field.
•
Condition: None.
Resolved problems in 12500-CMW710-F7373
201411050158
•
Symptom: When the system time is not within the time range defined for an ACL rule used by a
portal access policy, the ACL rule still takes effect.
•
Condition: This symptom can be seen when the portal access policy uses an ACL rule and the
ACL is configured with a time range.
201410240137
•
Symptom: CVE-2014-3567
•
Condition: When an OpenSSL SSL/TLS/DTLS server receives a session ticket the integrity of
that ticket is first verified. In the event of a session ticket integrity check failing, OpenSSL will fail
to free memory causing a memory leak. By sending a large number of invalid session tickets an
attacker could exploit this issue in a Denial of Service attack.
•
Symptom: SSL 3.0 Fallback protection
•
Condition: OpenSSL has added support for TLS_FALLBACK_SCSV to allow applications to
block the ability for a MITM attacker to force a protocol downgrade. Some client applications
(such as browsers) will reconnect using a downgraded protocol to work around interoperability
bugs in older servers. This could be exploited by an active man-in-the-middle to downgrade
connections to SSL 3.0 even if both sides of the connection support higher protocols. SSL 3.0
contains a number of weaknesses including POODLE (CVE-2014-3566).
•
Symptom: CVE-2014-3568
•
Condition: When OpenSSL is configured with "no-ssl3" as a build option, servers could accept
and complete a SSL 3.0 handshake, and clients could be configured to send them.
201410160045
•
Symptom: The switch learns BGP routes slowly.
•
Condition: This symptom can be seen when the switch has learned a large amount of BGP
routes with different AS_PATH attributes.
201412010343
•
Symptom: An interface card might be rebooted or isolated unexpectedly.
•
Condition: This symptom can be seen when the traffic load on the interface card is heavy and
the CPU of the interface card sends packets frequently.
201409090538
•
Network: A-----B-----C
25
•
Symptom: The default routes that device B advertises to device C for the first time are correct.
Later, device B advertises the updates for only one default route to device C.
•
Condition: This symptom can be seen when device A advertises several default routes with
different RDs to device B and device B advertises these default routes to device C.
201409090508
•
Symptom: After the patch is installed, an aggregate group member port cannot be assigned to
its aggregation group.
•
Condition: This symptom can be seen when the following conditions exist:

The switch is configured with LACP.

An aggregation group member port on an interface card is in Individual state.
201409150123
•
Symptom: The system displays logs showing that the MAD status flaps for some aggregate
interfaces.
•
Condition: This symptom can be seen when the device is configured with multiple aggregation
groups and is configured with LACP MAD.
201501070499
•
Symptom: The output interface is not updated for the host route of VPN B.
•
Condition: This symptom can be seen when routes of VPN B are redistributed into VPN A and
ARP entries in VPN B are changed.
201412300342
•
Symptom: The system might take a long time to obtain node information for interfaces on a
card.
•
Condition: This symptom can be seen when an interface of the card is installed with a failed
transceiver module.
201412120330
•
Symptom: BGP cannot form ECMP routing over routes with a MED of 0 or null.
•
Condition: This symptom can be seen if BGP is not configured with a MED or configured with a
MED of 0.
201412310300
•
Symptom: CVE-2014-9295
•
Condition: Stack-based buffer overflows in ntpd in NTP before 4.2.8 allow remote attackers to
execute arbitrary code via a crafted packet.
Resolved problems in 12500-CMW710-F7372
201409090487
•
Symptom: The switch reboots unexpectedly.
•
Condition: This symptom occurs when MPLS VPN is enabled on the switch and the switch
receives abnormal MPLS Echo Reply packets.
201408290277
•
Symptom: CVE-2014-3508.
26
•
Condition: A flaw in OBJ_obj2txt may cause pretty printing functions such as
X509_name_oneline, X509_name_print_ex et al. to leak some information from the stack.
Applications may be affected if they echo pretty printing output to the attacker.
201408290278
•
Symptom: CVE-2008-5161
•
Description: Error handling in the SSH protocol in several SSH servers/clients, including
OpenSSH 4.7p1 and possibly other versions, when using Cipher Block Chaining (CBC) mode,
makes it easier for remote attackers to recover certain plaintext data.
201410200318
•
Symptom: The switch cannot forward packets to the UDP helper server.
•
Condition: This symptom occurs when a subnet broadcast address is configured as the UDP
helper server address on a VLAN interface.
201409090512
•
Symptom: The switch might unexpectedly reboot during ARP learning.
•
Condition: This symptom might occur if the MPUs are 64-bit systems and the interface cards
are 32-bit CPU systems.
201410200341
•
Symptom: The MAC address entries of the whole switch are deleted.
•
Condition: This symptom can be seen when STP is configured on the switch and the state of
STP edge ports flaps.
201409090447
•
Symptom: A port might go down unexpectedly.
•
Condition: This symptom can be seen when the switch uses QSFP+ transceiver modules from
JDSU.
201409090534
•
Symptom: A system exception occurs when multiple MDCs execute the display
diagnostic-information command.
•
Condition: This symptom can be seen when multiple MDCs execute the display
diagnostic-information command.
201409090470
•
Symptom: The MPU might reboot unexpectedly.
•
Condition: This symptom can be seen when the MPU is started.
201406130122
•
Symptom: CVE-2014-0224.
•
Condition: When Open SSL Server or Client is used.
201407070031
•
Symptom: The ports except for IRF physical ports on a standalone switch or IRF fabric cannot
come up.
•
Condition: This symptom can be seen if the total number of ports on the switch or IRF fabric
exceeds 800.
201406060537
•
Symptom: BGP cannot redistribute OSPF summary routes.
•
Condition: This symptom can be seen if BGP is configured to redistribute OSPF routes.
27
201405120277
•
Symptom: A portal user might fail to come online if the execution of the display portal user all
command is interrupted by pressing ctrl+c.
•
Condition: This symptom might be seen if the execution of the display portal user all
command is interrupted by pressing ctrl+c.
201404240066
•
Symptom: An SSH user fails to log in to the switch.
•
Condition: This symptom can be seen if an ACS server is used for authentication and
login-service is telnet.
201404240054
•
Symptom: Quitting Telnet fails, resulting in high CPU usage.
•
Condition: This symptom can be seen if the following procedure is performed:

Telnet to a switch and then telnet to another switch from the switch.

Display large amounts of information through telnet.

Quit telnet.
201404240076
•
Symptom: CPU usage on the MPU is 100% after a static route is configured.
•
Condition: This symptom can be seen if the configured static route's next hop and destination
address are in the same subnet, and the next hop does not identify any device.
201405120282
•
Symptom: The CPU usage is high when sFlow is enabled.
•
Condition: This symptom can be seen if the following conditions exist:

The interface connected to the sFlow collector is a Layer 3 Ethernet interface or
subinterface that is on a different card from the interface configured with sFlow.

Fast forwarding is used to send sFlow packets.
201404170185
•
Symptom: ip mtu settings get lost after the switch is rebooted.
•
Condition: This symptom can be seen after the switch is rebooted.
201404240079
•
Symptom: A DHCP client takes a long time to get an IP address from the DHCP server on the
switch.
•
Condition: This symptom can be seen if the requested IP address of the DHCP client is not on
the same subnet as the DHCP server's IP address.
201407070026
•
Symptom: The switch fails to display the portal authentication page for a portal user that tries to
access an external URL.
•
Condition: This symptom can be seen if the following conditions exist:

The HTTP get packet from the portal user contains multiple TCP segments.

The external URL is longer than 1024 bytes.
201407070077
•
Symptom: Service interruption randomly occurs on all interfaces.
•
Condition: This symptom can be seen if the switch receives large numbers of HTTP redirect
packets.
28
Resolved problems in 12500-CMW710-F7371
201406130140
•
Symptom: The switch tears down a TCP connection in established state upon receiving a SYN
packet that has a sequence number within the receive window of the connection.
•
Condition: This symptom can be seen when the switch receives a SYN packet that has a
sequence number within the receive window of a TCP connection in established state.
201405040279
•
Symptom: The output from the display link-aggregation load-sharing mode command
shows incorrect information.
•
Condition: This symptom can be seen in the output from the display link-aggregation
load-sharing mode command.
201406040701
•
Symptom: When an exception occurs to SRAM for the FAP chip on a 16-port 10-GbE interface
card, JC782A, JC783A or JC814A, other interface cards are also affected.
•
Condition: This symptom can be seen when an exception occurs to SRAM for the FAP chip on
a 16-port 10-GbE interface card, JC782A, JC783A or JC814A.
201405190377
•
Symptom: The output from the display lldp local-information interface command shows
incorrect information for some parameters.
•
Condition: This symptom can be seen when the display lldp local-information
interface command is executed for a 40G or 100G transceiver module.
Resolved problems in
12500-CMW710-R7328P01
201402110148
•
Symptom: A 16-port 10-GbE module (JC782A, JC783A or JC814A) cannot start up.
•
Condition: This symptom occurs if the 16-port 10-GbE module has the new DRAM chips.
201401080140
•
Symptom: The MRPNE MPU restarts automatically.
•
Condition: The MPU's CPU has bugs. This symptom occurs occasionally when a dead loop
exists on the CPU.
Resolved problems in 12500-CMW710-R7328
201312260027
•
Symptom: The switch might discard packets that match a default route.
•
Condition: This might occur if the following conditions exist:

A public/private IPv4/IPv6 default route is configured.

A card is rebooted, or it is assigned to an MDC or reclaimed.
201312300410
•
Symptom: Interface cards prefixed with LST1XP40RFG or LST1CP4RFG (JG794A, JG788A)
fail to work.
29
•
Condition: This occurs when the system operating mode is enhanced L2.
201312190049
•
Symptom: An NQA icmp-echo operation fails to receive responses.
•
Condition: This might occur when the following conditions exist:

The NQA icmp-echo operation sends lots of packets at a short time.

The NQA icmp-echo operation is configured with the frequence parameter.
Resolved problems in 12500-CMW710-R7326
201311260029
•
Symptom: It takes more than one minute to obtain port information through SNMP.
•
Condition: This can be seen if multiple interface cards are fully configured with transceiver
modules.
201312120299
•
Symptom: An interface card fails to forward IPv6 protocol packets such as OSPFv3 and PIM3
packets.
•
Condition: This occurs if the following conditions exist:

The interface card is prefixed with LST1XLP16RFD, LST1XP48LFD, LST1XP40RFD, or
LST1CP4RFD (JG796A, JG790A, JG792A, JG786A).

The interface card is enabled with IPv6 multicast.

The interface card is configured with lots of ACLs.
201311260217
•
Symptom: The terminal logging level informational, terminal monitor, and terminal
debugging commands and their undo forms do not take effect.
•
Condition: This can be seen if those commands are executed in tclsh.
201310310496
•
Symptom: Traffic interruption occurs for a short time.
•
Condition: This can be seen when the following conditions exist:

OSPF NSR is enabled.

The switch operates in IRF mode and has MAD enabled.

MAD detects conflicts and IRF state changes to Recovery.
201306280219
•
Symptom: The switch fails to start up.
•
Condition: This occurs if one the following conditions exists:

The main and backup startup configuration files are set through BootWare of the
LST1MRPNC (JC072A, JC808A, JC072B or JG497A) MPU.

The standby MPU obtains files from the active MPU.
201308130421
•
Symptom: The transceiver module type on interfaces that belong to a non-default MDC is
incorrect in the output from the display transceiver interface command.
•
Condition: This occurs if the following procedure is performed:
Exchange the transceiver modules of the interfaces when the non-default MDC is stopped.
Start the non-default MDC.
30
201308130450
•
Symptom: HWTACACS authorization has an exception.
•
Condition: This occurs when the 12500 switch acts as the client and a Cisco ACS acts as the
server.
201307080158
•
Symptom: Memory leaks occur.
•
Condition: This occurs when the ntp-service unicast-peer command is configured but the
ntp-service enable command is not configured.
201310240151
•
Symptom: The temperature of a card is very high.
•
Condition: This might occur if the temperature of the card is obtained through the ntp-service
enable command or MIB.
201309260660
•
Symptom: Multicast or broadcast traffic is duplicated or lost on an aggregate or IRF interface.
•
Condition: This occurs if the aggregate or IRF interface includes member ports on both the
EA/EB/EC/EF card and the FD/FG card and it acts as the egress interface.
201309260654
•
Symptom: Layer 2 aggregation load balancing is uneven for PPPoE packets.
•
Condition: This occurs because only the MAC address is involved in hash calculation, resulting
in uneven hash distribution.
201309260653
•
Symptom: A port of an XP40FG/LST3XP8 (JG794A, JC073B, JC068B or JC810A) card
completes an up/down operation slowly.
•
Condition: This can be seen when an up/down operation is performed to a port of an
XP40FG/LST3XP8 (JG794A, JC073B, JC068B or JC810A) card.
201309270089
•
Symptom: The switching fabric modules and line cards might be unexpectedly rebooted.
•
Condition: This might occur when large numbers of attacking ICMP packets exist.
HSV7D007515
•
Symptom: The OSPF process unexpectedly reboots.
•
Condition: This might occur when the following conditions exist:

There are large numbers of OSPF neighbors, ABRs, and ASBRs.

Route flapping occurs continually.
HSV7D007202
•
Symptom: The OSPF process is suspended and the CLI does not respond.
•
Condition: This occurs if OSPF is enabled on multiple interfaces when OSPF is performing
route calculation due to topology changes.
HSV7D006409
•
Symptom: The tftp client source interface command does not apply to TFTP operations.
•
Condition: This can be seen when TFTP operations are performed through MIB.
31
HSV7D006800
•
Symptom: The display interface command shows that traffic within the last 300 seconds is
zero, although the actual traffic is not zero.
•
Condition: This can be seen if the display interface command is executed after the switch has
operated for more than one hour.
HSV7D006392
•
Symptom: The input and output directions are both displayed as input in the output from the
display interface route-aggregation command.
•
Condition: This occurs if the display interface route-aggregation command is executed on a
Layer 3 aggregate interface.
HSV7D006864
•
Symptom: The TACACS client fails to communicate with an ACS server.
•
Condition: This occurs when the switch performs TACACS authentication with an ACS server.
HSV7D006308
•
Symptom: The optical power information of a Finisar 80 KM XFP module cannot be obtained
through CLI or SNMP.
•
Condition: This occurs if the Finisar 80 KM XFP module is not HP-certified and was
manufactured before 2011.
HSV7D006269
•
Symptom: sFlow cannot count traffic on a per-VLAN basis.
•
Condition: This can be seen when sFlow is enabled.
HSV7D006230
•
Symptom: A 48-port GbE interface card might unexpectedly reboot.
•
Condition: This might occur after the interface card has operated for a while.
HSV7D006781
•
Symptom: The displayed running time of a card is longer than its actual running time.
•
Condition: This can be seen if an interface card prefixed with LST1XP48, LST1XP40,
LST1XLP16 or LST1CP4 (JG796A, JG790A, JG794A, JG792A, JG788A, JG786A) and an
LST1SF18E1 or LST1SF08E1 (JG798A, JG800A) switching fabric module are installed.
HSV7D007310
•
Symptom: HP-certified transceiver modules are identified as non-HP-certified transceiver
modules.
•
Condition: This can be seen if HP-certified QSFP+ 10KM transceiver modules are installed.
201312020023
•
Symptom: An exception occurs to MSTP when the number of ports on any line card exceeds
60.
•
Condition: This can be seen when the number of ports on any line card exceeds 60 (including
aggregation group member ports).
32
Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc
Information to collect:
•
Technical support registration number (if applicable).
•
Product name, model or version, and serial number.
•
Operating system name and version.
•
Firmware version.
•
Error messages.
•
Product-specific reports and logs.
•
Add-on products or components.
•
Third-party products or components.
Documents
To find related documents, see the Hewlett Packard Enterprise Support Center website at
http://www.hpe.com/support/hpesc.
•
Enter your product name or number and click Go. If necessary, select your product from the
resulting list.
•
For a complete list of acronyms and their definitions, see HPE FlexNetwork technology
acronyms.
Related documents
The following documents provide related information:
•
HPE 12500 Routing Switch Series Installation Guide
•
HPE 12500 Routing Switch Series Configuration Guides
•
HPE 12500 Routing Switch Series Command References
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help
us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ([email protected]). When submitting your feedback, include the document title,
part number, edition, and publication date located on the front cover of the document. For online help
content, include the product name, product version, help edition, and publication date located on the
legal notices page.
33
Appendix A Feature list
Hardware features
Table 6 12500 series Chassis hardware features
Item
Dimensions (W × H ×D)
(excluding feet and
rack-mounting
brackets)
Weight
Input voltage
Max. power
consumption
12504
12508
12518
442 × 442 × 708 mm
(17.40 × 17.40 ×27.87
in)
442 × 975 × 740 mm
(17.40 × 38.39 ×29.13
in.)
442 × 1686 × 740 mm
(17.40 × 66.38 ×29.13 in.)
12504-AC:
12508-AC:
12518-AC:
Net weight: 56.5 kg
(124.56 lb)
Net weight: 97.5 kg
(214.95 lb)
Net weight: 166.8 kg
(367.72 lb)
Full configuration: ≤
100 kg (220.46 lb)
Full configuration: ≤ 180
kg (396.83 lb)
Full configuration: ≤ 315
kg (694.44 lb)
12504-DC:
12508-DC:
12518-DC:
Net weight: 58.5 kg
(128.97 lb)
Net weight: 99.5 kg
(219.36 lb)
Net weight: 170.8 kg
(376.54 lb)
Full configuration: ≤
100 kg (220.46 lb)
Full configuration: ≤ 180
kg (396.83 lb)
Full configuration: ≤ 315
kg (694.44 lb)
90 VAC to 264 VAC, 47 Hz to 63 Hz
–42 VDC to 72 VDC
2660 W (AC)
5420W (AC)
12240W (AC)
2690 W (DC)
5480W (DC)
12380W (DC)
0°C to 40°C (32°F to 104°F) (long-term operation)
Operating temperature
–10°C to 50°C (14°F to 122°F) (short-term operation: Continuous operation
should be less than 96 hours, and the total duration of such operations in one
year should be less than 15 days.)
Relative humidity
(noncondensing)
5% to 95%
Fan trays
1
2
2
LPU slots
4
8
18
Table 7 12500E series Chassis hardware features
Item
Dimensions (W × H ×D)
(excluding feet and
rack-mounting brackets)
Weight
12508E
12518E
442 × 975 × 740 mm (17.40 × 38.39
×29.13 in.)
442 × 1686 × 740 mm (17.40 ×
66.38 ×29.13 in.)
12508-AC:
12518-AC:
Net weight: 110 kg (242.50 lb)
Net weight: 176.8 kg (389.77 lb)
Full configuration: ≤ 200 kg (440.92
lb)
Full configuration ≤ 335 kg (738.54
lb)
34
12508-DC:
12518-DC:
Net weight: 111.4 kg (245.59 lb)
Net weight: 179.6 kg (395.94 lb)
Full configuration: ≤ 200 kg (440.92
lb)
Full configuration: ≤ 335 kg 738.54
lb)
90 VAC to 264 VAC, 47 Hz to 63 Hz
Input voltage
–42 VDC to 72 VDC
Max. power consumption
9110 W (AC)
17190 W (AC)
9210 W (DC)
17380 W (DC)
0°C to 40°C (32°F to 104°F) (long-term operation)
–10°C to 50°C (14°F to 122°F) (short-term operation: Continuous operation
should be less than 96 hours, and the total duration of such operations in one
year should be less than 15 days.)
Operating temperature
Relative humidity
(noncondensing)
5% to 95%
Fan trays
2
2
LPU slots
8
18
Table 8 12500 series unit/module hardware features
LPU
SFC
FlexFabric
MPU
FlexFabric
LPU
FlexFabric
SFC
4GB
1GB
128MB
8GB
4GB
128MB
Console
1
NA
NA
1
NA
NA
AUX
1
NA
NA
1
NA
NA
USB
1
NA
NA
1
NA
NA
Network
management
interface
1
NA
NA
1
NA
NA
MCC GE
interfaces
2
NA
NA
2
NA
NA
Item
MPU
processor
PowerPC
Boot ROM
4 MB
memory
Fixed
interfaces
NOTE:
In Table 8, MPU refers to LST2MRPNC1 (JC072A, JC808A, JC072B and JG497A), and FlexFabric
MPU refers to LST1MRPNE1 (JG802A) that is newly supported by R7326. R7326 supports both
LST2MRPNC1 and LST1MRPNE1 MPUs, and their MCC GE interfaces (which are not supported
by earlier versions).
Table 9 MPU features
Module
LST1MRPNE1(JG802A)
LST2MRPNC1(JC808A, JC072B
and JG497A)
CPU Frequency
Quad-Core CPU 1.8GHz
Singe Core CPU 1GHz
RAM memory
8GB
4GB
35
CF Card
4GB
1GB
Flash
512MB
128MB
MDC quantity
9
4
Table 10 12500 hardware modules with minimum software release
Item
Switch
chassis
MPU cards
Ethernet
interface
cards
HPE
SKU
Description
Minimum
Software
Release
JG784A
HPE FlexFabric 12518E AC Switch Chassis
R7326
JG782A
HPE FlexFabric 12508E AC Switch Chassis
R7326
JG783A
HPE FlexFabric 12508E DC Switch Chassis
R7326
JG785A
HPE FlexFabric 12518E DC Switch Chassis
R7326
JC654A
HPE 12504 AC Switch Chassis
R1728P02
JC655A
HPE 12504 DC Switch Chassis
R1728P02
JF430C
HP 12518 AC Switch Chassis
R1726
JC653A
HP 12518 DC Switch Chassis
R1726
JF431C
HP 12508 AC Switch Chassis
R1726
JC652A
HP 12508 DC Switch Chassis
R1726
JF431B
HP 12508 Switch Chassis
R1238P02
JF430B
HP 12518 Switch Chassis
R1238P02
JG802A
HPE FlexFabric 12500E Main Processing Unit
R7326
JG497A
HP 12500 MPU w/Comware v7 OS
R7125
JC072B
HP 12500 Main Processing Unit
R1726
JC808A
HP 12500 TAA-compliant Main Processing Unit
R1726
JC072A
HP 12500 Management Module
R1238P02
JG796A
HPE FlexFabric 12500 48-port 1/10GbE SFP+ FD Module
R7326
JG790A
HPE FlexFabric 12500 16-port 40GbE QSFP+ FD Module
R7326
JG794A
HPE FlexFabric 12500 40-port 1/10GbE SFP+ FG Module
R7326
JG792A
HPE FlexFabric 12500 40-port 1/10GbE SFP+ FD Module
R7326
JG788A
HP FlexFabric 12500 4-port 100GbE CFP FG Module
R7326
JG786A
HPE FlexFabric 12500 4-port 100GbE CFP FD Module
R7326
JC073B
HP 12500 8-port 10-GbE XFP LEB Module
R1728
JC068B
HP 12500 8-port 10-GbE XFP LEC Module
R1728
JC810A
HP 12500 8-port 10-GbE XFP LEC TAA-compliant Module
R1728
JC782A
HP 12500 16-port 10-GbE SFP+ LEB Module
R1728
JC783A
HP 12500 16-port 10-GbE SFP+ LEC Module
R1728
JC814A
HP 12500 16p 10-GbE SFP+ LEC TAA Module
R1728
JC075B
HP 12500 48-port GbE SFP LEB Module
R1726
36
Item
Switch
fabric
modules
HPE
SKU
Description
Minimum
Software
Release
JC069B
HPE 12500 48-port GbE SFP LEC Module
R1726
JC660A
HPE 12500 48-port GbE SFP LEF Module
R1726
JC074B
HP 12500 48-port Gig-T LEB Module
R1726
JC065B
HPE 12500 48-port Gig-T LEC Module
R1726
JC780A
HP 12500 8-port 10-GbE SFP+ LEB Module
R1726
JC781A
HP 12500 8-port 10-GbE SFP+ LEC Module
R1726
JC659A
HP 12500 8-port 10-GbE SFP+ LEF Module
R1726
JC064B
HP 12500 32-port 10-GbE SFP+ REB Module
R1726
JC476B
HP 12500 32-port 10-GbE SFP+ REC Module
R1726
JC811A
HPE 12500 48-port GbE SFP LEC TAA-compliant Module
R1726
JC809A
HPE 12500 48-port Gig-T LEC TAA-compliant Module
R1726
JC818A
HPE 12500 48-port GbE SFP LEF TAA-compliant Module
R1726
JC813A
HP 12500 8-port 10-GbE SFP+ LEC TAA-compliant Module
R1726
JC817A
HP 12500 8-port 10-GbE SFP+ LEF TAA-compliant Module
R1726
JC812A
HP 12500 32-port 10-GbE SFP+ REC TAA-compliant Module
R1726
JC075A
HP 48-Port GbE SFP LEB 12500 Module
R1238P02
JC069A
HP 48-Port GbE SFP 12500 Module
R1238P02
JC074A
HP 48-Port Gig-T Module LEB 12500 Mod
R1238P02
JC065A
HP 48-Port Gig-T 12500 Module
R1238P02
JC076A
HP 4-Port 10GBASE-R/W LEB 12500 Module
R1238P02
JC070A
HP 4-Port 10-GbE XFP 12500 Module
R1238P02
JC073A
HP 8-Port 10GBASE-R/W LEB 12500 Module
R1238P02
JC068A
HP 8-Port 10-GbE XFP 12500 Module
R1238P02
JC064A
HP 32-Port 10GE SFP+ 12500 Module (REB)
R1238P02
JC476A
HP 32-port 10GbE SFP+ REC 12500 Module
R1238P02
JG798A
HPE FlexFabric 12508E Fabric Module
R7326
JG800A
HPE FlexFabric 12518E Fabric Module
R7326
JC066A
HP 12518 Fabric Module
R1238P02
JC067B
HP 12508 Fabric Module
R1238P02
JC819A
HP 12518 TAA-compliant Fabric Module
R1726
JC820A
HP 12508 TAA-compliant Fabric Module
R1726
JC657A
HP 12518 G2 Fabric Module
R1728
JC658A
HPE 1250x G2 Fabric Module
R1728
JC816A
HP 12518 TAA-compliant G2 Fabric Module
R1728
JC815A
HPE 1250x TAA-compliant G2 Fabric Module
R1728
37
Item
OAA
modules
Transceiver
modules
and cables
HPE
SKU
Description
Minimum
Software
Release
JC635A
HP A12500 VPN Firewall Module
R7326
JG371A
HP 12500 20Gbps VPN Firewall Module
R7326
JD088A
HP X135 10G XFP LC LR Transceiver
R7326
JG325A
HP X140 40G QSFP+ MPO SR4 Transceiver
R7326
JG915A
HP X130 10G SFP+ LC LH 80km XVCR
R7326
JG661A
HP X140 40G QSFP+ LC LR4 SM XCVR
R7326
JG709A
HP X140 40G QSFP+ CSR4 300m XCVR
R7326
JG829A
HP X150 100G CFP LC LR4 10km SM XCVR
R7326
JF833A
HP X110 100M SFP LC FX Transceiver
R1238P02
JF832A
HP X120 100M/1G SFP LC LX Transceiver
R1238P02
JD103A
HP X120 1G SFP LC LH100 Transceiver
R1238P02
JD061A
HP X125 1G SFP LC LH40 1310nm Transceiver
R1238P02
JD062A
HP X120 1G SFP LC LH40 1550nm Transceiver
R1238P02
JD113A
HP X170 1G SFP LC LH70 1470 Transceiver
R1238P02
JD114A
HP X170 1G SFP LC LH70 1490 Transceiver
R1238P02
JD115A
HP X170 1G SFP LC LH70 1510 Transceiver
R1238P02
JD116A
HP X170 1G SFP LC LH70 1530 Transceiver
R1238P02
JD063B
HP X125 1G SFP LC LH70 Transceiver
R1238P02
JD109A
HP X170 1G SFP LC LH70 1550 Transceiver
R1238P02
JD110A
HP X170 1G SFP LC LH70 1570 Transceiver
R1238P02
JD111A
HP X170 1G SFP LC LH70 1590 Transceiver
R1238P02
JD112A
HP X170 1G SFP LC LH70 1610 Transceiver
R1238P02
JD119B
HP X120 1G SFP LC LX Transceiver
R1238P02
JD098B
HP X120 1G SFP LC BX 10-U Transceiver
R1238P02
JD099B
HP X120 1G SFP LC BX 10-D Transceiver
R1238P02
JD118B
HP X120 1G SFP LC SX Transceiver
R1238P02
JD089B
HP X120 1G SFP RJ45 T Transceiver
R1238P02
JD093B
HP X130 10G SFP+ LC LRM Transceiver
R1335
JD094B
HP X130 10G SFP+ LC LR Transceiver
R1238P02
JD092B
HP X130 10G SFP+ LC SR Transceiver
R1238P02
JD121A
HP X135 10G XFP LC ER Transceiver
R1238P02
JD107A
HP X130 10G XFP SC ZR Transceiver
R1238P02
JD108B
HP X130 10G XFP SC LR Transceiver
R1238P02
JG226A
HP X180 10G XFP LC LH 80km 1538.98nm DWDM
Transceiver
R1335
38
Item
HPE
SKU
Description
Minimum
Software
Release
JG227A
HP X180 10G XFP LC LH 80km 1539.77nm DWDM
Transceiver
R1335
JG228A
HP X180 10G XFP LC LH 80km 1540.56nm DWDM
Transceiver
R1335
JG229A
HP X180 10G XFP LC LH 80km 1542.14nm DWDM
Transceiver
R1335
JG230A
HP X180 10G XFP LC LH 80km 1542.94nm DWDM
Transceiver
R1335
JG231A
HP X180 10G XFP LC LH 80km 1558.98nm DWDM
Transceiver
R1335
JG232A
HP X180 10G XFP LC LH 80km 1559.79nm DWDM
Transceiver
R1335
JG233A
HP X180 10G XFP LC LH 80km 1560.61nm DWDM
Transceiver
R1335
JG234A
HP X130 10G SFP+ LC LH 40km Transceiver
R1335
JD117B
HP X130 10G XFP LC SR Transceiver
R1238P02
JD097B
HP X240 10G SFP+ to SFP+ 3m Direct Attach Copper Cable
R1335
JG081B
HP X240 10G SFP+ to SFP+ 5m Direct Attach Copper Cable
R1335
JC784A
HP X240 10G SFP+ to SFP+ 7m Direct Attach Copper Cable
R1726
Card specifications in different working modes
Table 11 EB/EC/EF card specifications in different working modes
System
Working
Mode
EB
EC
Standard
Stand
ard
Bridge
e
Route
e
Stand
ard
Bridge
e
Route
e
Advan
ce
ARP table
12K
12K
16K
64K
12K
16K
64K
64K
MAC table
64K
128K
128K
64K
256K
256K
128K
128K
IPv4 FIB
256K
256K
256K
256K
256K
256K
256K
1M
IPv6 FIB
64K
64K
128K
128K
64K
128K
128K
512K
MPLS L3VPN
512
512
1K
1K
512
1K
1K
2K
SPB
Not
support
Not
support
2K
4K
Not
Support
2K
4K
8K
2ASIC
4K@48B
16K@40B
64K@40B
4ASIC
8K@48B
32K@40B
128K@40B
8ASIC
16K@48B
64K@40B
NA
ACL
EF
39
Table 12 FD card specifications in different working modes
System Working Mode
Standard
Bridgee
Routee
Advance
Grand
ARP table
12K
32K
64K
64K
350K
MAC table
512K
512K
512K
512K
512K
IPv4 FIB
256K
256K
256K
1M
1M
IPv6 FIB
64K
128K
128K
512K
512K
MPLS L3VPN VRF
512
1K
1K
2K
2K
SPB
Not support
2K
4K
8K
8K
2 ASICs(XP40,
CP4)
IPCL:14K@48B;28K@24B
EPCL:2K@48B;4K@24B
ACL
4 ASICs(XP48,
XLP16)
IPCL:28K@48B;56K@24B
EPCL:4K@48B;8K@24B
Table 13 FG card specifications in different working modes
System Working Mode
Standard
Bridgee
Routee
Advance
Grand
ARP table
12K
32K
64K
64K
512K
MAC table
1M
1M
1M
1M
1M
IPv4 FIB
256K
256K
256K
1M
2M
IPv6 FIB
64K
128K
128K
512K
1M
MPLS L3VPN VRF
512
1K
1K
2K
4K
SPB
Not support
2K
4K
8K
8K
ACL
2 ASICs
256K@40B
128K@40B
Memory requirements of MPUs and interface cards
To run Comware 7, MPUs must be fitted with 4GB SDRAM and also have a CF card of at least 1 GB
in size. 4 GB SDRAM is fitted as standard in the JC072B and the JG497A, but the JC072A must be
upgraded from 1 GB to 4 GB of SDRAM by using two memory upgrade kits (2 x JC609A). If required,
1 GB CF cards (JC684A) are available for purchase. If an upgraded JC072A needs to be returned for
repair, be sure to retain the upgrade parts for use in the replacement unit.
Due to physical memory limits, interface cards with 512 MB memory do not support ISSU, and the
interfaces on each of these cards can be assigned to only one MDC. Except for these ISSU and
MDC limitations, these cards provide full support for all other features. The following table shows
details:
40
Table 14 Support of Ethernet interface cards for ISSU and MDC
HPE
SKU
Description
ISSU
MDC
JC075A
HP 48-Port GbE SFP LEB 12500 Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC069A
HP 48-Port GbE SFP 12500 Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC074A
HP 48-Port Gig-T Module LEB 12500 Mod
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC065A
HP 48-Port Gig-T 12500 Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC076A
HP 4-Port 10GBASE-R/W LEB 12500
Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC070A
HP 4-Port 10-GbE XFP 12500 Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC073A
HP 8-Port 10GBASE-R/W LEB 12500
Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC068A
HP 8-Port 10-GbE XFP 12500 Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC064A
HP 32-Port 10GE SFP+ 12500 Module
(REB)
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC476A
HP 32-port 10GbE SFP+ REC 12500
Module
Not
Supported
Supported with limitation: The
interfaces on one card can be
assigned to only one MDC
JC073B
HP 12500 8-port 10-GbE XFP LEB
Module
Supported
Supported
JC068B
HP 12500 8-port 10-GbE XFP LEC
Module
Supported
Supported
JC810A
HP 12500 8-port 10-GbE XFP LEC
TAA-compliant Module
Supported
Supported
JC782A
HP 12500 16-port 10-GbE SFP+ LEB
Module
Supported
Supported
JC783A
HP 12500 16-port 10-GbE SFP+ LEC
Module
Supported
Supported
JC814A
HP 12500 16p 10-GbE SFP+ LEC TAA
Module
Supported
Supported
JC075B
HP 12500 48-port GbE SFP LEB Module
Supported
Supported
JC069B
HPE 12500 48-port GbE SFP LEC
Module
Supported
Supported
JC660A
HPE 12500 48-port GbE SFP LEF Module
Supported
Supported
41
HPE
SKU
Description
ISSU
MDC
JC074B
HP 12500 48-port Gig-T LEB Module
Supported
Supported
JC065B
HPE 12500 48-port Gig-T LEC Module
Supported
Supported
JC780A
HP 12500 8-port 10-GbE SFP+ LEB
Module
Supported
Supported
JC781A
HP 12500 8-port 10-GbE SFP+ LEC
Module
Supported
Supported
JC659A
HP 12500 8-port 10-GbE SFP+ LEF
Module
Supported
Supported
JC064B
HP 12500 32-port 10-GbE SFP+ REB
Module
Supported
Supported
JC476B
HP 12500 32-port 10-GbE SFP+ REC
Module
Supported
Supported
JC811A
HPE 12500 48-port GbE SFP LEC
TAA-compliant Module
Supported
Supported
JC809A
HPE 12500 48-port Gig-T LEC
TAA-compliant Module
Supported
Supported
JC818A
HPE 12500 48-port GbE SFP LEF
TAA-compliant Module
Supported
Supported
JC813A
HP 12500 8-port 10-GbE SFP+ LEC
TAA-compliant Module
Supported
Supported
JC817A
HP 12500 8-port 10-GbE SFP+ LEF
TAA-compliant Module
Supported
Supported
JC812A
HP 12500 32-port 10-GbE SFP+ REC
TAA-compliant Module
Supported
Supported
Software features
Table 15 12500 software features
Category
Features
Link aggregation, port isolation, port mirroring, mirror sampling
DLDP
Link layer
MVRP
EOAM
Service aggregation group
MAC address management
Limit on the number of learned MAC addresses
Static MAC address configuration
Port-based VLANs
VLAN
Super VLAN
PVLAN
QinQ
Basic QinQ
Selective QinQ
42
Category
Features
IRF2: Up to four chassis
Virtualization
MDC: Up to four MDCs, each having a separate forwarding table (an
LST1MRPNE (JG802A) MPU supports a maximum of nine MDCs)
NOTE:
The enhanced IRF feature (four-chassis IRF) and MDC feature are
mutually exclusive.
STP/MSTP/RSTP
Spanning Tree Protocol
Digest snooping
PVST+
Traffic suppression
Port-based broadcast/unknown multicast/unknown unicast traffic
suppression
Traffic thresholds defined as a rate in pps or bps
Traffic accounting
PCL accounting (EPCL/IPCL)
Priority marking/re-marking
CAR (inbound/outbound)
Traffic shaping (outbound)
Congestion management
Queue management
QoS
Dynamic modular QoS CLI (MQC)
Port-based, VLAN-based, global, and control plane–based QoS
policies
Dynamic modification of QoS policies
WFQ/Bandwidth
Queue-based accounting
Inbound/outbound ACLs
ACL
Basic/advanced/user-defined ACLs
Port-based/VLAN/global ACLs
TCP, UDP, RawIP, Ping, Traceroute
Telnet, FTP, TFTP
ICMPv4
IPv4 protocols
DNS
UDP Helper
DHCP
NTP
ARP, ARP Proxy
IPv4/IPv6 dual stack
TCP6, UDP6, RawIP6, Pingv6, Traceroutev6
IPv6 Telnet, IPv6 FTP, IPv6 TFTP
IPv6 DNS
IPv6 protocols
ICMPv6
VRRPv3
DHCPv6
ND
PMTUD (IPv6)
6PE
43
Category
Features
RIPv1/v2
OSPFv2
IPv4 routing protocols
IS-IS
BGPv4
Static routing/route policy/route recursion/policy based routing for
IPv4
RIPng
OSPFv3
IPv6 routing protocols
IS-IS6
BGP4+
Static routing/route policy/route recursion/policy based routing for
IPv6
Layer-2 multicast
IGMPv1/v2/v3 snooping
MLDv1/v2 snooping
Multicast static routing
IPv4 intra-domain/inter-domain multicast routing
IPv4 multicast group management
Layer-3 multicast
IPv6 intra-domain multicast routing
IPv6 multicast group management
Multicast VPN
Bidirectional PIM
MPLS basic functions
MPLS L3VPN
MPLS
VLL
VPLS
MPLS-TE
6VPE
DCBX
FCoE
Data center
PFC
SPB (802.1aq4.6)
EVI
Data packet attack defense
Protocol packet attack defense
Device security
Attack detection
Protocol packet protection
Incoming/outgoing packet diagnosis
Packet validity check
URPF check
Packet filtering
Network security
ARP attack defense
SIP/SA consistency check
Protocol-classification-based traffic limit
Control plane QoS policy
44
Category
Features
Device management security
Network user binding
User security
AAA
SSH
Portal
MACsec
CLI-based device configuration through the console port
Device management methods
Remote CLI-based device configuration through the AUX port
(Modems are used in between.)
CLI-based device management through Telnet
CLI-based device management through SSH
File upload/download through FTP/TFTP
File management
Creation, copy, deletion, and saving of files and directories and
formatting
Standard mode
Enhanced Layer-2 mode
Supported system operating modes
Enhanced Layer-3 mode
Advanced mode
Grand mode
Ping
Traceroute
Network maintenance
LSP Ping/Tracert
Port loopback detection
NQA
SNMPv3
Network management platform iMC
LLDP/LLDP-MED
Network management
MIB
RMON
NETCONF
Packet capture
Card hot swapping
Switching fabric module redundancy
Active/standby switchover
Inline hot fix
GR
High availability
VRRP, VRRPE
BFD for VRRP/BGP/IS-IS/RIP/OSPF/static routing
IP FRR
ISSU
RRPP
Smart-link/Monitor-link
SDN
OpenFlow V1.3.1
Value-added services
OAA modules in Table 9
45
Appendix B Upgrading software
The software image files used on the 12500 switch series include the Comware images, BootWare
image, MBUS image, power supply monitoring image, and fan monitoring image.
•
Basic Comware images include the system image and the boot image. They include the
operating system kernel and feature modules required for device operation and network
services.
•
BootWare image is used to load the system software image and directs the switch to run the
system software image. Different CPUs use different BootWare images.
•
MBUS image, power supply monitoring image, and fan monitoring image are used by the
MBUS daughter card, power supply monitoring card, and fan monitoring card, respectively.
This section describes how to upgrade Comware software from one Comware V7 release to another.
For information about upgrading other software images, see HPE 12500 Routing Switch Series
Fundamentals Configuration Guide. For information about migrating from Comware V5 to Comware
V7, see the migration guide for 12500 switches.
Comware software file types
Comware V7 system image and boot image are released both in separate .bin files and in an .ipe
package file. The .ipe file includes one .bin system image and one .bin boot image.
These files are named with the following formats:
•
.ipe package—12500-Comware_version-Release.ipe. For example,
12500-CMW710-R7326.ipe.
•
.bin boot image—12500-Comware_version-BOOT-Release.bin. For example,
12500-CMW710-BOOT-R7326.bin.
•
.bin system image—12500-Comware_version-SYSTEM-Release.bin. For example,
12500-CMW710-SYSTEM-R7326.bin.
If you are migrating from Comware V5 to Comware V7, use the separate .bin system and boot image
files. If you are upgrading from one Comware V7 release to another, you can use the .ipe package
file.
The switch supports Comware image redundancy: main and backup. The switch always attempts to
load the main Comware images at startup. If a main Comware image is not available or corrupted,
the switch attempts to load the backup Comware image.
NOTE:
• In this section, the system software image used for upgrade is update.ipe. For software version
information, see Table 1.
• System software image size and system time that appear in the upgrade examples are for
illustration purposes only.
46
Upgrade methods
Use one of the following methods to upgrade Comware software:
Upgrade method
Remarks
Upgrading from the CLI without using ISSU
This method is disruptive. You must reboot the entire
device to complete the upgrade.
Upgrading from the BootWare menu
Use this method when the switch cannot start up.
The ISSU method enables a software upgrade without
service interruption.
Use this method for an IRF fabric or MPU-redundant
switch.
Performing an ISSU
This method is beyond the scope of this document. For
more information, see the fundamentals configuration
guide.
Preparing for the upgrade
Complete the following tasks before performing an upgrade:
•
Schedule the upgrade to a time that minimizes the impact on your live network. Non-ISSU
software upgrade requires a reboot and is disruptive.
•
Set up an upgrade environment. Figure 1 shows the console connection for local upgrade.
•
Verify that the switch and the file server can ping each other.
•
Run a TFTP or FTP server on the file server.
•
Log in to the CLI of the switch.
•
Put the new software images on the file server and specify the working directory.
•
Back up the Comware software images and configuration file to a PC for future rollback.
47
Figure 1 Console connection for local upgrade
Upgrading from the CLI without using ISSU
You can upgrade the Comware software from the CLI through TFTP or FTP.
Using TFTP to upgrade software
This section describes how to upgrade system software by using TFTP.
Backing up the running system software image and configuration file
1.
Use the save command in any view to save the running configuration.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
Chassis 1 Slot 0:
Save next configuration file successfully.
<Sysname>
2.
Use the dir command in user view to identify the Comware images and configuration file names
and verify that the CF card has enough space for the new system software images.
48
<Sysname> dir
Directory of cfa0:
0 drw-
- Sep 15 2012 14:32:26
diagfile
1 drw-
- Sep 15 2012 14:32:26
2 -rw-
37137408 Sep 15 2012 14:26:38
main-boot.bin
logfile
3 -rw-
62894080 Sep 15 2012 14:27:06
main-system.bin
4 -rw-
1694 Sep 15 2012 14:47:12
startup.cfg
1021808 KB total (864868 KB free)
<Sysname>
3.
Use the tftp put command in user view to upload the Comware images to the TFTP server.
<Sysname> tftp 192.168.1.1 put main-boot.bin
% Total
100 35.4M
% Received % Xferd
0
0
Average Speed
Time
Time
Time
Current
Dload
Total
Spent
Left
Speed
100 35.4M
0
Upload
474k
0:00:51
0:00:51 --:--:--
475k
<Sysname> tftp 192.168.1.1 put main-system.bin
% Total
% Received % Xferd
Average Speed
Dload
100 59.9M
0
0
100 59.9M
0
Upload
474k
Time
Total
0:01:26
Time
Time
Current
Spent
Left
Speed
0:01:26 --:--:--
475k
<Sysname>
4.
Use the tftp put command in user view to upload the startup.cfg file to the TFTP server.
<Sysname> tftp 192.168.1.1 put startup.cfg
% Total
% Received % Xferd
Average Speed
Dload
100
1.6k
0
0
100
1.6k
0
Upload
474k
Time
Total
0:00:00
Time
Time
Current
Spent
Left
Speed
0:00:00 --:--:--
475k
<Sysname>
Upgrading the system software
1.
Perform the tftp get command in user view to download the system software image file
update.ipe to the CF card on the switch.
<Sysname> tftp 192.168.1.1 get update.ipe
% Total
100 94.2M
% Received % Xferd
0 94.2M
0
0
Average Speed
Time
Time
Time
Current
Dload
Total
Spent
Left
Speed
678k
Upload
0
0:02:21
0:02:21 --:--:--
682k
<Sysname>
2.
Perform the boot-loader command in user view to load the file update.ipe and specify the file
as the main image file at the next reboot.
<Sysname>boot-loader file cfa0:/update.ipe slot 0 main
Images in IPE:
update-boot.bin
update-system.bin
This command will set the main startup software images. Continue? [Y/N]:y
49
Add images to target slot.
The specified file list will be used as the main startup software images at the
next reboot on slot 0.
3.
Perform the display boot-loader command in user view to verify that the file has been loaded.
<Sysname> display boot-loader
Software images on slot 0:
Current software images:
cfa0:/main-boot.bin
cfa0:/main-system.bin
Main startup software images:
cfa0:/update-boot.bin
cfa0:/update-system.bin
Backup startup software images:
None
4.
Perform the reboot command in user view to reboot the switch.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait..
.......DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
%May 16 07:53:35:583 2016 HPE DEV/5/SYSTEM_REBOOT: -MDC=1; System is rebooting no
w.
DDR2 SDRAM test successful.
5.
After the reboot is complete, perform the display version command to verify that the system
software image is correct.
Using FTP to upgrade software
This section describes how to upgrade system software by using FTP.
Backing up the running Comware software images and configuration
1.
Use the save command in any view to save the running configuration.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
Chassis 1 Slot 0:
Save next configuration file successfully.
<Sysname>
2.
Use the dir command in user view to identify the startup Comware software images and
configuration file and verify that the CF card has enough space for the new software images.
50
<Sysname> dir
Directory of cfa0:
0 drw-
- Sep 15 2012 14:32:26
diagfile
1 drw-
- Sep 15 2012 14:32:26
2 -rw-
37137408 Sep 15 2012 14:26:38
main-boot.bin
logfile
3 -rw-
62894080 Sep 15 2012 14:27:06
main-system.bin
4 -rw-
1694 Sep 15 2012 14:47:12
startup.cfg
1021808 KB total (864868 KB free)
<Sysname>
3.
Use the ftp command in user view to access the FTP server.
<Sysname> ftp 192.168.1.1
Connected to 192.168.1.1 (192.168.1.1).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (192.168.1.1:(none)): 1
331 Give me your password, please
Password:
230 Logged in successfully
Remote system type is MSDOS.
ftp>
4.
Use the put command in FTP client view to upload the current images to the FTP server.
ftp> binary
200 Type is Image (Binary)
ftp> put main-boot.bin
227 Entering Passive Mode (192,168,1,1,8,237)
150 "D:\test\main_boot.bin" file ready to receive in IMAGE / Binary mode
226 Transfer finished successfully.
37137408 bytes sent in 16.706 seconds (2.12 Mbyte/s)
ftp> put main-system.bin
227 Entering Passive Mode (192,168,1,1,8,237)
150 "D:\test\main_system.bin" file ready to receive in IMAGE / Binary mode
226 Transfer finished successfully.
62894080 bytes sent in 28.293 seconds (2.12 Mbyte/s)
5.
Use the put command in FTP client view to upload the startup .cfg file to the FTP server.
ftp> put startup.cfg
227 Entering passive mode (192,168,1,1,8,237)
150 "D:\test\startup.cfg" file ready to receive in ASCII mode
226 Transfer finished successfully.
1694 bytes sent in 0.001 seconds (2.12 Mbyte/s)
ftp>
Upgrading the system software
1.
Use the get command in FTP client view to download the software upgrade file update.ipe to
the CF card on the switch.
ftp> get update.ipe
227 Entering Passive Mode (192,168,1,1,8,238)
150 "D:\test\update.ipe" file ready to send (98780160 bytes) in IMAGE / Binary mode
51
226 Transfer finished successfully.
98780160 bytes received in 44.44 seconds (2.12 Mbyte/s)
ftp>
2.
Use the quit command in FTP client view to return to user view.
ftp>quit
221 Service closing control connection
<Sysname>
3.
Use the boot-loader command in user view to load the upgrade file update.ipe and specify the
file as the main startup image file.
<Sysname>boot-loader file cfa0:/update.ipe slot 0 main
Images in IPE:
update-boot.bin
update-system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to target slot.
The specified file list will be used as the main startup software images at the
next reboot on slot 0.
4.
Use the display boot-loader command in user view to verify that the images in the .ipe file
have been loaded.
<Sysname> display boot-loader
Software images on slot 0:
Current software images:
cfa0:/main-boot.bin
cfa0:/main-system.bin
Main startup software images:
cfa0:/update-boot.bin
cfa0:/update-system.bin
Backup startup software images:
None
5.
Use the reboot command in user view to reboot the switch.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait..
.......DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
%May 16 07:53:35:583 2016 HPE DEV/5/SYSTEM_REBOOT: -MDC=1; System is rebooting no
w.
DDR2 SDRAM test successful.
6.
After the reboot is complete, perform the display version command to verify that the system
software image is correct.
52
Upgrading from the BootWare menu
You can use the following methods to upgrade software from the BootWare menu:
•
Using TFTP/FTP to upgrade software through an Ethernet port
•
Using XMODEM to upgrade software through the console port
TIP:
Upgrading through an Ethernet port is faster than through the console port.
Accessing the BootWare menu
1.
Power on the switch, and information similar to the following will display:
System is starting...
Press Ctrl+D to access BASIC-BOOTWARE MENU
Booting Normal Extended BootWare
The Extended BootWare is self-decompressing...................................
Done!
****************************************************************************
*
*
*
HP 12500 BootWare, Version 2.19
*
*
*
****************************************************************************
Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P.
Compiled Date
: Jan 25 2013
CPU Type
: MPC8548E
CPU L1 Cache
: 32KB
CPU L2 Cache
: 512KB
CPU Clock Speed
: 1000MHz
Memory Type
: DDR2 SDRAM
Memory Size
: 4096MB
Memory Speed
: 400MHz
BootWare Size
: 4MB
Flash Size
: 128MB
cfa0 Size
: 999MB
NVRAM Size
: 1024KB
BASIC CPLD Version
: 005
EXTENDED CPLD Version : 005
PCB Version
: Ver.B
Board self testing...........................
Board steady testing...
[ PASS ]
Board SlotNo...
[
53
1
]
Subcard exist testing...
[ PASS ]
DX246
[ PASS ]
testing...
PHY88E1111
testing...
[ PASS ]
CPLD1 testing...
[ PASS ]
CPLD2 testing...
[ PASS ]
NS16550 register testing...
[ PASS ]
The switch's Mac address...
[3C:E5:A6:71:74:00]
CF Card testing...
[ PASS ]
BootWare Validating...
Press Ctrl+B to access EXTENDED-BOOTWARE MENU...
2.
Press Ctrl + B at the prompt.
Password recovery capability is enabled.
Note: The current operating device is cfa0
Enter < Storage Device Operation > to select device.
==========================<EXTENDED-BOOTWARE MENU>==========================
|<1> Boot System
|
|<2> Enter Serial SubMenu
|
|<3> Enter Ethernet SubMenu
|
|<4> File Control
|
|<5> Restore to Factory Default Configuration
|
|<6> BootWare Operation Menu
|
|<7> Skip Authentication for Console Login
|
|<8> Storage Device Operation
|
|<9> Product Special Operation
|
|<0> Reboot
|
==========================================================================
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Enter your choice(0-9)::
3.
Enter 2 in the BootWare menu to access the serial submenu.
You can upgrade the system software and modify serial port parameters in the serial submenu.
===========================<Enter Serial SubMenu>===========================
|Note:the operating device is cfa0
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Serial Interface Parameter
|
|<0> Exit To Main Menu
|
============================================================================
Enter your choice(0-5):
4.
Enter 3 in the BootWare menu to access the Ethernet submenu.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is cfa0
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
54
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Ethernet Parameter
|
|<0> Exit To Main Menu
|
|<Ensure The Parameter Be Modified Before Downloading!>
|
============================================================================
Enter your choice(0-5):
5.
Enter 4 in the BootWare menu to access the file control submenu, where you can display files,
modify file names, and delete files.
===============================<File CONTROL>===============================
|Note:the operating device is cfa0
|
|<1> Display All File(s)
|
|<2> Set Image File type
|
|<3> Delete File
|
|<0> Exit To Main Menu
|
============================================================================
Enter your choice(0-3):
Table 16 File control submenu options
Item
Description
<1> Display All File(s)
Display all files.
Set the software image attribute.
Software image attributes include main (M) and
backup (B). You can store only one main image and
one backup image on an MPU. Even though not
recommended, you can set a software image as
both the main and backup images (M+B).
<2> Set Image File type
For example, the file main.bin has the M attribute
and the file update.bin has the B attribute. After you
assign the M attribute to update.bin, the type of
update.bin changes to M+B and the type of main.bin
changes to N/A.
<3> Delete File
Delete files.
<0> Exit To Main Menu
Return to the BootWare menu.
Using TFTP/FTP to upgrade software through an Ethernet
port
1.
Enter 3 in the BootWare menu to access the Ethernet submenu, and then enter 6 to access the
Ethernet parameter set menu.
==========================<ETHERNET PARAMETER SET>==========================
|Note:
'.' = Clear field.
|
|
'-' = Go to previous field.
|
|
Ctrl+D = Quit.
|
============================================================================
Protocol (FTP or TFTP) :ftp
55
Load File Name
:main.ipe
:update.ipe
Target File Name
:main.ipe
:update.ipe
Server IP Address
:192.168.1.1
Local IP Address
:192.168.1.125
Subnet Mask
:255.255.255.0
Gateway IP Address
:192.168.1.2
FTP User Name
:user
FTP User Password
:***
Table 17 Parameter description
Field
Description
Load File Name
Name of the source file.
Target File Name
Name of the target file.
2.
Enter 2 to upgrade the main software images.
Loading.....................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
...................................................Done.
98844672 bytes downloaded!
Image file update-boot.bin is self-decompressing...
Saving file cfa0:/update-boot.bin ........Done.
Image file update-system.bin is self-decompressing...
Saving file cfa0:/update-system.bin ................Done.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is cfa0
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Ethernet Parameter
|
|<0> Exit To Main Menu
|
|<Ensure The Parameter Be Modified Before Downloading!>
|
============================================================================
Enter your choice(0-5):
3.
Enter 0 to return to the BootWare menu, and then enter 1 to reboot the system.
56
Using XMODEM to upgrade software through the console
port
XMODEM download through the console port is slower than TFTP or FTP download through an
Ethernet port. To save time, use TFTP or FTP as much as possible.
1.
Enter 2 in the BootWare menu to access the serial submenu.
===========================<Enter Serial SubMenu>===========================
|Note:the operating device is cfa0
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Serial Interface Parameter
|
|<0> Exit To Main Menu
|
============================================================================
Enter your choice(0-5):
2.
Enter 6 in the serial submenu to modify the baudrate.
===============================<BAUDRATE SET>===============================
|Note:'*'indicates the current baudrate
|
|
|
Change The HyperTerminal's Baudrate Accordingly
|---------------------------<Baudrate Available>---------------------------|
|<1> 9600(Default)*
|
|<2> 19200
|
|<3> 38400
|
|<4> 57600
|
|<5> 115200
|
|<0> Exit
|
============================================================================
Enter your choice(0-5):5
If you enter 5 to select 115200 bps, the following information appears:
Baudrate has been changed to 115200 bps.
Please change the terminal's baudrate to 115200 bps, press ENTER when ready.
NOTE:
If you use the default baudrate (9600 bps), go to Step 7.
3.
Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the
switch.
57
Figure 2 Disconnecting the terminal
4.
Select File > Properties, and in the Properties dialog box, click Configure.
Figure 3 Properties dialog box
5.
Select 115200 from the Bits per second list and click OK.
58
Figure 4 Modifying the baud rate
6.
Select Call > Call to reestablish the connection.
Figure 5 Reestablishing the connection
7.
Press Enter. The following information appears:
The current baudrate is 115200 bps
===============================<BAUDRATE SET>===============================
|Note:'*'indicates the current baudrate
|
|
|
Change The HyperTerminal's Baudrate Accordingly
|---------------------------<Baudrate Available>---------------------------|
|<1> 9600(Default)
|
|<2> 19200
|
|<3> 38400
|
|<4> 57600
|
|<5> 115200*
|
|<0> Exit
|
============================================================================
Enter your choice(0-5):
8.
Enter 0 to return to the serial submenu.
===========================<Enter Serial SubMenu>===========================
|Note:the operating device is cfa0
59
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Serial Interface Parameter
|
|<0> Exit To Main Menu
|
============================================================================
Enter your choice(0-5):
9.
Enter 2 in the serial submenu to upgrade the main software images.
Please Start To Transfer File, Press <Ctrl+C> To Exit.
Waiting ...CCCCC
10. Select Transfer > Send File in the HyperTerminal window.
Figure 6 Transfer menu
11. In the dialog box that appears, click Browse to select the source file, and select Xmodem from
the Protocol list.
Figure 7 File transmission dialog box
12. Click Send. The following dialog box appears:
60
Figure 8 File transfer progress
When the download is complete, the following information appears:
Download successfully!
98844672 bytes downloaded!
Input the File Name:update.ipe
Updating File cfa0:/update.ipe..............................................
.....................................................Done!
===========================<Enter Serial SubMenu>===========================
|Note:the operating device is cfa0
|
|<1> Download Image Program To SDRAM And Run
|
|<2> Update Main Image File
|
|<3> Update Backup Image File
|
|<4> Update User Private File
|
|<5> Modify Serial Interface Parameter
|
|<0> Exit To Main Menu
|
============================================================================
Enter your choice(0-5):
13. Enter 0 to return to the BootWare menu, and then enter 1 to reboot the system.
14. If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps. If the baud rate is
9600 bps, skip this step.
Handling software upgrade failures
If a software upgrade fails, the system runs the old software version.
To handle a software upgrade failure:
1.
Check the physical ports for a loose or incorrect connection.
61
2.
If you are using the console port for file transfer, check the HyperTerminal settings (including
the baud rate and data bits) for any incorrect settings.
3.
Check the file transfer settings:

If XMODEM is used, you must set the same baud rate for the terminal as for the console
port.

If TFTP is used, you must enter the same server IP address, file name, and working
directory as set on the TFTP server.

If FTP is used, you must enter the same FTP server IP address, source file name, working
directory, and FTP username and password as set on the FTP server.
4.
Check the FTP or TFTP server for any incorrect settings.
5.
Verify that the storage device has enough space for the upgrade file.
6.
If the "Something is wrong with the file" message appears, verify that the file is usable.
62