Loopback address as management address

Hi
Can I create loopback interfaces on all my layer-3 capable switches and use this address to manage all my switches instead of using vlan 1 as management vlan.what exactly i mean is
I have a 7200 router and ten 3750 switches connected to it. So can i create loop back on all my switches and 7200 and use this address to manage all the switches.
Is this possible. If so is there any disadvantage in doing so. Thanks for your help.

1) It means all loopback address in each device should be different. loopback interface just like a logical interface in a device.
2) VLAN 1 is default and built-in VLAN in a switch, we normally will create another VLAN for the management purpose only. You can assign the management VLAN to a port then this port will only be the management segment connection or include the management VLAN in the trunk to other devices.
In real situation, many providers use loopback address for the management and routing ID due to this interface never down. And you can assign separated subnet for the management segment w/o require to use production/data network subnet.
Hope this helps.

Similar Messages

  • Connect to switch loopback address

    Hello,
    I have a loopback address on swich A, also switch A connects to switch B through a trunk.  Switch B has 3 SVI vlans that are routed thru eigrp.  What I want to do is connect to switch A to loopback IP address. I tried a static route but did not work can connect to loopback address.  The config for switch A is loopback address is 192.168.137.6 255.255.255.255. On swich B one switch SVI address is 192.168.136.1 255.255.255.128 and eigrp  routes 192.168.136.1 thru network 192.168.136.0.  Can I use a static route from loopback address to SVI address 192.168.136.1 I tried that did not work. I just want to configure something only on switch A to connect  to loopback address for management, any suggenstions what will work and with what switch commands?
    Thanks,

    I am not fully understanding the environment that you describe and so do not fully understand your issue. But based on what I think that I do understand it seems to me that it should be possible to configure a host specific static route on switch B that would allow you to connect to the loopback on switch A, assuming that switch A has an IP address other than the loopback which is reachable from switch B. If this does not seem to adequately address your question then please provide clarification of your question.
    HTH
    Rick

  • Change the Loopback address in Linux

    Hi,
    Please can you tell me how to change the Loopback address in Linux.

    I wanted to change the loopback address and give a new IP address to my machine this is because I'm running Oracle10g on Linux in a virtual machine,I wanted to install Oracle 11g in another machine and enable communication between these machines please advice.

  • Virtual Hosts, lookupd and loopback address

    For days I've been trying to install and configure MySQL, phpMyAdmin and virtual hosts, but I just seem to be digging myself a deeper hole. I decided to focus on virtual hosts first and learned how to modify my httpd.conf, hosts and NetInfo files, only to discover that I also have to modify something called lookupd, which I can't even find.
    I posted a rather detail query at http://discussions.apple.com/thread.jspa?messageID=4232285#4232285
    and received this reply:
    [QUOTE]I'm not real sure it applies to virtual domains, but if you want your local machine to redirect URLs to a local domain you need to set up lookupd. . . . As it is, your browser is not even finding Apache because you have no DNS server. As an expedient alternative most people use the loopback address with a custom port number, but you are more demanding than that.[/QUOTE]
    Maybe you should repost in the UNIX section and use a better subject line. This is pretty geeky stuff.[/QUOTE]
    So is it true that I've been beating my brains out when there's a simpler method involving a loopback address with a custom port number? If so, can someone tell me how to do it or direct me to a tutorial? If, instead, I have to modify this lookupd file, how do I find it? I can't find it with Spotlight, and I haven't been able to locate it with TextWrangler yet.
    Thanks!

    You should ask this question at http://discussions.apple.com/forum.jspa?forumID=735&start=0

  • I don't use a proxy server to connect to the internet, but Firefox automatically configures itself to use the loopback address.

    I have a direct connection to the internet and don't use a proxy server. Every few weeks, Firefox automatically resets itself to be configured to use a proxy server at the loopback address (127.0.0.1). Manually changing it back to "No proxy" works, but I have to do so each time I open the browser or even a new tab. The only fix I can find is to create a new profile which gives me a new, clean install of FF, but then I lose all my add-ons. This has happened repeatedly now and it's extremely frustrating. I have scanned for malware but have not found any problems.

    hello rjlasser, first of all please make sure that none of your extensions is causing the issue (some youtube censorship circumvention addons also make use of proxies for example).
    otherwise please refer to [[How to fix preferences that won't save]] for some common solutions.

  • Does loopback address of a router have a vlan??

    hi all,
    i need to know if the interface IP for BGP link and the loopback address of router have a vlan for them or not??
    is yes, then how to check that?

    Peter
    While I basically agree with your response I would propose one refinement. If we are looking at the physical Ethernet interface of a router and if that interface is connected to a switch access port then there is certainly a VLAN associated with the switch side. And one might then also say that the VLAN is associated with the router physical interface.
    Perhaps another way to look at it starts from the fact that a defining characteristic of a VLAN is that it defines a layer 2 broadcast domain. A router physical interface also defines a layer 2 broadcast domain.
    HTH
    Rick

  • Lms discovery: loopback address

    Hi,
    I need to discover some new devices which are configured with several loopback interfaces. The problem is that the loopback interface used for Administration is not the one with the highest IP address (as I understood that it is the process followed by the discovery process).
    If I use "resolve by name" it takes the ip address discovered by CDP process (which is not the good one also). If I use the "resolve by loopback address", it takes the highest IP address of the loopack interfaces, chich is also not the good one.
    How can I solve this problem without turning off the automatic discovery process which is quite usefull

    Here is a good document written by Joe on Discovery process that explains it in detail.
    https://supportforums.cisco.com/docs/DOC-9005#Use_LoopBack_Address

  • Getclientinfo java bean returns loopback address

    I downloaded the getclientinfo java bean from OTN.
    Calling the form from any Window NT client within our intranet returns an IP address of 127.0.0.1.
    Is this correct?
    I don't intend to use the form on the web, just on the intranet.
    I tried calling it from an old SCO 7 box and got the correct value!!
    Help!

    If the PJC is not signed (or more likely the certificate is not imported on the client) then it returns the loopback rather than the real IP address

  • Cannot use loopback address in jmf audio receiver

    Hello, i am using the code from http://java.sun.com/products/java-media/jmf/2.1.1/solutions/AVReceive.html
    about transmitting and receiving audio data. It works fine but if i use a 127.0.0.1 address the receiver cannot connect to the audio streamer. Any idea?

    Yup. This will not work. I've tried with 127.0.0.1 and 0.0.0.0.. Both of them dont work..

  • How is NTP reply routed when requesting router uses loopback as source address

    The Cisco NTP Best Practices White Paper and DISA STIGs recommend setting the NTP source address to a loopback interface (e.g. "ntp source loopback0").
    But this only seems to work if the requesting (NTP client) router is the default gateway for the NTP server. 
    Specifically, the NTP server will attempt to reply to the requesting router's loopback-based source address (taken from the NTP request packet).  Since that address will always be non-local from the perspective of the NTP server, the NTP server will encapsulate the reply in a Layer 2 frame addressed to its default gateway.  If the gateway was the source of the original NTP request, that should work.  But in most other situations that gateway won't know how to reach a loopback-based address, and will discard the reply.
    I have verified this in tests with routers running both 12.4 and 15.1 releases (and NTP debugging enabled).  When the NTP source is a loopback address, NTP replies never reach the requesting router.  With the default NTP source address (i.e. based on the exit interface) everything works fine.
    Obviously, you could employ workarounds, such as static routes or injecting loopback addresses into your routing protocols.  But that seems uglier than leaving NTP source addresses at their defaults.
    Why is this "best practice" so commonly advocated without mention of some significant caveats regarding routing?  Am I missing something? 
    Thanks,
      Mark

    Michel:
    Thanks for the response.  Actually, I understand what kind of routing workarounds could allow NTP to function in spite of this "best practice."  But I am mystified as to why a Cisco "NTP best practice" paper (http://www.cisco.com/en/US/tech/tk869/tk769/technologies_white_paper09186a0080117070.shtml) and various security policies would call for setting a loopback address as the NTP source when that practice will often cause more problems than it solves.
    The stability of a loopback address is nice when that address is used to uniquely identify the platform for a routing protocol or syslog.  A loopback-based source address can also simplify ACL management, since that address won't change if an interface or link failure forces the router to send traffic from a different interface.  But I keep seeing security configuration guides/policies that call for also using a loopback address as the source for two-way protocols, such as FTP and NTP. That just doesn't make sense to me when you balance the routing implications against the limited security benefits (stable device identification, simplified ACL maintenance, and obfuscation of device addresses).
    I was hoping to learn that some obscure command might allow me to control which NTP exchanges use the loopback-based source address.  For example, the loopback source address would work fine on outgoing NTP broadcasts (and probably in replies from NTP servers).  But I would prefer that NTP client requests use a source address based on the exit interface. That way replies can be routed back to the client without cluttering up routing tables with routes to loopback addresses.
    So far, it looks like I'll need to chalk this up to poor coordination between the network security and network administration communities.
    Thanks again,
      Mark

  • Local Data Address Does not belong to any of this hosts local interfaces

    I cannot get through this exception while running
    sessionManager.initSession(
    localAddress,
    new SourceDescription[] {  },
    0.05,
    0.25);
    I get this debug output:
    Initalizing session (localAddress)
    DataAddress: 10.8.0.6/10.8.0.6
    ControlAddress: 10.8.0.6/10.8.0.6
    DataPort: 2838
    ControlPort: 2839
    10.8.0.6 is on my tun0 interface, I also tried with 192.168.1.100 which is on my eth2 interface but always get the message in the subject. The only address I can init session on is loopback address.
    I use code that looks at local interfaces and grabs ip address from one of them so I'm sure the assigned address belongs to one of my interfaces.
    Anybody knows how I can solve this problem?

    I solved this one. The problem is JMF seems to use InetAddress.getAllByName() which returns (at least in my case) only single IP address no matter how many addresses I have defined on my interfaces. The problem was solved by placing my IP address that I wanted to use by session manager into /etc/hosts. It must be the first line in /etc/hosts otherwise the other row that matches is used.

  • IP address lookup and Sockets

    Hi All,
    I have created a Socket using java.net.Socket(String host, int port) by passing the required host, port parameters.
    The host string is specified in the form of xxx.xxx.xxx.xxx, even though the Java
    program(client) is running on the same machine where the server socket is listening, (IP address is not specified as 'loopback address' localhost/127.0.0.1).
    Below are my queries for the above mentioned scenario.
    1) When the data is sent/received to/from the Socket, will the data
    travel across the network and return back to the same machine or it will be a direct send/receive within the same machine?
    2) Is the loopback address 'localhost/127.0.0.1' used internally by the underlying socket implementation without performing lookup of the IP address in the network?
    3) Does this behavior varies/depends on the underlying OS or the network
    protocol/configuration?
    Thanks in advance,
    Sreenivasulu

    1: it depends upon the mechanism through which the sockets between client and server are established (in ur case the client and the server is the same machine). When u specify the localhost/127.0.0.1, port where the server is listening, then i think the request should go out to the network and the OS will handle it by it self and manage the connection then the data will not travel through the whole network. Other wise when u specify that the server is listening on 192.168.0.0:9000 then the OS will go to look up server /dns it will tell him where this system in laying on the network is it in he same netwrok or out side this network and then a connection is established now the data will travel through the network, cause it will look for the system 192.168.0.0.
    2: when u will use the loopback for specific IP then the direct connection is made to the system.
    3: i can say nothing about this issus how the other OS are behaving cause i had mostly worked on Windows NT/2000
    i am in the learning process. If i am wrong plz correct me. And i am also very much interested for the replies from other users...
    thanx

  • How to see if an ip helper-address is configured on a VLAN

    Hi - I'm not exactly new to networking but this question will likely say otherwise :)
    I'm trying to figure out the command to show the running-config of a VLAN.  The goal is to see if an ip helper-address has been configured on a VLAN.
    This is both for a Cisco 6509 and Nexus 5k.
    I simply don't know all the commands for VLANs so I can't get this info presented to me.
    Thank You in advance

    Thanks for the prompt reply!  Still no bueno though.
    On the 6509 I get the following:
    6509#show ip interface vlan xxx
                                               ^
    % Invalid input detected at '^' marker.
    On the Nexus 5K I can't complete the command, stops down at show ip interface with the following listed as ? after interface:
    5K# show ip interface ?
      <CR>
      >                    Redirect it to a file
      >>                  Redirect it to a file in append mode
      A.B.C.D       Display interface for local IP address
      brief              Display summary of IP interface status and configuration
      ethernet        Ethernet IEEE 802.3z
      loopback      Loopback interface
      mgmt            Management interface
      operational   Display only interfaces that are administratively enabled
      port-channel  Port Channel interface
      vrf                   Display per-VRF information
      |                      Pipe command output to filter

  • Well Known Address (wka) issue

    Hi,
    I am hitting some issues whilst trying to configure and use multiple wkas in my cluster using Coherence 3.5.3.
    It appears that only the first WKA is being picked up from the configuration file, rather than the full list.
    For example, if I include the following in my tangosol-coherence-override.xml config file:
    <well-known-addresses>
    <socket-address id="1">
    <address>cyclone</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
    <socket-address id="2">
    <address>tornado</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
    </well-known-addresses>
    The logs will indicate that only a single wka is available (i.e. cyclone).
    If we try and bring proxy and storage nodes up on tornado they will not start up, as they will attempt to use cyclone.
    Does anyone have any ideas about where we might be going wrong?
    Cheers

    Hi Luk,
    Below is the tangosol-coherence-override.xml file I am using:
    Many Thanks
    <?xml version='1.0'?>
    <!-- Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
         Oracle is a registered trademarks of Oracle Corporation and/or its affiliates.
         This software is the confidential and proprietary information of Oracle Corporation.
         You shall not disclose such confidential and proprietary information and
         shall use it only in accordance with the terms of the license agreement you
         entered into with Oracle. This notice may not be removed or altered. -->
    <!DOCTYPE coherence SYSTEM "coherence.dtd">
    <!-- Note: This XML is set up for a development mode; search for "Note:"
         to find specific notes on changes suggested for production use. -->
    <coherence>
         <cluster-config>
              <member-identity>
                   <!-- Note: All members of the cluster must specify the same cluster name
                        in order to be allowed to join the cluster. -->
                   <cluster-name system-property="tangosol.coherence.cluster"></cluster-name>
                   <site-name system-property="tangosol.coherence.site"></site-name>
                   <rack-name system-property="tangosol.coherence.rack"></rack-name>
                   <machine-name system-property="tangosol.coherence.machine"></machine-name>
                   <process-name system-property="tangosol.coherence.process"></process-name>
                   <member-name system-property="tangosol.coherence.member"></member-name>
                   <role-name system-property="tangosol.coherence.role"></role-name>
                   <priority system-property="tangosol.coherence.priority"></priority>
              </member-identity>
              <unicast-listener>
                   <!-- Note: Specifying one or more "well known" addresses (WKA) will disable
                        all multicast communication. In this case, for a member to join the cluster
                        it will either have to be a WKA or there will have to be at least one WKA
                        member running. -->
                   <well-known-addresses>
                        <socket-address id="1">
                             <address>cyclone</address>
                             <port system-property="tangosol.coherence.wka.port"></port>
                        </socket-address>
    <socket-address id="2">
    <address>tornado</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
                   </well-known-addresses>
                   <!-- Note: The "localhost" setting may not work on systems that define
                        localhost as the loopback address; in that case, specify the machine name
                        or the specific IP address. -->
                   <address system-property="tangosol.coherence.localhost">localhost</address>
                   <port system-property="tangosol.coherence.localport">8088</port>
                   <port-auto-adjust system-property="tangosol.coherence.localport.adjust">true</port-auto-adjust>
                   <packet-buffer>
                        <maximum-packets>1428</maximum-packets>
                   </packet-buffer>
                   <priority>8</priority>
              </unicast-listener>
              <tcp-ring-listener>
                   <!-- Note: When encountering problems getting Coherence running on a system,
                        we suggest that this value be set to "false" until all other issues are resolved
                        in order to simplify trouble-shooting. -->
                   <enabled system-property="tangosol.coherence.tcpring">true</enabled>
                   <maximum-socket-closed-exceptions>2</maximum-socket-closed-exceptions>
                   <priority>6</priority>
              </tcp-ring-listener>
              <shutdown-listener>
                   <!-- Note: For production use, the suggested value is "none" (or "false")
                        unless testing has verified that the behavior on external shutdown is exactly
                        what is desired. -->
                   <enabled system-property="tangosol.coherence.shutdownhook">force</enabled>
              </shutdown-listener>
              <service-guardian>
                   <service-failure-policy>exit-cluster</service-failure-policy>
                   <!-- Note: For production use, the recommended value is equal to or greater
                        than the packet-delivery timeout. -->
                   <timeout-milliseconds system-property="tangosol.coherence.guard.timeout">65000</timeout-milliseconds>
              </service-guardian>
              <packet-speaker>
                   <priority>8</priority>
              </packet-speaker>
              <packet-publisher>
                   <packet-size>
                        <maximum-length>1468</maximum-length>
                        <preferred-length>1468</preferred-length>
                   </packet-size>
                   <packet-pool>
                        <maximum-packets>2048</maximum-packets>
                   </packet-pool>
                   <packet-delivery>
                        <resend-milliseconds>200</resend-milliseconds>
                        <!-- Note: For production use, the recommended value is the greater of
                             60000 and two times the maximum expected full GC duration. -->
                        <timeout-milliseconds>60000</timeout-milliseconds>
                        <heartbeat-milliseconds>1000</heartbeat-milliseconds>
                        <flow-control>
                             <enabled>true</enabled>
                             <pause-detection>
                                  <maximum-packets>16</maximum-packets>
                             </pause-detection>
                             <outstanding-packets>
                                  <maximum-packets>4096</maximum-packets>
                                  <minimum-packets>64</minimum-packets>
                             </outstanding-packets>
                        </flow-control>
                        <packet-bundling>
                             <maximum-deferral-time>1us</maximum-deferral-time>
                             <aggression-factor>0</aggression-factor>
                        </packet-bundling>
                   </packet-delivery>
                   <notification-queueing>
                        <ack-delay-milliseconds>16</ack-delay-milliseconds>
                        <nack-delay-milliseconds>1</nack-delay-milliseconds>
                   </notification-queueing>
                   <burst-mode>
                        <maximum-packets>0</maximum-packets>
                        <pause-milliseconds>10</pause-milliseconds>
                   </burst-mode>
                   <traffic-jam>
                        <maximum-packets>8192</maximum-packets>
                        <pause-milliseconds>10</pause-milliseconds>
                   </traffic-jam>
                   <packet-buffer>
                        <maximum-packets>32</maximum-packets>
                   </packet-buffer>
                   <priority>6</priority>
                   <!-- Note: Disabling the Publisher is used only by Java Real-Time Clients
                        to restrict their ability to use the cluster protocol (TCMP). When disabled,
                        a client is only be able to access clustered services via Extend proxies. -->
                   <enabled system-property="tangosol.coherence.tcmp.enabled">true</enabled>
              </packet-publisher>
              <incoming-message-handler>
                   <maximum-time-variance>16</maximum-time-variance>
                   <packet-pool>
                        <maximum-packets>2048</maximum-packets>
                   </packet-pool>
                   <use-nack-packets>true</use-nack-packets>
                   <priority>7</priority>
              </incoming-message-handler>
              <outgoing-message-handler>
                   <!-- Note: Uncomment the following section to activate gzip compression
                        for all network messages, which can help substantially with WAN and low-bandwidth
                        networks; for more information, see: http://www.tangosol.com/faq-coherence.jsp#filterconfig -->
                   <use-filters>
                        <!-- <filter-name>gzip</filter-name> -->
                   </use-filters>
              </outgoing-message-handler>
              <authorized-hosts>
                   <host-address></host-address>
                   <host-range>
                        <from-address></from-address>
                        <to-address></to-address>
                   </host-range>
              </authorized-hosts>
              <services>
                   <service id="1">
                        <service-type>ReplicatedCache</service-type>
                        <service-component>ReplicatedCache</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>standard-lease-milliseconds</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lease-granularity</param-name>
                                  <param-value>thread</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>mobile-issues</param-name>
                                  <param-value>false</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.replicated.request.timeout"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.replicated.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="2">
                        <service-type>OptimisticCache</service-type>
                        <service-component>ReplicatedCache.Optimistic</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.optimistic.request.timeout"></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.optimistic.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="3">
                        <service-type>DistributedCache</service-type>
                        <service-component>DistributedCache</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>standard-lease-milliseconds</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lease-granularity</param-name>
                                  <param-value>thread</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>partition-count</param-name>
                                  <param-value>257</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>local-storage</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.localstorage">true</param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>transfer-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.transfer">512</param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>backup-count</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.backupcount">1</param-value>
                             </init-param>
                             <init-param id="7">
                                  <param-name>backup-storage/type</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.backup">on-heap</param-value>
                             </init-param>
                             <init-param id="8">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.threads">5</param-value>
                             </init-param>
                             <init-param id="9">
                                  <param-name>key-associator/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="10">
                                  <param-name>key-partitioning/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="11">
                                  <param-name>partition-listener/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="12">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.task.hung"></param-value>
                             </init-param>
                             <init-param id="13">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.task.timeout"></param-value>
                             </init-param>
                             <init-param id="14">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.request.timeout"></param-value>
                             </init-param>
                             <init-param id="15">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="16">
                                  <param-name>backup-count-after-writebehind</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="17">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="4">
                        <service-type>Invocation</service-type>
                        <service-component>InvocationService</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.threads">5</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.task.hung"></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.task.timeout"></param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.request.timeout"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="5">
                        <service-type>LocalCache</service-type>
                        <service-component>LocalCache</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>lock-enforce</param-name>
                                  <param-value>false</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lock-wait</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="6">
                        <service-type>SimpleCache</service-type>
                        <service-component>SimpleCache</service-component>
                   </service>
                   <service id="7">
                        <service-type>Proxy</service-type>
                        <service-component>ProxyService</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>acceptor-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>proxy-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.threads">10</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.task.hung"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.task.timeout"></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.request.timeout"></param-value>
                             </init-param>
                             <init-param id="7">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="8">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="8">
                        <service-type>RemoteCache</service-type>
                        <service-component>RemoteCache</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>initiator-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="9">
                        <service-type>RemoteInvocation</service-type>
                        <service-component>RemoteInvocation</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>initiator-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                        </init-params>
                   </service>
              </services>
              <filters>
                   <filter id="1">
                        <filter-name>gzip</filter-name>
                        <filter-class>com.tangosol.net.CompressionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>strategy</param-name>
                                  <param-value>gzip</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>level</param-name>
                                  <param-value>default</param-value>
                             </init-param>
                        </init-params>
                   </filter>
                   <filter id="2">
                        <filter-name>symmetric-encryption</filter-name>
                        <filter-class>com.tangosol.net.security.PasswordBasedEncryptionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>password</param-name>
                                  <param-value system-property="tangosol.coherence.security.password"></param-value>
                             </init-param>
                        </init-params>
                   </filter>
                   <filter id="3">
                        <filter-name>pkcs-encryption</filter-name>
                        <filter-class>com.tangosol.net.security.ClusterEncryptionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>store</param-name>
                                  <param-value system-property="tangosol.coherence.security.keystore">./keystore.jks</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>keyAlias</param-name>
                                  <param-value>local</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>keyPassword</param-name>
                                  <param-value system-property="tangosol.coherence.security.password"></param-value>
                             </init-param>
                        </init-params>
                   </filter>
              </filters>
         </cluster-config>
         <logging-config>
              <destination system-property="tangosol.coherence.log">stdout</destination>
              <logger-name system-property="tangosol.coherence.log.logger"></logger-name>
              <severity-level system-property="tangosol.coherence.log.level">9</severity-level>
              <message-format>{date}/{uptime} {product} {version} &lt;{level}&gt;
                   (thread={thread}, member={member}): {text}</message-format>
              <character-limit system-property="tangosol.coherence.log.limit">1048576</character-limit>
         </logging-config>
         <configurable-cache-factory-config>
              <class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
              <init-params>
                   <init-param>
                        <param-type>java.lang.String</param-type>
                        <param-value system-property="tangosol.coherence.cacheconfig">coherence-cache-config.xml</param-value>
                   </init-param>
              </init-params>
         </configurable-cache-factory-config>
         <cache-factory-builder-config>
              <class-name system-property="tangosol.coherence.cachefactorybuilder">com.tangosol.net.DefaultCacheFactoryBuilder</class-name>
         </cache-factory-builder-config>
         <management-config>
              <!-- Note: Setting this value to 'local-only', 'remote-only or 'all' will
                   require the javax.management.* classes be available on the classpath. -->
              <managed-nodes system-property="tangosol.coherence.management">all</managed-nodes>
              <!-- Note: Setting this value to 'true' will require the Enterprise Edition
                   license. -->
              <allow-remote-management system-property="tangosol.coherence.management.remote">true</allow-remote-management>
              <refresh-policy system-property="tangosol.coherence.management.refresh.policy">refresh-ahead</refresh-policy>
              <refresh-expiry system-property="tangosol.coherence.management.refresh.expiry">1s</refresh-expiry>
              <refresh-timeout system-property="tangosol.coherence.management.refresh.timeout">250ms</refresh-timeout>
              <read-only system-property="tangosol.coherence.management.readonly">false</read-only>
              <default-domain-name>AGP Cache</default-domain-name>
              <service-name>Management</service-name>
              <server-factory>
                   <class-name system-property="tangosol.coherence.management.serverfactory"></class-name>
              </server-factory>
              <mbeans xml-override="{tangosol.coherence.mbeans /custom-mbeans.xml}">
                   <mbean id="1">
                        <mbean-query>java.lang:*</mbean-query>
                        <mbean-name>type=Platform</mbean-name>
                        <enabled system-property="tangosol.coherence.management.jvm.all">true</enabled>
                   </mbean>
              </mbeans>
              <reporter>
                   <configuration system-property="tangosol.coherence.management.report.configuration">reports/report-group.xml</configuration>
                   <autostart system-property="tangosol.coherence.management.report.autostart">false</autostart>
                   <distributed system-property="tangosol.coherence.management.report.distributed">false</distributed>
              </reporter>
         </management-config>
         <security-config>
              <enabled system-property="tangosol.coherence.security">false</enabled>
              <login-module-name>Coherence</login-module-name>
              <access-controller>
                   <class-name>com.tangosol.net.security.DefaultController</class-name>
                   <init-params>
                        <init-param id="1">
                             <param-type>java.io.File</param-type>
                             <param-value system-property="tangosol.coherence.security.keystore"></param-value>
                        </init-param>
                        <init-param id="2">
                             <param-type>java.io.File</param-type>
                             <param-value system-property="tangosol.coherence.security.permissions"></param-value>
                        </init-param>
                   </init-params>
              </access-controller>
              <callback-handler>
                   <class-name />
              </callback-handler>
         </security-config>
         <license-config>
              <edition-name system-property="tangosol.coherence.edition">GE</edition-name>
              <license-mode system-property="tangosol.coherence.mode">dev</license-mode>
         </license-config>
    </coherence>

  • Different Source Address for a SNMP trap paquet

    We use a common platform to manage the CISCO routers for several customers. We are using to manage the devices w/ a loopback address as source of snmp paquet.
    We use something like this ...
    Router(config)#snmp-server host 172.25.1.1 ORATRAP
    Router(config)#snmp-server trap-source loopback0
    Router(config)#end
    Now, there is some customers that request us to receipt the snmp-traps w/ an ip source of their own ip space (192.168.2.x/24).I cannot imagine how this can be achieve?... Please any idea?. Thks. Eduard.

    Thks., for your help. This is important matter to us. We also working in the idea of snmp track collector close to our own NMC... but this may cost also money... . So, we are going to try another approach first..
    Somewhat like this below....
    snmp-server enable traps
    snmp-server informs
    snmp-server source-interface traps
    snmp-server source-interface informs
    snmp-server host traps version 1 community string publicCust
    snmp-server host informs version 2 community string publicBT
    For the get's every MNC sends to the declared IP, so We thing that will use the same IP in answer.
    I will let you know. Eduard.

Maybe you are looking for