06-04-2008 09:46 AM - edited 03-03-2019 10:13 PM
I am working with a 3845 with 3 dual T1 WICS and 2 2851's with 1 dual T1 and a single T1 WIC. Having trouble getting them to communicate across simulated T1 connections. I have made the test cables for loopbacks and have all WICS connected (3 to each 2851 ) I cannot get any communication acrossed the routers, ie, ping. Previous routers have serial lines to establish point-to-point routes but do not see serial interfaces on the newer configuration IOS 12.4 (17b). My test cables are configured by creating jumper patch cables with 1-4, 2-5, 4-1, 5-2. All WICS are lit green on the CD lights. Once communications are established, how are the T1 lines bonded? There will be 3 T1 lines bonded to each 2851 from the 3845.
3845 sho run
version 12.4 no service pad service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption service sequence-numbers ! hostname cisco3845 ! boot-start-marker boot-end-marker ! card type t1 0 0 card type t1 0 1 card type t1 0 2 security authentication failure rate 3 log
security passwords min-length 6
logging buffered 51200 debugging
logging buffered 51200 debugging logging console critical enable secret xxx ! no aaa new-model clock timezone PCTime -6 clock summer-time PCTime date Apr 6 2003 2:00 Oct 26 2003 2:00
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-participate wic 2
no ip source-route ip
06-04-2008 09:54 AM
Hi Bill,
I don't see any serial interfaces in the running config [may be because of formatting].
Can you upload the show run and show diag output in a txt file.
+ show ver
-> Sushil
06-04-2008 10:10 AM
Bill
It is not clear in your post what kind of cards these are. But I suspect that the issue is that the cards support both T1 and E1 and need to be identified to IOS what they are to do. Use the command card type t1
If that does not solve your issue then it would help if you would post the output of show diag and the complete running-config.
HTH
Rick
06-04-2008 01:12 PM
06-04-2008 05:56 PM
Bill
Maybe I have some good news and perhaps some not so good news. I found some interesting things in this link:
The good news is that there is a command in controller t1 config mode for:
channel-group 1 timeslots 1-23
and the channel-group command that assigns certain channels is the command that creates the serial interface:
interface Serial0/0:1
ip address x.x.x.x m.m.m.m
The not so good news is that according to this link:
Cisco IOS Image -- To run these features on T1/E1 interfaces, you must install an IP Plus or IP Voice image (minimum) of Cisco IOS Release 12.3(14)T or a later release.
and you are running the IP BASE feature set. So it may be that you will need to upgrade the IOS image to a different feature set (not necessarily a different version) to be able to use these interfaces.
I would give the channel-group command a shot. If it works that is good. And if it does not produce the serial interfaces then you need a different image.
HTH
Rick
06-06-2008 05:01 AM
Rick,
Is the 12.3(14)T a downloadable IOS or is this one that will need an initial purchase?
Thanks
Bill
06-06-2008 07:42 AM
Bill
If the router is covered by a maintenance contract then the IOS should be a downloadable issue. If the router is not covered by maintenance then it probably is a purchase issue.
HTH
Rick
06-06-2008 07:45 AM
Rick,
The routers are new. We started the installation on Monday of this week. I am not sure if a contract was sold with them or not.
Bill
06-06-2008 09:25 AM
Bill
It may depend on the terms specified by who ever sold the routers to you. I would be optimistic that most new routers are covered by a warranty that should cover it. But you probably should check with who ever sold the routers to you.
HTH
Rick
06-10-2008 07:47 AM
Rick,
I am still waiting to hear from my sources regarding the IOS upgrade, as to if it is a purchase or downloadable. I was attempting the command to create the serial interface. Looking at my options, it appears the serial is not there. Am I in the correct place?
cisco3845(config-if)#?
Interface configuration commands:
access-expression Build a bridge boolean access expression
arp Set arp type (arpa, probe, snap) or timeout
backup Modify backup parameters
bandwidth Set bandwidth informational parameter
bgp-policy Apply policy propagated by bgp community string
carrier-delay Specify delay for interface transitions
cdp CDP interface subcommands
dampening Enable event dampening
default Set a command to its defaults
delay Specify interface throughput delay
description Interface specific description
diffserv diffserv (Provisioning)
dot1q dot1q interface configuration commands
exit Exit from interface configuration mode
flow-sampler Attach flow sampler to the interface
help Description of the interactive help system
hold-queue Set hold queue depth
ip Interface Internet Protocol config commands
keepalive Enable keepalive
llc2 LLC2 Interface Subcommands
load-interval Specify interval for load calculation for an
cisco3845(config-if)#
06-10-2008 08:51 AM
Bill
This output indicates that you are in interface config mode (cisco3845(config-if)#). I believe that you want to be in controller t1 mode to enter the channel-group command which would create the serial interface.
HTH
Rick
06-10-2008 11:31 AM
06-10-2008 12:58 PM
Bill
I am glad that you managed to get the serial interfaces configured. Is this still on the IP Base image?
I have looked at the configs and while there are some things that I would question (especially the network statements under router rip) I do not see config problems that would explain not being able to ping the main router ethernet from a remote. The main router does have static routes configured for each remote ethernet with a correct next hop address. And each remote has a valid default route configured which should get to the main.
I wonder if some interfaces are not working as expected. Could you post the output of these commands from the main router and from at least one of the remote routers:
show ip route
show ip interface brief
show cdp neighbor detail
HTH
Rick
06-10-2008 01:20 PM
Rick,
I ran the commands to one file. The last command received an error about % CDP is not enabled. The RIP was just a test that did not get removed. The remote routers can ping/telnet into the main router Gigabit Eth address but cannot telnet/ping the remotes Gigabit Eth addresses from the main site router. This is still the IP Base image. I have a case open and have received an email from Luis Aguero.
06-10-2008 01:36 PM
Bill
The additional information is quite helpful and shows exactly what the issue is. from the remote router:
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 192.168.10.1 YES NVRAM up down
If the remote ethernet interface is protocol down then it can not receive or respond to the ping. I suspect the interface is down because nothing is connected to it. The simple solution would be to connect something to the ethernet interface. If there is some reason for not connecting something to the interface then as a test you could configure "no keepalive" under the remote ethernet interface. This will bring the interface protocol up.
HTH
Rick
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: