DX Application Performance Management

 View Only
Expand all | Collapse all

TIM Interface Configuration issue

  • 1.  TIM Interface Configuration issue

    Posted Apr 15, 2016 06:19 AM

    Hi,

     

    We have done with the fresh installation of TIM 10.0 .

    Lunix team has assigned interface to get the traffic data.

    eth0 is the management and eth1 is the monitored port.

    if they are assigning different I'p and different gate ways the server is getting hung(Putty is getting inactivated.

    If they disable the eth1 it will work fine.

     

    Can you please suggest us if we can use different I'p and same gateway for both eth0 and eth1.Or else please suggest us what need to be done.

     

    ---------------------------------------------------------------------------------------

    [root@timdcblr01 network-scripts]# cat ifcfg-eth

    ifcfg-eth0  ifcfg-eth1

    [root@timdcblr01 network-scripts]# cat ifcfg-eth0

    DEVICE=eth0

    BOOTPROTO=none

    HWADDR=40:f2:e9:38:31:50

    IPV6INIT=no

    NM_CONTROLLED=no

    ONBOOT=yes

    TYPE=Ethernet

    UUID="de63b628-5df0-46da-812a-d474495fbf2a"

    IPADDR=172.16.11.163

    NETMASK=255.255.255.192

    GATEWAY=172.16.11.129

    DNS1=172.16.11.136

    USERCTL=no

    [root@timdcblr01 network-scripts]#

     

    -----------------------------------------------------------------------------------

    [root@timdcblr01 network-scripts]# cat ifcfg-eth1

    DEVICE=eth1

    BOOTPROTO=none

    HWADDR=40:f2:e9:38:31:51

    IPV6INIT=no

    NM_CONTROLLED=yes

    ONBOOT=yes

    TYPE=Ethernet

    UUID="c91d2854-1126-48e4-a3f1-373b1af11388"

    USERCTL=no

    IPADDR=10.25.1.31

    NETMASK=255.255.255.192

    GATEWAY=10.25.1.1

    [root@timdcblr01 network-scripts]#

     

     

    Thanks.



  • 2.  Re: TIM Interface Configuration issue

    Posted Apr 15, 2016 06:40 AM

    Hi Sangamesh,

     

    You don't need IP on monitoring interface.

     

    Regards,

    Mukesh Singh

    On Apr 15, 2016 3:49 PM, "sangameshk" <



  • 3.  Re: TIM Interface Configuration issue

    Posted Apr 15, 2016 07:00 AM

    Hello Mukhesh,

     

    Thanks for your suggestion.We have commented the IP address,gateway for the same.

    PFB:

    [root@timdcblr01 network-scripts]# cat ifcfg-eth1

    DEVICE=eth1

    BOOTPROTO=none

    HWADDR=40:f2:e9:38:31:51

    IPV6INIT=no

    NM_CONTROLLED=yes

    ONBOOT=yes

    TYPE=Ethernet

    UUID="c91d2854-1126-48e4-a3f1-373b1af11388"

    USERCTL=no

    #IPADDR=10.25.1.31

    #NETMASK=255.255.255.192

    #GATEWAY=10.25.1.1

    =============

    [root@timdcblr01 network-scripts]# ifconfig

    eth0      Link encap:Ethernet  HWaddr 40:F2:E9:38:31:50

              inet addr:172.16.11.163  Bcast:172.16.11.191  Mask:255.255.255.192

              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

              RX packets:26394344 errors:0 dropped:0 overruns:0 frame:0

              TX packets:30993423 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:1000

              RX bytes:5022971983 (4.6 GiB)  TX bytes:32028466222 (29.8 GiB)

              Interrupt:17 Memory:c1a80000-c1aa0000

     

     

    eth1      Link encap:Ethernet  HWaddr 40:F2:E9:38:31:51

              UP BROADCAST MULTICAST  MTU:1500  Metric:1

              RX packets:405671036 errors:0 dropped:0 overruns:0 frame:0

              TX packets:175067 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:1000

              RX bytes:381089219609 (354.9 GiB)  TX bytes:11221085 (10.7 MiB)

              Interrupt:18 Memory:c1980000-c19a0000

     

     

    lo        Link encap:Local Loopback

              inet addr:127.0.0.1  Mask:255.0.0.0

              UP LOOPBACK RUNNING  MTU:65536  Metric:1

              RX packets:133606 errors:0 dropped:0 overruns:0 frame:0

              TX packets:133606 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:0

              RX bytes:11476861 (10.9 MiB)  TX bytes:11476861 (10.9 MiB)

     

    [root@timdcblr01 network-scripts]#

     

    =============

     

    Error:It's showing as "No data on network interface "eth1".

    Can you please let me know what has to be done here.

     

    Thanks.



  • 4.  Re: TIM Interface Configuration issue

    Posted Apr 17, 2016 08:51 AM

    Hey

    Eth 1 should be non IP mirror port.

    Regards

    Vinay Nayak



  • 5.  Re: TIM Interface Configuration issue

    Broadcom Employee
    Posted Apr 17, 2016 09:39 AM

    Hi: You should probably open a case if the queries provided cannot help get to resolution. I would look at your interfacefilters.xml to see if set up right, and review your apmpacket logs. Also check your web server filters Thanks Hal German



  • 6.  Re: TIM Interface Configuration issue

    Broadcom Employee
    Posted Apr 17, 2016 06:13 PM

    Thanks Hal,

    There is already an open case 00348367 that I am helping puran02 with.

    Sangamesh, I will reply from the case.

     

    Thanks

    Lynn



  • 7.  RE: Re: TIM Interface Configuration issue

    Posted Jan 30, 2020 02:19 PM
    Hi team,

    currently have this same problem. Did they identify the problem?

    Thanks for the help with this topic.
    Richard



  • 8.  RE: Re: TIM Interface Configuration issue
    Best Answer

    Broadcom Employee
    Posted Jan 31, 2020 08:10 AM

    Configure the eth1 file file (/etc/sysconfig/network-scripts/ifcfg-eth1

    DEVICE=eth1
    BOOTPROTO=none
    HWADDR=40:f2:e9:38:31:51
    IPV6INIT=no
    NM_CONTROLLED=no
    ONBOOT=yes
    TYPE=Ethernet

    This will put the network interface active, and apply no boot protocol (bootp/dhcp etc.) and make sure the network manager does not touch it.




  • 9.  RE: Re: TIM Interface Configuration issue

    Posted Feb 04, 2020 02:14 PM
    Hi Jörg,
    By deleting the line associated with mac address, and restarting the interface, the problem was resolved.
    Thanks
    Richard



  • 10.  RE: Re: TIM Interface Configuration issue

    Broadcom Employee
    Posted Feb 05, 2020 03:52 AM
    That surprises me. usually the Mac-Address is used to actually assign the Mac to the specified Interface name. In this case 
    40:f2:e9:38:31:51 will be bound to "eth1".

    The behavior has  probably changed over time. Thx for the heads-up :)