Routing

last person joined: 4 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  SNMP - Loopbackinterface lo0

    Posted 07-02-2019 01:33

    Hello!

    Im a newly examined IT-Operations technician whos currently employed at an consultant companys IT-department, im not a certified Juniper or Cisco technician but my studies have evolved around Cisco and im currently learning Juniper so please be patient with me.

    My problem is following:

    We are undergoing an exchange of ISP deliverer, we are moving from layer 2 MPLS-OSPF routing to Layer 3 OSPF routing with Cisco virtual routers that our ISP handles.
    We have EX-3300 and EX-3400 switches on our offices that are routed threw our ISP routers to our datacenter.

    We have a non-segmented server network with a /23 address where a CentOS client named NedI currently is present.

    The primary interface leading to our ISP is configured with a routing instance to the Virtual router (Configuration will be present below), and we have routing to a loopback interface lo0 wich we would like to use for SNMP discoveries.
    Allt the ports are open and i can PING the loopback interface from the CentOS client, and ping the CentOS client via the loopback interface.
    I can reach the Switches that are still on MPLS with our Fiber-provider.

    All help is appreciated.

    Configuration:

    root@SW01> show configuration snmp
    community public {
    authorization read-only;
    routing-instance ***-Data {
    clients {
    ***.***.8.1/32;
    ***.***.8.2/32;
    ***.***.8.3/32;
    ***.***.8.4/32;
    }
    }
    }
    routing-instance-access {
    access-list {
    *;
    }
    }

    {master:0}
    root@SW01> show configuration snmp |display set| no-more
    set snmp community public authorization read-only
    set snmp community public routing-instance 901-Data clients ***.***.1.1/32
    set snmp community public routing-instance 901-Data clients ***.***.1.2/32
    set snmp community public routing-instance 901-Data clients ***.***.1.3/32
    set snmp community public routing-instance 901-Data clients ***.***.1.4/32
    set snmp routing-instance-access access-list *

    root@SW01> show configuration routing-instances
    901-Data {
    instance-type virtual-router;
    interface lo0.0;
    interface vlan.101;
    interface vlan.901;
    interface vlan.911;
    routing-options {
    router-id ***.***.***.30;
    }
    protocols {
    ospf {
    area 0.0.0.0 {
    interface vlan.901;
    interface lo0.0 {
    passive;
    }
    interface vlan.101 {
    passive;
    }
    interface vlan.911;
    }
    }
    }
    }
    902-Voip {
    instance-type virtual-router;
    interface vlan.102;
    interface vlan.902;
    interface vlan.912;
    routing-options {
    router-id ***.***.***.0;
    }
    protocols {
    ospf {
    area 0.0.0.0 {
    interface vlan.902;
    interface vlan.102 {
    passive;
    }
    interface vlan.912;
    }
    }
    }
    }









  • 2.  RE: SNMP - Loopbackinterface lo0
    Best Answer

    Posted 07-02-2019 02:35

    Welcome to Junos.

     

    For snmp access inside a routing instance you need to add the routing instance name and @ to the community name from the source.

     

    name@community

     

    Otherwise Junos assumes it is directed to the main or root routing instance.

     



  • 3.  RE: SNMP - Loopbackinterface lo0

    Posted 07-02-2019 03:36

    Thank you for this Spuluka, a simple solution to what is a simple problem i assume.

    I had this configured in the NedI Config but it was case-sensitive so thereby not accepted.

    Best Regards
    Andreas