Maximum number of routes nearing (IPv6)-cisco-nxos

Maximum number of routes nearing (IPv6)-cisco-nxos

Vendor: cisco

OS: nxos

Description:
Many devices have a limit for the number of IPv6 routes that can be defined. Indeni will alert prior to the number of routes reaching the limit.

Remediation Steps:
Consider removing certain routes.
|
|1. Execute the “show ip route summary” command to display the current contents of the IPv6 routing table in summary format.
|2. Consider to deploy route summarization to decrease the total number of ipv6 prefixes.
|3. Consider to clean up the configuration from unused routes.

How does this work?
This script logs into the Cisco Nexus switch using SSH and retrieves the output of the “show inventory” command. The reported device type is used to identify the max routes value based on a static table. Nexus 3000: 40,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/7x/b_Nexus3k_Verified_Scalability_7x/b_Nexus3k_Verified_Scalability_7x_chapter_01.html) Nexus 5000: 3,600 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html) Nexus 5500: 3,600 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/Verified_Scalability/700N11/b_N5500_Verified_Scalability_700N11/b_N5500_Verified_Scalability_700N11_chapter_01.html Nexus 5600: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html) Nexus 6000: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html) Nexus 7000: 32,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_managinging_rib_fib.html) Nexus 9300: 6,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html) Nexus 9500: 20,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)

Why is this important?
Identify the maximum number of IPv6 unicast routes a certain Cisco Nexus platform can support. This information is used to generate reports if the total number of routes reaches the limit.

Without Indeni how would you find this?
This data is not available through SNMP or syslog. The administrator would have to find this information from the official Data sheet of each Cisco Nexus model.

nexus-show-inventory-max-resources

name: nexus-show-inventory-max-resources
description: Nexus show inventory for max resources (routes, arp)
type: monitoring
monitoring_interval: 60 minutes
requires:
    vendor: cisco
    os.name: nxos
comments:
    routes-limit:
        why: |
            Identify the maximum number of IPv4 unicast routes a certain Cisco Nexus platform can support. This information is used to generate reports if the total number of routes reaches the limit.
        how: |
            This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show inventory" command. The reported device type is used to identify the max routes value based on a static table.
            Nexus 3000: 40,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/7x/b_Nexus3k_Verified_Scalability_7x/b_Nexus3k_Verified_Scalability_7x_chapter_01.html)
            Nexus 5000: 7,200 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html)
            Nexus 5500: 7,200 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/Verified_Scalability/700N11/b_N5500_Verified_Scalability_700N11/b_N5500_Verified_Scalability_700N11_chapter_01.html
            Nexus 5600: 8,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 6000: 8,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 7000: 56,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_managinging_rib_fib.html)
            Nexus 9300: 12,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
            Nexus 9500: 128,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
        without-indeni: |
            This data is not available through SNMP or syslog. The administrator would have to find this information from the official Data sheet of each Cisco Nexus model.
        can-with-snmp: false
        can-with-syslog: false
    routes-limit-ipv6:
        why: |
            Identify the maximum number of IPv6 unicast routes a certain Cisco Nexus platform can support. This information is used to generate reports if the total number of routes reaches the limit.
        how: |
            This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show inventory" command. The reported device type is used to identify the max routes value based on a static table.
            Nexus 3000: 40,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/7x/b_Nexus3k_Verified_Scalability_7x/b_Nexus3k_Verified_Scalability_7x_chapter_01.html)
            Nexus 5000: 3,600 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html)
            Nexus 5500: 3,600 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/Verified_Scalability/700N11/b_N5500_Verified_Scalability_700N11/b_N5500_Verified_Scalability_700N11_chapter_01.html
            Nexus 5600: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 6000: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 7000: 32,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_managinging_rib_fib.html)
            Nexus 9300: 6,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
            Nexus 9500: 20,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
        without-indeni: |
            This data is not available through SNMP or syslog. The administrator would have to find this information from the official Data sheet of each Cisco Nexus model.
        can-with-snmp: false
        can-with-syslog: false
    arp-limit:
        why: |
            Identify the maximum number of IPv4 ARP entries a certain Nexus platform can support. This information is used to generate reports if the total number of entries reaches the limit.
        how: |
            This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show inventory" command. The reported device type is used to identify the ARP cache size value based on a static table.
            Nexus 3000: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/7x/b_Nexus3k_Verified_Scalability_7x/b_Nexus3k_Verified_Scalability_7x_chapter_01.html)
            Nexus 5000: 8,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html)
            Nexus 5500: 8,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/Verified_Scalability/700N11/b_N5500_Verified_Scalability_700N11/b_N5500_Verified_Scalability_700N11_chapter_01.html
            Nexus 5600: 32,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 6000: 32,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 7000: 60,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_managinging_rib_fib.html)
            Nexus 9300: 5,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
            Nexus 9500: 40,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
        without-indeni: |
            This data is not available through SNMP or syslog. The administrator would have to find this information from the official Data sheet of each Cisco Nexus model.
        can-with-snmp: false
        can-with-syslog: false
    neighbor-discovery-limit:
        why: |
            Identify the maximum number of IPv6 neighbor entries a certain Nexus platform can support. This information is used to generate reports if the total number of entries reaches the limit.
        how: |
            This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show inventory" command. The reported device type is used to identify the maximum size of the neighbor discovery cache based on a static table.
            Nexus 3000: 1,500 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/7x/b_Nexus3k_Verified_Scalability_7x/b_Nexus3k_Verified_Scalability_7x_chapter_01.html)
            Nexus 5000: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html)
            Nexus 5500: 4,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/Verified_Scalability/700N11/b_N5500_Verified_Scalability_700N11/b_N5500_Verified_Scalability_700N11_chapter_01.html
            Nexus 5600: 16,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 6000: 16,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/verified_scalability/701N11/b_N5600_Verified_Scalability_701N11/b_N6000_Verified_Scalability_700N11_chapter_01.html)
            Nexus 7000: 30,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_managinging_rib_fib.html)
            Nexus 9300: 5,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
            Nexus 9500: 30,000 (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/scalability/guide_703I11/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_703I11.html)
        without-indeni: |
            This data is not available through SNMP or syslog. The administrator would have to find this information from the official Data sheet of each Cisco Nexus model.
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        command: show inventory | include Chassis
    parse:
        type: AWK
        file: show_inventory_max_resources.parser.1.awk

routes_defined_limit_ipv6

// Deprecation warning : Scala template-based rules are deprecated. Please use YAML format rules instead.

package com.indeni.server.rules.library.templatebased.crossvendor

import com.indeni.server.rules.RuleContext
import com.indeni.server.rules.library.templates.NearingCapacityTemplateRule
import com.indeni.server.rules.RemediationStepCondition

/**
  *
  */
case class routes_defined_limit_ipv6() extends NearingCapacityTemplateRule(
  ruleName = "routes_defined_limit_ipv6",
  ruleFriendlyName = "All Devices: Maximum number of routes nearing (IPv6)",
  ruleDescription = "Many devices have a limit for the number of IPv6 routes that can be defined. Indeni will alert prior to the number of routes reaching the limit.",
  usageMetricName = "routes-usage-ipv6",
  limitMetricName = "routes-limit-ipv6",
  threshold = 80.0,
  alertDescriptionFormat = "There are %.0f IPv6 routes defined where the limit is %.0f.",
  baseRemediationText = "Consider removing certain routes.")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |1. Execute the "show ip route summary" command to display the current contents of the IPv6 routing table in summary format.
      |2. Consider to deploy route summarization to decrease the  total number of ipv6 prefixes.
      |3. Consider to clean up the configuration from unused routes.
    """.stripMargin
)