Pete’s Packet

I don’t think I can. I know I can!

ROMmon Recovery for the Cisco 2600

Posted by Peter Kurdziel on July 15, 2009

http://www.cisco.com/en/US/products/hw/routers/ps259/products_tech_note09186a0080094a0b.shtml

rommon 1 > dir flash:
         File size         Checksum   File name
5358032 bytes (0x51c1d0)   0x7b16    c2600-i-mz.122-10b.bin
rommon 2 >

is the image valid?

rommon 2 > boot flash:c2600-i-mz.122-10b.bin

or

rommon 2 > confreg
correct if necessary (0x2102)


rommon 3 > reset

I had 3 routers crash today! Three different IOS's = bad checksum . What's going on? 

Hmmm a clue; *** System received a SegV exception ***

ERROR: 'Segmentation Violation (SegV) Exceptions' are always related to software
issues.
TRY THIS: Please refer to the TAC Case Collection - SegV exceptions for troubleshooting.
REFERENCE: For more information, see SegV Exceptions.

http://www.ciscotaccc.com/kaidara-advisor/core/showcase?case=K21445274
Cause of SegV Exceptions


SegV exceptions are always software problems. It is possible for different software issues to cause a SegV exception, such as:


    

  •  Access to an invalid memory address
    • 

  •  Write access to a read-only memory region
    • 

  •  A jump to an invalid PC (often 0x0)
    •

Posted in Real World, Routing & Switching Lab, Troubleshooting | Leave a Comment »

Day 60 – where does the time go?

Posted by Peter Kurdziel on July 15, 2009

So much to do and so little time. The nerves are starting to kick in.  I will be ready. :)

Wrapping up multicasting today. Then moving on to IPV6.

Posted in Routing & Switching Lab | Leave a Comment »

IP Protocol Numbers

Posted by Peter Kurdziel on July 13, 2009

http://www.iana.org/assignments/protocol-numbers/

Note: In the Internet Protocol version 4 (IPv4) [RFC791] there is a field
called "Protocol" to identify the next level protocol.  This is an 8
bit field.  In Internet Protocol version 6 (IPv6) [RFC1883], this field
is called the "Next Header" field.

Registry:
Decimal  Keyword          Protocol                                 References
-------  ---------------  ---------------------------------------  ------------------
0        HOPOPT           IPv6 Hop-by-Hop Option                   [RFC1883]
1        ICMP             Internet Control Message                 [RFC792]
2        IGMP             Internet Group Management                [RFC1112]
3        GGP              Gateway-to-Gateway                       [RFC823]
4        IP               IP in IP (encapsulation)                 [RFC2003]
5        ST               Stream                                   [RFC1190][RFC1819]
6        TCP              Transmission Control                     [RFC793]
7        CBT              CBT                                      [Ballardie]
8        EGP              Exterior Gateway Protocol                [RFC888][DLM1]
9        IGP              any private interior gateway             [IANA]
                          (used by Cisco for their IGRP)
