API tools faq
paste
Advertisement
timhalo

cisco-catalyst-65xx-notes

timhalo
Nov 27th, 2014
236
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 29.49 KB | None | 0 0
raw download clone embed print report
  1. Catalyst 65xx Notes based on various Cisco docs via http://www.cisco.com.
  2.  
  3. Contents:
  4.  
  5. Types of Chassis, Supervisor Engines and Line Cards
  6. 10-Gigabit-Ethernet standards
  7. Details of an example line card: WS-X6908-10G-2T
  8. Excerpts from Cat6500-E Chassis
  9. Datasheet
  10. Backplane
  11. Supervisor Engines
  12. PFC - Policy Feature Card
  13. Types of Line Cards
  14. DFC - Distributed Forwarding Card
  15. A Packet being switche from ingress to egress through a Cat65xx
  16. Virtual Switching System
  17. EtherChannel
  18. Various Commands for Cat65xx
  19. View VSS Switch info.
  20. Switching Fabric
  21. Redundancy (Stateful SwitchOver and NonStop Forwarding)
  22. Port Speed & Duplex
  23. 802.3x Flow Control, PAUSE Frames
  24. Power Management and Environmental Monitoring
  25. (***'show platform'*** - fabric/harware utilization)
  26. Which link on an EtherChannel would be used
  27. mLACP for Server Access
  28. Hardware Layer3 Switching
  29. Traffic and Storm-Control
  30. General info on Buffers, Queues, & Thresholds
  31.  
  32. +-----------------------------------------------------------------+
  33. | |
  34. +-----------------------------------------------------------------+ Types of Chassis, Supervisor Engines and Line Cards
  35.  
  36. Chassis
  37.  
  38. WS-C6503-E 3-slot 4-RU
  39. WS-c6504-E 4-slot 5-RU
  40. WS-C6506-E 6-slot 12-RU
  41. WS-C6509-E 9-slot 15-RU
  42. WS-C6509-V-E 9-slot vertical
  43. WS-C6513-E 13-slot 20-RU
  44.  
  45. Supervisors
  46. Supervisor 2T - (2) 10GbE ports / MSFC5 with PFC4
  47. Supervisor 2T - (2) 10GbE ports / MSFC5 with PFC4XL
  48. Virtual Switching Supervisor 720 - (2) 10GbE ports / MSFC3 XL
  49. Virtual Switching Supervisor 720 - (2) 10Gbe ports / MSFC3
  50. Sup720 Fabric - (2) GbE ports / MSFC with PFC3BXL
  51. Sup720 Fabric - (2) GBE ports / MSFC3 PFC3B
  52. Sup32 - (2) 10GbE ports with PFC3B
  53. Sup32 - (8) GbE ports with PFC3B
  54.  
  55. Line Cards - 10Gb Ethernet
  56. 8 port w/ DFC4
  57. 8 port w/ DFC4XL
  58. 16 port w/ DFC4
  59. 16 port w/ DFC4XL
  60. 16 port (copper) w/ DFC4
  61. 16 port (copper) w/ DFC4XL
  62. 16 port w/ DFC3C/DFC3CXL
  63. 16 port (copper) w/ DFC3C/DFC3CXL
  64. 8 port w/ DFC3C
  65. 4 port w/o DFC
  66.  
  67. Line Cards - Gb Ethernet
  68. 48 port w/ DFC4 fabric-enabled
  69. 48 port w/ DFC4XL fabric-enabled
  70. 24 port w/ DFC4 fabric-enabled
  71. 24 port w/ DFC4XL fabric-enabled
  72. 24 port fabric-enabled
  73. 48 port fabric-enabled
  74.  
  75. Line Cards - 10/100/1000 Ethernet
  76. 48 port w/ DFC4 fabric-enabled
  77. 48 port w/ DFC4XL fabric-enabled
  78. 48 port fabric-enabled
  79.  
  80. MSFC = Multi-layer Switching Feature Card
  81. PFC = Policy Feature Card
  82. DFC = Distributed Feature Card
  83.  
  84. +-----------------------------------------------------------------+
  85. | |
  86. +-----------------------------------------------------------------+ 10-Gigabit-Ethernet standards
  87.  
  88. 802.3ae-2002 - 10GbE standard (fiber), 2002.
  89. 802.3an-2006 - 10GBaseT standard (10GbE over copper), 2006.
  90. - Shielded Cat6, 6a, Cat7 up to 100 meters (330 feet).
  91. - Cat6 UTP up to 55 meters (181 feet).
  92.  
  93. +-----------------------------------------------------------------+
  94. | |
  95. +-----------------------------------------------------------------+ Details of an example line card: WS-X6908-10G-2T
  96.  
  97. Source: http://www.cisco.com/c/en/us/products/switches/catalyst-6500-series-switches/datasheet-listing.html
  98.  
  99. - Backplane connection at 80Gbps full duplex.
  100. - Forwarding: IPv4 60mpps ; IPv4 30mpps.
  101. - ACL(s): Non-XL: 48k security, 16k QoS ; XL: 192k Security, 64K QoS.
  102. - VLAN(s): 16k supported.
  103. - MAC table: 128k addresses.
  104. - Port buffers: 256 MB per port. 128MB ingress, 128MB egress.
  105. - DFC4XL is an attached daughter card:
  106. - Supports the FIB.
  107. - IPv4 Unicast / MPLS entries: 1024k (DFC4 256k).
  108. - IPv6 Unicast / IPv4 multicast: 512k.
  109.  
  110. +-----------------------------------------------------------------+
  111. | |
  112. +-----------------------------------------------------------------+ Excerpts from Cat6500-E Chassis Datasheet.
  113.  
  114. Source: http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/data_sheet_c78-708665.html
  115.  
  116. - Up to 2 terabits per second system b/w capacity. (? 13 slot X 80gbps per slot for ingress and for egress ?)
  117. - 80Gbps b/w per slot.
  118. - Slot capacities: 3, 4, 6, 9, 9-vertical, 13.
  119. - Standby hot-sync: from 50 to 200ms switch-over
  120. - Redundant power supplies and hot-swappable fan-trays.
  121.  
  122. +-----------------------------------------------------------------+
  123. | |
  124. +-----------------------------------------------------------------+ Excerpts from Cat6500 Architecutre; Backplane
  125.  
  126. Source: http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper0900aecd80673385.html
  127.  
  128. - (2) backplanes
  129. - 32 Gbps shared switching bus; interconnects line-cards.
  130. - Line cards also connect over high speed switching path: crossbar switching fabric.
  131. - First generation switching fabric: switching capacity: 256 Gbps
  132. - Supervisor 720: crossbar switching fabric integrated directly into the Sup board itself.
  133. - Eliminates need for standalone switch fabric module.
  134. - Switching capacity: 720 Gbps.
  135. - Some chassis allow for line-cards to have (2) channels in and out of the switching fabric.
  136. - Crossbar switching fabric. What does it do? Allows each line card to forward and receive data to
  137. every other line card over a unique set of transmission paths.
  138.  
  139. +-----------------------------------------------------------------+
  140. | |
  141. +-----------------------------------------------------------------+ Excerpts from Cat6500 Architecutre; Supervisor Engines
  142.  
  143. - Same link as Backplane section; Brief info on Sup cards:
  144. - Sup32
  145. - Switch Processor (SP): 256MB bootflash. Max 512MB.
  146. - 64MB bootflash for Route Processor (RP).
  147. - DRAM is 256MB for both RP & SP.
  148. - NVRAM = 2MB.
  149. - Sup 720
  150. - Integrates Crossbar fabric, PFC, & MSFC.
  151. - PFC, MSFC No longer optional. (In earlier Sups, they were?).
  152. - Increased bandwidth support on the crossbar switching fabric.
  153. - Backward compatible with earlier line cards. (Preserve line card investments).
  154. - DRAM: 1GB switch processor. 1GB route processor.
  155. - SP bootflash = 512MB default.
  156. - RP bootflash = 64MB.
  157. - NVRAM = 2MB.
  158. - Later vesions of the 720 Sup support additional features for example:
  159. - MPLS support in hardware.
  160. - EoMPLS
  161. - Security ACL hit counters
  162. - Multipath URPF check performed in hardware.
  163. - Etc... See the Architecture White Paper (link above) for more info.
  164. -MSFC handles control plane functions; e.g. Layer 3 routing protocols.
  165. - Is integrated onto the Supervisor card.
  166. - MSFC3 supports forwarding rates of up to 500Kpps. (I assume this is re: control-plane traffic).
  167. - Route Processor and Switch Processor is located on the MSFC3.
  168. - RP manages: L3 routing protocols, ARP, ICMP [reception/response], SVI(s), etc.
  169. - SP manages: L2 such as Spanning Tree, VTP, CDP, pushing FIB tables to the PFC.
  170. - MSFC daughter card doesn't do forwarding. Creates the CEF table from the routing protocols,
  171. then pushes to any PFC or DFC(s) present.
  172.  
  173. +-----------------------------------------------------------------+
  174. | |
  175. +-----------------------------------------------------------------+ Excerpts from Cat6500 Architecutre; PFC - Policy Feature Card
  176.  
  177. Catalyst 6500 Architecture, Policy Feature Card
  178. - Daughter card that sits on the Supervisor Card.
  179. - Contains ASIC(s) to accelerate L2/L3 switching.
  180. - Apparently the PFC is the 'transit packet' forwarding engine/mechanism.
  181. - Is this an alternative to the DFC? Meaning if a DFC is added, then the PFC is disabled???
  182. - PFC3BXL supports up to 1 million routes in it's forwarding tables.
  183. - Also supports such Features (many if not all (?) processed in hardware).
  184. - NAT/PAT, uRPF, GRE, MPLS, BiDir PIM, Egress Policing, etc.
  185.  
  186. +-----------------------------------------------------------------+
  187. | |
  188. +-----------------------------------------------------------------+ Excerpts from Cat6500 Architecutre; Types of Line Cards
  189.  
  190. - Classic. Single connection to the 32Gbps shared bus.
  191. - CEF256. Connection to both the 32Gbps shared bus and the Switching Fabric. Uses the
  192. switching fabric if a Sup 720 is present. Connects at 8Gbps.
  193. - CEF720. Same as CEF256. Connects at 20Gbps.
  194. - dCEF256. Does not connect to shared bus. Requires switch fabric. Connects at 8Gbps.
  195. - dCEF720. Does not connect to shared bus. Requires switch fabric. Connects at 20Gbps.
  196. - Single or Dual Fabric Line Cards. i.e. Cat6513:
  197. - Slots 1 through 8 are single channel. (So these slots can't accept dual channel line cards).
  198. - Slots 9 through 13 are dual channel fabric.
  199.  
  200.  
  201. +-----------------------------------------------------------------+
  202. | |
  203. +-----------------------------------------------------------------+ DFC - Distributed Forwarding Card
  204.  
  205. - Used on selected line cards to support local switching.
  206. - That is switching within the line card itself where the packet doesn't cross the dBUS or switch fabric.
  207. - Uses same ASICs as found on the PFC(s).
  208. - Supports the layer2 and layer3 switching of frames.
  209. - Holds copies of ACL(s) (for QoS and Security) for local processing of ACLs.
  210. - Supported only by certain Supervisors and different generations cannot be mixed.
  211.  
  212. A note on ACL (QoS / Security) processing.
  213. - The Cisco doc, “...6500 Architecture Whitepaper...” says there is no performance hit when ACL(s)
  214. are implemented as the lookups are performed in hardware.
  215. - ACL(s) are pushed into both the PFC & DFC.
  216.  
  217.  
  218.  
  219. +-----------------------------------------------------------------+
  220. | |
  221. +-----------------------------------------------------------------+ A Packet being switche from ingress to egress through a Cat65xx
  222.  
  223. Source: "Cisco Catalyst Architecture White Paper at
  224. http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper0900aecd80673385.html
  225.  
  226. For below steps see Figure 24 at above linke: Direct image link:
  227. http://www.cisco.com/c/dam/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper0900aecd80673385.doc/_jcr_content/renditions/prod_white_paper0900aecd80673385_23.jpg
  228.  
  229. (1) Packet arrives at port and is passed to fabric asic.
  230. (2) Fabric ASIC forwards packet header to the local DFC.
  231. (3) DFC performs Forwarding Lookup along with QoS/Security ACL to see if that processing is necessary.
  232. Results passed back to Fabric ASIC.
  233. (4) Fabric ASIC forwards packet over switch fabric to dst port.
  234. (5) Destination Line Card receives the packet and forwards out the port.
  235.  
  236.  
  237. +-----------------------------------------------------------------+
  238. | |
  239. +-----------------------------------------------------------------+ Virtual Switching System
  240.  
  241. - Enables two physical switch chassis to behave as one single logical entity for packet forwarding
  242. and configuration management.
  243. - Of the (2) chassis one is in Active mode, the other is in Hot Standby mode.
  244. - Only the Active chassis runs the control plane; Layer2 & Layer3 switching and routing protocols.
  245. - Active chassis pushes control plane updates to the Standby unit.
  246. - Virtual Switch Link (VSL) connects to Supervisor on each Switch. Used for control traffic between
  247. Active and Standby. Will send data plane traffic if no direct (local) path.
  248. - Both chassis' forward [transit] packets at the data plane level.
  249. - Spanning-Tree dependency reduced: No physical loops since VSS pairs seen as single logical
  250. switch and Multi-chassis Etherchannel (MEC) can be used.
  251. - Still: must use STP tools (Root Guard, BPDU filter, etc) in case of accidentally created loops.
  252. - First Hop Redundancy Protocols are eliminated.
  253. - Need only a single IP-address to serve as a gateway, rather than 3 used, e.g. HSRP.
  254. - System configuration is from the Active chassis. Interface names take on format: <type>
  255. <Switch/Slot/Port> ; E.g.: show interface te2/5/4 indicates: Switch 2, Slot 5, Port 4.
  256. - There are various Hardware (interface) requirements. See Catalyst Config docs for info.
  257. - Config changes can only occur on Active chassis. Changes are pushed to Standby chassis.
  258.  
  259.  
  260. Traditional
  261. -------------------------------------------
  262.  
  263. [R1] [R2]
  264. | \ / |
  265. | \ / |
  266. | X |
  267. | / \ |
  268. | / \ |
  269. [D1]-----[D2]
  270. | \ / |
  271. | \ / |
  272. | X |
  273. | / \ |
  274. | / \ |
  275. |-->| /<-| \ |<<--similar circumstances for A2's ports.
  276. | [A1] | [A2]
  277. | |
  278. | |-vlan10 port is blocking
  279. | |-vlan20 port is operational
  280. |
  281. |-vlan10 operational
  282. |-vlan20 port is blocking
  283.  
  284.  
  285. VSS Physical View
  286. -------------------------------------------
  287.  
  288.  
  289. [R1] [R2]
  290. | \ /<-|-----\
  291. | \ / |<-----\
  292. | X | \--(2) ports form (1) MultiChassis EtherChannel.
  293. | / \ | -Same for R1's ports to D1 & D2 respectively.
  294. | / \ | -Same for A1's ports to ...
  295. [D1]-----[D2] -Same for A2's ports ...
  296. | \ ^-/--|---\
  297. | \ / | \-- Virtual Switch Link (link for control plane and non-local switch to switch traffic).
  298. | X |
  299. | / \ |
  300. | / \ |
  301. | / \ |
  302. [A1] [A2]
  303.  
  304.  
  305. VSS Logical View
  306. -------------------------------------------
  307.  
  308. [R1] [R2]
  309. \\ //
  310. \\ //
  311. +-----+ R1, R2, A1, A2 each see a single switch.
  312. | VSS |
  313. +-----+
  314. // \\
  315. // \\
  316. [A1] [A2]
  317.  
  318.  
  319.  
  320. VSS, Dual Active Detection
  321. - Dual Active is a situation when the redundant chassis also becomes Active.
  322. - That is, communication on the VSL between the two switches is lost and they both believe
  323. they are to be the Active Chassis. (might be a.k.a 'Split Brain').
  324. - This situation is problematic and detrimental to the network.
  325. - Detection methods:
  326. - Enhanced PAgP: PAgP messaging can (then) occur across a MEC (transiting an neighboring
  327. switch) in order for the two VSS member switches to communicate. Faster than IP-BFD.
  328. - IP Bidirectional Forwarding Detection: Backup link that uses BFD messaging.
  329. - Dual-Active Fast Hello: Uses special hello messages over a backup link. Faster than IP-BFD.
  330.  
  331. +-----------------------------------------------------------------+
  332. | |
  333. +-----------------------------------------------------------------+ EtherChannel
  334.  
  335. - Multiple Ethernet links combined to appear as one link, either at Layer2 or Layer3.
  336. - Protocol:
  337. - PAgP - Port Aggregation Control Protocol; Cisco proprietary
  338. - LACP - Link Aggregation Control Protocol (802.3ad); IEEE standard.
  339. - PAgP and LACP are not compatible; both ends must match.
  340. - PAgP as the EtherChannel control-protocol; mode options:
  341. - On = statically on
  342. - Auto = doesn't initiat PAgP but does respond to PAgP
  343. - Desirable = will initiat PAgP
  344. - Will not work:
  345. - Auto <> Auto
  346. - On <> Auto
  347. - On <> Desirable.
  348. - In fact a combination of Desirable <> On (or NotEtherChannel <> On), can
  349. result i a bridge loop & traffic storm.
  350. - Port states:
  351. - bundled - is part of an EtherChannel; can tx/rx bpdu(s) & data traffic.
  352. - Suspended - not part of an EtherChannel; can rx bpdu(s) but cannot tx; data trafic blocked.
  353. - Standalone - port is not bundled in EtherChannel; can tx/rx bpud(s) & data traffic.
  354. - If one end of an etherchannel has more ports thant the other; then the mismatched ports enter Standalone state.
  355. This can cause problems.
  356. - Config option exists to force StandAlone port in this condition to be disbaled.
  357. - Implication: User complaines of slow performance or sees a link in his/her EtherChannel is down, then check
  358. the remote side for this condition.
  359. - LACP - will form EtherChannel only between ports in passive or active mode.
  360. - Port mode combinations:
  361. Active <> Active > Works
  362. Active <> Passive > Works
  363. Passive <> Passive > Doesn't work
  364. - Up to 8 ports in an LACP Bundle; with up to 8 hot-standby ports.
  365. - If an active port failes then a standby-port is rotated into the group.
  366. - [Some] Basic Requirements
  367. - Same speed, same duplex
  368. - A member link port cannot be a SPAN destination port
  369. - If L2 etherchannel, then ports in access mode must be in the same VLAN
  370. - If L2 trunking: use same trunk mode (on | auto | desirable); allow same vlans on each side.
  371. - Load distribution algorithms: "Fixed Algorithm (default) and Adaptive Algorithm
  372. - Some external devices could require the Fixed Algorithm. See Config Guide for details.
  373. - Change of algorithm means on DFC equipped modules (or on Active Supervisor in dual-sup) that EtherChannel ports will flap.
  374.  
  375. # show interfaces <intf> etherchannel
  376.  
  377. # show etherchannel <port-channel-num> port-channel
  378.  
  379. # show lacp sys-id
  380.  
  381. # show etherchannel load-balance
  382.  
  383. # show etherchannel summary
  384.  
  385. +-----------------------------------------------------------------+
  386. | |
  387. +-----------------------------------------------------------------+ Various Commands for Cat65xx
  388.  
  389. Source: “Catalyst 6500 Release 12.2SX Software Configuration Guide” at
  390. http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12­2SX/configuration/guide/book.html
  391.  
  392. +-----------------------------------------------------------------+
  393.  
  394.  
  395. View VSS Switch info.
  396.  
  397. # show switch virtual [ role | link ]
  398.  
  399. +-----------------------------------------------------------------+
  400.  
  401. MultiChassis EtherChannel
  402. - Configure at normal etherchannel. VSS recognizes it as cross-chassis.
  403.  
  404. +-----------------------------------------------------------------+
  405.  
  406. Switching Fabric
  407.  
  408. # show fabric switching-mode module all
  409. - Modes: Compact, Truncated, Bus; Compact = Best Performance
  410. - Applicable for Sup720 & Sup720-10GE
  411. - See Config Guide for info on modes
  412.  
  413. # show fabric status
  414. - Various entries showing slot, speed, status, etc.
  415.  
  416. # show fabric errors
  417.  
  418. +-----------------------------------------------------------------+
  419.  
  420. Redundancy (Stateful SwitchOver and NonStop Forwarding)
  421.  
  422. # show redundancy states
  423.  
  424. show cef stat
  425. - Look for NSF capable = yes
  426.  
  427. # show ip bgp neighbors <a.b.c.d>
  428. - Look for Graceful Restart = advertised and received
  429.  
  430. # show ip ospf
  431. - Look for Non-stop Forwarding enabled
  432.  
  433. # show isis nsf
  434.  
  435. # show ip protocols
  436. - For EIGRP, look for: EIGRP NSF enabled
  437.  
  438. +-----------------------------------------------------------------+
  439.  
  440. Port Speed & Duplex
  441. - 10GbE & GbE: negotiation process: Link Negotiation
  442. - 10/100/1000mbps: negotiation process: Auto Negotiation
  443. - If one side is Auto the other side must be Auto
  444. - One side cannot negotiate speed/duplex if the other side is hard-coded.
  445. - If manually set speed to 10 or 100Mbps the switch prompts to set duplex.
  446. - Speed cannot be Auto if Duplex is not Auto
  447. - Duplex mode on GbE & 10GbE is Full. This cannot be changed.
  448. - OK, so apparently there is no concept of "What duplex should we use?
  449. during Link Negotiation process.
  450. - Link Negotiation (LN) states and port status :
  451. - Both Local Port & Remote Port are set to LN = OFF, then both ports: UP
  452. - Both Local Port & Remote Port are set to LN = ON, then both ports: UP
  453. - Both Local Port & Remote Port are mismatched. One side is Up, one side is Down.
  454. - Reference Section 1.9 at http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/best/practices/recommendations.html
  455.  
  456.  
  457. # show interfaces <intf>
  458. - See duplex & speed setting
  459.  
  460. # show interfaces <intf> transceiver properties
  461. - Check negotiation status
  462.  
  463. +-----------------------------------------------------------------+
  464.  
  465. 802.3x Flow Control, PAUSE Frames
  466.  
  467. - If receive buffers become full, the port can send PAUSE frames to stop transmission for a specified time.
  468. - 10GbE fiber ports respond to PAUSE frames by default. On [at least] WS-X6502-10GE, this is non-configurable.
  469.  
  470. (config­if)# flowcontrol [ received | send ] [ on | off | desired ]
  471.  
  472. Gigabit Ethernet supports desired option, in that if it's uknown what remote port supports.
  473.  
  474. show interface <intf> flowcontrol
  475.  
  476.  
  477. +-----------------------------------------------------------------+
  478.  
  479. Power Management and Environmental Monitoring
  480.  
  481. - Systems with redundant power/supplies, both must be same wattage
  482. - Some configurations require more wattage than can be supplied by a single power supply.
  483. - Implication: If a power/supply fails, some services through a Cat65xx will be affected.
  484. - Obviously, redundancy is not support in this scenario.
  485.  
  486. # show power
  487. - View details of system power (total, used, available, etc).
  488.  
  489. # show power status power-supply 2
  490.  
  491. # show env status power-supply [ 1 | 2 ]
  492.  
  493. # show platform hardware capacity cpu
  494. - View CPU capacity & utilization for route-processor, switch-processor, and switching module.
  495.  
  496. # show platform hardware capacity eobc EOBC Resources
  497. - Display EOBC related statistics, such as Packets/sec, Total Packets, Dropped Packets; for route-processor,
  498. switch-processor, and DFC(s).
  499.  
  500. # show platform hardware capacity fabric Switch Fabric Resources
  501. - Display Current and Peak Switching utilization.
  502.  
  503. # show platform hardware capacity forwarding
  504. - Utilization of MAC tables, FIB TCAM per-proto (e.g. IP-FIB), Adjacency Tables (ARP/phy-intf).
  505.  
  506. # show platform hardware capacity interface Interface Resources
  507. - shows interface resouce; e.g. Interface Tx/Rx drops; Buffer sizes
  508.  
  509.  
  510.  
  511. +-----------------------------------------------------------------+
  512. | |
  513. +-----------------------------------------------------------------+ Determining which link an EtherChannel will send a frame on.
  514.  
  515. Source: https://supportforums.cisco.com/discussion/11113941/test-etherchannel-commands-7609
  516.  
  517. # show etherchannel load-balance
  518. - First check what the load-balance method is.
  519. - Also if ingress port is PFC controlled just use default command above.
  520.  
  521. # show etherchannel load-balance module <mod_num>
  522. - But if it's DFC controled than add module operator.
  523.  
  524. # remote login switch
  525. - connect to the SP (switch-processor)
  526.  
  527. # attach <slot_num>
  528. - Connect to other linecards (DFC) besides the SP.
  529.  
  530. # test etherchannel load-balance interface port-channel <num> <operator depends on algo>
  531.  
  532.  
  533.  
  534. +-----------------------------------------------------------------+
  535. | |
  536. +-----------------------------------------------------------------+ mLACP for Server Access (mLACP = MultiChassis Link Aggregation Control Protocol)
  537.  
  538. InterChassis
  539. Communication
  540. +----+ Channel (ICC) +----+
  541. Point of | A1 |--------------------| A2 | Point of
  542. Attachment +----+ +----+ Attachment
  543. \ /
  544. \<-----------------/-------\
  545. \ /<--------\
  546. \ / \-Dual Link LACP EtherChannel
  547. Active Link Standby Link
  548. \ /
  549. \<-------/-------\
  550. \ /<--------\
  551. \ / \-Dual Link LACP EtherChannel
  552. +------+
  553. |Server|
  554. | DHD | DHD = Dual Homed Device
  555. +------+
  556.  
  557.  
  558.  
  559. # show redundancy interchassis
  560. - Config Guide lists the operator "interface" ; Command Ref lists the operator "interchassis"
  561.  
  562. # show lacp multi-chassis [ group | port-channel ]
  563.  
  564. # show lacp internal
  565.  
  566. # show lacp neighbor
  567.  
  568.  
  569. +-----------------------------------------------------------------+
  570. | |
  571. +-----------------------------------------------------------------+ Hardware Layer3 Switching
  572.  
  573.  
  574. - Instead of the Route Processor (RP), the PFC(s) & DFC(S) can forward, at wire speed, IP unicast traffic between subnets
  575. - This means this type of packet forwarding occurs in hardware rather than in software via the RP.
  576. - Forwarding decision made locally at ingress. Rewrite info sent to egress port where packet is rewritten:
  577. L2 dst, L2 src, L3 IP TTL, L3 checksum, L2 checksum/FCS.
  578. - H/W L3 Switching is default & cannot be disabled.
  579. - Load-balancing in use is Per-Flow (ip src / ip dst pair).
  580. - "ip load-sharing per-packet" ; "ip cef accounting per-prefix" ; "ip cef accounting non-recursive"
  581. - These commands only apply to traffic that is CEF switched in software by the RP.
  582. - Implication: per-packet load-sharing means forwarding via the slow path.
  583.  
  584. # show interface <intf> | begin L3_in_Switched
  585.  
  586. +-----------------------------------------------------------------+
  587. | |
  588. +-----------------------------------------------------------------+ Traffic and Storm-Control
  589.  
  590. - Occurs when packets flood the LAN and degrade network performance.
  591. - Monitors unicast, multicast, broadcast traffic over a 1-second interval period.
  592. - Compares traffic level with a threshold percentage.
  593. - Traffic level over the threshold is dropped.
  594. - There are options to shutdown the interface (err-disable) or send an snmp trap)
  595. - Shut / no shut to clear err-disable. (Research other methods if such is possible).
  596. - Note that if you enabled both broadcast and multicast storm-control and either one drives the utilization past the threshold, then
  597. both types of traffic will be suppressed.
  598.  
  599. (config-if)# storm-control [ broadcast | multicast | unicast ] level <level>
  600.  
  601. The level percentage is an approximation due to different packet sizes
  602. and counting methods.
  603.  
  604. # show interfaces <intf> counters storm-control
  605.  
  606.  
  607. +-----------------------------------------------------------------+
  608. | |
  609. +-----------------------------------------------------------------+ Some General info on Buffers, Queues, & Thresholds – Cat6500 Ethernet Modules
  610.  
  611. Source: http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper09186a0080131086.html
  612.  
  613. - Some type of receive and transmit buferring will occur.
  614. - Because frames must be stored & enqueued as forwarding decisions are made & output to the line is scheduled.
  615. - Ingress to the switch fabric rarely cause of congestion.
  616. - Egress ports are where majority of packets will be destined,
  617. - therefore transmit-side buffers are larger than received-side.
  618. - No QoS configured: means FIFO with tail-drop is implemented.
  619. - Enabling QoS means port buffers are spread to one or more queues.
  620. - With QoS, Ingress & Egress scheduling is based on CoS values.
  621. - Default: Higher CoS mapped to Higher Queue (does Higher Q mean higher priority?).
  622. - Drop Thresholds (each Queue has two types: Tail drop, WRED drop):
  623. - Tail Drop: Frames of given CoS accepted into queue until Threshold reached. Subsequent frames are dropped until
  624. queue drops below threshold value.
  625. - WRED Drop: Low & High Watermarks. Accepted into queue up to Low watermark. Then random drop with increasing
  626. probability of drop as approaching High Watermark. After high watermark then drop all until below h/w.
  627. - Port Queue and Threshold Acronyms. (Example only. See doc for more listings).
  628. - Rx: 1q2t - 1 standard queue with 2 tail drop thresholds.
  629. - Rx: 1q4t - 1 standard queue with 4 tail drop thresholds.
  630. - Rx: 2q4t - 2 standard queues with four WRED drop thresholds per queue.
  631. - Tx: 2q2t - 2 standard queues with 2 tail drop thresholds per queue.
  632. - Tx: 1p2q2t - 1 strict-priority queue with 2 tail drop thresholds per queue.
  633. - Example Buffer size, Queues, and Thresholds for:
  634. - WS-X6748-GE-TX 48-port (10/100/1000T), Dual-Fabric with RJ45.
  635. - Total Buffer size – 1.3 MB
  636. - Rx Buffer size – 166 KB
  637. - Tx Buffer size – 1.2 MB
  638. - Rx Port type – with DFC3: 2q8t; with CFC: 1q8t
  639. - Tx Port type – 1p3q8t DWRR
  640. - Rx Queue size – with DFC3: Q2 33KB, Q1 133KB; with CFC Q1 166KB
  641. - Tx Queue size – SP 175KB, Q3 175KB, Q2 233 KB, Q1 583 KB
  642.  
  643. +-----------------------------------------------------------------+
  644. | |
  645. +-----------------------------------------------------------------+
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!