No magic file found in flash -- Booting in ROMMON mode

If you have a router that goes directly in ROMMON mode and is returned with an error "No magic file found in flash"

Couple of solutions,

If you get a message saying "no magic number found" then chances are your EEPROM has gotten corrupted. You probably will have to replace the box or call Cisco TAC. This is from Cisco's CCO:

"No magic number found in RP1 EEPROM
Explanation The structure containing the system MAC address needed by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.

Recommended Action Return the RP for reprogramming and call your technical support representative for assistance. "


You can try the following methods to recover your box.

(1)Check the confreg value and make sure it correct.
show config
Configuration register is 0x2102.

(2)Try booting from ROMMON mode only
u can try following commands
IP_ADDRESS=1.1.1.1
IP_SUBNET_MASK=255.0.0.0
GATWAY=1.1.1.2 (UR MACHINES IP ADDRESS)
TFTP_SERVER=1.1.1.2
TFTP_FILE= bootable image file
tftpdnld

(3) XModem
It can be done using Xmodem through the console connection. It takes a LONG time compared to other methods, but you can speed it up a little bit by changing the baud rate on the console from 9600 to 19200 or whatever is the fastest. This can be done in ROMMON. Don't forget to also change the baud on your serial connection on your laptop. Some of the particulars of how to do this depend on what program you use--hyperterm, teraterm, etc.

DHCP config with MS loopback adapter

Here is the attached snapshot and config of my dhcp on 3725 router to get the desired result. Yes I m excited!


ip dhcp pool DATA
network 172.16.2.0 255.255.255.0
default-router 172.16.2.1
dns-server 4.2.2.2
!
!
!
interface FastEthernet0/0
ip address 172.16.2.1 255.255.255.0
duplex auto

Configuring Inter VLAN routing and DHCP-Scope-VLAN Bindings

Hats off to Taha for digging it to the level it demanded, this exercise has polished DHCP and inter vlan routing issues. the details of the config are as follows



Replace the 3550 with 3725 hooked with NM-16-ESW, yep im speaking the GNS-3 language, the IP addressing is different from the above image but topology remains the same, the configs are follows.


Layer3_Switch Config

!---ENABLING IP ROUTING

conft# ip routing

!---INTERFACE TO DHCP ROUTER

conft# interface fa1/1
conft# no switchport
conft# ip address 200.1.1.1 255.255.255.0
conft# no shutdown

!---CREATING DATA AND VOICE VLANS

conft# vlan 10
conft# name VOICE
conft# vlan 10
conft# name DATA

!---CREATING SVIs FOR DATA AND VOICE VLANS

conft# interface vlan 10
conft# ip address 172.16.1.1 255.255.255.0
ADDING AN IP HELPER ADDRESS TO DHCP SERVER TO GET AN IP THROUGH VOICE SCOPE
conft# ip helper-address 200.1.1.2

conft# no shutdown

conft# interface vlan 20
conft# ip address 172.16.2.1 255.255.255.0
ADDING AN IP HELPER ADDRESS TO DHCP SERVER TO GET AN IP THROUGH DATA SCOPE
conft# ip-helper address 200.1.1.2
conft# no shutdown

!---INTERFACE TO PC AND IP SOFT/PHONE

conft# interface fa1/10
conft# switchport access vlan 20
conft# switchport voice vlan 10
conft# no shutdown


!---CREATING A DEFAULT ROUTE

------------------------------------------------------------

DHCP Router Config

conft# interface fa0/0

conft# ip address 200.1.1.2 255.255.255.0
conft# no shutdown


(config)# ip dhcp excluded-address 172.16.1.1 172.16.1.9
(config)# ip dhcp excluded-address 172.16.2.1 172.16.2.9

(config)# ip dhcp pool DATA
(dhcp-config)# network 172.16.2.0 255.255.255.0
(dhcp-config)# default-router 172.16.2.1
(dhcp-config)# dns-server 4.2.2.2
(dhcp-config)# exit

(config)# ip dhcp pool VOICE
(dhcp-config)# network 172.16.1.0 255.255.255.0
(dhcp-config)# default-router 172.16.1.1
(dhcp-config)# option 150 ip 172.16.1.1
(dhcp-config)# exit

(config)# ip route 172.16.1.0 255.255.255.0 200.1.1.1
(config)# ip route 172.16.2.0 255.255.255.0 200.1.1.1


very helpful reference document,

http://www.cisco.com/en/US/tech/tk389/tk815/technologies_configuration_example09186a008019e74e.shtml

Voice Lab Setup 17-1-09

I have started setting up my home voice lab with initial infrastructure using 3725 routers at HQ, BR1 and BR2. I have added wic-2T and nm-16esw cards in each router. The initial step include the frame-relay setup among above 3 routers using frame relay switch. We can ping each HQ > BR1 and vice versa and also From HQ > BR2 and vice versa.

The config snap and topology snap is attached for your review.

Next steps would be adding HQ to local LAN, configuring vlans, dhcp server and ospf.

MCSE log

Classes of IP addresses,

Class A : 1-126 : 1.0.0.1 to 126.255.255.254
Class B : 128-191 : 128.1.0.1 to 191.255.255.254
Class C : 192-223 : 192.0.1.1 to 223.255.254.254
Class D : 224-239 : 224.0.0.0 to 239.255.255.255
Class E : 240-254 : 240.0.0.0 to 254.255.255.254

pecial address ranges

Some addresses are reserved for special uses (RFC 3330).^[2]