10       BBN-RCC-MON      BBN RCC Monitoring                       [SGC]
11       NVP-II           Network Voice Protocol                   [RFC741][SC3]
12       PUP              PUP                                      [PUP][XEROX]
13       ARGUS            ARGUS                                    [RWS4]
14       EMCON            EMCON                                    [BN7]
15       XNET             Cross Net Debugger                       [IEN158][JFH2]
16       CHAOS            Chaos                                    [NC3]
17       UDP              User Datagram                            [RFC768][JBP]
18       MUX              Multiplexing                             [IEN90][JBP]
19       DCN-MEAS         DCN Measurement Subsystems               [DLM1]
20       HMP              Host Monitoring                          [RFC869][RH6]
21       PRM              Packet Radio Measurement                 [ZSU]
22       XNS-IDP          XEROX NS IDP                             [ETHERNET][XEROX]
23       TRUNK-1          Trunk-1                                  [BWB6]
24       TRUNK-2          Trunk-2                                  [BWB6]
25       LEAF-1           Leaf-1                                   [BWB6]
26       LEAF-2           Leaf-2                                   [BWB6]
27       RDP              Reliable Data Protocol                   [RFC908][RH6]
28       IRTP             Internet Reliable Transaction            [RFC938][TXM]
29       ISO-TP4          ISO Transport Protocol Class 4           [RFC905][RC77]
30       NETBLT           Bulk Data Transfer Protocol              [RFC969][DDC1]
31       MFE-NSP          MFE Network Services Protocol            [MFENET][BCH2]
32       MERIT-INP        MERIT Internodal Protocol                [HWB]
33       DCCP             Datagram Congestion Control Protocol     [RFC4340]
34       3PC              Third Party Connect Protocol             [SAF3]
35       IDPR             Inter-Domain Policy Routing Protocol     [MXS1]
36       XTP              XTP                                      [GXC]
37       DDP              Datagram Delivery Protocol               [WXC]
38       IDPR-CMTP        IDPR Control Message Transport Proto     [MXS1]
39       TP++             TP++ Transport Protocol                  [DXF]
40       IL               IL Transport Protocol                    [Presotto]
41       IPv6             Ipv6                                     [Deering]
42       SDRP             Source Demand Routing Protocol           [DXE1]
43       IPv6-Route       Routing Header for IPv6                  [Deering]
44       IPv6-Frag        Fragment Header for IPv6                 [Deering]
45       IDRP             Inter-Domain Routing Protocol            [Hares]
46       RSVP             Reservation Protocol                     [Braden]
47       GRE              General Routing Encapsulation            [Li]
48       DSR              Dynamic Source Routing Protocol          [RFC4728]
49       BNA              BNA                                      [Salamon]
50       ESP              Encap Security Payload                   [RFC4303]
51       AH               Authentication Header                    [RFC4302]
52       I-NLSP           Integrated Net Layer Security  TUBA      [GLENN]
53       SWIPE            IP with Encryption                       [JI6]
54       NARP             NBMA Address Resolution Protocol         [RFC1735]
55       MOBILE           IP Mobility                              [Perkins]
56       TLSP             Transport Layer Security Protocol        [Oberg]
                          using Kryptonet key management
