cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
dougk
New Contributor

Switches stop responding for short periods of time

We have a customer with 7 Adtran switches. (2) 1534, (3) 1238 R2 (2) 1234 R2. The 1238 and the 1234 are on 10.5.3 (per Adtran support). I did have the on firmware 2A R10-8. When the 1238 * 1234 were on that version they, on occassion, were losing half of their POE ports. A reboot fixed the issue. Per Adtran support, they suggested I take them to 10.5.3. Which is a downgrade but I did.

They are set up as follows they have separate wiring for data and phones. These switches below are all voice switches. All set as VLAN 200 as native

Floor 1-1238 (Phone switch) with PBX equipment attached (ShoreTel)

     -Fiber Module connects to 2nd floor

     -Fiber module connects to 3rd floor

     -1 port on 1238 connects to one of the 1534s. The primary 1534 is a core switch and gateway for voice and data subnets. VLANS 1 (data) 200 (Voice). Both VLANs have IPs

Floor 2

1238 Fiber connect to 1st floor

1234 patch cable connected to 1238

Floor 3

1238 Fiber connect to 1st floor

1234 patch cable connected to 1238

Issue we have been having and we are not sure if it was present prior to the change in firmware. Is that the 1 of the switches in the 5 voice switches stops responding to anything for 5 to 15 minutes. The phones remain powered on and they do not reboot. They just go from No Service to back into service. If it is the 1238 that goes out, any switch connected behind it becomes unresponsive as well (obviously). We did have it where fiber from Floor 3 was going to Fiber in Floor 2, The Floor 2 to Floor 1. We changed it so each of the other 2 floors connect directly to floor 1.

Today the 1234 on Floor 3 went out for 10 minutes. The phones went from No Service to back in service. During that time, I couldn't ping the switch. When the phones came back to normal, I got into the switch just fine. (all other of the 4 switches were accessible). I am at a loss. I believe this is a firmware bug, but we had issues with the higher firmware versions.

During that 10 minute peroid, nothing was posted to the switch log between the time it stopped responding and the time it came back.

2013.09.20 14:58:59 INTERFACE_STATUS.swx 0/15 changed state to up 

2013.09.20 15:09:16 OPERATING_SYSTEM.SESSION User admin login OK on portal HTTP (192.168.10.250:54017)

There isn't much to these configs. Here is the config for the switch that went out today. All of the other switches are almost 100% identical.


! ADTRAN, Inc. OS version R10.5.3
! Boot ROM version XB.01.02
! Platform: NetVanta 1234 PoE, part number 1702595G1

!
hostname "Voice-3rd Floor 1234"

!
clock timezone -5-Eastern-Time
ip default-gateway 192.168.10.10
name-server 8.8.8.8
!
!
no auto-config
!
event-history on
event-history priority debug
logging forwarding on
logging facility local0
logging forwarding priority-level debug
logging forwarding receiver-ip 192.168.10.250
no logging email

!
!
no dot11ap access-point-control

!
qos queue-type wrr 25 25 25 expedite
!

!
vlan 1
  name "Default"
!
vlan 200
  name "Phones"
!
interface switchport 0/1
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/2
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/3
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/4
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/5
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/6
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/7
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/8
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/9
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/10
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/11
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/12
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/13
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/14
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/15
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/16
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/17
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/18
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/19
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/20
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/21
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/22
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/23
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
interface switchport 0/24
  description --->Phone<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200
!
!
interface gigabit-switchport 0/1
  description --->Trunk or Uplink Port<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200

!
interface gigabit-switchport 0/2
  description --->Trunk or Uplink Port<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200

!
interface gigabit-switchport 0/3
  description --->Trunk Fiber<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200

!
interface gigabit-switchport 0/4
  description --->Trunk Fiber<---
  spanning-tree edgeport
  no shutdown
  switchport access vlan 200

!
!
!
interface vlan 1
  ip address  10.10.10.5  255.255.255.0
  shutdown
!
interface vlan 200
  ip address  192.168.10.233  255.255.254.0
  ip mtu 1500
  no awcp
  no shutdown
!
!
!
!
!
no tftp server
no tftp server overwrite
http server
http secure-server
snmp agent
no ip ftp server
no ip scp server
no ip sntp server

!
end


Labels (1)
0 Kudos
2 Replies
Anonymous
Not applicable

Re: Switches stop responding for short periods of time

:

It appears you have opened a ticket with ADTRAN Technical Support for assistance with this post.  Please, return to this post and update it when you have finished.

Levi

Anonymous
Not applicable

Re: Switches stop responding for short periods of time

-

I went ahead and flagged this post as "Assumed Answered". If any of the responses on this thread assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons. This will make them visible and help other members of the community find solutions more easily. If you have any additional information on this that others may benefit from, please come back to this post to provide an update. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Noor