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 Ariya Amirjalali
Stats
Member since
04-14-2016
7
Posts
0
Helpful
0
Solutions
Created by
Ariya Amirjalali
in Switching
in Switching
10-03-2017
03:06 PM
10-03-2017
03:06 PM
Hey Guys, I have an issue that I cant find a solution for. I'm implementing VLANs on our network but DHCP is the issue. So for now I have VLAN 32 and 100. Both can talk to each other through the router policy. VLAN 32 receives IPs from (Windows Server 2016) POOL 1, but VLAN 100 does not receive IPs from POOL 2. It receives from POOL 1 and ignores the pool 2. DHCP relay agent is on the switch. The DHCP traffic gets to the DHCP server but it gets it from the wrong pool. And this is driving me crazy since I have been doing everything right. VLAN 32 172.16.32.1/24 VLAN 100 172.16.100.1/24 Any suggestions???
... View more
Labels:
09-25-2016
12:30 AM
Yea sorry about that.
So ca n you explain why it doesn't work if you don't use "source loopback" when pinging?
... View more
09-24-2016
11:35 AM
Hello Deepak,
I'm running OSPF on R2 and R3 so no need for static routes.
R1#ping 192.168.33.1 source loopback 1 ... did actually work.
Can you explain why it doesnt work as ping 192.168.33.1 but when you use source loopback, it will actually ping, I guess that made me confused
... View more
09-24-2016
11:24 AM
I did have routes for both, I did traceroute and it looks like it drops it at R2
... View more
09-23-2016
11:18 PM
Hey guys,
I have a problem with this topology, I'm new to BGP so I'm trying to understand this.
(R1)
ip route 192.168.2.2 255.255.255.255 209.165.202.130
router bgp 65100 bgp log-neighbor-changes network 209.165.200.224 mask 255.255.255.224 neighbor 192.168.2.2 remote-as 65000 neighbor 192.168.2.2 ebgp-multihop 255 neighbor 192.168.2.2 update-source Loopback0
(R2)
ip route 209.165.201.1 255.255.255.255 209.165.202.129
router bgp 65000 bgp log-neighbor-changes network 192.168.22.0 neighbor 192.168.3.3 remote-as 65000 neighbor 192.168.3.3 update-source Loopback0 neighbor 192.168.3.3 next-hop-self neighbor 209.165.201.1 remote-as 65100 neighbor 209.165.201.1 ebgp-multihop 255 neighbor 209.165.201.1 update-source Loopback0
(R3)
router bgp 65000 bgp log-neighbor-changes network 192.168.33.0 neighbor 192.168.2.2 remote-as 65000 neighbor 192.168.2.2 update-source Loopback0
The thing I dont understand is that R1 and R2 can ping each other but R1 and R3 can't Both R1 and R3 have entrees in the bgp table for each other but wont ping each other.
Can someone explain why?
... View more
Labels:
04-14-2016
01:16 AM
I came across this question and I'm having trouble understanding it. "What are the steps towards isolating a dynamic routing loop in a mixed static/dynamic environment?"
... View more
- Tags:
- #ccna #ccnp
Labels:
Created by
Ariya Amirjalali
in Switching
10-03-2017
10-03-2017
Hey Guys,I have an issue that I cant find a solution for. I'm
implementing VLANs on our network but ...
09-25-2016
Yea sorry about that. So can you explain why it doesn't work if you
don't use "source loopback" when...
09-24-2016
Hello Deepak, I'm running OSPF on R2 and R3 so no need for static
routes. R1#ping 192.168.33.1 sourc...
09-23-2016
Hey guys, I have a problem with this topology, I'm new to BGP so I'm
trying to understand this. (R1)...
Public Statistics
| Date Registered | 04-14-2016 01:13 AM |
| Date Last Visited | 08-03-2018 03:00 AM |
| Total Messages Posted | 7 |
.jpg "VIP Advisor"){kind=icon}
