About e.nieuwstad

e.nieuwstad · ‎05-20-2015

I am writing a number of modules for Ansible. The first Ansible module logs in to the UCS and gathers some basis facts including a cookie and maybe the priv. These facts are stored internally by Ansible so they can be used in further Ansible plays. Subsequent modules would use the previously generated cookie to do their magic If each module would create a session this would generate a huge load on the authentication system. It could be that each module is executed multiple times. All the modules will be executed after each other and the cookie will never reach its expiration time before the Ansible playbook finishes. Of course a final module would terminate the session again.

e.nieuwstad · ‎05-19-2015

I changed the Login method myself to have this feature. I simply added a cookie parameter to the Login Method. If a cookie is specified the cookie self._cookie will be set and the entire AaaLogin method will be skipped. The only drawback is is is that the lastUpdateTime/domains/priv/refreshPeriod/sessionId and version dont't get a value assigned. I don't believe these vars are used in any other method. Will see when I do any additional testing. I also found a minor bug when the logout is done there is no check if the cookie is already expired. No use to do it when the FI already expired the cookie.

e.nieuwstad · ‎05-13-2015

It would be nice to be able to re-attach to a session by means of the cookie. Script 1 creates the UCSHandle and returns the Cookie. Any following scripts would use that cookie to re-attach to the session and do their work. A final script would close the session. This would prevent a lot of logins a use case I am thinking about.

e.nieuwstad · ‎03-17-2015

We are trying to establish BFD on a E-BGP neighbor betweer a ASR9K and a Juniper SRX firewall. But can't seem to get it up and running. Should we also configure something on the interface regarding BFD. We don't use multihop BGP. The neighbourship is built over a L3 subinterface on a Bundle interface. Are tehre any limitatations in this?

e.nieuwstad · ‎01-28-2015

Xander, upgrade is working now. Another question when would you use the asr9k-mini-px.vm-4.3.4 and when would you use the asr9k-mini-px.pie-4.3.4 Regards Eelco

e.nieuwstad · ‎01-28-2015

We are in the progress of upgrading our ASR9001 from 4.3.0 to 4.3.4. We are having some issues with the service pack. I prefer to only activate those packages required by the router and no additional ones Install operation 35 '(admin) install activate disk0:*4.3.4* synchronous test' started by user 'cisco' via CLI at 12:20:06 UTC Wed Jan 28 2015. Warning: No changes will occur due to 'test' option being specified. The following is the predicted output Warning: for this install command. Info: This operation will activate the following packages: Info: disk0:asr9k-mini-px-4.3.4 Info: disk0:asr9k-px-4.3.4.sp5-1.0.0 Info: disk0:asr9k-mpls-px-4.3.4 Info: disk0:asr9k-mgbl-px-4.3.4 Info: disk0:asr9k-mcast-px-4.3.4 Info: disk0:asr9k-k9sec-px-4.3.4 Info: disk0:asr9k-fpd-px-4.3.4 Error: Cannot proceed with the activation because of the following package incompatibility: Error: asr9k-adv-video-supp-4.3.4.sp5-1.0.0 needs iosxr-adv-video-4.3.4, or equivalent, to be active on Error: the same nodes. Error: Suggested steps to resolve this: Error: - check the installation instructions. Error: - activate or deactivate the specified packages on the specified nodes. Install operation 35 failed at 12:20:54 UTC Wed Jan 28 2015. RP/0/RSP0/CPU0:ISLRE021(admin)# We only require those 6 packages and no more. However as in the SP% is also something related to video the upgrade fails. How can we work around this. With 4.3.0 we just selected the patches required for our configuration. I don't like to install patches for protocols we do not use for example

e.nieuwstad · ‎08-20-2014

I want to connect a L2 domain redundantly to A VPLS cloud. I am struggling to get this done without creating any loops. The customer has a its own L2 domain and wants to connect it via L2 to the VPLS cloud. As the customer has also spanned vlans between his two sites this will introduce a loop. Packets exit PE-1 to CE-1. Traversee the customer L2 cloud and reenter the VPLS cloud again Via CE-2 and PE-2. Obviously an unwanted situation. I was thinking if I could solve this with Pseudowire redundancy. If I am correct only if both ends of the PW decide the PW should become active it starts forwarding traffic. If the backups are configured as below I should only have one PW active at all times CE-1( CE11 in drawing my mistake) fails PE-1 transfers it PW to CE-2 to Active state PE-1 fails and CE-1 makes The PW to PE-2 active. The PW between PE-2 and CE-2 is just in case of a dual failure and unlikely to ever becoming active. The alternative woulde be to make CE-1 and CE-2 part of the STP domain but I prefer no to become involved in the customer L2 STP domain

e.nieuwstad · ‎01-08-2014

After a upgrade to 4.3.0 and some patches the usage of the bootflash is about 90% sh filesystem Thu Jan 9 06:46:37.933 UTC File Systems: Size(b) Free(b) Type Flags Prefixes - - network rw qsm/dev/fs/tftp: - - network rw qsm/dev/fs/rcp: - - network rw qsm/dev/fs/ftp: 1006632960 1006349312 dumper-lnk rw qsm/dumper_disk0a: 3019898880 2383787008 dumper-lnk rw qsm/dumper_harddisk: 224256 195584 dumper-lnk rw qsm/dumper_nvram: 4026515456 2631576576 dumper-lnk rw qsm/dumper_disk0: 28966912 28943732 dumper-lnk rw qsm/dumper_configflash: 44695552 4668992 dumper-lnk rw qsm/dumper_bootflash: 4026515456 2631576576 flash-disk rw disk0: 3019898880 2383787008 harddisk rw harddisk: 1006632960 1006349312 flash-disk rw disk0a: 44695552 4668992 flash rw bootflash: 28966912 28943732 flash rw configflash: 224256 195584 nvram rw nvram: ASR90001# when I look at all the files in the bootflash I am unable to locate the files which take up all this space. We have this on multiple devices. Any commands availble to show hidden files (if any) would a chkdsk fix this.

e.nieuwstad · ‎10-14-2013

In ourde design we have a vpc in which some members are Hot-stanby in bundle sh port-channel summary interface port-channel 2 Flags: D - Down P - Up in port-channel (members) I - Individual H - Hot-standby (LACP only) s - Suspended r - Module-removed S - Switched R - Routed U - Up (port-channel) M - Not in use. Min-links not met -------------------------------------------------------------------------------- Group Port- Type Protocol Member Ports Channel -------------------------------------------------------------------------------- 2 Po2(SU) Eth LACP Eth1/5(H) Eth1/6(P) this is as designed. However when we request the status via SNMP we get a down down status. The device on the other end gives the status up up which is what we want. Does anyone have a clever idea to solve it.

e.nieuwstad · ‎10-09-2013

Xander I understand the taskgroup concept however I would have liked to have a predefined task-group which has read access to everything. The concept is clear thanks again for your help.

e.nieuwstad · ‎10-08-2013

xander, I tried to second option taskgroup priv5 inherit taskgroup operator and I log in with a user who gets priv5 from the tacacs server I am even not able to do a show int brie. I would like to keep the configuration as simple as possible and in a central place. It appears this is not possible so I think I'll go with updating the tacacs-server with all the required read permissions.

e.nieuwstad · ‎10-08-2013

hi is there a simple way to grant read access to everyhting so in stead of service = exec { task = "r:bgp,r:aaa,r:interface,r:ipv4 etc etc etc etc" } i would like to do service = exec { task = "r:*" }

e.nieuwstad · ‎08-19-2013

Even better ( I guess) Gold AC PSUs (N20-PAC5-2500W) below revision version of 341-0293-10 are missing fixes implemented via ECO E106290. This fix was applied to SN QCI1534A2YR and later. One of the useful things to know with the PSUs is the manufacturing date. To figure out when the PSU was manufactured you take the first 2 numbers and add them to 1996. The next two digits are the manufacturing week. So SN QCI1534A2YR was manufactured in week 34 of 2011 (Aug 22-28). Platinum PSUs have the fix, however they had issues when they were first released that look similar to i2c – check hot issues on dcn-wiki for more info. (CSCtz59519 / CSCtx90410 ) So if the manufacturing date is key to see if you might be affected by it.

e.nieuwstad · ‎08-19-2013

