swinog

swinog@lists.swinog.ch

1 participants
2934 discussions

Selling Cisco 7206 VXR NPEG1 - good price
by Hofer Ruedi 22 Nov '17

22 Nov '17

Dear all I am selling 3 x Cisco 7206 VXR / NPEG1 / dual power supply They were bought in 2003 and used until recently. They are in good condition and clean. See tech spec below for details. Price: CHF33.30/piece (bid >0 welcome;) - No guarantee No Support - No Lasers - No Cables - No Shipping, pickup at our premises only, see address below - Cash-only payment First come first served. Please contact me offlist if interestet. mailto:ruedi.hofer@ewb.ch Freundliche Grüsse Ruedi Hofer Leiter Telecom Center Energie Wasser Bern Monbijoustrasse 11, Postfach, 3001 Bern ruedi.hofer(a)ewb.ch<mailto:ruedi.hofer@ewb.ch>, ewb.ch<http://www.ewb.ch/> Summary : - Cisco 7206VXR, 6-slot chassis - NPE-G1 / 512MB RAM / 64MB Flash Card - 3x1GB Interface Web Refrence : https://www.cisco.com/c/en/us/td/docs/routers/7200/install_and_upgrade/netw… ####################################### RAW DATA ################################################## ewb-ch-emc-brn01-rm-01#sh inventory raw NAME: "Chassis", DESCR: "Cisco 7206VXR, 6-slot chassis" PID: CISCO7206VXR , VID: , SN: 30827013 NAME: "I/O and CPU Slot 0", DESCR: "I/O and Processor Slot Container" PID: , VID: , SN: NAME: "NPE-G1 0", DESCR: "Cisco 7200 Series Network Processing Engine NPE-G1" PID: NPE-G1 , VID: , SN: 31248843 NAME: "GBIC Port Container 0/1", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/1", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/2", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/2", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/3", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/3", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "Flash Card Slot Container CPU", DESCR: "Flash Card Slot Container CPU" PID: , VID: , SN: NAME: "disk2", DESCR: "64MB Compact Flash Disk for NPE-G1" PID: MEM-NPE-G1-FLD64 , VID: , SN: NAME: "NPE Inlet Temperature 0", DESCR: "NPE Inlet Temperature Sensor" PID: , VID: , SN: NAME: "NPE Outlet Temperature 0", DESCR: "NPE Outlet Temperature Sensor" PID: , VID: , SN: NAME: "+3.45 V Voltage 0", DESCR: "+3.45 V Voltage Sensor" PID: , VID: , SN: NAME: "+5.15 V Voltage 0", DESCR: "+5.15 V Voltage Sensor" PID: , VID: , SN: NAME: "+12.15 V Voltage 0", DESCR: "+12.15 V Voltage Sensor" PID: , VID: , SN: NAME: "-11.95 V Voltage 0", DESCR: "-11.95 V Voltage Sensor" PID: , VID: , SN: NAME: "Gi0/1", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/2", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/3", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "PA Slot 1", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 2", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 3", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 4", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 5", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 6", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PEM 0", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 0", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: NAME: "PEM 1", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 1", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: ewb-ch-emc-brn01-rm-01#sh ver ewb-ch-emc-brn01-rm-01#sh version Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(8c), RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Tue 12-Dec-06 03:30 by prod_rel_team ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1) BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(15)B, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) System image file is "disk2:c7200-jk9o3s-mz.124-8c.bin" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export(a)cisco.com<mailto:export@cisco.com>. Cisco 7206VXR (NPE-G1) processor (revision A) with 491520K/32768K bytes of memory. Processor board ID 30827013 SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache 6 slot VXR midplane, Version 2.7 Last reset from power-on PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points. Current configuration on bus mb1 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points. Current configuration on bus mb2 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. Please refer to the following document "Cisco 7200 Series Port Adaptor Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com> for c7200 bandwidth points oversubscription and usage guidelines. 3 Gigabit Ethernet interfaces 509K bytes of NVRAM. 62976K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes). 16384K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2102

1 0

Re: [swinog] RIPE database and more specific routes
by Scott Weeks 21 Nov '17

21 Nov '17

