I also agree with Rick's assessment of the situation. Out of curiosity, once the hosts connect, how are other network critical values farmed out to the connected hosts, such as the IP addresses of DNS or WINS servers? Do you use DCHP on this network, or do you manually configure these values in the connected hosts? pw ... View more

Do you have packet captures that show problems with session negotiation? pw ... View more

You may want to look at this command: ntp server x.x.x.x or, ntp server north-america.pool.ntp.org might work for you. Good luck, pw ... View more

A couple of thoughts here. First, this entry: interface FastEthernet0/0 description Yipes 10Mbps Connection ip address 66.xx.xxx.2 255.255.255.252 no ip proxy-arp ip nat outside ip virtual-reassembly ip route-cache flow speed 100 full-duplex no cdp enable Your description says 10Mbps, but your config says 100Mbps, which is right? Further, do you have proper link negotiation set up between switches. Specifically how is link speed and duplex set on the DLINK? Generally, on Cisco switches, it is better to hard code the values if they can be properly set for a non-changing link, such as a switch to switch connection. On the other hand, non-Cisco switches may not always play well with Cisco and sometimes are more/better optimized for plug and play. You could possibly have speed and duplex mismatches on the DLINK switch. You have not posted the config, so it is hard to say. Also, it might be useful to throw both switches into 100Mbps half duplex mode and pop a sniffer (via a 100mbps hub) in the middle of the mix and see what is happening. Capture the frames and see if the two are playing nicely with each other. Good luck, pw ... View more

When you say you checked the bandwidth on these links, how did you perform this check? Specifically, what measurement tool did you use? When you performed the check with the tools you used, did you account for header overhead and session negotiation (if using TCP as an underlying connection protocol)? Did you attempt to use TTCP as a measurement tool for your available bandwidth? When measuring available bandwidth on a line, all headers, CRCs/checksums, etc., are generally not counted in the computed speed of downloads, but they do consume the usable bandwidth. pw ... View more

You are correct, configuration of dense mode is simpler, hence the reason that many use it first. There are design considerations when employing multicast in a network that should be looked at before optiing for one version over another. Here is an excellent article by Pete Welcher that covers PIM dense mode and what it is all about and the design considerations of using it: http://www.netcraftsmen.net/welcher/papers/multicast02.html Likewise, Pete wrote another article about PIM sparse mode and the pros and cons of using it: http://www.netcraftsmen.net/welcher/papers/multicast03.html Both are excellent articles that will weigh the relative advantages and disadvantages of using both methods. It's a good read and it may help on what you are trying to do. pw ... View more

Okay, since I do not see 224.0.1.39 in your multicast routing table, it validates that you do not have anyone in the rp-announce group, so it stands to reason you would not see any traffice on the RPlistening group. Validate this with a "show ip mroute count" command and see how many packets are sent or received in that group. My guess would be zero, hence inactive. The next better question would be, why you elected to go with dense mode? Do you anticipate having a lot of multicast listeners for the multicasts you send? Any particular reason for not going with sparse-dense mode? Just curious. pw ... View more

http://www.cisco.com/warp/public/129/isdn_disc_code.html If I read the disconnect code right, it would seem that, "The switch receives the ISDN number in the correct format. However, the number does not belong to destination equipment." That almost sounds like the configured number on your router is not spitting back a result the telco switch expects and is unhappy and disconnects the circuit. If it were a DSL connection, I would say throw a hub between the router and the ethernet interface and try to capture the PPPoE traffic, but it is a little harder with ISDN unless you have a WAN sniffer. I am not sure what type of 2500 series router you have or what version of code you are running, but I have this running on my 2520: 2520>sh ver Cisco Internetwork Operating System Software IOS (tm) 2500 Software (C2500-JS-L), Version 12.2(5), RELEASE SOFTWARE (fc1) Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Wed 12-Sep-01 09:09 by pwade Image text-base: 0x03078B98, data-base: 0x00001000 ROM: System Bootstrap, Version 11.0(10c)XB2, PLATFORM SPECIFIC RELEASE SOFTWARE (fc1) BOOTLDR: 3000 Bootstrap Software (IGS-BOOT-R), Version 11.0(10c)XB2, PLATFORM SPECIFIC RELEASE SOFTWARE (fc1) 2520 uptime is 8 minutes System returned to ROM by power-on System image file is "flash:c2500-js-l.122-5.bin" cisco 2520 (68030) processor (revision M) with 14336K/2048K bytes of memory. Processor board ID 07945310, with hardware revision 00000003 Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. Basic Rate ISDN software, Version 1.1. 1 Ethernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 2 Low-speed serial(sync/async) network interface(s) 1 ISDN Basic Rate interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read ONLY) Configuration register is 0x2102 Keep in mind, this is running the enterprise feature set, also known as the "kitchen sink version" - it's in there. That is not to say that the usability of the IOS stopped for 2500s at 12.2(5), but my guess is that if you booost the gain on your DRAM to the max allowed, you might be able to run that version of IOS. It just takes a while to load. pw ... View more

Recheck your legend/header data for this output: Entry Flags: C - Directly Connected S - Signal IC - Internal Copy X - Inactive D - Dormant, * - MFIB special entry Interface Flags: A - Accept F - Forward S - Signal IC - Internal Copy NP - Not Platform fast-switched Now if your real question was, "what does inactive mean?" I would say that represents a path that was checked using "Reverse Path Forwarding" and was determined to be a path that is not needed on the multicast distribution tree to ensure all multicasts enabled hosts receive the multicast. In short, nobody is yet listening on VLAN 600 for either 224.0.1.40 (cisco-rp-discovery) or 234.74.74.74 (some type of multicast app you are running) multicast packets. To check this, when you do a "show ip mroute", does 224.0.1.40 show up in the multicast routing table? If so, what does the entry look like? pw ... View more

