New to ansible and have a quick question.  When running a simple playbook to show version and show running and append to an output.  The output puts quotes around everything and displays the \n for a carriage return instead of going to the next line.  How do I get rid of the "" and have a carriage return for a "clean" output?  Thanks   here is my playbook: - name: show version   hosts: "ios-devices"   gather_facts: false   connection: local   vars:    cli:     hosts: "{{ inventory_hostname }}"     username: admin     password: cisco     transport: cli   tasks:    - name: show version      ios_command:       commands: show  run      register: output    - name: show output      debug:       var: output.stdout    - name: copy output to file      copy: content="{{ output }}" dest=./output/{{ inventory_hostname }}.txt   Snip of the output: 2018", "!", "version 15.4", "service timestamps debug datetime msec", "service timestamps log datetime msec", "no service password-encryption", "!", "hostname R1", "!", "boot-start-marker", "boot-end-marker", "!", "aqm-register-fnf", "!", "!", "aaa new-model", "!", "!", "aaa authentication login default local", "!", "!", "!", "!", "!", "aaa session-id common", "clock timezone EET 2 0", "mmi polling-interval 60", "no mmi auto-configure", "no mmi pvc", "mmi snmp-timeout 180", "!   ... View more

Good Morning,   I have been given the recent task of rebuilding a multinational enterprise network.  The previous architect created a lot of problems by doing mutual two route redistribution between several protocol in several areas causing a lot of instability. We resolved instability with a lot of complex routing policies I am not comfortable with.  The decision has been made to re-architect the whole network.     This network has five "major sites"  each one of these sites have a pair of ASRs.  The ASRs are connected in a ring and form a MPLSL3VPN backbone supported in house.  One VRF will be configured to two links to a downstream "core" at each site.  So like this: R1-PE-Site-A---mpls-----R2-PE-Site-A---mpls---R1-PE-Site-B----R2-PE-Site-B-----...and so on   Each site is like this: R1-PE-Site-A---MPLS----R2-PE-Site-A     |                                             | site A core R1-----------site a core R2   Fortunately the MPLS backbone was done well and is stable, and for now will stay in place.  The task has been given to rebuild the major sites with one protocol and remove all the redistribution within the sites causing the problem.    Long story short I am trying to figure out the "best " PE-CE routing protocol to use.  The sites will all run OSPF as an IGP due to multivendor.  Right now, I like the idea of running OSPF as PE-CE because of the downward bit preventing loops automatically.  But I also like the idea of running straight BGP since it is native and I can control path selection way easier.  AS path loop prevention is nice as well.  Myself and the team supporting is comfortable with both protocols.       Also I would like to point out that each one of the major sites has a provider managed dual connected MPLS hub.  We control the CEs at the hub that connect the provider MPLS via BGP CE-PE.   And I am worried about the downward bit on OSPF coming into a major site and being blocked into the provider managed MPLS downstream in the network.     So like this   R1-PE-Site-A---MPLS----R2-PE-Site-A     <-subnet from major site arrives here     |                                             |                         & DN bit set site A core R1-----------site a core R2            <-ospf route propagated to R1      |                                           |                              & R2 DN bit set AR1                                        AR2                       |                                               | Provider 1 MPLS                    Provider 2 MPLS   <-ospf route blocked due to dn bit |                                                   | smaller remote sites--------smaller remote sites   Log story short what is the best PE-CE peering at the major sites to the ASR company managed MPLS backbone?   Thanks in advance! ... View more