: But I am concerned some people may build filters using : only exact matches, so it seems safer to have route : objects for more specifics. :: I´d suggest to create each route object for each :: announced prefix...IMHO you are very right - there are :: for sure networks out there, which will filter your :: prefixes, when you do not have a matching route object :: entry ... That seems painful when fast action is required. Say you have a /16 and someone is hijacking a /23 withing it. Before mitigating damage by announcing the two /24s you'd have to update the registry and wait for the upstream to accept it? Do you just preregister all the /24, /23, /22, etc prefix combinations in advance? scott _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

1 0

Selling Cisco 7206 VXR NPEG1 - new price
by Hofer Ruedi 20 Nov '17

20 Nov '17

1 0

RIPE database and more specific routes
by Vincent Bernat 20 Nov '17

20 Nov '17

Hey! I am updating the route/inetnum objects in the RIPE database and I am wondering if I have to create more specific route objects. For example, I have the following routes announced: - 89.145.160.0/21 - 89.145.160.0/22 (FR7) - 89.145.164.0/23 (DK2) - 89.145.166.0/23 (GV2) Each more specific route is announced in a different location. Should I create only the top route object or should I create a route object for each announce? If I look at bgpq3, I see by default, it uses exact matches: $ bgpq3 -4 -J -E AS61098 | grep 89.145 route-filter 89.145.160.0/21 exact; route-filter 89.145.160.0/22 exact; route-filter 89.145.164.0/23 exact; route-filter 89.145.166.0/23 exact; However, I use it this way: $ bgpq3 -R 24 -4 -J -E AS61098 | grep 89.145 route-filter 89.145.160.0/21 upto /24; But I am concerned some people may build filters using only exact matches, so it seems safer to have route objects for more specifics. -- If more of us valued food and cheer and song above hoarded gold, it would be a merrier world. -- J.R.R. Tolkien

3 2

Hoodie found @ SwiNOG #32
by Steven Glogger 10 Nov '17

10 Nov '17

Who‘s missing something like this? :) greetings -steven gruss -steven

1 0

##### SwiNOG#32 - Travel Info #####
by Simon Ryf 08 Nov '17

08 Nov '17

Dear SwiNOG Community, Please find general information about the SwiNOG #32 meeting below. Date: 09.11.2017 - Registration 08h15 - 09h15 Location: Gurtenpark, Bern: https://goo.gl/maps/kuxy4QUrcoy >From Bern main station you may take: - S-Bahn S3 Belp and exit at Wabern station - Tram 9 (Wabern) and exit at Gurtenbahn stop Then take the Gurtenbahn to the Gurtenpark. -> You DO NOT have to pay a fee, just tell you attend to the SwiNOG event. Don’t throw away the ticket - you'll need it to get back down. Map (Ground Station of the cable rail): https://goo.gl/maps/5uSKtgbianM2 Suggested trains from Geneva: 06h14 Zurich: 07h02 WIRELESS ACCESS During the meeting, you have access to free WLAN! See you at SwiNOG #32! Simon Ryf SwiNOG Organisation

1 0

## Agenda - SwiNOG#32'ers - we're ready ##
by Simon Ryf 05 Nov '17

05 Nov '17

