Hi, I have a cisco Nexus7700 C7706 (6 Slot) Chassis ("Supervisor Module-2") with   System version: 6.2(16) and we are getting theese messages.   What is the meaning of the log? do I have a memory problem or something?   2017 Oct 12 09:08:49 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 10:05:08 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 10:45:21 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 10:52:38 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 11:02:25 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 11:06:43 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 11:13:21 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 11:23:06 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr 2017 Oct 12 11:59:56 HNTGDC_02VDIS_CS7706H urib: Urib smalloc Failed to allocate rte_tlv_ptr ... View more

Hi,       We were making some changes on the routing of a ISR4451 (adding neighbors to an OSPF process) and then, the router log the next message May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. May 7 01:41:39 GMT: This is a loadbalancing scenario, could not find correct if_number. After that, a lot of OSPF neighbors were DOWN and UP again several times. What is the meaning of this message????? and why caused a OSPF convergence??? ... View more

Hi!. Anybody knows something about this messages? We have ISR-4451 with ISR WAAS installed. These error messages are showed alot in the CLI 070502: Dec 8 10:35:08: %MDNSPROXY-3-API_FAIL_MDNS: Resolve Service API failed 070503: Dec 8 10:35:09: %MDNSPROXY-3-API_FAIL_MDNS: Resolve Service API failed 070504: Dec 8 10:35:10: %MDNSPROXY-3-API_FAIL_MDNS: Resolve Service API failed 070505: Dec 8 10:35:11: %MDNSPROXY-3-API_FAIL_MDNS: Resolve Service API failed 070506: Dec 8 10:35:13: %APPNAV_CONTROLLER-4-SNG_UNAVAILABLE: APPNAV-CONTROLLER: Alarm #30001, Severity: Major 070510: Dec 8 10:36:28: %APPNAV_CONTROLLER-4-SNG_UNAVAILABLE: APPNAV-CONTROLLER: Alarm #30001, Severity: Major 070511: Dec 8 10:37:44: %APPNAV_CONTROLLER-4-SNG_UNAVAILABLE: APPNAV-CONTROLLER: Alarm #30001, Severity: Major 070512: Dec 8 10:38:53: %APPNAV_CONTROLLER-4-SNG_UNAVAILABLE: APPNAV-CONTROLLER: Alarm #30001, Severity: Major Here is a show version. ------------------ show version ------------------ Cisco IOS XE Software, Version 03.16.03.S - Extended Support Release Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2016 by Cisco Systems, Inc. Compiled Thu 09-Jun-16 22:15 by mcpre Cisco IOS-XE software, Copyright (c) 2005-2016 by cisco Systems, Inc. All rights reserved. Certain components of Cisco IOS-XE software are licensed under the GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such GPL code under the terms of GPL Version 2.0. For more details, see the documentation or "License Notice" file accompanying the IOS-XE software, or the applicable URL provided on the flyer accompanying the IOS-XE software. ROM: IOS-XE ROMMON RO_HNTGDC_01_TGU-WR4451H uptime is 15 weeks, 5 days, 12 hours, 23 minutes Uptime for this control processor is 15 weeks, 5 days, 12 hours, 24 minutes System returned to ROM by reload at 22:13:53 CST Fri Aug 19 2016 System restarted at 22:16:15 CST Fri Aug 19 2016 System image file is "bootflash:/isr4400-universalk9.03.16.03.S.155-3.S3-ext.SPA.bin" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export@cisco.com. Suite License Information for Module:'esg' -------------------------------------------------------------------------------- Suite Suite Current Type Suite Next reboot -------------------------------------------------------------------------------- FoundationSuiteK9 None None None securityk9 appxk9 AdvUCSuiteK9 None None None uck9 cme-srst cube Technology Package License Information: ----------------------------------------------------------------- Technology Technology-package Technology-package Current Type Next reboot ------------------------------------------------------------------ appxk9 appxk9 Permanent appxk9 uck9 None None None securityk9 securityk9 Permanent securityk9 ipbase ipbasek9 Permanent ipbasek9 cisco ISR4451-X/K9 (2RU) processor with 7793143K/6147K bytes of memory. Processor board ID FTX1927AHBE 8 Gigabit Ethernet interfaces 32768K bytes of non-volatile configuration memory. 16777216K bytes of physical memory. 30658359K bytes of flash memory at bootflash:. 20971520K bytes of SATA hard disk at harddisk:. Configuration register is 0x2102 ... View more

Hi!, We have a rare behavior on a couple of Nexus 7010. We have connected a new server with two interfaces configured as active/standby to a couple of nexus FEX interfaces. Something like this. ----------- Server||-----> NIC1 (active) ---> Interface 101/1/6 on Fex 101 --> Nexus #1 7010 L2 Context Server||-----> NIC2 (standby) ---> Interface 104/1/6 on Fex 104 --> Nexus #2 7010 L2 Context ______ The configuration on these interfaces are just "switchport access vlan 56" but the server had connectivity issues (some people can reach the ip and some other not). Looking for a problem with the server we just find out this. If you look for the MAC address on the Nexus #1, the MAC address is being learned on Eth101/1/6 3T-NX7-S1-L2# 3T-NX7-S1-L2# sh mac address-table | grep 0894.ef10.1344 * 56 0894.ef10.1344 dynamic 0 F F Eth101/1/6 BUT if you look for the same MAC address on the Nexus #2, the Mac address is also learned on the interface Ethernet 101/1/6 but this interfaces does not exist on this Nexus!! 3T-NX7-S2-L2# 3T-NX7-S2-L2# sh mac address-table | grep 0894.ef10.1344 * 56 0894.ef10.1344 dynamic 0 F F Eth101/1/6 3T-NX7-S2-L2# sh mac address-table | include 101/1/6 * 56 0894.ef10.1344 dynamic 30 F F Eth101/1/6 3T-NX7-S2-L2# sh int ethernet 101/1/6 ^ % Incomplete command at '^' marker. 3T-NX7-S2-L2# sh fex FEX FEX FEX FEX Number Description State Model Serial ------------------------------------------------------------------------ 103 FEX-2248TP-1GE Online N2K-C2248TP-1GE FOX1724G9BN 104 FEX-2248TP-1GE Online N2K-C2248TP-1GE FOX1724G99C 3T-NX7-S2-L2# The connection between the two Nexus 7010 is with Fabric Path, the Vlan 56 is also a Fabric Path Vlan. I have no explanation for this behavior.  Any idea will be appreciated. ... View more