57       SKIP             SKIP                                     [Markson]
58       IPv6-ICMP        ICMP for IPv6                            [RFC1883]
59       IPv6-NoNxt       No Next Header for IPv6                  [RFC1883]
60       IPv6-Opts        Destination Options for IPv6             [RFC1883]
61                        any host internal protocol               [IANA]
62       CFTP             CFTP                                     [CFTP][HCF2]
63                        any local network                        [IANA]
64       SAT-EXPAK        SATNET and Backroom EXPAK                [SHB]
65       KRYPTOLAN        Kryptolan                                [PXL1]
66       RVD              MIT Remote Virtual Disk Protocol         [MBG]
67       IPPC             Internet Pluribus Packet Core            [SHB]
68                        any distributed file system              [IANA]
69       SAT-MON          SATNET Monitoring                        [SHB]
70       VISA             VISA Protocol                            [GXT1]
71       IPCV             Internet Packet Core Utility             [SHB]
72       CPNX             Computer Protocol Network Executive      [DXM2]
73       CPHB             Computer Protocol Heart Beat             [DXM2]
74       WSN              Wang Span Network                        [VXD]
75       PVP              Packet Video Protocol                    [SC3]
76       BR-SAT-MON       Backroom SATNET Monitoring               [SHB]
77       SUN-ND           SUN ND PROTOCOL-Temporary                [WM3]
78       WB-MON           WIDEBAND Monitoring                      [SHB]
79       WB-EXPAK         WIDEBAND EXPAK                           [SHB]
80       ISO-IP           ISO Internet Protocol                    [MTR]
81       VMTP             VMTP                                     [DRC3]
82       SECURE-VMTP      SECURE-VMTP                              [DRC3]
83       VINES            VINES                                    [BXH]
84       TTP              TTP                                      [JXS]
85       NSFNET-IGP       NSFNET-IGP                               [HWB]
86       DGP              Dissimilar Gateway Protocol              [DGP][ML109]
87       TCF              TCF                                      [GAL5]
88       EIGRP            EIGRP                                    [CISCO][GXS]
89       OSPFIGP          OSPFIGP                                  [RFC1583][JTM4]
90       Sprite-RPC       Sprite RPC Protocol                      [SPRITE][BXW]
91       LARP             Locus Address Resolution Protocol        [BXH]
92       MTP              Multicast Transport Protocol             [SXA]
93       AX.25            AX.25 Frames                             [BK29]
94       IPIP             IP-within-IP Encapsulation Protocol      [JI6]
95       MICP             Mobile Internetworking Control Pro.      [JI6]
96       SCC-SP           Semaphore Communications Sec. Pro.       [HXH]
97       ETHERIP          Ethernet-within-IP Encapsulation         [RFC3378]
98       ENCAP            Encapsulation Header                     [RFC1241,RXB3]
99                        any private encryption scheme            [IANA]
100      GMTP             GMTP                                     [RXB5]
101      IFMP             Ipsilon Flow Management Protocol         [Hinden]
102      PNNI             PNNI over IP                             [Callon]
103      PIM              Protocol Independent Multicast           [Farinacci]
104      ARIS             ARIS                                     [Feldman]
105      SCPS             SCPS                                     [Durst]
106      QNX              QNX                                      [Hunter]
107      A/N              Active Networks                          [Braden]
108      IPComp           IP Payload Compression Protocol          [RFC2393]
109      SNP              Sitara Networks Protocol                 [Sridhar]
110      Compaq-Peer      Compaq Peer Protocol                     [Volpe]
111      IPX-in-IP        IPX in IP                                [Lee]
112      VRRP             Virtual Router Redundancy Protocol       [RFC3768]
113      PGM              PGM Reliable Transport Protocol          [Speakman]
114                       any 0-hop protocol                       [IANA]
115      L2TP             Layer Two Tunneling Protocol             [Aboba]
116      DDX              D-II Data Exchange (DDX)                 [Worley]
117      IATP             Interactive Agent Transfer Protocol      [Murphy]
118      STP              Schedule Transfer Protocol               [JMP]
119      SRP              SpectraLink Radio Protocol               [Hamilton]
120      UTI              UTI                                      [Lothberg]
121      SMP              Simple Message Protocol                  [Ekblad]
122      SM               SM                                       [Crowcroft]
123      PTP              Performance Transparency Protocol        [Welzl]
124      ISIS over IPv4                                            [Przygienda]
125      FIRE                                                      [Partridge]
126      CRTP             Combat Radio Transport Protocol          [Sautter]
127      CRUDP            Combat Radio User Datagram               [Sautter]
128      SSCOPMCE                                                  [Waber]
129      IPLT                                                      [Hollbach]
130      SPS              Secure Packet Shield                     [McIntosh]
131      PIPE             Private IP Encapsulation within IP       [Petri]
132      SCTP             Stream Control Transmission Protocol     [Stewart]
133      FC               Fibre Channel                            [Rajagopal]
134      RSVP-E2E-IGNORE                                           [RFC3175]
135      Mobility Header                                           [RFC3775]
136      UDPLite                                                   [RFC3828]
137      MPLS-in-IP                                                [RFC4023]
138      manet            MANET Protocols                          [RFC5498]
139      HIP              Host Identity Protocol                   [RFC5201]
140      Shim6            Shim6 Protocol                           [RFC5533]
141-252                   Unassigned                               [IANA]
253                       Use for experimentation and testing      [RFC3692]
254                       Use for experimentation and testing      [RFC3692]
255      Reserved                                                  [IANA]

Posted in Real World, Routing & Switching Lab | Leave a Comment »

ipv6 cef – For Unicast RPF to work, Cisco Express Forwarding must be configured globally in the router

Posted by Peter Kurdziel on July 8, 2009

The following prerequisites apply to Cisco Express Forwarding and distributed Cisco Express Forwarding for IPv6: – To forward IPv6 traffic using Cisco Express Forwarding or distributed Cisco Express Forwarding, you must configure forwarding of IPv6 unicast datagrams globally on the router by using the ipv6 unicast-routing command, and you must configure an IPv6 address on an interface by using the ipv6 address command.

– You must enable Cisco Express Forwarding for IPv4 globally on the router by using the ip cef command before enabling Cisco Express Forwarding for IPv6 globally on the router by using the ipv6 cef command.

– To use Unicast Reverse Path Forwarding (RPF), enable Cisco Express Forwarding switching or distributed Cisco Express Forwarding switching in the router. There is no need to configure the input interface for Cisco Express Forwarding switching. As long as Cisco Express Forwarding is running on the router, individual interfaces can be configured with other switching modes.

Note For Unicast RPF to work, Cisco Express Forwarding must be configured globally in the router. Unicast RPF will not work without Cisco Express Forwarding.

Posted in IPV6, Routing & Switching Lab | Leave a Comment »

TEN TIPS FOR TAKING THE LAB EXAM

Posted by Peter Kurdziel on July 8, 2009

TEN TIPS FOR TAKING THE LAB EXAM

