So if a line card fails in a Cisco device and the chassis is rebooted, then the ifindex for all or some of the interfaces may suddenly change. To combat this enter the following command:
1 | snmp-server ifindex persist |
This command will globally fix the ifindex of interfaces. Here’s the Cisco link.
We were recently doing some chassis replacements and I got my final ASR 9000 chassis in. We were able to successfully upgrade it and were letting it do its customary hardware burn in when we notice some odd messages hitting the log:
RP/0/RSP0/CPU0:Nov 8 13:44:57.220 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAILURE : Power-module 0/PS0/M0/SP failure condition raised
RP/0/RSP0/CPU0:Nov 8 13:44:58.322 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAIL_REASON : Power-module 0/PS0/M0/SP fail reason: Module shutdown due to no external stable input power feed present
RP/0/RSP0/CPU0:Nov 8 13:44:58.322 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAILURE : Power-module 0/PS0/M1/SP failure condition raised
RP/0/RSP0/CPU0:Nov 8 13:44:59.425 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAIL_REASON : Power-module 0/PS0/M1/SP fail reason: Module shutdown due to no external stable input power feed present
RP/0/RSP0/CPU0:Nov 8 13:44:59.425 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAILURE : Power-module 0/PS0/M2/SP failure condition raised
RP/0/RSP0/CPU0:Nov 8 13:45:00.527 CST: pwrmon[381]: %PLATFORM-PWRMON-2-MODULE_FAIL_REASON : Power-module 0/PS0/M2/SP fail reason: Module shutdown due to no external stable input power feed present
When we tried to examine the modules we got the following:
RP/0/RSP1/CPU0#admin sh env power
Fri Nov 8 12:05:33.672 CST
R/S/I Modules Capacity Status
(W)
0/PS0/M0/*
host PM 0 Unpowered0/PS0/M1/*
host PM 0 Unpowered0/PS0/M2/*
host PM 0 UnpoweredR/S/I Power Supply Voltage Current
(W) (V) (A)
0/PS0/M0/* 0.0 0.0 0.0
0/PS0/M1/* 0.0 0.0 0.0
0/PS0/M2/* 0.0 0.0 0.0
————–
Total: 0.0
Our chassis has 4 horizontal PSUs, and the info above is only showing 3 slots, and none are registering power…but the chassis is up and working. It turns out the chassis comes with several hardware configurations, and the operator can make configuration changes that tell the chassis which it is utilizing. For some reason this chassis decided to default to the wrong configuration.
Check this link for full options.
First the following is run to begin the process to change the PSU configuration:
1 2 3 4 5 6 7 8 9 10 | RP/0/RSP0/CPU0:RO9_P2RSP3# run Wed Jul 4 20:18:58.034 UTC # pwrmod_change Current system: power supply type : AC power supply version 2 chassis type : 10-slot chassis bpid: 0x2fa, PID: ASR-9010-AC UDI name: ASR-9010 AC, UDI desc: ASR-9010 AC |
This chart gives you the options to enter:
Please enter the number that corresponds to the power supply type that is being migrated
to. Do not enter the current power system information, use the future power system type.
1) AC power supply version 1, fits 3 across in single power shelf
2) DC power supply version 1, fits 3 across in single power shelf
3) AC power supply version 2, fits 4 across in single power shelf
4) DC power supply version 2, fits 4 across in single power shelf
5) AC power supply version 3, fits 3 across in single power shelf
6) DC power supply version 3, fits 4 across in single power shelf
ATTENTION: You are about to commit a change in the power system type for the chassis.
Please confirm that the OLD and NEW power system information listed here is correct.
Once the system software change is committed, you must physically remove the OLD power
system and replace it with the NEW power system of the type specified below here. Any
mismatch between the programmed system value and the actual physical installation may
cause boot and power management issues in the system.
From here I just entered the number 3 because I have 4 AC power supplies horizontal on one shelf. Shortly after entering the command everything was showing up properly, and all was right with the world. I hope this helps you out, as it can be a bit obtuse to diagnose.
Happy routing folks 🙂
This week Greg,Tomas, Nick, and Tommy talk about networking and listen to traffic driving by Tomas’ house.
This week we talk about:
– George A had a cheap SM OTDR he likes…I wonder if he still does?
– Use caution with cambium 3000s and it looks like 4.4.2 firmware is “pretty good” so far.
– Several of us have played with the Mikrotik Audience so far: Review sample from ISPSupplies!
– IPv6 tracing – imcpv6 vs. udp
– Unifi LTE – LTE gateway
– Unifi Dream Machine – new router AP for the house
– Ubiquiti UAP-Beacon HD mesh AP
– UBNT stealthily enables data collection
– Why does Nick B maintain so many random domains?
– Tomas is introducing a “Linux-desktop-only” policy at Unimus – should be fun times…
Help support us by becoming a patron! <==join our Slack team!
Keep contacting us: contactus (at) thebrotherswisp.com or https://facebook.com/thebrotherswisp
Click the link below to view the article!
This week Greg, Mikey, Tomas, Cox, Thrift, Miller, Alex, Tom, and new friend Serena get deep on some interesting tops and reflect on 100 episodes over 7 years.
This week we talk about:
– Michael Ducharme – route cache update. Stale routes could be cached for months. Subnets deleted from a router still cache network and broadcast addresses for months and those IPs are unreachable.
– Fortnite END event
– Zayo sets local preference on customer connections to 200 by default…dirty rascals.
– Virtual router efficiencies. Mikrotik is better on vmware in v6 kernal due to old drivers.
– VLAN 1002-1005 in Cisco is a no-go.
– Nvidia (new version out now!) shields for streaming. (and plex!)
– Reflections on 100 episodes over 7 years.
Help support us by becoming a patron! <==join our Slack team!
Keep contacting us: contactus (at) thebrotherswisp.com or https://facebook.com/thebrotherswisp
Click the link below to view the article!
I was recently working with a WISP doing some network upgrades, when I hit an issue I hadn’t stumbled upon before. Their previous engineer had set them up on VLANs 1001, 1002, 1003, and 1004. I tried swapping them over to using a Cisco 4948(which is a great switch) in their core, but as it turns out only VLAN 1001 would work. After doing some quick research I see the following when I do a “show vlan”:
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
I’ve seen these show up a million times before, but I never bothered looking too close. It’s obvious from the VLAN names that they are old legacy token ring and FDDI VLANs, which who cares, right? The part I missed was act/unsup. The “unsp” stands for unsupported. This means that these VLANs are completely unusable no matter what you do. I’m not sure if this holds true for every Cisco switch, but it appears to be the case for the majority of the catalyst line.
So, for compatibility’s sake, you may want to avoid those VLANs in your network, even if you aren’t using Cisco kit.
Good luck and happy switching.
This week Greg, Mikey, and Tomas do the dirty minutes before everyone leaves for WISPAPALOOZA; have fun errbody!
This week we talk about:
Nick A got married; oh to be young and in love.
Quote of the week “He doesn’t pay me enough to shut up.” – John Osmon
The slack recommends 4 port Intel SFP+ interfaces(x710-da4).
Thomas recommends a Pi4 for projects that need to do a gig for remote BW tests
Thrift says: disabling route cache will cause you more problems than it solves. V7 has no route-cache in kernel.
Mikrotik broadcast/multicast storms can make the router inaccessible, but may not lock it up.
Thomas says : virtually all models of FiberStore switches have different firmware/CLI/syntax
Carlan has an interesting idea to vinyl wrap antennas to have them blend in
Matt Whitely shares viso cafe free stencils
Carlan also shares yEd graphing…has some neat auto spacing options
Ubiquiti unifi flexHD access point
Greg’s Lincoln Log PC
WISPAPALOOZA
Security:
Cisco ASA DoS
Win NTLM domain takeover
“Automation Thinking”
Help support us by becoming a patron! <==join our Slack team!
Keep contacting us: contactus (at) thebrotherswisp.com or https://facebook.com/thebrotherswisp
Click the link below to view the article!
This week Greg, Mikey, and Tomas do a lot with a little, and at the end we get a patented Mike rant in place of the normal Tomas one LOL
This week we talk about:
Warshipping
WISPAPALOOZA 2019
Mikoritk trolled us with the “new hardware found in new NPK file”…thanks Obama
ROS v7 alpha 2 out, CHR release available
Colin asks about 802.3ad(LACP) and how to distribute traffic. Transmit hasing, bro.
Mikrotik CSS port security – lock on first, no other options.
Chad had random reboot issues 6.44.5 long term- official response “might be bonding issue fixed in 6.45”
Jeremy asks about notification systems: pagerduty, opsgenie, victorops, email to sms
NetXMS 3.0 released
Mike complains about municipalities and fiber – he complains about everything
Help support us by becoming a patron! <==join our Slack team!
Keep contacting us: contactus (at) thebrotherswisp.com or https://facebook.com/thebrotherswisp
Click the link below to view the article!