Wired Intelligent Edge

 View Only
Expand all | Collapse all

HP-ProCurve 2910-48G al Monitor Port only sees egress traffic

This thread has been viewed 0 times
  • 1.  HP-ProCurve 2910-48G al Monitor Port only sees egress traffic

    Posted May 07, 2013 03:50 AM

    Hi all,

     

    I am having trouble setting up port mirroring. I have a HP-ProCurve 2910-48G al and I have setup port mirroring of multiple ports (being members of different VLANs). The configuration is attached below. The problem is that I can only see egress traffic on the mirror ports (e.g. traffic leaving on Port 31) using Wireshark on the monitor port (port 41).

     

    Any ideas? From the manual I understand that the VLAN membership of the monitor port does only affect wether monitored traffic leaves tagged or untagged on the mirror port. I think it should not affect ingress/egress mirroring. Or am I missing something here?

     

    Best Regards,

      Daniel

     

    Running configuration:

    ; J9147A Configuration Editor; Created on release #W.14.38

    hostname "hp2910"
    module 1 type J9147A
    mirror-port 41
    interface 1
       name "A"
    exit
    interface 2
       name "B"
    exit
    interface 11
       name "C"
    exit
    interface 12
       name "D"
    exit
    interface 21
       name "E"
    exit
    interface 31
       name "F"
    exit
    interface 32
       name "G"
    exit
    interface 46
       disable
    exit
    interface 48
       name "H"
    exit
    ip default-gateway 192.168.1.1
    vlan 1
       name "DEFAULT_VLAN"
       untagged 42-45
       no untagged 1-41,46-48
       no ip address
       exit
    vlan 101
       name "VLAN101"
       forbid 11-45,47
       untagged 1-10
       tagged 46,48
       no ip address
       exit
    vlan 102
       name "VLAN102"
       forbid 1-10,21-45,47
       untagged 11-20
       ip address 10.1.17.6 255.255.255.0
       tagged 46,48
       exit
    vlan 103
       name "VLAN103"
       forbid 1-20,31-45,47
       untagged 21-30
       tagged 46,48
       no ip address
       exit
    vlan 111
       name "VLAN111"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 112
       name "VLAN112"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 113
       name "VLAN113"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 114
       name "VLAN114"
       forbid 1-30,37-40,42-46
       untagged 31-36,41
       tagged 47-48
       no ip address
       exit
    vlan 1101
       name "VLAN1101"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 1102
       name "VLAN1102"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 1103
       name "VLAN1103"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 1104
       name "VLAN1104"
       forbid 1-45,47
       tagged 46,48
       no ip address
       exit
    vlan 115
       name "VLAN115"
       forbid 1-36,41-46
       untagged 37-40
       tagged 47-48
       no ip address
       exit
    vlan 116
       name "VLAN116"
       tagged 47-48
       no ip address
       exit
    interface 31-32,37-40
       monitor
       exit
    no web-management
    ip timep manual 192.168.1.11
    snmp-server community "XXXXX" operator
    snmp-server contact "Me"
    spanning-tree config-name "abcd"
    spanning-tree instance 1 vlan 101-103 111-113 1101-1104
    spanning-tree instance 2 vlan 114
    spanning-tree instance 2 priority 4
    spanning-tree priority 11
    password manager



  • 2.  RE: HP-ProCurve 2910-48G al Monitor Port only sees egress traffic

    Posted May 08, 2013 02:42 AM

     

    interface 31-32,37-40
       monitor all both



  • 3.  RE: HP-ProCurve 2910-48G al Monitor Port only sees egress traffic

    Posted May 14, 2013 11:31 AM

    Hi Vince_Whirlwind,

     

    thanks for your answer. Unfortunately the switch does not allow this command. On this model only "monitor" is allowed, it does not take any additional parameters.

     

    Any other ideas?

     

    Best Regards,

      Daniel