1 Read the entire exam first and check for addressing issues. Do not skip any details or sections.
2 Manage your time. Make a plan to cover all the sections in the time provided. Work out how much time you will spend on each section, keeping in   mind the point value of the questions. Don’t forget to allow time at the end to verify your solutions.
3 Clarify the requirements of each question. Don’t assume requirements that aren’t mentioned in the question. During the lab, if you are in any doubt, verify your understanding of the question with the proctor.
4 Do each question as a unit. Configure and verify before moving to the next   question. You may want to redraw the topology with all the details available.   This will help you visualize and map the network.
5 Troubleshoot. You must know how to troubleshoot using the tools available.   Although troubleshooting is important, don’t lose too much time working on a  2- or 3-point question. If you’re caught off-guard by an unfamiliar topic, don’t let it absorb too much time. Work on the things you are more comfortable with and go back to difficult items later.
6 Keep a list. During the exam, make notes on configurations and settings as you move through the exam. Make a separate list for items you have not been able to address or where you have not achieved the desired result which you’ll need to revisit.
7 Test your work. Never rely on a configuration done in the early hours of   the exam. There is a possibility that an item you configured a few sections earlier can become broken and non-functional. Keep in mind that points are awarded for working configuration only.
8 Save your configurations often.
9 Don’t make any drastic changes in the last half hour of the exam.
10 Speed is vital on the exam. Review and practice core material the week before the exam to ensure you can move quickly through the less challenging questions.

Posted in Routing & Switching Lab | Leave a Comment »

Interesting problem 3550 etherchannel problem

Posted by Peter Kurdziel on July 8, 2009

ref: http://forum.internetworkexpert.com/ubbthreads.php/ubb/showflat/Number/14757/page/1#Post14757

If you use a 3550 as SW3 or SW4 it doesn’t like traffic being routed out a layer 3 port and then back across the switch in layer 2. 3560’s are fine with this behaviour. I think this is because a 3550 will send traffic for it’s own L3 port to the CPU:

My SW4 is a 3550 and my SW3 is a 3560:

Rack1SW4#sh run int fa0/20
Building configuration…

Current configuration : 87 bytes
!
interface FastEthernet0/20
no switchport
ip address 204.12.1.10 255.255.255.0
end

Rack1SW4#sh int fa0/20 | i bia
Hardware is Fast Ethernet, address is 000c.ced3.c580 (bia 000c.ced3.c580)

Rack1SW4#sh mac-address-table address 000c.ced3.c580
Mac Address Table
——————————————-

Vlan Mac Address Type Ports
—- ———– ——– —–
All 000c.ced3.c580 STATIC CPU
Total Mac Addresses for this criterion: 1

Rack1SW3#sh run int fa0/21
Building configuration…

Current configuration : 86 bytes
!
interface FastEthernet0/21
no switchport
ip address 204.12.1.9 255.255.255.0
end

Rack1SW3#sh int fa0/21 | i bia
Hardware is Fast Ethernet, address is 001a.6c81.15c1 (bia 001a.6c81.15c1)

Rack1SW3#sh mac-address-table address 001a.6c81.15c1
Mac Address Table
——————————————-

Vlan Mac Address Type Ports
—- ———– ——– —–
53 001a.6c81.15c1 DYNAMIC Fa0/19
Total Mac Addresses for this criterion: 1

So you can see that SW3 knows at layer 2 to get to the layer 3 port you need to go out via the trunk to SW4 and back over the access-vlan to the layer 3 interface.

SW4 thinks that to get to this mac address you go to the CPU, not out the trunk to SW3 and back over the access-vlan to the layer 3 interface.

For this reason SW4 cannot ping SW3 or R5, only BB3 (which is connected to SW3 so the traffic needn’t transit back over SW4 at layer 2).

Rack1SW4#ping 204.12.1.255

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.12.1.255, timeout is 2 seconds:

Reply to request 0 from 204.12.1.254, 28 ms
Reply to request 1 from 204.12.1.254, 28 ms
Reply to request 2 from 204.12.1.254, 8 ms
Reply to request 3 from 204.12.1.254, 28 ms
Reply to request 4 from 204.12.1.254, 20 ms

This makes this lab impossible to complete on 3550’s as SW3 or SW4 without modification. Just make the Fa0/20 into a vlan interface so that it doesn’t have to double hop SW4.

Rack1SW4(config)#do sh run int fa0/20
Building configuration…

Current configuration : 87 bytes
!
interface FastEthernet0/20
no switchport
ip address 204.12.1.10 255.255.255.0
end

