[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem With E1
- Subject: Problem With E1
- From: hcb at netcases.net (Howard C. Berkowitz)
- Date: Thu, 26 Feb 2009 07:36:31 -0500
- In-reply-to: <[email protected]>
- References: <[email protected]>
> -----Original Message-----
> From: Shivlu Jain [mailto:shivlu.jain at gmail.com]
> Sent: Thursday, February 26, 2009 4:05 AM
> To: nanog at nanog.org
> Subject: Problem With E1
> Since morning I am facing a issue in which one of E1 is configured under
> OSPF. OSPF neighborship is up but not able to send and receive the data.
> configuration is plain vanila. Why it is happening so; I donot know?
> Thanks & Regards
> shivlu jain
If this is an operational circuit, this is a good example of why it can
extremely useful to document the working configuration of a resource, so you
can compare the malfunctioning configuration. The document may well be
stored as a file, and the comparison could be made with diff or a similar
Don't forget SNMP and NetFlow, both on the router, but also SNMP on the
access device, modem, multiplexer, etc.
When that circuit first came up, I probably would have captured the
information from the router's equivalent of the Cisco commands:
* show interface
* show ip interface
* show ip ospf interface
* show ip ospf neigbors
Possibly show ip ospf database and show ip ospf database neighbors; perhaps
save the routing table when storing those displays.
Even more displays could be useful, such as subinterfaces.
Electrical tests, such as verifying the signal clocking and amplitude, are
usually last resorts -- although do verify that no one has moved the cabling
among router/CSU ports, and that everything has power.