[e-nsp] Extreme switch "show iparp" - IP Rejected

[root net]

The secondary IP is only configured because it's the /30 between the
provider and that BGP peering router.

interface Port-channel1.2
 description transport vlan
 encapsulation dot1Q 2
 ip address 192.168.0.1 255.255.255.224

interface Port-channel1.3
 description provider vlan
 encapsulation dot1Q 3
 ip address 192.168.1.1 255.255.255.252 secondary
 ip address 172.16.0.2 255.255.255.252

One thing I forgot to mention is that VLAN transport is a L3 VLAN. This was
really only to ping Switch C on VLAN transport.


On Fri, Jul 20, 2012 at 3:12 AM, Robert Lister <robl at lentil.org> wrote:

>
> Config snippets may help to work this out.
>
> By 'secondary IP' how is this configured on the cisco, and why?
>
> Rob
>
> --
> Robert Lister
>
>
> Provider assigned a /30 say 172.16.0.0/30 -> his IP is say 172.16.0.1/30
> Switch A is not assigned an IP on the /27. This switch is simple all L2
> (tagged/untagged or trunk/access ports)
> Switch B is assigned an IP from a /27 say 192.168.0.4/27
> Switch C is assigned an IP from a /27 say 192.168.0.2/27
> Main Router is assigned an IP from a /27 say 192.168.0.1/27 and the
> secondary IP is 172.16.0.2/30
>
>
> sh iparp
> Destination     Mac                Age Static  VLAN    [VID]   Port
> 192.168.0.1  mac-address-here    0   NO  vlan-name-here  [0002]  1
>      Dynamic Entries:        1              Static Entries:       0
>      Pending Entries:        0
>          Out Request:       16                Out Response:      11
>           In Request:     1875                 In Response:      19
>       Proxy Answered:        0
>             Rx Error:        0                 Dup IP Addr:       0
>       Rejected count:      480                 Rejected IP: 172.16.0.2
>        Rejected Port:        1                Rejected I/F: transport
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/extreme-nsp/attachments/20120720/4b6449bc/attachment.html>