• October 16, 2018, 03:42:21 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Problem in connection between VSP7254XSQ & 4826GTS-PWR+  (Read 3081 times)

0 Members and 1 Guest are viewing this topic.

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« on: July 13, 2016, 12:33:34 PM »
I migrate the ASWes from old DSW (5530-24TFD) into new DSW/BEB (VSP7254XSQ). I don't see the old 4826GTS-PWR+ on my new DSW (gigabit1/5). I see only f.e. the ERSes ERS3549GTS-PWR+ (gigabit1/4).
- The AUTOTOPOLOGY table doesn't show me the 4800.
- I am not able to reach my old 4800 in MGMT network, via ICMP or SSH.
- The physical interface is up und operational
- I changed the GBIT Tranceiver - no effects, Port is still up and operational
- I reconnected the ERS3500 from gi1/4 into gi1/5 - the SW could be visible
- I reconnected the ERS4800 from gi1/5 into gi1/4 - teh SW is not visible
- L1 is OK.

Any ideas?

Code: [Select]
#show autotopology nmm-table
==========================================================================================
                                      Topology Table
==========================================================================================
Local                                                                              Rem
Port     IpAddress       SegmentId MacAddress   ChassisType            BT LS  CS   Port
------------------------------------------------------------------------------------------
1/4      10.42.4.240     0x00012f  10cdae87f801 ERS3549GTS-PWR+        12 Yes HtBt  1/47

Code: [Select]
show interface gi1/4 & show interface gi1/5
==================================================================================================
                                          Port Interface
==================================================================================================
PORT                            LINK  PORT           PHYSICAL          STATUS         LICENSE
NUM      INDEX DESCRIPTION      TRAP  LOCK     MTU   ADDRESS           ADMIN  OPERATE STATUS
--------------------------------------------------------------------------------------------------
1/4      195   GbicOther        true  false    1950  c4:be:d4:01:20:03 up     up      n/a
1/5      196   GbicOther        true  false    1950  c4:be:d4:01:20:04 up     up      n/a


==========================================================================================
                                        Port Name
==========================================================================================
PORT                                                     OPERATE  OPERATE  OPERATE
NUM      NAME                           DESCRIPTION      STATUS   DUPLX    SPEED    VLAN
----------------------------------------------------------------------------------------------------
1/4      ERS3500              GbicOther        up       full     1000     Tagged
1/5      ERS4800              GbicOther        up       full     1000     Tagged
ACE-Fx I #00531


Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #1 on: July 13, 2016, 01:15:21 PM »
And other questions:

- How can I check the MAC table on VSP7200?
Code: [Select]
SW:1(config)#show mac-address-table ?
Display forwarding database tables info
  aging-time  Display forwarding database aging time



SW:1(config)#show mac-address-table
                                                          ^
% Incomplete command.  See '^' marker.


- How can I activate the LLDP on VSP7200?
Code: [Select]
(config)#lldp ?
  tx-hold-multiplier  transmission hold multiplier
  tx-interval         transmission interval
Code: [Select]
(config)#show lldp port 1/5

====================================================================================================
                             LLDP Admin Port Status

====================================================================================================
----------------------------------------------------------------------------------------------------
Port       AdminStatus  ConfigNotificationEnable
----------------------------------------------------------------------------------------------------
1/5        disabled     disabled
ACE-Fx I #00531

Offline MatzeKS

  • Sr. Member
  • ****
  • Posts: 300
    • matzeks
    • Controlware GmbH - Germany
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #2 on: July 13, 2016, 05:05:11 PM »
Hi mixthoor,

regarding the missing topology information of the ERS-4800 please make sure that "auto-topology" is enabled on the ERS-4800. Which software version have you running on the ERS-4800? Did you try to reset the 4800 to factory defaults?

VSP7200 (VOSS-Code):
LLDP is currently (VOSS 5.1.1.1) not implemented per default.
In VOSS 5.1 Fabric Attach (FA) comes in place and if you enable FA on uplink port(s) LLDP will be come active on this/those ports to discover the "LLDP neighbor(s)" to get FA working.


Display Mac-Table on VOSS:

