Diagnosing the switch

CISCO CLI

HP CLI


Switch#show interface port-channel 1
Port-channel1 is up, line protocol is up
(connected)
Hardware is EtherChannel, address is
001d.4608.e217 (bia 001d.4608.e217)
MTU 1500 bytes, BW 2000000 Kbit, DLY 10
usec,

Certain lines have been omitted here but appear on the screen.

 

No HP equivalent

Comments: Take note of the bandwidth on the Cisco side: BW = 2000000 Kbit (2x1 Gbps).

 

CISCO CLI

HP CLI


Switch#show etherchannel 1 detail
Group state = L2
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 8
Protocol: LACP
Minimum Links: 0

Certain lines have been omitted here but appear on the screen.


Ports in the Port-channel:
Index Load Port  EC state No of bits
-----+----+-----+--------+-------
  0    00   Gi0/23Passive  0
  0    00   Gi0/24Passive  0

Certain lines have been omitted here but appear on the screen.

ProCurve(config)#show lacp

	LACP

PORT  LACP    TRUNK  PORT   LACP 
NUMB  ENABLED GROUP  STATUS PARTNER
1     Passive 1      Down   No          
2     Passive 2      Down   No

Certain lines have been omitted here but appear on the screen.

23    Active  Trk1   Up     Yes
24    Active  Trk1   Up     Yes

Comments: LACP is associated with the chosen aggregation mode. Warning: The term Passive shown in the HP CLI refers to the interface and does not concern the LACP configuration mode.

 

CISCO CLI

HP CLI


Switch#debug etherchannel
PAgP/LACP Shim/FEC  debugging is on
00:14:44: FEC: Un-Bndl msg NOT send to PM
for port Gi0/23 from Po1
00:14:44: FEC: delete port (Gi0/23) from
agport (Po1)
00:14:44: FEC: lacp_switch_remove_port_from_
associated_list_internal: Gi0/23 deleted from
the associated list for Po1
00:14:45: %LINEPROTO-5-UPDOWN: Line
protocol on Interface GigabitEthernet0/23,
changed state to down

Certain lines have been omitted here but appear on the screen.


00:59:50: %LINK-3-UPDOWN:Interface
GigabitEthernet0/23, changed state to up

Certain lines have been omitted here but appear on the screen.


00:59:51: FEC: add port (Gi0/23) to agport
(Po1)
00:59:52: FEC: lacp_fec_bundle_internal:
Determine if msg to PM to bundle port
Gi0/23 with Po1 is needed
00:59:52: FEC: pagp_switch_want_to_bundle:
Bndl msg to PM for port Gi0/23 to Agport Po1
00:59:52: %LINEPROTO-5-UPDOWN: Line
protocol on Interface GigabitEthernet0/23,
changed state to up

	
ProCurve(config)#show log
Keys:   W=Warning   I=Information
        M=Major     D=Debug
---  Event Log listing: Events Since
Boot  ---
I 13/10/15 00:00:57 ports: trunk Trk1 is
now active
I 13/10/15 00:00:57 ports: port 23 in 
Trk1 is now on-line
I 13/10/15 00:00:57 ports: port 24 in
Trk1 is now on-line
							

Certain lines have been omitted here but appear on the screen.

I 13/10/15 09:52:58 ports: port 23 in
Trk1 is now off-line
I 13/10/15 09:52:58 ports: port 25 is 
Blocked by LACPI 02/10/13 09:52:58 ports: port 23 in 
Trk5 is now on-line

Comments: Pings are sent to the SN firewall from a workstation connected to the switch.

The cable connected to the first port in the aggregate has been unplugged.

Cisco's debug mode or HP's log mode shows changes that have been made.

When the cable is plugged back in, the aggregate will switch back to its usual status.

Don't forget to exit debug mode on the Cisco switch.

While no pings are ever lost when they pass through the HP switch, they will be on the Cisco switch every time its status changes (when one of the cables is unplugged or plugged back in).