Rack1SW4(config)#int fa0/20
Rack1SW4(config-if)#no ip add
Rack1SW4(config-if)#int vlan 53
11:23:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan53, changed state to up
Rack1SW4(config-if)#ip add 204.12.1.10 255.255.255.0
Rack1SW4(config-if)#end
11:24:00: %SYS-5-CONFIG_I: Configured from console by console
Rack1SW4#ping 204.12.1.255

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.12.1.255, timeout is 2 seconds:

Reply to request 0 from 204.12.1.9, 1 ms
Reply to request 0 from 204.12.1.254, 32 ms
Reply to request 0 from 204.12.1.5, 4 ms
Reply to request 1 from 204.12.1.9, 1 ms
Reply to request 1 from 204.12.1.254, 24 ms
Reply to request 1 from 204.12.1.5, 4 ms
Reply to request 2 from 204.12.1.9, 1 ms
Reply to request 2 from 204.12.1.254, 20 ms
Reply to request 2 from 204.12.1.5, 12 ms
Reply to request 3 from 204.12.1.9, 1 ms
Reply to request 3 from 204.12.1.5, 1 ms
Rack1SW4#

Posted in Routing & Switching Lab | Leave a Comment »

Oh no the switch crashed… Unexpected exception to CPUvector 1100

Posted by Peter Kurdziel on July 7, 2009

SW4(config-if)#interface Vlan10
SW4(config-if)#no  ip pim sparse-mode
SW4

Unexpected exception to CPUvector 1100, PC = 535BF4
-Traceback= 535BF4 536C54 537E40 538DF8 441D24 4382CC

=== Flushing messages (15:45:51 UTC Tue Mar 2 1993) ===

Buffered messages:
protocol on Interface FastEthernet0/21, changed state to down
00:05:36: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to down
00:05:36: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to down
00:05:36: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to down
00:06:09: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
00:06:09: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to up
00:06:09: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to up
00:06:12: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to down
00:06:12: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to down
00:06:12: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to down
00:06:14: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to up
00:06:14: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to up
00:06:14: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
00:06:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/19, changed state to up
00:06:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/21, changed state to up
00:06:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/20, changed state to up
00:13:52: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state to up
00:13:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
00:16:29: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/13 because of VTP domain mismatch.
00:16:29: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/14 because of VTP domain mismatch.
00:16:29: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/15 because of VTP domain mismatch.
00:17:09: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/16 because of VTP domain mismatch.
00:17:09: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/17 because of VTP domain mismatch.
00:17:09: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/18 because of VTP domain mismatch.
00:17:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
00:17:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down
00:17:14: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up
00:17:14: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
00:18:04: %LINK-5-CHANGED: Interface Vlan1, changed state to administratively down
00:18:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
00:18:15: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/19 because of VTP domain mismatch.
00:18:15: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/21 because of VTP domain mismatch.
00:18:15: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port Fa0/20 because of VTP domain mismatch.
00:18:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
00:18:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
00:18:33: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
00:18:33: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up
00:18:34: %SYS-5-CONFIG_I: Configured from console by console
00:18:34: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 155.1.108.8 (Port-channel1) is up: new adjacency
00:18:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
00:18:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up
00:18:35: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
00:18:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
00:19:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
1d02h: %SYS-5-CONFIG_I: Configured from console by console
1d15h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to down
Queued messages:
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE4, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 16-Jul-07 03:03 by myl

Data Load Translation Miss Exception (0×1100)!
CPU Register Context:
Vector = 0×00001100  PC = 0×00535BF4  MSR = 0×4008B030  CR = 0×40000044
LR = 0×00536C54  CTR = 0×00537E04  XER = 0×00000000
R0 = 0×00000000  R1 = 0×01C660E0  R2 = 0×00000000  R3 = 0×0154BF70
R4 = 0×00000003  R5 = 0xFEC0FEC0  R6 = 0xFEE00000  R7 = 0×0154BF70
R8 = 0×0154BF74  R9 = 0×02182228  R10 = 0×00000000  R11 = 0×00000000
R12 = 0×088851A4  R13 = 0×06D0A240  R14 = 0×00538D3C  R15 = 0×00000000
R16 = 0×00000000  R17 = 0×00000000  R18 = 0×00000000  R19 = 0×00000000
R20 = 0×00000000  R21 = 0×00000000  R22 = 0×00000000  R23 = 0×00000000
R24 = 0×00000000  R25 = 0×00000003  R26 = 0×00000000  R27 = 0×00000000
R28 = 0×00000000  R29 = 0×0154BF50  R30 = 0×0D0D0D0D  R31 = 0×0154BF70

