- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2018 06:43 PM - edited 03-08-2019 02:43 PM
See attached packet tracer diagram.
Not quite sure what is going on here go 3 issues.
1. So the Interconnect Sw Primary is not able to ping the directly connected InterRt Primary.
2. Access Sw 1 can't ping any other sub intefaces on directly connected router, but can ping designated mgmt sub interface which is the 0.0.0.0 route.
3. What is best summary statement to put on router for static route to ALL 192.168.X ?
See configs below - left no applicable configs out as configs pretty basic excluding HSRP.
InterConSw_Prim#
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
description Trunk2_InterRt_Prim
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/2
!
interface Vlan1
no ip address
shutdown
!
interface Vlan251
mac-address 000c.cf26.8702
ip address 192.168.251.7 255.255.255.0
!
interface Vlan252
mac-address 000c.cf26.8701
ip address 192.168.252.7 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.251.10
=====================================================
InterRt_Prim#
interface GigabitEthernet0/0/0
description Link2_Sw0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0/0.10
encapsulation dot1Q 10
ip address 10.10.10.1 255.255.255.0
!
interface GigabitEthernet0/0/0.12
encapsulation dot1Q 12
ip address 10.10.12.1 255.255.255.0
!
interface GigabitEthernet0/0/0.14
encapsulation dot1Q 14
ip address 10.10.14.1 255.255.255.0
!
interface GigabitEthernet0/0/0.252
description NE_Mgmt
encapsulation dot1Q 252
ip address 192.168.252.2 255.255.255.0
standby 1 ip 192.168.252.1
standby preempt
standby 0 track GigabitEthernet0/0/1
!
interface GigabitEthernet0/0/1
description Link2_FW
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0/1.251
encapsulation dot1Q 251
ip address 192.168.251.2 255.255.255.0
standby 2 ip 192.168.251.1
standby 2 preempt
standby 0 track GigabitEthernet0/0/1
!
interface GigabitEthernet0/0/1.252
encapsulation dot1Q 252
no ip address
!
interface Vlan1
no ip address
shutdown
!
ip classless
ip route 192.168.250.0 255.255.255.0 192.168.252.5
ip route 192.168.180.0 255.255.255.0 192.168.252.5
ip route 0.0.0.0 0.0.0.0 192.168.252.7
!
ip flow-export version 9
===================================================
ServerAccSw#
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
description Link2_Rt0
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/2
description Link2_Sw1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface Vlan1
no ip address
shutdown
!
interface Vlan180
mac-address 0001.c9cc.0e04
ip address 192.168.180.1 255.255.255.0
!
interface Vlan200
mac-address 0001.c9cc.0e03
ip address 192.168.200.1 255.255.255.0
!
interface Vlan250
mac-address 0001.c9cc.0e02
ip address 192.168.250.1 255.255.255.0
!
interface Vlan252
description NEMgmt
mac-address 0001.c9cc.0e01
ip address 192.168.252.5 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.252.1
!
ip flow-export version 9
!
!
!
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2018 11:01 AM
@CiscoBrownBelt wrote:
Ok after shutting down SVI252 on the INterconnSw now I can ping the .252 interface on the InterRt.
Any idea why? I would like to still use a .252 subnet on all devices or at least the INteronSw.
See below graphic - when you try and ping the Gi0/0/0 vlan 252 interface on the router from the switch, the source IP used will be the switch's vlan 252 IP Address (this will fail as you saw in your debug as you are spanning a vlan across router interfaces). When you shutdown the switch's vlan 252 interface and try the ping again it is successful because the source IP will be one of the switch's non-vlan 252 interfaces. Have a look at my previous post on configuring bridging on the router.
hth
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2018 12:19 PM
With vPC, you still need to create an HSRP instance per vlan and give each SVI a unique IP address.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2018 07:02 PM - edited 04-19-2018 07:04 PM
Hi
Also have you created the VLAN 251 and 252 on the Interconnect SW Primary? It can be verified through: show vlan brief or set up the following:
switch
conf t
vlan 251
vlan 252
Now I see some static routes but I think they dont have the proper next hop.
>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2018 06:11 AM
Yes I created those.
I have the ports that connect to the InterRt as switchport access vlan 251 and not trunk and ping works pinging from the Intercon to InterRt but InterRt can't ping the SVIs on the Intercon Sw.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2018 06:16 AM
Hi
Could you please share the following output from both devices?:
show ip int brief
Thank you in advance.
>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 05:57 AM - edited 04-21-2018 10:27 AM
Ok so I have the InterconSw as trunk g0/1 which connects directly to g0/0/1 of InterRt.
InterRt can ping only 251.7 but not 252.7 SVI on the InterConSw
InterCon Sw can only ping the directly connected interface g0/0/1 251.1, 2 but no other subinterfaces (g0/0/0.10 10.1, 12.1) which connects to AccessSw 1.
See configs - I also attached another screenshot of the topology.
InterConSw_Prim#sh ip int br
Interface IP-Address OK? Method Status Protocol
FastEthernet0/1 unassigned YES unset down down
FastEthernet0/2 unassigned YES unset down down
FastEthernet0/3 unassigned YES unset down down
FastEthernet0/4 unassigned YES unset down down
FastEthernet0/5 unassigned YES unset down down
FastEthernet0/6 unassigned YES unset down down
FastEthernet0/7 unassigned YES unset down down
FastEthernet0/8 unassigned YES unset down down
FastEthernet0/9 unassigned YES unset down down
FastEthernet0/10 unassigned YES unset down down
FastEthernet0/11 unassigned YES unset down down
FastEthernet0/12 unassigned YES unset down down
FastEthernet0/13 unassigned YES unset down down
FastEthernet0/14 unassigned YES unset down down
FastEthernet0/15 unassigned YES unset down down
FastEthernet0/16 unassigned YES unset down down
FastEthernet0/17 unassigned YES unset down down
FastEthernet0/18 unassigned YES unset down down
FastEthernet0/19 unassigned YES unset down down
FastEthernet0/20 unassigned YES unset down down
FastEthernet0/21 unassigned YES unset down down
FastEthernet0/22 unassigned YES unset down down
FastEthernet0/23 unassigned YES unset down down
FastEthernet0/24 unassigned YES unset down down
GigabitEthernet0/1 unassigned YES unset up up
GigabitEthernet0/2 unassigned YES unset up up
Vlan1 unassigned YES unset administratively down down
Vlan251 192.168.251.7 YES manual up up
Vlan252 192.168.252.7 YES manual up up
InterConSw_Prim#ping 192.168.251.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.251.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/1 ms
InterConSw_Prim#ping 192.168.251.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.251.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
InterConSw_Prim#ping 192.168.251.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.251.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms
InterConSw_Prim#ping 10.10.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
InterConSw_Prim#ping 10.10.12.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.12.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
!
interface GigabitEthernet0/1
description Trunk2_InterRt_Prim
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/2
!
interface Vlan1
no ip address
shutdown
!
interface Vlan251
mac-address 000c.cf26.8701
ip address 192.168.251.7 255.255.255.0
!
interface Vlan252
mac-address 000c.cf26.8702
ip address 192.168.252.7 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.251.10
!
ip flow-export version 9
=========================================================
InterRt_Prim#sh ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES unset up up
GigabitEthernet0/0/0.1010.10.10.1 YES manual up up
GigabitEthernet0/0/0.1210.10.12.1 YES manual up up
GigabitEthernet0/0/0.1410.10.14.1 YES manual up up
GigabitEthernet0/0/0.252192.168.252.2 YES manual up up
GigabitEthernet0/0/1 unassigned YES unset up up
GigabitEthernet0/0/1.251192.168.251.2 YES manual up up
GigabitEthernet0/0/1.252unassigned YES unset up up
Loopback1 1.1.1.1 YES manual up up
Vlan1 unassigned YES unset administratively down down
InterRt_Prim#ping 192.168.251.7
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.251.7, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
InterRt_Prim#ping 192.168.252.7
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.252.7, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
interface GigabitEthernet0/0/0
description Link2_Sw0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0/0.10
encapsulation dot1Q 10
ip address 10.10.10.1 255.255.255.0
!
interface GigabitEthernet0/0/0.12
encapsulation dot1Q 12
ip address 10.10.12.1 255.255.255.0
!
interface GigabitEthernet0/0/0.14
encapsulation dot1Q 14
ip address 10.10.14.1 255.255.255.0
!
interface GigabitEthernet0/0/0.252
description NE_Mgmt
encapsulation dot1Q 252
ip address 192.168.252.2 255.255.255.0
standby 1 ip 192.168.252.1
standby preempt
standby 0 track GigabitEthernet0/0/1
!
interface GigabitEthernet0/0/1
description Link2_FW
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0/1.251
encapsulation dot1Q 251
ip address 192.168.251.2 255.255.255.0
standby 2 ip 192.168.251.1
standby 2 preempt
standby 0 track GigabitEthernet0/0/1
!
interface GigabitEthernet0/0/1.252
encapsulation dot1Q 252
no ip address
!
interface Vlan1
no ip address
shutdown
!
ip classless
ip route 192.168.250.0 255.255.255.0 192.168.252.5
ip route 192.168.180.0 255.255.255.0 192.168.252.5
ip route 0.0.0.0 0.0.0.0 192.168.252.7
!
ip flow-export version 9
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 06:04 AM
Also, what is best way to summarize or enter a route statement if I want to point all traffic for
192.168.180.X, 200.X, 250.X ?
How about is I want a statement for everthing in the 192.168.X.X networks would it be
192.168.0.0 255.255.0.0 (Exit interface or IP e.g. 192.168.252.5)?
Here is the config for the AccessSw on the topology.
ServerAccSw#sh ip int br
Interface IP-Address OK? Method Status Protocol
FastEthernet0/1 unassigned YES unset up up
FastEthernet0/2 unassigned YES unset up down
FastEthernet0/3 unassigned YES unset down down
FastEthernet0/4 unassigned YES unset down down
FastEthernet0/5 unassigned YES unset down down
FastEthernet0/6 unassigned YES unset down down
FastEthernet0/7 unassigned YES unset down down
FastEthernet0/8 unassigned YES unset down down
FastEthernet0/9 unassigned YES unset down down
FastEthernet0/10 unassigned YES unset down down
FastEthernet0/11 unassigned YES unset down down
FastEthernet0/12 unassigned YES unset down down
FastEthernet0/13 unassigned YES unset down down
FastEthernet0/14 unassigned YES unset down down
FastEthernet0/15 unassigned YES unset down down
FastEthernet0/16 unassigned YES unset down down
FastEthernet0/17 unassigned YES unset down down
FastEthernet0/18 unassigned YES unset down down
FastEthernet0/19 unassigned YES unset down down
FastEthernet0/20 unassigned YES unset down down
FastEthernet0/21 unassigned YES unset down down
FastEthernet0/22 unassigned YES unset down down
FastEthernet0/23 unassigned YES unset down down
FastEthernet0/24 unassigned YES unset down down
GigabitEthernet0/1 unassigned YES unset up up
GigabitEthernet0/2 unassigned YES unset up up
Vlan1 unassigned YES unset administratively down down
Vlan180 192.168.180.1 YES manual up up
Vlan200 192.168.200.1 YES manual up up
Vlan250 192.168.250.1 YES manual up up
Vlan252 192.168.252.5 YES manual up up
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
description Link2_Rt0
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/2
description Link2_Sw1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface Vlan1
no ip address
shutdown
!
interface Vlan180
mac-address 0001.c9cc.0e01
ip address 192.168.180.1 255.255.255.0
!
interface Vlan200
mac-address 0001.c9cc.0e02
ip address 192.168.200.1 255.255.255.0
!
interface Vlan250
mac-address 0001.c9cc.0e03
ip address 192.168.250.1 255.255.255.0
!
interface Vlan252
description NEMgmt
mac-address 0001.c9cc.0e04
ip address 192.168.252.5 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.252.1
!
ip flow-export version 9
!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2018 06:54 AM
Pinging using trunk ports on the intercom sw works now, but not pinging between VLAN252 subnets.
I don't get it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2018 06:57 AM
Sorry to summarize, both Prim and Sec InterRouters can ping the SVI for 251 on the Interonn sw, the InterconSw can ping all Subinterfaces but the .252.X subinterfaces on the InterRouters which is HSRP.
Did you see my HSRP configs? Am I missing something? 251.X is configured for HSRP as well but all those IPs ping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 09:57 AM
Can you post a diagram and put all the IPs on the interfaces and point out which ones you can ping and which ones you can't?
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 10:26 AM
Sure here is the diagram.
The configs are in the reply above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 01:44 PM
Sorry there is typo on the diagram. It is g0/0/1.251 192.168.251.1 on the InnerRt Prim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 11:48 AM
Hi
You don't have an IP Address on your InterRouter's Gi0/0.1.252 sub-interface. Can you try adding the following:
interface GigabitEthernet0/0/1.252
encapsulation dot1Q 252
no ip address
ip unnumbered GigabitEthernet0/0/0.252
hth
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 01:18 PM
I already have an IP on g0/0/0.252 192.168.252.1 (Standby 1) which is a sub-interface that connects to the access switch so I can't.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 01:24 PM
Hi
Apply the command "ip unnumbered GigabitEthernet0/0/0.252" under subinterface Gi0/0.1.252 not under Gi0/0.0.252)
From Cisco document:
The IP unnumbered interface configuration enables IP processing on an interface without assigning an IP address to the interface. The IP unnumbered interface borrows an IP address from another interface that is already configured on the device to conserve network and address space
hth
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2018 01:36 PM
Looks like packet tracer ISR 4321 does not support that.
Do you think an actual ISR4000 series (4431, etc) will support that? This is probably why it is not working right?
