Thanks for the link, Pete. That's very helpful! John
On Tue, Jul 29, 2014 at 8:49 AM, Pete Lumbis <alum...@gmail.com> wrote: > MFIB was added in 12.4.24T (or maybe 15.0M) and...I want to say SRD code. > You can think of it like multicast CEF. Just like the RIB builds FIB, > mroute builds mfib. It's also the code where you see the pim tunnel > interfaces for encap (on the FHR) and decap (on the RP). > > This might be helpful. > > http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipmulti_mfib/configuration/xe-3s/Multicast_Forwarding_Information_Base_Overview.html > > > On Tue, Jul 29, 2014 at 10:22 AM, John Neiberger <jneiber...@gmail.com> > wrote: > >> This looks like a command that is new in 12.2(33)SRD or SRE. At my old >> job, >> all of our 7600s were running 12.2(33)SRC2. My new job has quite a variety >> of code running. The box I'm on right now is running SRE code and does >> have >> these commands available. I'm just not sure what they're trying to tell >> me. >> They're quite different from the mfib commands availalbe on XR, for >> example. It seems to be providing additional information related to the >> state of distributed multicast forwarding, but I have no idea about the >> specifics. For example, what is a broker in this context? >> >> router#show mfib linecard >> >> IPv4 MFIB >> Slot Linecard status Broker status >> 3/0 inactive inactive >> 2/0 inactive inactive >> 1/0 sync enabled >> >> IPv6 MFIB >> Slot Linecard status Broker status >> >> IPv4:Default, 29 entries, 33 ioitems >> Slot Table state >> 1/0 Sync >> >> >> router#show mfib linecard summary >> >> IPv4 MFIB >> Slot Linecard status Broker status >> 3/0 inactive inactive >> 2/0 inactive inactive >> 1/0 sync enabled >> >> router#show mfib ? >> background MFIB background processing >> broker MFIB information related to update brokers >> error MFIB error state >> linecard MFIB information related to linecards >> nsf MFIB SSO NSF statistics >> state MFIB state >> table MFIB master table record >> timers MFIB timers >> >> <cr> >> >> router#show mfib state >> MFIB Status: >> RP instance >> IPv4 MFIB Status: >> Enable state: distributed enabled >> Running state: running distributed >> IPv6 MFIB Status: >> Enable state: disabled >> Running state: not running >> RRP HA state: >> Is standby RRP: no >> RF Peer Presence: no >> RF PeerComm reached: no >> Redundancy mode: sso(3) >> IPv4 MFIB NSF sync: disabled/not running >> IPv6 MFIB NSF sync: disabled/not running >> >> MFIB ISSU Status: >> MFIB IPv4 pull >> No slots are ISSU capable. >> >> >> router#show mfib table >> 1 active IPv4 table >> Table Entries State Flags >> v4:Default 29 Sync DEF,LCS,CEN,CON,EOF,PRG >> >> >> >> >> On Mon, Jul 28, 2014 at 7:50 PM, Tony <td_mi...@yahoo.com> wrote: >> >> > Hi John, >> > >> > Yes, mfib = multicast FIB. >> > >> > Are the boxes in question running multicast ? (hint: "show run | i >> > multicast") >> > >> > What were the previous tickets about (or opened for) ? >> > >> > I'm not sure why they would be used for anything other than >> > troubleshooting multicast traffic, it could be specific to a linecard if >> > that was the problem encountered. >> > >> > >> > regards, >> > Tony. >> > >> > >> > ------------------------------ >> > *From:* John Neiberger <jneiber...@gmail.com> >> > *To:* "cisco-nsp@puck.nether.net" <cisco-nsp@puck.nether.net> >> > *Sent:* Tuesday, 29 July 2014 2:47 AM >> > *Subject:* [c-nsp] Cisco 7600 and 'show mfib' commands >> >> > >> > I'm at a new job and was looking at a few recent trouble tickets. I see >> > that TAC had them use variations of the 'show mfib' commands, like 'show >> > mfib linecard summary'. At my previous job, we had a few hundred 7600s >> but >> > I don't recall TAC ever directing us to use those commands. I took a >> peek >> > at them and it's not clear what I'm looking at. >> > >> > When I see mfib, I assume multicast FIB. I can't really tell if that's >> what >> > I'm looking at or not, or the significance of the commands. >> > >> > I wasn't able to find much good info about these commands on CCO. Do >> any of >> > you have any idea what these are really looking at? It seems that they >> > might be useful for troubleshooting linecard issues but I'm entirely >> > unfamiliar with them. >> > _______________________________________________ >> > cisco-nsp mailing list cisco-nsp@puck.nether.net >> > https://puck.nether.net/mailman/listinfo/cisco-nsp >> > archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > >> > >> > >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/