For more details, please see ourCookie Policy.


Ethernet Switch

Reply
Highlighted
New Member
Posts: 1
Registered: ‎01-29-2019

How to to packet capture in BCM switch, FYI we are using BCM.0 in our Hardware

How to do packet packet from a particular port in the BCM switches.

I will explain my scenario, we have a Hw that is having BCM as switch fabric, so packets from switch fabric are forwarded to a controller, but there we are observering some discards. We donot know what is the reason for the discards, and what those packets are. If we could able to capture packets in the bcm port, we could able to identify the reason for discarding and the packet.

 

Versions:

BCM.0> version
Broadcom Command Monitor: Copyright (c) 1998-2010 Broadcom Corporation
Release: unknown built no datestamp (no date)
From unknown@unknown:unknown
Platform: x86_64
OS: Unix (Posix)
Chips:

 

BCM56820_A0,

 

 


BCM56640_A0,
BCM56850_A0, BCM56340_A0,

PHYs: BCM5218, BCM5220/21, BCM5226, BCM5228,
BCM5238, BCM5248, BCM5324/FE, BCM5348/FE,
BCM53242/FE, BCM53262/FE, BCM53101/FE, BCM53280/FE,
BCM53600/FE, BCM5400, BCM5401, BCM5402,
BCM5404, BCM5424/34, BCM5411, BCM5461,
BCM5464, BCM5466, BCM5478, BCM5488,
BCM54980, BCM54980, BCM54980, BCM54980,
BCM53314, BCM5482/801x, BCM54684, BCM54640,
BCM54682E, BCM54684E, BCM54685, BCM54616,
BCM84707, BCM84073, BCM84074, BCM84728,
BCM84748, BCM84727, BCM84747, BCM84762,
BCM84764, BCM84042, BCM84044, BCM54280,
BCM54282, BCM54240, BCM54285, BCM5428X,
BCM54290, BCM54292, BCM54294, BCM54295,
BCM5421S, BCM54680, BCM53324, BCM53125,
BCM53128, BCM53010, BCM53018, BCM5302X
BCM54880, BCM54881, BCM54810, BCM54811,
BCM89500, BCM54640E, BCM54880E, BCM54680E,
BCM52681E, BCM8703, BCM8704, BCM8705/24/25,
BCM8706/8726, BCM8727, BCM8728/8747, BCM8072,
BCM8073, BCM8074, BCM8040, BCM8481X,
BCM84812, BCM84821, BCM84822, BCM84823,
BCM84833, BCM84834, BCM84835, BCM84836,
BCM84844, BCM84846, BCM84848, BCM8750,
BCM8752, BCM8754, BCM84740, BCM84164,
BCM84758, BCM84780, BCM84784, BCM84328,
BCM84793, BCM82328, copper sfp

 

 

Phy information is captured below, and we need a packet capture in the interface/port : xe27( 85)

 

BCM.0> phy info
Phy mapping dump:
port id0 id1 addr iaddr name timeout
xe0( 1) 0 0 1 a1 <Unnamed PHY> 0
xe1( 5) 0 0 1 a5 <Unnamed PHY> 0
xe2( 9) 0 0 1 a9 <Unnamed PHY> 0
xe3( 13) 0 0 1 ad <Unnamed PHY> 0
xe4( 17) 0 0 1 b1 <Unnamed PHY> 0
xe5( 21) 0 0 1 b5 <Unnamed PHY> 0
xe6( 25) 0 0 1 c1 <Unnamed PHY> 0
xe7( 29) 0 0 1 c5 <Unnamed PHY> 0
xe8( 33) 0 0 1 c9 <Unnamed PHY> 0
xe9( 37) 0 0 1 8d <Unnamed PHY> 0
xe10( 38) 0 0 1 8e <Unnamed PHY> 0
xe11( 39) 0 0 1 8f <Unnamed PHY> 0
xe12( 40) 0 0 1 90 <Unnamed PHY> 0
xe13( 41) 0 0 1 91 <Unnamed PHY> 0
xe14( 42) 0 0 1 92 <Unnamed PHY> 0
xe15( 43) 0 0 1 93 <Unnamed PHY> 0
xe16( 44) 0 0 1 94 <Unnamed PHY> 0
xe17( 45) 0 0 1 cd <Unnamed PHY> 0
xe18( 49) 0 0 1 e1 <Unnamed PHY> 0
xe19( 53) 0 0 1 85 <Unnamed PHY> 0
xe20( 57) 0 0 1 1ad <Unnamed PHY> 0
xe21( 61) 0 0 1 d1 <Unnamed PHY> 0
xe22( 65) 0 0 1 e5 <Unnamed PHY> 0
xe23( 69) 0 0 1 81 <Unnamed PHY> 0
xe24( 73) 0 0 1 1a9 <Unnamed PHY> 0
xe25( 77) 0 0 1 89 <Unnamed PHY> 0
xe26( 81) 0 0 1 1b1 <Unnamed PHY> 0
xe27( 85) 0 0 1 e9 <Unnamed PHY> 0
xe28( 89) 0 0 1 1a5 <Unnamed PHY> 0
xe29( 90) 0 0 1 1a6 <Unnamed PHY> 0
xe30( 91) 0 0 1 1a7 <Unnamed PHY> 0
xe31( 92) 0 0 1 1a8 <Unnamed PHY> 0
hg0( 93) 0 0 1 1a1 <Unnamed PHY> 0
hg1( 94) 0 0 1 195 <Unnamed PHY> 0
hg2( 95) 0 0 1 191 <Unnamed PHY> 0
hg3( 96) 0 0 1 18d <Unnamed PHY> 0
xe32( 97) 0 0 1 189 <Unnamed PHY> 0
xe33( 98) 0 0 1 18a <Unnamed PHY> 0
xe34( 99) 0 0 1 18b <Unnamed PHY> 0
xe35(100) 0 0 1 18c <Unnamed PHY> 0
hg4(101) 0 0 1 185 <Unnamed PHY> 0
hg5(102) 0 0 1 181 <Unnamed PHY> 0
hg6(103) 0 0 1 f1 <Unnamed PHY> 0
hg7(104) 0 0 1 ed <Unnamed PHY> 0

 

Please help us on this.

Join the Broadcom Support Community

Get quick and easy access to valuable resources across the Broadcom Community Network.