VSP8284-02:1#sho vlan mac-address-entry ?
  mac                 Mac address
  port                Portlist
  <1-4059>            Vlan id
  spbm-tunnel-as-mac  show spbm mac-address-entry tunnel as mac
  <cr>


VSP8284-02:1#sho lldp neighbor

==========================================================================================
                                      LLDP Neighbor
==========================================================================================

Port: 1/35      Index    : 1                  Time: 21 day(s), 14:17:43
                ChassisId: MAC Address        04:78:56:xx:xx:00
                PortId   : MAC Address        04:78:56:xx:xx:xx
                SysName  : 4926GTS-01
                SysCap   : Br / B
                PortDescr: Port 25
                SysDescr : Ethernet Routing Switch 4926GTS-PWR+     HW:00       FW:7.1.0.5   SW:v7.2.0.009
------------------------------------------------------------------------------------------
Total Neighbors : 1
------------------------------------------------------------------------------------------
Capabilities Legend: (Supported/Enabled)
B= Bridge,    D= DOCSIS,    O= Other,     R= Repeater,
S= Station,   T= Telephone, W= WLAN,      r= Router


VSP8284-02:1#sho fa elements

====================================================================================================
                        Fabric Attach Discovery Elements

====================================================================================================
                         MGMT                                         ELEM ASGN
PORT   TYPE              VLAN STATE  SYSTEM ID                        AUTH AUTH
----------------------------------------------------------------------------------------------------
1/35   proxy             910  T / S  04:78:56:xx:xx:00:00:00:00:xx    AP   AP

====================================================================================================
                      Fabric Attach Authentication Detail

====================================================================================================
       ELEM OPER                      ASGN OPER
PORT   AUTH STATUS                    AUTH STATUS
----------------------------------------------------------------------------------------------------
1/35   successAuth                    successAuth

State Legend: (Tagging/AutoConfig)
T= Tagged,    U= Untagged,    D= Disabled,    S= Spbm,    V= Vlan,    I= Invalid

Auth Legend:
AP= Authentication Pass,  AF= Authentication Fail,
NA= Not Authenticated,  N= None

VSP8284-02:1#sho autotopology nmm-table
==========================================================================================
                                      Topology Table
==========================================================================================
Local                                                                              Rem
Port     IpAddress       SegmentId MacAddress   ChassisType            BT LS  CS   Port
------------------------------------------------------------------------------------------
0/0      17x.xxx.xx.11   0x000000  xxxxxxxxxxxx VSP8284XSQ             12 Yes HtBt  0/0
1/25     10.x.xxx.10     0x000xxx  xxxxxxxxxxxx ERS5510-48T            12 Yes HtBt  1/47
1/31     10.x.xxx.12     0x000xxx  xxxxxxxxxxxx ERS4826GTS-PWR+        12 Yes HtBt  1/25
1/33     10.x.xxx.11     0x000xxx  xxxxxxxxxxxx ERS5510-48T            12 Yes HtBt  1/48
1/35     10.x.xxx.14     0x000xxx  xxxxxxxxxxxx ERS4926GTS-PWR+        12 Yes HtBt  1/25
1/39     10.x.xxx.10     0x000xxx  xxxxxxxxxxxx ERS5928GTS-PWR+        12 Yes HtBt  1/27
2/31     10.x.xxx.12     0x000xxx  xxxxxxxxxxxx ERS4826GTS-PWR+        12 Yes HtBt  1/26
2/35     10.x.xxx.13     0x000xxx  xxxxxxxxxxxx ERS5928GTS-PWR+        12 Yes HtBt  1/25
2/39     10.x.xxx.10     0x000xxx  xxxxxxxxxxxx ERS5928GTS-PWR+        12 Yes HtBt  1/28
VSP8284-02:1#




