Nick
asked on
Excessive broadcasts originating from my switch(HP procurve) and weird network problems
In the past two days i have had an issue where all of my sharp branded printers are expericing packet loss. No other machines seem to have this problem and i haven't heard from any users having problems with any applications. Just sometimes their printers don't work. There are no errors/alrerts on my hp 5406zl switch. I have been running a Fluke network analyzer and it is showing alot of broadcast originating from my hp switch.
The switch is doing layer 3 routing and all of my general traffic is in vlan 1 on 4 subnets.
Here is the config,
Running configuration:
; J8697A Configuration Editor; Created on release #K.13.71
hostname "ProCurve Switch 5406zl"
module 1 type J8702A
module 2 type J8702A
module 3 type J8702A
module 4 type J8705A
interface D1
name "Internet Ports"
flow-control
exit
interface D2
name "Internet Ports"
flow-control
exit
interface D3
name "Internet Ports"
flow-control
exit
interface D4
name "Internet Ports"
flow-control
exit
interface D5
name "Frontier Uplink to Fiber"
flow-control
exit
interface D6
name "Internet Ports"
flow-control
exit
interface D7
name "Internet Ports"
flow-control
exit
interface D8
name "Internet Ports"
flow-control
exit
interface D9
name "Internet Ports"
flow-control
exit
interface D10
name "Internet Ports"
flow-control
exit
interface D11
name "Internet Ports"
flow-control
exit
interface D12
name "Internet Ports"
flow-control
exit
interface D13
name "Compellent 2081 ISCSI"
flow-control
exit
interface D15
name "Compellent 2080 ISCSI"
flow-control
exit
interface D17
name "Riverbed Switch Access"
flow-control
exit
interface D19
name "Archive replication"
flow-control
exit
interface A1
name "Trunk to Bladon Router"
flow-control
exit
interface A2
name "redmail"
exit
interface A3
name "VM2"
flow-control
exit
interface A4
name "ironport"
exit
interface A5
name "VM2"
flow-control
exit
interface A6
name "isa"
exit
interface A7
name "Cisco Wireless Controller"
exit
interface A8
name "msp server"
exit
interface A9
name "vm6 trunk"
flow-control
exit
interface A10
name "archive"
exit
interface A11
name "vm6 trunk"
flow-control
exit
interface A12
name "dc1"
exit
interface A13
name "vm1 trunk"
flow-control
exit
interface A14
name "REDVC"
exit
interface A15
name "vm1 trunk"
flow-control
exit
interface A16
name "sophos"
exit
interface A17
name "trunk to switch3"
flow-control
exit
interface A18
name "trigeo"
exit
interface A19
name "trunk to switch3"
flow-control
exit
interface A20
name "Dvr Controller"
exit
interface A21
name "Trunk to Switch2"
flow-control
exit
interface A22
name "storetermserv"
exit
interface A23
name "Trunk to Switch2"
flow-control
exit
interface A24
name "daxdb"
exit
interface B1
flow-control
exit
interface B2
name "Compellent CTRL ports"
exit
interface B3
name "VM2"
flow-control
exit
interface B4
name "Compellent CTRL ports"
exit
interface B5
name "VM2"
flow-control
exit
interface B6
name "SAN Fiber Switches"
exit
interface B8
name "SAN Fiber Switches"
exit
interface B9
name "vm6 trunk"
flow-control
exit
interface B10
name "Md3000i Management"
exit
interface B11
name "vm6 trunk"
flow-control
exit
interface B12
name "Md3000i Management"
exit
interface B13
name "vm1 trunk"
flow-control
exit
interface B14
name "jde servers external"
exit
interface B15
name "vm1 trunk"
flow-control
exit
interface B16
name "jde servers external"
exit
interface B17
name "trunk to switch3"
flow-control
exit
interface B18
name "jde servers external"
exit
interface B19
name "trunk to switch3"
flow-control
exit
interface B20
name "jde server internal"
exit
interface B21
name "Trunk to Switch2"
flow-control
exit
interface B22
name "jde server internal"
exit
interface B23
name "Trunk to Switch2"
flow-control
exit
interface B24
name "jde server internal"
exit
interface C3
name "VM2"
flow-control
exit
interface C5
name "VM2"
flow-control
exit
interface C19
name "Snort Mirror Port"
exit
trunk A21,A23,B21,B23 Trk2 Trunk
trunk A9,A11,B9,B11 Trk6 Trunk
trunk A13,A15,B13,B15 Trk1 Trunk
trunk A17,A19,B17,B19 Trk3 Trunk
trunk A3,A5,B3,B5,C3,C5 Trk12 Trunk
ip default-gateway 192.168.90.254
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged A1-A2,A4,A6-A8,A10,A12,A14 ,A16,A18,A 20,A22,A24 -B2,B4,B6- B8,B10,B12 ,B14,B16,B 18,B20,B22 ,B24-C2,C4 ,C6-C24,D1 4,D16,D18, D21,D23,Tr k1-Trk3,Tr k6,Trk12
ip address 192.168.90.1 255.255.255.0
ip address 192.168.92.1 255.255.255.0
ip address 192.168.91.1 255.255.255.0
ip address 172.25.25.1 255.255.255.0
no untagged D1-D13,D15,D17,D19-D20,D22 ,D24
ip proxy-arp
exit
vlan 101
name "101replicati"
untagged D13,D15,D17,D19
no ip address
exit
vlan 100
name "100jdeprivat"
untagged D20,D22,D24
no ip address
exit
vlan 102
name "102internet"
untagged D1-D12
no ip address
exit
vlan 250
name "VLAN250"
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
mirror 1 port C19
ip route 0.0.0.0 0.0.0.0 192.168.90.254
interface A1
monitor all Both mirror 1
exit
interface A12
monitor all Both mirror 1
exit
interface A14
monitor all Both mirror 1
exit
snmp-server community "public" Operator
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
spanning-tree Trk6 priority 4
spanning-tree Trk12 priority 4
password manager
password operator
The switch is doing layer 3 routing and all of my general traffic is in vlan 1 on 4 subnets.
Here is the config,
Running configuration:
; J8697A Configuration Editor; Created on release #K.13.71
hostname "ProCurve Switch 5406zl"
module 1 type J8702A
module 2 type J8702A
module 3 type J8702A
module 4 type J8705A
interface D1
name "Internet Ports"
flow-control
exit
interface D2
name "Internet Ports"
flow-control
exit
interface D3
name "Internet Ports"
flow-control
exit
interface D4
name "Internet Ports"
flow-control
exit
interface D5
name "Frontier Uplink to Fiber"
flow-control
exit
interface D6
name "Internet Ports"
flow-control
exit
interface D7
name "Internet Ports"
flow-control
exit
interface D8
name "Internet Ports"
flow-control
exit
interface D9
name "Internet Ports"
flow-control
exit
interface D10
name "Internet Ports"
flow-control
exit
interface D11
name "Internet Ports"
flow-control
exit
interface D12
name "Internet Ports"
flow-control
exit
interface D13
name "Compellent 2081 ISCSI"
flow-control
exit
interface D15
name "Compellent 2080 ISCSI"
flow-control
exit
interface D17
name "Riverbed Switch Access"
flow-control
exit
interface D19
name "Archive replication"
flow-control
exit
interface A1
name "Trunk to Bladon Router"
flow-control
exit
interface A2
name "redmail"
exit
interface A3
name "VM2"
flow-control
exit
interface A4
name "ironport"
exit
interface A5
name "VM2"
flow-control
exit
interface A6
name "isa"
exit
interface A7
name "Cisco Wireless Controller"
exit
interface A8
name "msp server"
exit
interface A9
name "vm6 trunk"
flow-control
exit
interface A10
name "archive"
exit
interface A11
name "vm6 trunk"
flow-control
exit
interface A12
name "dc1"
exit
interface A13
name "vm1 trunk"
flow-control
exit
interface A14
name "REDVC"
exit
interface A15
name "vm1 trunk"
flow-control
exit
interface A16
name "sophos"
exit
interface A17
name "trunk to switch3"
flow-control
exit
interface A18
name "trigeo"
exit
interface A19
name "trunk to switch3"
flow-control
exit
interface A20
name "Dvr Controller"
exit
interface A21
name "Trunk to Switch2"
flow-control
exit
interface A22
name "storetermserv"
exit
interface A23
name "Trunk to Switch2"
flow-control
exit
interface A24
name "daxdb"
exit
interface B1
flow-control
exit
interface B2
name "Compellent CTRL ports"
exit
interface B3
name "VM2"
flow-control
exit
interface B4
name "Compellent CTRL ports"
exit
interface B5
name "VM2"
flow-control
exit
interface B6
name "SAN Fiber Switches"
exit
interface B8
name "SAN Fiber Switches"
exit
interface B9
name "vm6 trunk"
flow-control
exit
interface B10
name "Md3000i Management"
exit
interface B11
name "vm6 trunk"
flow-control
exit
interface B12
name "Md3000i Management"
exit
interface B13
name "vm1 trunk"
flow-control
exit
interface B14
name "jde servers external"
exit
interface B15
name "vm1 trunk"
flow-control
exit
interface B16
name "jde servers external"
exit
interface B17
name "trunk to switch3"
flow-control
exit
interface B18
name "jde servers external"
exit
interface B19
name "trunk to switch3"
flow-control
exit
interface B20
name "jde server internal"
exit
interface B21
name "Trunk to Switch2"
flow-control
exit
interface B22
name "jde server internal"
exit
interface B23
name "Trunk to Switch2"
flow-control
exit
interface B24
name "jde server internal"
exit
interface C3
name "VM2"
flow-control
exit
interface C5
name "VM2"
flow-control
exit
interface C19
name "Snort Mirror Port"
exit
trunk A21,A23,B21,B23 Trk2 Trunk
trunk A9,A11,B9,B11 Trk6 Trunk
trunk A13,A15,B13,B15 Trk1 Trunk
trunk A17,A19,B17,B19 Trk3 Trunk
trunk A3,A5,B3,B5,C3,C5 Trk12 Trunk
ip default-gateway 192.168.90.254
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged A1-A2,A4,A6-A8,A10,A12,A14
ip address 192.168.90.1 255.255.255.0
ip address 192.168.92.1 255.255.255.0
ip address 192.168.91.1 255.255.255.0
ip address 172.25.25.1 255.255.255.0
no untagged D1-D13,D15,D17,D19-D20,D22
ip proxy-arp
exit
vlan 101
name "101replicati"
untagged D13,D15,D17,D19
no ip address
exit
vlan 100
name "100jdeprivat"
untagged D20,D22,D24
no ip address
exit
vlan 102
name "102internet"
untagged D1-D12
no ip address
exit
vlan 250
name "VLAN250"
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
mirror 1 port C19
ip route 0.0.0.0 0.0.0.0 192.168.90.254
interface A1
monitor all Both mirror 1
exit
interface A12
monitor all Both mirror 1
exit
interface A14
monitor all Both mirror 1
exit
snmp-server community "public" Operator
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
spanning-tree Trk6 priority 4
spanning-tree Trk12 priority 4
password manager
password operator
ASKER
that is the plan, but i cannot do it at this time. Do you believe that is the issue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it is unclear for me, that broadcasts is a issue.
I would like to know if printers are experiencing packet loss all the time or during some hours. and how many broadcasts in kbps you have, when printers are suffering from packet loss.
and one more things to check: actual connection speeds for printers (my experience shows this is an issue in most such cases). if it happens to be 10 half, then even shy volume of broadcasts can cause a issue. and in 10 mbps half the could be if auto negotiation fails for some reason. in this case try to configure 100 full at both ends - switch and printer.
and I hope you don't have unicast NLB clusters out there. If you have, then check for unicast flooding (this is when all PCs within a vlan receive a traffic, which is happening between NLB node and any other PC)
I would like to know if printers are experiencing packet loss all the time or during some hours. and how many broadcasts in kbps you have, when printers are suffering from packet loss.
and one more things to check: actual connection speeds for printers (my experience shows this is an issue in most such cases). if it happens to be 10 half, then even shy volume of broadcasts can cause a issue. and in 10 mbps half the could be if auto negotiation fails for some reason. in this case try to configure 100 full at both ends - switch and printer.
and I hope you don't have unicast NLB clusters out there. If you have, then check for unicast flooding (this is when all PCs within a vlan receive a traffic, which is happening between NLB node and any other PC)
ASKER
yes, basically all day. all printers are 100mb auto, connected at full.
Also should i turn on multicast filtering
" Direct multicast packets to only those portions of the network where they are needed. This improves network performance in networks using the IGMP protocol with high levels of multicast traffic. "
"
Also should i turn on multicast filtering
" Direct multicast packets to only those portions of the network where they are needed. This improves network performance in networks using the IGMP protocol with high levels of multicast traffic. "
"
please try to use wireshark to capture that traffic. you can also show it here, but please check that there were no passwords captured.
multicast filtering will help only if you have multicast traffic within your network. in most cases you don't
multicast filtering will help only if you have multicast traffic within your network. in most cases you don't
ASKER
will do. thanks for the response.
you can do that. you have to enable them globally first:
http://www.windowsnetworking.com/articles_tutorials/Configuring-Disk-Quotas-Windows-2003.html
http://www.windowsnetworking.com/articles_tutorials/Configuring-Disk-Quotas-Windows-2003.html
I advise you to assign different VLANs to each subnet.