Dear SwiNOG community, Agenda for SwiNOG #32 on Tuesday 09.11.2017 on top of Gurten. Registration ends 03.10.2017 23:59:00, after that - please write us for late reg (with extra costs). We still have time for Lightning Talks, if you’re up for it, you’ll get a free voucher for the next event or if submitted before 06.11.2017 – for SwiNOG#32 CHF 100.- for 5 minutes (just saying…) Agenda http://www.swinog.ch/meetings/swinog32/ Sponsor Presentation / tba | tba (Extreme Networks) Free Range Routing or how we ditched OSPF for BGP unnumbered (based on RFC5549) | Manuel Schweizer (cloudscale.ch) As a contributor to the FRR project, I’m going to explain what FRR is and how we at cloudscale.ch are using it. Furthermore, I will shed some light at why we chose a certain x86-based hardware platform and provide a future outlook of where FRR is heading. Network Unit Testing with SaltStack | Urs Baumann (INS - Institute for Networked Solutions) Enabling unit testing in the network with Nuts (network unit testing system) and SaltStack. Technical presentation how the open source software Nuts uses SaltStack to test the network. colt onDemand - from visions in 2012 to reality in 2017 | Andreas Glag (Colt) SwissIX Update | Manuel Schweizer (SwissIX) SwissIX Update Flowmon DDoS Defender | Pavel Minařík (Flowmon) Flowmon DDoS Defender is a scalable anti-DDoS solution leveraging netflow data from routers or dedicated network probes for real-time detection and automated mitigation of volumetric attacks led against customer’s infrastructure. It provides the state of the art detection with automated mitigation within a minute, deep understanding of attack characteristics and a full-range of methods for successful attack mitigation ranging from alerting (e-mail, syslog, SNMP trap), traffic diversion (PBR, BGP, RTBH, Flowspec), execution of scripts, mitigation in cloud with Scrubbing centres or on-premise through specific out of-band DDoS systems. if (network == server) { magic happens } | Attilla de Groot (Cumulus Networks) Automating the network has become common practice. One thing that we don’t want to automate are operator mistakes on a fabric level. How can this be prevented by building a CI/CD environment using Cumulus, NetQ, Ansible and Gitlab. Introduction to LoRaWAN | Christian Mäder LoRaWAN is a network stack designed mostly to retrieve data from IoT sensors with limited power source. This talk will be an introduction to how this network stack works; like how it does the addressing and routing or what it's secrecy promises are. Piranha: where all the fishy routes meet... | Pascal Gloor (Quickline) Do you really know what's going on in your BGP? Analyse your BGP in realtime. Update - Communityrack.org and Community-IX.ch | Markus Meier (Communityrack.org) Community Update Social Event Looking forward to seeing all of you!!! Simon SwiNOG

2 1

What blacklists does @bluewin.ch use
by Benoit Panizzon 31 Oct '17

31 Oct '17

Hello List A Mailserver from a business customer of ours is blacklisted @ bluewin. The Error Message from Bluewin MXes directing to the removal site: https://www.swisscom.ch/en/res/hilfe/ip-blacklist.html Our customer has requested removal via this form, no success. Our customer has contacted bluewin and opened a trouble ticket. He got the information that his ISP (us) should take care to remove his IP from the blacklists, but is not getting any information about which blacklists. http://multirbl.valli.org Blacklisted: 0 We are at a loss. Does anyone know what kind of blacklists bluewin uses? Kind regards -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

BlueWin and Cloudmark
by DUCHET Rémy 31 Oct '17

31 Oct '17

Hello @ll, We have some customers that have spam issues when sending email to @bluewin.ch . Since 2 months, all emails sent to @bluewin.ch recipients are marked junk. Thats what we can trace : X-Bluewin-Spam-Analysis: v=2.1 cv=eL3e9Cd1 c=1 sm=1 tr=0 p=fUeVjJJZAAAA:8 a=qTcuhanu2jf2BI9KYv9RyA==:117 a=qTcuhanu2jf2BI9KYv9RyA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=K_h_1cidfDUA:10 a=xqWC_Br6kY4A:10 a=02M-m0pO-4AA:10 a=oXc4haEe4je61EW4P-sA:9 a=wPNLvfGTeEIA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=VzdpOnGMIpnfysyMU8MA:9 a=rUqq3GAnYQ2zrqZp:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=a4CKYyBK0OAZSS6edTcA:9 a=pA59YpQ9dOODYSR3:18 a=KQqxNPgzF0kA:10 a=359DcwL6FTx8MXQu2PII:22 X-Bluewin-Spam-Score: 100.00 If anybody from Bluewin can contact me off list Thanks, Rémy

1 1

Re: [swinog] ##### SwiNOG #32 - Agenda #####
by Simon Ryf 30 Oct '17

30 Oct '17

Dear SwiNOGers Final Agenda is online. http://www.swinog.ch/meetings/swinog32/index.asp (order can still change) Please hurry up with your registration, we’ll close it this Friday 23:59. After that, you’ll have to late reg with increased fee. There are still slots for Speed Talks or a 30min talk. If you think you could last minute contribute, please let me know. Would be nice :-) Tomorrow I will send you an update with a detailed Agenda including the abstracts. Br Simon Important Dates for SwiNOG#31 03.11.2017 Registration closes (only late reg possible after that) 09.11.2017 Meeting day

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog