I have a Cisco 3750 connected to another Cisco 3750 via media converted fibre link.
Near side switch:
Current configuration : 2508 bytes
no service pad
service timestamps debug uptime
service timestamps log datetime
no service password-encryption
ip host X 172.16.0.2
ip name-server 188.8.131.52
ip name-server 202.x.x.x
ip name-server 184.108.40.206
ip name-server 202.x.x.x
vtp mode transparent
cluster enable laptop 0
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
vlan access-map word 1
switchport access vlan 2
switchport mode access
ip address 192.168.0.33 255.255.255.0 secondary
ip address 10.108.108.1 255.255.252.0 secondary
ip address 192.168.192.2 255.255.255.252 secondary
ip address 192.168.20.20 255.255.255.0 secondary
ip address 192.168.10.9 255.255.255.0
ip address 172.16.0.1 255.255.0.0
no ip address
ip route 0.0.0.0 0.0.0.0 192.168.0.27
ip route 10.1.0.0 255.255.0.0 172.16.0.2
ip route 10.250.6.0 255.255.255.0 192.168.192.1
ip route 57.8.x.x.x.x.x.108.108.10
ip route 192.168.5.7 255.255.255.255 192.168.10.10
ip http server
ip access-list standard TEST10SUBNET
ip access-list extended CMP-NAT-ACL
dynamic Cluster-HSRP deny ip any any
dynamic Cluster-NAT permit ip any any
ip access-list extended TEST
permit ip any any
line con 0
line vty 0 4
line vty 5 15
We have created a seperate VLAN on both switches in order to set primary addresses of both on the 172.16.x.x network, and handle all routing internal to the switches. From the near side switch I am able to ping all remote networks.
On a host on VLAN1 on the near side switch, I can ping 172.16.0.1 which is an address on VLAN2 but not the far end of the fibre link or any other host on the far end of the link. If I trace to 172.16.0.1 it lists 1 hop directly to 172.16.0.1. If I trace to 172.16.0.2 I go to 192.168.10.9 and then the trace carries on for a few hops and gets lost. How can I get full transparency between networks?
I would start by adding the following routes to the far side router:
ip route 192.168.0.33 255.255.255.0 172.16.0.1
ip route 10.108.108.1 255.255.252.0 172.16.0.1
ip route 192.168.192.2 255.255.255.252 172.16.0.1
ip route 192.168.20.20 255.255.255.0 172.16.0.1
ip route 192.168.10.9 255.255.255.0 172.16.0.1
Hope that helps - pls rate the post if it does.
Actually, the above may or may not work.
Since you are using distinct subnets for each VLAN, I would suggest that you not use the same VLAN IDs on each side.. On the far side router, you should configure the 172.16.0.2 address under interface VLAN2. Remove the subnets from VLAN2 into a new VLAN. In addition, change VLAN1 to be some VLAN ID that you are not using elsewhere.
Thanks for the prompt response.
Just for clarification:
Far side router is using 172.16.x.x in VLAN3. Near side router is using 172.16.x.x in VLAN2.
Why would I be able to ping 172.16.0.1 which is effectively in VLAN 2 on the near router from a host on the near routers VLAN 1 but nothing else.
Apparently far side router is able to ping 172.16.0.1 which is VLAN 2 on near router from a server 10.1.1.10 which is a far network!
Default gateway on remote network is set to an ISA box which is probably performing routing. No other layer device is available near side of the link.
Once again, thank you!
Answer to your first question: the switch knows exactly how to get to 172.16.0.1 since it's a directly connected address.
As for your second question, it's a bit hard to answer without understanding what the rest of your network looks like ... Have you got a network diagram you could post ?
I'm afraid I'm not able to open that file.. it seems to be referencing some other files that are not there..
Would you be able to paste it into a Word document ?
Now, are you in a position to make any changes to the switches ? If so, we can start doing stuff on a step-by-step basis...
I will have direct access to the near side router: the far side router is another company. Its an extranet situation. I can certainly forward change requests as needs be. Access is being configured as we speak, but probably won't happen before COB, so I hope we can continue this conversation tomorrow (I am in NZ). Thank you so much for your help.
Just one more thing before you go.. Is the link between the two 3750s configured as a trunk ? Can you post the output of 'show interfaces trunk'
I'm in Brisbane, by the way...
Oh okay.. that kinda changes the whole story..
So Gig1/0/21 from the near-side switch is connected to Gig0/16 on the other side, right ?
That explains a few things...
One thing you can quicky do is to add the following static route to the far-end switch:
ip route 192.168.0.0 255.255.255.0 172.16.0.1
Then, try to ping 172.16.0.2 from one of the hosts on the 192.168.0.x network...
Hope that helps - pls do remember to rate posts..
I referred back to your original post to finish it off. We have asked the remote site to implement, and tests look okay.