From golem at mtm-info.pl Thu Dec 6 06:35:23 2018 From: golem at mtm-info.pl (Rafal O.) Date: Thu, 6 Dec 2018 12:35:23 +0100 Subject: [rbak-nsp] syslogd messages Message-ID: <163180146.20181206123523@mtm-info.pl> Hello How to access these messages and where are they stored ? %LOG-4-EXT_MSGS: syslogd has received 12 external msgs -- Pozdrowienia, Rafal O. From lukasz at alfa-system.pl Fri Dec 14 03:52:42 2018 From: lukasz at alfa-system.pl (=?UTF-8?Q?=c5=81ukasz_Kopiszka?=) Date: Fri, 14 Dec 2018 09:52:42 +0100 Subject: [rbak-nsp] BGP - neighbor peer-as Message-ID: <94e2950e-c5e2-b624-4162-50006c31da7a@alfa-system.pl> Hi, I need to do something like this: ?router bgp 198050 ? neighbor 192.168.12.184 internal ? neighbor 192.168.12.184 peer-as 65000 ??? address-family ipv4 unicast ????? route-map wanguard-in in ????? route-map wanguard-out out but unfortunately my SEOS-12.1.1.5p2-Release don't support such syntax "neighbor 192.168.12.184 peer-as 65000" Is there any other way to do it? -- Pozdrawiam, ?ukasz Kopiszka http://alfa-system.pl From me at geordish.org Fri Dec 14 03:57:23 2018 From: me at geordish.org (Dave Bell) Date: Fri, 14 Dec 2018 08:57:23 +0000 Subject: [rbak-nsp] BGP - neighbor peer-as In-Reply-To: <94e2950e-c5e2-b624-4162-50006c31da7a@alfa-system.pl> References: <94e2950e-c5e2-b624-4162-50006c31da7a@alfa-system.pl> Message-ID: If you have a different AS number, it?s not an iBGP session. What are you trying to accomplish? On Fri, 14 Dec 2018 at 08:54, ?ukasz Kopiszka wrote: > Hi, > > I need to do something like this: > > router bgp 198050 > neighbor 192.168.12.184 internal > neighbor 192.168.12.184 peer-as 65000 > address-family ipv4 unicast > route-map wanguard-in in > route-map wanguard-out out > > but unfortunately my SEOS-12.1.1.5p2-Release don't support such syntax > "neighbor 192.168.12.184 peer-as 65000" > > Is there any other way to do it? > > -- > Pozdrawiam, > ?ukasz Kopiszka > http://alfa-system.pl > > _______________________________________________ > redback-nsp mailing list > redback-nsp at puck.nether.net > https://puck.nether.net/mailman/listinfo/redback-nsp > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dado at korolev-net.ru Sun Dec 16 06:58:32 2018 From: dado at korolev-net.ru (Evgenii Davidov) Date: Sun, 16 Dec 2018 14:58:32 +0300 Subject: [rbak-nsp] se400 fan speed? In-Reply-To: References: Message-ID: <20181216115832.GP81393@korolev-net.ru> hello is it possible to control fans's speed on se400? it seems that they are not working sometimes thanks Fan Tray Status Present Fan(s) Status Normal N/A fan tray 0C204210802995 20 4 22-JUN-2008 N/A N/A enterprises.2352.2.4.1.1.1.2.1 = "Fan Tray" enterprises.2352.2.4.1.1.1.4.1 = 1 enterprises.2352.2.4.1.2.1.2.1 = "Power Supply A" enterprises.2352.2.4.1.2.1.2.2 = "Power Supply B" enterprises.2352.2.4.1.2.1.4.1 = 1 enterprises.2352.2.4.1.2.1.4.2 = 3 enterprises.2352.2.4.1.3.1.2.11.1 = "1500mV voltage sensor, slot 1" enterprises.2352.2.4.1.3.1.2.11.2 = "1800mV voltage sensor, slot 1" enterprises.2352.2.4.1.3.1.2.11.3 = "2500mV voltage sensor, slot 1" enterprises.2352.2.4.1.3.1.2.11.4 = "3300mV voltage sensor, slot 1" enterprises.2352.2.4.1.3.1.2.22.1 = "1500mV voltage sensor, slot 4" enterprises.2352.2.4.1.3.1.2.22.2 = "1800mV voltage sensor, slot 4" enterprises.2352.2.4.1.3.1.2.22.3 = "2600mV voltage sensor, slot 4" enterprises.2352.2.4.1.3.1.2.22.4 = "3300mV voltage sensor, slot 4" enterprises.2352.2.4.1.3.1.2.24.1 = "1200mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.2 = "1200mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.3 = "1300mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.4 = "1800mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.5 = "2500mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.6 = "3300mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.7 = "12000mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.8 = "900mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.2.24.9 = "1500mV voltage sensor, slot 6" enterprises.2352.2.4.1.3.1.3.11.1 = Gauge32: 1500 enterprises.2352.2.4.1.3.1.3.11.2 = Gauge32: 1800 enterprises.2352.2.4.1.3.1.3.11.3 = Gauge32: 2500 enterprises.2352.2.4.1.3.1.3.11.4 = Gauge32: 3300 enterprises.2352.2.4.1.3.1.3.22.1 = Gauge32: 1500 enterprises.2352.2.4.1.3.1.3.22.2 = Gauge32: 1800 enterprises.2352.2.4.1.3.1.3.22.3 = Gauge32: 2600 enterprises.2352.2.4.1.3.1.3.22.4 = Gauge32: 3300 enterprises.2352.2.4.1.3.1.3.24.1 = Gauge32: 1200 enterprises.2352.2.4.1.3.1.3.24.2 = Gauge32: 1200 enterprises.2352.2.4.1.3.1.3.24.3 = Gauge32: 1300 enterprises.2352.2.4.1.3.1.3.24.4 = Gauge32: 1800 enterprises.2352.2.4.1.3.1.3.24.5 = Gauge32: 2500 enterprises.2352.2.4.1.3.1.3.24.6 = Gauge32: 3300 enterprises.2352.2.4.1.3.1.3.24.7 = Gauge32: 12000 enterprises.2352.2.4.1.3.1.3.24.8 = Gauge32: 900 enterprises.2352.2.4.1.3.1.3.24.9 = Gauge32: 1500 enterprises.2352.2.4.1.3.1.4.11.1 = Gauge32: 1513 enterprises.2352.2.4.1.3.1.4.11.2 = Gauge32: 1801 enterprises.2352.2.4.1.3.1.4.11.3 = Gauge32: 2480 enterprises.2352.2.4.1.3.1.4.11.4 = Gauge32: 3304 enterprises.2352.2.4.1.3.1.4.22.1 = Gauge32: 1513 enterprises.2352.2.4.1.3.1.4.22.2 = Gauge32: 1801 enterprises.2352.2.4.1.3.1.4.22.3 = Gauge32: 2574 enterprises.2352.2.4.1.3.1.4.22.4 = Gauge32: 3304 enterprises.2352.2.4.1.3.1.4.24.1 = Gauge32: 1176 enterprises.2352.2.4.1.3.1.4.24.2 = Gauge32: 1181 enterprises.2352.2.4.1.3.1.4.24.3 = Gauge32: 1284 enterprises.2352.2.4.1.3.1.4.24.4 = Gauge32: 1777 enterprises.2352.2.4.1.3.1.4.24.5 = Gauge32: 2465 enterprises.2352.2.4.1.3.1.4.24.6 = Gauge32: 3242 enterprises.2352.2.4.1.3.1.4.24.7 = Gauge32: 11938 enterprises.2352.2.4.1.3.1.4.24.8 = Gauge32: 876 enterprises.2352.2.4.1.3.1.4.24.9 = Gauge32: 1494 enterprises.2352.2.4.1.4.1.2.11.1 = "Temperature sensor on slot 1" enterprises.2352.2.4.1.4.1.2.22.1 = "Temperature sensor on slot 4" enterprises.2352.2.4.1.4.1.2.24.1 = "Temperature sensor on slot 6 - Processor" enterprises.2352.2.4.1.4.1.2.24.2 = "Temperature sensor on slot 6 - Exhaust Air" enterprises.2352.2.4.1.4.1.2.24.3 = "Temperature sensor on slot 6 - Inlet Air" enterprises.2352.2.4.1.4.1.2.29.1 = "Fan Tray Temperature sensor" enterprises.2352.2.4.1.4.1.3.11.1 = Gauge32: 58 enterprises.2352.2.4.1.4.1.3.22.1 = Gauge32: 60 enterprises.2352.2.4.1.4.1.3.24.1 = Gauge32: 53 enterprises.2352.2.4.1.4.1.3.24.2 = Gauge32: 38 enterprises.2352.2.4.1.4.1.3.24.3 = Gauge32: 35 enterprises.2352.2.4.1.4.1.3.29.1 = Gauge32: 0 enterprises.2352.2.4.1.6.1.2.11.1 = "Temperature sensor on slot 1" enterprises.2352.2.4.1.6.1.2.22.1 = "Temperature sensor on slot 4" enterprises.2352.2.4.1.6.1.2.24.1 = "Temperature sensor on slot 6 - Processor" enterprises.2352.2.4.1.6.1.2.24.2 = "Temperature sensor on slot 6 - Exhaust Air" enterprises.2352.2.4.1.6.1.2.24.3 = "Temperature sensor on slot 6 - Inlet Air" enterprises.2352.2.4.1.6.1.2.29.1 = "Fan Tray Temperature sensor" enterprises.2352.2.4.1.6.1.3.11.1 = Gauge32: 58 enterprises.2352.2.4.1.6.1.3.22.1 = Gauge32: 60 enterprises.2352.2.4.1.6.1.3.24.1 = Gauge32: 53 enterprises.2352.2.4.1.6.1.3.24.2 = Gauge32: 38 enterprises.2352.2.4.1.6.1.3.24.3 = Gauge32: 35 enterprises.2352.2.4.1.6.1.3.29.1 = Gauge32: 0 -- Evgenii V Davidov From lukasz at alfa-system.pl Tue Dec 18 11:26:47 2018 From: lukasz at alfa-system.pl (=?UTF-8?Q?=c5=81ukasz_Kopiszka?=) Date: Tue, 18 Dec 2018 17:26:47 +0100 Subject: [rbak-nsp] BGP - neighbor peer-as In-Reply-To: <94e2950e-c5e2-b624-4162-50006c31da7a@alfa-system.pl> References: <94e2950e-c5e2-b624-4162-50006c31da7a@alfa-system.pl> Message-ID: Problem solved: ? neighbor 192.168.12.184 external ??? remote-as 65000 ??? address-family ipv4 unicast ????? route-map wanguard-in in ????? route-map wanguard-out out -- Pozdrawiam, ?ukasz Kopiszka http://alfa-system.pl From lukasz at alfa-system.pl Tue Dec 18 11:43:09 2018 From: lukasz at alfa-system.pl (=?UTF-8?Q?=c5=81ukasz_Kopiszka?=) Date: Tue, 18 Dec 2018 17:43:09 +0100 Subject: [rbak-nsp] BGP inaccessible next-hop Message-ID: <7d62bfee-0108-f570-3587-f33d6ed9fbc2@alfa-system.pl> Hi, My lab config: context BGP ?community-list REDIRECT ? seq 10 permit 65000:667 ?route-map rm-in permit 200 ? match community-list REDIRECT ? set ip next-hop 192.168.99.89 ?route-map rm-out deny 10 ? neighbor 192.168.12.184 external ??? remote-as 65000 ??? address-family ipv4 unicast ????? route-map rm-in in ????? route-map rm-out out ?ip route 192.168.99.89/32 context FILTER context FILTER ?interface int1 ? ip address 192.168.99.89/30 ?ip route 0.0.0.0/0 192.168.99.90 First step I'm marking IP 93.179.215.2 with community 6500:667 BGP#show bgp route 93.179.215.2/32 BGP ipv4 unicast routing table entry: 93.179.215.2/32, version 0 Paths: total 1, best path count 0, best peer 0.0.0.0 Not downloaded to RIB (no bestpath) Not advertised to any peer 65000 ? Nexthop 192.168.99.89 (inaccessible), peer 192.168.12.184 (192.168.12.184), AS 65000 ? Origin IGP, localpref 100, med 0, weight 100, external ? Community: 65000:667 Problem: next-hop 192.168.99.89 is inaccessible Question: How can I solve issue with inaccessible next-hop to FILTER context? PS: IP 192.168.99.90/30 is interface on PC with running tcpdump but there is no incomming traffic. -- Pozdrawiam, ?ukasz Kopiszka http://alfa-system.pl From lukasz at alfa-system.pl Tue Dec 18 11:43:09 2018 From: lukasz at alfa-system.pl (=?UTF-8?Q?=c5=81ukasz_Kopiszka?=) Date: Tue, 18 Dec 2018 17:43:09 +0100 Subject: [rbak-nsp] BGP inaccessible next-hop Message-ID: <7d62bfee-0108-f570-3587-f33d6ed9fbc2@alfa-system.pl> Hi, My lab config: context BGP ?community-list REDIRECT ? seq 10 permit 65000:667 ?route-map rm-in permit 200 ? match community-list REDIRECT ? set ip next-hop 192.168.99.89 ?route-map rm-out deny 10 ? neighbor 192.168.12.184 external ??? remote-as 65000 ??? address-family ipv4 unicast ????? route-map rm-in in ????? route-map rm-out out ?ip route 192.168.99.89/32 context FILTER context FILTER ?interface int1 ? ip address 192.168.99.89/30 ?ip route 0.0.0.0/0 192.168.99.90 First step I'm marking IP 93.179.215.2 with community 6500:667 BGP#show bgp route 93.179.215.2/32 BGP ipv4 unicast routing table entry: 93.179.215.2/32, version 0 Paths: total 1, best path count 0, best peer 0.0.0.0 Not downloaded to RIB (no bestpath) Not advertised to any peer 65000 ? Nexthop 192.168.99.89 (inaccessible), peer 192.168.12.184 (192.168.12.184), AS 65000 ? Origin IGP, localpref 100, med 0, weight 100, external ? Community: 65000:667 Problem: next-hop 192.168.99.89 is inaccessible Question: How can I solve issue with inaccessible next-hop to FILTER context? PS: IP 192.168.99.90/30 is interface on PC with running tcpdump but there is no incomming traffic. -- Pozdrawiam, ?ukasz Kopiszka http://alfa-system.pl From me at geordish.org Tue Dec 18 15:56:29 2018 From: me at geordish.org (Dave Bell) Date: Tue, 18 Dec 2018 20:56:29 +0000 Subject: [rbak-nsp] BGP inaccessible next-hop In-Reply-To: <7d62bfee-0108-f570-3587-f33d6ed9fbc2@alfa-system.pl> References: <7d62bfee-0108-f570-3587-f33d6ed9fbc2@alfa-system.pl> Message-ID: Thats odd that this doesn't work, but I guess a BGP route can't recurse to a static route for some reason? Try an inter-context interface instead. That seems to work. context BGP interface int2 intercontext p2p 1 ip address 10.0.0.1/30 community-list REDIRECT seq 10 permit 65000:667 route-map rm-in permit 200 match community-list REDIRECT set ip next-hop 10.0.0.2 route-map rm-out deny 10 neighbor 192.168.12.184 external remote-as 65000 address-family ipv4 unicast route-map rm-in in route-map rm-out out ip route 192.168.99.89/32 context FILTER context FILTER interface int1 ip address 192.168.99.89/30 interface int2 intercontext p2p 1 ip address 10.0.0.2/30 ip route 0.0.0.0/0 192.168.99.90 Dave On Tue, 18 Dec 2018 at 16:44, ?ukasz Kopiszka wrote: > Hi, > > My lab config: > > context BGP > > community-list REDIRECT > seq 10 permit 65000:667 > > route-map rm-in permit 200 > match community-list REDIRECT > set ip next-hop 192.168.99.89 > > route-map rm-out deny 10 > > neighbor 192.168.12.184 external > remote-as 65000 > address-family ipv4 unicast > route-map rm-in in > route-map rm-out out > > ip route 192.168.99.89/32 context FILTER > > context FILTER > > interface int1 > ip address 192.168.99.89/30 > > ip route 0.0.0.0/0 192.168.99.90 > > > First step I'm marking IP 93.179.215.2 with community 6500:667 > > BGP#show bgp route 93.179.215.2/32 > BGP ipv4 unicast routing table entry: 93.179.215.2/32, version 0 > Paths: total 1, best path count 0, best peer 0.0.0.0 > Not downloaded to RIB (no bestpath) > Not advertised to any peer > > 65000 > Nexthop 192.168.99.89 (inaccessible), peer 192.168.12.184 > (192.168.12.184), AS 65000 > Origin IGP, localpref 100, med 0, weight 100, external > Community: 65000:667 > > Problem: > next-hop 192.168.99.89 is inaccessible > > > Question: > How can I solve issue with inaccessible next-hop to FILTER context? > > > PS: IP 192.168.99.90/30 is interface on PC with running tcpdump but > there is no incomming traffic. > > > -- > Pozdrawiam, > ?ukasz Kopiszka > http://alfa-system.pl > > _______________________________________________ > redback-nsp mailing list > redback-nsp at puck.nether.net > https://puck.nether.net/mailman/listinfo/redback-nsp > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukasz at alfa-system.pl Tue Dec 18 22:16:45 2018 From: lukasz at alfa-system.pl (=?UTF-8?Q?=c5=81ukasz_Kopiszka?=) Date: Wed, 19 Dec 2018 04:16:45 +0100 Subject: [rbak-nsp] BGP inaccessible next-hop In-Reply-To: References: Message-ID: <9d27824a-a95f-ae28-5978-6172a7a15d60@alfa-system.pl> Nexthop is accessible but still no incomming traffic from redirected IP in FILTER context. Probably I'm missing something in configuration which will pass traffic from redirected IP. On FILTER context I try to "start shell" and tcpdump but there is no traffic from redirected IP. Is there a other way to monitor specific interface than "start shell" and tcpdump? -- Pozdrawiam, ?ukasz Kopiszka https://alfa-system.pl From S.Mikhaylovskiy at vconnect.ru Wed Dec 19 06:36:24 2018 From: S.Mikhaylovskiy at vconnect.ru (Mikhaylovskiy Sergey) Date: Wed, 19 Dec 2018 11:36:24 +0000 Subject: [rbak-nsp] se1200 link-group maximum-links Message-ID: Hello, there may be more than 8 ports in SE1200? Table 15 lists the range of values for the max-active argument when configuring an 802.1Q, Ethernet, or access link group with SmartEdge 100 native ports, FE and GE ports on media interface cards (MICs), or SmartEdge 400 and SmartEdge 800 traffic cards. Table 15 Range of Values for max-active Argument Port Type Link Group Type Range of Values GE3, GE1020, 10GE Access 1 to 2(1) Ethernet 1 to 8 802.1Q 1 to 8 FE, GE (all other versions) Access 1 to 8 Ethernet 1 to 8 802.1Q 1 to 8 (1) Configuring a value of 2 is subject to configuration restrictions. See the paragraph immediately following this table ? ?????????, ?????? ???????????? ????? ???????? ????? ???????? ??????, ??????? ??????? ?????? ???????? Virgin Connect 141092, ?????????? ???., ?. ???????, ???. ?????????, ??. ??????, 14?. ?: +7 (498) 300 39 65 ?: s.mikhaylovskiy at vconnect.ru Save paper! Don?t print / ???????? ???????! ?? ?????????????? [cid:image001.png at 01D497A8.4A830F30] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6035 bytes Desc: image001.png URL: From brandonl at localtel.com Wed Dec 19 09:30:51 2018 From: brandonl at localtel.com (Brandon Leeberg) Date: Wed, 19 Dec 2018 14:30:51 +0000 Subject: [rbak-nsp] se1200 link-group maximum-links In-Reply-To: References: Message-ID: <1dee46224dc64c0aad6a19cebcbc5167@localtel.com> I would also like to know if an access link-group can have more than 2 in an SE1200. I?m thinking no, but it would be great? From: redback-nsp [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Mikhaylovskiy Sergey Sent: Wednesday, December 19, 2018 3:36 AM To: 'redback-nsp at puck.nether.net' Subject: [rbak-nsp] se1200 link-group maximum-links Hello, there may be more than 8 ports in SE1200? Table 15 lists the range of values for the max-active argument when configuring an 802.1Q, Ethernet, or access link group with SmartEdge 100 native ports, FE and GE ports on media interface cards (MICs), or SmartEdge 400 and SmartEdge 800 traffic cards. Table 15 Range of Values for max-active Argument Port Type Link Group Type Range of Values GE3, GE1020, 10GE Access 1 to 2(1) Ethernet 1 to 8 802.1Q 1 to 8 FE, GE (all other versions) Access 1 to 8 Ethernet 1 to 8 802.1Q 1 to 8 (1) Configuring a value of 2 is subject to configuration restrictions. See the paragraph immediately following this table ? ?????????, ?????? ???????????? ????? ???????? ????? ???????? ??????, ??????? ??????? ?????? ???????? Virgin Connect 141092, ?????????? ???., ?. ???????, ???. ?????????, ??. ??????, 14?. ?: +7 (498) 300 39 65 ?: s.mikhaylovskiy at vconnect.ru Save paper! Don?t print / ???????? ???????! ?? ?????????????? [cid:image001.png at 01D49764.61C80810] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6035 bytes Desc: image001.png URL: