- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 4108GL IP Routing slow
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2011 08:04 PM
12-26-2011 08:04 PM
4108GL IP Routing slow
Hello,
we use a Procurve 4108GL as backbone switch. Our LAN is seperated into four subnets which should be routed by the Procurve. Our problem is that routing between the subnets is extremly slow, we got ping resonses between 5 and 100ms, sometime even ping drops. CPU Utilization is about 20%.
Following the configuration of the ProCurve...
Regards,
Steve
es-mdf-cs01# show run
Running configuration:
; J4865A Configuration Editor; Created on release #G.07.109
hostname "es-mdf-cs01" cdp run module 1 type J4893A module 2 type J4862B module 3 type J4893A module 4 type J4862B module 8 type J4863A module 5 type J4862B interface A1 no lacp exit interface A2 no lacp exit interface A3 disable no lacp exit interface A4 no lacp exit interface A5 no lacp exit interface A6 disable no lacp exit interface B1 no lacp exit interface B2 no lacp exit interface B3 no lacp exit interface B4 no lacp exit interface B5 no lacp exit interface B6 no lacp exit interface B7 no lacp exit interface B8 no lacp exit interface B9 no lacp exit interface B10 no lacp exit interface B11 no lacp exit interface B12 no lacp exit interface B13 no lacp exit interface B14 no lacp exit interface B15 no lacp exit interface B16 no lacp exit interface B17 no lacp exit interface B18 no lacp exit interface B19 no lacp exit interface B20 no lacp exit interface B21 no lacp exit interface B22 no lacp exit interface B23 no lacp exit interface B24 no lacp exit interface C1 no lacp exit interface C2 no lacp exit interface C3 no lacp exit interface C4 disable no lacp exit interface C5 no lacp exit interface C6 no lacp exit interface D1 no lacp exit interface D2 no lacp exit interface D3 no lacp exit interface D4 no lacp exit interface D5 no lacp exit interface D6 no lacp exit interface D7 no lacp exit interface D8 no lacp exit interface D9 no lacp exit interface D10 no lacp exit interface D11 no lacp exit interface D12 no lacp exit interface D13 no lacp exit interface D14 no lacp exit interface D15 no lacp exit interface D16 no lacp exit interface D17 no lacp exit interface D18 no lacp exit interface D19 no lacp exit interface D20 no lacp exit interface D21 no lacp exit interface D22 no lacp exit interface D23 no lacp exit interface D24 no lacp exit interface H1 no lacp exit interface H2 no lacp exit interface H3 no lacp exit interface H4 no lacp exit interface H5 no lacp exit interface H6 no lacp exit interface E1 no lacp exit interface E2 no lacp exit interface E3 no lacp exit interface E4 no lacp exit interface E5 no lacp exit interface E6 no lacp exit interface E7 no lacp exit interface E8 no lacp exit interface E9 no lacp exit interface E10 no lacp exit interface E11 no lacp exit interface E12 no lacp exit interface E13 no lacp exit interface E14 no lacp exit interface E15 no lacp exit interface E16 no lacp exit interface E17 no lacp exit interface E18 no lacp exit interface E19 no lacp exit interface E20 no lacp exit interface E21 no lacp exit interface E22 no lacp exit interface E23 no lacp exit interface E24 no lacp exit ip default-gateway 172.16.1.1 sntp server 64.16.211.38 sntp server 172.16.1.8 sntp server 172.16.1.4 ip routing logging facility syslog logging 172.16.1.4 snmp-server community "public" Unrestricted vlan 1 name "DEFAULT_VLAN" forbid A1,C3-C4 untagged A2,A4-A6,B1-B24,C1-C2,C5-C6,D1-D24,E2-E24,H1-H5 ip address 172.16.1.1 255.255.248.0 no untagged A1,A3,C3-C4,E1,H6 ip igmp exit vlan 2 name "ITClub" forbid A1 untagged C4,E1 no ip address ip helper-address 172.16.1.8 tagged C3,H4 ip igmp exit vlan 100 name "WAN_Routing" untagged A1,A3,C3 ip address 172.31.255.1 255.255.255.0 ip igmp exit vlan 99 name "CIPA_Filter" forbid C4 untagged H6 ip address 192.168.255.254 255.255.255.0 tagged E1 ip igmp exit vlan 10 name "Wireless" forbid A1,C3-C4 ip address 172.16.8.1 255.255.248.0 ip helper-address 172.16.1.8 tagged A5,H4 ip igmp 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 ip route 172.18.0.0 255.255.0.0 172.31.255.2 ip route 172.17.0.0 255.255.0.0 172.31.255.3 ip route 0.0.0.0 0.0.0.0 192.168.255.1 ip route 172.19.0.0 255.255.0.0 172.31.255.3 ip route 172.15.0.0 255.255.0.0 172.31.255.3 no stack auto-join spanning-tree priority 1 password manager