AOC servicing for NET3 switches seems to be in the code as early as the 11.3 release. I am guessing that maybe there was something buggy about that specific code train you have running on the 2500. Just to get it to work, you might want to try playing with these commands and see if the IOS will respect them and act on them: dialer idle-timeout 300 (set it there just for test purposes) dialer isdn short-hold 300 (set it there just for test purposes) Make sure to remove these after testing so your ISDN bills do not increase. If the IOS does respect these commands, I can only conclude that maybe the default was set to something other than the default (120 seconds). Since you and I don't get access to the source code, they why part will remain a mystery ;-) If that still does not fix it, you may wish to consider temporarily loading a different version of IOS, just to see if the version you have is just plain buggy for this feature. I am guessing a good place to start would be a known good value of IOS 12.2(17a) if you have it. Of course, if this is a production network, that might be a little harder to do (possibly off hours maybe?) pw ... View more

Well, I can only conclude one of a couple of things. 1. THe BPDUs you captured on other parts of the network were also PVST+ frames but you may have missed that on inspection of the capture. or, 2. Somebody has disabled PVST+ and is running MISTP (mono instance spanning tree protocol) in anticipation of having/joining an 802.1Q topology. By default, PVST+ is on by default for Catalyst 6000 switches. Maybe you could capture some of these other frames that are on other parts of the switched network that have a different destination address and no mention of PVST+ ? Also, if you can access the console of the CAT 6000, try this command: show spantree X (where X is each VLAN) The output should look something like this: Console> (enable) show spantree 1 VLAN 1 Spanning tree mode PVST+ Spanning tree type ieee . Bridge ID MAC ADDR 00-d0-00-4c-18-00 Bridge ID Priority 32769 (bridge priority: 32768, sys ID ext: 1) Bridge Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec Then try running this command: show spantree mistp-instance active See if you get any output like this: Console> (enable) show spantree mistp-instance active Instance 1 Spanning tree mode MISTP-PVST+ Spanning tree type ieee Spanning tree instance enabled Designated Root 00-d0-00-4c-18-00 Designated Root Priority 32769 (root priority: 32768, sys ID ext: 1) Designated Root Cost 0 Designated Root Port none VLANs mapped: 6 Root Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec Bridge ID MAC ADDR 00-d0-00-4c-18-00 Bridge ID Priority 32769 (bridge priority: 32768, sys ID ext: 1) VLANs mapped: 6 Bridge Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec If so, maybe somebody inadvertently turned on MISTP? pw ... View more

Whoa, not so fast! If this is a point to point link (versus a switched WAN link such as frame relay), then you are dealing iwth a garden hose, in effect. The water comes in one and and can only go out the other end. Because of this, the need for a MAC address is only for management purposes, not addressing. As such, the protocols that can be used for a point-to-point serial link are PPP and Cisco's HDLC (among others). Look at each: PPP header: Flag—A single byte that indicates the beginning or end of a frame. The flag field consists of the binary sequence 01111110. Address—A single byte that contains the binary sequence 11111111, the standard broadcast address. PPP does not assign individual station addresses. Control—A single byte that contains the binary sequence 00000011, which calls for transmission of user data in an unsequenced frame. A connectionless link service similar to that of Logical Link Control (LLC) Type 1 is provided. (For more information about LLC types and frame types, refer to Chapter 16.) Protocol—Two bytes that identify the protocol encapsulated in the information field of the frame. The most up-to-date values of the protocol field are specified in the most recent Assigned Numbers Request For Comments (RFC). Data—Zero or more bytes that contain the datagram for the protocol specified in the protocol field. The end of the information field is found by locating the closing flag sequence and allowing 2 bytes for the FCS field. The default maximum length of the information field is 1,500 bytes. By prior agreement, consenting PPP implementations can use other values for the maximum information field length. Frame check sequence (FCS)—Normally 16 bits (2 bytes). By prior agreement, consenting PPP implementations can use a 32-bit (4-byte) FCS for improved error detection. ***NOTE - The address field does not assign single station addresses! Now for HDLC: http://www.wildpackets.com/images/compendium/Cisco_HDLC_Frame.gif In Cisco HDLC (cHDLC), the Address field is always one byte and takes only one of two values: 0x0F (unicast), or 0x8F (broadcast). These protocols (PPP and HDLC) sit at layer 2 of the OSI model. G.703 is effectively a layer 1 (physical layer) standard. It basically defines how those 1's and 0's will go out on the wire in a manner that is recognizable to the distand physical layer device, such as a CSU/DSU. Each layer functions on top of the other layers and they have dependencies. IP (Internet Protocol) will not work unless some layer 2 protocol is properly functioning, such as Ethernet, token ring, LAPB, PPP, or HDLC. These layer 2 protocols are not much good unless the layer 1 protocols are working properly. G.703 is a layer 1 protocol. Expect to see a web page transmitted over a leased line by taking application layer output (HTTP) and pasing it down to TCP (Transmission Control Protocol), that passes it to IP, which passes it to HDLC, which might use G.703 as the transmission standard at the physical layer. Does this make sense? ... View more

See if this is relevant: http://www.microsoft.com/technet/security/bulletin/fq00-015.mspx pw ... View more

Does this help on the error codes? http://www.cisco.com/en/US/tech/tk713/tk730/technologies_tech_note09186a0080094a41.shtml#topic1 pw ... View more