PXE-E76 Bad Or Missing Multicast Discovery Address
Jan 30, 2013
I've installed a Windows Server 2008 R2 Enterprise Edition with ADDS, DNS and DHCP server.Everything is configured correctly and running fine when I use an independent network.When I uninstall the DHCP on the server and connect it to my primary network with a Linux router (ClearOS) handling DHCP i get an error message on the client computer when trying to boot with PXE."PXE-E76: Bad or missing multicast discovery address".What do I need to do to make this work with my Linux router? Some port that has to be forwarded internally from the router to the WDS server?
just ran a discovery on a large network and found 49 wireless controllers (5500, 4400 and 2000 series) and none of them are showing the controller serial number. They are all running 7.0.235.0 and I found no bugs that match this issue.
AP radio resets when the AP Multicast Mode IP is set 0.0.0.0 under the General Tab?
I rebuilt my lab controller and moved the management interface to a new subnet. Somehow, the AP Multicase Mode IP under the General Settings was removed. Afterwards, my AP's radios would reset every 2-3 minutes. After comparing my lab config to production, I noticed the IP was missing from that field. Setting the Multicast IP to 239.232.78.1 fixed the issue.
1)is there any methods to let LMS 4.2 discover Cisco devices based on specific ip like Loopback address ? coz in my Cisco devices i have more than ip address configured?
I have ADSL router WAG54G2.I both new mobile, I can't put the mobile MAC address in "Wireless MAC Filter" because it is started with 5C:...The answer is "The MAC address cannot be the multicast address".
Our church computer isp is WildBlue.They tested the satellite connection as well as the modem.Everything is fine from that end, however, I get a 'server not found' error message.I was told by WildBlue that they cannot see an ip address for the computer. How do I fix this so that we can have the internet back? The computer has WIN XP.
I have a stack of 3750's running IOS 12.2(25). "IP forward-protocal" command is configured, but the IP helper command is just not an option to put on an interface. Any have any idea of why that could be?
I know that very few people have their wireless controllers on version 7.4.100. But has any one noticed that the NAT IP address field in the management interface configuration menu is missing?, although it is mentioned as being present in the WLC 7.4 configuration guide. This would definitely affect Office-Extend.
One of our Cat5513 has been displaying a lot of the error message below:
%SYS-4-P2_WARN: 8/Invalid traffic from multicast source address 01:00:5a:52:4c:4d on port 8/58
The frequency of this is quite disturbing. What this error is about? Module no.8 is our Gigabit Ethernet WS-X5410. Can that multicast address be mapped to an IP address or unicast mac-addresS? How can i go about resolving this?
We are running LMS Prime 4.2.3 on a Softappliance. We have a Cisco Switch behind a Non Cisco Layer-3 Device. In the end host tabe we see only the MAC-Addresses of the host connected to this switch. No IP-Address. The corresponding IP-Addresses are in the ARP-Table of this non Cisco Layer-3 Device. The arp table can also be read by snmp. Is it possible to get the ip address in the UT End Host Table in such an environment?
I try to pass multicast traffic between two vrf on the same 3750 switch. I have IP services IOS and sdm template routing.
here is my config:
ip routing ! ip vrf vpn2 rd 1:1 mdt default 232.1.1.1 route-target export 1:1 route-target import 1:1
[code]....
Now I'm stuck - I don't know what to do to pass multicast traffic. Do I have any chance to run this config on 3750 chassis?Perhaps "Configuring Multicast VPN Extranet Support" document will be useful, but it concerns Catalyst 6500? [URL]
my system's network discovery is always off even when i try to put it on again it goes back off immediately...can it be related to the firewall settings or wat else can be preventing it from coming on?
I am having trouble getting 1142 LAP to find the controller. We are running an ASA 5505 at our main campus where the 5508 is located. Each Of our distribution centers have a PIX501 and from there about 3-5 AP's each. The AP's that were primmed before instalation work great, however we need the ability to get the other ones that were already installed and not finding controller to work with out cycling them through main campus. I have opened up UDP ports 12222-12223 and 5246-5246 with no luck.
we're evaulating the Cisco SM 4.2. After adding my ASA 5520 the Policies are discovered from the device except the RA VPN Policies.I tried to trigger the discovery process manually and i got this errormessage Please verify the device "IP address", "hostname", "domain name" and "port number" are correct, there is network connectivity between the CS Manager server and the device, and the device is configured to accept https connections, the device is running, and then retry this operation.which i don't understand because the other policies were retrieved just fine.
I have a problem discovering some ASA firewalls on a network. I have several ASA firewalls on this /24 network, but some of them I can't discover e.g 149.x.x.107 is discovered ok, but 149.x.x.20 I can't discover. It seems that it's not even trying to discover the devices I have problems with. Nothing is shown in the discovery log.
Whenever I select it and apply changes, then reopen, it has reverted back to the off position. I have removed all firewalls and software that could interact with it (disconnected it from the network whilst in this state). I have set the correct services to automatic as they should be. It is getting rather frustrating not being able to share my media across the home network. I can see and utilise other computers media but none can utilise said computers media
LMS 4.2, W2K8 R2.I was having an issue with discovery adding devices to with corrupt information (seemingly random strings of characters in several fields). While I was trying to clean this up a scheduled discovery kicked off and further exacerbated the issues I was having. Frustrated, I deleted all entries from the discovery schedule until I could get things cleaned up.
Now I want to go back and troubleshoot the discovery process. Trouble is, I can't get discovery to do anything anymore. I disabled all modules but CDP. I added a single seed IP address under the CDP configuration. This is the address of a 3560V2 switch that is not in DCR. When I started discovery it completed in about 2 seconds and didn't discover anything, including the seed device. So I added another 3560V2 as a seed device under global settings. Same results. Thinking that it had been working using scheduled discovery, I set up a schedule and kicked it off that way. Same results. Finally I added one of these seed devices to DCR and let LMS fully learn about it. Ran another discovery. Still no joy.
I started an SNMP debug on the seed devices before starting discovery. I see the SNMP get coming from LMS, the switches respond and the discovery completes with 0 devices discovered.CS Discovery.log contains no meaningful information. Only messages about "No appenders could be found for logger".
my customer is using Cisco Prime 4.1 as an Upgrade from LMS 4.0 and has made a discovery of a new added Cat 4506E with a Sup 7E and Modules.All the devices have been discovered, excepted the module WS-X4712-SFP+E.Is this card not supported yet ?I could not find any detailled and actual information about the support or not of this module, or about the conditions for the Module support it in Prime 4.1..How ist it possible to proceed to having this module discovered ?
We have just installed LMS 4.0.1 and started to discover parts of the network. After the discovery process finished successfully - 100+ new devices were added to DCR message - I was able to see the devices by clicking on their number but when I go to Inventory-Add/Import/Manage Devices I cannot see any device in the Group that I created.If I restart the CiscoWorks Daemon Manager process the newly discovered devices are added to the custom Group. This seems like a bug as I had a LMS 4.0 evaluation installation a few months ago and device discovery was working fine meaning the devices were added immediately to the Inventory.
i am installing a CWLMS 4.0 and everything was good until i have reached the discovery for the devices, i am dealing with a bank setup and the branches is connected using layer 3 MPLS, branches are located behind the ISP router, so as a cdp neighbor i cant see anything but the ISP router at my Core.
so i cant see the branches routers as neighbors to my (seed Device) Core, and i have tried to use the ping sweep and i could not reach them also. and also to add them manually as we were doing before in the earlier versions of CWLMS, using the Devices and Credintials, this option is removed from the LMS 4.0 as i have red in a document.
1- snmp is configured on all devices. 2- access-list is configured on all devices. 3- i am able to reach the LAN Devices without any problems and the configuration is the same on all of the devices.
We are running CiscoPrime LMS 4.1 and I have a problem with PingSweep in Device Discovery. Our company's branches connect to the main site through GETVPN. Discovery through CDP, Routing Table and ARP cannot be used based on the document written by Joseph Clarke [URL] and which is extremely useful. So the only available option is PingSweep.
The loopback interfaces of all the remote GETVPN devices are in the same IP range, so this was configured in Module Settings --> Ping Sweep in the Discovery.
Unfortunately none of the devices get discovered, even though there is icmp connectivity from the server to the loopbacks.
I am using lms 3.2.where I have added devices manually.Because discovery settings the device are taking some random ip updating the display and hostname.
I am using CISCO PRIME LMS 4.1 for manage my network, i ran a device discovery job using a ping sweep on the ip ranges of my network, ie 192.168.1.0/24, 192.168.2.0/24 and so on... the discovery found all my devices, but it discovered duplicate devices with illegal ip Addresses, i.e.,
ip device 192.168.1.255 S1 192.168.2.0 S1 192.168.2.1 S1 (the real address)
all in reachable status.
I don't understand why the program adds that repeated illegal addresses.. How can I run the device discovery to avoid this problem?
I have just installed prime 1.3 (brand new install), we have started a discovery job to find one switch (IP address), this job has so far come up with 311 credential failures and appears to be going through every 127.0.0.x IP address it can.Is there a way of stopping this job from running. Clicking on the Red X next to the name has no effect.
I have one questions regarding if C6509 suports "ip tcp path-mtu-discovery" ? apply this command to GRE interface on C6509? if yes, let me know what is the the IOS for that.
I have a client with a 2112 WLC and 1252AG radios. The clients work fine, but an SNMP management server can not reach any of the clients over the wireless. Before the WLC and new AP's were installed, they were running older Cisco Autonomous AP's and had no problems with SNMP. My monitoring system uses SNMP and it can reach the WLC just fine, so there doesnt appear to be any issues on the switched network. What can be blocking the SNMP on the WLC?
I have newly deployed a Prime Infrastructure (PI) in my network, and i want to add my wirless controller in it. I get an error SNMP time out whenever i add my controller to PI through SNMP.
There are default SNMP configurations in the controller and i am simply adding them in PI with their private/public SNMP string.
WLC 5508 is connected to my core switch and PI is connected to another switch which is directly connected to core switch via Layer 3.
Is there any configuration required to be done on the switch side.?
whats the difference between custom and standard discovery? There´s a line on the help page: "The Use Policy Configuration Settings radio button will be enabled only after adding a Default Credential Set Policy."The radio button is not enabled although I´ve two default credential sets and two default credential sets policy configuration.
we are running CiscoPrime LMS 4.1 and I have the following problem.I have configured SNMP Settings as shown below (the order of the targets is exactly as it is configured on the server):As can be seen we use three different read community strings. I also have exluded a bunch of IP ranges and IPs from the filter settings. When I manually start discovery everything works fine, meaning that all devices in the above ranges that need to be discovered are discovered as "reachable". The problem appears in the scheduled discovery (happens once daily). In that case only the devices with Read Community snmp1, get discovered as "reachable". All other devices with Read community snmp2 & snmp3, as well as those that are excluded in the filter settings, are discovered as "unreachable".The discovery uses DCR as seed and seed devices are also configured.I also have a problem with PingSweep in the discovery, but I will open another discussion so that I don't complicate this one too much.
I have noticed that our LMS does not collect any information about wireless users connected to autonomous access points, although I can see the mac address of the wireless users on the switch (2960) Trunk port connecting to the AP via CLI. I can also get the IP address from the core switch. Even after selecting 'Perform Data Collection' on the AP in the topology, the Wireless End hosts report remains blank.
I am trying to enable the option 'End host Discovery on Selected Trunks' in the 'Acquisition configuration in Trunk' menu and after selecting the switch where the AP resides and clicking 'show Trunk' I get the message 'there are no trunks in the device(s) selected', although there are several trunk ports on this switch, other than the one connecting to the AP. The switch and the AP are managed by LMS. We are facing this problem with all Autonomus APs. We do not use WLSE. Is there something missing to discover these Wireless hosts ?
I´m getting started on ciscoworks and i trying to configure a device discovery to start but i have some questions about how configure this tool exist 5 parameters that i have to configure to start the device discovery.
I want to add devices that found neighbors via CDP son in the configuring discovery module setting i choice that option In the configuring seed device setting i choose DCR as seed device that means those devices already in the DCR start discovering from those devices but you can add more seed devices how i can add a seed device ? with ip addres or something like this? and this device have to be in the DCR already or not? The configuring SNMP settings, this community correspond to what device? the devices that i want to add ? and in the field target name what ip adders have to be? and if i have different community of snmp in my devices what device and snmp community have to configure in this parameter
