ascend pipe130 ip routing table

ascend pipe130 ip routing table

Post by Tim Shee » Fri, 12 Jun 1998 04:00:00



I seem to be having a routing problem with an Ascend Pipe130.  It is
being used in a nailed T1 environment (recently switched from ISDN).

The T1 is fine, and the upstream router is configured properly as far
as I know.  The only change is the addition of encapsulating ppp.
(they had a loaner router that has been working for a month on this
T1).

Anyway, from I can get across the T1 to the upstream directly
connected serial port, but no further (ie another serial port on the
same upstream router).  The thing is, it worked for a while....while I
was testing it, we got out to the Internet with no problem.....within
an hour or two, it was not working....

I looked at the routing table (which is pasted below), but haven't a
clue what all those entries mean (no documentation available either).

I am used to working strictly with Cisco, and in comparing the two
tables, this makes no sense to me.

Any help or pointers would be greatly appreciated!!!!

ascend% sh ip route

Destination        Gateway       IF     Flg     Pref Met     Use  Age
127.0.0.0/8        -             bh0    CP       0   0       0    8556
127.0.0.1/32       -             local  CP       0   0       4    8556
127.0.0.2/32       -             rj0    CP       0   0       0    8556
207.63.39.0/25     -             ie0    C        0   0   15555    8556
207.63.39.33/32    -             local  CP       0   0    4915    8556
209.174.137.32/30 209.174.137.33 wan1   rGT      1   1       0    8546
209.174.137.33/32 209.174.137.33 wan1   rT       1   1    1913    8546
209.174.137.33/32 209.174.137.33 wan1   *SG    120   7       2    8556
209.174.137.34/32  -             local  CP       1   0     854    8556
224.0.0.0/4        -             mcast  CP       0   0    1851    8556
224.0.0.5/32       -             bh0    CP       0   0       0    8556
224.0.0.6/32       -             bh0    CP       0   0       0    8556
224.0.0.9/32       -             local  CP       0   0       0    8556
255.255.255.255/32 -             ie0    CP       0   0       1    8556

Thanks again!!!

Tim Sheets

 
 
 

ascend pipe130 ip routing table

Post by Tim Shee » Sat, 13 Jun 1998 04:00:00


....Thanks to Kevin Smith for this response...

Quote:> > Anyway, from I can get across the T1 to the upstream directly
> > connected serial port, but no further (ie another serial port on the

> Confused! What does this mean...? You can telnet to the other box?

Well, I could ping to the port at the other end of the T1 (the
upstream
router), but no other serial ports on the upstream router.  Once I
telnetted
to the upstream, I could get anywhere.....  more later with your
notes....

Quote:> > I am used to working strictly with Cisco, and in comparing the two
> > tables, this makes no sense to me.

> Yes, the docs would definitely help...imagine my problems with the Cisco and
> no docs...as an Ascend user....

I agree!!!  But, in this particular instance, when you show the IP
routing
table on a cisco, it tells you in some header info, what all the flags
mean...the Ascend didn't :-(

Quote:> > Destination        Gateway       IF     Flg     Pref Met     Use  Age
> > 127.0.0.0/8        -             bh0    CP       0   0       0    8556
> > 127.0.0.1/32       -             local  CP       0   0       4    8556
> > 127.0.0.2/32       -             rj0    CP       0   0       0    8556
> > 207.63.39.0/25     -             ie0    C        0   0   15555    8556
> > 207.63.39.33/32    -             local  CP       0   0    4915    8556
> > 209.174.137.32/30 209.174.137.33 wan1   rGT      1   1       0    8546
> > 209.174.137.33/32 209.174.137.33 wan1   rT       1   1    1913    8546
> > 209.174.137.33/32 209.174.137.33 wan1   *SG    120   7       2    8556
> > 209.174.137.34/32  -             local  CP       1   0     854    8556
> > 224.0.0.0/4        -             mcast  CP       0   0    1851    8556
> > 224.0.0.5/32       -             bh0    CP       0   0       0    8556
> > 224.0.0.6/32       -             bh0    CP       0   0       0    8556
> > 224.0.0.9/32       -             local  CP       0   0       0    8556
> > 255.255.255.255/32 -             ie0    CP       0   0       1    8556

> No default route in the routing table...should it point to the remote
> box? Set the default route to 209.174.137.33 in the menu:

Good eye!!  That was the problem.....  Actually, I did have a default
route
set there, but something else in the configuration (WAN Alias) was
over-riding
it (at least that is my best assessment).  I found that each time I
went into
the menu for the default route, and came back out, the table reflected
the
default route...but if the Ascend was reset, it didn't keep it.
 When I took out the entry for WAN Alias, it worked each time, even
after a
reset.

Thanks for your time and help!!!!

 
 
 

1. exchange routes between global IP routing table and VRF routing table

I understand that we can inject the global routes into the VRF routing
table using ip route vrf vrf_name x.x.x.x y.y.y.y next_hop global
command, and vice versa, however, my question is, is there any way to
do it dynamicly (like using dynamic routing protocol)? Since
currently, my customer VRF has a lot of public segment, e.g.
A.x.x.x/8, B.y.y.y/8. They need to access Internet over MPLS VPN link,
but I don't want to take care of every segment manually (using the
static routes with global switch commands).

If there is any way to do it dynamicly, please drop me a line, I
appreciate any input and help.

zher

2. How do you restore data Bk'd up w/ NT4?

3. BGP routes to IP main routing table

4. Displaying in work window.

5. EIGRP topology table vs routing table

6. Still going....

7. Difference between routing-table and forwarding-table

8. Eigrp topology table vs routing table

9. arp table filling rapidly after changing 0.0.0.0 route from ip to int

10. How to capture long ip route table from 7507 unattendedly?

11. Question on adding ip address to route table in 2501

12. IP routing tables for Cisco routers IOS versions 10.3 and 11.7