• February 24, 2018, 01:28:05 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: COM v3.1 and VSP 7000 - Problem with discovery  (Read 883 times)

0 Members and 1 Guest are viewing this topic.

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
COM v3.1 and VSP 7000 - Problem with discovery
« on: March 10, 2016, 11:46:04 AM »
Hi, I need your help.

COM v3.1
VSP 7000 OS 10.3.2.011 (with 10.4.0.003 the same problem)

- App doesn't draw the topology of my switch's connections
- "Dump topology" shows me the list of my neighbour, all are discovered with SONMP
- "Show" connections table is empty
- Device is via SNMP reachable
- ALL links are up
- I've deactivated the autotopology and reactivate it
- I've deactivated the SNMP and reactivate it
- via LLDP I see all my neighbours with IPs
- my autotopology shows me 24 connections
- my VSP 7000 works in a stack (half ring):
Code: [Select]
VSP7K-STACK-NEW(config)#sh stack health

------------------------------------------------------------------------------
UNIT#            Switch Model       Cascade Up            Cascade Down
------------------------------------------------------------------------------
1 (Base)          7024XLS           OK                    LINK DOWN or MISSING
2                 7024XLS           LINK DOWN or MISSING  OK

------------------------------------------------------------------------------
Switch Units Found = 2
Stack Health Check = WARNING - NON-RESILIENT
Stack Diagnosis = Stack in non-resilient mode.
Recommend to add/replace the identified cable(s).

- I deactivated the option "filter untagged frames" on trunk links:

Code: [Select]
Unit/Port  Frames     Frames    PVID PRI    Tagging    Name
--------- -------- ------------ ---- --- ------------- ----------------
2/24      No       Yes          1    0   TagAll        Unit 2,Port 24



I've read the COM limitations for VSP 7k on his site:
https://downloads.avaya.com/css/P8/documents/100173537
and I've seen the supportet VSP's version on this site: https://downloads.avaya.com/css/P8/documents/100182341

but in my COM I have already the other VSPs (not in a stack) with teh same OS and it workds there. Where is an error?

ACE-Fx I #00531


Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: COM v3.1 and VSP 7000 - Problem with discovery
« Reply #1 on: March 16, 2016, 07:05:28 AM »
We created the SMLT with this 2 VSPs and after that, I see the topology table in Avaya COM.

With STACK + OS 10.3.2.011 or 10.4.0.003 + Avaya COM 3.1 (august 2014) ist doesn't work. BTW: I can't upgrade Avaya COM into 3.1.3 (februrary 2016).
ACE-Fx I #00531