Mittwoch, 29. Juni 2011

bgp bestpath as-path ignore - Wow a hidden command to freak network engineers

Rack1SW1(config-router)#bgp bestpath ?
  compare-routerid  Compare router-id for identical EBGP paths
  cost-community    cost community
  med               MED attribute

Rack1SW1(config-router)#bgp bestpath as-path ignore
Rack1SW1(config-router)#end
Rack1SW1#sh run | i
*Mar  1 02:13:46.567: %SYS-5-CONFIG_I: Configured from console by console
Rack1SW1#sh run | incl ignore
 bgp bestpath as-path ignore <-- a command like test crash :D
Rack1SW1#

Rack1SW1#test crash
WARNING: Command selections marked with '(crash router)' will crash
         router when issued. However a selection 'C' will need to
         be issued IMMEDIATELY before these selections to enable them.


Type the number for the selected crash:
--------------------------------------
 1  (crash router) Bus Error, due to invalid address access
 2  (crash router) Bus Error, due to parity error in Main memory
 3  (crash router) Bus Error, due to parity error in I/O memory
 4  (crash router) Address Error, due to fetching code from odd address
 5  (crash router) Jump to zero
 6  (crash router) Software forced crash
 7  (crash router) Illegal read of address zero
 8  (crash router) Divide by zero
 9  (crash router) Corrupt memory
 A  (crash router) Test assert() failure
 C  Enable crash router selection marked with (crash router)
 P  (crash router) Test assert_production() failure
 R  (crash router) User enter read bus error address
 U  (crash router) User enter write bus error address
 W  (crash router) Software watchdog timeout (*** Watch Dog Timeout ***)
 w  (crash router) Process watchdog timeout (SYS-2-WATCHDOG)
 d  Disable crashinfo collection
 e  Enable crashinfo collection
 i  Display contents of current crashinfo flash file
 m  Write crashinfo on crashinfo RAM
 n  Change crashinfo flash file name
 q  Exit crash menu
 s  Save crashinfo to current crashinfo flash file
 c  Close current crashinfo flash file
 t  Write crashinfo on console TTY
 x  Exit crash menu
?

Donnerstag, 23. Juni 2011

INE WB Vol1 - 6.42 OSPF Database Filtering

Never seen this one in reallife :/


CoolRouter
router ospf 99
neighbor 1.2.3.4 database-filter all out
CoolSwitch:
interface Vlan12
ip ospf database-filter all out

Dienstag, 21. Juni 2011

INE WB Vol1 - 6.38 OSPF Summarization and Discard Routes

Rack1R5#sh ip route 150.1.2.2
Routing entry for 150.1.0.0/22
  Known via "ospf 1", distance 110, metric 65, type intra area
  Routing Descriptor Blocks:
  * directly connected, via Null0
      Route metric is 65, traffic share count is 1

Rack1R5#conf t 
Enter configuration commands, one per line.  End with CNTL/Z.
Rack1R5(config)#router ospf 1
Rack1R5(config-router)#no dis
Rack1R5(config-router)#no disca
Rack1R5(config-router)#no discard-route i
Rack1R5(config-router)#no discard-route internal
Rack1R5(config-router)#end
Rack1R5#sh ip route 150.
*Jun 21 13:19:52.114: %SYS-5-CONFIG_I: Configured from console by console
Rack1R5#sh ip route 150.1.2.2
% Subnet not in table
Rack1R5#sh ip route 150.1.2.2
% Subnet not in table
Rack1R5#sh ip route de
Rack1R5#sh ip route  
Codes: 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

Gateway of last resort is 155.1.45.4 to network 0.0.0.0

     51.0.0.0/32 is subnetted, 1 subnets
O E2    51.51.51.51 [110/20] via 155.1.0.2, 00:00:10, Serial0/0/0
O E2 204.12.1.0/24 [110/20] via 155.1.45.4, 00:00:10, Serial0/1/0
                   [110/20] via 155.1.0.4, 00:00:10, Serial0/0/0
     155.1.0.0/16 is variably subnetted, 19 subnets, 2 masks
O IA    155.1.146.0/24 [110/65] via 155.1.45.4, 00:00:10, Serial0/1/0
                       [110/65] via 155.1.0.4, 00:00:10, Serial0/0/0
                       [110/65] via 155.1.0.1, 00:00:10, Serial0/0/0
