Solved: Sorry I mean RIP wipe out the

dbrill001 · ‎09-22-2015

What I have currently is two buildings each with a Catalyst which routes traffic to all the different Vlans with RIP. These two buildings are connected through a MAN.

This is what I need to do. I had fiber run and I have the hardware. I need to hook the two buildings up to the faster connection. I have tried to do this already but building number 1's RIP info over wrote the Vlan table of Building number two's RIP info.

Can I just recreate the Vlans from building number two on building number one's catalyst and remove them from building building number two's catalyst then hook up the fiber line and have it all work?

Jon Marshall · ‎09-22-2015

If each switch has it's own vlans and IP subnets and you route for all traffic between the switches then make the link a L3 routed link and then you can't possibly overwrite the vlan database.

So use an unused IP subnet with a /30 subnet mask. As you are using network 10.0.0.0 under RIP choose it from this.

Then configure the ports on either end with one of the IPs from that subnet eg.

int <x/y>
no switchport
ip address 10.x.x.x 255.255.255.252

this will work fine as long as you do not need to extend any vlans/IP subnets between your switches.

Does this make sense ?

If it is still unclear please come back for clarification.

Jon

View solution in original post

devils_advocate · ‎09-22-2015

I am a little confused.

Do you actually mean VLAN or do you mean routing table?

VLAN is a Layer 2 concept and RIP is a Layer 3 Routing protocol.

dbrill001 · ‎09-22-2015

Sorry I mean RIP wipe out the VLAN database and put the VLAN database from Catalyst 1.

devils_advocate · ‎09-22-2015

I am still confused.

RIP has nothing to do with the VLAN database.

RIP is the Routing Information Protocol and (if configured) will dynamically learn routes from neighbor routers which are also configured for RIP. No VLAN information is contained within RIP exchanges.

The VLAN database is local to each LAN.

Are you sure you are using RIP between the Switches in each building?

The only way one switch could overwrite the VLAN database of another is if you were using VTP (Vlan trunking protocol).

You need to clarify what you mean.

dbrill001 · ‎09-22-2015

To be honest that is why I am on here I assume it is RIP and we are using VLAN Trunking Protocol. To me it I thought it was RIP sorry. So what is the best way for connecting these? We do use RIP.

devils_advocate · ‎09-22-2015

I would guess that VTP is the culprit if a new switch has overwritten the Vlan database of an existing switch.

Its going to depend on the current setup.

We need to know if you are Routing between the buildings or whether it is a Layer 2 topology.

Can you post the results of the following commands on the existing (i.e old switch) that is still left in building 2:

#show ip protocols
#show ip route

Thanks

dbrill001 · ‎09-22-2015

This is building 1 (2103)

2103Catalyst#show ip prot
2103Catalyst#show ip protocols
*** IP Routing is NSF aware ***

Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 27 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
    Interface             Send Recv Triggered RIP Key-chain
    Vlan1                 2     2
    Vlan9                 2     2
    Vlan10                2     2
    Vlan21                2     2
    Vlan22                2     2
    Vlan23                2     2
    Vlan25                2     2
    Vlan30                2     2
    Vlan31                2     2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
    10.0.0.0
Routing Information Sources:
    Gateway         Distance      Last Update
    10.10.30.2           120      00:00:13
Distance: (default is 120)

2103Catalyst#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       + - replicated route, % - next hop override

Gateway of last resort is 10.10.30.2 to network 0.0.0.0

S*    0.0.0.0/0 [1/0] via 10.10.30.2
      10.0.0.0/8 is variably subnetted, 27 subnets, 2 masks
R        10.10.0.0/24 [120/1] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.1.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
C        10.10.9.0/24 is directly connected, Vlan9
L        10.10.9.1/32 is directly connected, Vlan9
C        10.10.10.0/24 is directly connected, Vlan10
L        10.10.10.1/32 is directly connected, Vlan10
R        10.10.11.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.12.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.13.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.14.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.20.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
C        10.10.21.0/24 is directly connected, Vlan21
L        10.10.21.1/32 is directly connected, Vlan21
C        10.10.22.0/24 is directly connected, Vlan22
L        10.10.22.1/32 is directly connected, Vlan22
C        10.10.23.0/24 is directly connected, Vlan23
L        10.10.23.1/32 is directly connected, Vlan23
C        10.10.25.0/24 is directly connected, Vlan25
L        10.10.25.1/32 is directly connected, Vlan25
C        10.10.30.0/24 is directly connected, Vlan30
L        10.10.30.1/32 is directly connected, Vlan30
C        10.10.31.0/24 is directly connected, Vlan31
L        10.10.31.1/32 is directly connected, Vlan31
R        10.10.40.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
R        10.10.50.0/24 [120/2] via 10.10.30.2, 00:00:22, Vlan30
C        10.135.169.0/24 is directly connected, Vlan1
L        10.135.169.22/32 is directly connected, Vlan1
      216.237.225.0/27 is subnetted, 1 subnets
