none
syndicating Azure marketplace content RRS feed

  • Question

  • Hello all,

    I have successfully registered my ASDK within an Azure account following https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-registration#register-disconnected-with-capacity-billing

    VERBOSE: 2018-09-11.15-59-35: Connection to AzS-ERCS01 successful
    VERBOSE: 2018-09-11.15-59-35: Activating Azure Stack (this may take up to 10 minutes to complete).
    VERBOSE: 2018-09-11.16-03-52: Removing any existing PSSession...
    VERBOSE: 2018-09-11.16-03-52: Your environment has finished the registration and activation process.
    VERBOSE: 2018-09-11.16-03-52: *********************** End log: New-AzsActivationResource ***********************

    Nevertheless I am not able to sync my ASDK Marketplace with Azure Content. I also get "You need to register and activate before you can start syndicating Azure marketplace content. Follow instructions here to register and activate"

    I got Internet Connection from my ASDK Host. Is there something else to do to get my marketplace synced?

    Thank you

    Wednesday, September 12, 2018 9:08 AM

All replies

  • Are you using an AAD or ADFS Deployment?

    Also, please be sure that you are logging into the Admin portal - https://adminportal.local.azurestack.external. 

    I see that you linked the steps for a disconnected environment, were you able to verify the registration?

    Wednesday, September 12, 2018 7:03 PM
    Moderator
  • Registration & activation were successfull. All Portal sites are browsable also. I think we got another Problem.

    Tracert from ASDK Host:

    PS C:\Windows\system32> tracert 8.8.8.8
    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  10.220.97.1
      2    <1 ms    <1 ms    <1 ms  10.220.255.5
      3    <1 ms    <1 ms    <1 ms  10.254.250.10
      4     *        *        *     Request timed out.

    Tracert from Azs-BGPNAT01:

    PS C:\Windows\system32> Enter-PSSession -ComputerName Azs-BGPNAT01
    [Azs-BGPNAT01]: PS C:\Users\AzureStackAdmin\Documents> tracert 8.8.8.8
    
    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2     *        *        *     Request timed out.
      3     *        *        *     Request timed out.
    The remote pipeline has been stopped.
        + CategoryInfo          : ResourceUnavailable: (:) [], ParentContainsErrorRecordException
        + FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException

    I tried a wireshark in promiscous mode an ASDK host an both tracerts look ok. TTL is decreased correct. However, I got timeouts on AZS-BGPNAT01. Also invoke-WebRequests from Azs-BGPNAT01 fail. Routing & Standard-GW seem to be ok.

    [Azs-BGPNAT01]: PS C:\Users\AzureStackAdmin\Documents> route print
    ===========================================================================
    Interface List
      2...02 63 c0 a8 c8 01 ......Microsoft Hyper-V Network Adapter #2
     14...02 63 0a dc 61 7a ......Microsoft Hyper-V Network Adapter
      1...........................Software Loopback Interface 1
      4...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
    ===========================================================================
    
    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0      10.220.97.1    10.220.97.122    281
          10.220.97.0    255.255.255.0         On-link     10.220.97.122    281
        10.220.97.122  255.255.255.255         On-link     10.220.97.122    281
        10.220.97.255  255.255.255.255         On-link     10.220.97.122    281
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
        192.168.102.2  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.3  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.4  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.5  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.6  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.7  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.8  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.102.9  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.10  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.11  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.12  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.13  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.14  255.255.255.255   192.168.200.64    192.168.200.1     15
       192.168.102.15  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.1  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.2  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.3  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.4  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.5  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.6  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.7  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.105.8  255.255.255.255   192.168.200.64    192.168.200.1     15
        192.168.200.0    255.255.255.0         On-link     192.168.200.1    271
        192.168.200.1  255.255.255.255         On-link     192.168.200.1    271
      192.168.200.255  255.255.255.255         On-link     192.168.200.1    271
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
            224.0.0.0        240.0.0.0         On-link     192.168.200.1    271
            224.0.0.0        240.0.0.0         On-link     10.220.97.122    281
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      255.255.255.255  255.255.255.255         On-link     192.168.200.1    271
      255.255.255.255  255.255.255.255         On-link     10.220.97.122    281
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
        192.168.200.0    255.255.255.0         On-link   Default
              0.0.0.0          0.0.0.0      10.220.97.1  Default
    ===========================================================================
    
    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    331 ::1/128                  On-link
      2    271 fe80::/64                On-link
     14    281 fe80::/64                On-link
      2    271 fe80::41d6:390d:f640:3790/128
                                        On-link
     14    281 fe80::596c:230c:a7e0:ac51/128
                                        On-link
      1    331 ff00::/8                 On-link
      2    271 ff00::/8                 On-link
     14    281 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

    Friday, September 14, 2018 2:06 PM
  • Are you having any other issues with the stack environment? This might not be an issue if you have connectivity in needed areas. 

    Also, to check for connectivity, it is best to use a TCP ping with PSPing or TNC. 

    Friday, September 14, 2018 7:02 PM
    Moderator