Meraki Switch Unknown in Network Visualization | Nutanix Community
Skip to main content
Solved

Meraki Switch Unknown in Network Visualization


Forum|alt.badge.img+1

Hello,

 

I have instantiated a new cluster and I can’t seem to figure out why the Network Visualization won’t work for my cluster.  LLDP is enabled on my Meraki switch. I can see when new devices join my network as Nutanix on both my eero and firewalla.

 

When I do lldpctl from the host it shows the following:

-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface:    eth0, via: LLDP, RID: 1, Time: 1 day, 01:01:39
  Chassis:     
    ChassisID:    mac ac:17:c8:2f:de:80
    SysName:      Home - switch
    SysDescr:     Meraki MS225-24P Cloud Managed PoE Switch
    MgmtIP:       x.x.x.x
    Capability:   Bridge, on
  Port:        
    PortID:       ifalias 9
    PortDescr:    Port 9
    TTL:          120
  VLAN:         1, pvid: yes
  Unknown TLVs:
    TLV:          OUI: 00,18,0A, SubType: 1, Len: 4 00,2C,32,89
-------------------------------------------------------------------------------
Interface:    eth1, via: LLDP, RID: 1, Time: 1 day, 01:01:38
  Chassis:     
    ChassisID:    mac ac:17:c8:2f:de:80
    SysName:      Home - switch
    SysDescr:     Meraki MS225-24P Cloud Managed PoE Switch
    MgmtIP:       x.x.x.x
    Capability:   Bridge, on
  Port:        
    PortID:       ifalias 15
    PortDescr:    Port 15
    TTL:          120
  VLAN:         1, pvid: yes
  Unknown TLVs:
    TLV:          OUI: 00,18,0A, SubType: 1, Len: 4 00,2C,32,89
-------------------------------------------------------------------------------
 

 

When I search the health_server.log I see the following errors:

2024-08-08 13:00:36,222Z INFO scheduler.py:472 Sch:SCH_0 Pool Exec Count 316 Executing Plugin (task, id: 21, name: switch_interface_stats_collector, scope: Local)
2024-08-08 13:00:36,223Z INFO scheduler.py:128 [switch_interface_stats_collector] PID 30898 Exec Count 316 Started the execution of pool task (task, id: 21, name: switch_interface_stats_col
lector, scope: Local).
2024-08-08 13:00:36,224Z INFO ncc_task.py:430 [switch_interface_stats_collector] Timeout for switch_interface_stats_collector is 1230 seconds
2024-08-08 13:00:36,227Z INFO base_plugin.py:1835 [switch_interface_stats_collector] Check name = collect_interface_stats
2024-08-08 13:00:36,228Z INFO network_config_manager.py:47 [switch_interface_stats_collector] NWVIZ: Reading the network configuration from Zookeeper.
2024-08-08 13:00:36,229Z INFO scheduler_job_queue_manager.py:362 Adding task: (task, id: 65, name: ahv_remote_log_forwarding_check, scope: Local) Init Delay: 5
2024-08-08 13:00:36,230Z ERROR network_config_manager.py:202 [switch_interface_stats_collector] NWVIZ: Could not parse switch configuration - Error parsing message.
2024-08-08 13:00:36,230Z ERROR network_config_manager.py:77 [switch_interface_stats_collector] NWVIZ: Empty/Invalid network configuration received. Ignored the configuration.
2024-08-08 13:00:36,238Z INFO kvm_utils.py:137 [switch_interface_stats_collector] Executing command lldpcli show chassis
2024-08-08 13:00:36,428Z INFO kvm_utils.py:137 [switch_interface_stats_collector] Executing command lldpcli show chassis
2024-08-08 13:00:36,515Z INFO switch_interface_collector.py:257 [switch_interface_stats_collector] NWVIZ: Discover the switch and interfaces to collect the statistics.
2024-08-08 13:00:36,516Z INFO switch_interface_collector.py:535 [switch_interface_stats_collector] NWVIZ: No information collected through LLDP/CDP - nwviz_ignore_auto_discovery == True
2024-08-08 13:00:36,519Z ERROR switch_interface_collector.py:1358 [switch_interface_stats_collector] NWVIZ: No valid switch config to update switch vendor type.
2024-08-08 13:00:36,519Z INFO switch_interface_collector.py:712 [switch_interface_stats_collector] NWVIZ: Validating the switch table entries and discovering the interfaces.
2024-08-08 13:00:36,520Z INFO switch_interface_collector.py:278 [switch_interface_stats_collector] NWVIZ: Time taken to re-validate the switch table is 0.000471.
2024-08-08 13:00:36,520Z INFO switch_interface_collector.py:1441 [switch_interface_stats_collector] NWVIZ: No valid switch interfaces to collect the statistics
2024-08-08 13:00:36,638Z INFO insights_publish.py:166 [switch_interface_stats_collector] NWVIZ: Successfully published switch interface statistics to Insights.
2024-08-08 13:00:36,823Z INFO switch_interface_collector.py:322 [switch_interface_stats_collector] NWVIZ: Time taken to collect and publish the switch interface statistics to Arithmos is 0.302467

Is there a requirement for me to use SMTP or shouldn’t LLDP/CDP be enough.

 

 

Best answer by JeroenTielen

To have this (the info at the right) I always need to enable SNMP on the switch and configure this in SNMP under settings in prism element. 

 

 

LLDP will only give me this information: 

 

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

6 replies

JeroenTielen
Forum|alt.badge.img+8
  • Vanguard
  • 1363 replies
  • Answer
  • August 8, 2024

To have this (the info at the right) I always need to enable SNMP on the switch and configure this in SNMP under settings in prism element. 

 

 

LLDP will only give me this information: 

 

 


Forum|alt.badge.img+1
  • Author
  • Adventurer
  • 9 replies
  • August 8, 2024

@JeroenTielen 

Thanks for the info. So I added the Switch information where I think it needed to be added.

I can see the switch now on the switch configuration

 

 

Still showing up as unknown / data unavailable on the visualization page.

I know that the SNMP is working on the switch correctly because I can walk the switch with the credentials I set up from a different device no problem.

I dig through the logs some more.

 


ktelep
Nutanix Employee
Forum|alt.badge.img+5
  • Nutanix Employee
  • 540 replies
  • August 9, 2024

I”m not sure if you’ve seen this document yet:  https://portal.nutanix.com/page/documents/kbs/details?targetId=kA032000000TVfiCAG

However you’ll note in the lldpctl data the interfaces are labeled as ‘ifAlias’ and not ‘ifname’, this may be the reason the port information is not populating.


JeroenTielen
Forum|alt.badge.img+8
  • Vanguard
  • 1363 replies
  • August 9, 2024

If you added the SNMP configuration correctly (and the cluster has access to it) then you need to wait before it will be shown. We are almost a day further at the moment of writing this, so it should be visible now :P 

 

If not, the link from Kurt above is really helpful. 


Forum|alt.badge.img+1
  • Author
  • Adventurer
  • 9 replies
  • August 9, 2024

Thanks guys!

@ktelep - I did see this page and to be honest, I got caught up on it saying local vs ifalias/ifname in Issue 1.  I have a ticket opened with Meraki.

 

 


Forum|alt.badge.img+1
  • Author
  • Adventurer
  • 9 replies
  • August 9, 2024

FYI, Meraki doesn’t support interface name only interface alias. Thanks for all your help.