R        216.237.225.224 [120/1] via 10.10.30.2, 00:00:22, Vlan30
2103Catalyst#

This is building 2 (2080)

2080Catalyst#show ip pro
2080Catalyst#show ip protocols
*** IP Routing is NSF aware ***

Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 25 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
    Interface             Send Recv Triggered RIP Key-chain
    Vlan1                 2     2
    Vlan11                2     2
    Vlan12                2     2
    Vlan13                2     2
    Vlan14                2     2
    Vlan20                2     2
    Vlan50                2     2
    Vlan100               2     2
    Vlan245               2     2
    FastEthernet0         2     2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
    10.0.0.0
Routing Information Sources:
    Gateway         Distance      Last Update
    10.10.0.20           120      00:00:06
    10.10.0.40           120      00:00:20
Distance: (default is 120)

2080Catalyst#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       + - replicated route, % - next hop override

Gateway of last resort is 10.10.30.2 to network 0.0.0.0

S*    0.0.0.0/0 [1/0] via 10.10.30.2
      10.0.0.0/8 is variably subnetted, 26 subnets, 2 masks
C        10.10.0.0/24 is directly connected, Vlan245
L        10.10.0.30/32 is directly connected, Vlan245
C        10.10.1.0/24 is directly connected, Vlan1
L        10.10.1.1/32 is directly connected, Vlan1
R        10.10.9.0/24 [120/1] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.10.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
C        10.10.11.0/24 is directly connected, Vlan11
L        10.10.11.1/32 is directly connected, Vlan11
C        10.10.12.0/24 is directly connected, Vlan12
L        10.10.12.1/32 is directly connected, Vlan12
C        10.10.13.0/24 is directly connected, Vlan13
L        10.10.13.1/32 is directly connected, Vlan13
C        10.10.14.0/24 is directly connected, Vlan14
L        10.10.14.1/32 is directly connected, Vlan14
C        10.10.20.0/24 is directly connected, Vlan20
L        10.10.20.1/32 is directly connected, Vlan20
R        10.10.21.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.22.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.23.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.25.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.30.0/24 [120/1] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.31.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
R        10.10.40.0/24 [120/1] via 10.10.0.40, 00:00:01, Vlan245
C        10.10.50.0/24 is directly connected, Vlan50
L        10.10.50.1/32 is directly connected, Vlan50
R        10.135.169.0/24 [120/2] via 10.10.0.20, 00:00:17, Vlan245
      216.237.225.0/27 is subnetted, 1 subnets
R        216.237.225.224 [120/1] via 10.10.0.20, 00:00:17, Vlan245
2080Catalyst#show ip protocols

devils_advocate · ‎09-22-2015

OK so it looks like RIP is running between the buildings.

What state are you in now?
Have you replaced one switch or both of them with new ones?

dbrill001 · ‎09-22-2015

Last night i backed out and disconnected the fiber link restored the 2080 switch to an old config and connected back to the the MAN.

I am trying to plan my next option.

Jon Marshall · ‎09-22-2015

Can you just clarify what it is you want to do.

Currently you have two switches each routing for it's own vlans and then exchanging those routes between each other.

Do you want to simply change to a new link but keep the same setup or are you looking to move all the L3 interfaces for the vlans to just one of the switches ?

If you simply want to keep the existing setup with the new link can you post -

1) the current configuration of the link at both ends

2) the configuration you used for the new connection

Jon

dbrill001 · ‎09-22-2015

We want to take use the new fiber 10Gb/s connection and take away the 20Mb/s connection. If we can leave both ends routing to their perspective VLANs great otherwise what do we need to do to have the fiber connection inplace with all the VLANs

Jon Marshall · ‎09-22-2015

You should just be able to use the new link ie. no change in the routing.

But something obviously went wrong.

As has been pointed out if your vlan database is overwritten that is nothing to do with RIP, it is more likely to do with VTP.

That is why I asked about how the connection between the switches was configured for the existing link and the new link ie.

a L2 link could create the problem you saw whereas as a L3 link wouldn't.

So if you could provide details of how the existing link is configured and how you configured the new link that may help us work out what went wrong.

Jon

dbrill001 · ‎09-22-2015

