So I took the plunge. I sat down with our network admin and scetched out
a plan for turning on OSPF. Background: PM3s running ComOS 3.8. Each PM3 has
48 modems and receives calls on PRIs.
Here's what we came up with. All dialup would come from a dedicated
Class-C block. All the Ethernet interfaces are on a /29 subnet. After a
little tinkering, I can see neighbors:
sho ospf ne
Inter- Last MD5
face Area Neighbor State Pri IP Address Hello ID
------ --------------- --------------- -------- --- --------------- ----- ---
ether0 0.0.0.1 132.241.60.129 Full/DR 1 132.241.60.241 2 N/A
The cisco seems to know what to do with packets within the PM3's Assigned
Address block. However, when I do a traceroute, I see:
traceroute 132.241.249.129
traceroute to 132.241.249.129 (132.241.249.129), 30 hops max, 20 byte packets
1 john-parker-e01.net.CSUChico.EDU (132.241.67.1) 2 ms 1 ms 1 ms
2 132.241.60.243 (132.241.60.243) 2 ms 1 ms 1 ms
3 132.241.60.241 (132.241.60.241) 2 ms 2 ms 2 ms
4 132.241.60.243 (132.241.60.243) 2 ms 2 ms 2 ms
5 132.241.60.241 (132.241.60.241) 2 ms 2 ms 2 ms
...
27 132.241.60.241 (132.241.60.241) 9 ms 8 ms 8 ms
28 132.241.60.243 (132.241.60.243) 8 ms 8 ms 8 ms
29 132.241.60.241 (132.241.60.241) 9 ms 8 ms 9 ms
30 132.241.60.243 (132.241.60.243) 9 ms 8 ms 9 ms
*** max ttl expired before reaching pm3dyn129.dip.CSUChico.EDU (132.241.249.129)
I can see that I'm close. The PM3 is rejecting the packets, even though
they fall within the block:
Assigned Address: 132.241.249.128 (Pool Size 48)
There are two areas. The PM3(Only one for the moment), is in area 1:
sho ospf ar
Stub
Authentication Area Default
Area Network Range Type ID Key Type Cost
--------------- ------------------ ---- --- ---------------- -------- -------
0.0.0.1 *132.241.249.0/24 **** Stub Not set
*132.241.60.240/29
The address for ether0 is 132.241.60.243. Here are the routes:
sho ro
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
0.0.0.0 0 132.241.60.241 local NS 1 ether0
132.241.60.129 32 132.241.60.241 ospf/IA HD 2 ether0
132.241.60.240 29 132.241.60.243 local NL 1 ether0
Here are the ospf Links:
sho ospf li
Router Links for Area 0.0.0.1
Link ID Advertising Router Sequence TOS Ext Age
--------------- ------------------ ---------- --- --- ----
132.241.60.129 132.241.60.129 0x8000006c No No 1147
132.241.60.243 132.241.60.243 0x8000002d No No 1056
Network Links for Area 0.0.0.1
Link ID Advertising Router Sequence TOS Ext Age Mask
--------------- ------------------ ---------- --- --- ---- ----
132.241.60.241 132.241.60.129 0x80000004 No No 1147 29
Summary Links from others for Area 0.0.0.1
Link ID Advertising Router Sequence TOS Ext Age Mask
--------------- ------------------ ---------- --- --- ---- ----
0.0.0.0 132.241.60.129 0x80000004 No No 370 0
132.241.60.129 132.241.60.129 0x80000068 No No 370 32
Summary Links from ourself for Area 0.0.0.1
Link ID Advertising Router Sequence TOS Ext Age Mask
--------------- ------------------ ---------- --- --- ---- ----
It looks like the PM3 is not advertising anything. Is that a correct
assumption? That doesn't look right to me. Shouldn't the PM3 be advertising
something for the pool?
I'm clearly missing something here and it's probably *very* simple. Can
someone give me a clue please? Thanks!
Chris...
-- What's the point?PGP fingerprint: 063FCE320681C336 78C164FC9B2F91EA - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>