ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

Brandnew J9850A 5406R Switch stops routing after some time.

KMB_Admin
Occasional Visitor

Brandnew J9850A 5406R Switch stops routing after some time.

Hi,

i have a problem with a brandnew 5406R zl2 Switch. Our core switch is a DXS-3326GSR from D-Link. The core switch provides the transport VLAN for this Switch untagged. One other VLAN are provided tagged. It is a trunked uplink via LACP:

Here is my confguration:

; J9850A Configuration Editor; Created on release #KB.16.01.0004
; Ver #0c:01.7c.59.f4.7b.ff.ff.fc.ff.ff.3f.ef:
hostname "*******"
module A type j9534a
module B type j9535a
module C type j9550a
module D type j9535a
trunk B21-B24,D21-D24 trk1 lacp
timesync sntp
sntp unicast
sntp server priority 1 192.168.1.35
no telnet-server
time daylight-time-rule western-europe
time timezone 60
ip dns domain-name "*******"
ip dns server-address priority 1 192.168.1.18
ip dns server-address priority 2 192.168.1.35
ip route 0.0.0.0 0.0.0.0 10.76.33.5
ip routing

interface A1
   flow-control
   exit
interface A2
   flow-control
   exit
interface A3
   flow-control
   exit
interface A4
   flow-control
   exit

.....

interface D24
   flow-control
   exit
snmp-server community "public" unrestricted
snmp-server contact "*******"
oobm
   no ip address
   exit
vlan 1
   name "DEFAULT_VLAN"
   no untagged A1-A24,B1-B20,C1-C24,D1-D20,Trk1
   no ip address
   exit
vlan 23
   name "server***"
   untagged D13-D20
   tagged Trk1
   ip address 192.168.1.72 255.255.255.0
   exit
vlan 550
   name "tn****"
   untagged Trk1
   ip address 10.76.33.6 255.255.255.252
   exit
vlan 560
   name "cn****"
   untagged A1-A24,B1-B20,C1-C24,D1-D12
   ip address 10.76.97.1 255.255.255.0
   ip helper-address 192.168.1.18
   exit
primary-vlan 560
spanning-tree Trk1 priority 4
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator

This configuration works fine after a reboot. In the Client Net 10.76.97.0/24 I'm getting an IP from DHCP and I can acces the whole network.:

ping 192.168.1.18 source 560
192.168.1.18 is alive, time = 1 ms

But after a irregular period of time (30 min - 12 hours) the switch stops routing from the client Vlan 560.

ping 192.168.1.18 source 560
Request timed out.

I' ve tried a lot to get this device working properly, but this Problem presists. The shown ip routing table is correct:

  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.
  ------------------ --------------- ---- --------- ---------- ---------- -----
  0.0.0.0/0          10.76.33.5      550  static               1          1
  10.76.33.4/30      tn****          550  connected            1          0
  10.76.97.0/24      cn****          560  connected            1          0
  127.0.0.0/8        reject               static               0          0
  127.0.0.1/32       lo0                  connected            1          0
  192.168.1.0/24     server****       23   connected            1          0

The clients get IP from DHCP but are not able to access someting. If the switch is in this non working status the only thing you can do to get it working again is a reboot. Then the switch will work for some time.

sincerely

Eric

2 REPLIES
Vince-Whirlwind
Honored Contributor

Re: Brandnew J9850A 5406R Switch stops routing after some time.

Is the host addressed as 192.168.1.18 patched to one of the untagged ports (D13-D20) on the 5400 that are in VLAN 23?

What is 192.168.1.18's default gateway set as?

What is connected to "Trk1"?

Why are you routing on the 5400 when you say your Dell switch is your "Core"?

If you have two switches doing routing, why are trunking VLANs between them?

When it is in a non-working state, show us a route print from the 192.168.1.18 host as well as from the Dell "Core".

KMB_Admin
Occasional Visitor

Re: Brandnew J9850A 5406R Switch stops routing after some time.

Hi Vince,

thanks for your reply. I think i have to wait now, but i think the Problem is located in the D-Link Core Switch. I have changed the port at the core switch and now the problems don't show up.

Eric