network issues
Hello guys,
I have a network setup and facing few problems in it. would appreciate if anyone can give some suggestion in improving it.
Devices
Core Switch = 4506-E
Access Switches = 2960
Connectivity
all access switches connected to core using single 1G fiber uplink.
Management
Vlan 100,
Core Switch = 192.168.100.1/24
Access Switches = 192.168.100.5/24 onwards
Data (internet)
vlans used 10 to 30
each vlan for 5 access switches
vlan 10 = 192.168.10.0/24 to vlan 30 = 192.168.30.0/24
DHCP Pools configured on Core Switch
default router for different vlans configured on the core switch (192.168.10.1, 192.168.11.1 .... 192.168.30.1)
default gateway configured on all access switches is 192.168.100.1 (management-ip address of core), should i keep this as a default gateway or should i change it to according to vlan (for example if access switch is in vlan 10, ip default gateway 192.168.10.1) ?
dhcp snooping is configured, spanning tree port fast configured, storm control configured
Problem
1) when connect computer to any access switch port, i face few packet drops after every 20 to 25 responses.
2) from the core side when i try to telnet any access switch, some switches take 3 to 4 tries to respond. if i ping them they will not respond, will use show mac address command, will not be able to see mac of the switch on management vlan. after 3 to 4 tries i will get ping response and will be able to telnet and will be able to see mac on that core switch port. what can be the reason for this issue ?
any suggestions for improving the network ? anything else i can implement on it ?
thank you
I have a network setup and facing few problems in it. would appreciate if anyone can give some suggestion in improving it.
Devices
Core Switch = 4506-E
Access Switches = 2960
Connectivity
all access switches connected to core using single 1G fiber uplink.
Management
Vlan 100,
Core Switch = 192.168.100.1/24
Access Switches = 192.168.100.5/24 onwards
Data (internet)
vlans used 10 to 30
each vlan for 5 access switches
vlan 10 = 192.168.10.0/24 to vlan 30 = 192.168.30.0/24
DHCP Pools configured on Core Switch
default router for different vlans configured on the core switch (192.168.10.1, 192.168.11.1 .... 192.168.30.1)
default gateway configured on all access switches is 192.168.100.1 (management-ip address of core), should i keep this as a default gateway or should i change it to according to vlan (for example if access switch is in vlan 10, ip default gateway 192.168.10.1) ?
dhcp snooping is configured, spanning tree port fast configured, storm control configured
Problem
1) when connect computer to any access switch port, i face few packet drops after every 20 to 25 responses.
2) from the core side when i try to telnet any access switch, some switches take 3 to 4 tries to respond. if i ping them they will not respond, will use show mac address command, will not be able to see mac of the switch on management vlan. after 3 to 4 tries i will get ping response and will be able to telnet and will be able to see mac on that core switch port. what can be the reason for this issue ?
any suggestions for improving the network ? anything else i can implement on it ?
thank you
Comments
-
EdTheLad Member Posts: 2,111 ■■■■□□□□□□Some configs would be nice, your management network is vlan 100 so the DG on the switches is correct 192.168.100.1.Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
-
mistabrumley89 Member Posts: 356 ■■■□□□□□□□What type of fiber cables are you using? SM or MM? Are your GBICS SM or MM? Not really enough to go on here, but just a couple basic things you can verify. Management VLAN should be fine to configure on your access switches. Can give us a copy of the log? Are ports flapping?Goals: WGU BS: IT-Sec (DONE) | CCIE Written: In Progress
LinkedIn: www.linkedin.com/in/charlesbrumley -
razam Member Posts: 39 ■■□□□□□□□□fiber cable single mode, GBICs also single mode.. ports are not flapping
please follow this post, same case..
http://www.techexams.net/forums/ccnp/95845-packet-drops.html -
tearofs Member Posts: 112Use Wireshark or Tcpdump(Linux) to track what's going on behind the scenes.
-
EdTheLad Member Posts: 2,111 ■■■■□□□□□□I would actively encourage real network problems as opposed to how does this protocol work, after all that's why we are studying in the first place t be able to fix real networking issues. Also relevant for diagnostics section on new ccie v5.Networking, sometimes i love it, mostly i hate it.Its all about the $$$$