« Last Edit: July 13, 2016, 05:16:39 PM by MatzeKS »
------------------------------------------------------
ACE-Fx #00050

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #3 on: July 14, 2016, 02:49:20 AM »
- On the Uplink Port (connection to ERS 4800), I don't see any MAC address.
- I can activate FA in the Port, then I receive the info, that the "VLANs on the Port are not allowed". I need the VLANs on this Port, it's UNI and there are many tagged frames from diffrent subnetworks.
- Autotopology on the ASW (ERS 4826) is activ, on the DSW I can see the connection, via old DSW I can reach the ASW with ICMP or SSH.
- I made an BOSS Upgrade on the ERS4826 - it doesn't help. On old DSW is visible, on new DSW not.
- I created the Case via Avaya Support Page.
ACE-Fx I #00531

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #4 on: July 14, 2016, 06:16:14 AM »
The problem was on 25,26 Ports (49,50) on ERS4826, ERS4850 switches. I had to replace the Gbit tranceivers from 25,26 into 23,24 and 49,50 into 47,48. After that I was able to see the ASWes via SONMP and reach them via SSH.
ACE-Fx I #00531

Offline MatzeKS

  • Sr. Member
  • ****
  • Posts: 300
    • matzeks
    • Controlware GmbH - Germany
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #5 on: July 14, 2016, 06:50:36 AM »
ok, that means you plugged your standard GBICs in the SFP+ ports  ;)
On ERS4826 the ports 25+26 will also work with SFP+


VSP8284-02:1#sho autotopology nmm-table
==========================================================================================
                                      Topology Table
==========================================================================================
...
1/31     10.x.xxx.12     0x000xxx  xxxxxxxxxxxx ERS4826GTS-PWR+        12 Yes HtBt  1/25
2/31     10.x.xxx.12     0x000xxx  xxxxxxxxxxxx ERS4826GTS-PWR+        12 Yes HtBt  1/26
...
------------------------------------------------------
ACE-Fx #00050

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #6 on: July 15, 2016, 02:37:46 AM »
OK, I have the old Nortel 1GBit Tranceiver.
I will try with the new
Code: [Select]
AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV

---
UPDATE:
it doesn't work...
DSW - VSP7200 v5.1.1.1
gi 1/7
Code: [Select]
==========================================================================================
                                        Port Name
==========================================================================================
PORT                                                     OPERATE  OPERATE  OPERATE
NUM      NAME                           DESCRIPTION      STATUS   DUPLX    SPEED    VLAN
----------------------------------------------------------------------------------------------------
1/7                                     GbicSx           up       full     1000     Tagged


====================================================================================================
                                   Port State


====================================================================================================
PORT NUM   ADMINSTATUS  PORTSTATE   REASON        DATE
----------------------------------------------------------------------------------------------------
1/7        up           up          --            07/15/16 10:11:11




====================================================================================================
                                  Port Config

====================================================================================================

PORT                      DIFF-SERV    QOS   MLT   VENDOR
NUM      TYPE             EN    TYPE   LVL   ID    NAME
----------------------------------------------------------------------------------------------------
1/7      GbicSx           true  core   1     0     Avaya


ASW - ERS4850 v5.9.3.023s
gi 49
Code: [Select]
(config)#show interfaces gbic-info 49
        Port  Number     49
        GBIC   Type      SX
        Wavelength       850 nm
        Vendor Name      AVAYA
        Vendor OUI       00019C
        Vendor Part #    PLRXPL-VI-S24-AV
        Vendor Revision  1
        Vendor Serial    JDSUCNCF13DT2EX
        HW Options       TX_DISABLE TX_FAULT RX_LOSS
        Date Code        03/28/2015
        CLEI Code        IPUIAHCWAA
        Product Code     AA1419048-E6


*****

ON VSP7200 I don't see the MACs in my MGMT VLAN:
Code: [Select]
# show vlan mac-address-entry port 1/7

====================================================================================================
                                    Vlan Fdb

====================================================================================================
VLAN            MAC                                   SMLT
ID   STATUS     ADDRESS            INTERFACE          REMOTE   TUNNEL
----------------------------------------------------------------------------------------------------

c: customer vid   u: untagged-traffic

0 out of 1002 entries in all fdb(s) displayed.

ASW is via ICMP or SSH or SONMP not visible. When I take the shared port 47 or 48, it works...
« Last Edit: July 15, 2016, 04:14:46 AM by mixthoor »
ACE-Fx I #00531

