Below you will find examples of my work, this includes some of my designs developed for anything from small to large customers, troubleshooting scenarios and much more.
|
Static Redistribution Woes with OSPF
This scenario was a support call where my routing expertise was called upon. The external peer router was receiving the route 10.99.16.0/20 from an unknown source and they was unable to correctly route traffic to the 10.99.23.0/24 network, it was being sent to 10.99.26.0/24 instead.
I began my investigation on the FortiGate firewall in area 1, checking the routing table with the command get router info routing-table all to see the gateway of the 10.99.16.0/20 route. Traffic was being directed out the IPSec tunnel. I quickly checked the area 1 core switch to see that the route was in fact being advertised from the firewall and not a backbone link between the two sites, it was being advertised by the firewall.
After logging into the area 2 firewall I checked the routing table to see where the traffic was being routed to and it was the router ID of the core switch in area 2, I also had a look in the OSPF LSDB with the FortiGate command get router info ospf database brief, this shown me that the 10.99.16.0/20 route was an E2 route, it must have been coming from another protocol.
I logged into the core switch and firstly checked the OSPF configuration with the command show run router ospf (it was a HP comware switch), I could see that OSPF was enabled and advertising out the 10.99.26.0/24 network, fine. However it was also redistributing static. Checking through the config with show run | i ip route there was a static route for 10.99.16.0/20. This would be the cause of the incorrect routing that the peer was experiencing.
Once the route was removed the peer received the LSDB update immediately and they was able to reach the destination servers they needed to. The routing inter-sites was also now functioning correctly and not looping between sites.
I began my investigation on the FortiGate firewall in area 1, checking the routing table with the command get router info routing-table all to see the gateway of the 10.99.16.0/20 route. Traffic was being directed out the IPSec tunnel. I quickly checked the area 1 core switch to see that the route was in fact being advertised from the firewall and not a backbone link between the two sites, it was being advertised by the firewall.
After logging into the area 2 firewall I checked the routing table to see where the traffic was being routed to and it was the router ID of the core switch in area 2, I also had a look in the OSPF LSDB with the FortiGate command get router info ospf database brief, this shown me that the 10.99.16.0/20 route was an E2 route, it must have been coming from another protocol.
I logged into the core switch and firstly checked the OSPF configuration with the command show run router ospf (it was a HP comware switch), I could see that OSPF was enabled and advertising out the 10.99.26.0/24 network, fine. However it was also redistributing static. Checking through the config with show run | i ip route there was a static route for 10.99.16.0/20. This would be the cause of the incorrect routing that the peer was experiencing.
Once the route was removed the peer received the LSDB update immediately and they was able to reach the destination servers they needed to. The routing inter-sites was also now functioning correctly and not looping between sites.
Campus Core Switch Design
These designs were part of the documentation package provided to the customer upon completion of the core switch update and move. The core switch update design, implementation and testing was performed working alongside the customer to ensure that the results were what they expected every step of the way.
These diagrams detail the physical topology, the layer 3 topology and the spanning tree topology. The customer was looking for up to date and centralized documentation.
These diagrams detail the physical topology, the layer 3 topology and the spanning tree topology. The customer was looking for up to date and centralized documentation.