O IA    155.1.23.0/24 [110/128] via 155.1.0.2, 00:00:10, Serial0/0/0
O       155.1.10.0/24 [110/3] via 155.1.58.8, 00:00:10, FastEthernet0/0
O       155.1.8.0/24 [110/2] via 155.1.58.8, 00:00:10, FastEthernet0/0
O IA    155.1.9.0/24 [110/67] via 155.1.0.3, 00:00:10, Serial0/0/0
O IA    155.1.13.0/24 [110/128] via 155.1.0.1, 00:00:10, Serial0/0/0
         
Rack1R5#

Sonntag, 19. Juni 2011

INE WB Vol1 - 6.36 OSPF Reliable Conditional Default Routing

Hm... aha a placeholder-route to null0 with tracking-option and then match with a prefix-list on a route-map to originate the default route.


 But what the INE guys are missing that they don't state you can impelement a new IP subnet to the requirements.

My first try was to add a normal default-route to the backbone-device add a track statement on this route, and everything is fine !?!
A more "straightforward" solution thatn INE, it's not necessary to do it with a 169...-whatever !?!

What do you think ?

Freitag, 17. Juni 2011

[SOLVED] WTF ? OSPF FULL ROUTING = TROUBLESHOOTING LAB

AutoInstall Using Frame Relay

If the new router is connected by a Frame Relay-encapsulated serial interface, AutoInstall will send a BOOTP request over the lowest numbered serial or HSSI interface. (The attempt to run AutoInstall over Frame Relay is performed only after attempts are made using SLARP over HDLC, DHCP, and RARP.)

The broadcast BOOTP request sent by the new router will contain the MAC address of the new router's interface. The staging router should be configured to forward the request using a helper address. A DHCP or BOOTP server will then return the IP address assigned to that MAC address. (Note that either a DHCP or BOOTP service can respond to the BOOTP request.)

AutoInstall using Frame Relay can be initiated over only the first serial interface on the new router. Specifically, Autoinstall over Frame Relay can be initiated over Serial 0 (S0), or Serial 1/0 (S1/0). For example, if the new router has serial interfaces S1/0 through S1/3 and S4/0 through S4/3, AutoInstall will be attempted over S1/0 only and cannot be forced to be initiated from S4/0. If AutoInstall over S1/0 fails, an Frame Relay attempt will not be made from any other serial port.

Only a helper address and a Frame Relay map need to be configured on the staging router. No MAC-to-IP address map is needed on the staging router. For configuration details, see the "Configuring a Frame Relay-Encapsulated Serial Interface Connection" section.

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf002.html#wp1011965

http://blog.ine.com/2008/06/29/understanding-frame-relay-mappings-to-0000/


Nice one :)

WTF ? OSPF FULL ROUTING = TROUBLESHOOTING LAB

Rack1R2#debug frame-relay pack
*Mar  1 04:20:12.473: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.3.3 on Serial0/0 from EXSTART to DOWN, Neighbor Down: Too many retransmissions
Rack1R2#debug frame-relay pack
*Mar  1 04:21:12.475: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.3.3 on Serial0/0 from DOWN to DOWN, Neighbor Down: Ignore timer expired
Rack1R2#debug frame-relay pack
*Mar  1 04:22:32.498: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.3.3 on Serial0/0 from EXSTART to DOWN, Neighbor Down: Dead timer expired
Rack1R2#debug frame-relay packshow
Rack1R2#sh
*Mar  1 04:24:57.881: %OSPF-5-ADJCHG: Process 1, Nbr 150.1.3.3 on Serial0/0 from EXSTART to DOWN, Neighbor Down: Too many retransmissions

R3#
*Mar  1 04:25:23.947: Serial1/0(i): dlci 302(0x48E1), pkt type 0x800, datagramsize 88
*Mar  1 04:25:23.979: Serial1/0:Encaps failed--no map entry link 7(IP)
R3#

Rack1R3#show frame-relay map
Serial1/0 (up): ip 0.0.0.0 dlci 304(0x130,0x4C00)
              broadcast,
              CISCO, status defined, active
Serial1/0 (up): ip 0.0.0.0 dlci 302(0x12E,0x48E0)
              broadcast,
              CISCO, status defined, active
Serial1/0 (up): ip 0.0.0.0 dlci 301(0x12D,0x48D0)
              broadcast,
              CISCO, status defined, active
Serial1/0 (up): ip 155.1.0.5 dlci 305(0x131,0x4C10), static,
              broadcast,
              CISCO, status defined, active
