BROCADE IP PRIMER

49F Link 50FPower11F 2F 3F 4F32Console5476981110131215141716191821202322252427262928313033323534373639384140434245444746 4849F Link 50FPower11F 2F 3F 4F32Console5476981110131215141716191821202322252427262928313033323534373639384140434245444746 4849F Link 50FPower11F 2F 3F 4F32Console5476981110131215141716191821202322252427262928313033323534373639384140434245444746 48The Routing TableHmm...Well, Switch C definitely knows how to get to 172.18.0.0/16, but itdoesn't know how to get back to 172.16.0.0/16. I think we're going to have totell it.BR-SwitchC#conf tBR-SwitchC(config)#ip route 172.16.0.0 255.255.0.0192.168.2.2Notice here again that we used the IP address of Switch B. Switch C doesn'tknow how to get to 192.168.1.0/30. We chose a gateway we knew Switch Ccould reach.That's fixed it, right? Let's send that ping again!Switch AICMP Echo Host Ce1192.168.1.1/30?Switch BICMP Echo Host Ce2192.168.2.2/30Switch CICMP Echo Host Cve 10172.16.0.1/24e1192.168.1.2/30ve 20172.17.0.1/24ICMP Echo-Reply Host Ae1192.168.2.1/30ICMPEcho ReplyHost AICMP Echo Host Cve 30172.18.0.1/24Host A172.16.0.10/24Host B172.17.0.10/24Host C172.18.0.10/24We still didn't get a reply? Nuts! Let's look at the diagram. Hmm... It seems tohave stopped at Switch B this time. What was Switch B's routing table again?BR-SwitchB#show ip routeTotal number of IP routes: 4Start index: 1 B:BGP D:Connected R:RIP S:Static O:OSPF*:Candidate defaultDestination NetMask Gateway Port Cost Type1 192.168.1.0 255.255.255.252 0.0.0.0 1 1 D2 192.168.2.0 255.255.255.252 0.0.0.0 2 1 D3 172.17.0.0 255.255.0.0 0.0.0.0 v20 1 D4 172.18.0.0 255.255.0.0 192.168.2.1 2 1 SWell, well. It seems Switch B doesn't know how to get to 172.16.0.0/16 either!Whew! This is getting hard. Okay, well, let's tell Switch B how to get there.BR-SwitchB#conf tBR-SwitchB(config)#ip route 172.16.0.0 255.255.0.0192.168.1.1Now, will it work? Shall I try another ping from Host A to Host C? I'm afraid tolook!Brocade IP Primer 225