Stack trace:
PC = 0×00535BF4, SP = 0×01C660E0
Frame 00: SP = 0×01C66108    PC = 0×00000000
Frame 01: SP = 0×01C66118    PC = 0×00536C54
Frame 02: SP = 0×01C66358    PC = 0×00537E40
Frame 03: SP = 0×01C66380    PC = 0×00538DF8
Frame 04: SP = 0×01C66388    PC = 0×00441D24
Frame 05: SP = 0×00000000    PC = 0×004382CC

Base ethernet MAC Address: 00:0b:be:bb:1f:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash…
flashfs[0]: 6 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 7151616
flashfs[0]: Bytes available: 8847360
flashfs[0]: flashfs fsck took 22 seconds.
…done Initializing Flash.
Boot Sector Filesystem (bs:) installed, fsid: 3
Loading “flash:/c3550-ipservicesk9-mz.122-25.SEE4.bin”…##############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################

File “flash:/c3550-ipservicesk9-mz.122-25.SEE4.bin” uncompressed and installed, entry point: 0×3000
executing…

Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software – Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE4, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 16-Jul-07 03:03 by myl
Image text-base: 0×00003000, data-base: 0×00DC4EBC

Initializing flashfs…
flashfs[1]: 6 files, 1 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 7151616
flashfs[1]: Bytes available: 8847360
flashfs[1]: flashfs fsck took 8 seconds.
flashfs[1]: Initialization complete.
…done Initializing flashfs.
POST: CPU Buffer Tests : Begin
POST: CPU Buffer Tests : End, Status Passed
POST: CPU Interface Tests : Begin
POST: CPU Interface Tests : End, Status Passed
POST: Switch Core Tests : Begin
POST: Switch Core Tests : End, Status Passed
POST: CPU Interface 2nd Stage Tests : Begin
POST: CPU Interface 2nd Stage Tests : End, Status Passed
POST: CAM Subsystem Tests : Begin
POST: CAM Subsystem Tests : End, Status Passed
POST: Ethernet Controller Tests : Begin
POST: Ethernet Controller Tests : End, Status Passed
POST: ILP Controller Tests : Begin
POST: ILP Controller Tests : End, Status Passed
POST: Loopback Tests : Begin
POST: Loopback Tests : End, Status Passed

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco WS-C3550-24-PWR (PowerPC) processor (revision A0) with 65526K/8192K bytes of memory.
Processor board ID CHK0652V1EK
Last reset from warm-reset
Running Layer2/3 Switching Image

Ethernet-controller 1 has 12 Fast Ethernet/IEEE 802.3 interfaces

Ethernet-controller 2 has 12 Fast Ethernet/IEEE 802.3 interfaces

Ethernet-controller 3 has 1 Gigabit Ethernet/IEEE 802.3 interface

Ethernet-controller 4 has 1 Gigabit Ethernet/IEEE 802.3 interface

24 FastEthernet interfaces
2 Gigabit Ethernet interfaces

The password-recovery mechanism is enabled.
384K bytes of flash-simulated NVRAM.
Base ethernet MAC Address: 00:0B:BE:BB:1F:00
Motherboard assembly number: 73-8100-05
Power supply part number: 341-0029-01
Motherboard serial number: CAT06510604
Power supply serial number: LIT0651059J
Model revision number: A0
Motherboard revision number: A0
Model number: WS-C3550-24PWR-SMI
System serial number: CHK0652V1EKFailed to generate persistent self-signed certificate.
Secure server will use temporary self-signed certificate.

Press RETURN to get started!

