Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) P75 local routes/disappearing pools
Hello,
I've noticed people talking about dissapearing IP #s and Wan Pools on
their Maxes and it seems seems as if I've got a surplus on one of my
P75's. I wonder if anyone can shed some light on what might be going on.
I recently noticed routes being added to the routing table. I never
noticed this until I loaded ver 6.02. Or maybe it was when my ISP went
to 6.1 ? I'm not sure which. ;-) We were having problems with the router
rebooting in the middle of ftp sessions. The upgrade has seemed to cure
the ftp problem but now I'm getting a lot of "local" routes showing up,
there are 46 of them in the latest screen capture of the routing table
below. All the routes beginning with 207.49.208.xxx/32 are a mystery to
me. RIP is turned off everywhere because there are some other vendors
routers running RIP connected to our network with that add hundreds more
routes we don't need and seems to slow things down. I have done a
traceroute on these from off site and the trace goes tothe MAX router I
connect to at our ISP and from then "destination host unreachable" the
#s are not visible as we are using NAT. This seems like the temporary
number we get when connect. This is a "newer" pipeline
75 without the slide switch, it's been in place close to a year, I have
an older P75 with a switch that has the same software version number but
only 2 of the "207" "local" routes is showing up on it. I've submitted a
trouble ticket #212756 to Ascend. They said the only thing this could be
is "RIP or forgotten static routes" and requested I send a screen
capture which I did (5-19) but have not gotten any response since. I
have gone over and over the config to be sure RIP is not on anywhere. We
do
have 4 static routes but none of them are "forgotten" and I would not
forget about 46 - this looks almost like an entire subnet.
Could this be the MAX at our ISP assigning an IP # each time we
connect that the P75 is somehow retaining? According to the flag they
are placed by NetMgt all have a Pref of 100 indicating they came from
RIP and are temporary but they don't go away when the link is down. They
will go away if I power down the router but soon build back up. Could
this be where your IP numbers/Wan Pools are disappearing to?
My next step is to contact my ISP and see if they have noticed anything.
The 143.61.xxx.xxx routes are to one of our networks.
The 192.168.100.xxx routes are to one of our networks.
The 198.177.164.xxx route is to a service provider.
The 204.246.2.xxx routes are to our ISP.
The 207.49.208.xxx/32 routes are the ones in question.
ascend% iproute show
Destination Gateway IF Flg Pref Met Use
Age
0.0.0.0/0 204.246.2.174 wanidle0 Sn 100 1 4348
127.0.0.0/8 - bh0 CP 0 0 0
1018508
127.0.0.1/32 - local CP 0 0 0
1018508
127.0.0.2/32 - rj0 CP 0 0 0
1018508
143.61.0.0/16 143.61.44.1 ie0 SG 60 8 13338
1018333
143.61.44.0/26 - ie0 C 0 0 14437
1018508
143.61.44.4/32 - local CP 0 0 4218
1018508
192.168.100.0/24 192.168.100.110 wan16 rGTM 60 7 142
193
192.168.100.0/24 192.168.100.110 wan16 SGM 60 7 3467
1018333
192.168.100.110/32 192.168.100.110 wan16 rT 60 7 265
193
192.168.100.110/32 192.168.100.110 wan16 *S 120 7 2
1018508
198.177.164.0/24 143.61.44.35 ie0 SG 60 2 256
1018333
204.246.2.160/27 204.246.2.174 wanidle0 SG 120 7 0
1018333
204.246.2.174/32 204.246.2.174 wanidle0 S 120 7 2
1018333
207.49.208.129/32 - local rPTn 100 0 96
920857
207.49.208.131/32 - local rPTn 100 0 25802
915458
207.49.208.132/32 - local rPTn 100 0 981
740897
207.49.208.134/32 - local rPTn 100 0 5973
26255
207.49.208.135/32 - local rPTn 100 0 14058
870146
207.49.208.136/32 - local rPTn 100 0 51
397814
207.49.208.137/32 - local rPTn 100 0 21606
923951
207.49.208.138/32 - local rPTn 100 0 140
424022
207.49.208.139/32 - local rPTn 100 0 2206
823678
207.49.208.141/32 - local rPTn 100 0 88
947850
207.49.208.142/32 - local rPTn 100 0 8220
906460
207.49.208.143/32 - local rPTn 100 0 1188
895822
207.49.208.146/32 - local rPTn 100 0 2267
709353
207.49.208.147/32 - local rPTn 100 0 1065
760224
207.49.208.148/32 - local rPTn 100 0 169
901221
207.49.208.150/32 - local rPTn 100 0 124
794884
207.49.208.151/32 - local rPTn 100 0 42
922657
207.49.208.152/32 - local rPTn 100 0 56
929855
207.49.208.153/32 - local rPTn 100 0 7731
904661
207.49.208.156/32 - local rPTn 100 0 20
521031
207.49.208.158/32 - local rPTn 100 0 1351
897215
207.49.208.159/32 - local rPTn 100 0 43
490485
207.49.208.160/32 - local rPTn 100 0 1526
820079
207.49.208.163/32 - local rPTn 100 0 2435
728251
207.49.208.164/32 - local rPTn 100 0 1415
938853
207.49.208.165/32 - local rPTn 100 0 96
915858
207.49.208.166/32 - local rPTn 100 0 17454
919057
207.49.208.167/32 - local rPTn 100 0 353
856072
207.49.208.168/32 - local rPTn 100 0 17121
898614
207.49.208.169/32 - local rPTn 100 0 25019
834477
207.49.208.171/32 - local rPTn 100 0 2440
942531
207.49.208.172/32 - local rPTn 100 0 293
933454
207.49.208.173/32 - local rPTn 100 0 267
907608
207.49.208.175/32 - local rPTn 100 0 1599
493840
207.49.208.176/32 - local rPTn 100 0 90
123504
207.49.208.177/32 - local rPTn 100 0 14560
526085
207.49.208.178/32 - local rPTn 100 0 464
97070
207.49.208.179/32 - local rPTn 100 0 763
832148
207.49.208.181/32 - local rPTn 100 0 3093
901581
207.49.208.182/32 - local rPTn 100 0 938
714220
207.49.208.183/32 - local rPTn 100 0 0
509246
207.49.208.184/32 - local rPTn 100 0 67
881324
207.49.208.185/32 - local rPTn 100 0 415
789544
207.49.208.186/32 - local rPTn 100 0 55
527215
207.49.208.187/32 - local rPTn 100 0 3446
794482
207.49.208.188/32 - local rPTn 100 0 4729
874936
224.0.0.0/4 - mcast CP 0 0 0
1018566
224.0.0.5/32 - bh0 CP 0 0 0
1018566
224.0.0.6/32 - bh0 CP 0 0 0
1018566
224.0.0.9/32 - local CP 0 0 0
1018566
255.255.255.255/32 - ie0 CP 0 0 54846
1018566
ascend%
I hope the table is readable, It seems the age column wraps under the IP
# no matter how I space it. Fixed width seems to align the table.
Please let me know if these routes are normal, I've have not seen any of
our other routers with routes like this.
We have 4 Pipeline 130's in use at this same location for branch office
connectivity, and several more Pipeline75's at other customers, none of
which look like this. I would take the unit back to an older software
version but our FTP session problems have gone away. Other than the
extra routes things seem to be working well.
Any help is appreciated.
Thanks,
Scott Starbuck
Aobe Network Group
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>