Home › Forums › FABRIC General Questions and Discussion › Unable to access slice
- This topic has 3 replies, 2 voices, and was last updated 1 year ago by Komal Thareja. 
- 
		AuthorPosts
- 
		
			
				
October 21, 2024 at 7:32 am #7666Hi, For the past 2-3 days, every time I create a slice and work on it for a few hours, I encounter the following error: “From 192.168.24.254 icmp_seq=1 Destination Net Unreachable.” SLICE_NAME = “ospf_13node” 
 SITE_NAME = “MASS”I created multiple different slices on different sites but still the issue persists. And for the slice extension using the Calendar by clicking on the small square shown next to Lease End atto choose the timestamp and then click on Extend, that is also not working. I’m using the script to extend the slice.October 21, 2024 at 9:59 am #7668Hi Kriti, I created a slice on MASS for a Layer2 Network as well as Layer3 network. Both slices were able to pass traffic. This may be something specific to your slice or configuration. Please share your slice id. We can help to take a look but would also recommend checking configuration on your side as well. Thank you for letting us know about the portal. We will work on addressing that as well. Thanks, Komal October 22, 2024 at 10:38 am #7671<caption>Slice</caption> ID 3c35fae8-f1f9-4ba2-98ef-e8ab03b9a798 October 22, 2024 at 11:20 am #7672Hi Kriti, It appears that there may be a configuration issue with your experiment. I recommend checking your settings. Based on your slice, there’s a Layer 2 network established between ipnode-1 (192.168.14.1)andn6 (192.168.14.254).I can confirm that pinging from ipnode-1ton6is successful, which indicates that the underlying Layer 2 network is functioning properly. While you do have a route onipnode-1to direct traffic throughn6, it seems that the subnet you’re trying to access is not reachable fromn6. This issue seems to be specific to your experiment’s configuration, so you may need to troubleshoot on your end.
 [root@ipnode-1 ~]# ip route list
 10.30.6.0/23 dev eth0 proto kernel scope link src 10.30.6.233 metric 100
 169.254.169.254 via 10.30.6.11 dev eth0 proto dhcp src 10.30.6.233 metric 100
 192.168.0.0/16 via 192.168.14.254 dev eth1
 192.168.14.0/24 dev eth1 proto kernel scope link src 192.168.14.1
 [root@ipnode-1 ~]# traceroute 192.168.28.1
 traceroute to 192.168.28.1 (192.168.28.1), 30 hops max, 60 byte packets
 1 192.168.14.254 (192.168.14.254) 0.422 ms !N 0.386 ms !N *
 [root@ipnode-1 ~]# traceroute 192.168.14.254
 traceroute to 192.168.14.254 (192.168.14.254), 30 hops max, 60 byte packets
 1 192.168.14.254 (192.168.14.254) 0.454 ms 0.434 ms 0.423 ms
 [root@ipnode-1 ~]#
 [root@ipnode-1 ~]#
 [root@ipnode-1 ~]#
 [root@ipnode-1 ~]# ping -c 5 192.168.14.254
 PING 192.168.14.254 (192.168.14.254) 56(84) bytes of data.
 64 bytes from 192.168.14.254: icmp_seq=1 ttl=64 time=0.069 ms
 64 bytes from 192.168.14.254: icmp_seq=2 ttl=64 time=0.062 ms
 64 bytes from 192.168.14.254: icmp_seq=3 ttl=64 time=0.102 ms
 64 bytes from 192.168.14.254: icmp_seq=4 ttl=64 time=0.066 ms
 64 bytes from 192.168.14.254: icmp_seq=5 ttl=64 time=0.076 msn6: 
 
 [root@n6 ~]# ip route list
 10.30.6.0/23 dev eth0 proto kernel scope link src 10.30.6.69 metric 100
 169.254.169.254 via 10.30.6.11 dev eth0 proto dhcp src 10.30.6.69 metric 100
 192.168.1.0/24 proto ospf metric 20
 nexthop via 192.168.8.2 dev eth3 weight 1
 nexthop via 192.168.12.1 dev eth1 weight 1
 192.168.2.0/24 via 192.168.8.2 dev eth3 proto ospf metric 20
 192.168.3.0/24 proto ospf metric 20
 nexthop via 192.168.8.2 dev eth3 weight 1
 nexthop via 192.168.12.1 dev eth1 weight 1
 192.168.4.0/24 via 192.168.12.1 dev eth1 proto ospf metric 20
 192.168.5.0/24 via 192.168.8.2 dev eth3 proto ospf metric 20
 192.168.6.0/24 proto ospf metric 20
 nexthop via 192.168.8.2 dev eth3 weight 1
 nexthop via 192.168.12.1 dev eth1 weight 1
 192.168.7.0/24 via 192.168.12.1 dev eth1 proto ospf metric 20
 192.168.8.0/24 dev eth3 proto kernel scope link src 192.168.8.1
 192.168.9.0/24 via 192.168.8.2 dev eth3 proto ospf metric 20
 192.168.10.0/24 via 192.168.8.2 dev eth3 proto ospf metric 20
 192.168.11.0/24 via 192.168.12.1 dev eth1 proto ospf metric 20
 192.168.12.0/24 dev eth1 proto kernel scope link src 192.168.12.2
 192.168.13.0/24 via 192.168.12.1 dev eth1 proto ospf metric 20
 192.168.14.0/24 dev eth2 proto kernel scope link src 192.168.14.254
 192.168.15.0/24 via 192.168.8.2 dev eth3 proto ospf metric 20
 192.168.16.0/24 via 192.168.12.1 dev eth1 proto ospf metric 20
 [root@n6 ~]# traceroute 192.168.28.1
 traceroute to 192.168.28.1 (192.168.28.1), 30 hops max, 60 byte packets
 connect: Network is unreachableThanks, Komal 
- 
		AuthorPosts
- You must be logged in to reply to this topic.