00:00:37: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
00:00:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
00:00:40: %SYS-5-CONFIG_I: Configured from memory by console
00:00:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
00:00:41: %SYS-5-RESTART: System restarted –
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE4, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 16-Jul-07 03:03 by myl
00:00:41: %LINK-5-CHANGED: Interface Vlan1, changed state to administratively down
00:00:43: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 155.1.108.8 (Port-channel1) is up: new adjacency
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/13, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/14, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/15, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/18, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
00:00:43: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to up
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/13, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/14, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/15, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/18, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/19, changed state to down
00:00:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/20, changed state to down
00:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
00:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down
00:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
00:00:46: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to down
00:00:46: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to down
00:00:46: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to down
00:00:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
00:00:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
00:00:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
00:00:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up
00:00:49: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
00:00:49: %LINK-3-UPDOWN: Interface FastEthernet0/21, changed state to up
00:00:49: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to up
00:00:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/18, changed state to up
00:00:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/13, changed state to up
00:00:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/14, changed state to up
00:00:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/15, changed state to up
00:00:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/20, changed state to up
00:00:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/21, changed state to up
00:00:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/19, changed state to up
00:01:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
00:01:41: %PLATFORM_CAT3550-1-CRASHED: System previously crashed with the following message:
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE4, RELEASE SOFTWARE (fc1)
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Copyright (c) 1986-2007 by Cisco Systems, Inc.
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Compiled Mon 16-Jul-07 03:03 by myl
00:01:41: %PLATFORM_CAT3550-1-CRASHED:
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Data Load Translation Miss Exception (0×1100)!
00:01:41: %PLATFORM_CAT3550-1-CRASHED: CPU Register Context:
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Vector = 0×00001100  PC = 0×00535BF4  MSR = 0×4008B030  CR = 0×40000044
00:01:41: %PLATFORM_CAT3550-1-CRASHED: LR = 0×00536C54  CTR = 0×00537E04  XER = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R0 = 0×00000000  R1 = 0×01C660E0  R2 = 0×00000000  R3 = 0×0154BF70
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R4 = 0×00000003  R5 = 0xFEC0FEC0  R6 = 0xFEE00000  R7 = 0×0154BF70
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R8 = 0×0154BF74  R9 = 0×02182228  R10 = 0×00000000  R11 = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R12 = 0×088851A4  R13 = 0×06D0A240  R14 = 0×00538D3C  R15 = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R16 = 0×00000000  R17 = 0×00000000  R18 = 0×00000000  R19 = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R20 = 0×00000000  R21 = 0×00000000  R22 = 0×00000000  R23 = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R24 = 0×00000000  R25 = 0×00000003  R26 = 0×00000000  R27 = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: R28 = 0×00000000  R29 = 0×0154BF50  R30 = 0×0D0D0D0D  R31 = 0×0154BF70
00:01:41: %PLATFORM_CAT3550-1-CRASHED:
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Stack trace:
00:01:41: %PLATFORM_CAT3550-1-CRASHED: PC = 0×00535BF4, SP = 0×01C660E0
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 00: SP = 0×01C66108    PC = 0×00000000
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 01: SP = 0×01C66118    PC = 0×00536C54
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 02: SP = 0×01C66358    PC = 0×00537E40
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 03: SP = 0×01C66380    PC = 0×00538DF8
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 04: SP = 0×01C66388    PC = 0×00441D24
00:01:41: %PLATFORM_CAT3550-1-CRASHED: Frame 05: SP = 0×00000000    PC = 0×004382CC
00:01:41: %PLATFORM_CAT3550-1-CRASHED:

After the switch rebooted everything seems fine.

I checked cisco.com’s bug tracker and this IOS is pretty buggy.

Posted in Routing & Switching Lab | Leave a Comment »

I got an awesome deal for a month long CCIE rack rental from Narbik

Posted by Peter Kurdziel on July 6, 2009

I got an awesome deal for a month long CCIE rack rental from Narbik. Student disctount: $450.00

More info http://www.micronicstraining.com/

Posted in Routing & Switching Lab | Leave a Comment »

Multicasting

Posted by Peter Kurdziel on July 6, 2009

Some reading:

http://www.cisco.com/en/US/docs/ios/12_0/np1/configuration/guide/1cmulti.pdf

http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/ipimt_ov.pdf

http://www.cisco.com/warp/public/cc/techno/tity/ipmu/tech/ipcas_dg.pdf

Multicast notes:

  • class d 224.0.0.0/4 (224.0.0.0 – 239.255.255.255)
  • reserved (like rfc 1918) – 224.0.0.0/24 (224.0.0.0 -224.0.0.255)
  • Administratively Scoped Block  – 239.0.0.0-239.255.255.255
  1. hello’s are sent every 30 sec to 224.0.0.13
  2. loopback – ip ospf point-to-point for RPF check
  3. (S,G) source tree / shortest path tree / source
    (*,G) shared tree / any source
  4. holdtime = 3.5x the hello
  5. highest IP wins DR
  6. lowest IP wins designated querier
  7. rp-address (unicast) must be advertised in unicast IGP
  8. mtrace to group address to see the reverse path
  9. traffic is always sent to the group address, never from.
  10. the source ip is always a unicast ip address, never a mcast address.
  11. igmp = router to client (automatically enabled with PIM)
  12. pim = router to router ( relies on unicast routing domain, do make sure you have full igp connectivity)
  13. sparse-mode – explicit join ( no traffic unless uyou request it) need’s an RP.
  14. dense-mode – implicit join (gets all traffic unlexx you don’t want it), flood and prune
  15. enabe mcast = ip multicast-routing (distributed on 3560)
  16. (*,G) don’t care about the source.  (S,G) knows the source
    • incoming null / outgoing null – does not know the source.
  17. Enable PIM on the shortest path to the Rp or you will get RFP failures.
  18. switching from a shared tree (*,G) to a  shortest path tree (S,G) = SPT switchover
  19. if theRPF fails the packet is dropped.
    • ping
    • sh ip mroute count
    • debup ip packet
    • ip mroute to rpf failure interface.
  20. RP
      • auto -rp
        • ip pim sparse-dense
        • ip pim send-rp-announce loopback scope 16
          ip pim send-rp-discovery scope 16
        • p pim autorp listener – use when you have sparse-mode interfaces/all sparse mode router.
        • fallback to dense mode is he default, to prevent it use : ip pim dm-fallback.
        • 224.0.1.39 (announce) and 224.0.1.40(discovery)
        • Candidate RPs advertize their willingness to be an RP via “RP-announcement” messages. These messages are periodically sent to a reserved well-known group 224.0.1.39 (CISCO-RP-ANNOUNCE).
        • RP mapping agents join group 224.0.1.39 and map the RPs to the associated groups. The RP mapping agents advertise the authoritative RP-mappings to another well-known group address 224.0.1.40 (CISCO-RP-DISCOVERY). All PIM routers join 224.0.1.40 and store the RP-mappings in their private cache.
        • deny statements – the groul ill be negatively cached and run int dense mode.
        • control updates with ip multicast boundry
        • For the Auto-RP with Multiple RPs scenario, no load balancing is provided, and, when an RP changes, convergence is normally on the order of 3 minutes.
      • Bootstrap router
        • ip pim sparse-mode
          ip pim bsr-candidate
          ip pim rp-candidate
        • use hash to load balance
        • multiples overlapping RP’s = highest priority wins
        • control updates with ip pim bsr-border
    • static – ip pim rp-address – you need this on all the mcast devices.
      • override – will override AUTORP or BSR rp mappings.
    • dynamic – auto-rp (cisco prorietary)  or BSR
  21. ip pim NBMA = use on hub in a FR network, to bypass split-horizon behavior.
  22. GRE is the duct tape of routing!!!  makse your tunnel interfaces passive.
  23. troubleshootin mcast:
    • 1  int s0/0 no ip mroute-cache -2- debup ip mpacket
    • debup ip pim
    • sh ip pim nei | rp | rp mapping | interface
    • sh ip pin int f0/0 detail
    • debup ip pim auto-rp <-shows you what RP is filtered.
    • sh run | in ip pim|int
    • keyword search under ip pim command reference
  24. ip helper-map
    • convert from mcast group to broadcast
      • ip multi helper-map 224.1.1.1 150.100.200.255 111
      • acecss-list 111 oer udp host 150.100.255.1 a eq 39000
  25. anycast – 2 RP’s with the same IP address’


    • r1
      int lo0
      ip add 10.0.0.1 255.255.255.255
      int lo1
      ip add 10.1.1.1 255.255.255.255
      ip msdp peer 10.1.1.2 connect-sour loo1
      ip msdp originator-id loo1
      ip pim rp-address 1.1.1.1 [acl]

      r2
      int lo0
      ip add 10.0.0.1 255.255.255.255
      int lo1
      ip add 10.1.1.2 255.255.255.255
      ip msdp peer 10.1.1.1 connect-sour loo1
      ip msdp originator-id loo1
      ip pim rp-address 1.1.1.1 [acl]

Posted in Multicast, Routing & Switching Lab | Leave a Comment »

Been busy

Posted by Peter Kurdziel on July 4, 2009

A friend of mine let me use his  workbook. I completed the first part and a few of the multiprotocol labs. Moving on.

Posted in Routing & Switching Lab | Leave a Comment »

« Previous Entries