We had the exact same issue with one of our chassis. After several tac cases it turned out there was a recall on the the PSU in that chassis. These PSU corrupted the I2C bus which caused these symptoms.

e.nieuwstad · ‎08-09-2013

we have this particular setup running with a N7K vpc cluster as DHD. Each N7K has one link to the active POA and one link to the standby POA. Failover works like a charm.

e.nieuwstad · 05-20-2015

I am writing a number of modules for Ansible. The first Ansible module logs in to the UCS and gather...

e.nieuwstad · 05-19-2015

I changed the Login method myself to have this feature. I simply added a cookie parameter to the Log...

e.nieuwstad · 05-13-2015

It would be nice to be able to re-attach to a session by means of the cookie. Script 1 creates the U...

e.nieuwstad · 03-17-2015

We are trying to establish BFD on a E-BGP neighbor betweer a ASR9K and a Juniper SRX firewall. But c...

e.nieuwstad · 01-28-2015

Xander, upgrade is working now.Another question when would you use theasr9k-mini-px.vm-4.3.4and when...

e.nieuwstad · 01-28-2015

We are in the progress of upgrading our ASR9001 from 4.3.0 to 4.3.4. We are having some issues with ...

e.nieuwstad · 08-20-2014

I want to connect a L2 domain redundantly to A VPLS cloud. I am struggling to get this done without ...

e.nieuwstad · 01-08-2014

After a upgrade to 4.3.0 and some patches the usage of the bootflash is about 90%sh filesystemThu Ja...

e.nieuwstad · 10-14-2013

In ourde design we have a vpc in which some members are Hot-stanby in bundlesh port-channel summary ...

e.nieuwstad · 10-09-2013

Xander I understand the taskgroup concept however I would have liked to have a predefined task-group...

e.nieuwstad · 10-08-2013

xander,I tried to second optiontaskgroup priv5 inherit taskgroup operatorand I log in with a user wh...

e.nieuwstad · 10-08-2013

hi is there a simple way to grant read access to everyhting so in stead of service = exec {task = "r...

e.nieuwstad · 08-19-2013

Even better ( I guess)Gold AC PSUs (N20-PAC5-2500W) below revision version of 341-0293-10 are missin...

e.nieuwstad · 08-19-2013

We had the exact same issue with one of our chassis. After several tac cases it turned out there was...

e.nieuwstad · 08-09-2013

we have this particular setup running with a N7K vpc cluster as DHD. Each N7K has one link to the ac...

Date Registered	‎04-10-2005 09:48 AM
Date Last Visited	‎04-06-2018 02:32 AM
Total Messages Posted	57
Total Helpful Votes Received	10

Re: ** Deprecated - Cisco UCS Python SD...

Re: ** Deprecated - Cisco UCS Python SD...

Re: ** Deprecated - Cisco UCS Python SD...

We are trying to establish

Xander, upgrade is working

ASR9001 upgrade with SP

Pseudowire redundancy

Re: ASR9000/XR Understanding Turboboot ...

SNMP status of hot standby port-channel...

Re: ASR9000/XR Using Task groups and un...

Re: ASR9000/XR Using Task groups and un...

Re: ASR9000/XR Using Task groups and un...

Chassis lost, UCS 2.1.2a

Chassis lost, UCS 2.1.2a

Re: ASR9000/XR: Multichassis LAG or MC-...

Re: Deprecated - Cisco UCS Python SDK - Deprecated

Re: Deprecated - Cisco UCS Python SDK - Deprecated

Re: Deprecated - Cisco UCS Python SDK - Deprecated

We are trying to establish

Xander, upgrade is working

ASR9001 upgrade with SP

Pseudowire redundancy

Re: ASR9000/XR Understanding Turboboot and initial System bring up

SNMP status of hot standby port-channel member

Re: ASR9000/XR Using Task groups and understanding Priv levels and authorization

Re: ASR9000/XR Using Task groups and understanding Priv levels and authorization

Re: ASR9000/XR Using Task groups and understanding Priv levels and authorization

Chassis lost, UCS 2.1.2a

Chassis lost, UCS 2.1.2a

Re: ASR9000/XR: Multichassis LAG or MC-LAG (MCLAG) guide