Here is the config and I just simply plugged the fiber into interface TenGigabitEthernet1/1 and interface TenGigabitEthernet1/2

2103Catalyst#show run
Building configuration...

Current configuration : 8837 bytes
!
! Last configuration change at 21:52:41 UTC Mon Sep 21 2015 by admin
! NVRAM config last updated at 09:56:33 UTC Sat Sep 19 2015 by admin
!
version 15.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname 2103Catalyst
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$n5/d$k3mGjmmMyhytaNLpoEjiQ0
!
username admin privilege 15 password 7 00201A1401581F545F791C
no aaa new-model
clock timezone UTC -5 0
clock summer-time UTC recurring
system mtu routing 1500
authentication mac-move permit
ip routing
no ip dhcp conflict logging
!
!
ip domain-name GD.COM
ip name-server 10.10.10.14
ip name-server 10.10.10.15
ip device tracking
!
mls qos map cos-dscp 0 8 16 24 32 46 48 56
!
crypto pki trustpoint TP-self-signed-4259500672
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-4259500672
revocation-check none
rsakeypair TP-self-signed-4259500672
!
!
crypto pki certificate chain TP-self-signed-4259500672
certificate self-signed 01
30820244 308201AD A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 34323539 35303036 3732301E 170D3933 30333031 30303031
32325A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 32353935
30303637 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100BD5D E5E9FB57 1ACA8B69 C15BB060 2BEE13CB 0C8BA35C 8386DF55 57B5F7F4
514663B2 09444026 612E589D EEFF3C3E 968651A5 094A215A 9454FB50 5EEE8AD2
608C10C0 99281818 75170B7C 69DDFD73 11E60E22 5840139A 30F26BFA 739387B9
57CEA114 A18F7BBE 35AC7164 2B525A7A 939D35F5 E626EA08 B678F812 F4E5B8EE
93D50203 010001A3 6C306A30 0F060355 1D130101 FF040530 030101FF 30170603
551D1104 10300E82 0C50464D 61696E53 77697463 68301F06 03551D23 04183016
80140E2F 0356A874 0AE8DFE4 1988A7CF 788D2113 804A301D 0603551D 0E041604
140E2F03 56A8740A E8DFE419 88A7CF78 8D211380 4A300D06 092A8648 86F70D01
01040500 03818100 692DBE76 BE5C3D7F FE9DF342 01BBBD3D 2C9D6E3F 5F7ED916
28FA16DB A6506D7E 07A323C1 17D3A289 DB781CCB BF48277E 219B4756 B5E24404
5E0FF80F 7EB6A633 BFE38822 3B230B2D 543BE382 525EFDDA 82BBFB5E DD082EAE
4C323615 CE63A070 33862FBB 911CCC6A A583386E 5D19D93F 05D29CB4 A0D2D0BD
6D38BBD0 88865213
quit
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
!
!
!
!
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
!
!
!
!
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport trunk allowed vlan 9,10
switchport mode trunk
!
interface Port-channel2
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport trunk allowed vlan 21,25
switchport mode trunk
!
interface Port-channel3
switchport trunk encapsulation dot1q
switchport trunk native vlan 22
switchport trunk allowed vlan 22,25
switchport mode trunk
!
interface Port-channel4
switchport trunk encapsulation dot1q
switchport trunk native vlan 23
switchport trunk allowed vlan 23,25
switchport mode trunk
!
interface Port-channel5
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 25,30
switchport mode trunk
!
interface Port-channel6
switchport trunk encapsulation dot1q
switchport trunk native vlan 31
switchport trunk allowed vlan 25,31
switchport mode trunk
!
interface Port-channel7
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0
no ip address
no ip route-cache
!
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport trunk allowed vlan 9,10
switchport mode trunk
channel-group 1 mode active
!
interface GigabitEthernet0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport trunk allowed vlan 9,10
switchport mode trunk
channel-group 1 mode active
!
interface GigabitEthernet0/3
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport trunk allowed vlan 21,25
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/4
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport trunk allowed vlan 21,25
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/5
switchport trunk encapsulation dot1q
switchport trunk native vlan 22
switchport trunk allowed vlan 22,25
switchport mode trunk
channel-group 3 mode active
!
interface GigabitEthernet0/6
switchport trunk encapsulation dot1q
switchport trunk native vlan 22
switchport trunk allowed vlan 22,25
switchport mode trunk
channel-group 3 mode active
!
interface GigabitEthernet0/7
switchport trunk encapsulation dot1q
switchport trunk native vlan 23
switchport trunk allowed vlan 23,25
switchport mode trunk
channel-group 4 mode active
!
interface GigabitEthernet0/8
switchport trunk encapsulation dot1q
switchport trunk native vlan 23
switchport trunk allowed vlan 23,25
switchport mode trunk
channel-group 4 mode active
!
interface GigabitEthernet0/9
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 25,30
switchport mode trunk
channel-group 5 mode active
!
interface GigabitEthernet0/10
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 25,30
switchport mode trunk
channel-group 5 mode active
!
interface GigabitEthernet0/11
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 25,30
switchport mode trunk
channel-group 5 mode active
!
interface GigabitEthernet0/12
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 25,30
switchport mode trunk
channel-group 5 mode active
!
interface GigabitEthernet0/13
switchport trunk encapsulation dot1q
switchport trunk native vlan 31
switchport trunk allowed vlan 25,31
switchport mode trunk
channel-group 6 mode active
!
interface GigabitEthernet0/14
switchport trunk encapsulation dot1q
switchport trunk native vlan 31
switchport trunk allowed vlan 25,31
switchport mode trunk
channel-group 6 mode active
!
interface GigabitEthernet0/15
!
interface GigabitEthernet0/16
!
interface GigabitEthernet0/17
!
interface GigabitEthernet0/18
!
interface GigabitEthernet0/19
!
interface GigabitEthernet0/20
!
interface GigabitEthernet0/21
!
interface GigabitEthernet0/22
switchport trunk encapsulation dot1q
switchport trunk native vlan 9
switchport mode trunk
macro description cisco-router
!
interface GigabitEthernet0/23
!
interface GigabitEthernet0/24
switchport mode access
switchport port-security
switchport port-security aging time 2
switchport port-security violation restrict
switchport port-security aging type inactivity
macro description cisco-desktop
spanning-tree portfast
spanning-tree bpduguard enable
!
interface GigabitEthernet1/1
!
interface GigabitEthernet1/2
!
interface GigabitEthernet1/3
!
interface GigabitEthernet1/4
!
interface TenGigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface TenGigabitEthernet1/2
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface Vlan1
ip address 10.135.169.22 255.255.255.0
!
interface Vlan9
description DMZ
ip address 10.10.9.1 255.255.255.0
!
interface Vlan10
description ServerRoom
ip address 10.10.10.1 255.255.255.0
!
interface Vlan21
description FrontOffice
ip address 10.10.21.1 255.255.255.0
ip helper-address 10.10.10.14
!
interface Vlan22
description Cave
ip address 10.10.22.1 255.255.255.0
ip helper-address 10.10.10.14
!
interface Vlan23
description Mezzanine
ip address 10.10.23.1 255.255.255.0
ip helper-address 10.10.10.14
!
interface Vlan25
description Wireless
ip address 10.10.25.1 255.255.255.0
ip helper-address 10.10.10.14
!
interface Vlan30
description Print Room
ip address 10.10.30.1 255.255.255.0
ip helper-address 10.10.10.14
!
interface Vlan31
description Print&Frame
ip address 10.10.31.1 255.255.255.0
ip helper-address 10.10.10.14
!
router rip
version 2
network 10.0.0.0
no auto-summary
!
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
!
ip route 0.0.0.0 0.0.0.0 10.10.30.2
!
!
ip sla enable reaction-alerts
access-list 10 permit 10.10.10.12
!
snmp-server community Pictures RO
!
!
line con 0
password 7 072B285E4B0A0D57474A5B
line vty 0 4
password 7 072B285E4B0A0D57474A5B
login local
length 0
line vty 5 15
password 7 00201A1401581F545F791C
login
!
!
monitor session 1 source interface Gi0/2
monitor session 1 destination interface Gi0/14
ntp server 10.10.10.10
ntp server winservices.gd.com
end

Jon Marshall · ‎09-22-2015

What do you mean you plugged it into both 10Gbps ports ie. it is only a single connection ?

What port does the existing link use ?

Or did you simply reuse the same ports ?

Do these two switches share any vlans/IP subnets or does each switch only have unique vlans/IP subnets ?

It's difficult to help without the full information.

Jon

dbrill001 · ‎09-22-2015

What do you mean you plugged it into both 10Gbps ports ie. it is only a single connection ?

Yes, Just got the fiber run between the buildings. Just bought the fiber hardware.

What port does the existing link use ?

The existing connection uses a Cat5 connection to a media converter that goes to the ISP on both ends.

Do these two switches share any vlans/IP subnets or does each switch only have unique vlans/IP subnets ?

Each Switch has its own subnets and VLANs.

Vlans, Fiber, and RIP