Quantcast
Channel: All Routing posts
Viewing all 8688 articles
Browse latest View live
↧

Overlapping subnets on interface

April 15, 2020, 6:24 am
$
0
0

Hello All,

 

I have a need to include /29 subnet on an interface that already contains the /24 of that same network.

 

For example. 

 

interface xe-2/0/0 unit 0 family inet address 10.1.0.0/24

interface xe-2/0/0 unit 0 family inet address 10.1.0.32/29

 

I am moving from cisco routers to Juniper, so I am still learning Juniper. The cisco allowed me to add this as a secondary IP address. Is there something I am missing or a better way to do this? I am not in a position to change the IP addresses on the client device. 

 

Thanks,

 

Matt

↧
Search

Re: Overlapping subnets on interface

April 15, 2020, 6:42 am
$
0
0

Hi,

 

you can not configure overlapping subnets on same interface but you can configure 2 logical units and configure the subnets.

If this solves your problem, please mark this post as "Accepted Solution."

↧
↧

Re: Overlapping subnets on interface

April 15, 2020, 6:57 am
$
0
0

I did try this and this configuration requires Vlan tagging on the interface. Since these 2 networks will be on the same vlan coming into the router, I can't create another unit on this interface with the same vlan tag.

 

Thanks,

 

Matt

↧

Re: Is an OSPF Link State Request message ever sent or received after an adjacency is FULL?

April 15, 2020, 12:37 pm
$
0
0

 

 

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \Smiley Happy/

 

Regards,

 

Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

 

 

 

↧

Re: Subscribers on MX

April 15, 2020, 4:16 pm
↧
↧

Re: Overlapping subnets on interface

April 15, 2020, 7:11 pm
$
0
0

Hi there,

 

 Depending on the encapsulation and interface, you could configure 1 or more logical interfaces (unit 0,1,2,3…). Physical interfaces configured as “unit 0 family inet address” will typically only allow one single unit, so you may try other type of encapsulation as you stated or using logical interfaces like IRBs. 

 

 However, JUNOS will not allow you to configure overlapping subnets on the same routing instance even if they belong to different interfaces or units as it will show a commit error or you will start seeing logs warming you about the problem.

 

 As a workaround, you can separate the interfaces into different Routing-instances like Virtual-Router type.  Keeping 10.1.0.0/24 on the default instance and moving 10.1.0.32/29 to a customized instance.

 

 Please note, routing instances will separate devices into 2 or more virtual devices. Each having separate routing tables. If you need communication between the instances, you need to use filters or RIB groups. More information can be found on the below links:

 

 You can find more information on the below links:

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/bridging-vrf-qfx-series-cli.html

 

https://www.juniper.net/documentation/en_US/release-independent/nce/topics/example/virtual-router-srx-use-case-edu-configuring.html

 

Best Regards,

 

If it clears your concerns, please mask as solved!

↧

Re: Overlapping subnets on interface

April 15, 2020, 9:28 pm
$
0
0

Thank you so much for the reply. Here is the config I did. The router didn't compain about it.  Can you tell me if I am thinking about this right. All I would need to do on the main instance is to create a route to 10.1.0.33 for the /29 network and a default route out of the VLAN20-Sub instace?

 

interfaces {
xe-0/1/0 {
   enable;
   vlan-tagging;
   gigether-options {
   speed 1g;
}
   unit 0 {
      vlan-id 10;
      family inet {
         address 10.1.0.0/24 {
      primary;
   }
}
   unit 21 {
      vlan-id 21;
      family inet {
      address 10.1.0.33/29;
}
}
}

routing-instances {
   VLAN20-Sub {
       instance-type virtual-router;
       interface xe-0/1/0.21;
}
}

↧

OSPF and subnet masks.

April 15, 2020, 10:49 pm
$
0
0

Hi.

 

When bringing up an OSPF adjacency, why must the subnet mask match over a multiaccess link but not over a point-to-point link?

 

Thanks.

↧
Search

Re: OSPF and subnet masks.

April 15, 2020, 11:28 pm
$
0
0

Hi,

 

From my understanding, if the subnet mask is ignored on a multiaccess link, IP's in different subnet can establish adjacency as they see the multicast packets. But post that, the unicast communication will be an issue because of which the LSA's will be affected resulting to a database inconsistency.

 

With respect to point-to-point link, I think RFC is more specific to interfaces such as Frame Relay rather than Ethernet. In Junos, OSPF fails to form adjacency even in point-to-point links for Ethernet interfaces.

 

Hope this helps.

 

Thanks and Regards,

Pradeep Kumar.

↧
↧

Re: OSPF and subnet masks.

April 15, 2020, 11:53 pm
$
0
0

Hi djadhav,

 

The Network Mask field in the Hello packet header contains the subnet mask of the advertising OSPF interface. Unnumbered point-to-point interfaces and virtual links set this value to 0.0.0.0.

 

As per RFC2328, section 10.5 (Receiving Hello Packets), there is one exception where Point-to-Point interfaces and on virtual links, the network mask in the received hello packets should be ignored.

Ethernet interfaces used as Point-to-Point are widely used for troubleshooting purposes. However, in Junos OS, the network mask will still be considered when Ethernet interfaces are used as Point-to-Point. This is an expected Junos OS behavior.

 

When Ethernet interfaces are used as Broadcast, Junos OS will still consider the network mask; in case of a mismatch, the OSPF neighbor will not form. The RFC exception applies to only actual Point-to-Point interfaces, such as Frame Relay. So, when configuring the Ethernet as Point-to-Point, it is recommended that the network mask also matches with the peer.

 

In certain cases, adjacency issues (INIT state) can occur when using the Point-to-Point Interface type for the Open Shortest Path First (OSPF) protocol. Messages such as this can be seen:

May 10 12:16:17.458702 OSPF rcvd Hello 10.171.222.6 -> 224.0.0.5 (ae0.1 IFL 128 area 0.0.0.0)
May 10 12:16:17.458739 Version 2, length 48, ID 10.0.0.1, area 0.0.0.0
May 10 12:16:17.458768 checksum 0x0, authtype 0
May 10 12:16:17.458799 mask 0.0.0.0, hello_ivl 10, opts 0x2, prio 1
May 10 12:16:17.458828 dead_ivl 40, DR 0.0.0.0, BDR 0.0.0.0
May 10 12:16:17.458856 neighbor 10.171.222.1
May 10 12:16:17.458893 OSPF packet ignored: netmask 0.0.0.0 mismatch from 10.171.222.6 on intf ae0.1 area 0.0.0.0

 

Please find the below link-

https://kb.juniper.net/InfoCenter/index?page=content&id=KB23533

 

Let me know if this solves your query.

 

Please mark this as an "Accepted solution" so that it can help others as well. Kudos would be much appreciated too Smiley Happy 

↧

Re: OSPF and subnet masks.

April 16, 2020, 12:06 am
$
0
0

Hello,

 

 wrote:

 why must the subnet mask match over a multiaccess link but not over a point-to-point link?

 

 

 

Because true p2p link (PPP or FR or ATM or IPSec/GRE tunnel) can have an IPv4 address with /32 subnet mask assigned to it.

With /32 subnet mask, OSPF Hello "network mask" field ANDed with neighbor IP would never match between neighbors so the decision was taken to ignore subnet mask on true p2p networks.

 

HTH

Thx

Alex  

↧

pic offline

April 16, 2020, 9:54 am
$
0
0

Hi all any idea about chassid logs below: The problem is pic(ms mic) on mx is intermitently working....

There is KB but couldn't find actual problem on the device

https://kb.juniper.net/InfoCenter/index?page=content&id=KB18822&act=login

 

3 17:16:40  ch_gencfg_update_startup_time_blob: Updated hw.chassis.startup_time to 1539844910.999170 (RE)
3 17:16:40  ch_gencfg_chassis_startup_time_handler: master_re: true, GENCFG_CHASSIS_STARTUP_TIME, minor_type: 8
3 17:37:30  pic offline req, pic 2, fpc 1 reason 0
3 17:37:30 CHASSISD_IFDEV_DETACH_PIC: ifdev_detach_pic(1/2)
3 17:37:30  LS: PIC DELETE: Deleting IFDs(#0) on pic 2 slot 1  ls_ifdev_detach
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id
3 17:37:30  does_fpc_i2cid_match_ifd_prefix: Cannot get i2c id

thx

Ar

 

↧

Re: pic offline

April 16, 2020, 12:47 pm
$
0
0

Hello Arix, Acording to those log on the Device they are related to hardware. 

This type of logs appears on the box when they recognize the SFPs, FPCs or any type of hardware connected on the box directly. 

The way to solve this errors is by rebooting the box ( In case the hardware is not affected ), But be noted that if even after the reboot if the logs keep showing up you will need to make some Physicall troubleshooting. 

Disconnect the SFPs on the Device and check ig by using a known working one the device stops generatign those logs. 

If even after you do that the device keep generating the logs will mean that hardware is affected and then the box will need to be replace. 

 

↧
↧

Re: weird logs

April 16, 2020, 11:25 pm
$
0
0

any workaround?

Any response these persistently occuring logs relating to what services or functionality of Junos. It is nearly every milisecond occurs... Millions.... where to start troublehooting...

bbe=smgd[2561]: sdb_create_extended_client_session_sts: Getting phy ifd failed for client 1711123 ret=-7 : 6440
bbe=smgd[2561]: sdb_create_extended_client_session_sts: Getting phy ifd failed for client 1711125 ret=-7 : 6440
bbe=smgd[2561]: sdb_remove_bundled_client_session_sts: Getting phy ifd failed for cient:1710980ret=-7 : 8971
bbe=smgd[2561]: sdb_remove_bundled_client_session_sts: Getting phy ifd failed for cient:1710982ret=-7 : 8971
bbe=smgd[2561]: sdb_remove_bundled_client_session_sts: Getting phy ifd failed for cient:1710983ret=-7 : 8971
bbe=smgd[2561]: sdb_remove_bundled_client_session_sts: Getting phy ifd failed for cient:1710984ret=-7 : 8971

 

↧

switchover

April 17, 2020, 12:33 am
$
0
0

Hi all,

What does the following log say and why does junos need to perform switchover?

 

chassisd[1283]: CHASSISD_PIC_RESET_ON_SWITCHOVER: PIC 3 in FPC 2 (type 1650: MS-MIC-40G, version 614) does not support GRES and will be reset on switchover

↧
Search

Re: switchover

April 17, 2020, 12:57 am
↧

L2circuit via RSVP with strict path

April 17, 2020, 12:57 am
$
0
0

Hi 

 

I found my l2cirucit is working via ldp. But not while enabled RSVP with static label. 

Could some provide me some advice about how to fix it?

 

via LDP :

Neighbor: 192.168.146.9

    Interface                 Type  St     Time last up          # Up trans

    ge-4/0/9.0(vc 10001)      rmt   RD   

      local PW status code: 0x00000000, Neighbor PW status code: 0x00000001

    ge-4/2/9.0(vc 10002)      rmt   RD   

      local PW status code: 0x00000000, Neighbor PW status code: 0x00000001

 

via RSVP with static label.

Neighbor: 192.168.146.96
Interface Type St Time last up # Up trans
ge-4/0/9.0(vc 10001) rmt OL
ge-4/2/9.0(vc 10002) rmt OL  

 

This is the infrastructure : Router1(182.54.131.22) -- Router 2 -- Router 3 -- Router 4(192.168.146.9,192.168.146.96)

And the attached is the configuration of MPLS on those routers

 

thanks 

Cloud

 

↧
↧

Betreff: switchover

April 17, 2020, 12:59 am
$
0
0

Hello Arix,

 

is this log message printed periodically? The Juniper documentation tells me the following:

 

System Log Message

PIC pic-slot n FPC pc-slot (type pic-type: pic-name, version version) does not support GRES and will be reset on switchover

Description

The chassis process (chassisd) noted that the Physical Interface Card (PIC) with the indicated characteristics needs to be reset when a graceful switchover occurs.

Type

Event: This message reports an event, not an error

Severity:

warning

 

 

Maybe there happened a graceful switchover in your system, and this is the information that you have to reset this PIC manually now.

↧

Betreff: switchover

April 17, 2020, 2:36 am
$
0
0

Hi all,

 

Juniper resource is indicating "This Syslog message is an event. It is not an error.". I am not sure to what extent this resource is indicating the case...... Because unfortunately it is huge impacting PIC card which has multiple high density of traffic....

 

CAn you tell me please what is relationship between PIC and GRES funtion.? And why is RE or Chassis needed to perform GRES? What reasons? Is it RE0 gonna be down and this is the reason to swithcover to RE1?

 

Th

A

 

↧

Re: L2circuit via RSVP with strict path

April 17, 2020, 3:15 am
$
0
0

Hey Cloud,

 

Greetings, please check out this information, if you need both signaling protocols to coexist you might want to see this: https://www.juniper.net/documentation/en_US/release-independent/nce/topics/task/configuration/layer-two-circuits-rsvp-ldp-lsp-solutions.html

 

 

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \Smiley Happy/

 

Regards,

 

Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

 

↧
Viewing all 8688 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>