Send netdisco-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Re: ND2 strange node behaviour (Mark Cooper)
   2. IPv6 support in netdisco ? (Andrew Daviel)
--- Begin Message ---
Looks like normal Cisco behaviour I have seen on chassis based and fixed format 
switches since 1999.  I never got a good answer from Cisco when I used to ask 
about it years ago.  Good luck and please share the answer if you get a good 
one.  Would be nice to know.

Thanks,Mark Cooper

*Cooper's Communications*
[email protected]




> On 30/5/2014 1:44 μμ, Alan Buxey wrote:
> 
> > That client device seems to be on the default native vlan. Not using 
> > seperate vlan for devices and mgnt? It may very well be a case of cam 
> > table exhaustion if it's one big flat l2 network. Check switch 
> > resources and the SDM profile in use on the switch.
> 
> Thank you Alan for your advice.
> 
> Yes, we are not using a separate vlan for management. We have a 
> relatively small network and we are far from table exhaustion. All 
> switches are Layer 2. Routing is done by a Cisco 3825 with multiple 
> interfaces.
> 
> Some (attempted) troubleshooting -always for the same node:
> 
> csw-astr0#sh clock
> 23:12:58.425 EET Fri May 30 2014
> csw-astr0#sh ip arp | incl 0004.0092.aa9d
> Internet  195.251.202.16         12   0004.0092.aa9d ARPA   Vlan1
> 
> So, the MAC address is in the arp table, but:
> 
> csw-astr0#sh mac-address-table address 0004.0092.aa9d
>            Mac Address Table
> -------------------------------------------
> 
> Vlan    Mac Address       Type        Ports
> ----    -----------       --------    -----
> 
> ...it is not available in the mac-address-table. If we ping the 
> associated IP address:
> 
> csw-astr0#ping 195.251.202.16
> 
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 195.251.202.16, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/9 ms
> 
> ...then the mac address shows up in the mac-address-table:
> 
> csw-astr0#sh clock
> 23:13:26.603 EET Fri May 30 2014
> csw-astr0#sh mac-address-table address 0004.0092.aa9d
>            Mac Address Table
> -------------------------------------------
> 
> Vlan    Mac Address       Type        Ports
> ----    -----------       --------    -----
>     1    0004.0092.aa9d    DYNAMIC     Fa0/3
> Total Mac Addresses for this criterion: 1
> 
> ...but after a few seconds, it is no more available:
> 
> csw-astr0#sh clock
> 23:13:45.167 EET Fri May 30 2014
> csw-astr0#sh mac-address-table address 0004.0092.aa9d
>            Mac Address Table
> -------------------------------------------
> 
> Vlan    Mac Address       Type        Ports
> ----    -----------       --------    -----
> 
> Yet, there is no problem with table space:
> 
>     csw-astr0#sh mac-address-table count
> 
>     Mac Entries for Vlan 1:
>     ---------------------------
>     Dynamic Address Count  : 26
>     Static  Address Count  : 0
>     Total Mac Addresses    : 26
> 
>     Mac Entries for Vlan 100:
>     ---------------------------
>     Dynamic Address Count  : 4
>     Static  Address Count  : 0
>     Total Mac Addresses    : 4
> 
>     Total Mac Address Space Available: 7418
> 
> Also:
> 
>     csw-astr0#show sdm prefer
>       The current template is "default" template.
>       The selected template optimizes the resources in
>       the switch to support this level of features for
>       0 routed interfaces and 255 VLANs.
> 
>        number of unicast mac addresses:   8K
>        number of IPv4 IGMP groups:        0.25K
>        number of IPv4/MAC qos aces:       0
>        number of IPv4/MAC security aces:  0.25K
> 
> Indeed, if I do a "ping 195.251.202.16" (either on the switch or from 
> another box) and then I IMMEDIATELY force a macsuck in ND2, then the 
> node (since it has been included for a short while -a few seconds- in 
> the MAC table) appears in ND2.
> 
> But why the particular MAC address is getting removed from the 
> MAC-Address-table so quickly? Any ideas will be appreciated!
> 
> Thanks,
> Nick
> 
> ------------------------------------------------------------------------------
> Time is money. Stop wasting it! Get your web API in 5 minutes.
> www.restlet.com/download
> http://p.sf.net/sfu/restlet
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
> 


--- End Message ---
--- Begin Message ---

I see on the website that IPv6 is "supported" in netdisco since version 1.1 or so.

How do I actually find IPv6 information ?

I just installed netdisco 2. I was hoping to find some Scope:Link information (fe80:: addresses) being used on our network, but I can't find anything - while Linux computers generate an address based on MAC address, and I can find that in netdisco, others e.g. Windows generate random addresses).

We have a Juniper EX8000 series router and Avaya switches. We don't have any global IPv6 outing configured yet, but we have been getting Scope:Link traffic including a flood from some broken Intel drivers.



--
Andrew Daviel, TRIUMF, Canada
Tel. +1 (604) 222-7376  (Pacific Time)



--- End Message ---
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to