Rack1R3#
Rack1R2#show frame-relay map
Serial0/0 (up): ip 0.0.0.0 dlci 213(0xD5,0x3450)
              broadcast,
              CISCO, status defined, inactive
Serial0/0 (up): ip 0.0.0.0 dlci 204(0xCC,0x30C0)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 203(0xCB,0x30B0)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 201(0xC9,0x3090)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 155.1.0.5 dlci 205(0xCD,0x30D0), static,
              broadcast,
              CISCO, status defined, active
Rack1R2#
*Mar  1 04:34:42.315: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:34:42.315: OSPF: End of hello processing
*Mar  1 04:34:42.795: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:34:42.795: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:34:43.721: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#
*Mar  1 04:34:44.751: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:34:44.755: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
Rack1R2#wr
Building configuration...

*Mar  1 04:34:48.425: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:34:48.425: OSPF: End of hello processing
*Mar  1 04:34:52.319: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:34:52.319: OSPF: End of hello processing
*Mar  1 04:34:52.796: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:34:52.796: OSPF: End of hello processing
*Mar  1 04:34:53.721: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
*Mar  1 04:34:54.751: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:34:54.755: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:34:55.685: OSPF: Rcv LS UPD from 150.1.5.5 on Serial0/0 length 56 LSA count 1
*Mar  1 04:34:55.737: OSPF: Rcv LS UPD from 150.1.5.5 on Serial0/0 length 56 LSA count 1
*Mar  1 04:34:55.793: OSPF: Rcv LS UPD from 150.1.5.5 on Serial0/0 length 84 LSA count 2
*Mar  1 04:34:57.431: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:34:57.431: OSPF: End of hello processing[OK]
Rack1R2#
*Mar  1 04:35:02.315: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:02.315: OSPF: End of hello processing
*Mar  1 04:35:02.796: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:02.796: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:03.722: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#
*Mar  1 04:35:04.751: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:04.755: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
Rack1R2#
*Mar  1 04:35:07.332: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:07.332: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:12.316: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:12.316: OSPF: End of hello processing
*Mar  1 04:35:12.805: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:12.809: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:13.722: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#
*Mar  1 04:35:14.752: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:14.756: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
Rack1R2#
*Mar  1 04:35:17.236: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:17.240: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:22.316: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:22.316: OSPF: End of hello processing
*Mar  1 04:35:22.809: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:22.809: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:23.722: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#
*Mar  1 04:35:24.752: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:24.756: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
Rack1R2#
*Mar  1 04:35:26.435: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:26.439: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:32.317: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:32.317: OSPF: End of hello processing
*Mar  1 04:35:32.966: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:32.966: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:35:33.723: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#
*Mar  1 04:35:34.753: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:34.757: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
Rack1R2#
*Mar  1 04:35:36.035: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:36.035: OSPF: End of hello processing
Rack1R2#debug f
*Mar  1 04:35:42.317: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:42.317: OSPF: End of hello processing
*Mar  1 04:35:42.970: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:42.970: OSPF: End of hello processing
Rack1R2#debug fram
Rack1R2#debug frame-relay packet
*Mar  1 04:35:43.723: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
Rack1R2#debug frame-relay packet
Frame Relay packet debugging is on
Rack1R2#
*Mar  1 04:35:44.753: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:44.757: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:35:45.735: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 96
*Mar  1 04:35:45.735: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:45.735: OSPF: End of hello processing
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#
*Mar  1 04:35:52.317: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:35:52.317: OSPF: End of hello processing
*Mar  1 04:35:52.970: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:35:52.974: OSPF: End of hello processing
Rack1R2#
Rack1R2#
*Mar  1 04:35:53.724: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
*Mar  1 04:35:54.753: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:35:54.757: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:35:54.757: Serial0/0: broadcast search
*Mar  1 04:35:54.757: Serial0/0: Broadcast on DLCI 204  link 7
*Mar  1 04:35:54.757: Serial0/0(o): dlci 204(0x30C1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:35:54.757: Serial0/0: Broadcast on DLCI 203  link 7
*Mar  1 04:35:54.757: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:35:54.757: Serial0/0: Broadcast on DLCI 201  link 7
*Mar  1 04:35:54.761: Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:35:54.761: Serial0/0: Broadcast on DLCI 205  link 7
*Mar  1 04:35:54.761: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:35:54.761: DLCI 213 is either deleted or i
Rack1R2#nactive
*Mar  1 04:35:54.781: broadcast dequeue
*Mar  1 04:35:54.781: Serial0/0(o):Pkt sent on dlci 204(0x30C1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:35:54.781: broadcast dequeue
*Mar  1 04:35:54.781: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:35:54.781: broadcast dequeue
*Mar  1 04:35:54.781: Serial0/0(o):Pkt sent on dlci 201(0x3091), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:35:54.882: broadcast dequeue
*Mar  1 04:35:54.882: Serial0/0(o):Pkt sent on dlci 205(0x30D1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:35:55.034: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 96
*Mar  1 04:35:55.034: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:35:55.034: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:36:02.318: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:36:02.318: OSPF: End of hello processing
*Mar  1 04:36:02.975: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:36:02.975: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:36:03.724: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
*Mar  1 04:36:04.233: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 96
*Mar  1 04:36:04.233: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:36:04.233: OSPF: End of hello processing
*Mar  1 04:36:04.754: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:36:04.762: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:36:04.762: Serial0/0: broadcast search
*Mar  1 04:36:04.762: Serial0/0: Broadcast on DLCI 204  link 7
*Mar  1 04:36:04.762: Serial0/0(o): dlci 204(0x30C1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:04.762: Serial0/0: Broadcast on DLCI 203  link 7
*Mar  1 04:36:04.762: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:04.762: Serial0/0: Broadcast on DLCI 201  link 7
*Mar  1 04:36:04.766: Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP),
Rack1R2# datagramsize 84
*Mar  1 04:36:04.766: Serial0/0: Broadcast on DLCI 205  link 7
*Mar  1 04:36:04.766: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:04.766: DLCI 213 is either deleted or inactive
*Mar  1 04:36:04.798: broadcast dequeue
*Mar  1 04:36:04.798: Serial0/0(o):Pkt sent on dlci 204(0x30C1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:04.798: broadcast dequeue
*Mar  1 04:36:04.798: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:04.798: broadcast dequeue
*Mar  1 04:36:04.798: Serial0/0(o):Pkt sent on dlci 201(0x3091), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:04.898: broadcast dequeue
*Mar  1 04:36:04.898: Serial0/0(o):Pkt sent on dlci 205(0x30D1), pkt type
0x800(IP), datagramsize 84
Rack1R2#
*Mar  1 04:36:12.082: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 80
*Mar  1 04:36:12.118: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 80
*Mar  1 04:36:12.162: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 80
*Mar  1 04:36:12.162: OSPF: Rcv LS UPD from 150.1.5.5 on Serial0/0 length 56 LSA count 1
*Mar  1 04:36:12.202: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 80
*Mar  1 04:36:12.206: OSPF: Rcv LS UPD from 150.1.5.5 on Serial0/0 length 56 LSA count 1
*Mar  1 04:36:12.318: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:36:12.318: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:36:13.051: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:36:13.051: OSPF: End of hello processing
*Mar  1 04:36:13.724: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
*Mar  1 04:36:14.029: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 96
*Mar  1 04:36:14.033: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:36:14.033: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:36:14.662: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 88
*Mar  1 04:36:14.754: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:36:14.766: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:36:14.766: Serial0/0: broadcast search
*Mar  1 04:36:14.766: Serial0/0: Broadcast on DLCI 204  link 7
*Mar  1 04:36:14.766: Serial0/0(o): dlci 204(0x30C1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:14.766: Serial0/0: Broadcast on DLCI 203  link 7
*Mar  1 04:36:14.766: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:14.770: Serial0/0: Broadcast on DLCI 201  link 7
*Mar  1 04:36:14.770: Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:14.770: Serial0/0: Broadcast on DLCI 205  link 7
*Mar  1 04:36:14.770: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:14.770: DLCI 213 is either deleted or ina
Rack1R2#ctive
*Mar  1 04:36:14.866: broadcast dequeue
*Mar  1 04:36:14.866: Serial0/0(o):Pkt sent on dlci 204(0x30C1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:14.866: broadcast dequeue
*Mar  1 04:36:14.866: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:14.866: broadcast dequeue
*Mar  1 04:36:14.866: Serial0/0(o):Pkt sent on dlci 201(0x3091), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:14.966: broadcast dequeue
*Mar  1 04:36:14.966: Serial0/0(o):Pkt sent on dlci 205(0x30D1), pkt type
0x800(IP), datagramsize 84
Rack1R2#
*Mar  1 04:36:22.323: OSPF: Rcv hello from 150.1.3.3 area 5 from Serial0/1 155.1.23.3
*Mar  1 04:36:22.323: OSPF: End of hello processing
*Mar  1 04:36:23.052: OSPF: Rcv hello from 192.10.1.254 area 51 from FastEthernet0/0 192.10.1.254
*Mar  1 04:36:23.052: OSPF: End of hello processing
Rack1R2#
*Mar  1 04:36:23.725: OSPF: Send hello to 224.0.0.5 area 5 on Serial0/1 from 155.1.23.2
*Mar  1 04:36:24.029: Serial0/0(i): dlci 205(0x30D1), pkt type 0x800, datagramsize 96
*Mar  1 04:36:24.029: OSPF: Rcv hello from 150.1.5.5 area 0 from Serial0/0 155.1.0.5
*Mar  1 04:36:24.033: OSPF: End of hello processing
*Mar  1 04:36:24.755: OSPF: Send hello to 224.0.0.5 area 51 on FastEthernet0/0 from 192.10.1.2
*Mar  1 04:36:24.771: OSPF: Send hello to 224.0.0.5 area 0 on Serial0/0 from 155.1.0.2
*Mar  1 04:36:24.771: Serial0/0: broadcast search
*Mar  1 04:36:24.771: Serial0/0: Broadcast on DLCI 204  link 7
*Mar  1 04:36:24.771: Serial0/0(o): dlci 204(0x30C1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:24.771: Serial0/0: Broadcast on DLCI 203  link 7
*Mar  1 04:36:24.771: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:24.771: Serial0/0: Broadcast on DLCI 201  link 7
*Mar  1 04:36:24.775: Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP),
Rack1R2# datagramsize 84
*Mar  1 04:36:24.775: Serial0/0: Broadcast on DLCI 205  link 7
*Mar  1 04:36:24.775: Serial0/0(o): dlci 205(0x30D1), pkt type 0x800(IP), datagramsize 84
*Mar  1 04:36:24.775: DLCI 213 is either deleted or inactive
*Mar  1 04:36:24.783: broadcast dequeue
*Mar  1 04:36:24.783: Serial0/0(o):Pkt sent on dlci 204(0x30C1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:24.783: broadcast dequeue
*Mar  1 04:36:24.783: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:24.783: broadcast dequeue
*Mar  1 04:36:24.783: Serial0/0(o):Pkt sent on dlci 201(0x3091), pkt type
0x800(IP), datagramsize 84
*Mar  1 04:36:24.883: broadcast dequeue
*Mar  1 04:36:24.883: Serial0/0(o):Pkt sent on dlci 205(0x30D1), pkt type
0x800(IP), datagramsize 84
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#
Rack1R2#sh fram
Rack1R2#sh frame-relay map
Rack1R2#sh frame-relay map
Serial0/0 (up): ip 0.0.0.0 dlci 213(0xD5,0x3450)
              broadcast,
              CISCO, status defined, inactive
Serial0/0 (up): ip 0.0.0.0 dlci 204(0xCC,0x30C0)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 203(0xCB,0x30B0)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 0.0.0.0 dlci 201(0xC9,0x3090)
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ip 155.1.0.5 dlci 205(0xCD,0x30D0), static,
              broadcast,
              CISCO, status defined, active
Rack1R2#

<-----------after------reload------------------------>
Rack1R2#show frame-relay map
Serial0/0 (up): ip 155.1.0.5 dlci 205(0xCD,0x30D0), static,
              broadcast,
              CISCO, status defined, active
Rack1R2#
Rack1R2#sh ip ospf nei

Neighbor ID     Pri   State           Dead Time   Address         Interface
150.1.5.5         0   FULL/  -        00:00:39    155.1.0.5       Serial0/0
150.1.3.3         0   FULL/  -        00:00:33    155.1.23.3      Serial0/1
192.10.1.254      1   FULL/DR         00:00:32    192.10.1.254    FastEthernet0/0
Rack1R2#
Rack1R3#sh ip ospf nei

Neighbor ID     Pri   State           Dead Time   Address         Interface
150.1.5.5         0   FULL/  -        00:00:39    155.1.0.5       Serial1/0
150.1.7.7         1   FULL/DR         00:00:36    155.1.37.7      FastEthernet0/0
150.1.1.1         0   FULL/  -        00:00:35    155.1.13.1      Serial1/2
150.1.2.2         0   FULL/  -        00:00:33    155.1.23.2      Serial1/3
Rack1R3#
 

Hm...

Mittwoch, 15. Juni 2011

INE WB Vol1 - 6.15 OSPF Demand Circuit

This feature is enabled with the interface level command ip ospf demand-
circuit, and is negotiated as part of the neighbor adjacency establishment. One side is sufficient.
The show command below output outlines the change in the adjacency between
R4 and R5 once the demand circuit feature is enabled.
Rack1R5#sh ip ospf int s0/1/0 | incl demand
  Configured as demand circuit.
  Run as demand circuit.
Rack1R5#

INE WB Vol1 - 6.14 OSPF Path Selection with Virtual-Links

6.14 OSPF Path Selection with Virtual-Links

Rack1R2#sh run | begin router
router ospf 1
router-id 150.1.2.2
log-adjacency-changes
auto-cost reference-bandwidth 30000
area 5 virtual-link 150.1.3.3
network 155.1.0.0 0.0.0.255 area 0
!
Rack1R2#sh ip ospf virtual-links
Virtual Link OSPF_VL2 to router 150.1.3.3 is down
  Run as demand circuit
  DoNotAge LSA allowed.
  Transit area 5, Cost of using 65535
  Transmit Delay is 1 sec, State DOWN,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Rack1R2#sh ip ospf virtual-links
Virtual Link OSPF_VL2 to router 150.1.3.3 is down
  Run as demand circuit
  DoNotAge LSA allowed.
  Transit area 5, Cost of using 65535
  Transmit Delay is 1 sec, State DOWN,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Rack1R2#sh ip ospf interface | incl Area
  Internet Address 155.1.0.2/24, Area 0
  Internet Address 0.0.0.0/0, Area 0
  Internet Address 150.1.2.2/24, Area 0
  Internet Address 155.1.23.2/24, Area 5
  Internet Address 192.10.1.2/24, Area 51
Rack1R2#sh run



Rack1R3#sh run | begin router
router ospf 1
router-id 150.1.3.3
log-adjacency-changes
auto-cost reference-bandwidth 30000
area 5 virtual-link 150.1.2.2
network 155.1.0.0 0.0.0.255 area 0
!
Rack1R3#sh ip ospf virtual-links
Virtual Link OSPF_VL1 to router 150.1.2.2 is up
  Run as demand circuit
  DoNotAge LSA allowed.
  Transit area 5, via interface Serial1/3, Cost of using 65535
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:07
Rack1R3#
Rack1R3#sh ip ospf int | incl Area
  Internet Address 150.1.3.3/24, Area 0
  Internet Address 155.1.0.3/24, Area 0
  Internet Address 155.1.37.3/24, Area 2
  Internet Address 155.1.13.3/24, Area 4
  Internet Address 155.1.23.3/24, Area 5
Rack1R3#

Fucking Virtual Links !!!!!!!!!!!!!!!

Dienstag, 14. Juni 2011

INE WB Vol1 - 6.11 OSPF Path Selection with Per-Neighbor Cost

Rack1R4(config-if)#bandwidth 768
Rack1R4(config-if)#do sh ip ospf int s0/0/0 | incl Cost
  Process ID 1, Router ID 223.255.255.255, Network Type POINT_TO_MULTIPOINT, Cost: 39062
Rack1R4(config-if)#no bandwidth
Rack1R4(config-if)#router ospf 1

R5(config)#router ospf 1
R5(config-router)#neighbor cost 39062

...yeah

Samstag, 11. Juni 2011

INE WB Vol1 - 5.22. EIGRP Filtering with Extended Access-Lists

Like RIP, extended access-lists when called as a distribute-list in IGP have a
different meaning than in redistribution or as in BGP. With BGP and
redistribution the “source” field in the ACL represents the network address, and
the “destination” field represents the subnet mask. In IGP distribute-list
application the “source” field in the ACL matches the update source of the route,
and the “destination” field represents the network address. This implementation
allows us to control which networks we are receiving, but more importantly who
we are receiving them from. Before the filter is applied, R5 routes as follows.

INE WB Vol1 - 5.17 EIGRP Stub Routing

Easy stuff.. just to remember
The EIGRP stub feature is used to limit the scope of EIGRP query messages,
and to limit what routes a neighbor advertises.

INE WB Vol1 - 5.15 EIGRP Unequal Cost Load Balancing

REVIEW !