I have what should be a simple issue, and I think I may be missing the basics.  I am moving a internet circuit from one DC to another.  The circuit currently terminates on an ASR 1002 IOSXE 03.06.00.S.  In preparation for the cut over I terminated the SMF (1-GBASE-LX/LH) on a Nexus 5548 to validate the cross connect and that I could ping across the /30 to the provider.  This was working after forcing 1000/full and disabling auto neg.  (XOs Ciena switch does not do auto neg. and this is forced on their side)  here is the port config on the 5548..  The SVI in vlan 750 was in the /30 and could ping. interface Ethernet1/18   no cdp enable   switchport access vlan 750   speed 1000   duplex full   no negotiate auto I moved the ASR 1002 and moved the port to the ASR and nothing.    Same port and provider we had before.  I confirmed with XO that this is the port.  And we are seeing correct light levels  and polarity (see below.)   XO confirms they are not learning a MAC on the Ciena switch but they see the correct light levels and I have called twice and they say all is good in the configuration on their side.  I tried a different SFP and the same.  I moved the cable back to the 5548 and it works..   The only difference I see is forcing the speed and duplex but this is not allowed on fiber ports on ASR to my knowledge.   ARP is flushed on the XO side, and the 5548 was removed last night.  /30 is correct. Any ideas here?  I do not get ARP from the other side of the /30.   I fell like this is basic and stupid but maybe someone can point something out.   This ASR terminated another XO internet connection at the old DC for years on this port. Thanks ar1.strlng.clevoh#show hw-module subslot 0/1 transceiver 1 status The Transceiver in slot 0 subslot 1 port 1 is enabled.   Module temperature                        = +24.953 C   Transceiver Tx supply voltage             = 3302.5 mVolts   Transceiver Tx bias current               = 12722 uAmps   Transceiver Tx power                      = -7.1 dBm   Transceiver Rx optical power              = -8.1 dBm ar1.strlng.clevoh# ar1.strlng.clevoh#show hw-module subslot 0/1 transceiver 1 idprom IDPROM for transceiver GigabitEthernet0/1/1:   Description                               = SFP optics (type 3)   Transceiver Type:                         = GE LX (20)   Product Identifier (PID)                  = GLC-LH-SMD            Vendor Revision                           = 00   Serial Number (SN)                        = AVJ190436HR       Vendor Name                               = CISCO             Vendor OUI (IEEE company ID)              = 00.17.6A (5994)   CLEI code                                 = WOTRB9YBAA   Cisco part number                         = 10-2625-01   Device State                              = Enabled.   Date code (yy/mm/dd)                      = 15/01/20   Connector type                            = LC.   Encoding                                  = 8B10B                                               NRZ   Nominal bitrate                           = GE (1300 Mbits/s)   Minimum bit rate as % of nominal bit rate = not specified   Maximum bit rate as % of nominal bit rate = not specified GigabitEthernet0/1/1 is up, line protocol is up   Hardware is SPA-2X1GE-V2, address is c08c.6081.f411 (bia c08c.6081.f411)   Internet address is 66.3.25.xxx/30   MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,      reliability 255/255, txload 1/255, rxload 1/255   Encapsulation ARPA, loopback not set   Keepalive not supported   Full Duplex, 1000Mbps, link type is force-up, media type is LX   output flow-control is on, input flow-control is on   ARP type: ARPA, ARP Timeout 04:00:00   Last input 00:00:07, output 00:00:40, output hang never   Last clearing of "show interface" counters never   Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0   Queueing strategy: fifo   Output queue: 0/40 (size/max)   5 minute input rate 0 bits/sec, 0 packets/sec   5 minute output rate 0 bits/sec, 0 packets/sec      1069 packets input, 250182 bytes, 0 no buffer      Received 267 broadcasts (0 IP multicasts)      0 runts, 0 giants, 0 throttles      0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored      0 watchdog, 802 multicast, 0 pause input      109 packets output, 6574 bytes, 0 underruns      0 output errors, 0 collisions, 2 interface resets      0 unknown protocol drops      0 babbles, 0 late collision, 0 deferred      0 lost carrier, 0 no carrier, 0 pause output      0 output buffer failures, 0 output buffers swapped out ar1.strlng.clevoh#show run int g0/1/1  ip address 66.3.25.xxx 255.255.255.252  no ip redirects  no ip unreachables  no ip proxy-arp  media-type sfp  no negotiation auto end ... View more

I have a WLC 8500 pair setup in the centralized in the datacenter.  All APs register the 8500 and talk back to the controller and the SSIDs are Mapped to VLANs inside the datacenter via CAPWAP.  The data center is setup with multiple layer 3 boundaries crossed before traffic reaches each site where the APs are.   Everything works fine but users wish to use Airprint or bonjour so iPADs, iPhones, etc can print.  Printers are wired in at each site so this traffic is local to the site.  Is this possible when the WLC is in a remote site and needs to cross layer 3 boundaries before it sees the printer when bonjour is link local multicast?  ... View more

Does anyone have experience running GLC-SX-MM over OM4 MMF?  I don't see why it wouldn't work other than I see the talks of modal bandwidth minimum is 4700Mhz.  According to this: http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/installation/note/78_15160.html It only mentions the highest of 2000Mhz for OM3 Thanks ... View more

Not sure if this belongs in switching for wireless.  I have a weird issue on a 3650 switch.   -The network is all flat 192.168.1.0/24.   -Switch interface VLAN is the default gateway of all PCs and wireless at @192.168.1.1.   -Switch has default route to ASA @192.168.1.3 -3650 has a WLC loaded.   Everything works except for iPhones running 9.1.3.  All other wired and wireless devices work, even iPhones running version 8.   iPhones join wireless fine and get correct default gateway of 192.168.1.1.  Switch can ping phone, but the ASA cannot.  Pinging the ASA from the phone responds and an ARP entry for the phone will appear on the ASA and the phone will be able to reach the internet.  Flushing ARP entry from the ASA will cause the phone to not be able to reach the internet.  The ASA will not have an ARP entry for the phone during this time.  Pinging the ASA causes an ARP entry and phone is able to reach the internet.   Enabling proxy ARP on the switch interface VLAN causes the issue to be fixed.  Packet caps on the ASA show traffic from the phone reaching the internet with no response.  I am stumped.  TAC wants a collaboration between the switching team and wireless team tomorrow but I would like to give the customer some answers.  Thanks ... View more