![]() But the flexibility to carve resources for these databases are only supported with the NCS5700 systems or line-cards using Jericho2 family of ASICS (Jericho2, Jericho2C, Qumran2C and Qumran2A) NCS5500/5700 Products The on-chip databases mentioned in the table #1 are common across all these different ASICS. Our latest platform in works will come with new Jericho2C+ ASIC from Broadcom. ![]() We use different ASICS from the same ASIC family on our NCS5500 and NCS5700 routers which are Qumran-MX, Jericho, Jericho+ and the latest Jericho2, Jericho2C, Qumran2C and Qumran2A ASICS. This shows the applications/features mapped to the important databases in the ASIC. Jericho On-Chip DatabasesĪ quick refresher of Jericho ASIC’s on-chip resources seen in the below table. Our focus of discussion will be on the memory databases available on the Jericho2 family of ASICS. They are out of the scope for the MDB discussion. ![]() We also have the on-chip buffers and off-chip HBM buffers used for queuing the packets. On the scale variant we have an external-TCAM (OptimusPrime2 in NCS5700 family) to offload storage of prefixes, ACL rules, QOS, etc for a higher scale compared to the base systems. In the NCS5500/NCS5700 routers we have various on-chip databases for different purposes like storing the IP prefix table, MAC information, Labels, Access-list rules and many more. We bring in that flexibility in the form of MDB (Modular Database) profiles in our NCS5700 Fixed systems and NC57 Linecards on the modular NCS5500 router operating in Native mode. So how to deploy the same product addressing these different scale requirements? And it comes with it’s own interesting set of features and importantly different scale requirements. In Today’s Network deployments we position our routers in various roles pertaining to different use cases. Understanding MDB (Modular Databases) on NCS5700 systems
0 Comments
Leave a Reply. |