This hardware profile is only relevant for systems/LC with the no eTCAM (“base” systems) using Jericho and “Jericho+ with Jericho-scale” (with the 256k-350k large LPM).
#Saf cisco ios version command full
They are mandatory if we need to store large routing tables (ie full internet view) and/or if want to configure URPF.ĭefault mode is “host-optimized” for IPv4 and “internet-optimized” for IPv6. These profiles will dictate how we distribute IPv4 and IPv6 prefixes in the different databases (LPM or LEM) depending on their prefix length. RP/0/RP0/CPU0:NCS5500-663(config)#hw-module fib ipv6 scale internet ? Internet-optimized-disable Configure by default Intetrnet optimized
RP/0/RP0/CPU0:NCS5500-663(config)#hw-module fib ipv4 scale internet-optimized ? Internet-optimized Configure Intetrnet optimized Host-optimized-disable Configure Host optimization by default Scale Configure scale mode for no-TCAM card We will define their role, the type of platforms using them, and potentially the conflicts with other profiles. Now, let’s review these profiles individually. Route-stats Configure multicast per-route statistics Oversubscription Configure oversubscription System uptime is 4 weeks 6 days 12 hours 8 minutes Graphical view of the 6.6.3 structureĬopyright (c) 2013-2019 by Cisco Systems, Inc. If not specifically mentioned, consider that activation of a new hw-module config will require a system or line card reload.įor this article, we use IOS XR 6.6.3, 7.0.2, 7.3.1, 7.4.1. what are the side effects of enabling them, if any.what they do and where they can be used.This document aims at listing all these options and clarify: To enable these particular resource optimizations, we carved the memories in specific ways, via “hardware profiles”. The NCS 5500 resources (databases where we store prefixes, nexthop, counters, …) have been optimized to accommodate the specific requirements of these networking roles. Introductionĭuring the 4 years of its existence, the NCS5500 has been used in a constantly growing number of network roles. This article is meant to be updated regularly, consider it a constant “work in progress”. You can find more content related to NCS5500 including routing memory management, URPF, ACLs, Netflow following this link. Correction of the max-classmap-size descriptionĬorrection: HQoS not needed for ingress policer on sub-ifĪdd: comment on the need to use UDK profile for packet-length match in ACLĪdd: hw-mod profiles till 7.3.1, updated the support for J2 based platforms for exisiting profilesĪdd: hw-mod profiles till 7.4.1, updated the support for J2 based platforms for exisiting profiles
0 kommentar(er)