Offline MatzeKS

  • Sr. Member
  • ****
  • Posts: 300
    • matzeks
    • Controlware GmbH - Germany
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #7 on: July 15, 2016, 04:27:52 AM »
You tried to use this GBIC Type (AA1419048-E6) on one of your ERS4850 SFP+ Ports, this type of Transceiver will work on ports 47-48 only.

AA1419048-E6:
Avaya / Nortel 1-port 1000Base-SX Small Form Factor Pluggable (SFP) Gigabit Ethernet Transceiver, connector type: LC. Digital Diagnostic Monitoring Interface

I'd recommend you this type of transceiver instead:
AA1403015-E6
https://www.flexoptix.net/en/sfp-plus-sr-transceiver-10-gigabit-stm64-mm-850nm-300m-5db-ddm-dom.html?compatibility=41335
------------------------------------------------------
ACE-Fx #00050

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #8 on: July 15, 2016, 05:02:08 AM »
I made some tests. I becam the tipp from Avaya Support - disable auto-negotiation.

---

TEST 1
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP

RESULT: ASW on DSW not visible, L1 UP/UP

----

TEST 2
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP

RESULT: ASW on DSW not visible, L1 UP/UP

----

TEST 3
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP

RESULT: ASW on DSW not visible, L1 UP/UP

----

TEST 4
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP

RESULT: ASW on DSW not visible, L1 UP/UP

---

TEST 5
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: DOWN, SPEED 1000, DUPLEX FULL

RESULT: ASW on DSW visible, L1 UP/UP

----

TEST 6
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: DOWN, SPEED 1000, DUPLEX FULL

RESULT: ASW on DSW visible, L1 UP/UP

----

TEST 7
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: JDS Uniphase SFP Optical Tranceiver, 200/100-M5/M6 SN-I 1000Base-SX, JSM-21S3AA1
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: DOWN, SPEED 1000, DUPLEX FULL

RESULT: ASW on DSW visible, L1 UP/UP

----

TEST 8
DSW: VSP-7254XSQ v5.1.1.1
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: UP, could not be disabled
<--->
ASW: ERS 4850GTS-PWR+ v.v5.9.3.023
TRANCEIVER: AVAYA GbE SX DDI 550m, 850nm AA1419048-E6, Class 1, 21CFR1040.10, LN#50, PLRXPL-VI-S24-AV
AUTO-NEGOTIATION: DOWN, SPEED 1000, DUPLEX FULL

RESULT: ASW on DSW visible, L1 UP/UP

*******************************

I need more information about TSHOOT Layer 1 on Avaya Switches in the future. I though, that L1 was OK, when I saw on the DSW:
Code: [Select]
==================================================================================================
                                          Port Interface
==================================================================================================
PORT                            LINK  PORT           PHYSICAL          STATUS         LICENSE
NUM      INDEX DESCRIPTION      TRAP  LOCK     MTU   ADDRESS           ADMIN  OPERATE STATUS
--------------------------------------------------------------------------------------------------
1/7      198   GbicSx           true  false    1950  c4:be:d4:01:20:06 up     up      n/a

I see right know, it is not enough. Can you give me some tipps about TSHOOT L1 on Avaya?
ACE-Fx I #00531

Offline mixthoor

  • Full Member
  • ***
  • Posts: 53
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #9 on: July 27, 2016, 03:02:04 AM »
I found useful command:
Code: [Select]
SW:1#show pluggable-optical-modules ?
  basic        Show basic SFP/SFP+ info
  config       Show pluggable-optical-modules config info
  detail       Show detail SFP/SFP+ info
  temperature  Show SFP/SFP+ temperature info
  voltage      Show SFP/SFP+ voltage info

The solution in this fall was disabling the Auto-Negotiation on ASWes (ERS 4800) and set the speed/duplex manually. Case closed.
ACE-Fx I #00531

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1564
    • Networkautobahn
Re: Problem in connection between VSP7254XSQ & 4826GTS-PWR+
« Reply #10 on: August 03, 2016, 05:03:58 AM »
Good to hear that it worked out.
Thanks for sharing the solution for your problem.

Cheers
Itīs always the networks fault!
networkautobahn.com