Updaten ArborOs

Copier de upgrade bestanden naar een USB disk en plaats deze in een USB aansluiting van de Arbor TRA.

Voor de installatie een volledige back-up maken:

/ services sp backup

/services/sp/backup# show

 Backup status

 Backup state: idle
 Full backup image timestamp: Mon Mar 09 07:41:26 +0000 2015
 Incremental backup image timestamp: Tue Mar 10 07:31:42 +0000 2015
 Backup image version: 7.0.1

/services/sp/backup# create full

admin@TRA:/services/sp/backup# show
 Backup status
 Backup state: running full backup

/services/sp/backup# show
 Backup status
 Backup state: running full backup

Totdat deze is voltooid en de state weer 'idle' word.

Om de inhoud van de USB disk op te vragen:

/ system files

admin@TRA:/system/files# dir usb:
 Peakflow-SP-7.0.2-FCCG-B 325651 May29 2015 Signed package
 arbos-6.1-FCCG-B 98610 May29 2015 Signed package

Controle bestaande OS en applicatie:

/system/files# show
 Installed packages:
 ArbOS_6.1 ArbOS 6.1 system files (build ELSJ-B) (arch x86_64)
 Peakflow-SP-7.0.1 Arbor Networks Peakflow SP (build ELSJ-B) (arch x86_64)

Stoppen van SP:

/ services sp

/services/sp# stop
Stopping Peakflow SP services......................................done.

Updaten van OS:

/ system files

/system/files# install usb:arbos-6.1-FCCG-B
Extracting package...done.
Changes to ArbOS will take effect after the next reload.

/system/files# reload
 You are about to reboot the system. Do you wish to proceed? [n] y
094: Rebooting the system..

/ system files
/system/files# show
 Installed packages:
 ArbOS_6.1 ArbOS 6.1 system files (build FCCG-B) (arch x86_64)
 Peakflow-SP-7.0.1 Arbor Networks Peakflow SP (build ELSJ-B) (arch x86_64)

Updaten van applicatie:

/ services sp stop

Stopping Peakflow SP services......................................done.

/ system files
/system/files# install usb:Peakflow-SP-7.0.2-FCCG-B
376: Peakflow-SP-7.0.2-FCCG-B conflicts with Peakflow-SP-7.0.1

 

Bij een conflict fout zoals (Peakflow-SP-7.0.2-FCCG-B conflicts with Peakflow-SP-7.0.1), eerst oude install verwijderen:

/system/files# uninstall Peakflow-SP-7.0.1 
Uninstalling package Peakflow-SP-7.0.1..done. 

/ system files install usb:Peakflow-SP-7.0.2-FCCG-B
Extracting package...done.
Collecting inventory information.done
Writing SNMP system description...done.
Upgrading to 7.0.2...
Adding direction to Host Detection table...done
Checking database schema........................................................................................................................................................................................................................................................................................done
Copying Misuse Default to Shared Host Detection Settings...done
Converting Managed Object Host Detection Settings to Shared Host Detection Settings...done
Upgrading malware fingerprint name...done
Saving ArbOS configuration...
Saving SP configuration...
Updating saved command cache (this may take a while)...done
Upgrade successful. Welcome to 7.0.2. 

De applicatie weer starten:

/ services sp start
Starting Peakflow SP services......done.

Google no longer returning AAAA records?

For the avoidance of mystery: Google performs measurements of IPv6 connectivity and latency on an ongoing basis. The Google DNS servers do not return AAAA records to DNS resolvers if our measurements indicate that for users of those resolvers, HTTP/HTTPS access to dual-stack Google services is substantially worse than to equivalent IPv4-only services. “Worse” covers both reliability (e.g., failure to load a URL) and latency (e.g., IPv6 is 100ms worse than IPv4 because it goes over an ocean). The resolvers must also have a minimum query volume, which is fairly low.

Tips:

I suggest checking if any of your affected users have broken 6to4 setups,
and that you are applying the relevant mitigations in RFC 6343.

MTU size issues and high latency have also both been mentioned as
possible reasons for the mysterious AAAA blacklist.

 

 

Netflow – FNF cheat sheet

Here’s a quick basic FNF (from ASR 1000):

flow exporter PRIMARY_NMS
 description FNF export to Primary NMS
 destination 192.168.100.100
 source Loopback0
 transport udp 9996
 template data timeout 60
!
flow monitor MONITOR_V4
 description IPv4 netflow monitor
 record netflow ipv4 original-input
 exporter PRIMARY_NMS
 cache timeout active 900
 cache entries 200000
!
flow monitor MONITOR_V6
 description IPv6 netflow monitor
 record netflow ipv6 original-input
 exporter PRIMARY_NMS
 cache timeout active 900
 cache entries 200000
!
!For each interface ....
!
interface GigabitEthernet0/0/0
 ip flow monitor MONITOR_V4 input
 ipv6 flow monitor MONITOR_V6 input
!
interface GigabitEthernet1/0/0
 ip flow monitor MONITOR_V4 input
 ipv6 flow monitor MONITOR_V6 input

sip trunk to asterisk

If the call is terminating on the 2800 ( ie ip to tdm) there is no need to transcode….

It would just be a standard sip offer/answer dialog.

As long as one codec matches it would be fine.

 

If you have 2 ip legs you should look into cisco border element configs as an SBC.

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book.html

 

You can then decide how to work the codec selection and how the cisco interacts( interferes may be a better term) with the media session between the 2 legs Transcoding would only be necessary if you have two IP legs and each leg needs to use a different codec.

Leg 1 g711a and leg2 g729 for example.

The 2800 can do this

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-border-element/100480-cube-transcode.html

IPv6 funny words

http://sophiedogg.com/funny-ipv6-words/

http://royal.pingdom.com/2009/02/06/ipv6-playtime-hiding-sentences-inside-addresses/

http://www.gossamer-threads.com/lists/nanog/users/142590

1 5 6 7 8 9 13