Author: mystajones
-
+
+
+
+
+
+
A multi function device failure in the far reaches of Australia requiring a quick re-route of the line from ISDN in to PSTN out and ‘boom’ we’re up and running again. From: dial-peer voice 1001 pots description *** Site Fax Number destination-pattern 0001 port 0/2/0 forward-digits all To: dial-peer voice 1001 pots trunkgroup…
-
A memory jogger for me, to view a failed call on the ISDN line. Disconnect Codes term mon debug isdn q931
-
Another option for your WLC on a VM 🙂 http://www.cisco.com/c/en/us/support/docs/wireless/virtual-wireless-controller/113677-virtual-wlan-dg-00.pdf
-
+
+
+
+
+
+
Every now and then you’ll have to use this command to verify Power Supply and other system environmental status. ROUTER#sh environment all SYSTEM POWER SUPPLY STATUS ========================== Internal Power Supply 1 Type: AC Internal Power Supply 1 Input Status and 12V Output Status: Fail Internal Power Supply 2 Type: AC…
-
+
+
+
+
+
+
Logical Construct of a Multi Tenant VxLAN EVPN with a Single Tenant in a VRF on a Nexux 9k One VLAN maps to one Layer-2 VNI Layer-2 VNI per Layer-2 segment A Tenant can have multiple VLANs, therefore multiple Layer-2 VNIs Traffic within one Layer-2 VNI is bridged Traffic between…
-
+
+
+
+
+
+
High availability gateways between multiple routers. A few options to choose from are typically HSRP (Hot Standby Routing Protocol) more common to our Cisco friends, or the more widely used standards based VRRP (Virtual Route Redundancy Protocol), of course there’s GLBP too but i’ll leave that one for a rainy…
-
+
+
+
+
+
+
Useful Quick Link
-
+
+
+
+
+
+
Inconsistent echo-reply from devices connected via VPC to Nexus 9300 while pinging from the Nexus exec prompt. With some of the testing I receive normal response when pinging from one Nexus, but no response when pinging from the other. In another test I receive a normal response to one Nexus, and duplicate replys…
-
Here’s a little something to help my fellow users out, in extending the disk allocation of Cisco Prime. Note; this is not something you will find in any Cisco documentation anywhere! It is aimed at stopping the /opt file system from filling up. Which would never have occurred had the Storage Guy allocated the…