Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About metuckness
04-30-2019
Stats
Member since
01-09-2014
92
Posts
0
Helpful
0
Solutions
04-23-2019
09:52 AM
Thank you very much. Finally, a straight forward example with configuration examples worked for me, thank you!
... View more
05-10-2018
06:58 AM
@metuckness wrote:
@Reza Sharifi wrote:
So, where is the host in vlan 113 located (what switch and what port)?
What is its IP address?
Is that static IP or DHCP?
Can that host ping its gateway ( 192.168.113.6) ?
It is located on the 3850. interface TenGigabitEthernet1/0/24, but they are all on the 113 subnet on the 3850, so far anyway, I haven't put any on the 116.
It's IP is statically assigned (as most are on that Subnet). 192.168.113.29 specifically.
@That host is what I am using on a daily basis. Yes it can ping the gateway (192.168.113.6) it can even ping the router @ 10.10.10.1, I can't get to any other 10.10.10.0/24 I add to a port.
What I don't get is the switches can ping 10.10.10.1 and 10.10.10.2. The router can ping 10.10.10.2.
No other ideas? Anyone?
... View more
05-09-2018
02:04 PM
@Reza Sharifi wrote:
So, where is the host in vlan 113 located (what switch and what port)?
What is its IP address?
Is that static IP or DHCP?
Can that host ping its gateway ( 192.168.113.6) ?
It is located on the 3850. interface TenGigabitEthernet1/0/24, but they are all on the 113 subnet on the 3850, so far anyway, I haven't put any on the 116.
It's IP is statically assigned (as most are on that Subnet). 192.168.113.29 specifically.
@That host is what I am using on a daily basis. Yes it can ping the gateway (192.168.113.6) it can even ping the router @ 10.10.10.1, I can't get to any other 10.10.10.0/24 I add to a port.
What I don't get is the switches can ping 10.10.10.1 and 10.10.10.2. The router can ping 10.10.10.2.
... View more
05-09-2018
01:36 PM
@Reza Sharifi wrote:
But in this case, the statement basically says, to get to
192.168.113.0 255.255.255.0 go to 192.168.100.251 while 192.168.113.0 is a connected interface.
The 2800 is routing to itself?
Also, physically, does the 3750 connect to the 3850 and then the 3850 to 2800?
HTH
I removed this statement from the 2911 router to see if it made a difference, it doesn't seem to have made a difference.
ip route 192.168.113.0 255.255.255.0 192.168.100.251
The 3850 has an LACP team attached to the 3750 stack. The 3750 is connected to the 2911 router.
I am not sure about the statement "routing to itself" can you clairify? Thanks!
... View more
05-09-2018
01:15 PM
@Reza Sharifi wrote:
Got it. Thanks for the clarification.
ip route 192.168.113.0 255.255.255.0 192.168.100.251
192.168.113.0 255.255.255.0 is a connected interface. Is there a reason for this statement?
HTH
ip route 192.168.113.0 255.255.255.0 192.168.100.251
This is a route statement for traffic from the 113 VLAN to be routed to another locations subnet once a year for video traffic. They turn the circuit on, the route allows us to monitor their camera feeds and once they are finished the circuit is turned off.
... View more
05-09-2018
12:56 PM
@Reza Sharifi wrote:
I don't see any 10.10.10.2 address in your config.
Also, do the clients in 192.168.113.0 subnet have the correct gateway?
What switch do these clients connect to?
HTH
I am not sure I understand the question.
Yes the 113 Subnet client have the correct gateway 192.168.113.6 (on the router config).
All the switches have the 113 and 116 and 10 vlans.
You will not see the 10.10.10.2 IP in the switches and routers config, it is a PC attached to the 3750 stack on port 4/0/1.
... View more
05-09-2018
12:32 PM
I am trying to get a VLAN added to my network, and I am unable to get clients from one VLAN to Ping the new VLAN I added. I can ping the address assigned to the Routers Virtual Interface, but I cannot ping clients behind that.
From the switches, I can ping clients behind the router.
So a switch can ping 10.10.10.1 (gateway, IP assigned to the router) and 10.10.10.2 A client PC attached to the 10.10.10.0 Subnet, but a client PC assigned to 192.168.113.0 subnet cannot ping 10.10.10.2, but can ping 10.10.10.1.
I will post the configurations to the switches and routers, trying to remove some of the settings to reduce the length.
Router (2911):
Building configuration... Current configuration : 5257 bytes no ipv6 cef ip source-route ip cef ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.0.0.102 255.255.255.252 ip helper-address 192.168.116.240 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address duplex auto speed auto ! interface GigabitEthernet0/1.10 encapsulation dot1Q 10 ip address 10.10.10.1 255.255.255.0 ip helper-address 10.10.10.2 ! interface GigabitEthernet0/1.113 encapsulation dot1Q 113 ip address 192.168.113.6 255.255.255.0 ip helper-address 192.168.100.1 ! interface GigabitEthernet0/1.116 encapsulation dot1Q 116 ip address 192.168.116.1 255.255.255.0 ip helper-address 192.168.100.1 ! interface GigabitEthernet0/2 ip address 10.0.0.42 255.255.255.252 duplex auto speed auto ! interface GigabitEthernet0/0/0 no ip address shutdown duplex auto speed auto ! ip forward-protocol nd ! ip route 0.0.0.0 0.0.0.0 192.168.116.251 ip route 10.4.0.0 255.255.240.0 192.168.113.227 ip route 10.231.2.0 255.255.255.0 192.168.116.3 ip route 10.231.5.0 255.255.255.0 192.168.116.3 ip route 172.22.0.0 255.255.0.0 192.168.113.245 ip route 172.23.140.0 255.255.255.0 192.168.113.245 ip route 192.168.2.0 255.255.255.0 192.168.113.1 ip route 192.168.3.0 255.255.255.0 192.168.113.1 ip route 192.168.6.0 255.255.255.0 192.168.113.1 ip route 192.168.100.0 255.255.255.0 10.0.0.41 ip route 192.168.101.0 255.255.255.0 10.0.0.41 ip route 192.168.105.0 255.255.255.0 10.0.0.41 ip route 192.168.107.0 255.255.255.0 10.0.0.41 ip route 192.168.108.0 255.255.255.0 10.0.0.41 ip route 192.168.109.0 255.255.255.0 10.0.0.41 ip route 192.168.113.0 255.255.255.0 192.168.100.251 ip route 192.168.114.0 255.255.255.0 10.0.0.41 ip route 192.168.118.0 255.255.255.0 10.0.0.41 ip route 192.168.151.0 255.255.255.0 10.0.0.101 ip route 192.168.159.0 255.255.255.0 10.0.0.41 ip route 192.168.200.0 255.255.255.0 10.0.0.41 !
Switch 3850:
Building configuration... boot-start-marker boot-end-marker ! ! vrf definition Mgmt-vrf ! address-family ipv4 exit-address-family ! ip routing ! ! quit diagnostic bootup level minimal spanning-tree mode rapid-pvst spanning-tree extend system-id hw-switch switch 1 logging onboard message level 3 ! redundancy mode sso ! ! ! class-map match-any non-client-nrt-class ! policy-map port_child_policy class non-client-nrt-class bandwidth remaining ratio 10 ! ! interface Port-channel3 description 20GB LACP to 3750 Stack switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate ! interface TenGigabitEthernet1/0/7 description Uplink to 3750 Stack switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate channel-group 3 mode desirable non-silent spanning-tree portfast trunk !
! interface TenGigabitEthernet1/0/8 description Uplink to 3750 Stack switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate channel-group 3 mode desirable non-silent spanning-tree portfast trunk
!
!
interface Vlan1 no ip address shutdown ! interface Vlan10 ip address 10.10.10.247 255.255.255.0 ip helper-address 10.10.10.2 ! interface Vlan113 ip address 192.168.113.247 255.255.255.0 ip helper-address 192.168.116.240 ! interface Vlan116 ip address 192.168.116.247 255.255.255.0 ip helper-address 192.168.116.240 ! ip route 0.0.0.0 0.0.0.0 192.168.113.6 !
Switch 3750:
Current configuration : 26895 bytes ! aaa session-id common stacks scan-lite switch 1 provision ws-c3750x-48 switch 2 provision ws-c3750x-48 switch 3 provision ws-c3750x-48 switch 4 provision ws-c3750x-48 system mtu routing 1500 ip routing quit ! spanning-tree mode pvst spanning-tree extend system-id no spanning-tree vlan 112-113 ! ! ! ! vlan internal allocation policy ascending ! ! interface Port-channel3 description LACP to 3850 Fiber switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate ! interface FastEthernet0 no ip address no ip route-cache cef no ip route-cache ! interface GigabitEthernet1/0/1 switchport trunk encapsulation dot1q switchport trunk allowed vlan 1,10,113,116,151 switchport mode trunk spanning-tree portfast ! interface TenGigabitEthernet2/1/1 description Uplink to FIBER Switch switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate spanning-tree portfast trunk channel-group 3 mode auto ! interface TenGigabitEthernet2/1/2 description Uplink to FIBER Switch switchport trunk encapsulation dot1q switchport trunk allowed vlan 10,113,116 switchport mode trunk switchport nonegotiate spanning-tree portfast trunk channel-group 3 mode auto ! interface GigabitEthernet4/0/1 switchport access vlan 10 switchport mode access ! interface GigabitEthernet4/0/45 description CONNECTED TO MGMNT PORT ASA5516 switchport access vlan 116 switchport mode access ! interface Vlan1 no ip address ! interface Vlan10 ip address 10.10.10.253 255.255.255.0 ip helper-address 10.10.10.2 ! interface Vlan113 ip address 192.168.113.253 255.255.255.0 ip helper-address 192.168.100.1 ! interface Vlan116 ip address 192.168.116.253 255.255.255.0 ip helper-address 192.168.100.1 ! interface Vlan151 ip address 192.168.151.253 255.255.255.0 ip helper-address 192.168.116.240 ! ip http server ip http secure-server end
... View more
Labels:
05-08-2018
01:52 PM
I changed the Subnet from 128.192 to 10.10.10.0/24 to avoid any publically addressable IP Subnets.
... View more
05-08-2018
05:17 AM
@Georg Pauwen wrote:
Hello,
what is the default gateway of your clients in VLAN 168 ?
The addressing looks odd, unless it is on purpose:
interface GigabitEthernet0/1.168 encapsulation dot1Q 168 ip address 168.192.1.1 255.255.255.0 ip helper-address 168.192.1.2
Are you sure it doesn't have to be 192.168.1.1 and 192.168.1.2 ?
The schema is on purpose.
Devices on the 168.192.1.0/24 would use 168.192.1.1 as their gateway. The router would send everything not explicitly routed somewhere else to that, which is a Firewall connected to fiber and the internet.
ip route 0.0.0.0 0.0.0.0 192.168.116.251
... View more
05-07-2018
02:50 PM
@Georg Pauwen wrote:
Hello,
is your 2911 doing the routing for the other VLANs as well ? Post the full config of your 2911...
Yes it is.
Current configuration : 5409 bytes ! version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption service sequence-numbers ! ! boot-start-marker boot-end-marker ! ! logging buffered 51200 warnings ! no aaa new-model ! no ipv6 cef ip source-route ip cef ! ! ! ! ! multilink bundle-name authenticated ! ! 3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030 31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274 69666963 6174652D 32363837 33343531 3930301E 170D3132 30333038 32313033 2A864886 F70D0101 05050003 81810039 F87D9F4E AACA1C33 C5B648D7 187C6557 31A927BF 5F1913BA 2B72F90F 76C84BFD A1B65543 51E25F19 02F9BC88 FBA09107 8D05BDCA 4E90A235 0E4DF373 F03233A4 83F62D6E DE787BA7 50576620 D3A91B0C A996B043 EC4CD37D 43B36500 3CCEA1A3 FA85B7CA 903D9E40 8EE2FEBB 462F1132 69C59F35 B567B6CF DDEE86B7 635EDD quit ! ! ! ! ! ! ! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.0.0.102 255.255.255.252 ip helper-address 192.168.116.240 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address duplex auto speed auto ! interface GigabitEthernet0/1.113 encapsulation dot1Q 113 ip address 192.168.113.6 255.255.255.0 ip helper-address 192.168.100.1 ! interface GigabitEthernet0/1.116 encapsulation dot1Q 116 ip address 192.168.116.1 255.255.255.0 ip helper-address 192.168.100.1 ! interface GigabitEthernet0/1.168 encapsulation dot1Q 168 ip address 168.192.1.1 255.255.255.0 ip helper-address 168.192.1.2 ! interface GigabitEthernet0/2 ip address 10.0.0.42 255.255.255.252 ip helper-address 192.168.100.1 duplex auto speed auto ! interface GigabitEthernet0/0/0 no ip address shutdown duplex auto speed auto ! ! ! ip forward-protocol nd ! ! ip route 0.0.0.0 0.0.0.0 192.168.116.251 ip route 10.4.0.0 255.255.240.0 192.168.113.227 ip route 10.231.2.0 255.255.255.0 192.168.116.3 ip route 10.231.5.0 255.255.255.0 192.168.116.3 ip route 168.192.1.0 255.255.255.0 168.192.1.253 ip route 172.22.0.0 255.255.0.0 192.168.113.245 ip route 172.23.140.0 255.255.255.0 192.168.113.245 ip route 192.168.2.0 255.255.255.0 192.168.113.1 ip route 192.168.3.0 255.255.255.0 192.168.113.1 ip route 192.168.6.0 255.255.255.0 192.168.113.1 ip route 192.168.100.0 255.255.255.0 10.0.0.41 ip route 192.168.101.0 255.255.255.0 10.0.0.41 ip route 192.168.105.0 255.255.255.0 10.0.0.41 ip route 192.168.107.0 255.255.255.0 10.0.0.41 ip route 192.168.108.0 255.255.255.0 10.0.0.41 ip route 192.168.109.0 255.255.255.0 10.0.0.41 ip route 192.168.113.0 255.255.255.0 192.168.100.251 ip route 192.168.113.0 255.255.255.0 168.192.1.252 ip route 192.168.113.0 255.255.255.0 168.192.1.253 ip route 192.168.114.0 255.255.255.0 10.0.0.41 ip route 192.168.118.0 255.255.255.0 10.0.0.41 ip route 192.168.151.0 255.255.255.0 10.0.0.101 ip route 192.168.159.0 255.255.255.0 10.0.0.41 ip route 192.168.200.0 255.255.255.0 10.0.0.41 ! ! ! ! control-plane ! ! ! ! scheduler allocate 20000 1000 end
... View more
05-07-2018
01:23 PM
Hi Everyone,
I could use some help with routing traffic over a new VLAN I added to my network. A quick rundown of the network.
I have a VLAN 113 that is my primary VLAN. I also have a 116 for admin. I don't want the 116 to have access to the 168 VLAN, so it is not mentioned much. I added another VLAN to the switches as VLAN168.
I have a 3850 Switch running 10GBT Fiber. That switch has a teamed LACP pair (Port-Channel) running to a 3750 that has the additional 10GB Fiber addons.
That port-channel group has this configuration:
3750 Group:
interface Port-channel3 description LACP to 3850 Fiber switchport trunk encapsulation dot1q switchport trunk allowed vlan 113,116,168 switchport mode trunk switchport nonegotiate
3850 Group:
interface Port-channel3 description 20GB LACP to 3750 Stack switchport trunk allowed vlan 113,116,168 switchport mode trunk switchport nonegotiate
The VLAN's have been enabled and assigned to ports.
The VLAN Configurations are:
3750:
interface Vlan168 ip address 168.192.1.253 255.255.255.0
3850:
interface Vlan168 ip address 168.192.1.252 255.255.255.0
I have no additional route statements on the 3750. From the switches, currently, I can ping the 168.192.1.1 address on the router,and I can ping a PC connected to a port assigned to the 168 VLAN with an IP of 168.192.1.2.
I can ping 168.192.1.1 from PC's on the 113 VLAN, but I cannot ping anything beyond that, so I cannot ping 168.192.1.2 from the 113 or 116 VLAN's.
The 2911 Router has a couple of routes I tried, but so far not much luck:
ip route 168.192.1.0 255.255.255.0 168.192.1.253
ip route 192.168.113.0 255.255.255.0 168.192.1.252
ip route 192.168.113.0 255.255.255.0 168.192.1.253
This is the 2911's Interface where the VLAN comes into it:
interface GigabitEthernet0/1.168 encapsulation dot1Q 168 ip address 168.192.1.1 255.255.255.0
Any suggestions on what I am missing to get PC's on the 113 VLAN to ping and access beyond the IP assigned to the 2911 Routers interface?
Thanks!
... View more
Labels:
05-03-2018
11:20 AM
So far it looks like it was a driver issue. I was able to locate a new driver for the card and updated it. So far, every test I have done with considerable transfers has completed without dropping network entirely. I think that might have solved the issue. It never occurred to me to update the drivers. Thanks!
... View more
04-25-2018
12:36 PM
@ITexpert wrote:
I have some questions before saying anything .
Did you test this scenario by connecting some other PC or laptop to same switch ?
If this happen with all the computers or PCs connected with this switch only but not PCs connected with other switch, that means nothing to do with NAS.
But if this is happening with only your PC but not with remaining devices then try updating network drivers.
Thanks,
Lovejit
Will do. I am doing some testing now to see. the other PC's don't ever really transfer large files so they haven't encountered it yet. But I will do some testing to see and also check f there are new drivers for the 10GB cards.
Will post an update.
... View more
04-24-2018
07:00 AM
@Reza Sharifi wrote:
Jumbo frame should be 9216. On the 3850, this is a global command and you have to reboot the switch for it to take effect. Also, enabling jumbo frame should not have the effect on any hosts.
HTH
The highest I can go is: <1500-9198> MTU size in bytes
... View more
04-23-2019
Thank you very much. Finally, a straight forward example with
configuration examples worked for me, ...
05-10-2018
@metuckness wrote: @Reza Sharifi wrote: So, where is the host in vlan
113 located (what switch and w...
05-09-2018
@Reza Sharifi wrote: So, where is the host in vlan 113 located (what
switch and what port)? What is ...
05-09-2018
@Reza Sharifi wrote: But in this case, the statement basically says, to
get to 192.168.113.0 255.255...
05-09-2018
@Reza Sharifi wrote: Got it. Thanks for the clarification. ip route
192.168.113.0 255.255.255.0 192....
05-09-2018
@Reza Sharifi wrote: I don't see any 10.10.10.2 address in your config.
Also, do the clients in 192....
05-09-2018
I am trying to get a VLAN added to my network, and I am unable to get
clients from one VLAN to Ping ...
Created by
metuckness
in Switching
05-08-2018
05-08-2018
I changed the Subnet from 128.192 to 10.10.10.0/24 to avoid any
publically addressable IP Subnets.
Created by
metuckness
in Switching
05-08-2018
05-08-2018
@Georg Pauwen wrote: Hello, what is the default gateway of your clients
in VLAN 168 ? The addressing...
Created by
metuckness
in Switching
05-07-2018
05-07-2018
@Georg Pauwen wrote: Hello, is your 2911 doing the routing for the other
VLANs as well ? Post the fu...
05-07-2018
Hi Everyone, I could use some help with routing traffic over a new VLAN
I added to my network. A qui...
Created by
metuckness
in Switching
05-03-2018
05-03-2018
So far it looks like it was a driver issue. I was able to locate a new
driver for the card and updat...
Created by
metuckness
in Switching
04-25-2018
04-25-2018
@ITexpert wrote: I have some questions before saying anything . Did you
test this scenario by connec...
Created by
metuckness
in Switching
04-24-2018
04-24-2018
@Reza Sharifi wrote: Jumbo frame should be 9216. On the 3850, this is a
global command and you have ...
Public Statistics
| Date Registered | 01-09-2014 08:47 AM |
| Date Last Visited | 04-30-2019 09:53 AM |
| Total Messages Posted | 92 |
.jpg "VIP Mentor"){kind=icon}