Address range	CIDR Equivalent	Purpose	RFC	Class	Total # of addresses
0.0.0.0 - 0.255.255.255	0.0.0.0/8	Zero Addresses	RFC 1700	A	16,777,216
10.0.0.0 - 10.255.255.255	10.0.0.0/8	Private IP addresses	RFC 1918	A	16,777,216
127.0.0.0 - 127.255.255.255	127.0.0.0/8	Localhost Loopback Address	RFC 1700	A	16,777,216
169.254.0.0 - 169.254.255.255	169.254.0.0/16	Zeroconf / APIPA	RFC 3330	B	65,536
172.16.0.0 - 172.31.255.255	172.16.0.0/12	Private IP addresses	RFC 1918	B	1,048,576
192.0.2.0 - 192.0.2.255	192.0.2.0/24	Documentation and Examples	RFC 3330	C	256
192.88.99.0 - 192.88.99.255	192.88.99.0/24	IPv6 to IPv4 relay Anycast	RFC 3068	C	256
192.168.0.0 - 192.168.255.255	192.168.0.0/16	Private IP addresses	RFC 1918	C	65,536
198.18.0.0 - 198.19.255.255	198.18.0.0/15	Network Device Benchmark	RFC 2544	C	131,072
224.0.0.0 - 239.255.255.255	224.0.0.0/4	Multicast	RFC 3171	D	268,435,456
240.0.0.0 - 255.255.255.255	240.0.0.0/4	Reserved[3],[4],[5]	RFC 1166	E	268,435,456

[edit] See also

Configuring IP Netflow in Cisco 3725

Configuring IP Netflow in Cisco 3725



Disclaimer: Credit to Josh (Head Geek) www.solarwinds.com

PoE and PoE+(802.3at)

Since the original introduction of PoE, the IEEE has initiated a new project called 802.3at which is commonly referred to as PoE+. This project enhances PoE in a couple of very important ways. First, it provides up to 30W of power to a Powered Device (PD), 25.5 watts to the device and 4.5 for line loss, and allows this power to also run on cabling designed for 1000BASE-T. Secondly,
it provides a new mechanism for communicating power capability and requirements using the 802.1ab Link Layer Discovery Protocol (LLDP). This protocol addition allows PoE+ switches to deliver power more efficiently and thereby provide power to more devices for a given power supply capacity. The new standard is going to be a superset of the 802.3af because it provides all
the same functionality, and more. The table below shows the capabilities of 802.3af versus 802.3at.

In order for 802.3at to provide higher power, Class D (Cat5e) or better cables are required. 802.3at also increases the minimum output voltage of the Power Source Equipment (PSE) from 44 volts to 50 volts. For this reason, you may note that ProCurve PoE+ devices use a 54 volt power supply.

Note:
The detection and classification functions ensure that if two PoE sources are attached together, power will not be improperly applied.
Here are some reasons why you might want to do this:

■ Simplifies installation and saves space - only one set of wires to bring to your appliance.
■ Saves time and money - there is no need to pay for additional electrical power runs or to delay your installation schedule to make them.
■ Minimal disruption to the workplace - the appliance can be easily moved, to wherever you can lay a LAN cable.
■ Safer - no AC voltages need to be added for additional network devices.
■ As well as the data transfer to and from the appliance, you can use SNMP network management infrastructure to monitor and control the appliances.
■ Appliances can be shut down or reset remotely - no need for a reset button or power switch.
■ When implementing wireless LAN systems it simplifies the radio frequency (RF) survey task, as the access point can easily be moved and wired in.

Power Through the Cable:

A standard CAT5 Ethernet cable has four twisted pairs. Only two of these pairs are used for 10Base-T and 100Base-TX data; all four are used for 1000Base-T data. The specification allows two options for using these cables for power:
■ The spare pairs are used. The pair on pins 4 and 5 are connected together and form the positive supply, and the pair on pins 7 and 8 are connected and form the negative supply.
■ The data pairs are used. Since Ethernet pairs are transformer coupled at each end, it is possible to apply DC power to the center tap of the isolation transformer without upsetting the data transfer. In this mode of operation the pair on pins 1 and 2 and the pair on pins 3 and 6 can be of either polarity.




The 802.3af standard does not allow both pairs (spare and data) to be used - a choice must be made. The Power Sourcing Equipment (PSE) applies power to either set of wires. HP ProCurve Networking switches, as a PSE, supply PoE power over the “data pair” or, pins 1 and 2, and the pair on pins 3 and 6. The Powered Device (PD) must be able to accept power from both options
because mid-span equipment must (according to the specification) supply power over the “spare pair” or pins 4 and 5, and the pair on pins 7 and 8.

An obvious requirement of the specification is to prevent damage to existing Ethernet equipment. A discovery process, run from the PSE, examines the Ethernet cables, looking for devices that comply with the specification. It does this by applying a small current-limited voltage to the cable and checks for the presence of a 25k ohm resistor in the remote device. Only if the resistor is present, will the full wattage be applied, but this is still current-limited to
prevent damage to cables and equipment in fault conditions.Once discovered, a different voltage is applied, and based upon the current drawn, the class of device can be determined. This indicates how much power is to be drawn. The 802.3at standard provides both a physical classification and a logical classification, which is even more precise. The PD must continue to draw a minimum current. If it does not (for example, when the device is unplugged) then the PSE removes the power and the discovery process begins again.

General Considerations
The following is an example list of considerations during the planning phase no matter which series of switches are being installed:
■ How many devices need PoE power?
■ What devices will need PoE power?
■ How much power will each device require, in watts?
■ What is the total of all their wattages?
■ Will the devices be connected to a 2910al, 3500yl, 5400 or to a 8200zl
switch?
■ How many ports are needed?
■ How many ports are available?
■ Are the devices to be powered by PoE power supported?

Disclaimer: http://cdn.procurve.com/training/Manuals/PoEPlannngGuide-Oct2009-59918574.pdf