📄 pimsm.tex
字号:
\>Assert winner WC: \>\>...\\ \>Assert lost WC: \>\>...\\ \>Assert tracking WC: \>\>.OO\\ \>Could assert WC: \>\>.O.\\ \>I am DR: \>\>.OO\\ \>Immediate olist RP: \>\>...\\ \>Immediate olist WC: \>\>.O.\\ \>Inherited olist SG: \>\>.O.\\ \>Inherited olist SG\_RPT: \>\>.O.\\ \>PIM include WC: \>\>.O.\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt Group:} The group address. \item {\tt Source:} The source address. \item {\tt RP:} The address of the RP for this entry. \item {\tt Flags:} The set of flags for this entry. For example: \begin{itemize} \item {\tt RP:} (*,*,RP) routing entry. \item {\tt WC:} (*,G) routing entry. \item {\tt SG:} (S,G) routing entry. \item {\tt SG\_RPT:} (S,G,rpt) routing entry. \item {\tt SPT:} The routing entry has the Shortest-Path Tree flag set. \item {\tt DirectlyConnectedS:} The routing entry is for a directly-connected source. \end{itemize}\end{itemize}The remaining lines per entry display various additional information for thatentry. Some of the information below contains a set of network interfaces:there is either ``.'' or ``O'' per interface (starting with the firstinterface according to the {\tt show pim interface} command), and if aninterface is included, it is marked with ``O''.\begin{itemize} \item {\tt Upstream interface (RP):} The name of the upstream interface toward the RP. \item {\tt Upstream MRIB next hop (RP):} The address of the next-hop router (according to the MRIB) toward the RP. In the above example the router itself is the RP, hence there is no next-hop router. \item {\tt Upstream RPF'(*,G):} The address of the next-hop router (according to PIM) toward the RP. Note that this address may be different, because it may be affected by PIM-specific events such as PIM Assert messages on the upstream interface. In the above example the router itself is the RP, hence there is no next-hop router. \item {\tt Upstream state:} The upstream state of this entry. \item {\tt Join timer:} The number of seconds until the upstream Join timer timeout. \item {\tt Local receiver include WC:} The set of interfaces that have local (*,G) receivers according to the MLD/IGMP module. \item {\tt Joins RP:} The set of interfaces that have received (*,*,RP) Join. \item {\tt Joins WC:} The set of interfaces that have received (*,G) Join. \item {\tt Join state:} The set of interfaces that are in Join state. \item {\tt Prune state:} The set of interfaces that are in Prune state. \item {\tt Prune pending state:} The set of interfaces that are in Prune-Pending state. \item {\tt I am assert winner state:} The set of interfaces that are in Assert Winner state. \item {\tt I am assert loser state:} The set of interfaces that are in Assert Loser state. \item {\tt Assert winner WC:} The set of interfaces for which the corresponding (*,G) entry is in Assert Winner state. \item {\tt Assert lost WC:} The set of interfaces for which the corresponding (*,G) entry has lost the PIM Assert. \item {\tt Assert tracking WC:} The set of interfaces for which the corresponding (*,G) entry desires to track the PIM Asserts. \item {\tt Could assert WC:} The set of interfaces for which the corresponding (*,G) entry could trigger a PIM Assert. \item {\tt I am DR:} The set of interfaces for which this is the Designated Router. \item {\tt Immediate olist RP:} The set of interfaces that are included in the immediate outgoing interfaces for the corresponding (*,*,RP) entry. \item {\tt Immediate olist WC:} The set of interfaces that are included in the immediate outgoing interfaces for the corresponding (*,RP) entry. \item {\tt Inherited olist SG:} The set of interfaces that are included in the outgoing interface list for packets forwarded on (S,G) state taking into account (*,*,RP) state, (*,G) state, asserts, etc. \item {\tt Inherited olist SG\_RPT:} The set of interfaces that are included in the outgoing interface list for packets forwarded on (*,*,RP) or (*,G) state taking into account (S,G,rpt) prune state, and asserts, etc. \item {\tt PIM include WC:} The set of interfaces to which traffic might be forwarded because of hosts that are local members on that interface.\end{itemize}The {\stt show pim join all} command can be used to displayinformation about all PIM multicast routing entries including those that maybe created internally by the PIM implementation. Typically, those are the(*,*,RP) entries that are created per RP for implementation-specific reasonseven though there is no requirement to do so. Currently, this command isused only for debugging purpose.\subsection{Monitoring PIM-SM Multicast Routing State Information}The {\stt show pim mfc} command can be used to displayinformation about PIM multicast forwarding entries that are installedin the multicast forwarding engine:\vspace{0.1in}\noindent\framebox[\textwidth][l]{\scriptsize\begin{minipage}{6in}\begin{alltt}\begin{tabbing}xxxx\=xxxxxxxxxxxx\=xxxxxxxxxxxxxxx\=x\=xxxxxxxxxxxxxx\=\killuser@hostname> \textbf{show pim mfc}\\Group \>\>Source \>\>RP\\224.0.1.20 \>\>10.4.0.2 \>\>10.2.0.2\\ \>Incoming interface : \>\>register\_vif\\ \>Outgoing interfaces: \>\>.O.\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt Group:} The group address. \item {\tt Source:} The source address. \item {\tt RP:} The address of the RP for this entry.\end{itemize}The remaining lines per entry display various additional information for thatentry. Some of the information below contains a set of network interfaces:there is either ``.'' or ``O'' per interface (starting with the firstinterface according to the {\tt show pim interface} command), and if aninterface is included, it is marked with ``O''.\begin{itemize} \item {\tt Incoming interface:} The name of the incoming interface. \item {\tt Outgoing interfaces:} The set of outgoing interfaces.\end{itemize}\subsection{Monitoring PIM-SM Multicast Routing Information Base}The {\stt show pim mrib} command can be used to displayinformation about the Multicast Routing Information Base (MRIB) that is usedby PIM:\vspace{0.1in}\noindent\framebox[\textwidth][l]{\scriptsize\begin{minipage}{6in}\begin{alltt}\begin{tabbing}xxxxxxxxxxxxxxxxxxx\=xxxxxxxxxxxxxxx\=xxxxxxxx\=xxxxxxxxx\=xxxxxxx\=xx\=xx\=x\=xxxx\=\killuser@hostname> \textbf{show pim mrib}\\DestPrefix \>NextHopRouter \>VifName \>VifIndex \>MetricPref \>\>\>Metric\\10.2.0.0/24 \>10.2.0.2 \>dc2 \>1 \>\>\>0 \>\>\>0\\10.3.0.0/24 \>10.3.0.1 \>dc1 \>0 \>\>\>0 \>\>\>0\\10.4.0.0/24 \>10.3.0.2 \>dc1 \>0 \>\>254 \>\>\>65535\\10.5.0.0/24 \>10.2.0.4 \>dc2 \>1 \>\>254 \>\>\>65535\\10.6.0.0/24 \>10.2.0.1 \>dc2 \>1 \>\>254 \>\>\>65535\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt DestPrefix:} The destination prefix address. \item {\tt NextHopRouter:} The address of the next-hop router toward the destination. \item {\tt VifName:} The name of the virtual interface toward the destination. \item {\tt VifIndex:} The virtual interface index of the virtual interface toward the destination. \item {\tt MetricPref:} The metric preference of the entry. \item {\tt Metric:} The routing metric of the entry.\end{itemize}\subsection{Monitoring PIM-SM Multicast Routing Information Base}The {\stt show pim neighbors} command can be used to displayinformation about the PIM neighbor routers:\vspace{0.1in}\noindent\framebox[\textwidth][l]{\scriptsize\begin{minipage}{6in}\begin{alltt}\begin{tabbing}xxxxxxxxxxxxx\=xxxxxxxxx\=xx\=xxxxxxxxxxxxxxxx\=xx\=xxxxxxx\=xxxxx\=xxxx\=xxxxx\=\killuser@hostname> \textbf{show pim neighbors}\\Interface \>DRpriority \>\>NeighborAddr \>V \>Mode \>Holdtime \>\>Timeout\\dc1 \>\>1 \>10.3.0.2 \>2 \>Sparse \>\>105 \>\>97\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt Interface:} The name of the interface toward the neighbor: \item {\tt DRpriority:} The DR priority of the neighbor. \item {\tt NeighborAddr:} The primary address of the neighbor. \item {\tt V:} The PIM protocol version used by the neighbor. \item {\tt Mode:} The PIM mode of the neighbor. E.g. {\tt Sparse} means PIM-SM. \item {\tt Holdtime:} The PIM Hello holdtime of the neighbor (in seconds). \item {\tt Timeout:} The number of seconds until the neighbor timeout (in case no more PIM Hello messages are received from it).\end{itemize}\subsection{Monitoring PIM-SM Candidate RP Set Information}The {\stt show pim rps} command can be used to displayinformation about the Candidate RP Set:\vspace{0.1in}\noindent\framebox[\textwidth][l]{\scriptsize\begin{minipage}{6in}\begin{alltt}\begin{tabbing}xxxxxxxxxxxxxxxx\=xxxxxxxxxx\=xxxx\=xxxxx\=xxxx\=xxxx\=xxxx\=xxxxxxxxxxx\=xx\=\killuser@hostname> \textbf{show pim rps}\\RP \>Type \>Pri \>Holdtime \>\>Timeout \>\>ActiveGroups \>\>GroupPrefix\\10.4.0.1 \>bootstrap \>192 \>\>150 \>\>134 \>\>0 \>224.0.0.0/4\\10.2.0.2 \>bootstrap \>192 \>\>150 \>\>134 \>\>1 \>224.0.0.0/4\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt RP:} The address of the Candidate RP. \item {\tt Type:} The type of the mechanism that provided the Candidate RP. \item {\tt Pri:} The priority of the Candidate RP. \item {\tt Holdtime:} The holdtime (in number of seconds) of the Candidate RP. \item {\tt Timeout:} The number of seconds until the Candidate RP timeout. If it is -1, the Candidate RP will never timeout. \item {\tt ActiveGroups:} The number of groups that use this Candidate RP. \item {\tt GroupPrefix:} The multicast group prefix address for this Candidate RP.\end{itemize}\subsection{Monitoring PIM-SM Scope Zone Information}The {\stt show pim scope} command can be used to displayinformation about the PIM scope zones:\vspace{0.1in}\noindent\framebox[\textwidth][l]{\scriptsize\begin{minipage}{6in}\begin{alltt}\begin{tabbing}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\=\killuser@hostname> \textbf{show pim scope}\\GroupPrefix \>Interface\\225.1.2.0/24 \>dc1\end{tabbing}\end{alltt}\end{minipage}}\vspace{0.1in}The fields for each entry (in order of appearance) are:\begin{itemize} \item {\tt GroupPrefix:} The multicast group prefix address of the scoped zone. \item {\tt Interface:} The name of the interface that is the boundary of the scoped zone.\end{itemize}Note that currently (March 2007), configuring multicast scoped zones is notsupported. This feature should be added in the future.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -