No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


MIB Reference

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Relationships Between Tables

Relationships Between Tables

Figure 148-1  Relationship between msdpPeerTable, msdpSACacheTable, and msdpMeshGroupTable

Figure 148-1 shows the relationship between msdpPeerTable, msdpSACacheTable, and msdpMeshGroupTable. SA entries in msdpSACacheTable are generated on the local router when SA messages are received from peers. Therefore, you can find the corresponding peer record in msdpPeerTable based on the msdpSACachePeerLearnedFrom and msdpSACacheRPFPeer objects in msdpSACacheTable. Similarly, mesh groups should be configured after peer relationship is set up. Therefore, msdpMeshGroupPeerAddress in msdpMeshGroupTable has a corresponding msdpPeerRemoteAddress in msdpPeerTable.

Updated: 2019-07-19

Document ID: EDOC1000174090

Views: 501115

Downloads: 49

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next